Re: [openstack-dev] [tripleo] ansible roles in tripleo

On Tue, Aug 14, 2018 at 1:53 PM Jill Rouleau wrote: > > Hey folks, > > Like Alex mentioned[0] earlier, we've created a bunch of ansible roles > for tripleo specific bits. The idea is to start putting some basic > cookiecutter type things in them to get things started, then move some >

[openstack-dev] neutron 13.0.0.0rc2 (rocky)

Hello everyone, A new release candidate for neutron for the end of the Rocky cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/neutron/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be

Re: [openstack-dev] [barbican][oslo][release][requirements] FFE request for castellan

> > > > > > I've approved it for a UC only bump > > > > > We are still waiting on https://review.openstack.org/594541 to merge, > but I already voted and noted that it was FFE approved. > > -- > Matthew Thode (prometheanfire) And I have now approved the u-c update. We should be all set now.

Re: [openstack-dev] [oslo] UUID sentinel needs a home

Do you mean an actual fixture, that would be used like: class MyTestCase(testtools.TestCase): def setUp(self): self.uuids = self.useFixture(oslofx.UUIDSentinelFixture()).uuids def test_foo(self): do_a_thing_with(self.uuids.foo) ? That's... okay I guess, but the

Re: [openstack-dev] [nova][cinder][neutron] Cross-cell cold migration

On Wed, Aug 22, 2018 at 08:23:41PM -0500, Matt Riedemann wrote: > Hi everyone, > > I have started an etherpad for cells topics at the Stein PTG [1]. The main > issue in there right now is dealing with cross-cell cold migration in nova. > > At a high level, I am going off these requirements: > >

Re: [openstack-dev] [monasca][goal][python3] monasca's zuul migration is only partially complete

On 23/08/18 13:34, Doug Hellmann wrote: Excerpts from Doug Szumski's message of 2018-08-23 09:53:35 +0100: Thanks Doug, we had a discussion and we agreed that the best way to proceed is for you to submit your patches and we will carefully review them. I proposed those patches this morning.

Re: [openstack-dev] [TripleO] podman: varlink interface for nice API calls

On Wed, Aug 15, 2018 at 5:49 PM Jay Pipes wrote: > > On 08/15/2018 04:01 PM, Emilien Macchi wrote: > > On Wed, Aug 15, 2018 at 5:31 PM Emilien Macchi > > wrote: > > > > More seriously here: there is an ongoing effort to converge the > > tools around

[openstack-dev] Bumping eventlet to 0.24.1

This is your warning, if you have concerns please comment in https://review.openstack.org/589382 . cross tests pass, so that's a good sign... atm this is only for stein. -- Matthew Thode (prometheanfire) signature.asc Description: PGP signature

Re: [openstack-dev] [glance][horizon] Issues we found when using Community Images

Hi Andy, Can you comment more on what needs to be updated in Sahara? Are they simply issues in the UI (sahara-dashboard) or is there a problem consuming community images on the server side? I'm happy to pitch in, just would like to do it efficiently. Thanks, Jeremy On Wed, Aug 22, 2018 at 5:31

Re: [openstack-dev] [magnum] supported OS images and magnum spawn failures for Swarm and Kubernetes

Now with Fedora 26 I have etcd available but etcd fails. [root@swarm-u2rnie4d4ik6-master-0 ~]# /usr/bin/etcd --name="${ETCD_NAME}" --data-dir="${ETCD_DATA_DIR}" --listen-client-urls="${ETCD_LISTEN_CLIENT_URLS}" --debug 2018-08-23 14:34:15.596516 E | etcdmain: error verifying flags,

Re: [openstack-dev] [TripleO] podman: varlink interface for nice API calls

Dan, thanks for the details and answers. Appreciated. Best, -jay On 08/23/2018 10:50 AM, Dan Prince wrote: On Wed, Aug 15, 2018 at 5:49 PM Jay Pipes wrote: On 08/15/2018 04:01 PM, Emilien Macchi wrote: On Wed, Aug 15, 2018 at 5:31 PM Emilien Macchi mailto:emil...@redhat.com>> wrote:

[openstack-dev] [release] Release countdown for week R-0, August 27 - 31

This is the final countdown email for the Rocky development cycle. Thanks to everyone involved in the Rocky release! Development Focus - Teams attending the PTG should be preparing for those discussions and capturing information in the etherpads:

