lp://staging/~bbaqar/charms/trusty/neutron-api/neutron-api-next
- Get this branch:
- bzr branch lp://staging/~bbaqar/charms/trusty/neutron-api/neutron-api-next
Branch merges
- OpenStack Charmers: Pending requested
-
Diff: 22 lines (+3/-0)2 files modifiedconfig.yaml (+1/-0)
hooks/charmhelpers/contrib/openstack/neutron.py (+2/-0)
Branch information
- Owner:
- Bilal Baqar
- Status:
- Development
Recent revisions
- 181. By David Ames
-
[Sunny Verma, r=thedac] vsd-cms-name passed for nuage >= kilo
This merge proposal include following changes:
1. Addition of vsd-cms-name in config file.
- This name is used to create the CMS ID on Nuage-VSD which should be unique per OSP cluster.2. Added nuage-packages in config file.
- Here you can mention what packages you want to install for as a part of nuage-plugin to neutron-api3. Added relation between Nuage-VSD and Neutron-Api.
- 180. By David Ames
-
[thedac, r=jamespage] Mitaka renamed neutron-
plugin- openvswitch- agent to neutron- openvswitch- agent fix amulet test - 177. By Liam Young
-
[gandelman-a, r=gnuoy]
Advertise API readiness to subordinates, allow subordinate specification of api_extensions
This advertises API readiness to subordinates via a new flag int the subordinate
relation. It determines readiness by the completion of required contexts. This
simply means the API service has enough of its topology completed to begin
servicing requests, and it has at least *started* the service (from the POV of
the init system). Its up to the subordinate service to ensure the API is
functional.It also allows subordinates to specify custom api_extension_paths to neutron-api.
- 174. By Edward Hope-Morley
-
[hopem,r=jamespage]
Sync charmhelpers to get support for supplying a Ascii Armor PGP key to
openstack-origin (currently only supports Radix64)
Closes-Bug: 1518975
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)