Re: [openstack-dev] [all][requirements] uncapping eventlet

On Mon, Apr 09, 2018 at 09:58:28AM -0400, Doug Hellmann wrote: > Now that projects don't have to match the global requirements list > entries exactly we should be able to remove caps from within the > projects and keep caps in the global list for cases like this where we > know we frequently

Re: [openstack-dev] [cyborg] Promote Li Liu as new core reviewer

+1 On Mon, Apr 9, 2018 at 3:13 PM, Nadathur, Sundar wrote: > Agreed! +1 > > Regards, > Sundar > > Hi Team, > > This is an email for my nomination of adding Li Liu to the core reviewer > team. Li Liu has been instrumental in the resource provider data model >

Re: [openstack-dev] [nova] Changes toComputeVirtAPI.wait_for_instance_event

Could you please help to share whether this kind of event is sent by neutron-server or neutron agent ? I searched neutron code from [1][2] this means the agent itself need tell neutron server the device(VIF) is up then neutron server will send notification to nova through REST API and in turn

Re: [openstack-dev] [zun] zun-api error

Hi Hongbin Lu, After I run the etcd service up and tried to create container I see the below error and my container is in error state Could you please share me if I need to change any configuration in neutron for docker kuryer ckercfg'] find_config_file

[openstack-dev] [ironic] this week's priorities and subteam reports

Hi, We are glad to present this week's priorities and subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. This Week's Priorities (as of the weekly ironic meeting) Weekly priorities

Re: [openstack-dev] [all][requirements] uncapping eventlet

On 04/09/2018 01:12 PM, Ben Nemec wrote: On 04/06/2018 04:02 AM, Jens Harbott wrote: 2018-04-05 19:26 GMT+00:00 Matthew Thode : On 18-04-05 20:11:04, Graham Hayes wrote: On 05/04/18 16:47, Matthew Thode wrote: eventlet-0.22.1 has been out for a while now, we

Re: [openstack-dev] [Openstack-operators] RFC: Next minimum libvirt / QEMU versions for "Stein" release

On 4/9/2018 4:58 AM, Kashyap Chamarthy wrote: Keep in mind that Matt has a tendency to sometimes unfairly over-simplify others views;-). More seriously, c'mon Matt; I went out of my way to spend time learning about Debian's packaging structure and trying to get the details right by talking to

Re: [openstack-dev] PBR and Pipfile

On 04/08/2018 04:10 AM, Gaetan wrote: Hello OpenStack dev community, I am currently working on the support of Pipfile for PBR ([1]), and I also follow actively the work on pipenv, which is now in officially supported by PyPA. Awesome - welcome! This is a fun topic ... There have been

Re: [openstack-dev] [cinder][nova] about re-image the volume

On 4/9/2018 1:00 PM, Duncan Thomas wrote: Hopefully this flow means we can do rebuild root filesystem from snapshot/backup too? It seems rather artificially limiting to only do restore-from-image. I'd expect restore-from-snap to be a more common use case, personally. Hmm, now you've got me

Re: [openstack-dev] [horizon][xstatic]How to handle xstatic if upstream files are modified

Hi, Xinni, I absolutely agree with Radomir. We should keep xstatic files without modifications. We don't know if they are used outside of OpenStack or not, so they should be the same as NPM packages Regards, Ivan Kolodyazhny, http://blog.e0ne.info/ On Mon, Apr 9, 2018 at 12:32 PM, Radomir

Re: [openstack-dev] [cinder][nova] about re-image the volume

On Mon, Apr 09, 2018 at 07:00:56PM +0100, Duncan Thomas wrote: > Hopefully this flow means we can do rebuild root filesystem from > snapshot/backup too? It seems rather artificially limiting to only do > restore-from-image. I'd expect restore-from-snap to be a more common > use case, personally. >

Re: [openstack-dev] [cyborg] Promote Li Liu as new core reviewer

Agreed! +1 Regards, Sundar Hi Team, This is an email for my nomination of adding Li Liu to the core reviewer team. Li Liu has been instrumental in the resource provider data model implementation for Cyborg during Queens release, as well as metadata standardization and programming design

Re: [openstack-dev] [all][requirements] uncapping eventlet

On 04/06/2018 04:02 AM, Jens Harbott wrote: 2018-04-05 19:26 GMT+00:00 Matthew Thode : On 18-04-05 20:11:04, Graham Hayes wrote: On 05/04/18 16:47, Matthew Thode wrote: eventlet-0.22.1 has been out for a while now, we should try and use it. Going to be fun times.

Re: [openstack-dev] [cinder][nova] about re-image the volume

Hopefully this flow means we can do rebuild root filesystem from snapshot/backup too? It seems rather artificially limiting to only do restore-from-image. I'd expect restore-from-snap to be a more common use case, personally. On 9 April 2018 at 09:51, Gorka Eguileor wrote: >

