Open Stack

Thanks for the info Mark.

A dumb question ... can’t seem to find the answer in ironic documentation ...

·         I understand how the interface over which the bare metal instance network boots/installs gets configured ...
i.e. thru DHCP response/configuration from the ironic conductor dhcp/boot server

·         but how would other interfaces, get configured on the bare metal server by ironic ?


Greg.

From: Mark Goddard <mark at stackhpc.com>
Reply-To: "openstack-dev at lists.openstack.org" <openstack-dev at lists.openstack.org>
Date: Friday, July 28, 2017 at 5:08 AM
To: "openstack-dev at lists.openstack.org" <openstack-dev at 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 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. This feature[3] will be added in the Pike release, at which point it will be possible to create bare metal instances with multiple ports.

[1] https://github.com/openstack/magnum/tree/master/magnum/drivers/k8s_fedora_atomic_v1/templates
[2] https://github.com/openstack/magnum/tree/master/magnum/drivers/k8s_coreos_v1/templates
[3] https://bugs.launchpad.net/ironic/+bug/1666009

Mark

On 17 July 2017 at 14:27, Waines, Greg <Greg.Waines at windriver.com<mailto:Greg.Waines at windriver.com>> wrote:
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 public Docker Hub over that interface ?
- public communications for containers over that interface ?

Greg.

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe<http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170728/634abcc0/attachment.html>