[Yahoo-eng-team] [Bug 1472244] [NEW] Remove dependency on Tempest from neutron

2015-07-07 Thread Dmitry Ratushnyy
Public bug reported:

As everyone knows, all neutron API tests copied from tempest tree into
neutron tree, And this tests already running on neutron gates.

But for current moment running this tests has some external dependencies
( TEMPEST_CONFIG_DIR and tempest.conf file itself).

Having dependency for API tests on third-party component is
unacceptable.

This bug is about removing dependency on tempest from neutron tests
completely by changing how tests are checking neutron configuration.

CONF object, which is used by tests during skip checks and other methods
should be refactor not rely on tempest.conf

Removing this dependency will simplify running of neutron tests

** 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/1472244

Title:
  Remove dependency on Tempest from neutron

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  As everyone knows, all neutron API tests copied from tempest tree into
  neutron tree, And this tests already running on neutron gates.

  But for current moment running this tests has some external
  dependencies ( TEMPEST_CONFIG_DIR and tempest.conf file itself).

  Having dependency for API tests on third-party component is
  unacceptable.

  This bug is about removing dependency on tempest from neutron tests
  completely by changing how tests are checking neutron configuration.

  CONF object, which is used by tests during skip checks and other
  methods should be refactor not rely on tempest.conf

  Removing this dependency will simplify running of neutron tests

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1472244/+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 1459343] [NEW] Port security enabled=True is not respected

2015-05-27 Thread Dmitry Ratushnyy
Public bug reported:

It is possible to send traffic through port with
port_security_enabled=True.

Steps to reproduce.

1) Create three VMS on one network:
Guest os:
 ubuntu-14.04

destination VM  to ping (10.100.0.3)
router VM to send traffic through (10.100.0.2)
source VM that will ping destination VM(10.100.0.1)

2) On source VM add route to destination via router ( sudo ip route add 
10.100.0.3 via 10.100.0.2)
3) On router VM  set net.ipv4.ip_forward = 1 (sudo sysctl  
net.ipv4.ip_forward = 1)
4) On  destination VM add route to 'source' via router ( sudo ip route add 
10.100.0.1 via 10.100.0.2) 
5) Start to ping destination on source VM.  
5.1) Check traffic on all VMs

** Affects: neutron
 Importance: Undecided
 Status: New


** Tags: port-security

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1459343

Title:
  Port security enabled=True is not respected

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  It is possible to send traffic through port with
  port_security_enabled=True.

  Steps to reproduce.

  1) Create three VMS on one network:
  Guest os:
   ubuntu-14.04

  destination VM  to ping (10.100.0.3)
  router VM to send traffic through (10.100.0.2)
  source VM that will ping destination VM(10.100.0.1)

  2) On source VM add route to destination via router ( sudo ip route add 
10.100.0.3 via 10.100.0.2)
  3) On router VM  set net.ipv4.ip_forward = 1 (sudo sysctl  
net.ipv4.ip_forward = 1)
  4) On  destination VM add route to 'source' via router ( sudo ip route add 
10.100.0.1 via 10.100.0.2) 
  5) Start to ping destination on source VM.  
  5.1) Check traffic on all VMs

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1459343/+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 1446087] [NEW] Impossible to create port with port_security_enabled = False and security_groups=[]

2015-04-20 Thread Dmitry Ratushnyy
Public bug reported:

Creating port with specifying both port_security_enabled=False and
security_groups=[] raises PortSecurityAndIPRequiredForSecurityGroups

Steps to reproduce:
1) Make sure that port security is enabled for ML2 (for DevStack 
https://review.openstack.org/#/c/162063/)

2) create network with neutron net-create
neutron net-create test
Created a new network:
+---+--+
| Field | Value|
+---+--+
| admin_state_up| True |
| id| 61a8a4be-d607-4683-b636-f1ae08bc135e |
| mtu   | 0|
| name  | test |
| port_security_enabled | True |
| provider:network_type | vxlan|
| provider:physical_network |  |
| provider:segmentation_id  | 1003 |
| router:external   | False|
| shared| False|
| status| ACTIVE   |
| subnets   |  |
| tenant_id | bbd1128dfeb141b3b6442d910cb64dfa |
+---+--+


2) Optional (does not affect result) 
neutron subnet-create 61a8a4be-d607-4683-b636-f1ae08bc135e 10.10.0.1/24
3) Try to create port 
neutron port-create 61a8a4be-d607-4683-b636-f1ae08bc135e --no-securty-groups 
--port-security-enabled=False

4) Result: 
Port security must be enabled and port must have an IP address in order to use 
security groups.

Expected result: Port created with port_security_enabled=False and no
security groups attached to port

** 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/1446087

Title:
  Impossible  to create port with port_security_enabled = False and
  security_groups=[]

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  Creating port with specifying both port_security_enabled=False and
  security_groups=[] raises PortSecurityAndIPRequiredForSecurityGroups

  Steps to reproduce:
  1) Make sure that port security is enabled for ML2 (for DevStack 
https://review.openstack.org/#/c/162063/)

  2) create network with neutron net-create
  neutron net-create test
  Created a new network:
  +---+--+
  | Field | Value|
  +---+--+
  | admin_state_up| True |
  | id| 61a8a4be-d607-4683-b636-f1ae08bc135e |
  | mtu   | 0|
  | name  | test |
  | port_security_enabled | True |
  | provider:network_type | vxlan|
  | provider:physical_network |  |
  | provider:segmentation_id  | 1003 |
  | router:external   | False|
  | shared| False|
  | status| ACTIVE   |
  | subnets   |  |
  | tenant_id | bbd1128dfeb141b3b6442d910cb64dfa |
  +---+--+

  
  2) Optional (does not affect result) 
  neutron subnet-create 61a8a4be-d607-4683-b636-f1ae08bc135e 10.10.0.1/24
  3) Try to create port 
  neutron port-create 61a8a4be-d607-4683-b636-f1ae08bc135e --no-securty-groups 
--port-security-enabled=False

  4) Result: 
  Port security must be enabled and port must have an IP address in order to 
use security groups.

  Expected result: Port created with port_security_enabled=False and no
  security groups attached to port

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1446087/+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