[openstack-dev] [nova] Rocky RC time regression analysis

Hey everyone, During our Rocky retrospective discussion at the PTG [1], we talked about the spec freeze deadline (milestone 2, historically it had been milestone 1) and whether or not it was related to the hectic late-breaking regression RC time we had last cycle. I had an action item to go

Re: [openstack-dev] [tc] bringing back formal TC meetings

On Fri, 2018-10-05 at 07:40 -0400, Doug Hellmann wrote: > Chris Dent writes: > > > On Thu, 4 Oct 2018, Doug Hellmann wrote: > > > > > TC members, please reply to this thread and indicate if you would > > > find > > > meeting at 1300 UTC on the first Thursday of every month > > > acceptable, and

Re: [openstack-dev] [placement] update 18-40

On Fri, 5 Oct 2018 14:31:05 +0100 (BST), Chris Dent wrote: * Propose counting quota usage from placement and API database (A bit out of date but may be worth resurrecting) I'd like to resurrect this spec but it really depends on being able to

Re: [openstack-dev] [manila] [infra] remove driverfixes/ocata branch [was: Re: [cinder][infra] Remove driverfixes/ocata branch]

On 05/10/18 13:06 -0700, Clark Boylan wrote: On Fri, Oct 5, 2018, at 12:44 PM, Tom Barron wrote: Clark, would you be so kind, at your conveniencew, as to remove the manila driverfixes/ocata branch? There are no open changes on the branch and `git log origin/driverfixes/ocata

Re: [openstack-dev] [manila] [infra] remove driverfixes/ocata branch [was: Re: [cinder][infra] Remove driverfixes/ocata branch]

On Fri, Oct 5, 2018, at 12:44 PM, Tom Barron wrote: > Clark, would you be so kind, at your conveniencew, as to remove the > manila driverfixes/ocata branch? > > There are no open changes on the branch and `git log > origin/driverfixes/ocata ^origin/stable/ocata --no-merges --oneline` > reveals

[openstack-dev] [manila] [infra] remove driverfixes/ocata branch [was: Re: [cinder][infra] Remove driverfixes/ocata branch]

Clark, would you be so kind, at your conveniencew, as to remove the manila driverfixes/ocata branch? There are no open changes on the branch and `git log origin/driverfixes/ocata ^origin/stable/ocata --no-merges --oneline` reveals no commits that we need to preserve. Thanks much! -- Tom

Re: [openstack-dev] [goals][python3][heat][manila][qinling][zaqar][magnum][keystone][congress] switching python package jobs

Doug Hellmann writes: > Doug Hellmann writes: > >> Doug Hellmann writes: >> >>> I think we are ready to go ahead and switch all of the python packaging >>> jobs to the new set defined in the publish-to-pypi-python3 template >>> [1]. We still have some cleanup patches for projects that have not

Re: [openstack-dev] [goals][python3][heat][manila][qinling][zaqar][magnum][keystone][congress] switching python package jobs

Doug Hellmann writes: > Doug Hellmann writes: > >> I think we are ready to go ahead and switch all of the python packaging >> jobs to the new set defined in the publish-to-pypi-python3 template >> [1]. We still have some cleanup patches for projects that have not >> completed their zuul

[openstack-dev] [cinder][qa] Enabling online volume_extend tests by default

Hey folks, Following up on the discussions that we had on the Denver PTG, the Cinder team is planning to enable online volume_extend tests[1] to be run by default. Currently, those tests are only run by some CI systems and infra jobs that explicitly set it to be so. We are also adding a negative

Re: [openstack-dev] Sphinx testing fun

On Thu, 2018-10-04 at 18:00 -0400, Doug Hellmann wrote: > Stephen Finucane writes: > > > On Thu, 2018-10-04 at 07:21 -0400, Doug Hellmann wrote: > > > Stephen Finucane writes: > > [snip] > > > > > Anyway, we can go figure out what's changed here and handle it but this > > > > is, at best,

Re: [openstack-dev] [release][searchlight] What should I do with the missing releases?

Thank Doug. On Fri, Oct 5, 2018 at 8:42 PM Doug Hellmann wrote: > Trinh Nguyen writes: > > > Dear release team, > > > > One thing comes up in my mind when preparing for the stein-1 release of > > Searchlight that is what should we do with the missing releases (i.e. > > Rocky)? Can I just

Re: [openstack-dev] [nova][stable] Preparing for ocata-em (extended maintenance)

The ocata-em tag request is up for review: https://review.openstack.org/#/c/608296/ On 9/28/2018 11:21 AM, Matt Riedemann wrote: Per the other thread on this [1] I've created an etherpad [2] to track what needs to happen to get nova's stable/ocata branch ready for Extended Maintenance [3]

Re: [openstack-dev] [keystone] Keystone Team Update - Week of 1 October 2018

On Fri, Oct 5, 2018, 07:04 Colleen Murphy wrote: > # Keystone Team Update - Week of 1 October 2018 > > ## News > > ### JSON-home > > As Morgan works through the flaskification project, it's been clear that > some of the JSON-home[1] code could use some refactoring and that the > document itself

Re: [openstack-dev] Ryu integration with Openstack

Hi, >From what I read so far about the Dragonflow project, it implements a distributed SDN controller, ie, there is a controller running in each of the compute nodes managing the openvswitch instance in that node. This is also what currently happens with the openvswitch agent on each node running

Re: [openstack-dev] Ryu integration with Openstack

Thank you. I will have a look. Regards, Niket On Fri, Oct 5, 2018 at 4:15 PM Miguel Angel Ajo Pelayo wrote: > have a look at dragonflow project, may be it's similar to what you're > trying to accomplish > > On Fri, Oct 5, 2018, 1:56 PM Niket Agrawal wrote: > >> Hi, >> >> Thanks for the help.

Re: [openstack-dev] [placement] update 18-40

> * What should we do about nova calling the placement db, like in >   > [nova-manage](https://github.com/openstack/nova/blob/master/nova/cmd/manage.py#L416) This should be purely a placement-side migration, nah? >   and >   >

Re: [openstack-dev] Ryu integration with Openstack

have a look at dragonflow project, may be it's similar to what you're trying to accomplish On Fri, Oct 5, 2018, 1:56 PM Niket Agrawal wrote: > Hi, > > Thanks for the help. I am trying to run a custom Ryu app from the nova > compute node and have all the openvswitches connected to this new >

Re: [openstack-dev] [Horizon] Horizon tutorial didn`t work

