There is a bit of a wish list of things people want in metadata for Ocata
at https://etherpad.openstack.org/p/ocata-nova-metadata-wishlist -- it
might be worth adding your requirements and a link to your spec there?
Michael
On Sat, Oct 8, 2016 at 5:04 AM, Bence Romsics
Jay, let me correct myself. After a round of discussion with Armando
I'm no longer sure exactly what nova changes would be needed. The
discussion went into a direction where we started to question which
part of the change should fall into neutron and which part into nova.
I think joint
Hi,
Armando: Replied in the RFE comments. Let's continue there.
Jay: Yes, plus the corresponding changes in the API validator.
Practically this: https://review.openstack.org/383801
Cheers,
Bence
On Fri, Oct 7, 2016 at 5:30 PM, Jay Pipes wrote:
> On 10/07/2016 09:43 AM,
On 10/07/2016 09:43 AM, Bence Romsics wrote:
Hi,
To follow up on the complications of bringing up trunk subports [1] I
have written up a small proposal for a tiny new feature affecting
neutron and nova. That is how to expose trunk details over metadata
API. To avoid big process overhead I have
On 7 October 2016 at 06:43, Bence Romsics wrote:
> Hi,
>
> To follow up on the complications of bringing up trunk subports [1] I
> have written up a small proposal for a tiny new feature affecting
> neutron and nova. That is how to expose trunk details over metadata
>
Hi,
To follow up on the complications of bringing up trunk subports [1] I
have written up a small proposal for a tiny new feature affecting
neutron and nova. That is how to expose trunk details over metadata
API. To avoid big process overhead I have opened a newton rfe ticket
[2], plus a nova