Re: [openstack-dev] [TripleO] podman: varlink interface for nice API calls

Question. Rather then writing a middle layer to abstract both container engines, couldn't you just use CRI? CRI is CRI-O's native language, and there is support already for Docker as well. Thanks, Kevin From: Jay Pipes [jaypi...@gmail.com] Sent:

Re: [openstack-dev] [TripleO] podman: varlink interface for nice API calls

On 8/23/18 6:36 PM, Fox, Kevin M wrote: Or use kubelet in standalone mode. It can be configured for either Cri-o or Docker. You can drive the static manifests from heat/ansible per host as normal and it would be a step in the greater direction of getting to Kubernetes without needing the

Re: [openstack-dev] [neutron][api][grapql] Proof of Concept

Hi Gilles, Ed pinged me earlier today in IRC in regards to this topic. After reading your message, I assumed that you had patches up for review in Gerrit. I looked for them, with the intent to list them in the agenda of the next Neutron team meeting, to draw attention to them. I couldn't find

Re: [openstack-dev] [nova][cinder][neutron] Cross-cell cold migration

On 23/08, Dan Smith wrote: > > I think Nova should never have to rely on Cinder's hosts/backends > > information to do migrations or any other operation. > > > > In this case even if Nova had that info, it wouldn't be the solution. > > Cinder would reject migrations if there's an incompatibility

Re: [openstack-dev] [oslo] UUID sentinel needs a home

> Do you mean an actual fixture, that would be used like: > > class MyTestCase(testtools.TestCase): > def setUp(self): > self.uuids = self.useFixture(oslofx.UUIDSentinelFixture()).uuids > > def test_foo(self): > do_a_thing_with(self.uuids.foo) > > ? > > That's... okay

[openstack-dev] [ironic][bifrost][sushy][ironic-inspector][ironic-ui][virtualbmc] sub-project/repository core reviewer changes

Greetings everyone! In our team meeting this week we stumbled across the subject of promoting contributors to be sub-project's core reviewers. Traditionally it is something we've only addressed as needed or desired by consensus with-in those sub-projects, but we were past due time to take a look

Re: [openstack-dev] [release] Release countdown for week R-0, August 27 - 31

2018年8月24日(金) 1:12 Sean McGinnis : > > This is the final countdown email for the Rocky development cycle. Thanks to > everyone involved in the Rocky release! > > Development Focus > - > > Teams attending the PTG should be preparing for those discussions and > capturing >

Re: [openstack-dev] [TripleO] podman: varlink interface for nice API calls

On 08/17/2018 07:45 AM, Cédric Jeanneret wrote: On 08/17/2018 12:25 AM, Steve Baker wrote: On 15/08/18 21:32, Cédric Jeanneret wrote: Dear Community, As you may know, a move toward Podman as replacement of Docker is starting. One of the issues with podman is the lack of daemon, precisely

Re: [openstack-dev] [all] [nova] [placement] placement below or beside compute after extraction?

On 8/23/2018 4:00 AM, Thierry Carrez wrote: In the OpenStack governance model, contributors to a given piece of code control its destiny. This is pretty damn fuzzy. So if someone wants to split out nova-compute into a new repo/project/governance with a REST API and all that, nova-core has no

Re: [openstack-dev] [TripleO] podman: varlink interface for nice API calls

Or use kubelet in standalone mode. It can be configured for either Cri-o or Docker. You can drive the static manifests from heat/ansible per host as normal and it would be a step in the greater direction of getting to Kubernetes without needing the whole thing at once, if that is the goal.

[openstack-dev] [all][api] POST /api-sig/news

Greetings OpenStack community, This week's meeting brings the return of the full SIG core-quartet as all core members were in attendance. The main topics were the agenda [7] for the upcoming Denver PTG [8], and the API-SIG still being listed as TC working group in the governance repository

Re: [openstack-dev] [all] [nova] [placement] placement below or beside compute after extraction?

On 8/22/2018 1:25 PM, Jeremy Stanley wrote: On 2018-08-22 11:03:43 -0700 (-0700), melanie witt wrote: [...] I think it's about context. If two separate projects do their own priority and goal setting, separately, I think they will naturally be more different than they would be if they were one

Re: [openstack-dev] [oslo] UUID sentinel needs a home

