Re: [openstack-dev] [all][requirements][docs] sphinx update to 1.7.4 from 1.6.5

2018-06-25 Thread Lance Bragstad
Thanks a bunch for digging into this, Tony. I'll follow up with the oauthlib maintainers and see if they'd be interested in these changes upstream. If so, I can chip away at it. For now we'll have to settle for not treating warnings as errors to unblock our documentation gate [0]. [0]

Re: [openstack-dev] [magnum] New temporary meeting on Thursdays 1700UTC

2018-06-25 Thread Fei Long Wang
Hi Spyros, Thanks for posting the discussion output. I'm not sure I can follow the idea of simplifying CNI configuration. Though we have both calico and flannel for k8s, but if we put both of them into single one config script. The script could be very complex. That's why I think we should define

Re: [openstack-dev] [all][requirements][docs] sphinx update to 1.7.4 from 1.6.5

2018-06-25 Thread Tony Breeds
On Mon, Jun 25, 2018 at 05:42:00PM -0500, Lance Bragstad wrote: > Keystone is hitting this, too [0]. I attempted the same solution that > Tony posted, but no luck. I've even gone so far as removing every > comment from the module to see if that helps narrow down the problem > area, but sphinx

Re: [openstack-dev] [all][requirements][docs] sphinx update to 1.7.4 from 1.6.5

2018-06-25 Thread Lance Bragstad
Keystone is hitting this, too [0]. I attempted the same solution that Tony posted, but no luck. I've even gone so far as removing every comment from the module to see if that helps narrow down the problem area, but sphinx still trips. The output from the error message isn't very descriptive

Re: [openstack-dev] [nova] Adding hostId to metadata

2018-06-25 Thread Michael Still
We only bump the version if something has changed IIRC. I think bumping when nothing has changed would create a burden for implementers of client software. So its not like you get a chance to sneak this in "for free". Does this information really need to be available in the host OS? Its trivial

[openstack-dev] [nova] Adding hostId to metadata

2018-06-25 Thread Mohammed Naser
Hi everyone: While working with the OpenStack infrastructure team, we noticed that we were having some intermittent issues where we wanted to identify a theory if all VMs with this issue were landing on the same hypervisor. However, there seems to be no way of directly accessing `hostId` from

Re: [openstack-dev] [nova] Need feedback on spec for handling down cells in the API

2018-06-25 Thread Matt Riedemann
On 6/7/2018 9:02 AM, Matt Riedemann wrote: We have a nova spec [1] which is at the point that it needs some API user (and operator) feedback on what nova API should be doing when listing servers and there are down cells (unable to reach the cell DB or it times out). tl;dr: the spec proposes

Re: [openstack-dev] [Openstack-sigs] [PTG] Updates!

2018-06-25 Thread Kendall Nelson
On Mon, Jun 25, 2018 at 11:00 AM Doug Hellmann wrote: > Excerpts from Jeremy Stanley's message of 2018-06-25 16:01:11 +: > > On 2018-06-25 11:26:29 -0400 (-0400), Doug Hellmann wrote: > > > Excerpts from Thierry Carrez's message of 2018-06-25 17:15:44 +0200: > > > > Doug Hellmann wrote: > >

[openstack-dev] [neutron] Networking projects not setup properly for Zuul v3 and local testing

2018-06-25 Thread Boden Russell
It appears a number of networking related projects aren't setup properly for Zuul v3 gate jobs, as well as for local testing when it comes to pulling in dependencies from source. Since this may not be a common concept, ask yourself: "should my project's master branch source be running with and

[openstack-dev] [neutron] Bug deputy report

2018-06-25 Thread Brian Haley
Hi, I was Neutron bug deputy last week. Below is a short summary about reported bugs. Critical bugs - None High bugs - * https://bugs.launchpad.net/neutron/+bug/1777908 - Ensure _get_changed_synthetic_fields() return updatable fields - breaks consumers - Boden

Re: [openstack-dev] [Release-job-failures][release][horizon] Release of openstack/xstatic-angular-material failed

2018-06-25 Thread Sean McGinnis
> > Apart from the fix, is there any good way to detect this kind of errors in > individual project reviews? > I've added xstatic version checking to our release request validation. Once this merges, we should be able to automatically catch and error on these types of conditions:

