Re: [OpenStack-Infra] Retiring some repos?

I digged into the remaining and will investigate whether we can retire them: openstack-infra/zuul-packaging Paul, should we abandon this one as well? openstack-infra/featuretracker (together with puppet-featuretracker) these work together with openstack/development-proposals from the

Re: [OpenStack-Infra] Retiring some repos?

On 2018-08-28 23:50, Clark Boylan wrote: > [...] I think these repos can definitely be retired: # Was part of bitergia work with openstack which is no longer done openstack-infra/activity-board # These may have been attempts at having puppet beaker testing play nice with our CI but we hacked

[openstack-dev] [infra] Retiring some unused repositories

The infra team plans to retire the following repositories: openstack-infra/activity-board openstack-infra/beaker-localhost openstack-infra/beaker-nodepool openstack-infra/err2d2 openstack-infra/js-afs-blob-store openstack-infra/js-openstack-registry-hooks

Re: [OpenStack-Infra] starting zuul migration for congress team repositories

All of the patches to import the zuul settings into these repositories are approved and we are ready to proceed with https://review.openstack.org/#/c/592970/ On Fri, Aug 17, 2018 at 9:20 PM Nguyễn Trí Hải wrote: > The Zuul project settings for the congress repositories > has begun. Please do

Re: [openstack-dev] [goal][python3] goal champion tools

For dealing with this problem, I turn off all the Timeline events in Preferences. On Wed, Aug 29, 2018 at 6:58 AM Doug Hellmann wrote: > The story with all of the tasks for tracking the zuul migration has so > many comments it will no longer display in my browser. So, I've created > 2 tools to

Re: [openstack-dev] [stable][nova] Nominating melwitt for nova stable core

On Tue, Aug 28, 2018 at 03:26:02PM -0500, Matt Riedemann wrote: > I hereby nominate Melanie Witt for nova stable core. Mel has shown that she > knows the stable branch policy and is also an active reviewer of nova stable > changes. > > +1/-1 comes from the stable-maint-core team [1] and then

Re: [openstack-dev] [TripleO][kolla-ansible][DevStack][Tempest][openstack-ansible] Collaborate towards creating a unified ansible tempest role in openstack-ansible project

On Mon, Aug 27, 2018 at 12:43 PM Mohammed Naser wrote: > Hi Chandan, > > This is great, I added some more OSA-side comments, I'd love for us to > find sometime to sit down to discuss this at the PTG. > > Thanks, > Mohammed > > On Mon, Aug 27, 2018 at 12:39 PM, Jesse Pretorius > wrote: > >>On

[openstack-dev] [Neutron] Tungsten Fabric (formally OpenContrail) at Denver PTG

The Tungsten Fabric community invites you to join us at the OpenStack

Re: [Openstack-operators] Openstack Kilo - Danger: There was an error submitting the form. Please try again.

Hi Anwar, The log message you posted below is not an error (it is at level DEBUG and can be ignored). I would look in your horizon logs and also. The API logs of nova/neutron/glance/cinder to see what’s going on. Good luck! Sam > On 28 Aug 2018, at 9:22 pm, Anwar Durrani wrote: > > Hi

Re: [openstack-dev] [tempest][qa][congress] trouble setting tempest feature flag

Ha. Turned out to be a simple mistake in hyphens vs underscores. On Tue, Aug 28, 2018 at 3:06 PM Eric K wrote: > > Any thoughts on what could be going wrong that the tempest tests still > see the default conf values rather than those set here? Thanks lots! > > Here is the devstack log line

Re: [openstack-dev] [all][election] TC Election Season

Excerpts from Tony Breeds's message of 2018-08-28 15:15:00 +1000: > Election details: https://governance.openstack.org/election/ > > Please read the stipulations and timelines for candidates and > electorate contained in this governance documentation. > > There will be further announcements

Re: [openstack-dev] [nova] [placement] XenServer CI failed frequently because of placement update

Thank you very much for the help, Bob, Jay and Eric. Naichuan Sun -Original Message- From: Bob Ball [mailto:bob.b...@citrix.com] Sent: Wednesday, August 29, 2018 12:22 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [nova] [placement]

