Re: [Openstack] HA Compute & Instance Evacuation

On 05/02/2018 02:43 PM, Torin Woltjer wrote: I am working on setting up Openstack for HA and one of the last orders of business is getting HA behavior out of the compute nodes. There is no HA behaviour for compute nodes. Is there a project that will automatically evacuate instances from a

[Openstack] HA Compute & Instance Evacuation

I am working on setting up Openstack for HA and one of the last orders of business is getting HA behavior out of the compute nodes. Is there a project that will automatically evacuate instances from a downed or failed compute host, and automatically reboot them on their new host? I'm curious

[Openstack] SRIOV Enablement in openstack error

Dear all, I am trying to enable the SRIOV interfaces in my openstack Pike installation. I am following the guide: https://docs.openstack.org/neutron/pike/admin/config-sriov.html I am getting following error in neutron while doing so: 2018-05-02 17:08:19.492 75833 ERROR

Re: [Openstack] SRIOV Enablement in openstack error

Hi Navdeep, The yellow lines that you outline are related to the ovs mechanism driver which indicate that it can't bind direct port which as expected. (/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/drivers/mech_agent.py is port of the ovs mechanism driver) The error with the sriov

Re: [Openstack] HA Compute & Instance Evacuation

We're using the original Masakari project for this and it works really well. In fact just last week we lost a compute node and all of VM's were successfully migrated to a reserve host in under 5 minutes. It's a really nice feeling when your infrastructure heals itself before you even get a chance

Re: [Openstack] HA Compute & Instance Evacuation

> There is no HA behaviour for compute nodes. > > You are referring to HA of workloads running on compute nodes, not HA of > compute nodes themselves. It was a mistake for me to say HA when referring to compute and instances. Really I want to avoid a situation where one of my compute hosts gives

Re: [Openstack] HA Compute & Instance Evacuation

I'm vaguely familiar with Pacemaker/Corosync, as I'm using it with HAProxy on my controller nodes. I'm assuming in this instance that you use Pacemaker on your compute hosts so masakari can detect host outages? If possible could you go into more detail about the configuration? I would like to

Re: [Openstack] [masakari] HA Compute & Instance Evacuation

On 05/02/2018 04:39 PM, Torin Woltjer wrote: > There is no HA behaviour for compute nodes. > > You are referring to HA of workloads running on compute nodes, not HA of > compute nodes themselves. It was a mistake for me to say HA when referring to compute and instances. Really I want to

Re: [Openstack] HA Compute & Instance Evacuation

Take this with a grain of salt because we're using the original version before the project moved under the Big Tent and I'm not sure how much it's evolved since then. I assume the basic functions are the same though. You're correct; Corosync and Pacemaker are used to determine if a compute node

Re: [openstack-dev] [Zun][k8s] AWS Fargate and OpenStack Zun

+1 This is beautifully clear and helpful. Thank you! Neil On Wed, 2 May 2018, 02:13 Shuai Zhao, wrote: > Thanks Hongbin, > > The article is really great! > > On Mon, Apr 30, 2018 at 2:40 PM, Kumari, Madhuri > wrote: > >> Thank you

Re: [openstack-dev] [api] REST limitations and GraghQL inception?

I fixed the GraphQL typo (my mistake) in $subject to help with future ML searches. Please see inline too. On 02/05/18 07:37, Flint WALRUS wrote: Ok, here are my two cents regarding GraphQL integration within Openstack and some thoughts around this topic. 1°/- Openstack SDK should still

[openstack-dev] [neutron] How to specify OpenStack version for Zuul tests?

Hello, Is there any way to specify the OpenStack version for Zuul test? Currently, neteworking-onos project is very outdated, and I need to create a stable version for the codes for each OpenStack version (Ocata/Pike/Queens). Each version of OpenStack has different requirements in particular

Re: [openstack-dev] Overriding project-templates in Zuul

> > I think in actuality, both operations would end up as intersections: > > === === > Matcher Template Project Result > === === > files ABBC B > irrelevant-files ABBC B >

Re: [openstack-dev] [api] REST limitations and GraghQL inception?

Hi Gilles, folks, Nice to read such answers, I’m really thrilled by what could goes out from this discussion. One last thing regarding the SDK and Broker part of the discussion. GraphQL and SDK: Obviously as you noticed it, I was focused on the python-openstacksdk part of things even if it

