summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* doc: Fix release notes to point to new download locationHEADmasterSol Jerome2015-11-131-1/+1
| | | | | | | 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>
* doc: Add 1.4.0pre2 release notes to tocSol Jerome2015-11-131-0/+1
| | | | Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
* Version bump to 1.4.0pre2Sol Jerome2015-11-1316-16/+22
| | | | Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
* Merge pull request #301 from AlexanderS/feature/systemd-extraChris St. Pierre2015-10-201-0/+14
|\ | | | | Client/Tools/Systemd: Find extra entries
| * Client/Tools/Systemd: Find extra entriesAlexander Sulfrian2015-07-271-0/+14
| | | | | | | | Add FindExtra to get a listing of all extra systemd entries.
* | Info: EventDebug, Update and Quit are now command classesAlexander Sulfrian2015-10-131-17/+26
| |
* | Options: Add possibility to have aliases for commandsAlexander Sulfrian2015-10-131-12/+20
| | | | | | | | | | | | | | 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").
* | DefaultACL: Deny remote access to expire_metadata_cacheAlexander Sulfrian2015-10-131-1/+2
| |
* | Info: expirecache only for interactive shellAlexander Sulfrian2015-10-131-0/+1
| | | | | | | | | | The expirecache subcommand is only usefull from an interactive shell, so do not advertise it in the help from the commandline.
* | Info: Fix expirecache subcommandAlexander Sulfrian2015-10-131-5/+4
| | | | | | | | The expirecache subcommand was using an old API.
* | Options: Add possibility to have interactive only SubcommandsAlexander Sulfrian2015-10-131-5/+14
| | | | | | | | | | | | | | 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.
* | Info: Fix bcfg2-info shellAlexander Sulfrian2015-10-131-25/+47
| |
* | Options: Really reparse the argument list of SubcommandsAlexander Sulfrian2015-10-131-0/+1
| | | | | | | | | | | | 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.
* | Admin: Add expirecache commandAlexander Sulfrian2015-10-132-0/+34
| | | | | | | | | | | | | | 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.
* | Merge pull request #309 from AlexanderS/fix/report-filtersChris St. Pierre2015-10-131-12/+31
|\ \ | | | | | | Reporting: Do not fail, if no interactions found
| * | Reporting: Do not fail, if no interactions foundAlexander Sulfrian2015-09-181-12/+31
| | | | | | | | | | | | | | | | | | 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.
* | | Merge pull request #299 from AlexanderS/fix/cachingChris St. Pierre2015-10-0511-32/+99
|\ \ \ | | | | | | | | Expire metadata cache in all Connector plugins.
| * | | doc: Fix docs about cachingAlexander Sulfrian2015-07-271-4/+6
| | | | | | | | | | | | | | | | | | | | | | | | 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.
| * | | Properties: Expire the metadata cache during reload of the filesAlexander Sulfrian2015-07-272-14/+42
| | | |
| * | | Probes: Use core.metadata_cache instead of Bcfg2.Server.CacheAlexander Sulfrian2015-07-271-7/+8
| | | |
| * | | AWSTags: Expire metadata cache at start of client runAlexander Sulfrian2015-07-271-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| * | | PuppetENC: Fix cache expirationAlexander Sulfrian2015-07-271-1/+1
| | | | | | | | | | | | | | | | This was maybe missing in 38f3cfcfd.
| * | | GroupLogic: Expire metadata cache on config file changesAlexander Sulfrian2015-07-271-1/+12
| | | |
| * | | SSHbase: Expire metadata cache on pubkey eventAlexander Sulfrian2015-07-271-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| * | | Ohai: Expire metadata cache, if ohai data changesAlexander Sulfrian2015-07-271-1/+6
| | | |
| * | | TemplateHelper: Expire metadata cache on FileMonitor eventAlexander Sulfrian2015-07-272-4/+15
| | |/ | |/|
* | | Merge branch 'fix/django1.7' of https://github.com/AlexanderS/bcfg2Sol Jerome2015-10-0130-2150/+2977
|\ \ \
| * | | Reports: Use try/except and no version comparisonAlexander Sulfrian2015-09-291-3/+2
| | | |
| * | | tools/upgrade: Fix checking for related fieldsAlexander Sulfrian2015-09-291-7/+9
| | | | | | | | | | | | | | | | | | | | If we check for the existance of a related object, newer django versions (>= 1.5) raise a ObjectDoesNotExist exception and we have to handle it.
| * | | Reporting: Add django.setup()Alexander Sulfrian2015-09-291-0/+3
| | | | | | | | | | | | | | | | | | | | bcfg2-reports does not call sync_databases or migrate_databases before making the database queries. So we need to initialize django here, too.
| * | | Reporting: Replace get_template_from_string() for django 1.8Alexander Sulfrian2015-09-231-2/+9
| | | | | | | | | | | | | | | | | | | | Django 1.8 introduced different template engines and droped the get_template_from_string function as it does not support the new feature.
| * | | DBSettings: XViewMiddleware was moved into another packageAlexander Sulfrian2015-09-231-2/+8
| | | | | | | | | | | | | | | | The old name was deprecated with django1.6 and removed with django1.8.
| * | | Reporting: Replace _meta.get_all_field_names() for django 1.8Alexander Sulfrian2015-09-231-1/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The _meta API was changed with django 1.8 and get_fields() now returns all model fields even fields defined in related models. But while creating the Entries we use this field list for construction and the list should only contain local fields.
| * | | Reports: Add explicit default valueAlexander Sulfrian2015-09-231-1/+1
| | | | | | | | | | | | | | | | | | | | Django changed the default value for BooleanFields some time ago, so we add an explicit default value to remove the warnings.
| * | | Reports: Fix InternalDatabaseVersionAlexander Sulfrian2015-09-232-14/+23
| | | | | | | | | | | | | | | | | | | | | | | | You could not import a class, that is defined in a function. We need to return the class, but we do not want to define it multiple times. So we have to save the class in a global variable.
| * | | DBSettings: allow_syncdb is replaced with allow_migrateAlexander Sulfrian2015-09-231-1/+8
| | | |
| * | | Reporting: Do not use django.db.backend in newer django versionsAlexander Sulfrian2015-09-232-12/+22
| | | | | | | | | | | | | | | | | | | | | | | | The private API django.db.backend is deprecated in django 1.7 and removed in django 1.8, so we use another way to get the DatabaseOperations from the connection.
| * | | tools/upgrade: Support multiple databasesAlexander Sulfrian2015-09-231-3/+5
| | | | | | | | | | | | | | | | | | | | Do not use the global django connection object but the matching instance from the django connections list.
| * | | tools/upgrade: Parse the Options before using djangoAlexander Sulfrian2015-09-231-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | We need to go through the Options parsing before we could use django and import the models. The Options parsing will setup django and prepare the required settings.
| * | | Replace close_connection() for newer django versionsAlexander Sulfrian2015-09-232-4/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | django.db.close_connection() is deprecated in django1.7 (and removed in 1.8). The new django.db.close_old_connections() does not seem to work like the old one (see http://stackoverflow.com/a/32614137), so we replace it with an own implementation.
| * | | Server: Use close_db_connection decorator everywhereAlexander Sulfrian2015-09-231-4/+1
| | | |
| * | | Server/Admin: Remove load_models() callAlexander Sulfrian2015-09-231-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | The models should be loaded during the options parsing and so this call issues a warning message from django, that the models are already registered.
| * | | Server/Admin: Remove call of django.setupAlexander Sulfrian2015-09-231-3/+0
| | | | | | | | | | | | | | | | django.setup() is already called from the option parsing before.
| * | | DBSettings: syncdb is replaced by migrateAlexander Sulfrian2015-09-231-2/+4
| | | |
| * | | DBSettings: Automatically upgrade migrations from south to djangoAlexander Sulfrian2015-09-231-0/+43
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | On the first use with django-1.7 we manually get the south migration status and fake apply the django migration to that point. With that users can switch to django migrations at any point of time. The code simply takes the name of the last south migration and forwards the django migrations to that point. Therefor it is required to keep the names of the migrations in sync. It is required to keep the migration names of the two systems in sync.
| * | | Add matching django migrations for southAlexander Sulfrian2015-09-237-272/+411
| | | |
| * | | Reporting: Clear error message if django is missingAlexander Sulfrian2015-09-231-8/+7
| | | |
| * | | fix check for reporting in src/lib/Bcfg2/Server/Plugins/Reporting.pyJonas Jochmaring2015-09-231-7/+11
| | | |
| * | | added django.setup() calls to src/lib/Bcfg2/DBSettings.pyJonas Jochmaring2015-09-232-2/+6
| | | |
| * | | update testsuite for django 1.7Jonas Jochmaring2015-09-231-0/+4
| | | |
generated by cgit v1.2.3-1-g7c22 (git 2.25.1) at 2024-05-06 05:58:54 +0000