Re: [OpenStack-Infra] Retiring some repos?

On 2018-08-28 14:50:40 -0700 (-0700), Clark Boylan wrote: [...] > # Project to provide alternate Gerrit UI that never got commits > openstack-infra/puppet-vinz > openstack-infra/vinz > openstack-infra/vinz-webclient [...] As an aside, if we ever decide to rename nodepool, recycling this name gets

Re: [openstack-dev] [tempest][qa][congress] trouble setting tempest feature flag

Any thoughts on what could be going wrong that the tempest tests still see the default conf values rather than those set here? Thanks lots! Here is the devstack log line showing the flags being set:

[openstack-dev] [goal][python3] goal champion tools

The story with all of the tasks for tracking the zuul migration has so many comments it will no longer display in my browser. So, I've created 2 tools to look at the data from the command line. https://review.openstack.org/597245 has a tool to list the task assignments

Re: [OpenStack-Infra] Retiring some repos?

On Sun, Aug 19, 2018, at 9:47 AM, Andreas Jaeger wrote: > A quick search with codesearch suggests that these can be retired since > I couldn't find a user: > > openstack-infra/activity-board > openstack-infra/beaker-localhost > openstack-infra/beaker-nodepool > openstack-infra/err2d2 >

Re: [openstack-dev] [goal][python3] week 3 update

Excerpts from Michel Peterson's message of 2018-08-28 16:30:02 +0300: > On Mon, Aug 27, 2018 at 10:37 PM, Doug Hellmann > wrote: > > > > > If your team is ready to have your zuul settings migrated, please > > let us know by following up to this email. We will start with the > > volunteers, and

Re: [openstack-dev] [goal][python3] week 3 update

Excerpts from Doug Hellmann's message of 2018-08-28 17:42:29 -0400: > Excerpts from Zane Bitter's message of 2018-08-28 16:47:06 -0400: > > On 27/08/18 15:37, Doug Hellmann wrote: > > > == Next Steps == > > > > > > If your team is ready to have your zuul settings migrated, please > > > let us

[OpenStack-Infra] [goal][python3][heat] starting zuul migration for heat

The migration of Zuul project settings for the heat repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack-dev/heat-cfnclient - openstack/heat - openstack/heat-agents - openstack/heat-cfntools -

Re: [openstack-dev] [goal][python3] week 3 update

Excerpts from Zane Bitter's message of 2018-08-28 16:47:06 -0400: > On 27/08/18 15:37, Doug Hellmann wrote: > > == Next Steps == > > > > If your team is ready to have your zuul settings migrated, please > > let us know by following up to this email. We will start with the > > volunteers, and then

Re: [openstack-dev] [stable][nova] Nominating melwitt for nova stable core

+1 from me On Tue, Aug 28, 2018 at 5:27 PM Sean McGinnis wrote: > On Tue, Aug 28, 2018 at 03:26:02PM -0500, Matt Riedemann wrote: > > I hereby nominate Melanie Witt for nova stable core. Mel has shown that > she > > knows the stable branch policy and is also an active reviewer of nova > stable

Re: [openstack-dev] [stable][nova] Nominating melwitt for nova stable core

On Tue, Aug 28, 2018 at 03:26:02PM -0500, Matt Riedemann wrote: > I hereby nominate Melanie Witt for nova stable core. Mel has shown that she > knows the stable branch policy and is also an active reviewer of nova stable > changes. > > +1/-1 comes from the stable-maint-core team [1] and then

Re: [openstack-dev] [ironic] proposing metalsmith for inclusion into ironic governance

Might be a good option to plug in to the kubernetes cluster api https://github.com/kubernetes-sigs/cluster-api too. Thanks, Kevin From: Mark Goddard [m...@stackhpc.com] Sent: Tuesday, August 28, 2018 10:55 AM To: OpenStack Development Mailing List (not for usage

[openstack-dev] [Neutron] Denver PTG Team Dinner

