Re: [openstack-dev] OpenStack Operators Midcycle

Just a friendly reminder for those who are up on the other side of the globe. Please take a moment to put some ideas for sessions in the etherpad - https://etherpad.openstack.org/p/MEX-ops-meetup Even if you are not able to make the midcycle, please take time to propose sessions. On Wed, Jul 5,

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

On Jul 14, 2017, at 14:10, Ed Leafe wrote: > > On Jul 14, 2017, at 2:17 PM, Zane Bitter wrote: > >> * The pool of OpenStack developers is a fixed resource, and if we make it >> clear that some projects are unwelcome then their developers will be >>

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

On 15/07/17 03:45, Ed Leafe wrote: On Jul 13, 2017, at 10:32 PM, Fei Long Wang wrote: I agree with Zane for most of the parts. But one thing I don't really understand is, why OpenStack community is still confusing at the IaaS, PaaS and SaaS, does the classification

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

On Jul 14, 2017, at 2:17 PM, Zane Bitter wrote: > * The pool of OpenStack developers is a fixed resource, and if we make it > clear that some projects are unwelcome then their developers will be > reassigned to 'core' projects in a completely zero-sum process. (Nnope.)

[openstack-dev] [all] Proposal to change integrated neutron grenade gate job to multi-node

Hi, While looking at ways to reduce the number of jobs we run in the Neutron gate, I found we ran two very similar jobs for some projects: gate-grenade-dsvm-neutron-ubuntu-xenial (single-node job) gate-grenade-dsvm-neutron-multinode-ubuntu-xenial (2-node job) We talked about this in the

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

On 07/14/2017 11:43 AM, Joshua Harlow wrote: Out of curiosity, since I keep on hearing/reading all the tripleo discussions on how tripleo folks are apparently thinking/doing? redesigning the whole thing to use ansible + mistral + heat, or ansible + kubernetes or ansible + mistral + heat +

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

Part of the confusion I think is in the different ways helm can be used. Helm can be used to orchestrate the deployment of a whole service (ex, nova). "launch these 3 k8s objects, template out this config file, run this job to init the db, or this job to upgrade the db, etc", all as a single

Re: [openstack-dev] [kolla] Looking for Docker images for Cinder, Glance etc for oVirt

Hello, If it helps, we are building on a regular basis a subset of the kolla images. They are pushed in dockerhub under beyondtheclouds namespace [1]. stable/ocata images should be up-to-date, master is tagged latest. Nevertheless some caveats of relying on those tags are mentionned in this

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

On Fri, Jul 14, 2017 at 3:38 PM, Steven Dake wrote: > > > On Fri, Jul 14, 2017 at 10:26 AM, James Slagle > wrote: >> > James, > >> >> Just to frame the conversation with a bit more context, I'm sure there >> are many individual features/bugs/special

Re: [openstack-dev] [keystone] stable/ocata and stable/newton are broken

All the patches in the original note have merged for both stable/ocata and stable/newton. Existing patches to both branches are being recheck and rebased. On 07/13/2017 06:04 PM, Lance Bragstad wrote: > Oh - the original issues with the stable branches were reported here: > >

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

On Fri, Jul 14, 2017 at 10:26 AM, James Slagle wrote: > On Fri, Jul 14, 2017 at 12:16 PM, Fox, Kevin M wrote: > > https://xkcd.com/927/ > > That's cute, but we aren't really trying to have competing standards. > It's not really about competition

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

On 13/07/17 23:32, Fei Long Wang wrote: I agree with Zane for most of the parts. But one thing I don't really understand is, why OpenStack community is still confusing at the IaaS, PaaS and SaaS, does the classification really mater at nowadays? Do we really need a label/tag for OpenStack to

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

I actually like the idea of moving to kolla-kubernetes. I guess there would be a bunch of work towards giving folks an upgrade path and reaching feature parity; but this would happen anyway eurgh the switch to kubernetes. And this would have the added value of merging two communities, thus more

Re: [openstack-dev] [all] New setuptools release, and the world is broken

Excerpts from Jeremy Stanley's message of 2017-07-14 16:18:04 +: > On 2017-07-14 16:05:36 + (+), Jesse Pretorius wrote: > > On 7/14/17, 4:54 PM, "Doug Hellmann" wrote: > [...] > > > I wonder if we could convince the PyPA folks to allow get-pip.py > > >to

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

On Fri, Jul 14, 2017 at 12:16 PM, Fox, Kevin M wrote: > https://xkcd.com/927/ That's cute, but we aren't really trying to have competing standards. It's not really about competition between tools. > I don't think adopting helm as a dependency adds more complexity then

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

