[openstack-dev] [nova][osc] Documenting compute API microversion gaps in OSC

I've started an etherpad [1] to identify the compute API microversion gaps in python-openstackclient. It's a small start right now so I would appreciate some help on this, even just a few people looking at a couple of these per day would get it done quickly. Not all compute API

[openstack-dev] [glance] bug smash today

Today (Friday, 8 June UTC time) is our Rocky-2 bug smash. Hang out in #openstack-glance and keep the etherpad updated: https://etherpad.openstack.org/p/glance-rocky-bug-smash cheers, brian __ OpenStack Development Mailing

Re: [openstack-dev] [nova] increasing the number of allowed volumes attached per instance > 26

On Thu, Jun 7, 2018, 4:17 PM Matt Riedemann wrote: > On 6/7/2018 1:54 PM, Jay Pipes wrote: > > > > If Cinder tracks volume attachments as consumable resources, then this > > would be my preference. > > Cinder does: > > https://developer.openstack.org/api-ref/block-storage/v3/#attachments > >

Re: [openstack-dev] [TC] Stein Goal Selection

On 6/7/2018 3:25 PM, Kendall Nelson wrote: I know it doesn't fit the shiny user facing docket that was discussed at the Forum, but I do think its time we make migration official in some capacity as a release goal or some other way. Having migrated Ironic and having TripleO on the schedule for

[openstack-dev] [infra][all] Upcoming Zuul behavior change for files and irrelevant-files

Hi, Earlier[1][2], we discussed proposals to make files and irrelevant-files easier to use -- particularly ways to make them overridable. We settled on an approach, and it is now implemented. We plan on upgrading OpenStack's Zuul to the new behavior on Monday, June 11, 2018. To summarize the

Re: [openstack-dev] [TC] Stein Goal Selection

On 2018-06-07 14:19:41 -0700 (-0700), Clark Boylan wrote: [...] > We stopped following latest Ubuntu when they dropped non LTS > support to 9 months. What we do have are suse tumbleweed images > which should get us brand new everything in a rolling fashion. If > people are interested in this type

Re: [openstack-dev] [tc][ptl][python3][help-wanted] starting work on "python 3 first" transition

Excerpts from Thomas Goirand's message of 2018-06-07 22:17:11 +0200: > On 06/06/2018 10:04 PM, Doug Hellmann wrote: > > I have started submitting a series of patches to fix up the tox.ini > > settings for projects as a step towards running "python3 first" > > [1]. The point of doing this now is to

Re: [openstack-dev] [TC] Stein Goal Selection

On Thu, Jun 7, 2018, at 1:53 PM, Thomas Goirand wrote: > On 06/04/2018 08:59 PM, Ivan Kolodyazhny wrote: > > I hope we'll have Ubuntu 18.04 LTS on our gates for this activity soon. > > It becomes > > important not only for developers but for operators and vendors too. > > By the time the project

Re: [openstack-dev] [nova] increasing the number of allowed volumes attached per instance > 26

On 6/7/2018 1:54 PM, Jay Pipes wrote: If Cinder tracks volume attachments as consumable resources, then this would be my preference. Cinder does: https://developer.openstack.org/api-ref/block-storage/v3/#attachments However, there is no limit in Cinder on those as far as I know. --

Re: [openstack-dev] [TC] Stein Goal Selection

On 06/04/2018 08:59 PM, Ivan Kolodyazhny wrote: > I hope we'll have Ubuntu 18.04 LTS on our gates for this activity soon. > It becomes > important not only for developers but for operators and vendors too. By the time the project will be gating on Python 3.6, most likely there's going to be 3.7

Re: [openstack-dev] [TC] Stein Goal Selection

Hello :) I think that these two goals definitely fit the criteria we discussed in Vancouver during the S Release Goal Forum Session. I know Storyboard Migration was also mentioned after I had to dip out to another session so I wanted to follow up on that. I know it doesn't fit the shiny user

Re: [openstack-dev] [tc][ptl][python3][help-wanted] starting work on "python 3 first" transition

On 06/06/2018 10:14 PM, Sean McGinnis wrote: > On 06/06/2018 03:04 PM, Doug Hellmann wrote: >> I have started submitting a series of patches to fix up the tox.ini >> settings for projects as a step towards running "python3 first" >> [1]. The point of doing this now is to give teams a head start on

Re: [openstack-dev] [tc][ptl][python3][help-wanted] starting work on "python 3 first" transition

On 06/06/2018 10:04 PM, Doug Hellmann wrote: > I have started submitting a series of patches to fix up the tox.ini > settings for projects as a step towards running "python3 first" > [1]. The point of doing this now is to give teams a head start on > understanding the work involved as we consider

Re: [openstack-dev] [nova] increasing the number of allowed volumes attached per instance > 26