Dear Neutron Team, Our PTG Denver team dinner will take place on Thursday 7pm, at https://www.famousdaves.com/Denver-Stapleton, 0.5 miles from the Renaissance Hotel, which translates to an easy 10 minutes walk: https://goo.gl/JZVg8D I am holding a reservation under my name for 20 people. Please

Re: [openstack-dev] [goal][python3] week 3 update

On 27/08/18 15:37, Doug Hellmann wrote: == Next Steps == If your team is ready to have your zuul settings migrated, please let us know by following up to this email. We will start with the volunteers, and then work our way through the other teams. Heat is ready. I already did master (and by

Re: [openstack-dev] [stable][nova] Nominating melwitt for nova stable core

On Tue, Aug 28, 2018 at 03:26:02PM -0500, Matt Riedemann wrote: > I hereby nominate Melanie Witt for nova stable core. Mel has shown that she > knows the stable branch policy and is also an active reviewer of nova stable > changes. > > +1/-1 comes from the stable-maint-core team [1] and then

[openstack-dev] [stable][nova] Nominating melwitt for nova stable core

I hereby nominate Melanie Witt for nova stable core. Mel has shown that she knows the stable branch policy and is also an active reviewer of nova stable changes. +1/-1 comes from the stable-maint-core team [1] and then after a week with no negative votes I think it's a done deal. Of course

Re: [OpenStack-Infra] starting zuul migration for Oslo team repositories

Excerpts from Doug Hellmann's message of 2018-08-06 11:54:35 -0400: > The Zuul project settings for the Oslo repositories > has begun. Please do not approve any changes to > openstack-infra/project-config/zuul.d/projects.yaml for > the following repositories: > > - openstack-dev/cookiecutter > -

[Openstack] Usery Portal for Cloud Sandboxes

Hi, I have written a Sandbox portal for cloud users who want to test Openstack clouds. I released a beta here**https://github.com/lhaig/usery/tree/v0.1-beta.1* * I would appreciate some feedback on it if anyone has the time to look at it.* * Thanks Lance* *

Re: [openstack-dev] [all][tc][openstack-helm] On the problem of OSF copyright headers

Sorry for the noise folks - the change was well-intentioned but uninformed! We will revert the changes. Thanks, Matt -Original Message- From: Jeremy Stanley Sent: Tuesday, August 28, 2018 12:00 PM To: openstack-dev@lists.openstack.org Cc: MCEUEN, MATT Subject:

Re: [openstack-dev] [nova] [placement] extraction (technical) update

On Aug 28, 2018, at 10:47 AM, Matt Riedemann wrote: > >> 1.1 Run the git filter-branch on a copy of nova >> 1.1.1 Add missing files to the file list: >> 1.1.1.1 .gitignore >> 1.1.1.2 # ANYTHING ELSE? > > Unless I were to actually run the git filter-branch tooling to see

Re: [openstack-dev] [all][tc][openstack-helm] On the problem of OSF copyright headers

On 2018-08-28 10:11:18 -0700 (-0700), John Dickinson wrote: [...] > It would be *really* helpful to have a simple rule or pattern for > each file's header. Something like "Copyright (c) created>-present by contributors to this project". I applaud and share your desire for a clear rule on such

[openstack-dev] [tc] [all] TC Report 18-35

HTML: https://anticdent.org/tc-report-18-35.html I didn't do a TC report last week because we spent much of the time discussing the issues surrounding extracting the placement service from nova. I've been working on making that happen—because that's been the intent from the start—for a couple

Re: [openstack-dev] [all][tc][openstack-helm] On the problem of OSF copyright headers

In this context, there's also the question of copyright headers for documentation files which we do not require - see https://wiki.openstack.org/wiki/Documentation/Copyright This came up recently with: https://review.openstack.org/#/c/593662/ I'm happy to see a canonical place for this

Re: [openstack-dev] [ironic] proposing metalsmith for inclusion into ironic governance

+1. I like it. Could also be a good fit for Kayobe's undercloud equivalent at some point. On Tue, 28 Aug 2018 at 18:51, Jim Rollenhagen wrote: > On Mon, Aug 27, 2018 at 12:09 PM, Dmitry Tantsur > wrote: > >> Hi all, >> >> I would like propose the metalsmith library [1][2] for inclusion into

Re: [openstack-dev] [ironic] proposing metalsmith for inclusion into ironic governance

On Mon, Aug 27, 2018 at 12:09 PM, Dmitry Tantsur wrote: > Hi all, > > I would like propose the metalsmith library [1][2] for inclusion into the > bare metal project governance. > > What it is and is not > - > > Metalsmith is a library and CLI tool for using Ironic+Neutron for

Re: [openstack-dev] [all][tc][openstack-helm] On the problem of OSF copyright headers

Excerpts from Jeremy Stanley's message of 2018-08-28 16:59:56 +: > [Obligatory disclaimer: I am not a lawyer, this is not legal advice, > and I am not representing the OpenStack Foundation in any legal > capacity here.] > > TL;DR: You should not be putting "Copyright OpenStack Foundation" on

Re: [openstack-dev] [all][tc][openstack-helm] On the problem of OSF copyright headers

On 28 Aug 2018, at 9:59, Jeremy Stanley wrote: [Obligatory disclaimer: I am not a lawyer, this is not legal advice, and I am not representing the OpenStack Foundation in any legal capacity here.] TL;DR: You should not be putting "Copyright OpenStack Foundation" on content in Git

[openstack-dev] [all][tc][openstack-helm] On the problem of OSF copyright headers

[Obligatory disclaimer: I am not a lawyer, this is not legal advice, and I am not representing the OpenStack Foundation in any legal capacity here.] TL;DR: You should not be putting "Copyright OpenStack Foundation" on content in Git repositories, or anywhere else for that matter (unless you know

Re: [openstack-dev] [nova] [placement] extraction (technical) update

> Grenade already has it's own "resources db" right? So we can shove > things in there before we upgrade and then verify they are still there > after the upgrade? Yep, I'm working on something right now. We create an instance that survives the upgrade and validate it on the other side. I'll just

Re: [openstack-dev] [nova] [placement] extraction (technical) update

On 8/28/2018 10:57 AM, Dan Smith wrote: The from-rocky will also need to extract data from the nova-api database for the placement tables and put it into the new placement database (as real operators will have to do). It'll need to do this after the split code has been installed and the schema

Re: [openstack-dev] [nova] [placement] XenServer CI failed frequently because of placement update

> Yeah, the nova.CONF cpu_allocation_ratio is being overridden to 0.0: The default there is 0.0[1] - and the passing tempest-full from Zuul on https://review.openstack.org/#/c/590041/ has the same line when reading the config[2]: We'll have a dig to see if we can figure out why it's not

Re: [openstack-dev] [nova] [placement] XenServer CI failed frequently because of placement update

Yeah, the nova.CONF cpu_allocation_ratio is being overridden to 0.0: Aug 27 07:43:02.179927 dsvm-devstack-citrix-lon-nodepool-1379254 nova-compute[21125]: DEBUG oslo_service.service [None req-4bb236c4-54c3-42b7-aa4e-e5c8b1ece0c7 None None] cpu_allocation_ratio = 0.0 {{(pid=21125)

Re: [openstack-dev] [nova] [placement] extraction (technical) update

On Tue, 28 Aug 2018, Matt Riedemann wrote: Are people okay with that and willing to commit to being okay with that answer in reviews? To some extent we need to have some faith on the end result: the tests work. If people are not okay with that, we need the people who are not to determine and

Re: [openstack-dev] [nova] [placement] extraction (technical) update

> Grenade uses devstack so once we have devstack on master installing > (and configuring) placement from the new repo and disable installing > and configuring it from the nova repo, that's the majority of the > change I'd think. > > Grenade will likely need a from-rocky script to move any config

Re: [openstack-dev] [nova] [placement] extraction (technical) update

Forgive me for barging into this, but just with my deployer and PTL of a deployment project hat on.. As part of the split, wouldn't we *not* need to make a devstack change if this is done correctly because placement will become a nova dependency, which is pulled out of Git and when using Zuul,

[Openstack-operators] [kolla][ceph]

What is the best practice for adding more Ceph OSD's to kolla in a production environment. Does deploy do anything to the existing data or does it simply add the OSD's (and potentially increase the placement groups if re-configured)? reconfigure doesnt touch newly prepared disks from what I see

Re: [openstack-dev] [nova] [placement] extraction (technical) update

On 8/28/2018 6:20 AM, Chris Dent wrote: On Mon, 27 Aug 2018, melanie witt wrote: I think we should use the openstack review system (gerrit) for moving the code. We're moving a critical piece of nova to its own repo and I think it's worth having the review and history contained in the

Re: [openstack-dev] [nova] [placement] extraction (technical) update

On 8/28/2018 8:11 AM, Balázs Gibizer wrote: I also think that we can add a non-voting tempest full job as well. Making it green depends on how hard to deploy placement from the new repo to tempest. I think as soon as placement repo has passing gabbits (e.g functional job) and we can deploy

Re: [openstack-dev] [nova] [placement] XenServer CI failed frequently because of placement update

On 8/28/2018 9:07 AM, Chris Dent wrote: On Tue, 28 Aug 2018, Bob Ball wrote: Just looking at Naichuan's output, I wonder if this is because allocation_ratio is registered as 0 in the inventory. Yes. Whatever happened to cause that is the root, that will throw the math off into zeroness in

Re: [OpenStack-Infra] Launch node and the new bridge server

Ian Wienand writes: > On 08/28/2018 09:48 AM, Clark Boylan wrote: >> On Mon, Aug 27, 2018, at 4:21 PM, Clark Boylan wrote: >> One quick new observation. launch-node.py does not install puppet at >> all so the subsequent ansible runs on the newly launched instances >> will fail when attempting to

Re: [openstack-dev] [nova][searchlight][designate][telemetry][mistral][blazar][watcher][masakari]Possible deprecation of Nova's legacy notification interface

Hi gibi, Thanks for the information. The Searchlight team would love to migrate to the new version of Nova notification. I apology for this late response since I just take over the project after your first email sent. We will discuss this at the next team meeting and figure out the plan. Bests,

[openstack-dev] [oslo] No meeting next two weeks

Next week is a US holiday so a lot of the team will be off, and the week after is the PTG. If you have anything to discuss in the meantime feel free to contact us in #openstack-oslo or here on the list. -Ben __ OpenStack

Re: [openstack-dev] [nova][searchlight][designate][telemetry][mistral][blazar][watcher][masakari]Possible deprecation of Nova's legacy notification interface

Thanks for all the responses. I collected them on the nova ptg discussion etherpad [1] (L186 at the moment). The nova team will talk about deprecation of the legacy interface on Friday on the PTG. If you want participate in the discussion but you are not planning to sit in the nova room whole

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

On 8/27/2018 1:53 PM, Matt Riedemann wrote: On 8/27/2018 12:11 PM, Miguel Lavalle wrote: Isn't multiple port binding what we need in the case of ports? In my mind, the big motivator for multiple port binding is the ability to change a port's backend Hmm, yes maybe. Nova's usage of multiple

[openstack-dev] [nova]Notification subteam meeting cancelled

Hi, There won't be notification subteam meeting this week. Cheers, gibi __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [Openstack] [nova]Capacity discrepancy between command line and MySQL query

On 08/27/2018 09:40 AM, Risto Vaaraniemi wrote: Hi, I tried to migrate a guest to another host but it failed with a message saying there's not enough capacity on the target host even though the server should me nearly empty. The guest I'm trying to move needs 4 cores, 4 GB of memory and 50 GB

Re: [openstack-dev] [nova] [placement] XenServer CI failed frequently because of placement update

On Tue, 28 Aug 2018, Bob Ball wrote: Just looking at Naichuan's output, I wonder if this is because allocation_ratio is registered as 0 in the inventory. Yes. Whatever happened to cause that is the root, that will throw the math off into zeroness in lots of different places. The default (if

Re: [openstack-dev] [nova] [placement] XenServer CI failed frequently because of placement update

We're not running with [1], however that did also fail the CI in the same way - see [2] for the full logs. The first failing appeared to be around Aug 27 08:32:14: Aug 27 08:32:14.502788 dsvm-devstack-citrix-lon-nodepool-1379254 devstack@placement-api.service[13219]: DEBUG

Re: [openstack-dev] [nova] [placement] extraction (technical) update

>> 2. We have a stack of changes to zuul jobs that show nova working but >> deploying placement in devstack from the new repo instead of nova's >> repo. This includes the grenade job, ensuring that upgrade works. > > I'm guessing there would need to be changes to Devstack itself, outside > of

Re: [openstack-dev] [goal][python3] week 3 update

On Mon, Aug 27, 2018 at 10:37 PM, Doug Hellmann wrote: > > If your team is ready to have your zuul settings migrated, please > let us know by following up to this email. We will start with the > volunteers, and then work our way through the other teams. > The networking-odl team is willing to

Re: [openstack-dev] [nova] [placement] XenServer CI failed frequently because of placement update

Naichuan- Are you running with [1]? If you are, the placement logs (at debug level) should be giving you some useful info. If you're not... perhaps you could pull that in :) Note that it refactors the _get_provider_ids_matching method completely, so it's possible your problem will

Re: [openstack-dev] [nova] [placement] extraction (technical) update

On Tue, Aug 28, 2018 at 1:20 PM, Chris Dent wrote: On Mon, 27 Aug 2018, melanie witt wrote: I think we should use the openstack review system (gerrit) for moving the code. We're moving a critical piece of nova to its own repo and I think it's worth having the review and history

Re: [openstack-dev] [Freezer] Reactivate the team

Hi Saad, That is the time to migrate Freezer to Storyboard, not the meeting time. :) Bests, *Trinh Nguyen *| Founder & Chief Architect *E:* dangtrin...@gmail.com | *W:* *www.edlab.xyz * On Tue, Aug 28, 2018 at 8:48 PM Saad Zaher wrote: >

[Openstack] BluePrint Approve Request (by FUJITSU)

Dear Sean McGinnis I am FUJITSU employee. My Name is Qian Mingyue. I am dealling update of FUJITSU OpenStack Cinder Volume Driver, and have registered a blueprint on Launchpad, which URL is https://blueprints.launchpad.net/cinder/+spec/fujitsu-eternus-dx-driver-update Could you please check the

Re: [openstack-dev] [nova] [placement] XenServer CI failed frequently because of placement update

On 08/28/2018 04:17 AM, Naichuan Sun wrote: Hi, experts, XenServer CI failed frequently with an error "No valid host was found. " for more than a week. I think it is cause by placement update. Hi Naichuan, Can you give us a link to the logs a patchset's Citrix XenServer CI that has failed?

[openstack-dev] [tripleo] PTG topics and agenda

Hello folks! With the PTG being quite soon, I just wanted to remind folks to add your topics on the etherpad: https://etherpad.openstack.org/p/tripleo-ptg-stein Also, please vote for the topics you're the most interested in, so we can add them to the agenda. I'll submit a potential agenda by

Re: [openstack-dev] [nova] [placement] extraction (technical) update

On Mon, Aug 27, 2018 at 5:31 PM, Matt Riedemann wrote: On 8/24/2018 7:36 AM, Chris Dent wrote: Over the past few days a few of us have been experimenting with extracting placement to its own repo, as has been discussed at length on this list, and in some etherpads:

Re: [openstack-dev] [Freezer] Reactivate the team

Hello Kendall, Can we get the old meeting slot which is Thursday @ 14:00 UTC if this is Ok with everyone ? Thanks, Saad! On Mon, Aug 27, 2018 at 11:46 PM Kendall Nelson wrote: > Hello, > > Here is the change that adds Freezer to StoryBoard[1]. If we can get the > PTL's +1, we can move

[Openstack-operators] Openstack Kilo - Danger: There was an error submitting the form. Please try again.

Hi Team, I am using KILO, i am having issue while launching any instance, its ending up with following error *Danger: *There was an error submitting the form. Please try again. i have managed to capture the log, where i have found as tail -f /var/log/nova/nova-conductor.log 2018-08-28

Re: [openstack-dev] [nova] [placement] extraction (technical) update

On Mon, 27 Aug 2018, melanie witt wrote: I think we should use the openstack review system (gerrit) for moving the code. We're moving a critical piece of nova to its own repo and I think it's worth having the review and history contained in the openstack review system. This seems a

Re: [openstack-dev] [nova] [placement] extraction (technical) update

2018-08-27 23:31 GMT+08:00 Matt Riedemann : > On 8/24/2018 7:36 AM, Chris Dent wrote: > >> >> Over the past few days a few of us have been experimenting with >> extracting placement to its own repo, as has been discussed at >> length on this list, and in some etherpads: >> >>

Re: [OpenStack-Infra] Launch node and the new bridge server

On 08/28/2018 09:48 AM, Clark Boylan wrote: On Mon, Aug 27, 2018, at 4:21 PM, Clark Boylan wrote: One quick new observation. launch-node.py does not install puppet at all so the subsequent ansible runs on the newly launched instances will fail when attempting to stop the puppet service (and will

Re: [openstack-dev] [rpm-packaging] Step down as a reviewer

Hi Alberto, Am Mo., 13. Aug. 2018 um 11:08 Uhr schrieb Alberto Planas Dominguez : > I will change my role at SUSE at the end of the month (August 2018), so > I request to be removed from the core position on those projects. Sad to see you go, but I appreciate the heads up and wish you all the

Re: [openstack-dev] [nova] [placement] extraction (technical) update

On Mon, 2018-08-27 at 14:23 -0700, melanie witt wrote: > On Mon, 27 Aug 2018 10:31:50 -0500, Matt Riedemann wrote: > > On 8/24/2018 7:36 AM, Chris Dent wrote: > > > > > > Over the past few days a few of us have been experimenting with > > > extracting placement to its own repo, as has been

Re: [openstack-dev] [Searchlight] Team meeting next week

Hi Manh, 15:00 UTC is 22:00 in your time zone. Bests, On Tue, Aug 28, 2018, 17:26 Dinh Manh wrote: > Dear All. > I'm very sorry for my lately reply, but the time of 15:00 UTC is my office > work time so i'm afraid that i can't join with team in that time. > Very sorry. > > Best regards. > > >

Re: [openstack-dev] [TripleO]Addressing Edge/Multi-site/Multi-cloud deployment use cases (new squad)

On 08/22/2018 03:26 PM, Jiri Tomasek wrote: Hi, - Plan and template management in git.   This could be an iterative step towards eliminating Swift in the undercloud.   Swift seemed like a natural choice at the time because it was an existing   OpenStack service. 

[openstack-dev] [nova] [placement] XenServer CI failed frequently because of placement update

Hi, experts, XenServer CI failed frequently with an error "No valid host was found. " for more than a week. I think it is cause by placement update. It looks ` _get_provider_ids_matching ` return empty when allocate candidates, but filter statements looks good(vcpu/memory/disk):

Re: [openstack-dev] [Searchlight] Team meeting next week

For those who want to follow up previous meetings, please refer to this Etherpad: https://etherpad.openstack.org/p/search-team-meeting-agenda Bests, *Trinh Nguyen *| Founder & Chief Architect *E:* dangtrin...@gmail.com | *W:* *www.edlab.xyz *

Re: [openstack-dev] Appointing Slawek Kaplonski to the Neutron Drivers team

Congrats Slawek! I'm sure you'll rock as a driver too! Kuba On 27/08/2018 18:42, Miguel Lavalle wrote: > Dear Neutron team, > > In order to help the Neutron Drivers team to perform its very important job > of guiding the community to evolve the OpenStack Networking architecture to > meet the