Hi Jea-Min, I filed a bug [1] and proposed a fix for it [2] [1] https://bugs.launchpad.net/horizon/+bug/1796312 [2] https://review.openstack.org/608274 Regards, Ivan Kolodyazhny, http://blog.e0ne.info/ On Tue, Oct 2, 2018 at 6:55 AM Jea-Min Lim wrote: > Thanks for the reply. > > If you need

[openstack-dev] [keystone] Keystone Team Update - Week of 1 October 2018

# Keystone Team Update - Week of 1 October 2018 ## News ### JSON-home As Morgan works through the flaskification project, it's been clear that some of the JSON-home[1] code could use some refactoring and that the document itself is inconsistent[2], but we're unclear whether anyone uses this

[openstack-dev] [placement] update 18-40

HTML: https://anticdent.org/placement-update-18-40.html Here's this week's placement update. We remain focused on specs and pressing issues with extraction, mostly because until the extraction is "done" in some form doing much other work is a bit premature. # Most Important There have been

Re: [openstack-dev] [nova] [ironic] agreement on how to specify options that impact scheduling and configuration

Added [ironic] topic. On 10/04/2018 06:06 PM, Chris Friesen wrote: While discussing the "Add HPET timer support for x86 guests" blueprint[1] one of the items that came up was how to represent what are essentially flags that impact both scheduling and configuration.  Eric Fried posted a spec

Re: [openstack-dev] [tc] bringing back formal TC meetings

+1 to bringing back formal meetings. A few replies below regarding time/agenda. On Fri, Oct 5, 2018 at 5:38 AM Doug Hellmann wrote: > Thierry Carrez writes: > > > Ghanshyam Mann wrote: > >> On Fri, 05 Oct 2018 02:47:53 +0900 Jeremy Stanley < > fu...@yuggoth.org> wrote > >> > On

[openstack-dev] [puppet] Heads up for changes causing restarts!

Hello, Due to bugs and fixes that has been needed we are probably going to merge some changes to Puppet modules which will cause a refresh of their services meaning they will be restarted. If you are following the stable branches (stable/rocky in this case) and not using tagged releases

Re: [openstack-dev] Ryu integration with Openstack

Hi, Thanks for the help. I am trying to run a custom Ryu app from the nova compute node and have all the openvswitches connected to this new controller. However, to be able to run this new app, I have to first stop the existing neutron openvswitch agents in the same node as they run Ryu app

Re: [openstack-dev] [Distutils] pip 18.1 has been released!

Watch for changes in pip's behavior. - Doug Pradyun Gedam writes: > On behalf of the PyPA, I am pleased to announce that pip 18.1 has just > been released. > > To install pip 18.1, you can run:: > > python -m pip install --upgrade pip > > or use get-pip as described in >

Re: [openstack-dev] [api] Open API 3.0 for OpenStack API

GraphQL has introspection features that allow clients to pull the schema (types, queries, mutations, etc): https://graphql.org/learn/introspection/ That said, it seems like using this in a client like OpenStackSDK would get messy quickly. Instead of asking for which versions are supported, you'd

Re: [openstack-dev] [all][Searchlight] Always build universal wheels