Re: [openstack-dev] [cinder] making volume available without stopping VM

2018-06-25 Thread Sean McGinnis
> > In fact, I'm ok with delayed resize (upon power-cycle), and it's not an > issue for me that VM don't detect changes immediately. What I want to > understand is that changes to Cinder (and, thus, underlying changes to CEPH) > are safe for VM while it's in active state. > No, this is not

[openstack-dev] [masakari] Masakarimonitors EndpointNotFound Issue

2018-06-25 Thread Braian Leiva
Hello everyone, I've configured masakari-api (controller node01) and masakari-processmonitor (node02, node03 compute nodes) but I have an issue when I try to test the instance migration between nodes. The node alive can't reach to public endpoint for instance-ha. Jun 25 18:23:50 node02 python2:

[openstack-dev] OpenStack Mentorship Program Relaunch

2018-06-25 Thread Ell Marquez
Hello all, We are happy to announce the relaunch of the OpenStack Mentoring program, and we are kicking off with some changes to the program that we hope will better serve the community. Previously mentoring occurred through one on one partnering of mentor and mentee; this new program will focus

[openstack-dev] [tripleo] Referring to the --templates directory?

2018-06-25 Thread Lars Kellogg-Stedman
Is there a way to refer to the `--templates` directory when writing service templates? Existing service templates can use relative paths, as in: resources: ContainersCommon: type: ./containers-common.yaml But if I'm write a local service template (which I often do during

Re: [openstack-dev] [Openstack-sigs] [PTG] Updates!

2018-06-25 Thread Doug Hellmann
Excerpts from Jeremy Stanley's message of 2018-06-25 16:01:11 +: > On 2018-06-25 11:26:29 -0400 (-0400), Doug Hellmann wrote: > > Excerpts from Thierry Carrez's message of 2018-06-25 17:15:44 +0200: > > > Doug Hellmann wrote: > > > > Are we planning to have space for goal teams to answer > > >

Re: [openstack-dev] [ironic] SOFT_REBOOT powers off/on the server

2018-06-25 Thread Ben Nemec
A soft reboot should allow the server to shut down gracefully. A reset wouldn't do that, at least as I understand it. A reset would be more appropriate for a hard reboot, although I see Dmitry had a couple of other concerns with implementing it as a reset on the review. -Ben On 06/25/2018

Re: [openstack-dev] [cinder] making volume available without stopping VM

2018-06-25 Thread Chris Friesen
On 06/23/2018 08:38 AM, Volodymyr Litovka wrote: Dear friends, I did some tests with making volume available without stopping VM. I'm using CEPH and these steps produce the following results: 1) openstack volume set --state available [UUID] - nothing changed inside both VM (volume is still

Re: [openstack-dev] [all][requirements] we need to talk about eventlet

2018-06-25 Thread Jeremy Stanley
On 2018-06-25 10:19:50 -0500 (-0500), Matthew Thode wrote: > On 18-06-25 10:58:26, Doug Hellmann wrote: > > Excerpts from Matthew Thode's message of 2018-06-25 09:38:28 -0500: > > > On 18-06-25 08:59:23, Doug Hellmann wrote: > > > > Excerpts from Matthew Thode's message of 2018-06-24 02:42:23

Re: [openstack-dev] [Openstack-sigs] [PTG] Updates!

2018-06-25 Thread Jeremy Stanley
On 2018-06-25 11:26:29 -0400 (-0400), Doug Hellmann wrote: > Excerpts from Thierry Carrez's message of 2018-06-25 17:15:44 +0200: > > Doug Hellmann wrote: > > > Are we planning to have space for goal teams to answer > > > implementation questions? > > > > At previous PTGs the "goal rooms" ended

Re: [openstack-dev] [all][requirements] we need to talk about eventlet

2018-06-25 Thread Doug Hellmann
Excerpts from Matthew Thode's message of 2018-06-25 10:19:50 -0500: > On 18-06-25 10:58:26, Doug Hellmann wrote: > > Excerpts from Matthew Thode's message of 2018-06-25 09:38:28 -0500: > > > On 18-06-25 08:59:23, Doug Hellmann wrote: > > > > Excerpts from Matthew Thode's message of 2018-06-24

Re: [openstack-dev] [Openstack-sigs] [PTG] Updates!