Re: [openstack-dev] [neutron] How to specify OpenStack version for Zuul tests?

On Wed, May 2, 2018 at 2:10 AM, Sangho Shin wrote: > Hello, > > Is there any way to specify the OpenStack version for Zuul test? > > Currently, neteworking-onos project is very outdated, and I need to create > a stable version for the codes for each OpenStack version >

[openstack-dev] Problems with all OpenStack APIs & uwsgi with Content-Lenght and connection reset by peer (ie: 104)

Hi there! It's been a month I was knocking my head on the wall trying to get uwsgi working with all of OpenStack API uwsgi applications. Indeed, when OpenStack component (like for example, nova-compute) were talking to uwsgi, then they were receiving a 104 error (ie: connection reset by peer)

Re: [openstack-dev] Problems with all OpenStack APIs & uwsgi with Content-Lenght and connection reset by peer (ie: 104)

On Wed, 2 May 2018, Thomas Goirand wrote: What was disturbing was that, doing the same request with curl worked perfectly. Even more disturbing, it looked like I was having the issue nearly always in virtualbox, but not always in real hardware, where it sometimes worked. What was making the

[openstack-dev] [cyborg]No Team Meeting this Wed

Hi team, Since I'm traveling to KubeCon this week, let's cancel the weekly meeting today . You are still more than welcome to raise questions or just chat on our irc channel :) __ OpenStack Development Mailing List (not for

Re: [Openstack-operators] [openstack-dev] [nova] Default scheduler filters survey

Thanks Tim, pre-emptible instances are definitely of interest too. I'll be in Vancouver, hope to meet up at some point. And thanks Mathieu for sharing the code, if we build anything of wider interest I'll try to get it shared. Cheers, Dave -- ** Dave Holland ** Systems Support -- Informatics

Re: [Openstack-operators] Need feedback for nova aborting cold migration function

As an operator dealing with platforms that do cold migration I would like to be able to abort and rollback the process. That would give us a better service quality and availability. We do have no choices but to use cold migration on some of our remote sites as they don’t get a unified storage

Re: [openstack-dev] [Openstack-operators] The Forum Schedule is now live

On Wed, May 2, 2018 at 5:19 AM, Jimmy McArthur wrote: > > No problem, we have both on the schedule. I moved the Project Update to > 11-11:20 so you can have a few minutes before the Onboarding starts at > 11:50. > >

Re: [Openstack-operators] [openstack-dev] The Forum Schedule is now live

On Wed, May 2, 2018 at 5:19 AM, Jimmy McArthur wrote: > > No problem, we have both on the schedule. I moved the Project Update to > 11-11:20 so you can have a few minutes before the Onboarding starts at > 11:50. > >

Re: [openstack-dev] [Openstack-operators] The Forum Schedule is now live

Emilien Macchi wrote: Could we change the title of the slot and actually be a TripleO Project Update session? It would have been great to have the onboarding session but I guess we also have 2 other sessions where we'll have occasions to meet: TripleO Ops and User feedback and TripleO and

Re: [Openstack-operators] [openstack-dev] The Forum Schedule is now live

Emilien Macchi wrote: Could we change the title of the slot and actually be a TripleO Project Update session? It would have been great to have the onboarding session but I guess we also have 2 other sessions where we'll have occasions to meet: TripleO Ops and User feedback and TripleO and

Re: [openstack-dev] The Forum Schedule is now live

Gilles, Just responded to the ZenDesk ticket :) Cheers, Jimmy Gilles Dubreuil May 2, 2018 at 12:09 AM Hi Jimmy, Do you have an update about the API SIG slot? Thanks, Gilles __

Re: [openstack-dev] The Forum Schedule is now live

Jimmy, Fantastic! Thank you. Cheers, Gilles On 02/05/18 22:25, Jimmy McArthur wrote: Gilles, Just responded to the ZenDesk ticket :) Cheers, Jimmy Gilles Dubreuil May 2, 2018 at 12:09 AM Hi Jimmy, Do you have an update about the API SIG slot? Thanks, Gilles

[openstack-dev] [tc][stackalytics][neutron] neutron-lib not showing as TC-approved project on stackalytics

Back in 2016 we tagged neutron-lib as a "tc-approved-release" and as a result neutron-lib commits/reviews showed up on stackalytics under TC-approved Project Types. However as of recent that's seemed to have changed and neutron-lib commits/reviews are no longer showing up [1] even though it

