Re: [openstack-dev] [all] Python 3.6 testing is available on Fedora 26 nodes

Thanks for the follow up, it's really helpful for us to support Python 3.6 smoothly in the future. 2017-08-25 12:29 GMT+08:00 Ian Wienand : > Hello, > > In a recent discussion [1] I mentioned we could, in theory, use Fedora > 26 for Python 3.6 testing (3.6.2, to be exact).

[openstack-dev] [all] Python 3.6 testing is available on Fedora 26 nodes

Hello, In a recent discussion [1] I mentioned we could, in theory, use Fedora 26 for Python 3.6 testing (3.6.2, to be exact). After a few offline queries we have put theory into practice, sorted out remaining issues and things are working. For unit testing (tox), you can use the

[openstack-dev] [nova] nova 16.0.0.0rc2 (pike)

Hello everyone, A new release candidate for nova for the end of the Pike cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/nova/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally

Re: [openstack-dev] [ironic]clean failed after I finished

Hi,Richard: Thanks for your response,after I set the auto_clean=false,It’s OK now.I think it’ll be much better if drac driver have more detail in official docs Date: Wed, 23 Aug 2017 20:11:02 + From: > To:

Re: [openstack-dev] [neutron] [tests] [tempest] Neutron dvr tempest test problem

On Thu, Aug 24, 2017 at 5:13 AM, Luigi Toscano wrote: > On Thursday, 24 August 2017 12:51:05 CEST Ning Yao wrote: >> Hi, all >> >> I encounter a problem about neutron tempest test. I run the tempest >> neutron plugin test against my self-build OpenStack, and I find that >>

Re: [openstack-dev] [tripleo] add mistral to the auto-update package list for TripleO CI

I think I'm +0 on this. On the one hand we do have the gating job on Mistral, on the other hand our gate jobs don't exercise all of the functionality of some projects, especially Mistral. I know in the past introspection has been broken by changes in Mistral, and that wouldn't be caught by

Re: [openstack-dev] [Openstack-operators] [kolla][puppet][openstack-ansible][tripleo] Better way to run wsgi service.

I have been running api services behind uwsgi in http mode from Newton forward. I recently switched to the uwsgi+nginx model with 2 containers since I was having wierd issues with things that I couldn't track down. Mainly after I started using keystone with ldap. There would be timeouts and

[openstack-dev] [tripleo] tripleo-image-elements 7.0.0.0rc1 (pike)

Hello everyone, A new release candidate for tripleo-image-elements for the end of the Pike cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/tripleo-image-elements/ Unless release-critical issues are found that warrant a release candidate respin,

[openstack-dev] [tripleo] tripleo-puppet-elements 7.0.0.0rc1 (pike)

Hello everyone, A new release candidate for tripleo-puppet-elements for the end of the Pike cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/tripleo-puppet-elements/ Unless release-critical issues are found that warrant a release candidate

[openstack-dev] [tripleo] tripleo-heat-templates 7.0.0.0rc1 (pike)

Hello everyone, A new release candidate for tripleo-heat-templates for the end of the Pike cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/tripleo-heat-templates/ Unless release-critical issues are found that warrant a release candidate respin,

[openstack-dev] [tripleo] add mistral to the auto-update package list for TripleO CI

Greetings, I'd like to propose that the mistral project be added to the list of projects where in CI the very latest built packages are added to each CI run [1]. This will help get patches that depend on mistral patches to more quickly be tested and merged. For example Honza's patch [2] depends

[openstack-dev] [keystone] [nova] [neutron] [cinder] [ironic] [glance] [swift] Baremetal/VM SIG PTG Schedule/Etherpad

Hi all, Keystone has a few cross-project topics we'd like to share with a wider group, like the Baremetal/VM SIG. As a result, I attempted to dust off some of the Baremetal/VM sessions [0][1] from Boston and port the popular topics over to the etherpad for the PTG [2]. Maybe it will kick start

[openstack-dev] [sahara] sahara-image-elements 7.0.0.0rc2 (pike)

Hello everyone, A new release candidate for sahara-image-elements for the end of the Pike cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/sahara-image-elements/ Unless release-critical issues are found that warrant a release candidate respin,

[openstack-dev] [sahara] sahara 7.0.0.0rc2 (pike)

Hello everyone, A new release candidate for sahara for the end of the Pike cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/sahara/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally

