openstack-base: Need a better name that includes novaKVM and MAAS

[adam-stokes]

Currently the name in the list is OpenStack with NovaKVM which includes the use of MAAS. However, this may be confusing or unknown so we need a better name that includes both Nova with KVM and the use of MAAS.

Suggestions welcomed!

Current proposal

OpenStack Nova-KVM on MAAS
OpenStack Nova-KVM in LXD
OpenStack Nova-KVM Telemetry on MAAS
OpenStack Nova-KVM Telemetry in LXD
OpenStack Nova-LXD on MAAS
OpenStack Nova-LXD in LXD

[ryan-beisner]

Typically we don't specify Nova KVM in the title of scenarios, as it's the default. But I can see where you might want to differentiate in the UI.

The published charm store bundles openstack-base and openstack-telemetry both use nova-kvm and are targeted to metal deployments via the Juju MAAS provider.

The published charm store bundle openstack-lxd uses nova-lxd and is targeted to metal-deployments via the Juju MAAS provider.

The developer scenario which places openstack on a single machine via the Juju LXD provider is named openstack-on-lxd: http://docs.openstack.org/developer/charm-guide/openstack-on-lxd.html

To translate that, I see 6 combos of what (bundle) and how (provider).

Perhaps this?:

OpenStack Nova-KVM Base on MAAS
OpenStack Nova-KVM Base on LXD
OpenStack Nova-KVM Telemetry on MAAS
OpenStack Nova-KVM Telemetry on LXD
OpenStack Nova-LXD on MAAS
OpenStack Nova-LXD on LXD

[adam-stokes]

The developer scenario which places openstack on a single machine via the Juju LXD provider is named openstack-on-lxd: http://docs.openstack.org/developer/charm-guide/openstack-on-lxd.html

Thanks, side note, what does conjure-up need to do in order to get added to those docs?

[ryan-beisner]

I was thinking the same -- we should lead with a reference and pointer to conjure-up in that doc. Having said that, we do intend to continue to maintain that procedure in the raw, at that location.

As far as getting it added, it's an OpenStack upstream repo, which takes proposals via gerrit in line with all other OpenStack upstream projects.

Please see:

• http://docs.openstack.org/developer/charm-guide/how-to-contribute.html
• http://docs.openstack.org/developer/charm-guide/find-us.html

Feel free to either raise a review, discuss in #openstack-charms, and/or hop on the next meeting.

Cheers.

[adam-stokes]

Thanks @ryan-beisner, I believe we're going to keep the 1:1 spell bundle ratio and I'll start adding those additional spells to satisfy that list you posted in the previous comment. If you get time could you post the jujucharms.com URLS for those bundles (if they exist) or if we need to pull down the openstack-base bundle and alter accordingly.

[ryan-beisner]

The stable OpenStack Charmer bundles are published here, and are all targeted to MAAS:

• https://jujucharms.com/u/openstack-charmers

AFAIK, there aren't CS: published "*-on-lxd" variants, as those are typically dev bundles.

[adam-stokes]

Will be working to implement these on this branch: https://github.com/conjure-up/spells/tree/openstack-refactor

One thing I may do is document a process to generate the openstack spells from a few template files to help keep things in sync without to much overhead with repeating steps etc.