[openstack-dev] [nova] Changes to ComputeVirtAPI.wait_for_instance_event

As part of a bug fix [1], the internal ComputeVirtAPI.wait_for_instance_event interface is changing to no longer accept event names that are strings, and will now require the (name, tag) tuple form which all of the in-tree virt drivers are already using. If you have an out of tree driver

Re: [openstack-dev] Vancouver Forum - Post your selected topics now

Csatari, Gergely (Nokia - HU/Budapest) wrote: > There are two lists of etherpads for forum brainstorming in > https://wiki.openstack.org/wiki/Forum/Vancouver2018 and there is > http://forumtopics.openstack.org/ . > > Is my understanding correct, that ultimatelly all ideas should go to >

Re: [openstack-dev] [all] [api] Re-Reminder on the state of WSME

On 04/09/2018 07:22 AM, Chris Dent wrote: A little over two years ago I sent a reminder that WSME is not being actively maintained: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088658.html Today I was reminded of this becasue a random (typo-related) patchset

[openstack-dev] [nova] Rocky forum topics brainstorming

Hey everyone, Let's collect forum topic brainstorming ideas for the Forum sessions in Vancouver in this etherpad [0]. Once we've brainstormed, we'll select and submit our topic proposals for consideration at the end of this week. The deadline for submissions is Sunday April 15. Thanks,

Re: [openstack-dev] [all] Changes to Zuul role checkouts

If you're not familiar with the "override-checkout" configuration, you can find the documentation about it here [1] and some example usage here [2]. [1]: https://zuul-ci.org/docs/zuul/user/config.html#attr-job.override-checkout [2]: http://codesearch.openstack.org/?q=override-checkout David

[openstack-dev] [all] Changes to Zuul role checkouts