On 06/07/2018 12:07 PM, Matt Riedemann wrote: On 6/7/2018 12:56 PM, melanie witt wrote: C) Create a configurable API limit for maximum number of volumes to attach to a single instance that is either a quota or similar to a quota. Pros: lets operators opt-in to a maximum that works in their

Re: [openstack-dev] [nova] increasing the number of allowed volumes attached per instance > 26

On 06/07/2018 01:56 PM, melanie witt wrote: Hello Stackers, Recently, we've received interest about increasing the maximum number of allowed volumes to attach to a single instance > 26. The limit of 26 is because of a historical limitation in libvirt (if I remember correctly) and is no

[openstack-dev] [tc][ptl] team, SIG, and working group liaisons

As we discussed in today's office hours, I have set up some space in the wiki for us to track which TC members are volunteering to act as liaison to the teams and other groups within the community to ensure they have the assistance and support they need from the TC.

[openstack-dev] [RDO] Rocky Milestone 2 RDO Test Days June 14-15

Who’s up for a rematch?- Rocky Milestone 2 is here and we’re ready to rumble! Join RDO [0] on June 14 & 15 for an awesome time of taking down bugs and fighting errors in the most recent release [1].- We certainly won’t be pulling any punches. Want to get in on the action? We’re looking for

Re: [openstack-dev] [nova] increasing the number of allowed volumes attached per instance > 26

+operators (I forgot) On 6/7/2018 1:07 PM, Matt Riedemann wrote: On 6/7/2018 12:56 PM, melanie witt wrote: Recently, we've received interest about increasing the maximum number of allowed volumes to attach to a single instance > 26. The limit of 26 is because of a historical limitation in

Re: [openstack-dev] [nova] increasing the number of allowed volumes attached per instance > 26

On 6/7/2018 12:56 PM, melanie witt wrote: Recently, we've received interest about increasing the maximum number of allowed volumes to attach to a single instance > 26. The limit of 26 is because of a historical limitation in libvirt (if I remember correctly) and is no longer limited at the

[openstack-dev] [nova] increasing the number of allowed volumes attached per instance > 26

Hello Stackers, Recently, we've received interest about increasing the maximum number of allowed volumes to attach to a single instance > 26. The limit of 26 is because of a historical limitation in libvirt (if I remember correctly) and is no longer limited at the libvirt level in the present

[openstack-dev] [release] Release countdown for week R-11, June 11-15

Hey everyone, here is this week's countdown email. Development Focus - Teams should be focused on implementing planned work for the cycle. It is also a good time to review those plans and reprioritize anything if needed based on the what progress has been made and what looks

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

Greetings OpenStack community, Today's meeting was brief, covering only 1 major topic. The main topic for the SIG today was the migration of bug tracking from Launchpad to StoryBoard[7]. No firm plans were made to migrate yet, but the group agreed that this migration would be positive from a

[openstack-dev] Berlin Summit CFP Deadline July 17

Hi everyone, The Call for Presentations is open for the Berlin Summit , November 13-15. The deadline to submit your presentation has been extended to July 17. At the Vancouver

Re: [openstack-dev] [kolla][vote] Nominating Steve Noyes for kolla-cli core reviewer

The vote has passed, with 12 people voting, and them all being +1. Welcome to the core kolla-cli reviewer team Steve. I have made the appropriate gerrit changes so you now have "the power". -- Borne On 05/31/2018 10:02 AM, Borne Mace wrote: Greetings all, I would like to propose the

Re: [openstack-dev] [cinder] Removing Support for Drivers with Failing CI's ...

