Re: [openstack-dev] [TripleO] easily identifying how services are configured

On 08/02/2018 11:41 PM, Steve Baker wrote: > > > On 02/08/18 13:03, Alex Schultz wrote: >> On Mon, Jul 9, 2018 at 6:28 AM, Bogdan Dobrelya >> wrote: >>> On 7/6/18 7:02 PM, Ben Nemec wrote: On 07/05/2018 01:23 PM, Dan Prince wrote: > On Thu, 2018-07-05 at 14:13 -0400, James

[openstack-dev] [all][docs] ACTION REQUIRED for projects using readthedocs

Hello, tl;dr : any projects using the "docs-on-readthedocs" job template to trigger a build of their documentation in readthedocs needs to: 1) add the "openstackci" user as a maintainer of the RTD project 2) generate a webhook integration URL for the project via RTD 3) provide the unique

[openstack-dev] [openstack-infra][openstack-third-party-ci][nodepool][ironic] nodepool can't ssh to the VM it created

Hi all, I’m now encountering a strange problem when using nodepool 0.5.0 to manage openstack cloud. It can create VM successfully in the openstack could, but can’t ssh to it. The nodepool.log is: >nodepool.log << END 2018-08-02 22:25:36,152 ERROR nodepool.utils: Failed to negotiate SSH:

Re: [openstack-dev] [nova] How to debug no valid host failures with placement

On 08/02/2018 06:18 PM, Michael Glasgow wrote: On 08/02/18 15:04, Chris Friesen wrote: On 08/02/2018 01:04 PM, melanie witt wrote: The problem is an infamous one, which is, your users are trying to boot instances and they get "No Valid Host" and an instance in ERROR state. They contact

[openstack-dev] [barbican][ara][helm][tempest] Removal of fedora-27 nodes

Greetings, We've had fedora-28 nodes online for some time in openstack-infra, I'd like to finish the migration process and remove fedora-27 images. Please take a moment to review and approve the following patches[1]. We'll be using the fedora-latest nodeset now, which make is a little easier for

Re: [openstack-dev] [designate][stable] Stable Core Team Updates

On Tue, Jul 31, 2018 at 06:39:36PM +0100, Graham Hayes wrote: > Hi Stable Team, > > I would like to nominate 2 new stable core reviewers for Designate. > > * Erik Olof Gunnar Andersson > * Jens Harbott (frickler) > > Erik has been doing a lot of stable reviews recently, and Jens has shown >

Re: [openstack-dev] [nova] How to debug no valid host failures with placement

On 08/02/18 15:04, Chris Friesen wrote: On 08/02/2018 01:04 PM, melanie witt wrote: The problem is an infamous one, which is, your users are trying to boot instances and they get "No Valid Host" and an instance in ERROR state. They contact support, and now support is trying to determine why

[openstack-dev] [keystone] Prospective RC1 Bugs

Hey all, I went through all bugs opened during the Rocky release and came up with a list of ones that might be good to fix before next week [0]. The good news is that more than half are in progress and none of them are release blockers, just ones that would be good to get in. Let me know if you

Re: [openstack-dev] [TripleO] easily identifying how services are configured

On 02/08/18 13:03, Alex Schultz wrote: On Mon, Jul 9, 2018 at 6:28 AM, Bogdan Dobrelya wrote: On 7/6/18 7:02 PM, Ben Nemec wrote: On 07/05/2018 01:23 PM, Dan Prince wrote: On Thu, 2018-07-05 at 14:13 -0400, James Slagle wrote: I would almost rather see us organize the directories by

Re: [openstack-dev] [infra][horizon][osc] ClientImpact tag automation

On 2018-08-02 14:16:10 -0500 (-0500), Sean McGinnis wrote: [...] > Interesting... I hadn't looked into Gerrit functionality enough to know about > these. Looks like this is probably what you are referring to? > > https://gerrit.googlesource.com/plugins/its-storyboard/ Yes, that. Khai Do (zaro)

Re: [openstack-dev] [nova] How to debug no valid host failures with placement

On 2018-08-02 14:04:10 -0600 (-0600), Chris Friesen wrote: [...] > At a previous Summit[1] there were some operators that said they just always > ran nova-scheduler with debug logging enabled in order to deal with this > issue, but that it was a pain to isolate the useful logs from the not-useful

