Re: [openstack-dev] [Neutron][Nova] Expose trunk details over metadata API

2016-10-08 Thread Michael Still 
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 
wrote:

> 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 nova-neutron design would be beneficial to avoid a
> ping-pong between the projects. So far the discussion lacks the
> opinions of nova developers. It would be welcome:
> https://bugs.launchpad.net/neutron/+bug/1631371
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Rackspace Australia
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron][Nova] Expose trunk details over metadata API

2016-10-07 Thread 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 nova-neutron design would be beneficial to avoid a
ping-pong between the projects. So far the discussion lacks the
opinions of nova developers. It would be welcome:
https://bugs.launchpad.net/neutron/+bug/1631371

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

Re: [openstack-dev] [Neutron][Nova] Expose trunk details over metadata API

2016-10-07 Thread Bence Romsics 
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, 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 opened a newton rfe ticket
>> [2], plus a nova specless blueprint [3] pointing to it. Please let me
>> know if I should have followed a different process.
>
>
> Hi Ben,
>
> If I'm reading the Neutron RFE bug correctly, the only change you would need
> in Nova is modifying the column type for the instance_metadata.value column
> from VARCHAR(255) to TEXT.
>
> Is that a correct understanding?
>
> Best,
> -jay
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

Re: [openstack-dev] [Neutron][Nova] Expose trunk details over metadata API

2016-10-07 Thread Jay Pipes 

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 opened a newton rfe ticket
[2], plus a nova specless blueprint [3] pointing to it. Please let me
know if I should have followed a different process.


Hi Ben,

If I'm reading the Neutron RFE bug correctly, the only change you would 
need in Nova is modifying the column type for the 
instance_metadata.value column from VARCHAR(255) to TEXT.


Is that a correct understanding?

Best,
-jay

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

Re: [openstack-dev] [Neutron][Nova] Expose trunk details over metadata API

2016-10-07 Thread Armando M. 
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
> API. To avoid big process overhead I have opened a newton rfe ticket
> [2], plus a nova specless blueprint [3] pointing to it. Please let me
> know if I should have followed a different process.
>
>
Replied on [2]. From a Neutron's standpoint, I suspect you already have
what you need.


> Cheers,
> Bence
>
> [1] http://lists.openstack.org/pipermail/openstack-dev/2016-
> September/104848.html
> [2] https://bugs.launchpad.net/neutron/+bug/1631371
> [3] https://blueprints.launchpad.net/nova/+spec/trunk-details-meta
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron][Nova] Expose trunk details over metadata API

2016-10-07 Thread Bence Romsics 
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 specless blueprint [3] pointing to it. Please let me
know if I should have followed a different process.

Cheers,
Bence

[1] 
http://lists.openstack.org/pipermail/openstack-dev/2016-September/104848.html
[2] https://bugs.launchpad.net/neutron/+bug/1631371
[3] https://blueprints.launchpad.net/nova/+spec/trunk-details-meta

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