lp:charms/neutron-gateway

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

200. By Narinder Gupta on 2016-08-12

Enable neutron gw charm to control # of workers

Charm was missing this functionality and this patch is to add
this feature. We were trying to deploy this charm on bare metal
host machine with 72 cores. In end up creating 144 processes for
nova-metadata-api, and neutron.

This patch will provide the option to limit the number of worker
process in case of high number of cores in a host.

Enable it for icehouse, kilo, liberty and mitaka.

cherry picked from commit 93d6440e459f19676ce9336332e4f91efc85897f

Partial-Bug: 1600482
Change-Id: Iedcbe6c53746a203937b78dd00e83fda7681bd8f

199. By David Ames on 2016-07-28

Updates for stable branch creation for 16.07

Set defaultbranch for git review/gerrit.
Switch amulet tests to stable.
Switch to using stable charm-helpers branch.

Change-Id: I4c8d4374b6f383d763ee64aaec3c53789e3e1c0e

198. By Liam Young on 2016-07-21

Pre 1607 release charm-helpers sync

Sync charmhelpers to pick up bug fixes for 1607 release

Change-Id: Iba9fab03a12d07dae14d54c9d080ff807af8ad94

197. By James Page on 2016-07-20

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: Idcf2d080b90909f4b52b45826118d7c6be20ae05

196. By James Page on 2016-07-18

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: I9b36f8a6375da5cf5807d51e1d009c47d74dc1dd

195. By David Ames on 2016-07-15

Pre-release charm-helpers sync

To begin release testing get each charm up to date with lp:charm-helpers

Change-Id: Ib5307473c7cba65c816bed923c1ed82e2d988f47

194. By Corey Bryant on 2016-07-13

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: I37a1cc5f767cbc4d035ee534437ff66ca7100751

193. By James Page on 2016-07-12

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: Ia08b7840efa33fd301d0e2c55bb30ae1a102cbfa
Closes-Bug: 1547122

192. By James Page on 2016-07-08

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: Ic3dbdd41f87c0362f7f725d0f58458f5239ea093
Closes-Bug: 1547122

191. By Corey Bryant on 2016-07-07

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: I784e6b9908222995c56c9f3c06cc54f0254d4761