| 2015-05-29 22:51:31 |
Ed Warnicke |
bug |
|
|
added bug |
| 2015-05-29 22:55:00 |
Ed Warnicke |
description |
*What is being requested*
This request is to add an attribute 'labels' to the neutron 'port' object. The type of 'labels' is a list of strings.
*Why is it being requested*
There are many use cases in which you wish to provide hint-by-reference to downstream providers of neutron services (like controllers) for which you would like to allow the user to provide hint-by-reference about the nature of the port and the service it should receive.
In the parlance of the Neutron API Documentation:
****************************************************************************************************************
| Parameter | Style | Type | Description |
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| labels | plain | xsd:list | A list of opaque strings to be interpreted as hints-by-reference by the neutron provider |
****************************************************************************************************************
Examples:
1) Indicate the Network Policy that should be applied to the port. Most network policy systems resolve policy based upon the
'Endpoint Group(s)' (abbreviated EPGs) and Endpoint (think port) (abbreviated EP) is placed in. 'labels' could be used to indicate EPG membership for a port. For example:
{
"port": {
"labels": [ "epg:blue", "epg:green" ],
...
}
}
2) Indicate the type of Virtual Network Function (VNF) of the VM being deployed on the port. This would be important for a controller rendering Service Function Chains (SFCs) to know so that it knew it had additional VNFs of that type to use in the SFCs it was constructing. For example:
{
"port": {
"labels": [ "vnf-type:firewall-3" ],
...
}
}
*Who needs it*
This is needed to assist the OpenDaylight Controller in being able to better provide the Policy and SFC services. However, this mechanism is agnostic as to the underlying controller, and also can be used for a variety of other useful purposes. Anywhere that it would be useful to pass on hints-by-reference to downstream providers could take advantage of it. |
*What is being requested*
This request is to add an attribute 'labels' to the neutron 'port' object. The type of 'labels' is a list of strings.
*Why is it being requested*
There are many use cases in which you wish to provide hint-by-reference to downstream providers of neutron services (like controllers) for which you would like to allow the user to provide hint-by-reference about the nature of the port and the service it should receive.
In the parlance of the Neutron API Documentation:
**************************************************************************
| Parameter | Style | Type | Description | |
--------------------------------------------------------------------------
| labels | plain | xsd:list | A list of opaque strings to be |
| | | | interpreted as hints-by-reference by |
| | | | the neutron provider |
**************************************************************************
*Examples*
1) Indicate the Network Policy that should be applied to the port. Most network policy systems resolve policy based upon the
'Endpoint Group(s)' (abbreviated EPGs) and Endpoint (think port) (abbreviated EP) is placed in. 'labels' could be used to indicate EPG membership for a port. For example:
{
"port": {
"labels": [ "epg:blue", "epg:green" ],
...
}
}
2) Indicate the type of Virtual Network Function (VNF) of the VM being deployed on the port. This would be important for a controller rendering Service Function Chains (SFCs) to know so that it knew it had additional VNFs of that type to use in the SFCs it was constructing. For example:
{
"port": {
"labels": [ "vnf-type:firewall-3" ],
...
}
}
*Who needs it*
This is needed to assist the OpenDaylight Controller in being able to better provide the Policy and SFC services. However, this mechanism is agnostic as to the underlying controller, and also can be used for a variety of other useful purposes. Anywhere that it would be useful to pass on hints-by-reference to downstream providers could take advantage of it. |
|
| 2015-05-29 22:56:15 |
Ed Warnicke |
description |
*What is being requested*
This request is to add an attribute 'labels' to the neutron 'port' object. The type of 'labels' is a list of strings.
*Why is it being requested*
There are many use cases in which you wish to provide hint-by-reference to downstream providers of neutron services (like controllers) for which you would like to allow the user to provide hint-by-reference about the nature of the port and the service it should receive.
In the parlance of the Neutron API Documentation:
**************************************************************************
| Parameter | Style | Type | Description | |
--------------------------------------------------------------------------
| labels | plain | xsd:list | A list of opaque strings to be |
| | | | interpreted as hints-by-reference by |
| | | | the neutron provider |
**************************************************************************
*Examples*
1) Indicate the Network Policy that should be applied to the port. Most network policy systems resolve policy based upon the
'Endpoint Group(s)' (abbreviated EPGs) and Endpoint (think port) (abbreviated EP) is placed in. 'labels' could be used to indicate EPG membership for a port. For example:
{
"port": {
"labels": [ "epg:blue", "epg:green" ],
...
}
}
2) Indicate the type of Virtual Network Function (VNF) of the VM being deployed on the port. This would be important for a controller rendering Service Function Chains (SFCs) to know so that it knew it had additional VNFs of that type to use in the SFCs it was constructing. For example:
{
"port": {
"labels": [ "vnf-type:firewall-3" ],
...
}
}
*Who needs it*
This is needed to assist the OpenDaylight Controller in being able to better provide the Policy and SFC services. However, this mechanism is agnostic as to the underlying controller, and also can be used for a variety of other useful purposes. Anywhere that it would be useful to pass on hints-by-reference to downstream providers could take advantage of it. |
*What is being requested*
This request is to add an attribute 'labels' to the neutron 'port' object. The type of 'labels' is a list of strings.
*Why is it being requested*
There are many use cases in which you wish to provide hint-by-reference to downstream providers of neutron services (like controllers) for which you would like to allow the user to provide hint-by-reference about the nature of the port and the service it should receive.
In the parlance of the Neutron API Documentation:
Object: ports
Parameter: labels
Style: plain
Type: xsd:list
Description: A list of opaque strings to be interpreted as
hints-by-reference by the neutron provider
*Examples*
1) Indicate the Network Policy that should be applied to the port. Most network policy systems resolve policy based upon the
'Endpoint Group(s)' (abbreviated EPGs) and Endpoint (think port) (abbreviated EP) is placed in. 'labels' could be used to indicate EPG membership for a port. For example:
{
"port": {
"labels": [ "epg:blue", "epg:green" ],
...
}
}
2) Indicate the type of Virtual Network Function (VNF) of the VM being deployed on the port. This would be important for a controller rendering Service Function Chains (SFCs) to know so that it knew it had additional VNFs of that type to use in the SFCs it was constructing. For example:
{
"port": {
"labels": [ "vnf-type:firewall-3" ],
...
}
}
*Who needs it*
This is needed to assist the OpenDaylight Controller in being able to better provide the Policy and SFC services. However, this mechanism is agnostic as to the underlying controller, and also can be used for a variety of other useful purposes. Anywhere that it would be useful to pass on hints-by-reference to downstream providers could take advantage of it. |
|
| 2015-05-29 23:05:08 |
Armando Migliaccio |
neutron: status |
New |
Confirmed |
|
| 2015-06-02 00:27:59 |
Armando Migliaccio |
tags |
labels |
rfe |
|
| 2015-06-02 01:39:41 |
Armando Migliaccio |
neutron: status |
Confirmed |
Triaged |
|
| 2015-06-03 15:12:43 |
Kyle Mestery |
bug |
|
|
added subscriber Kyle Mestery |
| 2015-06-03 16:04:28 |
Kyle Mestery |
neutron: status |
Triaged |
Confirmed |
|
| 2015-06-03 16:37:26 |
Armando Migliaccio |
neutron: status |
Confirmed |
Triaged |
|
| 2015-06-04 17:42:53 |
John Joyce |
bug |
|
|
added subscriber John Joyce |
| 2015-06-14 13:53:42 |
yong sheng gong |
bug |
|
|
added subscriber yong sheng gong |
| 2015-06-15 17:08:21 |
uri elzur |
bug |
|
|
added subscriber uri elzur |
| 2015-06-19 20:24:16 |
cathy Hong Zhang |
bug |
|
|
added subscriber cathy Hong Zhang |
| 2015-06-23 10:14:19 |
Adrian Hoban |
bug |
|
|
added subscriber Adrian Hoban |
| 2015-06-23 17:45:28 |
Peter Balland |
bug |
|
|
added subscriber Peter Balland |
| 2015-06-25 12:19:24 |
Nell Jerram |
bug |
|
|
added subscriber Neil Jerram |
| 2015-06-28 15:23:56 |
Yapeng Wu |
bug |
|
|
added subscriber Yapeng Wu |
| 2015-06-29 03:22:09 |
shihanzhang |
bug |
|
|
added subscriber shihanzhang |
| 2015-07-02 16:29:15 |
sean mooney |
bug |
|
|
added subscriber sean mooney |
| 2015-07-17 16:05:26 |
Kyle Mestery |
neutron: status |
Triaged |
Won't Fix |
|