On 08/23/2018 01:25 PM, Doug Hellmann wrote: Excerpts from Eric Fried's message of 2018-08-23 09:51:21 -0500: Do you mean an actual fixture, that would be used like: class MyTestCase(testtools.TestCase): def setUp(self): self.uuids =

Re: [openstack-dev] [release] Release countdown for week R-0, August 27 - 31

> > > > We are still missing releases for the following tempest plugins. Some are > > pending getting pypi and release jobs set up, but please try to prioritize > > getting these done as soon as possible. > > > > barbican-tempest-plugin > > blazar-tempest-plugin > >

Re: [openstack-dev] [oslo] UUID sentinel needs a home

The compromise, using the patch as currently written [1], would entail adding one line at the top of each test file: uuids = uuidsentinel.UUIDSentinels() ...as seen (more or less) at [2]. The subtle difference being that this `uuids` wouldn't share a namespace across the whole process, only

Re: [openstack-dev] [TripleO] podman: varlink interface for nice API calls

On 8/23/18 6:22 PM, Fox, Kevin M wrote: Question. Rather then writing a middle layer to abstract both container engines, couldn't you just use CRI? CRI is CRI-O's native language, and there is support already for Docker as well. I may be messing up abstraction levels, but IMO when it's time

Re: [openstack-dev] [oslo] UUID sentinel needs a home

Excerpts from Eric Fried's message of 2018-08-23 09:51:21 -0500: > Do you mean an actual fixture, that would be used like: > > class MyTestCase(testtools.TestCase): > def setUp(self): > self.uuids = self.useFixture(oslofx.UUIDSentinelFixture()).uuids > > def test_foo(self): >

[openstack-dev] [senlin] Senlin Weekly Meeting Time Change

Thanks everyone for replying. Since there were no objections, we will move to the new meeting time. Our first meeting will be this week on Friday August 24 at 5:30 UTC. The meeting agenda has been posted: https://wiki.openstack.org/wiki/Meetings/SenlinAgenda#Agenda_.282018-08-24_0530_UTC.29 Feel

Re: [openstack-dev] [magnum] supported OS images and magnum spawn failures for Swarm and Kubernetes

Found the issue, I assume I have to use Fedora Atomic 26 until Rocky where I can start using Fedora Atomic 27. Will Fedora Atomia 28 be supported for Rocky? https://bugs.launchpad.net/magnum/+bug/1735381 (Run etcd and flanneld in system containers, In Fedora Atomic 27 etcd and flanneld are

Re: [openstack-dev] [nova][cinder][neutron] Cross-cell cold migration

> I think Nova should never have to rely on Cinder's hosts/backends > information to do migrations or any other operation. > > In this case even if Nova had that info, it wouldn't be the solution. > Cinder would reject migrations if there's an incompatibility on the > Volume Type (AZ, Referenced

Re: [openstack-dev] [goals][python3] please check with me before submitting any zuul migration patches

Hi, There is a conflict appearing on karbor projects: https://review.openstack.org/#/q/project:%255E.*karbor.*+topic:python3-first+status:open Please check the storyboard to check who is working on the target project if you want to help. https://storyboard.openstack.org/#!/story/2002586 On

Re: [openstack-dev] [glance][horizon] Issues we found when using Community Images

Hi Jeremy, > Can you comment more on what needs to be updated in Sahara? Are they > simply issues in the UI (sahara-dashboard) or is there a problem > consuming community images on the server side? We haven't looked into it much yet, so I couldn't tell you. I think it would be great to extend

[openstack-dev] cinder 13.0.0.0rc3 (rocky)

Hello everyone, A new release candidate for cinder for the end of the Rocky cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/cinder/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally

Re: [openstack-dev] [oslo] UUID sentinel needs a home

> On Aug 23, 2018, at 4:01 PM, Ben Nemec wrote: > > > >> On 08/23/2018 12:25 PM, Doug Hellmann wrote: >> Excerpts from Eric Fried's message of 2018-08-23 09:51:21 -0500: >>> Do you mean an actual fixture, that would be used like: >>> >>> class MyTestCase(testtools.TestCase): >>> def

Re: [openstack-dev] [neutron][api][grapql] Proof of Concept

Hi Miguel, I’m not sure but maybe You were looking for those patches: https://review.openstack.org/#/q/project:openstack/neutron+branch:feature/graphql > Wiadomość napisana przez Miguel Lavalle w dniu > 23.08.2018, o godz. 18:57: > > Hi Gilles, > > Ed pinged me earlier today in IRC in

