Ok Rich, I'm going to test your tools and add it in the workflow if available
on the host.
s.
- Original Message -
From: Richard W.M. Jones rjo...@redhat.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Friday, January 31,
On 03/02/14 06:09 +, Eiichi Aikawa wrote:
Hi,
Here is the blueprint about improvement of accessing to glance API server.
https://blueprints.launchpad.net/nova/+spec/improvement-of-accessing-to-glance
The summary of this bp is:
- Glance API Servers are categorized into two groups: Primary
On 01/02/14 00:06 -0800, Mike Perez wrote:
Folks,
I would love to get people together who are interested in Cinder stability
to really dedicate a few days. This is not for additional features, but rather
finishing what we already have and really getting those in a good shape
before the end
Hi Dmitry,
Thanks for the detail reply.
I am asking why because *except swift* all components are properly
installed ready to use.
So I need single hint that could solve my problem. And yes, in case of
Linux, no doubt that it has to work.
Waiting for favourable guidance,
Hi,
There is a blueprint ECU[1], and that is an interesting idea for me.
so I'd like to know the comments about ECU idea.
After production environments start, the operators will need to add
compute nodes before exhausting the capacity.
On the scenario, they'd like to add cost-efficient machines
Similar capabilities are being introduced here:
https://review.openstack.org/#/c/61839/
Regards,
Alex
From: Kenichi Oomichi oomi...@mxs.nes.nec.co.jp
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org,
Date: 03/02/2014 11:48 AM
Hi,
Sorry if this has been already discussed (traffic is high in this list).
I've just checked, and our global-requirements.txt still has:
WebOb=1.2.3,1.3
Problem: both Sid and Trusty have version 1.3.
What package is holding the newer version of webob? Can we work toward
supporting version
On 02 Feb 2014, at 23:10 , Alessandro Pilotti apilo...@cloudbasesolutions.com
wrote:
On 02 Feb 2014, at 23:01 , Michael Still mi...@stillhq.com wrote:
It seems like there were a lot of failing Hyper-V CI jobs for nova
yesterday. Is there some systemic problem or did all those patches
+1 Remote!
~Swapnil
On Mon, Feb 3, 2014 at 2:41 PM, Flavio Percoco fla...@redhat.com wrote:
On 01/02/14 00:06 -0800, Mike Perez wrote:
Folks,
I would love to get people together who are interested in Cinder
stability to really dedicate a few days. This is not for additional
features,
My apologies for firing this off and then hiding under the FOSDEM rock.
In light of the points raised by Devananda and Robert, I no longer think
fiddling with the scheduler is the way to go.
Note this was never intended to break/confuse all TripleO users -- I
considered it a cleaner
On 02/03/2014 11:45 AM, Thomas Goirand wrote:
Hi,
Sorry if this has been already discussed (traffic is high in this list).
I've just checked, and our global-requirements.txt still has:
WebOb=1.2.3,1.3
Problem: both Sid and Trusty have version 1.3.
What package is holding the newer version of
On 02/02/2014 08:33 PM, Jay Pipes wrote:
On Sun, 2014-02-02 at 07:13 -0500, Sean Dague wrote:
Just noticed this at the end of a successful run:
http://logs.openstack.org/15/63215/13/check/check-tempest-dsvm-full/2636cae/console.html#_2014-02-02_12_02_44_422
It looks like the merge of
On 01/29/2014 11:10 PM, Matt Riedemann wrote:
On Monday, January 27, 2014 7:17:27 AM, Alessandro Pilotti wrote:
On 25 Jan 2014, at 16:51 , Matt Riedemann mrie...@linux.vnet.ibm.com
wrote:
On 1/24/2014 3:41 PM, Peter Pouliot wrote:
Hello OpenStack Community,
I am excited at this
On Mon, Jan 27, 2014 at 12:42 PM, Doug Hellmann doug.hellm...@dreamhost.com
wrote:
We have a blueprint open for separating translated log messages into
different domains so the translation team can prioritize them differently
(focusing on errors and warnings before debug messages, for
On 12/20/2013 08:21 PM, Bogdan Dobrelya wrote:
*Preamble*
Hi stackers, I was trying to implement correct APP-NAME tags for remote
logging in Fuel for Openstack, and faced the
https://bugs.launchpad.net/nova/+bug/904307 issue. There are no logging
options in Python 2.6/2.7 to address this
On Mon, 2014-02-03 at 10:03 +0100, Flavio Percoco wrote:
IMHO, the bit that should really be optimized is the selection of the
store nodes where the image should be downloaded from. That is,
selecting the nearest location from the image locations and this is
something that perhaps should
On 02/03/2014 07:36 AM, Monty Taylor wrote:
On 02/02/2014 08:33 PM, Jay Pipes wrote:
On Sun, 2014-02-02 at 07:13 -0500, Sean Dague wrote:
Just noticed this at the end of a successful run:
On Mon, Feb 3, 2014 at 7:31 AM, Monty Taylor mord...@inaugust.com wrote:
On 02/03/2014 11:45 AM, Thomas Goirand wrote:
Hi,
Sorry if this has been already discussed (traffic is high in this list).
I've just checked, and our global-requirements.txt still has:
WebOb=1.2.3,1.3
Problem: both
On 02/03/2014 04:11 AM, Flavio Percoco wrote:
On 01/02/14 00:06 -0800, Mike Perez wrote:
Folks,
I would love to get people together who are interested in Cinder
stability to really dedicate a few days. This is not for additional
features, but rather finishing what we already have and really
Goodday, OpenStack DBaaS users/contributors.
I'd like to start topic related to refactoring of API extensions. Since
Trove already supports more than one db engines (mysql and redis in
single-instance mode).
At this moment if contributors will decide that one of the integrated
db engines
On 03/02/14 10:13 -0500, Jay Pipes wrote:
On Mon, 2014-02-03 at 10:03 +0100, Flavio Percoco wrote:
IMHO, the bit that should really be optimized is the selection of the
store nodes where the image should be downloaded from. That is,
selecting the nearest location from the image locations and
Hi,
I was at the FOSDEM event this week-end and some interesting talks about
asyncio raised my interest about this framework for replacing eventlet.
Although there is an experimental port of asyncio for Python 2.6 named
trollius [1], I think it would be a good move for having Python 3.
I know
Hi Vipin, Doug,
I've followed instructions from Doug and this page [1]. Will give
Infra folks a bit of time and then ping them in a day or so.
Git Repo on Github : https://github.com/dims/oslo.vmware
Request to create Gerrit Groups :
https://bugs.launchpad.net/openstack-ci/+bug/1275817
Review
Solum community,
I notice that we are using String(36) UUID values in the database schema as
primary key for many new tables that we are creating. For example:
https://review.openstack.org/#/c/68328/10/solum/objects/sqlalchemy/application.py
Proposal: Add an int or bigint ID as the primary
If you're running on a machine with devstack these dependencies *should*
already be met.
If you like to work on VMs on your local box I have build a Vagrant dev
environment that should take care of your dependencies here -
https://github.com/rackerlabs/vagrant-solum-dev
I think it's
Maybe wednesday at noon?
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
I have a related BP:
https://blueprints.launchpad.net/glance/+spec/image-location-selection-strategy
IMO, as I mentioned in its description, it can be applied in glance
and consumer (glance's client) both sides: in glance internal, this
can be used for image-download handling and direct_url_
On Mon, Feb 03 2014, Sylvain Bauza wrote:
I was at the FOSDEM event this week-end and some interesting talks about
asyncio raised my interest about this framework for replacing eventlet.
Although there is an experimental port of asyncio for Python 2.6 named
trollius [1], I think it would be
Which time zone?
On Wednesdays between 11.00am - noon (US Central time) there is git integration
working group meeting.
-Original Message-
From: Clayton Coleman ccole...@redhat.com
Sent: Monday, February 3, 2014 10:35am
To: OpenStack Development Mailing List (not for usage questions)
I was looking through Nova Objects with a view to creating an extensible object
that can be used by writers of plugins to include data generated by the plugin
(others have also done the same e.g. https://review.openstack.org/#/c/65826/ )
On the way I noticed what I think is a bug in Nova
Mike,
Great idea!
I can participate remotely.
Let me know how I can be of the best help!
Jay S. Bryant
IBM Cinder Subject Matter ExpertCinder Core Member
Department 7YLA, Building 015-2, Office E125, Rochester, MN
Telephone: (507) 253-4270, FAX (507) 253-6410
TIE Line: 553-4270
Hi,
Thanks for joining us today!
Here are the links to minutes and log:
Minutes:
http://eavesdrop.openstack.org/meetings/mistral/2014/mistral.2014-02-03-16.00.html
Log:
http://eavesdrop.openstack.org/meetings/mistral/2014/mistral.2014-02-03-16.00.log.html
Renat Akhmerov
@ Mirantis Inc.
Denis,
It seems that you are hitting on a couple of points here. 1) You aren't a
fan of the fact that calls to user/db are routed through an extensions
written for mysql. 2) This creates a conflict when a datastore does not
support those calls. I am confused about your solution.
Your suggestion
Thanks, Dims!
On Mon, Feb 3, 2014 at 11:12 AM, Davanum Srinivas dava...@gmail.com wrote:
Hi Vipin, Doug,
I've followed instructions from Doug and this page [1]. Will give
Infra folks a bit of time and then ping them in a day or so.
Git Repo on Github : https://github.com/dims/oslo.vmware
On Mon, 2014-02-03 at 16:22 +, Paul Montgomery wrote:
Solum community,
I notice that we are using String(36) UUID values in the database
schema as primary key for many new tables that we are creating. For
example:
On Thu, Jan 30, 2014 at 8:55 AM, Dan Smith d...@danplanet.com wrote:
I'm of the opinion that the scheduler should use objects, for all the
reasons that Nova uses objects, but that they should not be Nova
objects. Ultimately what the scheduler needs is a concept of capacity,
allocations, and
On Mon, 2014-02-03 at 17:04 +0100, Flavio Percoco wrote:
On 03/02/14 10:13 -0500, Jay Pipes wrote:
On Mon, 2014-02-03 at 10:03 +0100, Flavio Percoco wrote:
IMHO, the bit that should really be optimized is the selection of the
store nodes where the image should be downloaded from. That is,
Hello, Kevin.
1. Users/Databases CRUD operation are not the part of Trove core API.
2. And i'm not suggesting to define same extension, if database supports
ACL and storage distinction developer would be able to define
it's own ReST routes for all his needs in term of CRUD operations.
3.
So, I wrote the original rolling updates spec about a year ago, and the
time has come to get serious about implementation. I went through it and
basically rewrote the entire thing to reflect the knowledge I have
gained from a year of working with Heat.
Any and all comments are welcome. I intend
On Thu, Jan 30, 2014 at 10:45 PM, Christopher Yeoh cbky...@gmail.com wrote:
So with it now looking like nova-network won't go away for the forseable
future, it looks like we'll want nova-network support in the Nova V3 API
after all. I've created a blueprint for this work here:
Good point. We can try immediately after the git inter workflow if folks
prefer. 12pm US CST, 1pm EST.
- Original Message -
Which time zone?
On Wednesdays between 11.00am - noon (US Central time) there is git
integration working group meeting.
-Original Message-
On Mon, Feb 3, 2014 at 10:02 AM, Joe Gordon joe.gord...@gmail.com wrote:
On Thu, Jan 30, 2014 at 10:45 PM, Christopher Yeoh cbky...@gmail.com wrote:
So with it now looking like nova-network won't go away for the forseable
future, it looks like we'll want nova-network support in the Nova V3 API
On Thu, Jan 30, 2014 at 2:28 AM, Julien Danjou jul...@danjou.info wrote:
On Thu, Jan 30 2014, Joe Gordon wrote:
Hi Joe,
While looking at gate failures trying to improve our classification
rate I stumbled across this:
Hi everyone,
The OpenStack Infrastructure (Infra) team is hosting our weekly
meeting tomorrow, Tuesday February 4th, at 19:00 UTC in
#openstack-meeting
Meeting agenda available here:
https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting (anyone is
welcome to to add agenda items)
Everyone
Hi all,
Both openstack-meeting and openstack-meeting-alt are available today. Lets
meet at UTC 2000 @ openstack-meeting-alt.
Thanks,
Sandhya
From: Irena Berezovsky ire...@mellanox.commailto:ire...@mellanox.com
Date: Monday, February 3, 2014 12:52 AM
To: Sandhya Dasu
Nice idea. I also think that filters and weighers are FilterScheduler-specific.
Thus, that is unnecessary for SolverScheduler to try to translate all
filters/weighers into constraints. It would be easier for transition, though.
Anyway, we just need some placement logics that will be written as
Quick thoughts:
- I'd like to be able to express a minimum service percentage: e.g. I
know I need 80% of my capacity available at anyone time, so an
additional constraint to the unit counts, is to stay below 20% down at
a time (and this implies that if 20% have failed, either stop or spin
up
On Mon, Feb 3, 2014 at 7:13 AM, Jay Pipes jaypi...@gmail.com wrote:
On Mon, 2014-02-03 at 10:03 +0100, Flavio Percoco wrote:
IMHO, the bit that should really be optimized is the selection of the
store nodes where the image should be downloaded from. That is,
selecting the nearest location
On Wed, Jan 29, 2014 at 3:28 PM, Justin Santa Barbara
jus...@fathomdb.com wrote:
Jarret Raim wrote:
I'm presuming that this is our last opportunity for API review - if
this isn't the right occasion to bring this up, ignore me!
Apparently you are right:
For incubation
'Project APIs should be
Has anyone ever considered adding the concept of transaction IDs to the
openstack REST API?
I'm envisioning a way to handle long-running transactions more cleanly.
For example:
1) A user sends a request to live-migrate an instance
2) Openstack acks the request and includes a transaction
On Mon, 2014-02-03 at 10:59 -0800, Mark Washenberger wrote:
On Mon, Feb 3, 2014 at 7:13 AM, Jay Pipes jaypi...@gmail.com wrote:
On Mon, 2014-02-03 at 10:03 +0100, Flavio Percoco wrote:
IMHO, the bit that should really be optimized is the
selection of the
On 02/03/2014 12:28 PM, Khanh-Toan Tran wrote:
Another though would be the need for Instance Group API [1].
Currently users can only request multiple instances of the same
flavors. These requests do not need LP to solve, just placing
instances one by one is sufficient. Therefore we need this
On 02/03/14 at 01:10pm, Chris Friesen wrote:
Has anyone ever considered adding the concept of transaction IDs to
the openstack REST API?
I'm envisioning a way to handle long-running transactions more
cleanly. For example:
1) A user sends a request to live-migrate an instance
2) Openstack
The solver-scheduler is designed to solve for an arbitrary list of instances of
different flavors. We need to have some updated apis in the scheduler to be
able to pass on such requests. Instance group api is an initial effort to
specify such groups.
Even now the existing solver scheduler
Excerpts from Robert Collins's message of 2014-02-03 10:47:06 -0800:
Quick thoughts:
- I'd like to be able to express a minimum service percentage: e.g. I
know I need 80% of my capacity available at anyone time, so an
additional constraint to the unit counts, is to stay below 20% down at
a
On Mon, Feb 3, 2014 at 5:29 PM, Julien Danjou jul...@danjou.info wrote:
Last, but not least, trollius has been created by Victor Stinner, who
actually did that work with porting OpenStack in mind and as the first
objective.
AFAIK: victor had plans to send a mail about it to the list later
Hi,
Since, openstack-meeting-alt seems to be in use, baoli and myself are
moving to openstack-meeting. Hopefully, Bob Kukura Irena can join soon.
Thanks,
Sandhya
From: Sandhya Dasu sad...@cisco.commailto:sad...@cisco.com
Reply-To: OpenStack Development Mailing List (not for usage
On 02/03/2014 01:31 PM, Andrew Laski wrote:
On 02/03/14 at 01:10pm, Chris Friesen wrote:
Has anyone ever considered adding the concept of transaction IDs to
the openstack REST API?
I'm envisioning a way to handle long-running transactions more
cleanly. For example:
1) A user sends a request
So, I wrote the original rolling updates spec about a year ago, and the
time has come to get serious about implementation. I went through it and
basically rewrote the entire thing to reflect the knowledge I have
gained from a year of working with Heat.
Any and all comments are welcome. I
Hi all,
After talking with john g. about taskflow in cinder and seeing more and
more reviews showing up I wanted to start a thread to gather all our
lessons learned and how we can improve a little before continuing to add
too many more refactoring and more reviews (making sure everyone is
Basically, if object A has object B as a child, and deserialization
finds object B to be an unrecognized version, it will try to back
port the object A to the version number of object B.
Right, which is why we rev the version of, say, the InstanceList when we
have to rev Instance itself, and
On 03/02/14 16:22 +, Paul Montgomery wrote:
Solum community,
I notice that we are using String(36) UUID values in the database schema as
primary key for many new tables that we are creating. For example:
https://review.openstack.org/#/c/68328/10/solum/objects/sqlalchemy/application.py
Heya Clint, this BP looks really good - it should significantly simplify
the implementation of scaling if this becomes a core Heat feature. Comments
below.
On Mon, Feb 3, 2014 at 2:46 PM, Thomas Herve thomas.he...@enovance.comwrote:
So, I wrote the original rolling updates spec about a year
On Mon, Feb 3, 2014 at 1:53 PM, Joshua Harlow harlo...@yahoo-inc.com wrote:
Hi all,
After talking with john g. about taskflow in cinder and seeing more and
more reviews showing up I wanted to start a thread to gather all our
lessons learned and how we can improve a little before continuing to
Seems the openstack-meeting-alt is busy, let's use openstack-meeting
From: Sandhya Dasu (sadasu) [mailto:sad...@cisco.com]
Sent: Monday, February 03, 2014 8:28 PM
To: Irena Berezovsky; Robert Li (baoli); Robert Kukura; OpenStack Development
Mailing List (not for usage questions); Brian Bowen
Hello Again!
At the meeting last week we discussed some options around getting true
multitenancy in nova. The use case that we are trying to support can be
described as follows:
Martha, the owner of ProductionIT provides it services to multiple Enterprise
clients. She would like to offer
Excerpts from Thomas Herve's message of 2014-02-03 12:46:05 -0800:
So, I wrote the original rolling updates spec about a year ago, and the
time has come to get serious about implementation. I went through it and
basically rewrote the entire thing to reflect the knowledge I have
gained from
I was trying my best to avoid adding extra job types to support
mapreduce variants like streaming or mapreduce with pipes, but it seems
that adding the types is the simplest solution.
On the API side, Savanna can live without a specific job type by
examining the data in the job record.
I'd like to see if there is interest in discussing vendor plugins for L3
services. The goal is to strive for consistency across vendor plugins/drivers
and across service types (if possible/sensible). Some of this could/should
apply to reference drivers as well. I'm thinking about these topics
I have looked at the code that you posted. I am concerned that there
are db queries performed inside nested loops. The approach looks
sound from a functional perspective but I think these loops will run
very slowly and increase pressure on the db.
I tend to think that if a router has an extra
Hi,
I would be interested in this discussion. Below are some time slot
suggestions:
Mon: 19:00, 20:00 UTC (11:00, 12:00 PST)
Wed: 20:00, 21:00 UTC (12:00, 13:00 PST)
Thu: 19:00, 20:00, 21:00 UTC (11:00, 12:00, 13:00 PST)
Thanks,
-hemanth
On Mon, Feb 3, 2014 at 2:19 PM, Paul Michali
I see two points:
* having Savanna types mapped to Oozie action types is intuitive for hadoop
users and this is something we would like to keep
* it is hard to distinguish different kinds of one job type
Adding 'subtype' field will solve both problems. Having it optional will
not break backward
On Mon, Feb 3, 2014 at 1:50 PM, Adam Young ayo...@redhat.com wrote:
HACK: In a new client, look at the URL. If it ends with /v2.0, chop it
off and us the substring up to that point.
Now, at this point you are probably going: That is ugly, is it really
necessary? Can't we do something
On Tue, Feb 4, 2014 at 6:20 AM, Adam Young ayo...@redhat.com wrote:
We have to support old clients.
Old clients expect that the URL that comes back for the service catalog
has the version in it.
Old clients don't do version negotiation.
Thus, we need an approach to not-break old clients
Hi,
We are in the process of submitting a third party Neutron plugin that uses
urllib3 for the connection pooling feature available in urllib3. httplib2
doesn't provide this capability.
Is it possible to add urllib3 to requirements.txt? If this is OK, please
advise on the process to add this.
On Fri, Jan 31, 2014 at 12:13 PM, Devananda van der Veen
devananda@gmail.com wrote:
I think your driver should implement a wrapper around both VendorPassthru
interfaces and call each appropriately, depending on the request. This
keeps each VendorPassthru driver separate, and encapsulates
Hi, Stackers.
The deadline for icehouse comes really quickly and I understand that there
are a lot of work todo, but I would like get your attention about my
blueprint for configurable locked vm api.
- https://blueprints.launchpad.net/nova/+spec/configurable-locked-vm-api
So far, developer
Thanks john for the input.
Hopefully we can help focus some of the refactoring on solving the
state-management problem very soon.
For the mocking case, is there any active work being done here?
As for the state-management and persistence, I think that the goal of both
of these will be reached
On Tue, Feb 4, 2014 at 4:32 AM, Joe Gordon joe.gord...@gmail.com wrote:
On Thu, Jan 30, 2014 at 10:45 PM, Christopher Yeoh cbky...@gmail.com
wrote:
So with it now looking like nova-network won't go away for the forseable
future, it looks like we'll want nova-network support in the Nova V3
I’m interested to know why you are using urllib3 directly. Have you considered
using the requests module? requests is built upon urllib3 and already a
dependency of Neutron.
mark
On Feb 3, 2014, at 6:45 PM, Hemanth Ravi hemanthrav...@gmail.com wrote:
Hi,
We are in the process of
Hi,
Some Neutron developers have some really great slides from some of the summits,
and I'd like to link them in the documentation I am building as part of a
developer doc blueprint,
with proper attribution.
https://blueprints.launchpad.net/neutron/+spec/developer-documentation
I'm hoping to
On 02/03/2014 07:25 PM, Jae Sang Lee wrote:
Hi, Stackers.
The deadline for icehouse comes really quickly and I understand that there
are a lot of work todo, but I would like get your attention about my
blueprint for configurable locked vm api.
-
Mark,
We had started the plugin dev with grizzly initially and the grizzly
distribution included httplib2. We used urllib3 for the HTTPConnectionPool
object. Overlooked the requests module included in the master when we
migrated. I'll take a look at using requests for the same support.
Thanks,
Hi,
I've posted a preliminary agenda for the upcoming IPv6 meeting. See everyone
soon!
https://wiki.openstack.org/wiki/Meetings/Neutron-IPv6-Subteam#Agenda_for_Feb_4th
---
Sean M. Collins
___
OpenStack-dev mailing list
Hi,
This is just a reminder that we are going to have a weekly meeting of
Murano team in IRC (#openstack-meeting-alt) on Feb, 4 at 17:00 UTC (9am
PST) .
The agenda can be found here:
https://wiki.openstack.org/wiki/Meetings/MuranoAgenda#Agenda
Feel free to add anything you want to discuss.
--
On 02/03/2014 11:31 PM, Doug Hellmann wrote:
On Mon, Feb 3, 2014 at 7:31 AM, Monty Taylor mord...@inaugust.com
mailto:mord...@inaugust.com wrote:
On 02/03/2014 11:45 AM, Thomas Goirand wrote:
Hi,
Sorry if this has been already discussed (traffic is high in
On 1/13/2014 10:49 AM, Sahid Ferdjaoui wrote:
Hello all,
It looks 100% of the pep8 gate for nova is failing because of a bug reported,
we probably need to mark this as Critical.
https://bugs.launchpad.net/nova/+bug/1268614
Ivan Melnikov has pushed a patchset waiting for review:
1) Memcached based scheduler updates
2) Scheduler code forklift
3) Opens
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
On 4 February 2014 14:33, Joe Gordon joe.gord...@gmail.com wrote:
John and I discussed a third possibility:
nova-network v3 should be an extension, so the idea was to: Make
nova-network API a subset of neturon (instead of them adopting our API
we adopt theirs). And we could release v3
Hi, John and all,
I updated the blueprint
https://blueprints.launchpad.net/nova/+spec/pci-extra-info-icehouse according
to your feedback, to add the backward compatibility/upgrade issue/examples.
I try to separate this BP with the SR-IOV NIC support as a standalone
90 matches
Mail list logo
