Canonical Juju

  1. Bug #1357760
  2. Comment #2

Comment 2 for bug 1357760

Revision history for this message
Blake Rouse (blake-rouse) wrote :

Dang it I would really like to see this fixed. I am trying to setup Juju in a HA configuration using the manual provider for deploying MAAS 2.0 in HA configuration. Here is the setup I am trying to do for this configuration.

The following would be done using the manual provider.

physical-0 (bootstrap)
  machine-1 (lxc, postgres)
  machine-2 (lxc, maas-region)

physical-1 (enable-ha)
  machine-3 (lxc, postgres)
  machine-4 (lxc, maas-region)

physical-2 (enable-ha)
  machine-5 (lxc, postgres)
  machine-6 (lxc, maas-region)

With juju in HA and MAAS in HA then the same Juju could be pointed at the deployed MAAS. So you use Juju to deploy MAAS, then you use the same Juju to deploy OpenStack on MAAS, then you use the same Juju to deploy workloads on that OpenStack.

Not supporting the manual provider in this kinda hurts as with deploying MAAS you will most likely use the manual provider as you have nothing to start with for Juju to connect. I have Juju deploying MAAS in HA, I am only missing this "enable-ha" for Juju.

Here is the output for Juju using 2.0-beta5:

blake@blake-ubnt-desktop:~/Code$ juju status
[Services]
NAME STATUS EXPOSED CHARM

[Units]
ID WORKLOAD-STATUS JUJU-STATUS VERSION MACHINE PORTS PUBLIC-ADDRESS MESSAGE

[Machines]
ID STATE DNS INS-ID SERIES AZ
0 started 192.168.122.2 manual: xenial
1 started 192.168.122.3 manual:192.168.122.3 xenial
2 started 192.168.122.4 manual:192.168.122.4 xenial

blake@blake-ubnt-desktop:~/Code$ juju enable-ha --debug
2016-04-26 01:53:18 INFO juju.cmd supercommand.go:60 running juju [2.0-beta5 gc go1.6.1]
2016-04-26 01:53:18 INFO juju.juju api.go:213 connecting to API addresses: [192.168.122.2:17070 192.168.122.3:17070 192.168.122.4:17070]
2016-04-26 01:53:18 INFO juju.api apiclient.go:494 dialing "wss://192.168.122.2:17070/model/8177eb7c-c21d-4449-89e9-deff1a925aea/api"
2016-04-26 01:53:18 INFO juju.provider.manual provider.go:159 enable-os-refresh-update was not defined. Defaulting to true.
2016-04-26 01:53:18 INFO juju.provider.manual provider.go:159 enable-os-upgrade was not defined. Defaulting to false.
2016-04-26 01:53:18 INFO juju.api apiclient.go:271 connection established to "wss://192.168.122.2:17070/model/8177eb7c-c21d-4449-89e9-deff1a925aea/api"
2016-04-26 01:53:18 DEBUG juju.juju api.go:362 API hostnames unchanged - not resolving
2016-04-26 01:53:18 DEBUG juju.juju api.go:147 failed to connect via bootstrap config: aborted
2016-04-26 01:53:18 DEBUG juju.api apiclient.go:520 health ping failed: connection is shut down
2016-04-26 01:53:18 ERROR cmd supercommand.go:448 failed to create new controller machines: use "juju add-machine ssh:[user@]<host>" to provision machines