Excerpts from Bogdan Dobrelya's message of 2017-07-14 18:14:42 +0200: > On 14.07.2017 17:55, Michał Jastrzębski wrote: > > Guys you just described Kolla-Kubernetes pretty much... how about > > we join effort and work towards this goal together? > > That's exactly that I'd like we all to do. >

[openstack-dev] [horizon] [keystone] [requirements] [rpm-packaging] [deb-packaging] Merging Django OpenStack Auth with Horizon

Apologies in advance for so many tags, hoping this is seen by the appropriate people. I've put up a patch to merge Django OpenStack Auth (DOA) into the Horizon tree: https://review.openstack.org/#/c/482561/ There is a blueprint to track any further changes / issues here:

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

On 07/14/2017 06:16 PM, Fox, Kevin M wrote: https://xkcd.com/927/ I don't think adopting helm as a dependency adds more complexity then writing more new k8s object deployment tooling? I don't know much about the containerization work, and I don't have a big say in TripleO, but that's the

[openstack-dev] [nova] placement/resource providers update 28

Placement update 28. # What Matters Most Still claims in the scheduler. It's getting closer, the current hiccup is dealing with things like a resize on the same host. Diligent work and discussion in progress. The related changes are in the stack near:

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

First and foremost I just realized that I forgot to tag kolla and openstack-helm in the subject so, I apologize. I'm glad the subject was catchy enough to get your attention. Just want to raise here what I just mentioned on IRC: It's late in EU so I shouldn't be here right now but, I do want to

Re: [openstack-dev] [all] New setuptools release, and the world is broken

On 7/14/17, 5:18 PM, "Jeremy Stanley" wrote: >Is there a mechanism to leverage this in tox or when invoking >virtualenv? We don't run get-pip.py in most jobs because our images >have pip/setuptools preinstalled to get around bootstrapping issues, >though I

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

Out of curiosity, since I keep on hearing/reading all the tripleo discussions on how tripleo folks are apparently thinking/doing? redesigning the whole thing to use ansible + mistral + heat, or ansible + kubernetes or ansible + mistral + heat + ansible (a second time!) or ... Seeing all those

Re: [openstack-dev] [all] New setuptools release, and the world is broken

On 2017-07-14 15:55:40 + (+), Jesse Pretorius wrote: > I did a little spelunking to try and figure out where it is we put > pip onto the nodepool nodes. It appears that d-i-b for Ubuntu > Xenial uses packages to put it there, but that doesn’t explain how > the latest version got there.

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

On 14.07.2017 18:16, Fox, Kevin M wrote: > https://xkcd.com/927/ > > I don't think adopting helm as a dependency adds more complexity then writing > more new k8s object deployment tooling? > > There are efforts to make it easy to deploy kolla-kubernetes microservice > charts using ansible for

Re: [openstack-dev] [all] New setuptools release, and the world is broken

On 2017-07-14 16:05:36 + (+), Jesse Pretorius wrote: > On 7/14/17, 4:54 PM, "Doug Hellmann" wrote: [...] > > I wonder if we could convince the PyPA folks to allow get-pip.py > >to take a version argument, so we could specify which version we want in > >our

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

https://xkcd.com/927/ I don't think adopting helm as a dependency adds more complexity then writing more new k8s object deployment tooling? There are efforts to make it easy to deploy kolla-kubernetes microservice charts using ansible for orchestration in kolla-kubernetes. See:

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

On 14.07.2017 17:55, Michał Jastrzębski wrote: > Guys you just described Kolla-Kubernetes pretty much... how about > we join effort and work towards this goal together? That's exactly that I'd like we all to do. > > On 14 July 2017 at 08:43, Flavio Percoco wrote: >> On

Re: [openstack-dev] [all] New setuptools release, and the world is broken

On 7/14/17, 4:54 PM, "Doug Hellmann" wrote: > I wonder if we could convince the PyPA folks to allow get-pip.py >to take a version argument, so we could specify which version we want in >our jobs. We would still need a way to manage that version number, but >

Re: [openstack-dev] [all] New setuptools release, and the world is broken

On 7/14/17, 4:17 PM, "Jeremy Stanley" wrote: >Chicken and egg. Once you get to the point where pip can enforce > constraints, you already have a version of setuptools installed. And >as evidenced by, for example, this current bug you would just end up >breaking

Re: [openstack-dev] [all] New setuptools release, and the world is broken

Excerpts from Jeremy Stanley's message of 2017-07-14 15:17:52 +: > On 2017-07-14 10:50:50 -0400 (-0400), Doug Hellmann wrote: > > Excerpts from Jesse Pretorius's message of 2017-07-14 08:32:48 +: > > > FYI if you see the following error in your job logs, you have the new > > > setuptools

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