Re: [openstack-dev] [tc][stackalytics][neutron] neutron-lib not showing as TC-approved project on stackalytics

On Wed, May 2, 2018 at 9:16 AM, Boden Russell wrote: > Back in 2016 we tagged neutron-lib as a "tc-approved-release" and as a > result neutron-lib commits/reviews showed up on stackalytics under > TC-approved Project Types. > > However as of recent that's seemed to have

Re: [openstack-dev] [nova][placement] Trying to summarize bp/glance-image-traits scheduling alternatives for rebuild

On 4/23/2018 4:43 PM, Jay Pipes wrote: How about just having the conductor call GET /resource_providers?in_tree==, see if there is a result, and if not, don't even call the scheduler at all (because conductor would already know there would be a NoValidHost returned)? This makes filtering on

Re: [openstack-dev] [nova][placement] Trying to summarize bp/glance-image-traits scheduling alternatives for rebuild

On 4/23/2018 4:51 PM, Arvind N wrote: For #1, we can make the explanation very clear that we rejected the request because the original traits specified in the original image and the new traits specified in the new image do not match and hence rebuild is not supported. We don't reject rebuild

Re: [openstack-dev] [nova][placement] Trying to summarize bp/glance-image-traits scheduling alternatives for rebuild

On 4/24/2018 3:25 AM, Balázs Gibizer wrote: The algorithm Eric provided in a previous mail do the filtering for the RPs that are part of the instance allocation so that sounds good to me. Yeah I've been wondering if that solves this VF case. I think we should not try to adjust allocations

Re: [openstack-dev] [tc][docs] documenting openstack "constellations"

On Tue, 01 May 2018 10:08:23 -0400 Doug Hellmann wrote: > The TC has had an item on our backlog for a while (a year?) to > document "constellations" of OpenStack components to make it easier > for deployers and users to understand which parts they need to have > the

Re: [openstack-dev] [nova][placement] Trying to summarize bp/glance-image-traits scheduling alternatives for rebuild

On 4/24/2018 8:26 AM, Sylvain Bauza wrote: We also have pre-flight checks for move operations like live and cold migrations, and I'd really like to keep all the conditionals in the conductor, because it knows better than the scheduler which operation is asked. I'm not sure what "pre-flight

[openstack-dev] [docs] Documentation meeting canceled

Hi all, Apologies but have to go offline now so canceling today's docs meeting. If you want to talk to the docs team, join #openstack-doc. Thanks, pk __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [nova][placement] Trying to summarize bp/glance-image-traits scheduling alternatives for rebuild

On 5/1/2018 5:26 PM, Arvind N wrote: In cases of rebuilding of an instance using a different image where the image traits have changed between the original launch and the rebuild, is it reasonable to ask to just re-launch a new instance with the new image? The argument for this approach is

[openstack-dev] [keystone] [policy] no policy meeting today

Hi all, I'm going to cancel the policy meeting today since attendance has been waning the last month or two and there are no items on the agenda. We should discuss whether or not we want to continue using this meeting. At this point, most of the policy work is in helping projects consume

Re: [openstack-dev] [keystone] [policy] no policy meeting today

Perhaps this meeting would be a good opportunity to get some broader discussion on our default roles spec we have proposed[1]. [1] - https://review.openstack.org/#/c/523973/8/specs/define-default-roles.rst /R Harry On Wed, May 2, 2018 at 10:17 AM, Lance Bragstad wrote: >

Re: [openstack-dev] [openstack-ansible] Implement rotations for meetings handling

On Wed, May 2, 2018 at 11:14 AM, Jean-Philippe Evrard wrote: > Hello everyone, > > Now that we are all part-time, I'd like to toy with a new idea, > proposed in the past by Jesse, to rotate the duties with people who > are involved in OSA, or want to get involved more

Re: [openstack-dev] [openstack-ansible] Implement rotations for meetings handling

I am definitely +1 on this, I think it's a great idea. Thanks, Dave Wilde (d34dh0r53) On Wed, May 2, 2018 at 10:27 AM Mohammed Naser wrote: > On Wed, May 2, 2018 at 11:14 AM, Jean-Philippe Evrard > wrote: > > Hello everyone, > > > > Now that we

