Hi Murali,
Thanks for your response, I did the same, it has resolved errors apparently
but 1) neutron agent-list shows no agent for sriov, 2) neutron port is
created successfully but creating vm is erred in scheduling as follows:
result from neutron agent-list:
Just to be more clear, command $lspci | grep -i Ethernet gives following
output:
01:00.0 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port
Backplane Connection (rev 01)
01:00.1 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port
Backplane Connection (rev 01)
03:00.0
On 15/12/14 09:32, Anant Patil wrote:
On 12-Dec-14 06:29, Zane Bitter wrote:
On 11/12/14 01:14, Anant Patil wrote:
On 04-Dec-14 10:49, Zane Bitter wrote:
On 01/12/14 02:02, Anant Patil wrote:
On GitHub:https://github.com/anantpatil/heat-convergence-poc
I'm trying to review this code at the
On 15/12/14 07:47, Murugan, Visnusaran wrote:
Hi Zane,
We have been going through this chain for quite some time now and we still feel
a disconnect in our understanding.
Yes, I thought last week that we were on the same page, but now it looks
like we're drifting off again :(
Can you put
On 15/12/14 10:15, Anant Patil wrote:
On 13-Dec-14 05:42, Zane Bitter wrote:
On 12/12/14 05:29, Murugan, Visnusaran wrote:
-Original Message-
From: Zane Bitter [mailto:zbit...@redhat.com]
Sent: Friday, December 12, 2014 6:37 AM
To: openstack-dev@lists.openstack.org
Subject: Re:
Hi All, Since the split of the Neutron services (FWaaS, LBaaS, VPNaaS) into
individual repositories is done, and the follow-up activities are
progressing, I am proposing that we suspend the weekly IRC Advanced
Services' meeting [1] until we need it again.
Thanks,
~Sumit.
[1]
I'm happy to announce we've cleared the schedule and the Mid-Cycle is
confirmed for February 18 - 20 in Seattle, WA at HP's downtown offices.
Please refer to the etherpad linked below for details including address
and instructions for access to the building.
PLEASE make sure you add yourself to
So I think this is something we really should get agreement on across the
open stack API first before flipping back and forth on a case by case
basis.
Personally I think we should be using uuids for uniqueness and leave any
extra restrictions to a ui layer if really required. If we try to have
Hi David,
You error is not related to agent.
I would suggest to check:
1.nova.conf at your compute node for pci whitelist configuration
2. Neutron server configuration for correct physical_network label
matching the label in pci whitelist
3. Nova DB tables containing PCI
Meeting on #openstack-meeting at 1500 UTC (8:00AM MST)
1) Status on cleanup work -
https://wiki.openstack.org/wiki/Gantt/kilo
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
___
OpenStack-dev
-Original Message-
From: henry hly [mailto:]
Sent: Tuesday, December 16, 2014 3:12 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Minimal ML2 mechanism driver after Neutron
decomposition change
On Tue, Dec 16, 2014 at 1:53 AM, Neil
But then, is this decomposition is for the ML2 MDs or for all vendor specific
plugins/drivers in all the sub divisions around neutron?
Any comments on the same.
--
Trinath Somanchi - B39208
trinath.soman...@freescale.com | extn: 4048
-Original Message-
From: Irena Berezovsky
On 15 December 2014 at 09:53, Neil Jerram neil.jer...@metaswitch.com
wrote:
Hi all,
Following the approval for Neutron vendor code decomposition
(https://review.openstack.org/#/c/134680/), I just wanted to comment
that it appears to work fine to have an ML2 mechanism driver _entirely_
out
Hi David,
From the neutron agent-list I can see that you are not running the
sriov-agent.
Please run the sriov-agent after adding the below configuration.
Add the below configuration at controller in
/etc/neutron/plugins/ml2/ml2_conf_sriov.ini
[ml2_sriov]
# (ListOpt) Comma-separated list of
#
Thanks Nikolay,
I also left my comments and tend to like Alt2 better than others. Agree with
Dmitri that “all-permutations” thing can be just a different construct in the
language and “concurrency” should be rather a policy than a property of
“for-each” because it doesn’t have any impact on
Good questions. I'm also looking for the linux bridge MD, SRIOV MD...
Who will be responsible for these drivers?
Excellent question. In my opinion, 'technology' specific but not vendor
specific MD (like SRIOV) should not be maintained by specific vendor. It
should be accessible for all
Hi Irena and Murali,
Thanks a lot for your reply!
Here is the output from pci_devices table of nova db:
select * from pci_devices;
101 - 117 of 117 matches
Mail list logo