Re: [openstack-dev] [nova] How to debug no valid host failures with placement

On 08/02/2018 01:04 PM, melanie witt wrote: The problem is an infamous one, which is, your users are trying to boot instances and they get "No Valid Host" and an instance in ERROR state. They contact support, and now support is trying to determine why NoValidHost happened. In the past, they

Re: [openstack-dev] [infra][horizon][osc] ClientImpact tag automation

On Thu, Aug 02, 2018 at 05:56:23PM +, Jeremy Stanley wrote: > On 2018-08-02 10:09:48 -0500 (-0500), Sean McGinnis wrote: > [...] > > I was able to find part of how that is implemented in jeepyb: > > > > http://git.openstack.org/cgit/openstack-infra/jeepyb/tree/jeepyb/cmd/notify_impact.py >

Re: [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation

The Edge and Containers translations are now live. As new translations become available, we will add them to the page. https://www.openstack.org/containers/ https://www.openstack.org/edge-computing/ Note that the Chinese translation has not been added to Zanata at this time, so I've left the

Re: [openstack-dev] [nova] How to debug no valid host failures with placement

On Thu, 2 Aug 2018 13:20:43 -0500, Eric Fried wrote: And we could do the same kind of approach with the non-granular request groups by reducing the single large SQL statement that is used for all resources and all traits (and all agg associations) into separate SELECT statements. It could be

Re: [openstack-dev] [nova] How to debug no valid host failures with placement

> And we could do the same kind of approach with the non-granular request > groups by reducing the single large SQL statement that is used for all > resources and all traits (and all agg associations) into separate SELECT > statements. > > It could be slightly less performance-optimized but more

Re: [openstack-dev] [tripleo] The Weekly Owl - 25th Edition

On Thu, 2018-08-02 at 13:30 -0400, Pradeep Kilambi wrote: > > > On Wed, Aug 1, 2018 at 6:06 PM Jill Rouleau wrote: > > On Tue, 2018-07-31 at 07:38 -0400, Pradeep Kilambi wrote: > > >  > > >  > > > On Mon, Jul 30, 2018 at 2:17 PM Jill Rouleau > > wrote: > > > > On Mon, 2018-07-30 at 11:35

Re: [openstack-dev] [infra][horizon][osc] ClientImpact tag automation

On 2018-08-02 10:09:48 -0500 (-0500), Sean McGinnis wrote: [...] > I was able to find part of how that is implemented in jeepyb: > > http://git.openstack.org/cgit/openstack-infra/jeepyb/tree/jeepyb/cmd/notify_impact.py [...] As for the nuts and bolts here, the script you found is executed from a

Re: [openstack-dev] [nova] How to debug no valid host failures with placement

On 08/02/2018 01:40 PM, Eric Fried wrote: Jay et al- And what I'm referring to is doing a single query per "related resource/trait placement request group" -- which is pretty much what we're heading towards anyway. If we had a request for: GET /allocation_candidates?  resources0=VCPU:1&  

Re: [openstack-dev] [nova] How to debug no valid host failures with placement

I should have made it clear that this is a tiny incremental improvement, to a code path that almost nobody is even going to see until Stein. In no way was it intended to close this topic. Thanks, efried On 08/02/2018 12:40 PM, Eric Fried wrote: > Jay et al- > >> And what I'm referring to is

Re: [openstack-dev] [nova] How to debug no valid host failures with placement

Jay et al- > And what I'm referring to is doing a single query per "related > resource/trait placement request group" -- which is pretty much what > we're heading towards anyway. > > If we had a request for: > > GET /allocation_candidates? >  resources0=VCPU:1& >  

Re: [openstack-dev] [tripleo] The Weekly Owl - 25th Edition

On Wed, Aug 1, 2018 at 6:06 PM Jill Rouleau wrote: > On Tue, 2018-07-31 at 07:38 -0400, Pradeep Kilambi wrote: > > > > > > On Mon, Jul 30, 2018 at 2:17 PM Jill Rouleau wrote: > > > On Mon, 2018-07-30 at 11:35 -0400, Pradeep Kilambi wrote: > > > > > > > > > > > > On Mon, Jul 30, 2018 at 10:42 AM

Re: [openstack-dev] [infra][horizon][osc] ClientImpact tag automation

On 8/2/2018 10:59 AM, Radomir Dopieralski wrote: To be honest, I don't see much point in automatically creating bugs that nobody is going to look at. When you implement a new feature, it's up to you to make it available in Horizon and CLI and wherever else, since the people working there

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

Greetings OpenStack community, Today's meeting was primarily focused around two topics: the IETF[7] draft proposal for Best Practices when building HTTP protocols[8], and the upcoming OpenStack Project Teams Gathering (PTG)[9]. The group had taken a collective action to read the aforementioned

[openstack-dev] [nova] Guests not getting metadata in a Cellsv2 deploy

Hi, I have a fresh pike deployment and the guests are not getting metadata. To investigate it further it would really help me to understand what the metadata flow is supposed to look like. In my deployment the guest receives a 404 when hitting http://169.254.169.254/latest/meta-data. I have

Re: [openstack-dev] Setting-up NoVNC 1.0.0 with nova

On Sun, 2018-05-20 at 09:33 -0700, Matt Riedemann wrote: > On 5/20/2018 6:37 AM, Thomas Goirand wrote: > > The novnc package in Debian and Ubuntu is getting very old. So I thought > > about upgrading to 1.0.0, which has lots of very nice newer features, > > like the full screen mode, and so on. >

Re: [openstack-dev] [nova] How to debug no valid host failures with placement

Storage space is a concern; really? If it really is, then keep X of them for some definition of X (days, number, hours, other)? Offload the snapshot asynchronously if snapshotting during requests is a problem. We have the power! :) Chris Friesen wrote: On 08/01/2018 11:34 PM, Joshua Harlow