Re: [openstack-dev] [openstack-ansible] Implement rotations for meetings handling

+1, leading meetings is a great way to get folks involved in the Community and gives them some 'ownership' within the project. Amy (spotz) On Wed, May 2, 2018 at 10:14 AM, Jean-Philippe Evrard < jean-phili...@evrard.me> wrote: > Hello everyone, > > Now that we are all part-time, I'd like to toy

Re: [openstack-dev] [nova][placement] Trying to summarize bp/glance-image-traits scheduling alternatives for rebuild

> What if the API compares the original image required traits against the new image required traits, and if the new image has required traits which weren't in the original image, then (punt) fail in the API? Then you would at least have a chance > to rebuild with a new image that has required

Re: [Openstack-operators] [openstack-dev] [nova][placement] Trying to summarize bp/glance-image-traits scheduling alternatives for rebuild

On 5/1/2018 5:26 PM, Arvind N wrote: In cases of rebuilding of an instance using a different image where the image traits have changed between the original launch and the rebuild, is it reasonable to ask to just re-launch a new instance with the new image? The argument for this approach is

Re: [Openstack-operators] [openstack-dev] [nova][placement] Trying to summarize bp/glance-image-traits scheduling alternatives for rebuild

> What if the API compares the original image required traits against the new image required traits, and if the new image has required traits which weren't in the original image, then (punt) fail in the API? Then you would at least have a chance > to rebuild with a new image that has required

[openstack-dev] [nova][ironic] ironic_host_manager and baremetal scheduler options removal

The baremetal scheduling options were deprecated in Pike [1] and the ironic_host_manager was deprecated in Queens [2] and is now being removed [3]. Deployments must use resource classes now for baremetal scheduling. [4] The large host subset size value is also no longer needed. [5] I've gone

Re: [openstack-dev] [tc][docs] documenting openstack "constellations"

On 01/05/18 16:21, Doug Hellmann wrote: Excerpts from Andreas Jaeger's message of 2018-05-01 21:51:19 +0200: On 05/01/2018 04:08 PM, Doug Hellmann wrote: The TC has had an item on our backlog for a while (a year?) to document "constellations" of OpenStack components to make it easier for

Re: [openstack-dev] Overriding project-templates in Zuul

Joshua Hesketh writes: >> >> I think in actuality, both operations would end up as intersections: >> >> === === >> Matcher Template Project Result >> === === >> files AB

[openstack-dev] [openstack-ansible] Implement rotations for meetings handling

Hello everyone, Now that we are all part-time, I'd like to toy with a new idea, proposed in the past by Jesse, to rotate the duties with people who are involved in OSA, or want to get involved more (it's not restricted to core developers!). One of the first duties to be handled this way could be

[openstack-dev] Third party module commits to TripleO/Newton branch

Hi, I am working on TrilioVault deployment integration with TripleO. This integration will contain changes to TripleO heat templates repo and tripleO puppet module as shown in attached document. We are targeting this integration for OpenStack Newton release

Re: [openstack-dev] [tc][docs] documenting openstack "constellations"

Excerpts from Petr Kovar's message of 2018-05-02 15:56:36 +0200: > On Tue, 01 May 2018 10:08:23 -0400 > Doug Hellmann wrote: > > > The TC has had an item on our backlog for a while (a year?) to > > document "constellations" of OpenStack components to make it easier > > for

Re: [openstack-dev] Zuul memory improvements

Congrats on the improvements, Jim! Sounds like this is going to make a huge difference. Go Zuul! Cheers, Jimmy James E. Blair April 30, 2018 at 10:03 AM Hi, We recently made some changes to Zuul which you may want to know about if you interact with a large

Re: [OpenStack-Infra] [openstack-dev] Zuul memory improvements

Congrats on the improvements, Jim! Sounds like this is going to make a huge difference. Go Zuul! Cheers, Jimmy James E. Blair April 30, 2018 at 10:03 AM Hi, We recently made some changes to Zuul which you may want to know about if you interact with a large

Re: [openstack-dev] Problems with all OpenStack APIs & uwsgi with Content-Lenght and connection reset by peer (ie: 104)

I noticed something similar when deploying Keystone using nginx in the lab, and pretty sure I fixed it by setting uwsgi_ignore_client_abort to on. http://nginx.org/en/docs/http/ngx_http_uwsgi_module.html In addition to that flag I also have client_header_buffer_size 64k; uwsgi_buffer_size