2018-06-25 Thread Doug Hellmann
Excerpts from Thierry Carrez's message of 2018-06-25 17:15:44 +0200: > Doug Hellmann wrote: > > Are we planning to have space for goal teams to answer > > implementation questions? > > At previous PTGs the "goal rooms" ended up not being used (or very very > poorly-attended), so our current plan

[openstack-dev] [oslo][python3] testing the python3-first goal steps with oslo libraries

2018-06-25 Thread Doug Hellmann
We have already started some of the work to move Oslo to python3-first, and I would like to work through the remaining steps as a way of testing the goal documentation. Please take a look at the documentation [1] and let me know if you have any concerns or questions about us doing that. Thanks,

Re: [openstack-dev] [all][requirements] we need to talk about eventlet

2018-06-25 Thread Matthew Thode
On 18-06-25 10:58:26, Doug Hellmann wrote: > Excerpts from Matthew Thode's message of 2018-06-25 09:38:28 -0500: > > On 18-06-25 08:59:23, Doug Hellmann wrote: > > > Excerpts from Matthew Thode's message of 2018-06-24 02:42:23 -0500: > > > > The short of it is that we are currently using eventlet

Re: [openstack-dev] [Openstack-sigs] [PTG] Updates!

2018-06-25 Thread Thierry Carrez
Doug Hellmann wrote: Are we planning to have space for goal teams to answer implementation questions? At previous PTGs the "goal rooms" ended up not being used (or very very poorly-attended), so our current plan was to not allocate specific space, but leverage the "Ask me anything" project

Re: [openstack-dev] [all][requirements] we need to talk about eventlet

2018-06-25 Thread Doug Hellmann
Excerpts from Matthew Thode's message of 2018-06-25 09:38:28 -0500: > On 18-06-25 08:59:23, Doug Hellmann wrote: > > Excerpts from Matthew Thode's message of 2018-06-24 02:42:23 -0500: > > > The short of it is that we are currently using eventlet 0.20.0. The bot > > > proposes 0.22.1 which fails

Re: [openstack-dev] [all][requirements] we need to talk about eventlet

2018-06-25 Thread Matthew Thode
On 18-06-25 08:59:23, Doug Hellmann wrote: > Excerpts from Matthew Thode's message of 2018-06-24 02:42:23 -0500: > > The short of it is that we are currently using eventlet 0.20.0. The bot > > proposes 0.22.1 which fails updates, I think we need to start bugging > > projects that fail the cross

[openstack-dev] [manila] Rocky Review Focus

2018-06-25 Thread Tom Barron
It's less than a month till Milestone 3 so I've posted an etherpad with the new Manila driver and feature work that we've agreed to try to merge in Rocky: https://etherpad.openstack.org/p/manila-rocky-review-focus These are making good progress but in general need more review attention.

Re: [openstack-dev] [Release-job-failures] Release of openstack/xstatic-angular-material failed

2018-06-25 Thread Sean McGinnis
This release failed due to the version set in source being different than the tag being requested. I've proposed https://review.openstack.org/577828 to add checks to our validation job to catch these issues. Hopefully that will prevent this from happening again. For this release though, we will

[openstack-dev] [tc] Technical Committee update for 25 June

2018-06-25 Thread Doug Hellmann
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:

Re: [openstack-dev] [Release-job-failures][release][horizon] Release of openstack/xstatic-angular-material failed

2018-06-25 Thread Akihiro Motoki
First of all, thanks for the release team and Radomir. Apart from the fix, is there any good way to detect this kind of errors in individual project reviews? xstatic-cores have new members and all of them are not necessarily super familiar with the xstatic process. In addition, updates in xstatic

Re: [openstack-dev] [Release-job-failures][release][horizon] Release of openstack/xstatic-angular-material failed

2018-06-25 Thread Radomir Dopieralski
A fix for it is in review: https://review.openstack.org/577820 On Mon, Jun 25, 2018 at 3:07 PM, Andreas Jaeger wrote: > On 2018-06-25 14:57, Radomir Dopieralski wrote: > > Any idea where it took the 1.1.5.0 version from? > > git grep 1.1.5 shows at least: > > setup.cfg:description =

Re: [openstack-dev] [Openstack-sigs] [PTG] Updates!