Re: [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation

Frank, We expect to have these papers up this afternoon. I'll update this thread when we do. Thanks! Jimmy Frank Kloeker wrote: Hi Sebastian, okay, it's translated now. In Edge whitepaper is the problem with XML-Parsing of the term AT Don't know how to escape this. Maybe you will see the

Re: [openstack-dev] [infra][horizon][osc] ClientImpact tag automation

On Thu, Aug 02, 2018 at 05:59:20PM +0200, Radomir Dopieralski wrote: > To be honest, I don't see much point in automatically creating bugs that > nobody is going to look at. When you implement a new feature, it's up to > you to make it available in Horizon and CLI and wherever else, since the >

Re: [openstack-dev] [Openstack] [nova] [os-vif] [vif_plug_ovs] Support for OVS DB tcp socket communication.

On Wed, 2018-07-25 at 15:22 +0530, pranab boruah wrote: > Hello folks, > I have filed a bug in os-vif: > https://bugs.launchpad.net/os-vif/+bug/1778724 and working on a > patch. Any feedback/comments from you guys would be extremely > helpful. > Bug details: > OVS DB server has the feature of

Re: [openstack-dev] [infra][horizon][osc] ClientImpact tag automation

To be honest, I don't see much point in automatically creating bugs that nobody is going to look at. When you implement a new feature, it's up to you to make it available in Horizon and CLI and wherever else, since the people working there simply don't have the time to work on it. Creating a

[openstack-dev] [ironic] Next bug day is Tuesday August 28th! Vote for timeslot!

Hey all! Bug day was pretty productive today and we decided to schedule another one for the end of this month, on Tuesday the 28th. For details see the etherpad for the event [0] Also since we're changing things up, we decided to also put up a vote for the timeslot [1] If you have any

[openstack-dev] Add SRIOV mirroring support to Tap as a Service (https://review.openstack.org/#/c/584514/)

Hi TaaS Dev team, This mail is regarding the comment to move the changes out of stable/ocata branch. I would like to explain the reasons why we require these changes in Ocata branch. We intend to deploy TaaS-plugin with Openstack-helm (OSH) charts in our labs. However OSH as of now supports

[openstack-dev] [infra][horizon][osc] ClientImpact tag automation

I'm wondering if someone on the infra team can give me some pointers on how to approach something, and looking for any general feedback as well. Background == We've had things like the DocImpact tag that could be added to commit messages that would tie into some automation to create a

Re: [openstack-dev] [nova] How to debug no valid host failures with placement

On 08/01/2018 06:05 PM, Matt Riedemann wrote: On 8/1/2018 3:55 PM, Ben Nemec wrote: I changed disk_allocation_ratio to 2.0 in the config file and it had no effect on the existing resource provider.  I assume that is because I had initially deployed with it unset, so I got 1.0, and when I

Re: [openstack-dev] [nova] How to debug no valid host failures with placement

On 08/02/2018 01:12 AM, Alex Xu wrote: 2018-08-02 4:09 GMT+08:00 Jay Pipes >: On 08/01/2018 02:02 PM, Chris Friesen wrote: On 08/01/2018 11:32 AM, melanie witt wrote: I think it's definitely a significant issue that

Re: [openstack-dev] [nova] How to debug no valid host failures with placement

On 08/02/2018 04:10 AM, Chris Dent wrote: When people ask for something like what Chris mentioned: hosts with enough CPU: hosts that also have enough disk: hosts that also have enough memory: hosts that also meet extra spec host aggregate keys: hosts that also meet

[openstack-dev] [oslo] PTL on PTO, no meeting next week

I'm out next week and I'm told Monday is a bank holiday in some places, so we're going to skip the Oslo meeting for August 6th. Of course if you have issues you don't have to wait for a meeting to ask. The Oslo team is pretty much always around in #openstack-oslo. I should be back the

Re: [openstack-dev] Paste unmaintained

On Thu, 2 Aug 2018, Stephen Finucane wrote: Given that multiple projects are using this, we may want to think about reaching out to the author and seeing if there's anything we can do to at least keep this maintained going forward. I've talked to cdent about this already but if anyone else has

Re: [openstack-dev] Paste unmaintained

On Thu, Aug 2, 2018 at 10:27 AM, Doug Hellmann wrote: > Excerpts from Stephen Finucane's message of 2018-08-02 15:11:25 +0100: >> tl;dr: It seems Paste [1] may be entering unmaintained territory and we >> may need to do something about it. >> >> I was cleaning up some warning messages that nova

Re: [openstack-dev] [all][election] PTL nominations are now closed

> > > > Packaging_Rpm has a late candidate (Dirk Mueller). We always have a few > > teams per cycle that miss the election call, that would fall under that. > > +1 for appointing Dirk as PTL. > > Trove had a volunteer (Dariusz Krol), but that person did not fill the > > requirements for

Re: [openstack-dev] Paste unmaintained

Excerpts from Stephen Finucane's message of 2018-08-02 15:11:25 +0100: > tl;dr: It seems Paste [1] may be entering unmaintained territory and we > may need to do something about it. > > I was cleaning up some warning messages that nova was issuing this > morning and noticed a few coming from

Re: [openstack-dev] [nova] How to debug no valid host failures with placement

On 08/01/2018 11:34 PM, Joshua Harlow wrote: And I would be able to say request the explanation for a given request id (historical even) so that analysis could be done post-change and pre-change (say I update the algorithm for selection) so that the effects of alternations to said decisions

Re: [openstack-dev] [all][election] PTL nominations are now closed

Excerpts from Thierry Carrez's message of 2018-08-02 10:58:53 +0200: > Tony Breeds wrote: > > [...] > > There are 8 projects without candidates, so according to this > > resolution[1], the TC will have to decide how the following > > projects will proceed: Dragonflow, Freezer, Loci, Packaging_Rpm,

Re: [openstack-dev] [all][election] PTL nominations are now closed

Excerpts from Omer Anson's message of 2018-08-02 12:56:37 +0300: > Hi, > > I'm sorry for the inconvenience. I completely missed the nomination period. > Is it possible to send in a late nomination for Dragonflow? At this point the TC is going to be looking for a volunteer, so if there is one

[openstack-dev] Paste unmaintained

tl;dr: It seems Paste [1] may be entering unmaintained territory and we may need to do something about it. I was cleaning up some warning messages that nova was issuing this morning and noticed a few coming from Paste. I was going to draft a PR to fix this, but a quick browse through the

Re: [openstack-dev] [oslo] proposing Moisés Guimarães for oslo.config core

On Wed, 2018-08-01 at 09:27 -0400, Doug Hellmann wrote: > Moisés Guimarães (moguimar) did quite a bit of work on oslo.config > during the Rocky cycle to add driver support. Based on that work, > and a discussion we have had since then about general cleanup needed > in oslo.config, I think he would

Re: [openstack-dev] [all][election] PTL nominations are now closed

Excerpts from Jeremy Stanley's message of 2018-08-02 13:13:21 +: > On 2018-08-02 10:58:53 +0200 (+0200), Thierry Carrez wrote: > [...] > > Finally, RefStack: I feel like this should be wrapped into an > > Interoperability SIG, since that project team is not producing > > "OpenStack", but

Re: [openstack-dev] [all][election] PTL nominations are now closed

On 2018-08-02 10:58:53 +0200 (+0200), Thierry Carrez wrote: [...] > Finally, RefStack: I feel like this should be wrapped into an > Interoperability SIG, since that project team is not producing > "OpenStack", but helping fostering OpenStack interoperability. > Having separate groups (Interop WG,

Re: [openstack-dev] [i18n] Edge and Containers whitepapers ready for translation

Hello Ian, due the nature of the pot file format and mechanic we cant add the translators as msgid entries bc will only exist on the corresponding po file per lang said that , i think that we could create a solution using both [1] and [2] that said * adding "TRANSLATORS" msgid on pot file, so i

Re: [openstack-dev] [placement] #openstack-placement IRC channel requires registered nicks

On Thu, Aug 2, 2018 at 5:18 AM, Chris Dent wrote: > > > I thought I should post a message here for visibility that yesterday > we made the openstack-placement IRC channel +r so that the recent > spate of spammers could be blocked. > > This means that you must have a registered nick to gain

Re: [openstack-dev] [oslo] proposing Moisés Guimarães for oslo.config core

+1 2018-08-01 23:38 GMT+08:00 John Dennis : > On 08/01/2018 09:27 AM, Doug Hellmann wrote: > >> Moisés Guimarães (moguimar) did quite a bit of work on oslo.config >> during the Rocky cycle to add driver support. Based on that work, >> and a discussion we have had since then about general cleanup

Re: [openstack-dev] [nova] How to debug no valid host failures with placement

Responses to some of Jay's comments below, but first, to keep this on track with the original goal of the thread ("How to debug no valid host failures with placement") before I drag it to the side, some questions. When people ask for something like what Chris mentioned: hosts with enough

Re: [openstack-dev] [all][election] PTL nominations are now closed

Hi, I'm sorry for the inconvenience. I completely missed the nomination period. Is it possible to send in a late nomination for Dragonflow? Thanks, Omer Anson. On Thu, 2 Aug 2018 at 11:59, Thierry Carrez wrote: > Tony Breeds wrote: > > [...] > > There are 8 projects without candidates, so

[openstack-dev] [placement] #openstack-placement IRC channel requires registered nicks

I thought I should post a message here for visibility that yesterday we made the openstack-placement IRC channel +r so that the recent spate of spammers could be blocked. This means that you must have a registered nick to gain access to the channel. There's information on how to register at:

Re: [openstack-dev] [all][election] PTL nominations are now closed

Tony Breeds wrote: [...] There are 8 projects without candidates, so according to this resolution[1], the TC will have to decide how the following projects will proceed: Dragonflow, Freezer, Loci, Packaging_Rpm, RefStack, Searchlight, Trove and Winstackers. Here is my take on that...

[openstack-dev] [vitrage][ptg] Vitrage virtual PTG

Hi, As discussed in our IRC meeting yesterday [1], we will hold the Vitrage virtual PTG on the first week of October. If you would like to participate, you are welcome to add your name, time zone and ideas for discussion in the PTG etherpad[2]. [1]

Re: [openstack-dev] OpenStack lagging behind 2 major python versions: we need a Python 3.7 gate

Hi Thomas! On Thu, 2 Aug 2018 at 06:13, Thomas Goirand wrote: > On 07/12/2018 10:38 PM, Thomas Goirand wrote: > > Hi everyone! > > > > [...] > Here's more examples that shows why we should be gating earlier with > newer Python versions: > > Nova: > https://review.openstack.org/#/c/584365/ > >

Re: [openstack-dev] [all][election][tc] Lederless projects.

- Original Message - > On Wed, Aug 01, 2018 at 09:55:13AM +1000, Tony Breeds wrote: > > > > Hello all, > > The PTL Nomination period is now over. The official candidate list > > is available on the election website[0]. > > > > There are 8 projects without candidates, so according