[openstack-dev] [sahara] sahara-dashboard 7.0.0.0rc2 (pike)

Hello everyone, A new release candidate for sahara-dashboard for the end of the Pike cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/sahara-dashboard/ Unless release-critical issues are found that warrant a release candidate respin, this

[openstack-dev] [sahara] sahara-extra 7.0.0.0rc2 (pike)

Hello everyone, A new release candidate for sahara-extra for the end of the Pike cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/sahara-extra/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will

Re: [openstack-dev] [keystone] Queens PTG Planning

I've worked the topics into a schedule [0]. Monday and Tuesday are pretty general, but contain topics we need to discuss with other projects. I've left these time slots flexible for now and I'll start another thread to include other projects. Wednesday and Thursday are mostly project-specific

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

Greetings OpenStack community, Two main topics this week: Getting ready for the PTG and speculating about standards for representing singular resources in an HTTP response. The API-SIG will have a room on Monday and Tuesday at the PTG. In addition to the guided review process [6] we've

Re: [openstack-dev] [Openstack-operators] [kolla][puppet][openstack-ansible][tripleo] Better way to run wsgi service.

On Thu, Aug 24, 2017 at 11:15 AM, Jeffrey Zhang wrote: > We are moving to deploy service via WSGI[0]. > > There are two recommended ways. > > - apache + mod_wsgi > - nginx + uwsgi > > later one is more better. > > For traditional deployment, it is easy to implement. Use

[openstack-dev] [glance] priorities for THURSDAY (24 aug) and FRIDAY (25 aug)

Glance Pike RC-2 is available. Our current priorities are to test it out and report any critical bugs immediately (use the RC etherpad). We basically have Thursday and Friday to find, fix, and merge any changes for Pike. https://etherpad.openstack.org/p/glance-pike-RC-critical cheers, brian

Re: [openstack-dev] [ironic][docs] I see, you see, we all see red*

Hi Alex, Sorry, I don't know much about the docs stuff; Andreas' links were useful for enlightening me. Clearly, I'm biased and would prefer no difference in colour. What about that (darker?) blue from [0], where it sez (I'm referring to the upper-cased words here) 'Modern color theory uses

[openstack-dev] [neutron] neutron 11.0.0.0rc2 (pike)

Hello everyone, A new release candidate for neutron for the end of the Pike cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/neutron/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be

[openstack-dev] [neutron] networking-midonet 5.0.0.0rc2 (pike)

Hello everyone, A new release candidate for networking-midonet for the end of the Pike cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/networking-midonet/ Unless release-critical issues are found that warrant a release candidate respin, this

[openstack-dev] [neutron] networking-bgpvpn 7.0.0.0rc2 (pike)

Hello everyone, A new release candidate for networking-bgpvpn for the end of the Pike cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/networking-bgpvpn/ Unless release-critical issues are found that warrant a release candidate respin, this

[openstack-dev] [neutron] neutron-dynamic-routing 11.0.0.0rc2 (pike)

Hello everyone, A new release candidate for neutron-dynamic-routing for the end of the Pike cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/neutron-dynamic-routing/ Unless release-critical issues are found that warrant a release candidate

[openstack-dev] [neutron] networking-ovn 3.0.0.0rc2 (pike)

Hello everyone, A new release candidate for networking-ovn for the end of the Pike cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/networking-ovn/ Unless release-critical issues are found that warrant a release candidate respin, this candidate

[openstack-dev] [neutron] networking-sfc 5.0.0.0rc2 (pike)

Hello everyone, A new release candidate for networking-sfc for the end of the Pike cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/networking-sfc/ Unless release-critical issues are found that warrant a release candidate respin, this candidate

[openstack-dev] [neutron] neutron-fwaas 11.0.0.0rc2 (pike)

Hello everyone, A new release candidate for neutron-fwaas for the end of the Pike cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/neutron-fwaas/ Unless release-critical issues are found that warrant a release candidate respin, this candidate

[openstack-dev] [neutron] networking-bagpipe 7.0.0.0rc2 (pike)

Hello everyone, A new release candidate for networking-bagpipe for the end of the Pike cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/networking-bagpipe/ Unless release-critical issues are found that warrant a release candidate respin, this

[openstack-dev] [neutron] networking-odl 11.0.0.0rc2 (pike)

