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

On 07/13/2018 06:38 AM, Thomas Goirand wrote: > Now, both Debian and Ubuntu have Python 3.7. Every package which I > upload in Sid need to support that. Yet, OpenStack's CI is still > lagging with Python 3.5. OpenStack's CI is rather broad -- I'm going to assume we're talking about whole-system

Re: [openstack-dev] [tc] [all] TC Report 18-26

On 17/07/18 10:44, Thierry Carrez wrote: Finally found the time to properly read this... For anybody else who found the wall of text challenging, I distilled the longest part into a blog post: https://www.zerobanana.com/archive/2018/07/17#openstack-layer-model-limitations Zane Bitter

Re: [openstack-dev] [all][tc][release][election][adjutant] Welcome Adjutant as an official project!

Thanks! As the current project lead for Adjutant I welcome the news, and while I know it wasn't an easy process would like to thank everyone involved in the voting. All the feedback (good and bad) will be taken on board to make the service as suited for OpenStack as possible in the space we've

Re: [openstack-dev] [cinder][nova] Proper behavior for os-force_detach

On Tue, Jul 17, 2018 at 04:06:29PM -0300, Erlon Cruz wrote: > Hi Cinder and Nova folks, > > Working on some tests for our drivers, I stumbled upon this tempest test > 'force_detach_volume' > that is calling Cinder API passing a 'None' connector. At the time this was > added several CIs > went

Re: [openstack-dev] [tripleo] Stein blueprint - Plan to remove Keepalived support (replaced by Pacemaker)

On 07/17/2018 03:00 PM, Michele Baldessari wrote: Hi Jarda, thanks for these perspectives, this is very valuable! On Tue, Jul 17, 2018 at 06:01:21PM +0200, Jaromir Coufal wrote: Not rooting for any approach here, just want to add a bit of factors which might play a role when deciding which

Re: [openstack-dev] [tripleo] Stein blueprint - Plan to remove Keepalived support (replaced by Pacemaker)

Hi Jarda, thanks for these perspectives, this is very valuable! On Tue, Jul 17, 2018 at 06:01:21PM +0200, Jaromir Coufal wrote: > Not rooting for any approach here, just want to add a bit of factors which > might play a role when deciding which way to go: > > A) Performance matters, we should

[openstack-dev] [tc] Technical Committee update for 17 July

This is the weekly summary of work being done by the Technical Committee members. The full list of active items is managed in the wiki: https://wiki.openstack.org/wiki/Technical_Committee_Tracker We also track TC objectives for the cycle using StoryBoard at:

[openstack-dev] [cinder][nova] Proper behavior for os-force_detach

