| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| | |
|
| | |
|
|/
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|\ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The HelperModules of the TemplateHelper now expects a second argument with
the core, to be able to expire the metadata cache.
This is a fix-up for 36b2aa66627a4cc147f982d03688ae9df14bbe08.
|
|\ \ \ |
|
| | |/
| |/| |
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | | |
Newer versions of mock, does not support the CamelCase calls.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Be flexible and support the imports required by newer versions of the mock
package (>1.1.0). Because this new version is not available on all distributions
we are flexible and also support the old style.
|
|\ \ \ \ |
|
| | | | | |
|
| | |/ /
| |/| |
| | | |
| | | | |
Treat this the same as selinux.matchpathcon.
|
|\ \ \ \
| |_|/ /
|/| | | |
|
| | | |
| | | |
| | | |
| | | | |
generate
|
| | | | |
|
| |/ / |
|
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Install() of a client tool returns the changed states as dict, that will update
the global state. If nothing is handled withing a tool, it have to return an empty
dict and not None because the return value is directly used as argument for update:
> APT.Install() call failed:
> Traceback (most recent call last):
> File "/usr/lib/python2.7/dist-packages/Bcfg2/Client/__init__.py", line 739, in DispatchInstallCalls
> self.states.update(tool.Install(handled))
> TypeError: 'NoneType' object is not iterable
|
| |
| |
| |
| |
| |
| |
| | |
We are moving away from ANL hosting since we no longer have anyone there
who is involved in managing the project.
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| |
| |
| |
| | |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| |
| |
| |
| | |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|\ \
| | |
| | | |
Client/Tools/Systemd: Find extra entries
|
| | |
| | |
| | |
| | | |
Add FindExtra to get a listing of all extra systemd entries.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
You can add now a list of aliases to a Subcommand to make it available with
different names. Each alias in the list is used without modification,
especially the aliases do not get converted to lower case (this is for example
required for "EOF").
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
The expirecache subcommand is only usefull from an interactive shell, so
do not advertise it in the help from the commandline.
|
| | |
| | |
| | |
| | | |
The expirecache subcommand was using an old API.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Some subcommands only makes sense, if they are called from an interactive
shell and to interface a running server. Now we can mark a Subcommand
as only_interactive and it will not be callable as argument from the command
line.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
We change the parser namespace so contain all the global flags. So we silently
erase the parser cache and have to set the parsed flag, so that the Parser
does not use our "empty" new namespace as cached result.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Expirecache is now part of bcfg2-admin and will call expire_metadata_cache
from Core via XML-RPC. This will expire the metadata cache of the supplied
clients (or the complete cache if no arguments are supplied) on a running
bcfg2-server.
|
|\ \ \
| | | |
| | | | |
Reporting: Do not fail, if no interactions found
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
With the filter feature of bcfg2-reports it is possible that all
interactions of a client gets filtered. Now we simply skip those clients
without interactions and do not fail with an exception.
|
|\ \ \ \
| | | | |
| | | | | |
Expire metadata cache in all Connector plugins.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The data returned by Connector.get_additional_data is also cached, so the
plugin needs to invalidate the caches, even if it does not implement
Connector.get_additional_groups.
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
AWSTags cannot know whether the tags change, so it cannot expire the
metadata cache correctly. Instead we have to expire the cache at
beginning of each client run. This practically disables agressive
client metadata caching, so we print a warning.
|
| | | | |
| | | | |
| | | | |
| | | | | |
This was maybe missing in 38f3cfcfd.
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
SSHbase supply the public keyfiles as additional metadata, so we need to
expire the metadata cache if we get an event for such file. We would only
need to expire the metadata cache for hosts, that reference that exact file
(host or group specific) but we cannot get this information, so that we
simply expire the metadata cache for all hosts.
|
| | | | | |
|