Re: [openstack-dev] [ironic][bifrost][sushy][ironic-inspector][ironic-ui][virtualbmc] sub-project/repository core reviewer changes

++ // jim On Thu, Aug 23, 2018 at 2:24 PM, Julia Kreger wrote: > Greetings everyone! > > In our team meeting this week we stumbled across the subject of > promoting contributors to be sub-project's core reviewers. > Traditionally it is something we've only addressed as needed or > desired by

Re: [openstack-dev] [oslo] UUID sentinel needs a home

> The compromise, using the patch as currently written [1], would entail > adding one line at the top of each test file: > > uuids = uuidsentinel.UUIDSentinels() > > ...as seen (more or less) at [2]. The subtle difference being that this > `uuids` wouldn't share a namespace across the whole

Re: [openstack-dev] [nova] Rocky blueprint burndown chart

On 8/15/2018 3:47 PM, melanie witt wrote: I think part of the miss on the number of approvals might be because we extended the spec freeze date to milestone r-2 because of runways, thinking that if we completed enough things, we could approve more things. We didn't predict that accurately but

Re: [openstack-dev] [oslo] UUID sentinel needs a home

On 08/23/2018 12:25 PM, Doug Hellmann wrote: Excerpts from Eric Fried's message of 2018-08-23 09:51:21 -0500: Do you mean an actual fixture, that would be used like: class MyTestCase(testtools.TestCase): def setUp(self): self.uuids =

Re: [openstack-dev] [oslo] UUID sentinel needs a home

On Thu, 23 Aug 2018, Dan Smith wrote: ...and it doesn't work like mock.sentinel does, which is part of the value. I really think we should put this wherever it needs to be so that it can continue to be as useful as is is today. Even if that means just copying it into another project -- it's not

Re: [openstack-dev] [nova][vmware] need help triaging a vmware driver bug

On Fri, 17 Aug 2018 10:50:30 +0300, Radoslav Gerganov wrote: Hi, On 17.08.2018 04:10, melanie witt wrote: Can anyone help triage this bug? I have requested more info from the person who submitted this and provided some tips how to correlate nova-compute logs to vCenter logs in order to

Re: [openstack-dev] [release] Release countdown for week R-0, August 27 - 31

> > > > We are still missing releases for the following tempest plugins. Some are > > pending getting pypi and release jobs set up, but please try to prioritize > > getting these done as soon as possible. > > > > barbican-tempest-plugin > > blazar-tempest-plugin > >

[openstack-dev] neutron-fwaas 13.0.0.0rc2 (rocky)

Hello everyone, A new release candidate for neutron-fwaas for the end of the Rocky cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/neutron-fwaas/ Unless release-critical issues are found that warrant a release candidate respin, this candidate

Re: [openstack-dev] [release] Release countdown for week R-0, August 27 - 31

On Thu, Aug 23, 2018 at 10:12 AM, Sean McGinnis wrote: > This is the final countdown email for the Rocky development cycle. Thanks to > everyone involved in the Rocky release! > > Development Focus > - > > Teams attending the PTG should be preparing for those discussions and >

Re: [openstack-dev] [ironic][bifrost][sushy][ironic-inspector][ironic-ui][virtualbmc] sub-project/repository core reviewer changes

+1 On Thu, 23 Aug 2018, 20:43 Jim Rollenhagen, wrote: > ++ > > > // jim > > On Thu, Aug 23, 2018 at 2:24 PM, Julia Kreger > wrote: > >> Greetings everyone! >> >> In our team meeting this week we stumbled across the subject of >> promoting contributors to be sub-project's core reviewers. >>

Re: [openstack-dev] [Cyborg] Zoom URL for Aug 29 meeting

Please use this invite instead, because it does not have the time limits of the old one (updated in  Cyborg wiki as well). Time: Aug 29, 2018 10:00 AM Eastern Time (US and Canada) Join from PC, Mac, Linux, iOS or Android: *https://zoom.us/j/395326369* Or iPhone one-tap :     US:

[openstack-dev] Regarding cache-based cross-VM side channel attacks in OpenStack