Hi, We recently fixed a subtle but important bug related to how Zuul checks out repositories it uses to find Ansible roles for jobs. This may result in a behavior change, or even an error, for jobs which use roles defined in projects with multiple branches. Previously, Zuul would (with some

Re: [openstack-dev] [barbican][nova-powervm][pyghmi][solum][trove] Switching to cryptography from pycrypto

On Mon, Apr 2, 2018 at 8:26 AM, Jim Rollenhagen wrote: > On Sat, Mar 31, 2018 at 7:24 PM, Matthew Thode > wrote: > >> Here's the current status. I'd like to ask the projects what's keeping >> them from removing pycrypto in facor of a

Re: [openstack-dev] [nova] [placement] placement update 18-14

On Fri, 6 Apr 2018, Chris Dent wrote: * Eric and I discussed earlier in the week that it might be a good time to start an #openstack-placement IRC channel, for two main reasons: break things up so as to limit the crosstalk in the often very busy #openstack-nova channel and to lend a bit of

Re: [openstack-dev] [cinder][nova] about re-image the volume

On 4/9/2018 3:51 AM, Gorka Eguileor wrote: As I see it, the process would look something like this: - Nova detaches volume using OS-Brick - Nova calls Cinder re-image passing the node's info (like we do when attaching a new volume) - Cinder would: - Ensure only that node is connected to

Re: [openstack-dev] [neutron] [OVN] Tempest API / Scenario tests and OVN metadata

Hi, > Another idea is to modify test that it will: > 1. Check how many ports are in tenant, > 2. Set quota to actual number of ports + 1 instead of hardcoded 1 as it is > now, > 3. Try to add 2 ports - exactly as it is now, > > I think that this should be still backend agnostic and should fix

Re: [openstack-dev] [oslo.db] innodb OPTIMIZE TABLE ?

On Mon, Apr 9, 2018 at 5:53 AM, Gorka Eguileor wrote: > On 06/04, Michael Bayer wrote: >> On Wed, Apr 4, 2018 at 5:00 AM, Gorka Eguileor wrote: >> > On 03/04, Jay Pipes wrote: >> >> On 04/03/2018 11:07 AM, Michael Bayer wrote: >> >> > The MySQL / MariaDB

Re: [openstack-dev] [all][requirements] uncapping eventlet

Excerpts from Tony Breeds's message of 2018-04-09 13:39:30 +1000: > On Fri, Apr 06, 2018 at 09:41:07AM -0700, Clark Boylan wrote: > > > My understanding of our use of upper constraints was that this should > > (almost) always be the case for (almost) all dependencies. We should > > rely on

Re: [openstack-dev] [nova] [placement] placement update 18-14

On Fri, Apr 6, 2018 at 2:54 PM, Chris Dent wrote: > > This is "contract" style update. New stuff will not be added to the > lists. > > # Most Important > > There doesn't appear to be anything new with regard to most > important. That which was important remains important.

[openstack-dev] [keystone] Rocky forum topics

Hey all, I've created an etherpad [0] to collect ideas/proposals for forum sessions in Vancouver. Please take a look and add anything that you think we should propose as a forum session. The deadline for submissions is this Sunday. Thanks, Lance [0]

Re: [openstack-dev] [oslo.db] innodb OPTIMIZE TABLE ?

On Tue, Apr 03 2018, Jay Pipes wrote: > Possibly, though it's questionable to use MySQL/InnoDB for storing transient > data that is deleted often like ceilometer samples and keystone tokens. A much > better solution is to use RDBMS partitioning so you can simply ALTER TABLE .. > DROP PARTITION

[openstack-dev] [neutron][horizon][l2gw] Unable to create a floating IP

Hi, From Queens onwards we have a issue with horizon and L2GW. We are unable to create a floating IP. This does not occur when using the CLI only via horizon. The error received is ‘Error: User does not have admin privileges: Cannot GET resource for non admin tenant. Neutron server returns

Re: [openstack-dev] Vancouver Forum - Post your selected topics now

Hi, There are two lists of etherpads for forum brainstorming in https://wiki.openstack.org/wiki/Forum/Vancouver2018 and there is http://forumtopics.openstack.org/ . Is my understanding correct, that ultimatelly all ideas should go to http://forumtopics.openstack.org/ ? Thanks, Gerg0

[openstack-dev] [all] [api] Re-Reminder on the state of WSME

A little over two years ago I sent a reminder that WSME is not being actively maintained: http://lists.openstack.org/pipermail/openstack-dev/2016-March/088658.html Today I was reminded of this becasue a random (typo-related) patchset demonstrated that the tests were no longer passing and

[openstack-dev] Vancouver Forum - Post your selected topics now

Hi everyone, You've been actively brainstorming ideas of topics for discussion at the "Forum" at the Vancouver OpenStack Summit. Now it's time to select which ones you want to propose, and file them at forumtopics.openstack.org ! The topic submission website will be open until EOD on Sunday,

[openstack-dev] Todays Office Hour Time Change

Hey all, I have moved the office hour today from 16:00 UTC to 15:00 UTC. If there is demand we could make it a 2 hour slot or move it back. I wasn't able to make it for 16:00 UTC today and it will often be tricky for me. I think one of the biggest advantages to doing office hours is that we can

Re: [openstack-dev] [Openstack-operators] RFC: Next minimum libvirt / QEMU versions for "Stein" release

On Fri, Apr 06, 2018 at 12:12:31PM -0500, Matt Riedemann wrote: > On 4/6/2018 12:07 PM, Kashyap Chamarthy wrote: > > FWIW, I'd suggest so, if it's not too much maintenance. It'll just > > spare you additional bug reports in that area, and the overall default > > experience when dealing with CPU

Re: [openstack-dev] [oslo.db] innodb OPTIMIZE TABLE ?

On 06/04, Michael Bayer wrote: > On Wed, Apr 4, 2018 at 5:00 AM, Gorka Eguileor wrote: > > On 03/04, Jay Pipes wrote: > >> On 04/03/2018 11:07 AM, Michael Bayer wrote: > >> > The MySQL / MariaDB variants we use nowadays default to > >> > innodb_file_per_table=ON and we also

Re: [openstack-dev] [horizon][xstatic]How to handle xstatic if upstream files are modified

The whole idea about xstatic files is that they are generic, not specific to Horizon or OpenStack, usable by other projects that need those static files. In fact, at the time we started using xstatic, it was being used by the MoinMoin wiki project (which is now dead, sadly). The modifications you

Re: [openstack-dev] [cinder][nova] about re-image the volume

On 06/04, Matt Riedemann wrote: > On 4/6/2018 5:09 AM, Matthew Booth wrote: > > I think you're talking at cross purposes here: this won't require a > > swap volume. Apart from anything else, swap volume only works on an > > attached volume, and as previously discussed Nova will detach and > >

Re: [openstack-dev] [kolla] [tripleo] On moving start scripts out of Kolla images

On Sat, Apr 7, 2018 at 11:11 AM, Jeffrey Zhang wrote: > +1 for kolla-api > > Migrate all scripts from kolla(image) to kolla-ansible, will make image hard > to use by > downstream. Martin explain this clearly. we need some API to make images > more easy to use. > For the

[openstack-dev] [neutron] Bug deputy report

Hello everyone, I was on bug deputy between 2018/04/02 and 2018/04/09. I am sending a short summary of the bugs reported during this period. We do not have many bug reported this week. https://bugs.launchpad.net/neutron/+bug/1760047 - Confirmed but the importance is not yet decided. It is

Re: [openstack-dev] [neutron] [OVN] Tempest API / Scenario tests and OVN metadata

I don't necessarily agree that rewriting test is the solution here. May be for some extreme cases that could be fine, but from the maintenance point of view doesn't sound very practical IMHO. In some cases it can be just a parametrization of tests as they are, or simply accounting for a bit of