Hi,
As I understand it l2 population is not a requirement but it's strongly
recommended.
https://review.openstack.org/#/c/165311/ validates that OVS agent is
configured with l2_population enabled when DVR is enabled.
Now that DVR supports VLAN do we want to take back this validation ?
Itzik
:
L2pop is a requirement.
With the existing agent-based architecture, L2pop is used to update
the FDB tables on the compute hosts to make east/west traffic possible
whenever a new port is created or existing one is updated.
Cheers,
Armando
On 10 February 2015 at 23:07, Itzik Brown itz
Hi,
I think it's better to ask this question at ask.openstack.org or the
openstack mailing list.
BR,
Itzik
On 12/04/2014 12:26 PM, Akilesh K wrote:
Hi,
I am using neutron-plugin-sriov-agent.
I have configured pci_whitelist in nova.conf
I have configured ml2_conf_sriov.ini.
But when I
Hi,
Seems like you don't have available devices for allocation.
What's the output of:
#echo 'use nova;select hypervisor_hostname,pci_stats from
compute_nodes;' | mysql -u root
Itzik
On 12/02/2014 08:21 AM, Murali B wrote:
Hi
we are trying to bring-up the SRIOV on set-up.
facing the below
Hi,
When building a firewall with a rule to block a specific Traffic - the current
traffic is not blocked.
For example:
Running a Ping to an instance and then building a firewall with a rule to block
ICMP to this instance doesn't have affect while the ping command is still
running.
Exiting
- Original Message -
From: Carl Baldwin c...@ecbaldwin.net
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Monday, October 27, 2014 5:27:57 PM
Subject: Re: [openstack-dev] [Neutron] FWaaS/Security groups Not blocking
ongoing
On 8/30/2014 11:22 PM, Ian Wells wrote:
The problem here is that you've removed the vif_driver option and now
you're preventing the inclusion of named VIF types into the generic
driver, which means that rather than adding a package to an
installation to add support for a VIF driver it's now
On 27/08/2014 17:06, Daniel P. Berrange wrote:
On Tue, Aug 26, 2014 at 05:02:10PM +0300, Itzik Brown wrote:
Hi,
Following the conversation [1]:
My understanding was that the way to use out of the tree vif_driver is to
set vif_driver option in nova.conf
until there is a better way to support
Hi,
Following the conversation [1]:
My understanding was that the way to use out of the tree vif_driver is
to set vif_driver option in nova.conf
until there is a better way to support such cases but the commit [2]
removed this option.
Can someone clarify the current status (i.e. what is the
Hi,
I see that the option to specify vif_driver in nova.conf for libvirt is
deprecated for Juno release.
What is the way to use an external VIF driver (i.e. that is out of the
tree)?
Itzik
___
OpenStack-dev mailing list
Hi,
Have you looked at
https://github.com/openstack/neutron/blob/master/neutron/db/migration/README
?
Itzik
On 08/04/2014 23:41, Paul Ward wrote:
Is anyone else out there seeing failures that appear to be because
alembic is not upgrading db tables in neutron? I'm seeing, on an
upgrade,
Hi,
I have a patch waiting for review.
https://review.openstack.org/#/c/35189/ - Adding VIF Driver to support
Mellanox Plugin.
I'll appreciate any comment/review.
Thanks,
Itzik
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
On 05/07/2013 17:02, Daniel P. Berrange wrote:
On Thu, Jul 04, 2013 at 11:53:45AM +0300, Itzik Brown wrote:
Hi,
We released a code for a VIF Driver that will work with Mellanox
Quantum Plugin.
Mellanox plugin provisions Virtual Networks via embedded HCA
switching functionality (SR-IOV
13 matches
Mail list logo