Dear Sir, I would like to know, whether cache-based cross-VM side channel attacks are possible in OpenStack VM or not ? If the answer of above question is no, then what are the mechanisms employed in OpenStack to prevent or to mitigate such types of security threats? I'm looking forward to

[openstack-dev] [community][Rocky] Community Meeting: Rocky + project updates

Hi all, Updated meeting information below for the OpenStack Community Meeting on August 30 at 3pm UTC. We’ll cover what’s new in the Rocky release, hear updates from the Airship, Kata Containers, StarlingX and Zuul projects, and get a preview of the Berlin Summit. Hope you can join us, but if

[openstack-dev] sahara 9.0.0.0rc2 (rocky)

Hello everyone, A new release candidate for sahara for the end of the Rocky cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/sahara/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally

[openstack-dev] sahara-dashboard 9.0.0.0rc2 (rocky)

Hello everyone, A new release candidate for sahara-dashboard for the end of the Rocky cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/sahara-dashboard/ Unless release-critical issues are found that warrant a release candidate respin, this

Re: [openstack-dev] [neutron][api][grapql] Proof of Concept

On 24/08/18 04:58, Slawomir Kaplonski wrote: Hi Miguel, I’m not sure but maybe You were looking for those patches: https://review.openstack.org/#/q/project:openstack/neutron+branch:feature/graphql Yes that's the one, it's under Tristan Cacqueray name as he helped getting started.

Re: [openstack-dev] [barbican][oslo][release][requirements] FFE request for castellan

On 18-08-22 23:06:36, Ade Lee wrote: > Thanks guys, > > Sorry - it was not clear to me if I was supposed to do anything > further. It seems like the requirements team has approved the FFE and > the release has merged. Is there anything further I need to do? > > Thanks, > Ade > > On Tue,

[openstack-dev] [magnum] [magnum-ui] show certificate button bug requesting reviews

Hello, Requesting reviews from the magnum-ui core team for https://review.openstack.org/#/c/595245/ I'm hoping that we could make quick due of this and be able to backport it to the stable/rocky release, would be ideal to backport it for stable/queens as well. Best regards Tobias

Re: [openstack-dev] Redis licensing terms changes

Jimmy McArthur wrote: Hmm... http://antirez.com/news/120 Today a page about the new Creative Common license in the Redis Labs web site was interpreted as if Redis itself switched license. This is not the case, Redis is, and will remain, BSD licensed. However in the fake news era my attempts

[openstack-dev] [Cyborg] Zoom URL for Aug 29 meeting

For the August 29 weekly meeting [1], the main agenda is the discussion of Cyborg device/data models. We will use this meeting invite to present slides: Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/189707867 Or iPhone one-tap :     US: +16465588665,,189707867#  or

Re: [openstack-dev] [nova][cinder] Disabling nova volume-update (aka swap volume; aka cinder live migration)

On 22/08, Matthew Booth wrote: > On Wed, 22 Aug 2018 at 10:47, Gorka Eguileor wrote: > > > > On 20/08, Matthew Booth wrote: > > > For those who aren't familiar with it, nova's volume-update (also > > > called swap volume by nova devs) is the nova part of the > > > implementation of cinder's live

Re: [openstack-dev] [monasca][goal][python3] monasca's zuul migration is only partially complete

Reply in-line. On 23/08/18 00:32, Doug Hellmann wrote: Monasca team, It looks like you have self-proposed some, but not all, of the patches to import the zuul settings into monasca repositories. I found these:

Re: [openstack-dev] [all] [nova] [placement] placement below or beside compute after extraction?

melanie witt wrote: [...] I have been trying to explain why over several replies to this thread. Fracturing a group is not something anyone does to foster cooperation and shared priorities and goals. [...] I would argue that the group is already fractured, otherwise we would not even be

Re: [openstack-dev] [oslo] UUID sentinel needs a home

+1 for oslotest Jay Pipes 于2018年8月23日周四 上午11:24写道： > > On Wed, Aug 22, 2018, 10:13 AM Eric Fried wrote: > >> For some time, nova has been using uuidsentinel [1] which conveniently >> allows you to get a random UUID in a single LOC with a readable name >> that's the same every time you

Re: [openstack-dev] [nova][cinder] Disabling nova volume-update (aka swap volume; aka cinder live migration)

On 22/08, Sean McGinnis wrote: > > > > The solution is conceptually simple. We add a new API microversion in > > Cinder that adds and optional parameter called "generic_keep_source" > > (defaults to False) to both migrate and retype operations. > > > > This means that if the driver optimized

