Re: [openstack-dev] [QA][Nova] Special scenario tests

On Thu, Apr 27, 2017 at 11:56 PM, Matt Riedemann wrote: On 4/21/2017 8:36 AM, Ferenc Horváth wrote: Dear OpenStackerz, I'd like to improve the coverage of the current test suite over some special code parts in Nova. My main target is to add a few scenarios [1] that would

Re: [openstack-dev] [horizon] [horizon-plugin] Raising Django version cap

If you want to install Django 1.11 and test it, that would be very helpful, even if its just to open bugs. I’m in the process of adding a non-voting job for 1.11 right now, so we should be able to move quickly. Rob On 5 Jul 2017, at 01:36, Adrian Turjak

Re: [openstack-dev] [User-committee] [all][tc] Turning TC/UC workgroups into OpenStack SIGs

On 27 June 2017 at 23:47, Thierry Carrez wrote: > Setting up a common ML for common discussions (openstack-sigs) will > really help, even if there will be some pain setting them up and getting > the right readership to them :) It's worth a try! I agree it will probably

Re: [openstack-dev] [docs][all][ptl] doc-migration status

For those projects using an Install Guide: Since it will be moved into your normal doc tree, you cannot merge that change without disabling the install-guide jobs. I did this now for *all* projects with the following change to allow you moving forward: https://review.openstack.org/480375

Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

Hi all, Very sorry for the delay on processing this request. I have now EOL'd stable/mitaka branches for projects listed in [1]. If there are any mistakes it should be possible to restore the branch at the correct position. Similarly please let me know if there were any projects that should have

[openstack-dev] [ironic][magnum][kolla][ansible][puppet][rally] removing SSH drivers from Ironic

Hi all, as mitaka branch was finally EOLed, Ironic team is going to proceed with removal of SSH-based power and management drivers for virtualized HW which were deprecated back in newton release. Since newton the virtualbmc-based simulation of IPMI-capable HW is officially supported, and we plan

Re: [openstack-dev] [all][tc] Turning TC/UC workgroups into OpenStack SIGs

On 27 June 2017 at 23:47, Sean Dague wrote: > I still think I've missed, or not grasped, during this thread how a SIG > functions differently than a WG, besides name. Both in theory and practice. I think for the most part SIG is just a more fitting moniker for some of these

Re: [openstack-dev] [nova][placement] Add API Sample tests for Placement APIs

Thanks for providing a bit more information on your goals, that helps shape my answers a bit more usefully. See within. On Wed, 5 Jul 2017, Shewale, Bhagyashri wrote: So I'd say the api is verified. What is missing, and could be useful, is using those tests to get accurate and up to date

Re: [openstack-dev] [mistral] External GUI for Mistral is now at github

Lingxian, good idea. Most likely, we’ll record it and share publicly. Thanks Renat Akhmerov @Nokia On 4 Jul 2017, 19:21 +0700, Lingxian Kong , wrote: > That's awesome! It'd be better if there is a demo for introduction :-) > > > Cheers, > Lingxian Kong (Larry) > > > On

Re: [openstack-dev] [ceilometer]Understandig ceilometer

Hi Gordon, Thanks for the explanations! Br, György > -Original Message- > From: gordon chung [mailto:g...@live.ca] > Sent: 2017 július 4, kedd 23:58 > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [ceilometer]Understandig ceilometer > > > > On 04/07/17 05:14

Re: [openstack-dev] [kuryr] Nominate Kirill Zaitsev as kuryr-tempest-core reviewer

+1 发件人: Irena Berezovsky 答复: OpenStack List 日期: 2017年7月5日 星期三 12:52 至: OpenStack List 主题: Re: [openstack-dev] [kuryr] Nominate Kirill Zaitsev as kuryr-tempest-core reviewer +1 On Wed, Jul 5, 2017 at

Re: [openstack-dev] [nova][placement] Add API Sample tests for Placement APIs

>>So I'd say the api is verified. What is missing, and could be useful, is >>using those tests to get accurate and up to date representations of the JSON >>request and response bodies. If that's something we'd like to pursue as I >>said in my other message the 'verbose' functionality that can

Re: [openstack-dev] [tripleo] [ui] Integration testing in tripleo-ci

On Tue, Jul 4, 2017 at 7:48 PM, Emilien Macchi wrote: > On Fri, Jun 30, 2017 at 10:51 AM, Honza Pokorny wrote: >> I'd like to write some integration tests for the TripleO UI. Simple >> configuration checks, workflow tests, websocket tests, etc. >> >> I had

Re: [openstack-dev] [congress] Using congress to improve the consistency of configuration files.

This is the classical divide between workflows and business rule engines and we think that both are useful. While the first are invaluable to make a system reach a correct state, the second describe in a more declarative way what a correct state is and can also be used as a global model of the

