Any thoughts on this ?
Greg.
From: Greg Waines <greg.wai...@windriver.com>
Reply-To: "openstack-dev@lists.openstack.org"
<openstack-dev@lists.openstack.org>
Date: Friday, January 19, 2018 at 3:10 PM
To: "openstack-dev@lists.openstack.org" <openstack-dev@lists.openstack.org>
Cc: "Nasir, Shoaib" <shoaib.na...@windriver.com>
Subject: [openstack-dev] [magnum] [ironic] Why does magnum create instances
with ports using 'fixed-ips' ?
Hey there,
We have just recently integrated MAGNUM into our OpenStack Distribution.
QUESTION:
When MAGNUM is creating the ‘instances’ for the COE master and minion nodes,
WHY does it create the instances with ports using ‘fixed-ips’ ?
- instead of just letting the instance’s port dhcp for its
ip-address ?
I am asking this question because:
· we have also integrated IRONIC into our OpenStack Distribution, and
o currently support the simple (somewhat non-multi-tenant) networking approach
i.e.
§ ironic-provisioning-net TENANT NETWORK,
used to network boot the IRONIC Instances,
is owned by ADMIN but shared so TENANTS can create IRONIC instances,
§ AND,
we do NOT support the functionality to have IRONIC update the
adjacent switch configuration in order to move the IRONIC instance
on to a different (TENANT-owned) TENANT NETWORK after the instance
is created.
o so it is SORT OF multi-tenant in the sense that any TENANT can create an
IRONIC instance,
HOWEVER the IRONIC instances of all tenants are all on the same TENANT NETWORK
· In this environment,
When we use MAGNUM to create IRONIC COE Nodes
o it ONLY works if the ADMIN creates the MAGNUM Cluster,
o it does NOT work if a TENANT creates the MAGNUM Cluster,
§ because a TENANT can NOT create an instance port with ‘fixed-ips’ on a
TENANT NETWORK
that is not owned by himself.
appreciate any info on this,
Greg.
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
