Auto-aliases for OpenStack base snaps

[coreycb]

Hello,

The OpenStack base snaps (keystone, glance, neutron, nova, and nova-hypervisor) currently have the following aliases defined in their snapcraft.yaml:

keystone
app:manage - keystone-manage

glance
app:manage - glance-manage

neutron
app:manage - neutron-db-manage

nova
app:manage - nova-manage

nova-hypervisor
app:neutron-ovs-cleanup - neutron-ovs-cleanup
app:neutron-netns-cleanup - neutron-netns-cleanup

The source for these snaps is located at:

openstack/snap-keystone

openstack/snap-glance

openstack/snap-neutron

openstack/snap-nova

openstack/snap-nova-hypervisor

Can these aliases be defined as auto-aliases?

Thanks,
Corey

[jdstrand]

All of these make sense for the snaps in question and are properly namespaced to not conflict with anything outside of OpenStack snaps.

I was curious why the nova-hypervisor snap has aliases for commands that look like they belong in the neutron snap. Can you comment?

[coreycb]

Thanks for taking a look. Neutron support is split across 2 snaps in this architecture, similar to the architecture described here: https://docs.openstack.org/ocata/networking-guide/deploy-ovs-provider.html. The neutron snap itself provides controller services (api and database), while the nova-hypervisor snap includes neutron services that provide networking for instances.

[jdstrand]

Thanks @coreycb.

+1 for auto-aliases

[niemeyer]

Given @jdstrand’s comments above, +1 as well.

[jdstrand]

2 votes for
0 votes against
0 votes abstained

Requests granted and these are now live.