Re: [openstack-dev] [ironic][magnum][kolla][ansible][puppet][rally] removing SSH drivers from Ironic

On Wed, Jul 5, 2017 at 5:01 AM, Pavlo Shchelokovskyy wrote: > Hi all, > > as mitaka branch was finally EOLed, Ironic team is going to proceed with > removal of SSH-based power and management drivers for virtualized HW which > were deprecated back in newton release. >

Re: [openstack-dev] (no subject)

Hi Andy, Thank you. Yes, 15.1.6 seems good. Kind regards, Lawrence From: Andy McCrae Sent: 04 July 2017 17:31 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] (no subject) Hi Lawrence, On 4 July 2017 at 12:29,

[openstack-dev] [acceleration]No Cyborg Team Meeting today

Even the longest OpenStack team meeting need a rest for independence day :) However in the mean time please help review the open patches :) We will resume next week -- Zhipeng (Howard) Huang Standard Engineer IT Standard & Patent/IT Product Line Huawei Technologies Co,. Ltd Email:

[openstack-dev] [keystone] Queens PTG Planning

Hey all, I've started an etherpad [0] for us to collect topics and ideas for the PTG in September. I hope to follow the same planning format as last time. Everyone has the opportunity to add topics to the agenda and after some time we'll group related topics and start building a formal schedule.

[openstack-dev] [keystone] no policy meeting today

Hey all, Given the empty agenda [0] and the holiday, we will cancel the policy meeting this week. We'll pick up again next week. Thanks [0] https://etherpad.openstack.org/p/keystone-policy-meeting signature.asc Description: OpenPGP digital signature

[openstack-dev] [kolla] Today meeting cancelled due to lack of agenda

Some time to kick start brains after 4th of July:) Regards, Michal __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] [tripleo] [ui] Integration testing in tripleo-ci

On Wed, Jul 5, 2017 at 7:57 AM, Florian Fuchs wrote: > On Tue, Jul 4, 2017 at 7:48 PM, Emilien Macchi wrote: >> On Fri, Jun 30, 2017 at 10:51 AM, Honza Pokorny wrote: >>> I'd like to write some integration tests for the TripleO UI.

Re: [openstack-dev] [User-committee] [publiccloud-wg] Reminder meeting PublicCloudWorkingGroup

Thanks for the reminder Tobias. Edgar From: Tobias Rydberg Date: Tuesday, July 4, 2017 at 10:43 PM To: "user-commit...@lists.openstack.org" , "openstack-dev@lists.openstack.org" ,

Re: [openstack-dev] [tc][all][ptl] Most Supported Queens Goals and Improving Goal Completion

On 06/30/2017 04:38 AM, Thierry Carrez wrote: > Mike Perez wrote: >> [...] >> What do people think before we bikeshed on the name? Would having a >> champion volunteer to each goal to help? > It feels like most agree that having champions would help. Do we have > any volunteer for the

[openstack-dev] [tripleo] weekly meetings on #tripleo

After reading http://lists.openstack.org/pipermail/openstack-dev/2017-June/118899.html - we might want to collect TripleO's community feedback on doing weekly meetings on #tripleo instead of #openstack-meeting-alt. I see some direct benefits: - if you come up late in meetings, you could easily

Re: [openstack-dev] [tripleo] weekly meetings on #tripleo

I don't have a particularly strong opinion one way or another (probably because I tend to skip most of the meetings lately anyway...), but some thoughts inline. On 07/05/2017 11:56 AM, Emilien Macchi wrote: After reading

Re: [openstack-dev] [tripleo] weekly meetings on #tripleo

+1 On 5 Jul 2017 19:57, "Emilien Macchi" wrote: > After reading http://lists.openstack.org/pipermail/openstack-dev/2017- > June/118899.html > - we might want to collect TripleO's community feedback on doing > weekly meetings on #tripleo instead of #openstack-meeting-alt. > >

[openstack-dev] [Manila] Weekly meeting canceled

I'm not able to chair the meeting tomorrow and nobody has offered to chair the meeting in my stead so the meeting is canceled. We will meet as normal week. -Ben Swartzlander __ OpenStack Development Mailing List (not for

Re: [openstack-dev] OpenStack Operators Midcycle

Just a friendly reminder for those who are waking 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 Mon,

Re: [openstack-dev] [neutron] writable mtu

On 5 July 2017 at 14:14, Ihar Hrachyshka wrote: > Heya, > > we have https://bugs.launchpad.net/neutron/+bug/1671634 approved for > Pike that allows setting MTU for network on creation. This was actually in the very first MTU spec (in case no one looked), though it never

Re: [openstack-dev] [congress] Using congress to improve the consistency of configuration files. (OpenStack-dev Digest, Vol 63, Issue 5)