Guys you just described Kolla-Kubernetes pretty much... how about we join effort and work towards this goal together? On 14 July 2017 at 08:43, Flavio Percoco wrote: > On 14/07/17 17:26 +0200, Bogdan Dobrelya wrote: >> >> On 14.07.2017 11:17, Flavio Percoco wrote: >>> >>>

Re: [openstack-dev] [trove][all][tc] A proposal to rearchitect Trove

Yeah. Understood. Just was responding to the question, why you would ever want to do X. There are reasons. Being out of scope is an ok answer though. Thanks, Kevin From: Amrith Kumar [amrith.ku...@gmail.com] Sent: Thursday, July 13, 2017 9:22 PM To: OpenStack

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

On 14.7.2017 11:17, Flavio Percoco wrote: Greetings, As some of you know, I've been working on the second phase of TripleO's containerization effort. This phase if about migrating the docker based deployment onto Kubernetes. These phase requires work on several areas: Kubernetes deployment,

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

On 14/07/17 17:26 +0200, Bogdan Dobrelya wrote: On 14.07.2017 11:17, Flavio Percoco wrote: Greetings, As some of you know, I've been working on the second phase of TripleO's containerization effort. This phase if about migrating the docker based deployment onto Kubernetes. These phase

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

On Jul 13, 2017, at 10:32 PM, Fei Long Wang wrote: > I agree with Zane for most of the parts. But one thing I don't really > understand is, why OpenStack community is still confusing at the IaaS, > PaaS and SaaS, does the classification really mater at nowadays? Do we >

Re: [openstack-dev] [tripleo] containers-multinode-upgrades-nv is stable, please respect the results

Thanks Jirka. +1 with what you said, of course. Just some context on "why the job isn't voting NOW": https://review.openstack.org/#/c/479198/ Any feedback from folks working on CI & promotions is welcome. Thanks, On Fri, Jul 14, 2017 at 8:28 AM, Jiří Stránský wrote: > Hi all,

[openstack-dev] [tripleo] containers-multinode-upgrades-nv is stable, please respect the results

Hi all, i'm just sending this plea -- let's pay attention to the containers-multinode-upgrades-nv job results in the CI please, and treat it as voting if possible. There's been a fair amount of breakage lately but all was caused by merging TripleO patches on which the job failed. The job in

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

On 14.07.2017 11:17, Flavio Percoco wrote: > > Greetings, > > As some of you know, I've been working on the second phase of TripleO's > containerization effort. This phase if about migrating the docker based > deployment onto Kubernetes. > > These phase requires work on several areas:

Re: [openstack-dev] [all] New setuptools release, and the world is broken

On 2017-07-14 10:50:50 -0400 (-0400), Doug Hellmann wrote: > Excerpts from Jesse Pretorius's message of 2017-07-14 08:32:48 +: > > FYI if you see the following error in your job logs, you have the new > > setuptools to thank: > > > > AttributeError: Distribution instance has no attribute

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

On Fri, Jul 14, 2017 at 2:17 AM, Flavio Percoco wrote: > > Greetings, > > As some of you know, I've been working on the second phase of TripleO's > containerization effort. This phase if about migrating the docker based > deployment onto Kubernetes. > > These phase requires

Re: [openstack-dev] [all] New setuptools release, and the world is broken

Excerpts from Jesse Pretorius's message of 2017-07-14 08:32:48 +: > FYI if you see the following error in your job logs, you have the new > setuptools to thank: > > AttributeError: Distribution instance has no attribute 'install_requires' > > I’ve registered

Re: [openstack-dev] [kolla] Looking for Docker images for Cinder, Glance etc for oVirt

Also, For what it's worth, Cinder has a docker compose contrib directory here that we merged a month or so ago for standing up cinder. https://github.com/openstack/cinder/tree/master/contrib/block-box On Sat, Jul 8, 2017 at 2:03 PM, Leni Kadali Mutungi wrote: > Hello

Re: [openstack-dev] Website shows talk submission closed - its not 11:59 PM PST yet

Our apologies for the problem! An automated timer went off and closed the CFP erroneously. It is now up and running. Please proceed to your submission and complete the process. Thank you, Jimmy Chandan kumar July 14, 2017 at 9:39 AM Hi I am unable to submit a

[openstack-dev] [docs][all] trouble enabling warning-is-error due to "already registered" warnings

tl;dr - A few project that use wsme.sphinxext or some other extensions that register similar directives multiple times have been unable to turn on the warning-is-error flag as part of the doc migration. The solution to that problem is to add some warning suppression information to the local