Hi Cinder and Nova folks, Working on some tests for our drivers, I stumbled upon this tempest test 'force_detach_volume' that is calling Cinder API passing a 'None' connector. At the time this was added several CIs went down, and people started discussing whether this (accepting/sending a None

[openstack-dev] [oslo][all] Heads up for the new oslo.policy release

I just wanted to send a quick note about the recent oslo.policy release which may impact some projects. Some new functionality was added that allows a context object to be passed in to the enforcer directly, but as part of that we added a check that the type of the object passed in was valid

Re: [openstack-dev] [oslo] Reminder about Oslo feature freeze

And we are now officially in feature freeze for Oslo libraries. Only bugfixes should be going in at this point. I will note that the config drivers work is still in the process of merging because some of the later patches in that series got hung up on a unit test bug. I'm holding off on

Re: [openstack-dev] [neutron] How to look up a project name from Neutron server code?

Thanks Aditya, that looks like just what I need. Best wishes, Neil On Tue, Jul 17, 2018 at 5:48 PM Aditya Vaja wrote: > hey neil, > > neutron.conf has a section called '[keystone_authtoken]’ which has > credentials to query keystone as neutron. you can read the config as you’d > typically

Re: [openstack-dev] [tc] [all] TC Report 18-26

Inlining with KF> From: Thierry Carrez [thie...@openstack.org] Sent: Tuesday, July 17, 2018 7:44 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [tc] [all] TC Report 18-26 Finally found the time to properly read this... Zane Bitter

[openstack-dev] [all][tc][release][election][adjutant] Welcome Adjutant as an official project!

The Adjutant team's application [1] to become an official project has been approved. Welcome! As I said on the review, because it is past the deadline for Rocky membership, Adjutant will not be considered part of the Rocky release, but a future release can be part of Stein. The team should

Re: [openstack-dev] [Browbeat] proposing agopi as core

agopi** On Tue, Jul 17, 2018 at 1:33 PM, Joe Talerico wrote: > Proposing > ​agopi > as core for OpenStack Browbeat. He has been instruemntal in taking over > the CI components of Browbeat. His contributions and reviews reflect that! > > Thanks! > Joe >

[openstack-dev] [Browbeat] proposing agpoi as core

Proposing agpoi as core for OpenStack Browbeat. He has been instruemntal in taking over the CI components of Browbeat. His contributions and reviews reflect that! Thanks! Joe __ OpenStack Development Mailing List (not for

Re: [openstack-dev] [neutron] How to look up a project name from Neutron server code?

hey neil, neutron.conf has a section called ' [keystone_authtoken]’ which has credentials to query keystone as neutron. you can read the config as you’d typically do from the mechanism driver for any other property using oslo.config. you could then use python-keystoneclient with those creds to

Re: [openstack-dev] [neutron] How to look up a project name from Neutron server code?

On Tue, Jul 17, 2018 at 3:55 PM Jay Pipes wrote: > On 07/17/2018 03:36 AM, Neil Jerram wrote: > > Can someone help me with how to look up a project name (aka tenant name) > > for a known project/tenant ID, from code (specifically a mechanism > > driver) running in the Neutron server? > > > > I

Re: [openstack-dev] [tripleo] Updates/upgrades equivalent for external_deploy_tasks

On 07/10/2018 04:20 PM, Jiří Stránský wrote: > Hi, > > with the move to config-download deployments, we'll be moving from > executing external installers (like ceph-ansible) via Heat resources > encapsulating Mistral workflows towards executing them via Ansible > directly (nested Ansible process

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

HTML: https://anticdent.org/tc-report-18-29.html Again a relatively slow week for TC discussion. Several members were travelling for one reason or another. A theme from the past week is a recurring one: How can OpenStack, the community, highlight gaps where additional contribution may be

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

Your fellow reporter took a break from writing, but is now back on his pen. Welcome to the twenty-fifth edition of a weekly update in TripleO world! The goal is to provide a short reading (less than 5 minutes) to learn what's new this week. Any contributions and feedback are welcome. Link to the

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

Ian raises some great points :) I'll try to address below... Ian Y. Choi wrote: Hello, When I saw overall translation source strings on container whitepaper, I would infer that new edge computing whitepaper source strings would include HTML markup tags. One of the things I discussed with Ian

Re: [openstack-dev] [tripleo] Stein blueprint - Plan to remove Keepalived support (replaced by Pacemaker)

Not rooting for any approach here, just want to add a bit of factors which might play a role when deciding which way to go: A) Performance matters, we should be improving simplicity and speed of deployments rather than making it heavier. If the deployment time and resource consumption is not

Re: [openstack-dev] [Zun] Zun UI questions

Hongbin, I just wanted to follow-up and let a fresh install of the most recent release is working with no errors. Thanks so much for your assistance! Amy (spotz) On Sun, Jul 15, 2018 at 10:49 AM, Hongbin Lu wrote: > Hi Amy, > > The wrong Keystone URI might be due to the an issue of the

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

Hello, When I saw overall translation source strings on container whitepaper, I would infer that new edge computing whitepaper source strings would include HTML markup tags. On the other hand, the source strings of edge computing whitepaper which I18n team previously translated do not include

Re: [openstack-dev] [neutron] How to look up a project name from Neutron server code?

On 07/17/2018 03:36 AM, Neil Jerram wrote: Can someone help me with how to look up a project name (aka tenant name) for a known project/tenant ID, from code (specifically a mechanism driver) running in the Neutron server? I believe that means I need to make a GET REST call as here:

Re: [openstack-dev] [tc] [all] TC Report 18-26

Finally found the time to properly read this... Zane Bitter wrote: [...] We chose to add features to Nova to compete with vCenter/oVirt, and not to add features the would have enabled OpenStack as a whole to compete with more than just the compute provisioning subset of EC2/Azure/GCP. Could

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

Frank, I'm sorry to hear about the displeasure around the Edge paper. As mentioned in a prior thread, the RST format that Akihiro worked did not work with the Zanata process that we have been using with our CMS. Additionally, the existing EDGE page is a PDF, so we had to build a new

