ts.IPv4:
raise ext_sg.SecurityGroupEthertypeConflictWithProtocol(
ethertype=rule['ethertype'], protocol=rule['protocol'])
It should check for numbers and names from neutron_lib constants.
** Affects: neutron
Importance: Undecided
Assignee: Trevor McCasland (twm2016)
Public bug reported:
QinQ networks allows service providers to extend it's clients virtual
broadcast domains across their sites, without interfering with each
others VLANs. Where the s_tag will be used to transport the traffic from
the provider to the customer and the c_tag will be used for the
cu
Oh really? I'm a genius! Marking as invalid.
** Changed in: neutron
Status: Incomplete => Invalid
** Tags removed: needs-attention
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/16
This is already fixed in the openstack client. We are no longer
accepting changes for the neutronclient because it's deprecated.
$ openstack security group create test --project NEC
No project with a name or ID of 'NEC' exists.
** Changed in: neutron
Status: New => Invalid
--
You receive
This can easily be seen as a bug if they aren't verbose enough.. I'm
confused on how a log can be hidden. I can see how it can be hard to
find but it's still there.
** Changed in: neutron
Status: New => Incomplete
** Changed in: neutron
Status: Incomplete => Opinion
--
You receive
or you know what.. he mentions.. in the API layer. I could see how this
may be useful for people who just use the curl command.
** Changed in: neutron
Status: New => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to n
Looks like this was fixed by me in trove unknowingly,
https://review.openstack.org/#/q/owner:TM2086+status:merged+i18n+project:openstack/trove
** Changed in: trove
Status: New => Fix Released
** Changed in: trove
Assignee: (unassigned) => Trevor McCasland (twm2016)
** Chan
Public bug reported:
We want to allocate a range of VLANs to a port, this is how we filter
traffic with VNFs. This will work well with the adoption of QinQ
networks.
Currently this is limited to one VLAN per VF (untagged within the
VM)[1].
[1]http://lists.openstack.org/pipermail/openstack/2017-A
Public bug reported:
Allowed address pairs simply pairs IP addresses and mac addresses.
This RFE asks to allow '0.0.0.0/0' to be specified for the ip address or
to make it optional, so that a user can configure ports to filter
traffic with only a mac list.
** Affects: neutron
Importance: Un
Public bug reported:
Currently it is not possible to allow or disallow traffic by packet
type, specifically broadcast, unicast, and multicast types.
By adding fields to security groups we can use multiple backends to
enforce these rules. Whether it be rules enforced by a firewall, TCP
offloading,
Versioned github link from bug description:
https://github.com/openstack/neutron/blob/7bd521e7ce1c4ffe5b65aad12f3a1c1394c55473/neutron/db/l3_hamode_db.py#L578
Adding a case for the scenario described in the bug description will fix
the issue but is it HA if you only have one node? "an HA cluster i
** Changed in: neutron
Assignee: Trevor McCasland (twm2016) => (unassigned)
** Changed in: neutron
Status: In Progress => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchp
Public bug reported:
By integrating DPDK PMD drivers with SR-IOV we can see significant improvement
in NFV workloads. The virtual machines will be attached to hostdev devices
which will allow operators to use more advanced parameters to configure the VF
driver.
The requested changes in vif:
1. Th
13 matches
Mail list logo
