| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
In 9eb3db84, Bcfg2.Server.Admin.Mode.__call__() was changed from
pass to raise a NotImplementedError. This causes bcfg2-admin
compare and bcfg2-admin snapshots to fail because they call
Bcfg2.Server.Admin.Mode.__call__() right away. Since that method
didn't do anything anyway, it seems expediant to just avoid the call
altogether.
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
|
|
|
| |
While a lot of these dependencies can be useful, they aren't necessarily
required unless you expect to use particular functionality.
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
|
|
|
| |
Current RHEL variants and all supported Debian variants have python-ssl
support either via the builtin module or a backported python-ssl.
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
|
|
| |
The corresponding documentation was removed in ca6abe45.
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| |
|
| |
|
| |
|
|\
| |
| | |
Reporting: start a new thread for each import
|
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit f813f86f8ac2bc7b55f4eb6a0d936f1ce4f68ba7. Premature
optimization is the root of all evil, etc.
Conflicts:
src/lib/Bcfg2/Reporting/Collector.py
|
| |
| |
| |
| |
| |
| | |
1. Use a better convention for calling the threading.Thread constructor
2. Add docstring to ReportingStoreThread.run
3. Give the storage thread variable a better name
|
| |\
| |/
|/|
| | |
reporting-thread-each-data-import
|
| | |
|
|\ \
| | |
| | | |
Tests: Fix tests after 9a6a231
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This ensures consistency between the in-memory representation of
clients.xml and the representation on disk. If we don't read our
writes immediately, there's a race condition when creating a new
client: If it asserts its profile or version before the FAM event from
the clients.xml edit is processed, then the clients doesn't appear to
exist yet, and Bcfg2 complains.
|
| | | |
|
| | |
| | |
| | |
| | | |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| | | |
|
| | | |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When dealing with a high-latency database connection (eg. across a
WAN), the bcfg2-report-collector process can fall behind in its
import queue. The imports are very much bound by the response
latency of the database server and not processing throughput.
This patch fires off a new thread for each database interaction.
The thread itself simply falls out of scope when the interaction
is finished processing. The interaction object is still read from
the disk serially in order avoid having to create a locking mechanism
for that part of the process.
This change does potentially create greater load on the database
server, but ultimately the load is limited by rate at which the
bcfg2 server can generate work.
|
|/
|
|
|
|
|
|
| |
The addition of the call to load_xml in 9a6a231 causes the test to
fail because load_xml() expects to read a clients.xml file. The
actual actual open calls in write_xml are dummied out with Mock,
so no file is written, and thus cannot be read back. This commit
dummies out the load_xml and adds some more asserts for good measure.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
AWSTags allows querying tags from EC2, and setting groups based on the
tag names or values.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
The duplicate group check parsed groups differently from the actual
groups.xml parsing routines; the latter followed the documentation,
while the duplicate group check did now. This fixes the duplicate
group check to parse groups.xml correctly when looking for duplicates.
Fixes #140
|
|
|
|
|
|
|
| |
Reported on IRC:
http://colabti.org/irclogger/irclogger_log/bcfg2?date=2013-09-16;raw=on
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
|
|
| |
Instead of mocking get_filename, use its normal functionality. This
avoids a messy situation where we have to mock out a **magic call,
which py2.5 doesn't like at all.
|
|
|
|
|
|
|
|
|
| |
created
Previously, only two cases were handled properly: both public and
private keys had been created; or neither had been created. If the
private key had been created (e.g., manually added to the repo), the
public key would not be created from it. This fixes that.
|
|
|
|
|
|
| |
When installing an entry with no ACLs specified, but with ACLs on the
file as it exists on the filesystem, the ACL mask was preserved, even
as the ACLs are deleted.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| |
|
|
|
|
|
| |
Connector plugins can now create new groups, including the full range
of options on those groups (profile, public, category, etc.).
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This monitors XIncluded files even if should_monitor=False, since the
object monitoring the base file will not monitor XIncludes. This
ensures that XIncluded files are properly monitored whenever possible,
particularly for Bundler and Properties.
This is a partial backport of 5b66845 -- as much of a backport as is
possible without a module-level FAM object.
|
|\
| |
| |
| |
| | |
kincl/pre-action-processing-with-independent-entries
Pre action processing with independent entries
|
| | |
|