Juju Charms Collection

  1. Bug #1417407
  2. Comment #2

Comment 2 for bug 1417407

Revision history for this message
Jeff Lane  (bladernr) wrote : Re: haproxy enabled by default for keystone, cinder, openstack-dashboard, nova-cloud-controller and glance

I concur. To provide a little more detail, because this is enabled in the default charm, even non-HA openstacks become unusable when applying multiple services to the same machine outside of separate containers, which, until this point, has not really been an issue:

http://pastebin.ubuntu.com/10040950/

To really quickly duplicate it, all you need to do is:

juju bootstrap
juju deploy --to=0 --config=openstack.cfg keystone
juju ssh keystone/0
source ./nova.rc
keystone tenant-list
exit
juju deploy --to=0 --config=openstack.cfg nova-cloud-controller
juju ssh keystone/0
source ./nova.rc
keystone tenant-list

This is the contents of my openstack.cfg and nova.rc:

http://pastebin.ubuntu.com/10041027/

So I think now, the question is what is the suggested method for doing a non-HA installation? We were in the middle of working up a whitepaper with a customer when this change in the charms occurred. When we PoC'd our non-HA deployment and saved all the deployment steps for the whitepaper, this was not an issue.

Why do we simply not have charms called horizon and horizon-ha, nova-cloud-controller and nova-cloud-controller-ha and so on? (just curious why the decision to not rename them happened, was it a matter of maintenance in the future?)