Networks for different availability zones in Horizon

hai wu at
Sun Dec 19 02:44:58 UTC 2021

Not using vxlan, so there's no network span across availability zones.
It seems there's no built-in way to configure Horizon to do so. The
problem with this is that sometimes if user picks the wrong network
and availability zone combo, the VM will end up in the wrong state.
This is why it would be ideal to only show available networks for the
availability zone that the user already picked.

I am wondering how to modify the horizon source code to achieve this,
but I am not familiar with Angular, and the workflow code is pretty
complex for newbie ..

On Sat, Dec 18, 2021 at 6:31 PM Sean Mooney <smooney at> wrote:
> On Sat, 2021-12-18 at 13:45 -0600, hai wu wrote:
> > In Horizon "Launch Instance" workflow, in its 4th step of selecting
> > networks for the new instance, it would always show all the available
> > networks from all availability zones, regardless of which
> > "Availability Zone" got picked in 1st step of "Details".
> >
> > I tried to update some DB field for availability zone hint for the
> > relevant network, and that did not help.
> >
> > Any way to ensure in Horizon "Launch Instance" GUI workflow, after a
> > user picking one availability zone in step 1, it would only show the
> > related networks in that availability zone as available networks in
> > step 4?
> networks do not have any affinity to Avaiablity Zones.
> there is no mapping between neutron physnets and nova host aggreates which are use to
> model aviablityitz zones.
> when using tunneled networks like vxlan it is assuems that all hosts in a cloud acorss all avaiablity zones can access
> any tenant vxlan network. the same is also ture of vlan or flat network the only excption being that htey have physnet
> assocaited with them. physnets may not be aviable on all host but there is corralation between phsynets and aviaablity zones.
> unless you manually algin them.
> >

More information about the openstack-discuss mailing list