lp://qastaging/~openstack-charmers-next/charms/trusty/neutron-openvswitch/trunk
- Get this branch:
- bzr branch lp://qastaging/~openstack-charmers-next/charms/trusty/neutron-openvswitch/trunk
Branch merges
Branch information
- Status:
- Development
Recent revisions
- 131. By James Page
-
Resync charmhelpers for licensing change
The charm-helpers project have re-licensed to Apache 2.0
inline with the agreed licensing approach to intefaces,
layers and charms generally.Resync helpers to bring charmhelpers inline with charm
codebase.Change-Id: I1b988a174d4a23
6599cffef8334a2 923bf031fff - 130. By James Page
-
Re-license charm as Apache-2.0
All contributions to this charm where made under Canonical
copyright; switch to Apache-2.0 license as agreed so we
can move forward with official project status.Change-Id: I7bd44dc15ad951
bf2536e5ee10de0 1ec592b8970 - 129. By Corey Bryant
-
Add defaults for openstack-
origin- git config option openstack-
origin- git currently only supports YAML that specifies
the git repositories to deploy from.This adds support for default openstack-
origin- git values. The
default values supported are: icehouse, kilo, liberty, mitaka,
and master. For example: openstack-origin- git=master. Change-Id: I032cb58283d54a
9ccfcc268a7fd70 b460a03aa58 - 128. By James Page
-
Switch to using charm-store for amulet tests
All OpenStack charms are now directly published to the charm store
on landing; switch Amulet helper to resolve charms using the
charm store rather than bzr branches, removing the lag between
charm changes landing and being available for other charms to
use for testing.This is also important for new layered charms where the charm must
be build and published prior to being consumable.Change-Id: I1b601d88e32368
b0f0705795ba032 72a13816bb2 - 127. By James Page
-
Support new style (and multiple) external networks
Note that this change only impacts use of this charm when
Distributed Virtual Routing is enabled in a deployment.Switch the generated configuration to use "new" style external
networks when ext-port is not set. In this case we configure:external_
network_ bridge = (intentionally blank)
gateway_external_ network_ id = (blank) The current template configures external networks by using the default
external_network_ bridge= br-ex (implied when not set). This activates
legacy code which assumes that a single external network exists on
that bridge and the L3 Agent directly plugs itself in.
provider:network_ type, provider: physical_ network and
provider:segmentation_ id are ignored. You cannot create multiple
networks and you cannot use segmented networks (e.g. VLAN)By setting external_
network_ bridge = (intentionally blank) the L2
Agent handles the configuration instead, this allows us to create
multiple networks and also to use more complex network configurations
such as VLAN. It is also possible to use the same physical connection
with different segmentation IDs for both internal and external
networks, as well as multiple external networks.Legacy/existing configurations where ext-port is set generate the same
configuration as previous and should continue to work as before.
Migration from legacy to new style configuration is not supported.Change-Id: I3d06581850ccbe
5ea77741c4a546e 663b2957a91
Closes-Bug: #1536768 - 125. By James Page
-
Resync charm helpers
Add support for OpenStack Newton and Ocata.
Rework version detection code to just match on major version for
OpenStack projects using semantic versioning.Provide fallback version detection based on major.minor versions
for swift packages.Rework config-flags support helpers.
Fix is_ip function to correctly detect both IPv4 and IPv6 addresses.
Change-Id: Iacf0f688a6a74d
badde8591f0fa05 c83d5c92b4e - 124. By James Page
-
Drop use of resolve_address
The shared secret context makes use of 'resolve_address' to
resolve the local_ip address of the unit; the resulting
value is not actually used in the metadata_agent.ini template
and breaks under Juju 2.0, where resolve_address attempts
to use network-get to resolve the public endpoint of the
service using extra bindings (which are not relevant for this
charm).Drop use of resolve address and tidy templates; the default
127.0.0.1 address is fine for accessing the Nova Metadata
service from the Neutron Metadata agent proxy.Change-Id: I03fc6d1c7c8ca8
32b02a7df5b1666 c04aaecc589
Close-Bug: 1580271 - 123. By James Page
-
Resync charm-helpers
Avoid use of 'service --status-all' which is currently
broken on trusty for upstart managed daemons; the change
moves to detecting how the daemon is managed, and then
using upstart status XXX or the return code of service XXX
status to determine whether a process is running.Fixes for IPv6 network address detection under Ubuntu
16.04 which changes the output format of the ip commands
slightly.Update the version map to include 8.1.x as a Neutron
version for Mitaka.Change-Id: I023dbb4b3d7e16
d7ec50e5b78636e 5c7688ff9cc
Closes-Bug: 1581171
Closes-Bug: 1581598
Closes-Bug: 1580674 - 122. By Liam Young
-
Restart services when trigger from principle
Check to see if a restart trigger has been sent by the principle,
if it has then right the trigger uuid in to the neutron.conf to
trigger a service restartChange-Id: I19649cb73dad94
f4fe24412c0b8c3 7a28f30047d
Partial-Bug: 1571634
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)