[NEUTRON-100] provider-attributes appear as top level resource under neutron container Created: 30/Dec/15  Updated: 18/Aug/16  Resolved: 18/Aug/16

Status: Resolved
Project: neutron
Component/s: General
Affects Version/s: master
Fix Version/s: None

Type: Bug
Reporter: yong sheng gong Assignee: yong sheng gong
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

External issue ID: 4848

 Description   

https://github.com/opendaylight/neutron/blob/master/model/src/main/yang/neutron.yang#L43

top container should not use provider-attributes since they are not top level neutron resources

 Comments   
Comment by Isaku Yamahata [ 30/Dec/15 ]

Thanks for reporting this.
Looking at neutron api definition(http://git.openstack.org/cgit/openstack/neutron/tree/neutron/extensions/providernet.py#n31)

neutron-provider-ext.yang is also broken?
Can you please address it too?

Comment by Isaku Yamahata [ 30/Dec/15 ]

https://git.opendaylight.org/gerrit/#/c/31946/

Comment by yong sheng gong [ 30/Dec/15 ]

(In reply to Isaku Yamahata from comment #1)
> Thanks for reporting this.
> Looking at neutron api
> definition(http://git.openstack.org/cgit/openstack/neutron/tree/neutron/
> extensions/providernet.py#n31)
>
> neutron-provider-ext.yang is also broken?
> Can you please address it too?

let me have a look.

Comment by yong sheng gong [ 30/Dec/15 ]

Neutron network resource has indeed single provider or multiple providers under segments:
if it is the single one, it has no index, if it is multiple providers under segments, the API does not have index for each segment, but the implementation has.

Comment by Isaku Yamahata [ 30/Dec/15 ]

As talked on IRC, neutron has also multiprovidernet which allows user to specify multiple segment-ids.

I scratch it.

Generated at Wed Feb 07 20:25:34 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.