Hello Kevin.
There is a similar Neutron blueprint [1], originally meant for Havana but
now aiming for Juno.
I would be happy to join efforts with you regarding our blueprints.
See also: [2].
[1] https://blueprints.launchpad.net/neutron/+spec/ml2-external-port
[2]
Hi Kevin!
I had a few conversations with folks at the summit regarding this. Broadly
speaking, yes -- this integration would be very helpful for both discovery
and network/tenant isolation at the bare metal layer.
I've left a few comments inline
On Mon, May 19, 2014 at 3:52 PM, Kevin
Hi Devananda,
Most of this should work fine. The only problem part is handling the
servers that are first being booted and have never been connected to
Ironic. Neutron doesn't have control over the default network that all
un-provisioned switch ports should be a member of. Even if we added
Hi Igor,
Thanks for the pointers. Have you had a chance to look at the details of
our blueprint? Are there any workflows supported by yours that we forgot?
We would be happy to have you help on the reference implementation for this.
Thanks,
Kevin Benton
On Tue, May 20, 2014 at 3:13 AM, Igor
Hello,
I am working on an extension for neutron to allow external attachment point
information to be stored and used by backend plugins/drivers to place
switch ports into neutron networks[1].
One of the primary use cases is to integrate ironic with neutron. The basic
workflow is that ironic will