Re: [openstack-dev] [tc][docs] documenting openstack "constellations"

Excerpts from Zane Bitter's message of 2018-05-02 11:38:55 -0400: > On 01/05/18 16:21, Doug Hellmann wrote: > > Excerpts from Andreas Jaeger's message of 2018-05-01 21:51:19 +0200: > >> On 05/01/2018 04:08 PM, Doug Hellmann wrote: > >>> The TC has had an item on our backlog for a while (a year?)

Re: [Openstack-operators] [openstack-dev] [nova][ironic] ironic_host_manager and baremetal scheduler options removal

On Wed, May 2, 2018 at 12:49 PM, Matt Riedemann wrote: > On 5/2/2018 11:40 AM, Mathieu Gagné wrote: >> >> What's the state of caching_scheduler which could still be using those >> configs? > > > The CachingScheduler has been deprecated since Pike [1]. We discussed the >

Re: [Openstack-operators] [openstack-dev] [nova][ironic] ironic_host_manager and baremetal scheduler options removal

On 5/2/2018 12:00 PM, Mathieu Gagné wrote: If one can still run CachingScheduler (even if it's deprecated), I think we shouldn't remove the above options. As you can end up with a broken setup and IIUC no way to migrate to placement since migration script has yet to be written. You're

Re: [openstack-dev] [tc][docs] documenting openstack "constellations"

On 02/05/18 20:11, Doug Hellmann wrote: > Excerpts from Zane Bitter's message of 2018-05-02 11:38:55 -0400: >> On 01/05/18 16:21, Doug Hellmann wrote: >>> Excerpts from Andreas Jaeger's message of 2018-05-01 21:51:19 +0200: On 05/01/2018 04:08 PM, Doug Hellmann wrote: > The TC has had an

[openstack-dev] [Zun] Announce change of Zun core reviewer team

Hi all, I would like to announce the following change on the Zun core reviewers team: + Ji Wei Ji Wei has been working on Zun for a while. His contributions include blueprints, bug fixes, code reviews, etc. In particular, I would like to highlight that he has implemented two blueprints [1][2],

Re: [openstack-dev] [nova][ironic] ironic_host_manager and baremetal scheduler options removal

What's the state of caching_scheduler which could still be using those configs? Mathieu On Wed, May 2, 2018 at 12:25 PM, Matt Riedemann wrote: > The baremetal scheduling options were deprecated in Pike [1] and the > ironic_host_manager was deprecated in Queens [2] and is

Re: [Openstack-operators] [openstack-dev] [nova][ironic] ironic_host_manager and baremetal scheduler options removal

What's the state of caching_scheduler which could still be using those configs? Mathieu On Wed, May 2, 2018 at 12:25 PM, Matt Riedemann wrote: > The baremetal scheduling options were deprecated in Pike [1] and the > ironic_host_manager was deprecated in Queens [2] and is

Re: [openstack-dev] Third party module commits to TripleO/Newton branch

On 5/2/2018 11:23 AM, Shyam Biradar wrote: I am working on TrilioVault deployment integration with TripleO. This integration will contain changes to TripleO heat templates repo and tripleO puppet module as shown in attached document. We are targeting this

[Openstack-operators] [nova][ironic] ironic_host_manager and baremetal scheduler options removal

The baremetal scheduling options were deprecated in Pike [1] and the ironic_host_manager was deprecated in Queens [2] and is now being removed [3]. Deployments must use resource classes now for baremetal scheduling. [4] The large host subset size value is also no longer needed. [5] I've gone

Re: [Openstack-operators] [openstack-dev] [nova][ironic] ironic_host_manager and baremetal scheduler options removal

On 5/2/2018 11:40 AM, Mathieu Gagné wrote: What's the state of caching_scheduler which could still be using those configs? The CachingScheduler has been deprecated since Pike [1]. We discussed the CachingScheduler at the Rocky PTG in Dublin [2] and have a TODO to write a nova-manage data

Re: [openstack-dev] [tripleo] Third party module commits to TripleO/Newton branch

On Wed, May 2, 2018 at 10:23 AM, Shyam Biradar wrote: > Hi, > > I am working on TrilioVault deployment integration with TripleO. > This integration will contain changes to TripleO heat templates repo and > tripleO puppet module as shown in attached document. > > We

Re: [openstack-dev] [nova][ironic] ironic_host_manager and baremetal scheduler options removal

On 5/2/2018 12:00 PM, Mathieu Gagné wrote: If one can still run CachingScheduler (even if it's deprecated), I think we shouldn't remove the above options. As you can end up with a broken setup and IIUC no way to migrate to placement since migration script has yet to be written. You're

Re: [Openstack-operators] [openstack-dev] [nova][ironic] ironic_host_manager and baremetal scheduler options removal

On Wed, May 2, 2018 at 1:39 PM, Matt Riedemann wrote: > > I know you're just one case, but I don't know how many people are really > running the CachingScheduler with ironic either, so it might be rare. It > would be nice to get other operator input here, like I'm guessing

[openstack-dev] [all] Gerrit server replacement scheduled for May 2nd 2018

Hello from Infra. Today is the day for scheduled maintenance of gerrit, we'll be allocating 2 hours for the outage but don't expect it to take that long. During this time you will not be able to access gerrit. If you have any questions, or would like to follow along, please join us in

Re: [openstack-dev] Thank you TryStack!!

Just wanted to follow up on this. trystack.openstack.org is now correctly redirecting to the same place as trystack.org. Thanks, Jimmy Jimmy McArthur April 30, 2018 at 1:01 PM OK - got it :)

Re: [openstack-dev] [nova][ironic] ironic_host_manager and baremetal scheduler options removal

On Wed, May 2, 2018 at 12:49 PM, Matt Riedemann wrote: > On 5/2/2018 11:40 AM, Mathieu Gagné wrote: >> >> What's the state of caching_scheduler which could still be using those >> configs? > > > The CachingScheduler has been deprecated since Pike [1]. We discussed the >

Re: [openstack-dev] [openstack-ansible] Implement rotations for meetings handling

+1 good idea On Wed, May 2, 2018 at 9:09 AM, Amy Marrich wrote: > +1, leading meetings is a great way to get folks involved in the Community > and gives them some 'ownership' within the project. > > Amy (spotz) > > On Wed, May 2, 2018 at 10:14 AM, Jean-Philippe Evrard < >

Re: [openstack-dev] Problems with all OpenStack APIs & uwsgi with Content-Lenght and connection reset by peer (ie: 104)

On 05/02/2018 10:25 AM, Chris Dent wrote: > On Wed, 2 May 2018, Thomas Goirand wrote: > >> What was disturbing was that, doing the same request with curl worked >> perfectly. Even more disturbing, it looked like I was having the issue >> nearly always in virtualbox, but not always in real

Re: [openstack-dev] [openstack-ansible] Implement rotations for meetings handling

Excerpts from Jean-Philippe Evrard's message of 2018-05-02 17:14:07 +0200: > Hello everyone, > > Now that we are all part-time, I'd like to toy with a new idea, > proposed in the past by Jesse, to rotate the duties with people who > are involved in OSA, or want to get involved more (it's not

Re: [openstack-dev] [nova][ironic] ironic_host_manager and baremetal scheduler options removal

On 5/2/2018 11:40 AM, Mathieu Gagné wrote: What's the state of caching_scheduler which could still be using those configs? The CachingScheduler has been deprecated since Pike [1]. We discussed the CachingScheduler at the Rocky PTG in Dublin [2] and have a TODO to write a nova-manage data

Re: [openstack-dev] [nova][ironic] ironic_host_manager and baremetal scheduler options removal

On Wed, May 2, 2018 at 1:39 PM, Matt Riedemann wrote: > > I know you're just one case, but I don't know how many people are really > running the CachingScheduler with ironic either, so it might be rare. It > would be nice to get other operator input here, like I'm guessing

Re: [openstack-dev] [tc][docs] documenting openstack "constellations"

Excerpts from Graham Hayes's message of 2018-05-02 20:15:14 +0100: > On 02/05/18 20:11, Doug Hellmann wrote: > > Excerpts from Zane Bitter's message of 2018-05-02 11:38:55 -0400: > >> On 01/05/18 16:21, Doug Hellmann wrote: > >>> Excerpts from Andreas Jaeger's message of 2018-05-01 21:51:19 +0200:

[openstack-dev] [all] Gerrit server replacement finished

Hello from Infra. Gerrit maintenance has concluded successfully and running happily on Ubuntu Xenial. We were able to save and restore the queues from zuul, but as always be sure to check your patches as a recheck maybe be required. If you have any questions or comments, please reach out to us

Re: [openstack-dev] [nova][placement] Trying to summarize bp/glance-image-traits scheduling alternatives for rebuild

On 05/02/2018 10:07 AM, Matt Riedemann wrote: On 5/1/2018 5:26 PM, Arvind N wrote: In cases of rebuilding of an instance using a different image where the image traits have changed between the original launch and the rebuild, is it reasonable to ask to just re-launch a new instance with the

Re: [openstack-dev] [nova][placement] Trying to summarize bp/glance-image-traits scheduling alternatives for rebuild

Isnt this an existing issue with traits specified in flavor as well? Server is created using flavor1 requiring trait A on RP1. Before the rebuild is called, the underlying RP1 can be updated to remove trait A and when a rebuild is requested(regardless of whether the image is updated or not), we

Re: [openstack-dev] [nova][ironic] ironic_host_manager and baremetal scheduler options removal

On 5/2/2018 12:39 PM, Matt Riedemann wrote: FWIW, I think we can also backport the data migration CLI to stable branches once we have it available so you can do your migration in let's say Queens before g FYI, here is the start on the data migration CLI:

Re: [openstack-dev] [openstack-ansible] Implement rotations for meetings handling

Also +1.__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [Openstack-operators] [openstack-dev] [nova][placement] Trying to summarize bp/glance-image-traits scheduling alternatives for rebuild

On 5/2/2018 5:39 PM, Jay Pipes wrote: My personal preference is to add less technical debt and go with a solution that checks if image traits have changed in nova-api and if so, simply refuse to perform a rebuild. So, what if when I created my server, the image I used, let's say image1, had

Re: [Openstack-operators] [openstack-dev] [nova][placement] Trying to summarize bp/glance-image-traits scheduling alternatives for rebuild

Isnt this an existing issue with traits specified in flavor as well? Server is created using flavor1 requiring trait A on RP1. Before the rebuild is called, the underlying RP1 can be updated to remove trait A and when a rebuild is requested(regardless of whether the image is updated or not), we

Re: [openstack-dev] [nova][placement] Trying to summarize bp/glance-image-traits scheduling alternatives for rebuild

On Wed, 2 May 2018 17:45:37 -0500, Matt Riedemann wrote: On 5/2/2018 5:39 PM, Jay Pipes wrote: My personal preference is to add less technical debt and go with a solution that checks if image traits have changed in nova-api and if so, simply refuse to perform a rebuild. So, what if when I

Re: [Openstack-operators] [openstack-dev] [nova][ironic] ironic_host_manager and baremetal scheduler options removal

On 5/2/2018 12:39 PM, Matt Riedemann wrote: FWIW, I think we can also backport the data migration CLI to stable branches once we have it available so you can do your migration in let's say Queens before g FYI, here is the start on the data migration CLI:

Re: [openstack-dev] [nova][placement] Trying to summarize bp/glance-image-traits scheduling alternatives for rebuild

On 5/2/2018 5:39 PM, Jay Pipes wrote: My personal preference is to add less technical debt and go with a solution that checks if image traits have changed in nova-api and if so, simply refuse to perform a rebuild. So, what if when I created my server, the image I used, let's say image1, had

Re: [openstack-dev] [Zun] Announce change of Zun core reviewer team

Welcome to the team, Ji Wei ☺ Regards, Madhuri From: Hongbin Lu [mailto:hongbin...@gmail.com] Sent: Thursday, May 3, 2018 2:10 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [Zun] Announce change of Zun core

Re: [openstack-dev] [tripleo] validating overcloud config changes on a redeploy

On Fri, Apr 27, 2018 at 9:49 AM, Ade Lee wrote: > Hi, > > Recently I starting looking at how we implement password changes in an > existing deployment, and found that there were issues. This made me > wonder whether we needed a test job to confirm that password changes > (and

Re: [openstack-dev] [Zun] Announce change of Zun core reviewer team

+1 for Ji Wei :-) On Thu, May 3, 2018 at 4:40 AM, Hongbin Lu wrote: > Hi all, > > I would like to announce the following change on the Zun core reviewers > team: > > + Ji Wei > > Ji Wei has been working on Zun for a while. His contributions include > blueprints, bug fixes,