2018-06-25 Thread Doug Hellmann
Are we planning to have space for goal teams to answer implementation questions? Doug Excerpts from Kendall Nelson's message of 2018-06-20 11:24:38 -0700: > Hello Everyone! > > Wanted to give you some updates on PTG4 planning. We have finalized the > list of SIGs/ Groups/WGs/Teams that are

Re: [openstack-dev] [Release-job-failures][release][horizon] Release of openstack/xstatic-angular-material failed

2018-06-25 Thread Andreas Jaeger
On 2018-06-25 14:57, Radomir Dopieralski wrote: > Any idea where it took theĀ 1.1.5.0 version from? git grep 1.1.5 shows at least: setup.cfg:description = Angular-Material 1.1.5 (XStatic packaging standard) xstatic/pkg/angular_material/__init__.py:VERSION = '1.1.5' # version of the packaged

Re: [openstack-dev] [all][requirements] we need to talk about eventlet

2018-06-25 Thread Doug Hellmann
Excerpts from Matthew Thode's message of 2018-06-24 02:42:23 -0500: > The short of it is that we are currently using eventlet 0.20.0. The bot > proposes 0.22.1 which fails updates, I think we need to start bugging > projects that fail the cross test jobs. What do you think? > By "bugging" do

Re: [openstack-dev] [Release-job-failures][release][horizon] Release of openstack/xstatic-angular-material failed

2018-06-25 Thread Radomir Dopieralski
Any idea where it took the 1.1.5.0 version from? On Mon, Jun 25, 2018 at 2:38 PM, Doug Hellmann wrote: > Excerpts from zuul's message of 2018-06-25 12:14:34 +: > > Build failed. > > > > - xstatic-check-version http://logs.openstack.org/59/ >

Re: [openstack-dev] [Release-job-failures][release][horizon] Release of openstack/xstatic-angular-material failed

2018-06-25 Thread Doug Hellmann
Excerpts from zuul's message of 2018-06-25 12:14:34 +: > Build failed. > > - xstatic-check-version > http://logs.openstack.org/59/592a9d4c90f37cd33c6f861120f41ac8a67d909b/release/xstatic-check-version/a501dba/ > : FAILURE in 1m 31s > - release-openstack-python release-openstack-python :

[openstack-dev] [ironic] SOFT_REBOOT powers off/on the server

2018-06-25 Thread Lenny Berkhovsky
Hi, Is there a reason for powering off and on[1] instead of resetting server during SOFT_REBOOT? I have a patchset[2] that resets the server instead of power cycling it. [1] https://github.com/openstack/ironic/blob/master/ironic/drivers/modules/ipmitool.py#L820 elif power_state ==

[openstack-dev] [vitrage] Vitrage was migrated to StoryBoard

2018-06-25 Thread Ifat Afek
Hi, During the weekend we have completed the Vitrage migration to StoryBoard. Vitrage bugs and blueprints should be handled in StoryBoard from now on. All Vitrage bugs have been migrated and have the same bug number as in launchpad. Regarding the blueprints, we migrated the ones that we are

Re: [openstack-dev] [stable][horizon] Adding Ivan Kolodyazhny to horizon-stable-maint

2018-06-25 Thread Ivan Kolodyazhny
Thank you Tony and Team! Regards, Ivan Kolodyazhny, http://blog.e0ne.info/ On Mon, Jun 25, 2018 at 3:06 AM, Tony Breeds wrote: > On Mon, Jun 18, 2018 at 12:03:52PM +1000, Tony Breeds wrote: > > > Without strong objections I'll do that on (my) Monday 25th June. > > Done. > > Yours Tony. > >

Re: [openstack-dev] [magnum] New temporary meeting on Thursdays 1700UTC

2018-06-25 Thread Spyros Trigazis
Hello again, After Thursday's meeting I want to summarize what we discussed and add some pointers. - Work on using the out-of-tree cloud provider and move to the new model of defining it https://storyboard.openstack.org/#!/story/1762743 https://review.openstack.org/#/c/577477/ -

Re: [openstack-dev] [cinder] making volume available without stopping VM

2018-06-25 Thread Volodymyr Litovka
Hi Jay, We have had similar issues with extending attached volumes that are iSCSI based. In that case the VM has to be forced to rescan the scsi bus. In this case I am not sure if there needs to be a change to Libvirt or to rbd or something else. I would recommend reaching out to John