Re: [openstack-dev] [magnum] Interface configuration and assumptions for masters/minions launched by magnum

2017-08-01 Thread Mark Goddard
nstack-dev@lists. > openstack.org> > *Date: *Friday, July 28, 2017 at 5:08 AM > *To: *"openstack-dev@lists.openstack.org" <openstack-dev@lists. > openstack.org> > *Subject: *Re: [openstack-dev] [magnum] Interface configuration and > assumptions for masters/minions launch

Re: [openstack-dev] [magnum] Interface configuration and assumptions for masters/minions launched by magnum

2017-07-28 Thread Waines, Greg
AM To: "openstack-dev@lists.openstack.org" <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [magnum] Interface configuration and assumptions for masters/minions launched by magnum Hi Greg, Magnum clusters currently support using only a single network for all comm

Re: [openstack-dev] [magnum] Interface configuration and assumptions for masters/minions launched by magnum

2017-07-28 Thread Mark Goddard
Hi Greg, Magnum clusters currently support using only a single network for all communication. See the heat templates[1][2] in the drivers. . On the bare metal side, currently ironic effectively supports using only a single network interface due to a lack of support for physical network awareness.

[openstack-dev] [magnum] Interface configuration and assumptions for masters/minions launched by magnum

2017-07-17 Thread Waines, Greg
When MAGNUM launches a VM or Ironic instance for a COE master or minion node, with the COE Image, What is the interface configuration and assumptions for these nodes ? e.g. - only a single interface ? - master and minion communication over that interface ? - communication to Docker Registry or