[Yahoo-eng-team] [Bug 1587253] [NEW] Make logic network mtu to be Configurable
Public bug reported: In some scenes， Traffics of VMs belong to different logic network will pass through different physic network domains with various MTU values. like blow: ------ --- | VM1 || VM2 | | VM3 | ------ --- | || | || | || ------ --- | tenant1 || tenant2 | | tenant3 | | network || network | | network | ------ --- | || | || | || --- | | | proivder network | | mtu=9000| --- | || | || | || ------ --- | Physic || Physic | | physic | | network1|| network2| | network3| | mtu=1500|| mtu=1200| | mtu=9000| ------ --- tenant1 network pass through physic network1 tenant2 network pass through physic network2 tenant3 network pass through physic network3 So, I suggest to make the logic network MTU to be configurable to solve the problem. ** Affects: neutron Importance: Undecided Status: New ** Description changed: In some scenes， Traffics of VMs belong to different logic network will pass through different physic network domains with various MTU values. like blow: - ------ --- - | VM1 || VM2 | | VM3 | - ------ --- -| || -| || -| || - ------ --- - | tenant1 || tenant2 | | tenant3 | - | network || network | | network | - ------ --- -| || -| || -| || - --- - | | - | proivder network | - | mtu=9000| - --- -| || -| || -| || - ------ --- - | Physic || Physic | | physic | - | network1|| network2| | network3| - | mtu=1500|| mtu=1200| | mtu=9000| - ------ --- + ------ --- + | VM1 || VM2 | | VM3 | + ------ --- + | || + | || + | || + ------ --- + | tenant1 || tenant2 | | tenant3 | + | network || network | | network | + ------ --- + | || + | || + | || + --- + | | + | proivder network | + | mtu=9000| + ---
[Yahoo-eng-team] [Bug 1593039] [NEW] a networking-sfc document error
Public bug reported:
http://docs.openstack.org/developer/networking-sfc/api.html#problem-description
In this document:
In order to create a chain, the user needs to have the actual port objects. The
work flow would typically be:
1.create the ports
2.create the chain
3.boot the vm’s passing the ports as nic’s parameters
The sequence of b) and c) can be switched.
I think "The sequence of b) and c) can be switched." change to "The
sequence of 2) and 3) can be switched." will be better.
** Affects: neutron
Importance: Undecided
Assignee: JianGang Weng (weng-jiangang)
Status: New
** Changed in: neutron
Assignee: (unassigned) => JianGang Weng (weng-jiangang)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1593039
Title:
a networking-sfc document error
Status in neutron:
New
Bug description:
http://docs.openstack.org/developer/networking-sfc/api.html#problem-description
In this document:
In order to create a chain, the user needs to have the actual port objects.
The work flow would typically be:
1.create the ports
2.create the chain
3.boot the vm’s passing the ports as nic’s parameters
The sequence of b) and c) can be switched.
I think "The sequence of b) and c) can be switched." change to "The
sequence of 2) and 3) can be switched." will be better.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1593039/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1593039] Re: a networking-sfc document error
https://review.openstack.org/#/c/330472/ ** Changed in: neutron Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1593039 Title: a networking-sfc document error Status in neutron: Fix Released Bug description: http://docs.openstack.org/developer/networking-sfc/api.html#problem-description In this document: In order to create a chain, the user needs to have the actual port objects. The work flow would typically be: 1.create the ports 2.create the chain 3.boot the vm’s passing the ports as nic’s parameters The sequence of b) and c) can be switched. I think "The sequence of b) and c) can be switched." change to "The sequence of 2) and 3) can be switched." will be better. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1593039/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1597219] [NEW] default value display error in rbac-networks.rst
Public bug reported:
In the below document:
https://github.com/openstack/neutron-specs/blob/master/specs/liberty/rbac-networks.rst
In the Table of The Section "REST API Impact", the default value of the
'target_tenant' should be '*', but the displayed value is a black dot
'●'.
** Affects: neutron
Importance: Undecided
Assignee: JianGang Weng (weng-jiangang)
Status: New
** Changed in: neutron
Assignee: (unassigned) => JianGang Weng (weng-jiangang)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1597219
Title:
default value display error in rbac-networks.rst
Status in neutron:
New
Bug description:
In the below document:
https://github.com/openstack/neutron-specs/blob/master/specs/liberty/rbac-networks.rst
In the Table of The Section "REST API Impact", the default value of
the 'target_tenant' should be '*', but the displayed value is a black
dot '●'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1597219/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1597233] [NEW] rbac-create should return an duplicated error when use same 'object_id', 'object_type' and 'target_tenant'
Public bug reported:
RBAC entry should be unique by combination of 'object_id','object_type' and
'target_tenant'.
But in fact, if we only change the 'action' value, we can get another entry
with same 'object_id','object_type' and 'target_tenant'.
the process is:
[root@localhost devstack]# neutron rbac-create
a539e28b-5e6c-4436-b44f-e1f966b6a6a4 --type network --target_tenant tenant_id
--action access_as_shared
Created a new rbac_policy:
+---+--+
| Field | Value|
+---+--+
| action| access_as_shared |
| id| 0897f09b-1799-416e-9b5d-99d0e153a1b1 |
| object_id | a539e28b-5e6c-4436-b44f-e1f966b6a6a4 |
| object_type | network |
| target_tenant | tenant_id|
| tenant_id | aced7a29bb134dec82307a880d1cc542 |
+---+--+
[root@localhost devstack]# neutron rbac-create
a539e28b-5e6c-4436-b44f-e1f966b6a6a4 --type network --target_tenant tenant_id
--action access_as_external
Created a new rbac_policy:
+---+--+
| Field | Value|
+---+--+
| action| access_as_external |
| id| 2c12609e-7878-4161-b533-17b6413bcf0b |
| object_id | a539e28b-5e6c-4436-b44f-e1f966b6a6a4 |
| object_type | network |
| target_tenant | tenant_id|
| tenant_id | aced7a29bb134dec82307a880d1cc542 |
+---+--+
[root@localhost devstack]#
** Affects: neutron
Importance: Undecided
Assignee: JianGang Weng (weng-jiangang)
Status: New
** Changed in: neutron
Assignee: (unassigned) => JianGang Weng (weng-jiangang)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1597233
Title:
rbac-create should return an duplicated error when use same
'object_id','object_type' and 'target_tenant'
Status in neutron:
New
Bug description:
RBAC entry should be unique by combination of 'object_id','object_type' and
'target_tenant'.
But in fact, if we only change the 'action' value, we can get another entry
with same 'object_id','object_type' and 'target_tenant'.
the process is:
[root@localhost devstack]# neutron rbac-create
a539e28b-5e6c-4436-b44f-e1f966b6a6a4 --type network --target_tenant tenant_id
--action access_as_shared
Created a new rbac_policy:
+---+--+
| Field | Value|
+---+--+
| action| access_as_shared |
| id| 0897f09b-1799-416e-9b5d-99d0e153a1b1 |
| object_id | a539e28b-5e6c-4436-b44f-e1f966b6a6a4 |
| object_type | network |
| target_tenant | tenant_id|
| tenant_id | aced7a29bb134dec82307a880d1cc542 |
+---+--+
[root@localhost devstack]# neutron rbac-create
a539e28b-5e6c-4436-b44f-e1f966b6a6a4 --type network --target_tenant tenant_id
--action access_as_external
Created a new rbac_policy:
+---+--+
| Field | Value|
+---+--+
| action| access_as_external |
| id| 2c12609e-7878-4161-b533-17b6413bcf0b |
| object_id | a539e28b-5e6c-4436-b44f-e1f966b6a6a4 |
| object_type | network |
| target_tenant | tenant_id|
| tenant_id | aced7a29bb134dec82307a880d1cc542 |
+---+--+
[root@localhost devstack]#
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1597233/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1550171] [NEW] When an error status VM was deleted which a port belong to, The port can not be assigned to other VM again
Public bug reported: 1. When you create an VM with a given logic port, for some problem(such as all of the neutron agents is offline), the instance fall to the error status. 2. Resolve the problems, and delete the error VM Instance. 3. Create an new VM with the old port, then you will find the port can't be assigned Detail Operation process: http://paste.openstack.org/show/488310/ ** Affects: neutron Importance: Undecided Assignee: JianGang Weng (weng-jiangang) Status: In Progress ** Changed in: neutron Assignee: (unassigned) => JianGang Weng (weng-jiangang) ** Changed in: neutron Status: New => In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1550171 Title: When an error status VM was deleted which a port belong to, The port can not be assigned to other VM again Status in neutron: In Progress Bug description: 1. When you create an VM with a given logic port, for some problem(such as all of the neutron agents is offline), the instance fall to the error status. 2. Resolve the problems, and delete the error VM Instance. 3. Create an new VM with the old port, then you will find the port can't be assigned Detail Operation process: http://paste.openstack.org/show/488310/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1550171/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1550171] Re: When an error status VM was deleted which a port belong to, The port can not be assigned to other VM again
** Changed in: neutron Status: In Progress => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1550171 Title: When an error status VM was deleted which a port belong to, The port can not be assigned to other VM again Status in neutron: Invalid Bug description: 1. When you create an VM with a given logic port, for some problem(such as all of the neutron agents is offline), the instance fall to the error status. 2. Resolve the problems, and delete the error VM Instance. 3. Create an new VM with the old port, then you will find the port can't be assigned Detail Operation process: http://paste.openstack.org/show/488310/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1550171/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1550201] [NEW] When an error status VM was deleted which a port belong to, The port can not be assigned to other VM again
Public bug reported: 1. When you create an VM with a given logic port, for some problem(such as all of the neutron agents is offline), the instance fall to the error status. 2. Resolve the problems, and delete the error VM Instance. 3. Create an new VM with the old port, then you will find the port can't be assigned Detail Operation process: http://paste.openstack.org/show/488310/ ** Affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1550201 Title: When an error status VM was deleted which a port belong to, The port can not be assigned to other VM again Status in OpenStack Compute (nova): New Bug description: 1. When you create an VM with a given logic port, for some problem(such as all of the neutron agents is offline), the instance fall to the error status. 2. Resolve the problems, and delete the error VM Instance. 3. Create an new VM with the old port, then you will find the port can't be assigned Detail Operation process: http://paste.openstack.org/show/488310/ To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1550201/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
