ground, where we publish a
neutron-server container with a variety of common plugins. If operators
have specific requirements, they should create their own config file and
build their own images, which we expect any serious production setup to
be doing anyway.
-Paul
Hi Sandhya,
See inline:
On Mon, Dec 11, 2017 at 8:49 AM, Sandhya Dasu (sadasu) <sad...@cisco.com>
wrote:
> Hi Steven and Emilien,
>
> I need your advice on how to proceed with the fix in
> https://review.openstack.org/#/c/521632/.
Hi Steven and Emilien,
I need your advice on how to proceed with the fix in
https://review.openstack.org/#/c/521632/.
The issue in question is that code in puppet-neutron for the Nexus switch,
performs a ping test to see if all the Nexus switches specified in the
configuration are actually
+1
Thanks for organizing.
On 9/13/17, 7:28 AM, "Thomas Morin" wrote:
+1
-Thomas
Takashi Yamamoto, 2017-09-13 03:05:
> +1
>
> On Wed, Sep 13, 2017 at 2:56 AM, IWAMOTO Toshihiro
> wrote:
> > +1
>
+1
Looking fwd to it.
Sandhya
From: Sukhdev Kapur >
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
>
Date: Thursday, October 27, 2016 at
Hi Miguel,
Both time slots work for me. Thanks for rekindling this effort.
Thanks,
Sandhya
From: Miguel Ángel Ajo majop...@redhat.commailto:majop...@redhat.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
Hi Steve,
For SR-IOV testing we have a CI job running on a multi node setup with
Cisco SR-IOV NIC doing API testing on Neutron patches. It is not reporting
results up to Neutron yet and currently is used for internal testing only.
We are working on the following:
1. Getting the full Tempest
PM
To: Sandhya Dasu (sadasu); Brent Eagles; Steve Gordon
Cc: Dan Smith; OpenStack Development Mailing List (not for usage
questions); John Garbutt; Russell Bryant; yunhong-jiang; Itzik Brown;
Yongli He; Jay Pipes; Irena Berezovsky
Subject: Re: Informal meeting before SR-IOV summit presentation
Thanks for all your replies.
Thanks for the great inputs on how to frame the discussion in the etherpad
so it becomes easier for people to get on board. We will add author indent
to track the source of the changes. Will work on cleaning that up.
Regarding the session itself, as you probably
I have no idea, how to pick a location.
Should we meet at the Cisco booth at 1pm and then take it from there?
Any other ideas?
Thanks,
sandhya
On 5/9/14 3:17 PM, Brent Eagles beag...@redhat.com wrote:
On 09/05/14 04:21 PM, Sandhya Dasu (sadasu) wrote:
Thanks for all your replies.
Thanks
Hi,
It would be nice to have an informal discussion / unconference session
before the actual summit session on SR-IOV. During the previous IRC
meeting, we were really close to identifying the different use cases.
There was a dangling discussion on introducing another level of
indirection between
try to push some reference code later today.
BR,
Irena
-Original Message-
From: Robert Li (baoli) [mailto:ba...@cisco.com]
Sent: Wednesday, March 05, 2014 4:46 AM
To: Sandhya Dasu (sadasu); OpenStack Development Mailing List (not for
usage questions); Irena Berezovsky; Robert Kukura; Brian
.
5. Implement validate_port_binding(). This will always return True for Mds
that do not have an L2 agent.
Please let me know if I left out anything.
Thanks,
Sandhya
On 2/25/14 9:18 AM, Sandhya Dasu (sadasu) sad...@cisco.com wrote:
Hi,
As a follow up from today's IRC, Irena, are you looking
AM, Sandhya Dasu (sadasu) sad...@cisco.com wrote:
Hi Bob and Irena,
Thanks for the clarification. Irena, I am not opposed to a
SriovMechanismDriverBase/Mixin approach, but I want to first figure out
how much common functionality there is. Have you already looked at this?
Thanks,
Sandhya
On 2/5
wrote:
Please see inline my understanding
-Original Message-
From: Robert Kukura [mailto:rkuk...@redhat.com]
Sent: Tuesday, February 04, 2014 11:57 PM
To: Sandhya Dasu (sadasu); OpenStack Development Mailing List (not for
usage questions); Irena Berezovsky; Robert Li (baoli); Brian Bowen
there is a common pass between nova
and neutron.
BR,
Irena
From: Sandhya Dasu (sadasu) [mailto:sad...@cisco.com]
Sent: Friday, January 31, 2014 6:46 PM
To: Irena Berezovsky; Robert Li (baoli); Robert Kukura; OpenStack Development
Mailing List (not for usage questions); Brian Bowen (brbowen)
Subject: Re
here, just think we need common layer
for managing SRIOV port at neutron, since there is a common pass between nova
and neutron.
BR,
Irena
From: Sandhya Dasu (sadasu) [mailto:sad...@cisco.com]
Sent: Friday, January 31, 2014 6:46 PM
To: Irena Berezovsky; Robert Li (baoli); Robert Kukura; OpenStack
here, just think we need common layer
for managing SRIOV port at neutron, since there is a common pass between nova
and neutron.
BR,
Irena
From: Sandhya Dasu (sadasu) [mailto:sad...@cisco.com]
Sent: Friday, January 31, 2014 6:46 PM
To: Irena Berezovsky; Robert Li (baoli); Robert Kukura
for the summary.
Please, see inline
From: Robert Li (baoli) [mailto:ba...@cisco.com]
Sent: Thursday, January 30, 2014 10:45 PM
To: Robert Kukura; Sandhya Dasu (sadasu); Irena Berezovsky; OpenStack
Development Mailing List (not for usage questions); Brian Bowen (brbowen)
Subject: [openstack-dev] [nova][neutron
Hi Irena,
Thanks for pointing out an alternative to the network xml solution to live
migration. I am still not clear about the solution.
Some questions:
1. Where does the rename of the PCI device network interface name occur?
2. Can this rename be done for a VF? I think your example
Hi,
One use case was brought up in today's meeting that I think is not valid.
It is the use case where all 3 vnic types : Virtio, direct and macvtap (the
terms used in the meeting were slow, fast, faster/foobar) could be attached to
the same VM. The main difference between a direct and
21 matches
Mail list logo