> From: Jim Rollenhagen [mailto:[email protected]] > On Thu, May 12, 2016 at 06:48:02AM -0400, Sean Dague wrote: > > Let me make sure I understand the crux of the issue: services may need > > to create additional custom networking in order for the rest of the > > resource flow to work correctly. Ironic definitely needs this because > > it's building up an interesting simulated network here for it's guests > > to live on. > > > > That feels like we need a new pre_create (or early_create) phase that > > ironic could hook into to do that same network create. I think the only > > question in my mind is whether neutrons network create here should > move > > to early_create as well. > > This would work well, if we moved neutron's net-create to here, > because... > > > Does ironic's ovs setup need to happen after the neutron create phase > > here, or does it just need to happen before nova? > > Yes, the network needs to already exist when we do this. > > > Does ironic need to overwrite the $net_id that gets passed to Nova later? > > Nope, it's the same ID. We just get the OVS tap device for that network > and muck with it a bit. Then we set the shared property of the network: > > neutron net-update $ironic_net_id --shared true > > FWIW, to get the tap device, we do need to create a port on the network > (which we later delete), but I don't think that has any effect on what > you describe above.
As a note, a patch to Grenade has been posted to add an 'early_create' phase: https://review.openstack.org/315501 __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
