[Yahoo-eng-team] [Bug 1475190] [NEW] Network Profile is not supported in Kilo
Public bug reported: Cisco N1kv ML2 driver does not support network profiles extension in kilo. The network profile support in horizon needs to be removed for stable/kilo. ** Affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1475190 Title: Network Profile is not supported in Kilo Status in OpenStack Dashboard (Horizon): New Bug description: Cisco N1kv ML2 driver does not support network profiles extension in kilo. The network profile support in horizon needs to be removed for stable/kilo. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1475190/+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 1425236] [NEW] Enable/Disable Network Profile support for Cisco N1KV depending on the extension support for 'network_profile' by neutron
Public bug reported: Currently for ML2 plugin, cisco n1kv does not have support for network_profile. Therefore, the network_profile support should be disabled on the openstack dashabord. But port_profile support is still required for Cisco N1KV. A solution for this is to check the 'extension_list' from neutron for 'network_profile' and depending on that, enable/disable network_profile support. ** Affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1425236 Title: Enable/Disable Network Profile support for Cisco N1KV depending on the extension support for 'network_profile' by neutron Status in OpenStack Dashboard (Horizon): New Bug description: Currently for ML2 plugin, cisco n1kv does not have support for network_profile. Therefore, the network_profile support should be disabled on the openstack dashabord. But port_profile support is still required for Cisco N1KV. A solution for this is to check the 'extension_list' from neutron for 'network_profile' and depending on that, enable/disable network_profile support. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1425236/+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 1423453] [NEW] Delete ports when Launching VM fails when plugin is N1K
Public bug reported: When plugin is Cisco N1KV, ports gets created before launching VM instance. But upon failure of launching, the ports are not cleaned up in the except block. ** Affects: horizon Importance: Undecided Assignee: Shiv Prasad Rao (shivrao) Status: New ** Changed in: horizon Assignee: (unassigned) = Shiv Prasad Rao (shivrao) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1423453 Title: Delete ports when Launching VM fails when plugin is N1K Status in OpenStack Dashboard (Horizon): New Bug description: When plugin is Cisco N1KV, ports gets created before launching VM instance. But upon failure of launching, the ports are not cleaned up in the except block. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1423453/+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 1396387] [NEW] cisco n1kv: segment allocation table retrieves same segment id on concurrent requests
Public bug reported: When concurrent requests come from multiple tenants for network creation, neutron allows to create two network segment with same BD (vlan id and vxlan id) Expected behaviour : Should not reuse same bd [root@macc81f66b8f486 latest_os_sanity(openstack_admin)]# neutron net-show 164ff80d-4104-4f8c-a610-9ae32bfcab85 +---+--+ | Field | Value| +---+--+ | admin_state_up| True | | id| 164ff80d-4104-4f8c-a610-9ae32bfcab85 | | n1kv:member_segments | | | n1kv:profile_id | 1b5212d6-ac5b-4a07-9efe-0f97d0a8cae6 | | name | net-t3-p1-s1 | | provider:network_type | vlan | | provider:physical_network | p1 | | provider:segmentation_id | 1412 | | router:external | False| | shared| False| | status| ACTIVE | | subnets | 4ceded0e-54df-43fd-a229-adc8089ed6e1 | | tenant_id | 41c08065e4c247c5b43baff041b20c71 | +---+--+ [root@macc81f66b8f486 latest_os_sanity(openstack_admin)]# neutron net-show 128d1345-f152-4c18-9005-0fd119c263db +---+--+ | Field | Value| +---+--+ | admin_state_up| True | | id| 128d1345-f152-4c18-9005-0fd119c263db | | n1kv:member_segments | | | n1kv:profile_id | 1b5212d6-ac5b-4a07-9efe-0f97d0a8cae6 | | name | net-t2-p1-s1 | | provider:network_type | vlan | | provider:physical_network | p1 | | provider:segmentation_id | 1412 | | router:external | False| | shared| False| | status| ACTIVE | | subnets | 72ee84b5-fb4e-43c0-85a4-dccc002b7ff9 | | tenant_id | d31bcc1cc614426e888f02506c7d6197 | +---+--+ ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1396387 Title: cisco n1kv: segment allocation table retrieves same segment id on concurrent requests Status in OpenStack Neutron (virtual network service): New Bug description: When concurrent requests come from multiple tenants for network creation, neutron allows to create two network segment with same BD (vlan id and vxlan id) Expected behaviour : Should not reuse same bd [root@macc81f66b8f486 latest_os_sanity(openstack_admin)]# neutron net-show 164ff80d-4104-4f8c-a610-9ae32bfcab85 +---+--+ | Field | Value| +---+--+ | admin_state_up| True | | id| 164ff80d-4104-4f8c-a610-9ae32bfcab85 | | n1kv:member_segments | | | n1kv:profile_id | 1b5212d6-ac5b-4a07-9efe-0f97d0a8cae6 | | name | net-t3-p1-s1 | | provider:network_type | vlan | | provider:physical_network | p1 | | provider:segmentation_id | 1412 | | router:external | False| | shared| False| | status| ACTIVE | | subnets | 4ceded0e-54df-43fd-a229-adc8089ed6e1 | | tenant_id | 41c08065e4c247c5b43baff041b20c71 | +---+--+ [root@macc81f66b8f486 latest_os_sanity(openstack_admin)]# neutron net-show 128d1345-f152-4c18-9005-0fd119c263db +---+--+ | Field | Value