This is the classical divide between workflows and business rule engines and we think that both are useful. While the first are invaluable to make a system reach a correct state, the second describe in a more declarative way what a correct state is and can also

Re: [openstack-dev] [TripleO] quickstart failing due to unresolved dependencies

On Mon, Jul 3, 2017 at 11:18 PM, Udi Kalifon wrote: > I'm trying to install Pike. The undercloud has versions: > puppet-tripleo-7.1.1-0.20170627224658.f99b72a.el7.centos.noarch > instack-undercloud-7.1.1-0.20170619172442.4de8226.el7.centos.noarch > I think you're missing,

Re: [openstack-dev] [all][tc] Wiki

And I'd just like to point out, when was the last time you tried to find info contained in some etherpad on our etherpad server without having the etherpad's exact name? Either searched for a specific etherpad or for info you knew was somewhere on an etherpad somewhere on the

Re: [openstack-dev] [neutron] writable mtu

OK, so I should read before writing... On 5 July 2017 at 18:11, Ian Wells wrote: > On 5 July 2017 at 14:14, Ihar Hrachyshka wrote: > >> Heya, >> >> we have https://bugs.launchpad.net/neutron/+bug/1671634 approved for >> Pike that allows setting MTU

[openstack-dev] [neutron] writable mtu

Heya, we have https://bugs.launchpad.net/neutron/+bug/1671634 approved for Pike that allows setting MTU for network on creation. (but not update, as per latest comment from Kevin there) I already see a use case to modify MTU for an existing network (for example, where you enable Jumbo frames for

Re: [openstack-dev] [keystone] deprecating and removing tools/sample_data.sh

On Wed, Jul 5, 2017 at 9:36 PM, Lance Bragstad wrote: > Hi all, > > Keystone has a script to perform some bootstrapping operations [0]. It's > not really tested and its purpose has been superseded by using the > `keystone-manage bootstrap` command. Based on codesearch, only

Re: [openstack-dev] [TripleO][keystone] Pt. 2 of Passing along some field feedback

On 07/04/2017 12:58 PM, Emilien Macchi wrote: On Wed, Jun 28, 2017 at 3:47 PM, Lance Bragstad wrote: On 06/28/2017 02:29 PM, Fox, Kevin M wrote: I think everyone would benefit from a read-only role for keystone out of the box. Can we get this into keystone rather

Re: [openstack-dev] [tripleo] [ui] Integration testing in tripleo-ci

On 07/05/2017 10:21 AM, Emilien Macchi wrote: On Wed, Jul 5, 2017 at 7:57 AM, Florian Fuchs wrote: On Tue, Jul 4, 2017 at 7:48 PM, Emilien Macchi wrote: On Fri, Jun 30, 2017 at 10:51 AM, Honza Pokorny wrote: I'd like to write some

Re: [openstack-dev] [FEMDC] Use Cases

Following our discussion today, I have added a slide (see slide 11) in the google docs about not underestimating the importance of networking for our use cases. Specifically, to fully describe a use case, It would be useful to flesh out the following aspects. The performance of a specific use

Re: [openstack-dev] [nova] bug triage experimentation

On Wed, Jun 28, 2017 at 7:33 AM, Ben Nemec wrote: > > > On 06/23/2017 11:52 AM, Sean Dague wrote: >> >> The Nova bug backlog is just over 800 open bugs, which while >> historically not terrible, remains too large to be collectively usable >> to figure out where things

Re: [openstack-dev] [nova] bug triage experimentation

On Wed, Jun 28, 2017 at 7:33 AM, Ben Nemec wrote: > > > On 06/23/2017 11:52 AM, Sean Dague wrote: >> >> The Nova bug backlog is just over 800 open bugs, which while >> historically not terrible, remains too large to be collectively usable >> to figure out where things

Re: [openstack-dev] [nova] bug triage experimentation

On Fri, Jun 23, 2017 at 9:52 AM, Sean Dague wrote: > The Nova bug backlog is just over 800 open bugs, which while > historically not terrible, remains too large to be collectively usable > to figure out where things stand. We've had a few recent issues where we > just happened to

Re: [openstack-dev] [FEMDC][MassivelyDistributed] Strawman proposal for message bus analysis

Thank you Matt, This is very insightful. It helps. The second link did not work for me. In the presentation, it mentioned that the load consisted “Boot and List” operations through Rally. Did I understand well? Were those hitting the Openstack UI? Was keystone involved? Was it using Fernet or

[openstack-dev] [keystone] deprecating and removing tools/sample_data.sh

Hi all, Keystone has a script to perform some bootstrapping operations [0]. It's not really tested and its purpose has been superseded by using the `keystone-manage bootstrap` command. Based on codesearch, only openstack/rpm-packaging references the script [1]. Is anyone opposed to the