Re: [openstack-dev] [OpenStack-Dev][Nova] - https://launchpad.net/bugs/1667794 Changing hostname not to be treated as a pattern instead exact match will be done.

On 7/14/2017 6:49 AM, nidhi.h...@wipro.com wrote: Hello all, This is regarding bug 1667794 as mentioned in subject. Its review is going on here. https://review.openstack.org/#/c/474949/ *_Bug is - _**_Nova treats hostname as pattern_* *_Description_* Nova commands such as "hypervisor-list

[openstack-dev] CFP Closes today - Get your Presentations in!

Hi everyone, Don't forget - Call for Presentations for the OpenStack Summit Sydney closes *today at 11:59PM Pacific Time (July 15 at 6:59 UTC)!* Submit your proposals before the deadline. Interested in how the speaking

Re: [openstack-dev] [oslo][all] next week is deadline for final release for non-client libraries

Just a reminder, I will add final releases of oslo libraries for Pike on next Monday. 2017-07-10 22:37 GMT+08:00 ChangBo Guo : > OpenStackers, > > According to Pike Schedule https://releases.openstack. > org/pike/schedule.html > > Jul 17 - Jul 21 is the deadline for final

[openstack-dev] [OpenStack-Dev][Nova] - https://launchpad.net/bugs/1667794 Changing hostname not to be treated as a pattern instead exact match will be done.

Hello all, This is regarding bug 1667794 as mentioned in subject. Its review is going on here. https://review.openstack.org/#/c/474949/ Bug is - Nova treats hostname as pattern Description Nova commands such as "hypervisor-list --matching ", host-evacuate-live and host-evacuate and few more,

Re: [openstack-dev] [masakari]Where is the masakari-monitors spec repository?

Hi Sampath, Thank you for suggesting! I will use masakari-spec repo! On 2017/07/14 19:11, Sam P wrote: Hi Honjo, There are no dedicated spec repositories for masakari-monitors and python-masakariclient. Please use the masakari-spec repository[1] for spec discussion for those 2 projects.

Re: [openstack-dev] [masakari]Where is the masakari-monitors spec repository?

Hi Honjo, There are no dedicated spec repositories for masakari-monitors and python-masakariclient. Please use the masakari-spec repository[1] for spec discussion for those 2 projects. [1] https://review.openstack.org/#/q/project:openstack/masakari-specs --- Regards, Sampath On Fri, Jul

[openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

Greetings, As some of you know, I've been working on the second phase of TripleO's containerization effort. This phase if about migrating the docker based deployment onto Kubernetes. These phase requires work on several areas: Kubernetes deployment, OpenStack deployment on Kubernetes,

[openstack-dev] [all] New setuptools release, and the world is broken

FYI if you see the following error in your job logs, you have the new setuptools to thank: AttributeError: Distribution instance has no attribute 'install_requires' I’ve registered https://github.com/pypa/setuptools/issues/1086 to track the issue, and very quickly got a response and there’s a

Re: [openstack-dev] [rpm-packaging][karbor]

Message: 2 Date: Fri, 14 Jul 2017 12:10:00 +0530 From: Chandan kumar To: "OpenStack Development Mailing List (not for usage questions)" Subject: Re: [openstack-dev] [rpm-packaging][karbor] Message-ID:

Re: [openstack-dev] [rpm-packaging][karbor]

On Fri, Jul 14, 2017 at 12:10 PM, Chandan kumar wrote: > Hello Jiong, > > Thank you for packaging karbor. > > On Fri, Jul 14, 2017 at 11:49 AM, Jiong Liu wrote: >> Hello rpm-packaging team and folks, >> >> >> >> I got trouble with packaging OpenStack

[openstack-dev] [masakari]Where is the masakari-monitors spec repository?

Hi all, I want to push a new spec document of masakari-monitors. But there is not a masakari-monitors-spec repository. Can I push it to masakari-spec repository? Best regards, -- _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ Rikimaru Honjo E-mail:honjo.rikim...@po.ntt-tx.co.jp

Re: [openstack-dev] [rpm-packaging][karbor]

Hello Jiong, Thank you for packaging karbor. On Fri, Jul 14, 2017 at 11:49 AM, Jiong Liu wrote: > Hello rpm-packaging team and folks, > > > > I got trouble with packaging OpenStack project(karbor), which depends on two > packages: icalendar and abclient. > > icalendar

[openstack-dev] [rpm-packaging][karbor]

Hello rpm-packaging team and folks, I got trouble with packaging OpenStack project(karbor), which depends on two packages: icalendar and abclient. icalendar has pip package and RPM package, but RPM package can not be found by RDO CI. While abclient only has pip package but no RPM package.