lp:~openstack-charmers/charms/trusty/neutron-gateway/next
- Get this branch:
- bzr branch lp:~openstack-charmers/charms/trusty/neutron-gateway/next
Branch merges
Branch information
- Owner:
- OpenStack Charmers
- Status:
- Development
Recent revisions
- 199. By Corey Bryant
-
Use os_release() and blacklist python-pymysql for DFS
Use os_release() instead of get_os_
codename_ install_ source( ) to
determine the OpenStack release where possible. Make this change
in all paths that deploy from source uses because it checks both
openstack-origin and openstack-origin- git when determining the
release.Also don't install python-pymysql deb when deploying from source.
Change-Id: I0b8ea17c5b06ef
8ab6cf6c4cfd0a2 f4721615b91 - 198. By Liam Young
-
Pre 1607 release charm-helpers sync
Sync charmhelpers to pick up bug fixes for 1607 release
Change-Id: Iba9fab03a12d07
dae14d54c9d080f f807af8ad94 - 197. By James Page
-
Enable use of use_neutron flag
For mitaka onwards, use of the 'use_neutron' flag should be made
instead of setting the network API class.For newton, this is required as the network_api_class is ignored.
Change-Id: Idcf2d080b90909
f4b52b45826118d 7c6be20ae05 - 196. By James Page
-
Use bundletester for amulet test execution
Switch to using bundletester for execution of functional tests,
leveraging tox to build out test virtualenvs.Rename amulet tests inline with gate-* and dfs-* naming standards.
Update README to refer to functional testing section of the charm
guide.Change-Id: I9b36f8a6375da5
cf5807d51e1d009 c47d74dc1dd - 195. By David Ames
-
Pre-release charm-helpers sync
To begin release testing get each charm up to date with lp:charm-helpers
Change-Id: Ib5307473c7cba6
5c816bed923c1ed 82e2d988f47 - 194. By Corey Bryant
-
Various deploy from source changes and c-h sync
* openstack-origin is no longer required when using openstack-
origin- git.
* Drop kilo from openstack-origin- git default values because upper
constraints doesn't work in kilo for openstack-dashboard and glance.
* Add flag to allow for disabling upper constraints when using
openstack-origin- git with user-specified git repositories. Change-Id: I37a1cc5f767cbc
4d035ee534437ff 66ca7100751 - 193. By James Page
-
Avoid restart races for nova-api-metadata
It's possible that the nova-api-metadata will startup during the
time that the nova-conductor processes on the nova-cloud-controller
units are still starting up, resulting in a messaging timeout which
causes the daemon to exit 0.Upstart will restart a service in this scenario, however systemd is
configured in packaging to only restart 'on-failure' so will not
attempt to restart.This points to two other bugs - one that a messaging timeout results
in a exit code of 0, and that the OpenStack services under systemd
behave differently to under upstart.Install an override file for systemd based installs to mimic the
behaviour of upstart, and deal with a code logic problem in the
restart_trigger handling to ensure that the charm does at least
try to restart the nova-api-metadata service at the right points
in time.Change-Id: Ia08b7840efa33f
d301d0e2c55bb30 ae1a102cbfa
Closes-Bug: 1547122 - 192. By James Page
-
Use correct relation key for restarts
The nova-cloud-
controller charm set the relation key 'restart_trigger';
this charm was using 'restart_nonce' which obviously never gets set,
so the nova-api-metadata service would never actually get restarted
when required.Use the correct relation key, fixing remote restart triggers for
nova-api-metadata, resolving races in deployment.Change-Id: Ic3dbdd41f87c03
62f7f725d0f5845 8f5239ea093
Closes-Bug: 1547122 - 191. By Corey Bryant
-
Add systemd init support for deploy from source
systemd is used instead of upstart by default since Ubuntu 15.10
(Wily). This adds systemd init file support for nova services
that are deployed from source.Change-Id: I784e6b99082229
95c56c9f3c06cc5 4f0254d4761
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)