Peter, Thanks for getting that fixed.  The associated patch has been removed so we should be good now. Jay On 6/7/2018 9:15 AM, Peter Penchev wrote: On Mon, Jun 04, 2018 at 02:40:09PM -0500, Sean McGinnis wrote: Our CI has been chugging along since June 2nd (not really related to the

Re: [openstack-dev] [TC] Stein Goal Selection

On 06/07/2018 09:39 AM, Matt Riedemann wrote: On 6/5/2018 9:14 AM, Doug Hellmann wrote: In the past when we've had questions about how broadly a goal is going to affect projects, we did a little data collection work up front. Maybe that's the next step for this one? Does someone want to

Re: [openstack-dev] [TC] Stein Goal Selection

On 6/5/2018 9:14 AM, Doug Hellmann wrote: In the past when we've had questions about how broadly a goal is going to affect projects, we did a little data collection work up front. Maybe that's the next step for this one? Does someone want to volunteer to go around and talk to some of the project

Re: [openstack-dev] [cinder] Removing Support for Drivers with Failing CI's ...

On Mon, Jun 04, 2018 at 02:40:09PM -0500, Sean McGinnis wrote: > > > > Our CI has been chugging along since June 2nd (not really related to > > the timing of your e-mail, it just so happened that we fixed another > > small problem there). You can see the logs at > > > >

[openstack-dev] [nova] Need feedback on spec for handling down cells in the API

We have a nova spec [1] which is at the point that it needs some API user (and operator) feedback on what nova API should be doing when listing servers and there are down cells (unable to reach the cell DB or it times out). tl;dr: the spec proposes to return "shell" instances which have the

Re: [openstack-dev] [tc][ptl][python3][help-wanted] starting work on "python 3 first" transition

On Wed, 2018-06-06 at 16:04 -0400, Doug Hellmann wrote: > I have started submitting a series of patches to fix up the tox.ini > settings for projects as a step towards running "python3 first" > [1]. The point of doing this now is to give teams a head start on > understanding the work involved as

[openstack-dev] [cinder] Enabling tempest test for in-use volume extending

Hi. Since Pike release, Cinder supports in-use volume extending [1]. By default, it assumes that every storage backend is able to perform this operation. Thus, the tempest test for this feature should be enabled by default. A patch was submitted to enable it [2]. Please note that, after this

Re: [openstack-dev] [Cyborg] [Nova] Cyborg traits

Sorry for delay in responding on this. Comments inline. On 05/29/2018 07:33 PM, Nadathur, Sundar wrote: Hi all,    The Cyborg/Nova scheduling spec [1] details what traits will be applied to the resource providers that represent devices like GPUs. Some of the traits referred to vendor names.

Re: [openstack-dev] [Edge-computing] [edge][glance][mixmatch]: Wiki of the possible architectures for image synchronisation

I had some additional questions/comments on the Image Synchronization Options ( https://wiki.openstack.org/wiki/Image_handling_in_edge_environment ): One Glance with multiple backends · In this scenario, are all Edge Clouds simply configured with the one central glance for its GLANCE

[openstack-dev] [designate] Meeting Times update

Hi All, We had talked about moving to a bi-weekly meeting, with alternating times, and I have updated the meetings repo [0] with some suggested times. Please speak up if these do not suit! - Graham 0 - https://review.openstack.org/#/c/573204/ signature.asc Description: OpenPGP digital

[openstack-dev] [packaging] Extended Maintenance and Distro LTS coordination

At the summit in Vancouver there were sessions discussing Extended Maintenance. The general focus was on keeping upstream branches open in extended maintenance mode after 18 months rather than EOLing them. If at some point fixes cannot land in a given project's branch, and there is no reasonable

[openstack-dev] [publiccloud-wg] Meeting this afternoon for Public Cloud WG

Hi folks, Time for a new meeting for the Public Cloud WG.  Agenda can be found at https://etherpad.openstack.org/p/publiccloud-wg See you all at IRC 1400 UTC in #openstack-publiccloud Cheers, Tobias -- Tobias Rydberg Senior Developer Twitter & IRC: tobberydberg www.citynetwork.eu |

Re: [openstack-dev] [edge][glance][mixmatch]: Wiki of the possible architectures for image synchronisation

Hi, I did some work ont he figures and realised, that I have some questions related to the alternative options: Multiple backends option: * What is the API between Glance and the Glance backends? * How is it possible to implement location aware synchronisation (synchronise images only

Re: [openstack-dev] [stable][networking-bgpvpn][infra] missing networking-odl repository / tox-siblings & tox_install.sh

Hi Előd, Thanks for looking into that. Summary: - we  removed networking-odl from required-projects of networking-bgpvpn because of a history of networking-odl changes breaking functional tests in networking-bgvpn (since networking-bgpvpn master declares networking-odl in requirements.txt ,

[openstack-dev] [I18n] IRC Office hours reminder: June 7th at 13:00-14:00 UTC

Hello all, I18n team previously had team meetings but decided to have office hours instead [1]. Please feel free to come to #openstack-i18n IRC channel and ask and/or discuss anything on translation, internationalization, and/or localization issues on projects. Although I18n PTL is now busy

Re: [openstack-dev] [kuryr][kuryr-kubernetes] Propose to support Kubernetes Network Custom Resource Definition De-facto Standard Version 1

On Thu, Jun 7, 2018 at 3:52 AM, Peng Liu wrote: > Cool. > I'll start to prepare a BP for this, so we can have more detailed > discussion. Great! > > On Wed, Jun 6, 2018 at 11:08 PM, Antoni Segura Puimedon > wrote: >> >> On Wed, Jun 6, 2018 at 2:37 PM, Irena Berezovsky >> wrote: >> > Sounds

Re: [openstack-dev] [Openstack-operators] [openstack-ansible][releases][governance] Change in OSA roles tagging

> Right, you can set the stable-branch-type field to 'tagless' (see > http://git.openstack.org/cgit/openstack/releases/tree/README.rst#n462) and > then set the branch location field to the SHA you want to use. Exactly what I thought. > If you would be ready to branch all of the roles at one

[openstack-dev] [oslo][nova] anyway to specify req-id in LOG.xxx

Due to bug [1] looks like the req-id of each request will be recorded in context and then LOG.xxx will use the context if not spcified per bug reported, the periodic task seems reuse the context of its previous action and lead to same req-id in the log quick oslo code check didn't provide too