Re: [openstack-dev] [monasca][goal][python3] monasca's zuul migration is only partially complete

Excerpts from Doug Szumski's message of 2018-08-23 09:53:35 +0100: > Thanks Doug, we had a discussion and we agreed that the best way to > proceed is for you to submit your patches and we will carefully review them. I proposed those patches this morning. With the aid of your exemplary

Re: [openstack-dev] [oslo] UUID sentinel needs a home

On 08/23/2018 08:06 AM, Doug Hellmann wrote: Excerpts from Davanum Srinivas (dims)'s message of 2018-08-23 06:46:38 -0400: Where exactly Eric? I can't seem to find the import: http://codesearch.openstack.org/?q=(from%7Cimport).*oslotest=nope==oslo.utils -- dims oslo.utils depends on

Re: [openstack-dev] [magnum] supported OS images and magnum spawn failures for Swarm and Kubernetes

Thanks for all of your help everyone, I've been busy with other thing but was able to pick up where I left regarding Magnum. After fixing some issues I have been able to provision a working Kubernetes cluster. I'm still having issues with getting Docker Swarm working, I've tried with both

Re: [openstack-dev] [oslo] UUID sentinel needs a home

Where exactly Eric? I can't seem to find the import: http://codesearch.openstack.org/?q=(from%7Cimport).*oslotest=nope==oslo.utils -- dims On Wed, Aug 22, 2018 at 11:24 PM Jay Pipes wrote: > > On Wed, Aug 22, 2018, 10:13 AM Eric Fried wrote: > >> For some time, nova has been using

[openstack-dev] [tripleo][nova] nova rx_queue_size tx_queue_size config options breaks booting vm with SR-IOV

Hi all, Recent change in tripleo [1] configure nova rx_queue_size tx_queue_size config by default. It seem that this config option breaks booting vm with SR-IOV. See [2] The issues is because of this code [3] which configure virtio queue size if the in the interface xml the driver is vhost or

Re: [openstack-dev] [nova][cinder][neutron] Cross-cell cold migration

On 22/08, Matt Riedemann wrote: > Hi everyone, > > I have started an etherpad for cells topics at the Stein PTG [1]. The main > issue in there right now is dealing with cross-cell cold migration in nova. > > At a high level, I am going off these requirements: > > * Cells can shard across flavors

[openstack-dev] [neutron][ovs][TripleO] Enabling IPv6 address for tunnel endpoints

Hi I understand that currently tunnel endpoints are supported to be on IPv4 address only. I have a requirement for them to be on IPv6 endpoints as well with OpenDaylight. So the deployment will have IPv6 addresses for tenant network. I know OVS now supports IPv6 endpoints. I want to know if

Re: [openstack-dev] [oslo] UUID sentinel needs a home

Excerpts from Davanum Srinivas (dims)'s message of 2018-08-23 06:46:38 -0400: > Where exactly Eric? I can't seem to find the import: > > http://codesearch.openstack.org/?q=(from%7Cimport).*oslotest=nope==oslo.utils > > -- dims oslo.utils depends on oslotest via test-requirements.txt and

Re: [openstack-dev] [tripleo][nova] nova rx_queue_size tx_queue_size config options breaks booting vm with SR-IOV

On 8/23/2018 6:34 AM, Moshe Levi wrote: Recent change in tripleo [1] configure nova rx_queue_size tx_queue_size config by default. It seem that this config option breaks booting vm with SR-IOV. See [2] The issues is because of this code [3] which configure virtio queue size if the in the

Re: [openstack-dev] [tripleo][nova] nova rx_queue_size tx_queue_size config options breaks booting vm with SR-IOV

On 8/23/2018 7:10 AM, Matt Riedemann wrote: On 8/23/2018 6:34 AM, Moshe Levi wrote: Recent change in tripleo [1] configure nova rx_queue_size tx_queue_size config by default. It seem that this config option breaks booting vm with SR-IOV. See [2] The issues is because of this code [3] which

[openstack-dev] [tc] Technical Committee status for 23 August

This is the weekly summary of work being done by the Technical Committee members. The full list of active items is managed in the wiki: https://wiki.openstack.org/wiki/Technical_Committee_Tracker We also track TC objectives for the cycle using StoryBoard at: