Re: [openstack-dev] [neutron][stable] New release for Pike is overdue

I just +1ed Kuba's patch On Thu, Mar 15, 2018 at 10:49 AM, Jakub Libosvar wrote: > Thanks for notice. I sent a patch to request a new release: > https://review.openstack.org/#/c/553447/ > > Jakub > > On 15/03/2018 11:28, Jens Harbott wrote: > > The last neutron release for

Re: [openstack-dev] [neutron][stable] New release for Pike is overdue

Thanks for notice. I sent a patch to request a new release: https://review.openstack.org/#/c/553447/ Jakub On 15/03/2018 11:28, Jens Harbott wrote: > The last neutron release for Pike has been made in November, a lot of > bug fixes have made it into the stable/pike branch, can we please get > a

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

Greetings OpenStack community, A rousing good time at the API-SIG meeting today. We opened with some discussion on what might be missing from the Methods [7] section of the HTTP guidelines. At the PTG we had discussed that perhaps we needed more info on which methods were appropriate when.

[openstack-dev] Vancouver Summit Schedule now live!

The schedule is now live for the Vancouver Summit! Check out the 100+ sessions, demos, workshops and tutorials that will be featured at the Vancouver Summit, May 21-24. What’s New? As infrastructure has evolved, so has the Summit. In addition to OpenStack features and operations, you'll find

Re: [openstack-dev] [tripleo] TLS by default

On 03/15/2018 12:51 AM, Julia Kreger wrote: On Wed, Mar 14, 2018 at 4:52 AM, Dmitry Tantsur wrote: Just to clarify: only for public endpoints, right? I don't think e.g. ironic-python-agent can talk to self-signed certificates yet. For what it is worth, it is possible

Re: [openstack-dev] [Edge-computing] [FEMDC] Brainstorming regarding the Vancouver Forum

I have added a couple of points and links. Paul-André -- On 3/15/18, 9:46 AM, "lebre.adr...@free.fr" wrote: Hi all, I just created an FEMDC etherpad following the Melvin's email regarding the next Forum in Vancouver. Please do not hesitate to

[openstack-dev] [docs] Retiring openstack-doc-specs-core

Hi all, For historical reasons, the docs team maintains a separate core group for the docs-specs repo. With the new docs processes in place, we agreed at the Rocky PTG to further simplify the docs group setup and retire openstack-doc-specs-core by removing the existing members and adding

Re: [openstack-dev] Vancouver Summit Schedule now live!

On 3/15/2018 11:05 AM, Kendall Waters wrote: The schedule is organized by new tracks according to use cases: private & hybrid cloud, public cloud, container infrastructure, CI / CD, edge computing, HPC / GPUs / AI, and telecom / NFV. You can sort within the schedule to find sessions and

Re: [openstack-dev] Vancouver Summit Schedule now live!

On 3/15/2018 1:14 PM, Matt Riedemann wrote: On 3/15/2018 11:05 AM, Kendall Waters wrote: The schedule is organized by new tracks according to use cases: private & hybrid cloud, public cloud, container infrastructure, CI / CD, edge computing, HPC / GPUs / AI, and telecom / NFV. You can sort

Re: [openstack-dev] [kolla][vote] core nomination for caoyuan

+1 On Thu, Mar 15, 2018 at 5:40 AM Martin André wrote: > +1 > > On Tue, Mar 13, 2018 at 5:50 PM, Swapnil Kulkarni > wrote: > > On Mon, Mar 12, 2018 at 7:36 AM, Jeffrey Zhang > wrote: > >> Kolla core reviewer team, > >> > >> It

Re: [openstack-dev] [nova] about rebuild instance booted from volume

On 03/15/2018 09:46 AM, Dan Smith wrote: Rather than overload delete_on_termination, could another flag like delete_on_rebuild be added? Isn't delete_on_termination already the field we want? To me, that field means "nova owns this". If that is true, then we should be able to re-image the

Re: [openstack-dev] [nova] about rebuild instance booted from volume

Deleting all snapshots would seem dangerous though... 1. I want to reset my instance to how it was before 2. I'll just do a snapshot in case I need any data in the future 3. rebuild 4. oops Tim -Original Message- From: Ben Nemec Reply-To: "OpenStack Development

Re: [openstack-dev] Vancouver Summit Schedule now live!

On Thu, 15 Mar 2018 19:53:16 +, Kendall Nelson wrote: Jay's correct the Updates are happening. Project Updates are their own thing separate from the standard submission. Anne Bertucio had sent an email out to all PTLs (shortly before the election so it went to you and not Melanie) saying

[openstack-dev] [nova][neutron] Rocky PTG summary - nova/neutron

Hello Stackers, I've put together an etherpad [0] for the summary of the nova/neutron session from the PTG in the Croke Park Hotel breakfast area and included it as a plain text export on this email. Please feel free to edit or reply to this thread to add/correct anything I've missed.

Re: [openstack-dev] [nova][placement] update_provider_tree design updates

On Thu, 15 Mar 2018, Eric Fried wrote: One of the takeaways from the Queens retrospective [1] was that we should be summarizing discussions that happen in person/hangout/IRC/etc. to the appropriate mailing list for the benefit of those who weren't present (or paying attention :P ). This is

[openstack-dev] [nova][placement] update_provider_tree design updates

One of the takeaways from the Queens retrospective [1] was that we should be summarizing discussions that happen in person/hangout/IRC/etc. to the appropriate mailing list for the benefit of those who weren't present (or paying attention :P ). This is such a summary. As originally conceived,

Re: [openstack-dev] Vancouver Summit Schedule now live!

Hey Matt and Jay :) Jay's correct the Updates are happening. Project Updates are their own thing separate from the standard submission. Anne Bertucio had sent an email out to all PTLs (shortly before the election so it went to you and not Melanie) saying we had slots and you needed to request one

Re: [openstack-dev] [nova][placement] update_provider_tree design updates

Excellent and astute questions, both of which came up in the discussion, but I neglected to mention. (I had to miss *something*, right?) See inline. On 03/15/2018 02:29 PM, Chris Dent wrote: > On Thu, 15 Mar 2018, Eric Fried wrote: > >> One of the takeaways from the Queens retrospective [1]

[openstack-dev] OpenStack Ansible Disk requirements [docs] [osa]

Compute host disk requirements for Openstack Ansible seem high in the documentation. I think I have used smaller compute hosts in the past. Did something change in Queens? https://docs.openstack.org/project-deploy-guide/openstack-ansible/latest/overview-requirements.html Compute hosts Disk

Re: [openstack-dev] [Octavia] Using Octavia without neutron's extensions allowed-address-pairs and security-groups.

Hi Vadim, Yes, currently the only network driver available for Octavia (called allowed-address-pairs) uses the allowed-address-pairs feature of neutron. This allows active/standby and VIP migration during failover situations. If you need to run without that feature, an non-allowed-address-pairs

Re: [openstack-dev] [nova][cinder] Rocky PTG summary - nova/cinder

I realized I forgot to add the [cinder] tag to the subject line when I sent this originally. Sorry about that. Hello all, Here’s the PTG summary etherpad [0] for the nova/cinder session from the PTG, also included as a plain text export on this email. Cheers, -melanie [0]

[openstack-dev] [Tatu][Nova] Handling instance destruction

Heya, I've just stumbled across Tatu and the design presentation [1], and I am wondering how you handle cleaning up instances when they are deleted given that nova vendordata doesn't expose a "delete event". Specifically I'm wondering if we should add support for such an event to vendordata

[openstack-dev] Zuul project evolution

Hi, To date, Zuul has (perhaps rightly) often been seen as an OpenStack-specific tool. That's only natural since we created it explicitly to solve problems we were having in scaling the testing of OpenStack. Nevertheless, it is useful far beyond OpenStack, and even before v3, it has found

Re: [openstack-dev] [nova] about rebuild instance booted from volume

On 3/15/2018 5:29 PM, Dan Smith wrote: Yep, for sure. I think if there are snapshots, we have to refuse to do te thing. My comment was about the "does nova have authority to destroy the root volume during a rebuild" and I think it does, if delete_on_termination=True, and if there are no

Re: [openstack-dev] [nova][neutron] Rocky PTG summary - nova/neutron

On 3/15/2018 3:30 PM, melanie witt wrote:     * We don't need to block bandwidth-based scheduling support for doing port creation in conductor (it's not trivial), however, if nova creates a port on a network with a QoS policy, nova is going to have to munge the allocations and update

Re: [openstack-dev] [all][requirements] a plan to stop syncing requirements into projects

Excerpts from Matthew Thode's message of 2018-03-15 18:36:50 -0500: > On 18-03-15 19:29:37, Doug Hellmann wrote: > > Excerpts from Matthew Thode's message of 2018-03-15 10:24:10 -0500: > > > On 18-03-15 07:03:11, Doug Hellmann wrote: > > > > What I Want to Do > > > > - > > > > > >

[openstack-dev] [k8s][octavia][lbaas] Experiences on using the LB APIs with K8s

As I've been working more in the Kubernetes community, I've been evaluating the different points of integration between OpenStack services and the Kubernetes application platform. One of the weaker points of integration has been in using the OpenStack LBaaS APIs to create load balancers for

Re: [openstack-dev] [all][requirements] a plan to stop syncing requirements into projects

Excerpts from Matthew Thode's message of 2018-03-15 10:05:50 -0500: > On 18-03-15 09:45:38, Doug Hellmann wrote: > > Excerpts from Thierry Carrez's message of 2018-03-15 14:34:50 +0100: > > > Doug Hellmann wrote: > > > > [...] > > > > TL;DR > > > > - > > > > > > > > Let's stop copying exact

Re: [openstack-dev] [First Contact][SIG] Weekly Meeting

sorry I missed the meeting, I've been off with family related gastro fun, fun times... first me and then the pregnant wife which means spending the whole morning yesterday in hostpital re-hydrating the wife, just as a precaution to keep the baby safe. good news was the toddler wasn't hit as bad as

Re: [openstack-dev] [all][requirements] a plan to stop syncing requirements into projects

Excerpts from Jeremy Stanley's message of 2018-03-15 14:28:49 +: > On 2018-03-15 07:03:11 -0400 (-0400), Doug Hellmann wrote: > [...] > > 1. Update the requirements-check test job to change the check for > >an exact match to be a check for compatibility with the > >

Re: [openstack-dev] [all][requirements] a plan to stop syncing requirements into projects

Excerpts from Matthew Thode's message of 2018-03-15 10:24:10 -0500: > On 18-03-15 07:03:11, Doug Hellmann wrote: > > What I Want to Do > > - > > > > 1. Update the requirements-check test job to change the check for > >an exact match to be a check for compatibility with the > >

Re: [openstack-dev] [nova] about rebuild instance booted from volume

> Deleting all snapshots would seem dangerous though... > > 1. I want to reset my instance to how it was before > 2. I'll just do a snapshot in case I need any data in the future > 3. rebuild > 4. oops Yep, for sure. I think if there are snapshots, we have to refuse to do te thing. My comment was

Re: [openstack-dev] [all][requirements] a plan to stop syncing requirements into projects

On 18-03-15 19:29:37, Doug Hellmann wrote: > Excerpts from Matthew Thode's message of 2018-03-15 10:24:10 -0500: > > On 18-03-15 07:03:11, Doug Hellmann wrote: > > > What I Want to Do > > > - > > > > > > 1. Update the requirements-check test job to change the check for > > >an

[openstack-dev] [gate] Bug 1741275 is our top gate failure since March 13th

If you're noticed any volume-related tests failing this week, it's not just you. There is an old bug that is back where the c-sch CapacityFilter is kicking out the host because there is too much going on in the single host at once. http://status.openstack.org/elastic-recheck/#1741275

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

Hello, In order to continue and progress on the API Schema guideline [1] as mentioned in [2] to make APIs more machine-discoverable and also discussed during [3]. Unfortunately until a new or either a second meeting time slot has been allocated,  inconveniently for everyone, have to be done

Re: [openstack-dev] [Tatu][Nova] Handling instance destruction

Thanks for this. I read the README for the project after this and I do now realise you're using notifications for some of these events. I guess I'm still pondering if its reasonable to have everyone listen to notifications to build systems like these, or if we should messages to vendordata to

Re: [openstack-dev] [TripleO][CI][QA][HA][Eris][LCOO] Validating HA on upstream

On Thu, Mar 15, 2018 at 9:45 PM, Adam Spiers wrote: > Raoul Scarazzini wrote: >> >> On 15/03/2018 01:57, Ghanshyam Mann wrote: >>> >>> Thanks all for starting the collaboration on this which is long pending >>> things and we all want to have some start on

Re: [openstack-dev] [Tatu][Nova] Handling instance destruction

Hi Michael, Thanks for your message... and thanks for your vendordata work! About your question, Tatu listens to events on the oslo message bus. Specifically, it reacts to compute.instance.delete.end by cleaning up per-instance resources. It also listens to project creation and user role

Re: [openstack-dev] [api] APAC-friendly API-SIG meeting times

Hi, Any chance we can progress on this one? I believe there are not enough participants to split the API SIG meeting in 2, and also more likely because of the same lack of people across the 2 it could make it pretty inefficient. Therefore I think changing the main meeting time to another

Re: [openstack-dev] [k8s][octavia][lbaas] Experiences on using the LB APIs with K8s

Hi Chris, I wear a number of hats related to this discussion, so I'll add a few points of view :) It turns out that with > Terraform, it's possible to tear down resources in a way that causes > Neutron to > leak administrator-privileged resources that can not be deleted by a > non-privileged

[openstack-dev] [cyborg]Summary of Mar 14 Meeting

Hi Team, Here are the meeting summary for our post-ptg kickoff meeting. 0. Meeting recordings: https://www.youtube.com/watch?v=6AZn0SUC_hw , https://www.youtube.com/watch?v=-wE2GkSibDo , https://www.youtube.com/watch?v=E40JOm311WI 1. PoC from Shaohe and Dolpher (

Re: [openstack-dev] [TripleO][CI][QA][HA][Eris][LCOO] Validating HA on upstream

Hi All, Sorry, Late to the party... I have added myself. --- Regards, Sampath On Fri, Mar 16, 2018 at 9:31 AM, Ghanshyam Mann wrote: > On Thu, Mar 15, 2018 at 9:45 PM, Adam Spiers wrote: > > Raoul Scarazzini wrote: > >> > >> On

[openstack-dev] [all][requirements] a plan to stop syncing requirements into projects

Back in Barcelona for the Ocata summit I presented a rough outline of a plan for us to change the way we manage dependencies across projects so that we can stop syncing them [1]. We've made some progress, and I think it's time to finish the work so I'm volunteering to take some of it up during

Re: [openstack-dev] [kolla][vote] core nomination for caoyuan

+1 On Tue, Mar 13, 2018 at 5:50 PM, Swapnil Kulkarni wrote: > On Mon, Mar 12, 2018 at 7:36 AM, Jeffrey Zhang > wrote: >> Kolla core reviewer team, >> >> It is my pleasure to nominate caoyuan for kolla core team. >> >> caoyuan's output is fantastic

[openstack-dev] [neutron][stable] New release for Pike is overdue

The last neutron release for Pike has been made in November, a lot of bug fixes have made it into the stable/pike branch, can we please get a fresh release for it soon? __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [OpenStackAnsible] Tag repos as newton-eol

Looks good to me. On 15 March 2018 at 01:11, Tony Breeds wrote: > On Wed, Mar 14, 2018 at 09:40:33PM +, Jean-Philippe Evrard wrote: >> Hello folks, >> >> The list is almost perfect: you can do all of those except >> openstack/openstack-ansible-tests. >> I'd like to

Re: [openstack-dev] [openstack][charms] Openstack + OVN

Hi James, Just a small reminder that I have pushed a patch for review, according to changes you suggested :-) Thanks, Aakash On Mon, Mar 12, 2018 at 2:38 PM, James Page wrote: > Hi Aakash > > On Sun, 11 Mar 2018 at 19:01 Aakash Kt wrote: > >> Hi,

Re: [openstack-dev] [tripleo] FFE - Feuture Freeze Exception request for Routed Spine and Leaf Deployment

Hi, It has come to my attention that I missed one detail for the routed spine and leaf support. There is an issue with introspection and the filtering used to ensure only specified nodes are introspected. Apparently we are still using the iptables based PXE filtering in ironic-inspecter. (I

Re: [openstack-dev] [gnocchi] gnocchi-keystone verification failed.

On 2018-03-15 5:16 AM, __ mango. wrote: > hi， > The environment variable that you're talking about has been configured > and the error has not gone away. > > I was on OpenStack for the first time, can you be more specific? Thank > you very much. >

Re: [openstack-dev] [nova] Rocky PTG summary - cells

Thanks for the reply, both solution looks reasonable. On Thu, Mar 15, 2018 at 10:29 AM, melanie witt wrote: > On Thu, 15 Mar 2018 09:54:59 +0800, Zhenyu Zheng wrote: > >> Thanks for the recap, got one question for the "block creation": >> >> * An attempt to create an

Re: [openstack-dev] [TripleO][CI][QA][HA][Eris][LCOO] Validating HA on upstream

On 15/03/2018 01:57, Ghanshyam Mann wrote: > Thanks all for starting the collaboration on this which is long pending > things and we all want to have some start on this. > Myself and SamP talked about it during OPS meetup in Tokyo and we talked > about below draft plan- > - Update the Spec - 

Re: [openstack-dev] [TripleO][CI][QA][HA][Eris][LCOO] Validating HA on upstream

Raoul Scarazzini wrote: On 15/03/2018 01:57, Ghanshyam Mann wrote: Thanks all for starting the collaboration on this which is long pending things and we all want to have some start on this. Myself and SamP talked about it during OPS meetup in Tokyo and we talked about below

Re: [openstack-dev] [Openstack-operators] [nova] about rebuildinstance booted from volume

It seems that we can only delete the snapshots of the original volume firstly,then delete the original volume if the original volume has snapshots. Thanks, lijie -- Original -- From: "Tomáš Vondra"; Date: Wed, Mar 14, 2018 11:43 PM To:

[openstack-dev] [openstack-ops][heat][PTG] Heat PTG Summary

Hi Heat devs and ops It's a great PTG plus SnowpenStack experience. Now Rocky started. We really need all kind of input and effort to make sure we're heading toward the right way. Here is what we been discussed during PTG: - Future strategy for heat-tempest-plugin & functional tests -

Re: [openstack-dev] [masakari] Masakari Project mascot ideas

Thanks all. Seems like we are good to go with "St. Bernard". I think general image is [1]. Or let me know I am wrong. I will inform to Anne and Kendall,about our choice. [1] https://www.min-inuzukan.com/st-bernard.html --- Regards, Sampath On Wed, Mar 14, 2018 at 6:42 PM, Shewale, Bhagyashri <

[openstack-dev] [masakari] Rocky work items

Hi All, Rocky work items will be discussed in 3/20 masakari IRC meeting [1]. Current items are listed in etherpad [2] and new items, comments, questions are welcome. If you are not able to join IRC meeting, then please add sufficient details to your comment and your contacts (IRC or email) where

Re: [openstack-dev] [gnocchi] gnocchi-keystone verification failed.

On Thu, Mar 15 2018, __ mango. wrote: > I have a question about the validation of gnocchi keystone. There's no question in your message. > I run the following command, but it is not successful.(api.auth_mode :basic, > basic mode can be successful) > > # gnocchi status --debug > REQ: curl -g -i

Re: [openstack-dev] [horizon][neutron] tools/tox_install changes - breakage with constraints

Hi Andreas, all, > Note that thanks to the tox-siblings feature, we really continue to > install neutron and horizon from git - and not use the versions in > the global-requirements constraints file. This addresses my main concern, which was that by removing tools/tox_install.sh we would end up

Re: [openstack-dev] [horizon][neutron] tools/tox_install changes - breakage with constraints

On 2018-03-15 10:05, Thomas Morin wrote: > Hi Andreas, all, > > Andreas Jaeger, 2018-03-14 20:46: >> Note that thanks to the tox-siblings feature, we really continue to >> install neutron and horizon from git - and not use the versions in the >> global-requirements constraints file. > > This

[openstack-dev] [Octavia] Using Octavia without neutron's extensions allowed-address-pairs and security-groups.

Hi, I'm trying to install Octavia (from branch master) in my openstack installation. In my installation, neutron works with disabled extension allowed-address-pairs and disabled extension security-groups. This is done to improve performance. At the moment, i see that Octavia supporting for

[openstack-dev] [nova][libvirt] question on max cpu and memory

In order to work on [1] for prove libvirt is ok to do live-resize, I want to make following changes on xml file of instance to make maximum memory as 1G and current memory as 512M , and current CPU is a while maximum CPU is 2 so that we can hot resize through libvirt interface question I have is

Re: [openstack-dev] [horizon][neutron] tools/tox_install changes - breakage with constraints

Hi Doug, Doug Hellmann, 2018-03-14 23:42: > We keep doing lots of infra-related work to make it "easy" to do > when it comes to > managing dependencies. There are three ways to address the issue > with horizon and neutron, and none of them involve adding features > to pbr. > > 1. Things that

Re: [openstack-dev] [gnocchi] gnocchi-keystone verification failed.

hi??The environment variable that you're talking about has been configured and the error has not gone away. I was on OpenStack for the first time, can you be more specific? Thank you very much. -- Original -- From: "Julien

Re: [openstack-dev] [horizon][neutron] tools/tox_install changes - breakage with constraints

Excerpts from Thomas Morin's message of 2018-03-15 10:15:38 +0100: > Hi Doug, > > Doug Hellmann, 2018-03-14 23:42: > > We keep doing lots of infra-related work to make it "easy" to do > > when it comes to > > managing dependencies. There are three ways to address the issue > > with horizon and

Re: [openstack-dev] [Openstack-operators] [nova] about rebuildinstance booted from volume

On 3/15/2018 7:27 AM, 李杰 wrote: It seems that  we  can  only delete the snapshots of the original volume firstly,then delete the original volume if the original volume has snapshots. Nova won't be deleting the volume snapshots just to delete the volume during a rebuild. If we decide to

Re: [openstack-dev] [refstack] Full list of API Tests versus 'OpenStack Powered' Tests

Greg, For compliance it is sufficient to run https://refstack.openstack.org/#/guidelines. But it is good if you can also submit fill Tempest run. That is used internally by refstack to identify which tests to include in the future. This can be submitted anonymously if you like. Thanks, Arkady

Re: [openstack-dev] [nova] Rocky PTG summary - cells

I would also prefer not having to rely on reading all the cell DBs to calculate quotas. On Thu, Mar 15, 2018 at 3:29 AM, melanie witt wrote: > > > I would prefer not to block instance creations because of "down" cells, ​++ ​ > so maybe there is some possibility to

Re: [openstack-dev] [all][requirements] a plan to stop syncing requirements into projects

Doug Hellmann wrote: > [...] > TL;DR > - > > Let's stop copying exact dependency specifications into all our > projects to allow them to reflect the actual versions of things > they depend on. The constraints system in pip makes this change > safe. We still need to maintain some level of

Re: [openstack-dev] [all][requirements] a plan to stop syncing requirements into projects

Excerpts from Thierry Carrez's message of 2018-03-15 14:34:50 +0100: > Doug Hellmann wrote: > > [...] > > TL;DR > > - > > > > Let's stop copying exact dependency specifications into all our > > projects to allow them to reflect the actual versions of things > > they depend on. The constraints

[openstack-dev] [FEMDC] Brainstorming regarding the Vancouver Forum

Hi all, I just created an FEMDC etherpad following the Melvin's email regarding the next Forum in Vancouver. Please do not hesitate to propose ideas for sessions at the forum : https://wiki.openstack.org/wiki/Forum/Vancouver2018 ++ Ad_ri3n_

Re: [openstack-dev] [refstack] Full list of API Tests versus 'OpenStack Powered' Tests

Re-posting this question to ‘OPENSTACK REFSTACK’, Any guidance on what level of compliance is required to qualify for the OpenStack Logo ( https://www.openstack.org/brand/interop/ ), See questions below. Greg. From: Greg Waines Date: Monday, February 26, 2018 at 6:22

Re: [openstack-dev] [all][requirements] a plan to stop syncing requirements into projects

On 2018-03-15 07:03:11 -0400 (-0400), Doug Hellmann wrote: [...] > 1. Update the requirements-check test job to change the check for >an exact match to be a check for compatibility with the >upper-constraints.txt value. [...] I thought it might be possible to even just do away with this

Re: [openstack-dev] [nova] about rebuild instance booted from volume

On 03/14/2018 08:46 AM, Matt Riedemann wrote: On 3/14/2018 3:42 AM, 李杰 wrote:              This is the spec about  rebuild a instance booted from volume.In the spec,there is a        question about if we should delete the old root_volume.Anyone who is interested in        booted from

Re: [openstack-dev] [refstack] Full list of API Tests versus 'OpenStack Powered' Tests

On 2018-03-15 14:16:30 + (+), arkady.kanev...@dell.com wrote: [...] > This can be submitted anonymously if you like. Anonymous submissions got disabled (and the existing set of data from them deleted). See the announcement from a month ago for details:

Re: [openstack-dev] [nova] about rebuild instance booted from volume

> Rather than overload delete_on_termination, could another flag like > delete_on_rebuild be added? Isn't delete_on_termination already the field we want? To me, that field means "nova owns this". If that is true, then we should be able to re-image the volume (in-place is ideal, IMHO) and if not,

Re: [openstack-dev] [all][requirements] a plan to stop syncing requirements into projects

On 18-03-15 09:45:38, Doug Hellmann wrote: > Excerpts from Thierry Carrez's message of 2018-03-15 14:34:50 +0100: > > Doug Hellmann wrote: > > > [...] > > > TL;DR > > > - > > > > > > Let's stop copying exact dependency specifications into all our > > > projects to allow them to reflect the

Re: [openstack-dev] [all][requirements] a plan to stop syncing requirements into projects

On 18-03-15 07:03:11, Doug Hellmann wrote: > What I Want to Do > - > > 1. Update the requirements-check test job to change the check for >an exact match to be a check for compatibility with the >upper-constraints.txt value. > >We would check the value for the

[openstack-dev] [glance] OSSN-0076 brainstorming session Friday 16 March

I'm working on a spec to alleviate OSSN-0076 that would follow up the OSSN-0075 proposal [0], but have run into some problems. It would be helpful to lay them out and get some feedback. I'll be in the #openstack-glance channel at 16:30 UTC tomorrow (Friday) to discuss. Will take less than 1/2