Creating VM directly on external network.
Sean Mooney
smooney at redhat.com
Tue May 24 12:35:57 UTC 2022
On Tue, 2022-05-24 at 12:09 +0000, Eugen Block wrote:
> In addition to Seans comment I wanted to point out that you might need
> config-drive to ensure the VMs get their metadata since the neutron
> metadata service won't work on the external network. At least that's
> how we spin up instances in our external networks.
> The cli option would be
> 'openstack server create --image ... --config-drive true <VM_NAME>'
yes config drive is one way the ohter way is to configure neutron to server
the metadta via the dhcp namespace.
>
>
> Zitat von Sean Mooney <smooney at redhat.com>:
>
> > On Tue, 2022-05-24 at 10:50 +0000, Russell Stather wrote:
> > > Hi
> > >
> > > I have a charm based OpenStack setup. The network topology is as below.
> > >
> > > Creating vms on the internal network and adding floating ips works
> > > as expected.
> > >
> > > Adding vms on directly on to the ext_net does not. openstack allows
> > > me to do it, but I get host is unreachable when trying to connect.
> > > Is there some configuration I have missed?
> >
> > am off the top of my head have you ensured that dhcp is enabled on
> > the external network.
> > floating ips are implemtend using neutron routers so you cannot used
> > them with vms on an external network.
> > other then that you just need to make sure that the external network
> > subnet is routeable on your phsyical netowrk
> > have you tried connecting to the vm form a vm in your openstack
> > cloud to rule out datacenter routing issues.
> >
> > >
> > > Thanks
> > >
> > > [cid:3699cab3-ea6a-45eb-91c3-65e91056fd71]
>
>
>
>
More information about the openstack-discuss
mailing list