On 2018-10-05 07:20:01 -0400 (-0400), Doug Hellmann wrote: [...] > So, I think this all means we can leave the setup.cfg files as > they are and not worry about updating the wheel format flag. I continue to agree that, because of the reasons you state, it is not urgent to update setup.cfg (either

Re: [openstack-dev] [tc] bringing back formal TC meetings

On 2018-10-05 07:40:00 -0400 (-0400), Doug Hellmann wrote: [...] > I had in mind "email the chair your topic suggestion" and then "the > chair emails the agenda to openstack-dev tagged [tc] a bit in advance of > the meeting". There would also probably be some standing topics, like > updates for

Re: [openstack-dev] [release][searchlight] What should I do with the missing releases?

Trinh Nguyen writes: > Dear release team, > > One thing comes up in my mind when preparing for the stein-1 release of > Searchlight that is what should we do with the missing releases (i.e. > Rocky)? Can I just ignore it or do I have to create a branch for it? There was no rocky release, so I

Re: [openstack-dev] [tc] bringing back formal TC meetings

Chris Dent writes: > On Thu, 4 Oct 2018, Doug Hellmann wrote: > >> TC members, please reply to this thread and indicate if you would find >> meeting at 1300 UTC on the first Thursday of every month acceptable, and >> of course include any other comments you might have (including alternate >>

Re: [openstack-dev] [tc] bringing back formal TC meetings

Thierry Carrez writes: > Ghanshyam Mann wrote: >> On Fri, 05 Oct 2018 02:47:53 +0900 Jeremy Stanley >> wrote >> > On 2018-10-04 13:40:05 -0400 (-0400), Doug Hellmann wrote: >> > [...] >> > > TC members, please reply to this thread and indicate if you would >> > > find

Re: [openstack-dev] [api] Open API 3.0 for OpenStack API

Gilles Dubreuil writes: >> About the micro version, we discuss with your team mate dmitry in >> another email [1] > > Obviously micro version is a point of contention. > My take on this is because consuming them has been proven harder than > developing them. > The beauty of GraphQL is that

Re: [openstack-dev] [all] Zuul job backlog

Abhishek Kekane writes: > Hi Matt, > > Thanks for the input, I guess I should use ' > http://git.openstack.org/static/openstack.png' which will definitely work. > Clark, Matt, Kindly let me know your opinion about the same. That URL would not be on the local node running the test, and would

Re: [openstack-dev] [all][Searchlight] Always build universal wheels

Trinh Nguyen writes: > Thank Jeremy, Doug for explaining. > > On Fri, Oct 5, 2018 at 6:54 AM Doug Hellmann wrote: > >> Jeremy Stanley writes: >> >> > On 2018-10-04 23:11:22 +0900 (+0900), Trinh Nguyen wrote: >> > [...] >> >> Please avoid adding universal wheels to the project setup.cfg. >> >

[openstack-dev] Monasca agent problem

Hello, I have an issue with the monasca Agent. In fact, I installed monasca with Openstack using devstack. I want to minitor now the instances deployed using Openstack. For that I installed on each instance the monasca agent with the following link:

[openstack-dev] [release][searchlight] What should I do with the missing releases?

Dear release team, One thing comes up in my mind when preparing for the stein-1 release of Searchlight that is what should we do with the missing releases (i.e. Rocky)? Can I just ignore it or do I have to create a branch for it? Thanks and regards, -- *Trinh Nguyen* *www.edlab.xyz

Re: [openstack-dev] [tc] bringing back formal TC meetings

On Thu, 4 Oct 2018, Doug Hellmann wrote: TC members, please reply to this thread and indicate if you would find meeting at 1300 UTC on the first Thursday of every month acceptable, and of course include any other comments you might have (including alternate times). +1 Also, if we're going to

Re: [openstack-dev] [tc] bringing back formal TC meetings

Ghanshyam Mann wrote: On Fri, 05 Oct 2018 02:47:53 +0900 Jeremy Stanley wrote > On 2018-10-04 13:40:05 -0400 (-0400), Doug Hellmann wrote: > [...] > > TC members, please reply to this thread and indicate if you would > > find meeting at 1300 UTC on the first Thursday of

Re: [openstack-dev] [tc] bringing back formal TC meetings

On Fri, 05 Oct 2018 02:47:53 +0900 Jeremy Stanley wrote > On 2018-10-04 13:40:05 -0400 (-0400), Doug Hellmann wrote: > [...] > > TC members, please reply to this thread and indicate if you would > > find meeting at 1300 UTC on the first Thursday of every month > >

Re: [openstack-dev] [api] Open API 3.0 for OpenStack API

Hi Edison, Sorry for the delay. Please see inline... Cheers, Gilles On 07/09/18 12:03, Edison Xiang wrote: Hey gilles, Thanks your introduction for GraphQL and Relay. > GraphQL and OpenAPI have a different feature scope and both have pros and cons. I totally agree with you. They can work