Unnamed repository; edit this file 'description' to name the repository. https://git.platform-os.org/openstack/kolla.git/atom?h=master 2016-11-16T04:34:17+00:00 2016-11-16T04:34:17+00:00 Steven Dake stdake@cisco.com 2016-11-16T02:01:25+00:00 urn:sha1:3fcef82946f7053affcfb0b1b3ef4292beb9fa95 Change-Id: I5396e4b9927d3e65b6aa4185238a43a4765a996b 2015-12-22T04:28:53+00:00 SamYaple sam@yaple.net 2015-12-18T19:40:48+00:00 urn:sha1:ed82afa8e928ac7c9f5ad2162be2c27eaab8e2e6 Convert config creation from a playbook to an action_plugin. This reduces the complexity and confusion while retaining the same augment structure and flexibility. This allows us to remove the 0-byte files as requirements. They will still be used if they are present (this means we require additional documentation around them). DocImpact Closes-Bug: #1528430 Change-Id: I2c789f6be9f195c7771ca093a6d59499564b4740 2015-09-01T06:15:27+00:00 Hengqing Hu hudayou@hotmail.com 2015-08-31T07:58:13+00:00 urn:sha1:1dab839de49be7ef92f274416b417b2007c1d9bd According to Python 3 Porting guide http://docs.pythonsprints.com/python3_porting/py-porting.html Exceptions were changed in a few ways for Python 3. First, strings are no longer usable as exceptions. Additionally, the raise syntax no longer accepts comma-separated arguments, instead working with exception instances. Perhaps the largest difference in Python 3 is that exception objects are only available via the as keyword, which was introduced in 2.6. Change-Id: Ide665ecc4b7f14bd58bafab47e05a86a4cf2d141 Closes-Bug: #1490526 2015-07-27T10:06:55+00:00 Sam Yaple sam@yaple.net 2015-07-27T10:06:55+00:00 urn:sha1:53c0ada479815ef019e2a79bcf9e85d66810bb3a There is no benefit to hashing in merge_configs.py In fact, the opposite is true, hashes can collide. This does a direct compare rather than hash. Change-Id: I9ab7af13e813e2267984092027daf1658faf5bf3 Closes-Bug: #1478494 2015-07-12T03:14:49+00:00 Sam Yaple sam@yaple.net 2015-07-08T08:23:09+00:00 urn:sha1:05a6640a0fadd25603c5fe63483e1fab4f19d2ac Due to the licensing issues and the modules not existing in upstream Ansible yet, I have written a simple module to fill the gaps. This also uses Keystone v2.0 for all create of users, roles and endpoints. The implementation of Keystone v3 must be discussed after the new modules arrive. Partially-Implements: blueprint ansible-service Change-Id: I389edd56741360dd26fbbc0a982f365ca27ff446