Multiple networks with JUJU and 3rd party Cinder integration.

[Dimiter Naydenov]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 25.10.2014 03:13, Mark Shuttleworth wrote:
> On 24/10/14 15:28, Nate dell wrote:
>> I'll look at binding specific cdrs to the openstack charms. It
>> sounds like your suggesting using a configuration management
>> system like salt, ansible, puppet, or chef in conjunction with
>> juju. Ansible is setup at the client so will look to integrate
>> the two, was reluctant to do that out of fears they would step on
>> each other. The IRC channel has been very helpful in providing
>> suggestions on how to proceed on the cinder side.

Hey Nate,

Thanks for considering Juju for your scenario!

> 
> The different systems can easily be made to be polite to one
> another :)
> 
> In a little while you'll be able to specify a charm to put on
> every machine, or groups of machine, and that will probably be a
> cleaner way to handle the baseline machine setup.
> 
> Mark
> 
In the mean-time, until Juju starts to provide this feature, you can
consider a workaround.

It looks like all openstack charms can have a subordinate unit (on the
same machine) via the hacluster relation. If you write a shared
subordinate charm, deploy it, and relate it to the openstack services
you need to configure, you can have the same code executing on each
machine.

I hope this helps,
- -- 
Dimiter Naydenov <dimiter.naydenov at canonical.com>
juju-core team
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJUS909AAoJENzxV2TbLzHw7qoH/3T1fxB1ugJ5cJUTGvlPIF6p
BPq0xe3VwS82aCFDEbZZMwOsWhb8IlWtcuDTc0kS0zJRm5ZVwq0CZq5tIIYC30+V
pDmKBqGup8O6W8WyqWv80vssUOFt1gfMhL8OrRNJO/pklXD7J4i9qDiIx/Y3dYBu
vQBh8RbHZ0V/mESQ7yMgrJ1k9KdbvTLxpnUk5m+J2EfBAGfGbWZEdSeakGPb6DSo
yebmR1ThI0AP+srxx1mlDUo6p0MbNXe4VXlDu2oG8nOJg7A6sYKuCyYICO4lgq3p
gomxILNLHARCPY0O8tjNqQAiykW+OxdzxE1v0pb96xVnIrjpe1h50Ba3qrDwvX4=
=dhJp
-----END PGP SIGNATURE-----