lp:~openstack-charmers-next/charms/precise/rabbitmq-server/trunk

Created by James Page on 2015-09-21 and last modified on 2016-07-08
Get this branch:
bzr branch lp:~openstack-charmers-next/charms/precise/rabbitmq-server/trunk
Members of OpenStack Charmers - Testing Charms can upload to this branch. Log in for directions.

Branch merges

Related bugs

Related blueprints

Branch information

Owner:
OpenStack Charmers - Testing Charms
Status:
Development

Recent revisions

152. By James Page on 2016-07-08

Ensure rabbit hosts are resolvable

The update_hosts_file function requires a full map of entries to
write into /etc/hosts; the previous use of this function tried
to write individual host entries only.

Ensure that a full map of self + peers is written at appropriate
points in a units lifecycle to ensure self and peer hostname
resolvability.

(also fixed a typo in a status message)

Change-Id: If40b31a55641861a1e03985f318e012b545fcc25
Closes-Bug: 1592200
Closes-Bug: 1590085

151. By James Page on 2016-07-07

Complete switch to using charm-store for amulet

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

150. By James Page on 2016-07-06

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

149. By James Page on 2016-07-01

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

148. By Alex Kavanagh on 2016-06-17

Fix for multiple status_set() in assess_status()

This fixes a multiple status_set() bug in the implementation of assess_status()
on the charm, when it is determining whether it is active AND clustered.
The change hooks into the _determine_os_workload_status() directly in
charmhelpers to ensure that status_set() is only called once when
assess_status() is called.

Change-Id: Idfd93126c3edb41f83897c82ee7f20fe5f366559
Related-Bug:#1588462

147. By James Page on 2016-05-27

Resync charm helpers

This brings in a few changes, but specifically of interest is the
change to is_ip which correctly detects both IPv4 and IPv6 addresses,
resolving problems when Juju presents an IPv6 based private-address
back to the charm.

Change-Id: I3b6391053db83c8b3f1662f010783703b1f16d0a
Closes-Bug: 1574844

146. By James Page on 2016-05-26

Refactor hostname resolution via DNS

Due to oddities in the way that DNS used to work on older MAAS
versions, specifically when using LXC containers, the charm
would endeavour to discover a full forward/reverse resolvable
hostname/ip address to use when clustering with peers, and to
set the internal nodename for each RMQ instance.

Changes in MAAS 2.0 mean that an IP address may resolve to more
than 1 DNS record, making identification via DNS of the FQDN
problematic.

The charm actively manages /etc/hosts with IP address/hostname for
all peer units in a RMQ cluster using the cluster relation; make
use of this feature to allow the internal nodename of each unit
to actually be the hostname of the server, as the charm is ensuring
the resolvability of hostnames within the cluster.

To avoid races where the lead unit has not had its hostname written
to /etc/hosts, only cluster with the lead unit in the hook execution
where this actually happens.

Change-Id: Ia400c3b6e2cb1a5f2ee6f5fe98b5437033e02024
Closes-Bug: 1584902

145. By James Page on 2016-05-18

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: I947e783052fc77c70c0ffec2e0159a20a92215cc
Closes-Bug: 1581171
Closes-Bug: 1581598
Closes-Bug: 1580674

144. By David Ames on 2016-04-15

Do not check for rabbit user before installed

The charm was trying to lookup the rabbit user before rabbitmq-server
was installed. Check for installation state before doing so.

Change-Id: I25eb8e26d3e01b13e13205a41e4f1f2e924d96f7
Closes-Bug: #1570970

143. By Liam Young on 2016-04-13

Fix pbr requirement

Change-Id: I508ff26eaa14b17a9ba3f9ff10b82758da01340a

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
Stacked on:
lp:charms/rabbitmq-server
This branch contains Public information 
Everyone can see this information.