Hello everyone, A new release candidate for networking-odl for the end of the Pike cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/networking-odl/ Unless release-critical issues are found that warrant a release candidate respin, this candidate

[openstack-dev] [glance] glance 15.0.0.0rc2 (pike)

Hello everyone, A new release candidate for glance for the end of the Pike cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/glance/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally

Re: [openstack-dev] [ironic] ironic-staging-drivers core cleanup and additions

We seem to be in agreement, so I'll apply these changes. Thanks all! On 08/22/2017 11:24 AM, Dmitry Tantsur wrote: Hi all! This email concerns the ironic-staging-drivers project which is outside of the official Ironic governance. Please ignore it if you don't care about this project. I've

[openstack-dev] [tc] [all] reducing code complexity as a top-5 goal

In the rather long history of OpenStack there have been plenty of discussions about how to make sure that architectural and code complexity and various forms technical debt get the attention they deserve. Lots of different approaches from different angles; some more successful than others. One

Re: [openstack-dev] [neutron] [tests] [tempest] Neutron dvr tempest test problem

On Thursday, 24 August 2017 12:51:05 CEST Ning Yao wrote: > Hi, all > > I encounter a problem about neutron tempest test. I run the tempest > neutron plugin test against my self-build OpenStack, and I find that > tempest will run the dvr test and report NotImplementedERROR. I dig > into the test

Re: [openstack-dev] [oslo][oslo.config][ansible][tripleo][kolla][ptg] Pluggable drivers and protect plaintext secrets

So, I didn't find that topic in the TripleO umbrella[1]. Emilien, can you confirm that? If not, I have a suggestion, we can schedule into the reservable rooms and if we confirm that it will be able to do in the TripleO or any other team's agenda, we can remove it. What do you guys think? [1]

Re: [openstack-dev] [openstack-neutron] [neutron dvr tempest test problem]

On 24/08/2017 12:47, Ning Yao wrote: > Hi, all > > I encounter a problem about neutron tempest test. I run the tempest > neutron plugin test against my self-build OpenStack, and I find that > tempest will run the dvr test and report NotImplementedERROR. I dig > into the test code and find that

[openstack-dev] [neutron] [tests] [tempest] Neutron dvr tempest test problem

Hi, all I encounter a problem about neutron tempest test. I run the tempest neutron plugin test against my self-build OpenStack, and I find that tempest will run the dvr test and report NotImplementedERROR. I dig into the test code and find that even if I do not enable dvr router for my

[openstack-dev] [openstack-neutron] [neutron dvr tempest test problem]

Hi, all I encounter a problem about neutron tempest test. I run the tempest neutron plugin test against my self-build OpenStack, and I find that tempest will run the dvr test and report NotImplementedERROR. I dig into the test code and find that even if I do not enable dvr router for my

Re: [openstack-dev] [ironic][docs] I see, you see, we all see red*

Hey Ruby! Good point – thanks for bringing it up :) I was brought up to think that red was one of those colours that people had different (and sometimes really negative) associations with. When I look at our latest and greatest! ironic documentation (e.g. [1]), I see red. Not only do I see

[openstack-dev] About OpenStack's resource limit

Hi I think of  starting to use OpenStack. Because I want to monitor resource usage (CPU utilization, memory, ...etc) with OpenStack!! I have one question. Can I restrict resource with OpenStack? For example, is it possible to limit the CPU to 20 % for process that normally use 50% CPU? If

Re: [openstack-dev] [tricircle-Problem accessing the instance console]

Hi Meher, You can first check whether the nova-consoleauth and nova-novncproxy services are correctly running. If you use DevStack, the window names for these two services are n-cauth and n-novnc. BR Zhiyuan On Wed, 23 Aug 2017 at 23:55 wrote: > Hello to the Tricircle

Re: [openstack-dev] [nova] Less than 24 hours to Pike RC2

2017-08-24 11:34 GMT+08:00 Matt Riedemann : > This is just a reminder that we're in the final stretch for Pike RC2 which > happens tomorrow. > > There are a couple of fixes in flight yet for RC2 at the top of the > etherpad: > >

[openstack-dev] [infra] Request to delete some unused pages from OpenStack wiki

hi, The name of the project data protection as a service has been changed to Karbor for a long time. The name smuag is no longer needed. So some pages about smaug could be deleted from OpenStack wiki. But I don't have permissions. Hope that these pages[1] could be deleted by anyone who has