Open Stack

On Mon, 2019-10-07 at 17:28 -0500, Eric Fried wrote:
> > Miguel isn't talking about cycle wide goals. There are some proposed
> > process changes for nova in Ussuri [1] along with constraining the
> > amount of feature work approved for the release. I think Miguel is just
> > asking that routed networks support is included in that bucket and I'm
> > sure the answer is, like for anything, "it depends".
> 
> Agreed. What hasn't changed is that to get to the table it will need a
> blueprint [1] (which I don't see yet [2]) and spec [3] (likewise [4]).
for this specific effort while it would not be a community wide goal this effort
might benefit form a pop-up team of nova, placement and neutron developers to Shepard it along.
i have to admit while we discussed this at some length at the PTG i did not follow
the neutron development to see if they had got to the point of modelling subnets/segments
as placement aggregates and sharing resource providers of ips. we have definitely made progress on the
nova side thanks to gibi on move operations for ports with resource requests.

having a fourm to bring the 3 project together may help finally get this over the line.
that said i am not sure what remains to be done on the neutron side and what nova needs to do.
I speculated about the gaps in my previous responce based on the desgin we discussed in the past.
The current WIP patch was uploaded by matt https://review.opendev.org/#/c/656885 so i think he
understands nova process better then most, that said if migule and matt are tied up with things i
can try and help with the paperwork. Matt you have not been active on that patch since may is this
something you have time/intend to work on for Ussuri? im not necessarily signing up to work on this
at this point but it is a feature i think we should add and given i have not finalise what work i
intent to do in U i might be able to help.

@matt one point on your last comment to that patch that does perplex me somewhat was the assertion/implication
configuration of nova host aggreates woudl be required. part of the goal as i understood it was to require
no configuration on the nova side at all. i.e. instead of haveing a config option for a prefilter to update
the request spec by transforming the subnets into placement aggreates we would build on the port requests feature
we used for bandwith based schduling so that neutron can provide a resouce request for an ip and aggreate per port.
we could discuss this in a spec but the reason i bring it up is the current patch looks like it would be problematic
if you have a cloud with multiple network backeds say sriov and calico as its a global config rather then a backend
specific behavior that builds on the generic perport resource requests. anyway that is an implemantion detail/design
choice that we can discuss else where i just wanted to point it out.

> 
> efried
> 
> [1] https://blueprints.launchpad.net/nova/ussuri/+addspec
> [2] https://blueprints.launchpad.net/nova/ussuri
> [3] http://specs.openstack.org/openstack/nova-specs/readme.html
> [4] https://review.opendev.org/#/q/project:openstack/nova-specs+status:open
>