[openstack-dev] OpenStack Summit Berlin CFP Deadline Today

Hi everyone, The CFP for the OpenStack Summit Berlin closes July 17 at 11:59pm PST (July 18 at 6:59am UTC), so make sure to press submit on your talks for: • CI/CD • Container Infrastructure • Edge

Re: [openstack-dev] [magnum] Nominate Feilong Wang for Core Reviewer

Huge +1 Cheers, Lingxian Kong On Tue, Jul 17, 2018 at 7:04 PM, Yatin Karel wrote: > +2 Well deserved. > > Welcome Feilong and Thanks for all the Great Work!!! > > > Regards > Yatin Karel > > On Tue, Jul 17, 2018 at 12:27 PM, Spyros Trigazis > wrote: > > Hello list, > > > > I'm excited to

Re: [openstack-dev] [cinder] about block device driver

yes -- Original -- From: "Ivan Kolodyazhny"; Date: Tue, Jul 17, 2018 05:00 PM To: "OpenStack Developmen"; Subject: Re: [openstack-dev] [cinder] about block device driver Do you use the volumes on the same nodes where instances are located? Regards,

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

Hi Jimmy, permission was added for you and Sebastian. The Container Whitepaper is on the Zanata frontpage now. But we removed Edge Computing whitepaper last week because there is a kind of displeasure in the team since the results of translation are still not published beside Chinese version.

Re: [openstack-dev] [cinder] about block device driver

Do you use the volumes on the same nodes where instances are located? Regards, Ivan Kolodyazhny, http://blog.e0ne.info/ On Tue, Jul 17, 2018 at 11:52 AM, Rambo wrote: > yes,My cinder driver is LVM+LIO.I have upload the test result in > appendix.Can you show me your test results?Thank you! > >

Re: [openstack-dev] [cinder] about block device driver

yes,My cinder driver is LVM+LIO.I have upload the test result in appendix.Can you show me your test results?Thank you! -- Original -- From: "Ivan Kolodyazhny"; Date: Tue, Jul 17, 2018 04:09 PM To: "OpenStack Developmen"; Subject: Re: [openstack-dev]

Re: [openstack-dev] [cinder] about block device driver

Rambo, Did you try to use LVM+LIO target driver? It shows pretty good performance comparing to BlockDeviceDriver, Regards, Ivan Kolodyazhny, http://blog.e0ne.info/ On Tue, Jul 17, 2018 at 10:24 AM, Rambo wrote: > Oh,the instances using Cinder perform intense I/O, thus iSCSI or LVM is > not a

Re: [openstack-dev] [tripleo] New "validation" subcommand for "openstack undercloud"

I opened this RFE: https://bugzilla.redhat.com/show_bug.cgi?id=1601739 Regards, Udi Kalifon; Senior QE; RHOS-UI Automation On Tue, Jul 17, 2018 at 8:42 AM, Cédric Jeanneret wrote: > > > On 07/17/2018 06:57 AM, Udi Kalifon wrote: > > We should also add support for the openstack client to

[openstack-dev] [neutron] How to look up a project name from Neutron server code?

Can someone help me with how to look up a project name (aka tenant name) for a known project/tenant ID, from code (specifically a mechanism driver) running in the Neutron server? I believe that means I need to make a GET REST call as here:

Re: [openstack-dev] [cinder] about block device driver

Oh,the instances using Cinder perform intense I/O, thus iSCSI or LVM is not a viable option - benchmarked them several times, unsatisfactory results.Sometimes it's IOPS is twice as bad,could you show me your test data?Thank you! Cheers, Rambo -- Original

Re: [openstack-dev] [magnum] Nominate Feilong Wang for Core Reviewer

+2 Well deserved. Welcome Feilong and Thanks for all the Great Work!!! Regards Yatin Karel On Tue, Jul 17, 2018 at 12:27 PM, Spyros Trigazis wrote: > Hello list, > > I'm excited to nominate Feilong as Core Reviewer for the Magnum project. > > Feilong has contributed many features like Calico

[openstack-dev] [magnum] Nominate Feilong Wang for Core Reviewer

Hello list, I'm excited to nominate Feilong as Core Reviewer for the Magnum project. Feilong has contributed many features like Calico as an alternative CNI for kubernetes, make coredns scale proportionally to the cluster, improved admin operations on clusters and improved multi-master