Re: [openstack-dev] Mesos Conductor using container-create operations

[1]https://review.openstack.org/#/c/252789/ From: bharath_...@hotmail.com To: openstack-dev@lists.openstack.org Date: Wed, 9 Dec 2015 10:10:17 +0530 Subject: [openstack-dev] Mesos Conductor using container-create operations Hi, As we have discussed in last meeting, we cannot continue with chan

Re: [openstack-dev] [Neutron] Evolving the stadium concept

On 3 December 2015 at 02:21, Thierry Carrez wrote: > Armando M. wrote: > > On 2 December 2015 at 01:16, Thierry Carrez > > wrote: > >> Armando M. wrote: > >> >> One solution is, like you mentioned, to make some (or all) of > them > >> >> full-fledged pro

[openstack-dev] [tricircle]weekly meeting of Dec.9

Hi, Let’s have regular meeting today starting UTC1300 at #openstack-meeting Agenda: Progress of To-do list: https://etherpad.openstack.org/p/TricircleToDo Discussion of stateless design. Best Regards Chaoyi Huang ( Joe Huang ) From: joehuang [mailto:joehu...@huawei.com] Sent: Tuesday, December

[openstack-dev] [Tacker][Tricircle]Multi-VIM collaboration

Hi Tacker team, As I commented in the BP[1], our team is interested in a collaboration in this area. I think one of the collaboration point would be to define a mapping between tacker multi-vim api with Tricircle resource routing api table [2]. [1]https://review.openstack.org/#/c/249085/ [2] http

Re: [openstack-dev] [Fuel] FFE for Ubuntu bootstrap

+1 to extend FFE by 1 day Nastya. On Tue, Dec 8, 2015 at 9:51 PM, Dmitry Klenov wrote: > Hi Folks, > > I would like to ask for FFE extension by 1 day. Reason: we didn't have > green BVT today due to BUD network connectivity issue. > > Commits to merge: > >- https://review.openstack.org/#/c

Re: [openstack-dev] [all] using reno for release note management

On Wed, Dec 9, 2015 at 3:33 AM, Emilien Macchi wrote: > This morning the Puppet OpenStack had the weekly meeting [1] and we > discussed about using reno [2] for release note management. > > We saw three possibilities: > > 1/ we use reno and enforce each contributions (bugfix, feature, etc) to > a

Re: [openstack-dev] [nova] jsonschema for scheduler hints

2015-12-09 6:02 GMT+09:00 Andrew Laski : >> >> I'm fine with a new RPC call for getting the schema, but as I explained, I >> think the schema should be accepting all the in-tree filter hints (ie. >> nova.scheduler.filters.all_filters method), not only those which are enabled >> (ie. scheduler_defau

Re: [openstack-dev] [Neutron] [Tempest] where fwaas tempest tests should be?

hi, On Sat, Oct 24, 2015 at 9:25 PM, Doug Wiegley wrote: > >> On Oct 19, 2015, at 5:33 PM, Ihar Hrachyshka wrote: >> >>> On 16 Oct 2015, at 10:50, Takashi Yamamoto wrote: >>> >>> if i move fwaas tests from neutron to neutron-fwaas, [1] >>> is there easy way to run them together with the rest of

Re: [openstack-dev] [nova] jsonschema for scheduler hints

Hi Sylvain, 2015-12-04 17:48 GMT+09:00 Sylvain Bauza : >> >> That leaves the out-of-tree discussion about custom filters and how we >> could have a consistent behaviour given that. Should we accept something in >> a specific deployment while another deployment could 401 against it ? Mmm, >> bad to

[openstack-dev] Mesos Conductor using container-create operations

Hi, As we have discussed in last meeting, we cannot continue with changes in container-create[1] as long as we have suitable use case. But I honestly feel to have some kind of support for mesos + marathon apps, because magnum supports COE related functionalities for docker swarm (container-creat

Re: [openstack-dev] [keystone][doc][tempest] What title should be for OS-KSCRUD extension

Hi Dolph, Thank you for your quick feedback, 2015-12-09 12:33 GMT+09:00 Dolph Mathews : > I just noticed you suggested " "; if that's the prevailing > form, then I'd suggest "Change password (self-service)". Nice title for the api-site. Now Tempest's method is update_user_own_password() which ca

[openstack-dev] [Openstack-operators] [keystone] Removing functionality that was deprecated in Kilo and upcoming deprecated functionality in Mitaka

Hi All: Just to inform Steve and all the folks who brought up this talk ;We did some benchmarking using wsgi, apache and nginx for keystone with mysql as token backend and we got following results on Juno version. Hence I am just giving you brief highlight about the results we got. spawning

[openstack-dev] [cinder] Dependencies of snapshots on volumes

Hi all, Currently when deleting a volume, it checks whether there are snapshots created from it. If yes deletion is prohibited. But it allows to extend the volume, no check whether there are snapshots from it. The two behaviors in Cinder are not consistent from my viewpoint. In backend sto

Re: [openstack-dev] [Openstack-operators] [keystone] Removing functionality that was deprecated in Kilo and upcoming deprecated functionality in Mitaka

Hi All: Just to inform Steve and all the folks who brought up this talk ;We did some benchmarking using wsgi, apache and nginx for keystone with mysql as token backend and we got following results on Juno version. Hence I am just giving you brief highlight about the results we got. spawning 100

Re: [openstack-dev] [keystone][doc][tempest] What title should be for OS-KSCRUD extension

I just noticed you suggested " "; if that's the prevailing form, then I'd suggest "Change password (self-service)". On Tue, Dec 8, 2015 at 9:31 PM, Dolph Mathews wrote: > This is implemented as a "self-service user password change" on the v2 > public API. The user is required to have a token for

Re: [openstack-dev] [keystone][doc][tempest] What title should be for OS-KSCRUD extension

This is implemented as a "self-service user password change" on the v2 public API. The user is required to have a token for the password they are changing, and is required to know the original password before a new one can be set. There is a similar "administrative password reset" call on the v2 a

Re: [openstack-dev] [Murano] How to debug a failed deployment?

Hi Vahid, Thanks for feedback. We need additional proof that this bug doesn't block engine or deployments. Nikolay Starodubtsev Software Engineer Mirantis Inc. Skype: dark_harlequine1 2015-12-09 3:33 GMT+03:00 Vahid S Hashemian : > Hi Kate, > > You were right. The bug I referred to does no

[openstack-dev] [keystone][doc][tempest] What title should be for OS-KSCRUD extension

Hi Keystone-team, TL;DR: Keystone v2 API supports PATCH on '/OS-KSCRUD/users/{user_id}', What should we name the operation for? We are adding the api-site link to Tempest docstring for explaining how to use each REST APIs of each project. This work comes from previous discussion on openstack-

Re: [openstack-dev] [oslo.db][sqlalchemy][mistral] Configuring default transaction isolation level

Hi, Moshe, I think you can try the following way to change the isolation_level of a specific transaction when using oslo.db. We apply it to solve the concurrency issue happen in Senlin project. Hope that will be helpful. 1272 session = _session(context) 1273 session.begin() 1274 sessi

[openstack-dev] [heat] Rico Lin for heat-core

Thanks Sergey, for the nomination. And thanks guys to letting me join Heat-core. Means a lot to me. I will do my best in this important work, still have a lot to learn from you guys :) -- Best regards, *Rico Lin* 迎棧科技股份有限公司│886-963-612-021│ric...@inwinstack.com│ 886-2

Re: [openstack-dev] [Neutron] DVR + L3 HA + L2pop - Mapping out the work

I agree with your comments below. I hope we are not going to hold off on this patch, since we need to address the other issues. It makes sense to have a separate tag in the Launchpad to couple all the l3-ha-dvr-l2pop issues into a single bucket and track it to completion. The patch in question

Re: [openstack-dev] [OpenStack-docs] What's Up, Doc? 4 December 2015

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 So it turns out calendars are hard, and I screwed up the meeting times in my last newsletter. Corrected dates are below: On 07/12/15 13:28, Lana Brindley wrote: > > == Doc team meeting == > > We held the APAC docs meeting this week. Big thanks

Re: [openstack-dev] [Murano] How to debug a failed deployment?

Hi Kate, You were right. The bug I referred to does not block the engine. So when I looked at the engine log, this is what I see after trying to deploy an environment with the HOT package I attached in my earlier message: http://paste.openstack.org/show/481260/ I looked up the error message and

Re: [openstack-dev] [horizon] Proposal to add Richard Jones tohorizon-core

Thank you all! On 9 December 2015 at 04:23, David Lyle wrote: > Since the results are unanimous, closing early. Welcome Richard! > > David > > On Thu, Dec 3, 2015 at 12:08 PM, Thai Q Tran wrote: > > An equally BIG +1 from me! Thanks for all the reviews and patches from > your > > minions Richar

Re: [openstack-dev] [puppet] including openstacklib::openstackclient

We decided in the meeting today to just to a naked include: https://review.openstack.org/#/c/253311/ https://review.openstack.org/#/c/254824/ On Tue, Dec 8, 2015 at 11:29 AM, Cody Herriges wrote: > Matt Fischer wrote: > > I found this bug in the liberty branch [1] over the weekend in the > > ha

Re: [openstack-dev] [all] [release] New Mitaka release schedule page

Excerpts from Anne Gentle's message of 2015-12-08 17:00:17 -0600: > On Mon, Dec 7, 2015 at 4:35 PM, Anita Kuno wrote: > > > On 12/04/2015 05:50 AM, Thierry Carrez wrote: > > > Hi everyone, > > > > > > As part of the effort to move reference information off the wiki to a > > > more peer-reviewable

Re: [openstack-dev] [all] [release] New Mitaka release schedule page

On Mon, Dec 7, 2015 at 4:35 PM, Anita Kuno wrote: > On 12/04/2015 05:50 AM, Thierry Carrez wrote: > > Hi everyone, > > > > As part of the effort to move reference information off the wiki to a > > more peer-reviewable area, the Mitaka release schedule page was moved to: > > > > http://docs.openst

Re: [openstack-dev] [all] making project_id optional in API URLs

On 12/08/2015 05:55 PM, michael mccune wrote: On 12/03/2015 12:06 PM, Sean Dague wrote: So, for Cinder, Glance, Ironic, Manila, Magnum (and others I might have missed) where are you standing on this one? And are there volunteers in those projects to help move this forward? i'm +1 for removing

Re: [openstack-dev] [all] making project_id optional in API URLs

On 12/03/2015 12:06 PM, Sean Dague wrote: So, for Cinder, Glance, Ironic, Manila, Magnum (and others I might have missed) where are you standing on this one? And are there volunteers in those projects to help move this forward? i'm +1 for removing the project_id from the url. sahara uses it in

Re: [openstack-dev] [horizon] Proposal to add Timur Sufiev tohorizon-core

David and all the fellow Horizoneers, Thank you very much for the trust you put in me :). I'll do my best to be up to it! On Tue, 8 Dec 2015 at 22:47, David Lyle wrote: > Since the results are unanimous, closing early. Welcome Timur! > > David > > On Thu, Dec 3, 2015 at 12:06 PM, Thai Q Tran w

Re: [openstack-dev] [glance][tempest][defcore] Process to imrpove tests coverge in temepest

Hi Flavio, On Tue, Dec 8, 2015 at 9:52 PM, Flavio Percoco wrote: > > > Oh, I meant ocasionally. Whenever a missing test for an API is found, > it'd be easy enough for the implementer to sohw up at the meeting and > bring it up. >From my experience as a Tempest reviewer, I'd say that most newly a

Re: [openstack-dev] [Fuel] Patch size limit

Hey Igor! Thank you for the response! On 7 December 2015 at 12:03, Igor Kalnitsky wrote: > Hey Andrii, > > I'm totally agree with you about contribution guides, except one thing > - we need and should force users to split huge patches into set of > small ones. > I believe that this is much more

Re: [openstack-dev] [puppet] proposing Cody Herriges part of Puppet OpenStack core

+1 On Tue, Dec 8, 2015 at 4:15 PM, Matt Fischer wrote: > +1 > > On Tue, Dec 8, 2015 at 2:07 PM, Rich Megginson > wrote: > >> On 12/08/2015 09:49 AM, Emilien Macchi wrote: >> >> Hi, >> >> Back in "old days", Cody was already core on the modules, when they were >> hosted by Puppetlabs namespace.

Re: [openstack-dev] [puppet] proposing Cody Herriges part of Puppet OpenStack core

+1 On Tue, Dec 8, 2015 at 2:07 PM, Rich Megginson wrote: > On 12/08/2015 09:49 AM, Emilien Macchi wrote: > > Hi, > > Back in "old days", Cody was already core on the modules, when they were > hosted by Puppetlabs namespace. > His contributions [1] are very valuable to the group: > * strong knowl

[openstack-dev] [tripleo] Monitoring support

Hi, I've been spending some time on deploying monitoring in TripleO with Sensu. I recently made good progress. If you are interested by this work, feel free to look an etherpad I started [1]. Feel free to comment, review, and give any feedback, Thank you, [1] https://etherpad.openstack.org/p/tr

Re: [openstack-dev] [puppet] proposing Cody Herriges part of Puppet OpenStack core

On 12/08/2015 09:49 AM, Emilien Macchi wrote: Hi, Back in "old days", Cody was already core on the modules, when they were hosted by Puppetlabs namespace. His contributions [1] are very valuable to the group: * strong knowledge on Puppet and all dependencies in general. * very helpful to debug i

Re: [openstack-dev] [all] using reno for release note management

Excerpts from Emilien Macchi's message of 2015-12-08 14:33:00 -0500: > This morning the Puppet OpenStack had the weekly meeting [1] and we > discussed about using reno [2] for release note management. > > We saw three possibilities: > > 1/ we use reno and enforce each contributions (bugfix, featu

Re: [openstack-dev] [nova] jsonschema for scheduler hints

On 12/08/15 at 09:43pm, Sylvain Bauza wrote: Le 08/12/2015 21:23, Andrew Laski a écrit : On 12/06/15 at 02:49pm, Ken'ichi Ohmichi wrote: Hi Sean, 2015-12-02 23:23 GMT+09:00 Sean Dague : We have previously agreed that scheduler hints in Nova are an open ended thing. It's expected for sites

Re: [openstack-dev] [glance][tempest][defcore] Process to imrpove tests coverge in temepest

On 08/12/15 15:31 -0500, Matthew Treinish wrote: On Tue, Dec 08, 2015 at 07:25:50PM +, Flavio Percoco wrote: Greetings, I just reviewed a patch in tempest that proposed adding new tests for the Glance's task API. While I believe it's awesome that folks in the tempest team keep adding missin

Re: [openstack-dev] [nova] jsonschema for scheduler hints

Le 08/12/2015 21:23, Andrew Laski a écrit : On 12/06/15 at 02:49pm, Ken'ichi Ohmichi wrote: Hi Sean, 2015-12-02 23:23 GMT+09:00 Sean Dague : We have previously agreed that scheduler hints in Nova are an open ended thing. It's expected for sites to have additional scheduler filters which exp

Re: [openstack-dev] [puppet] proposing Cody Herriges part of Puppet OpenStack core

On Tue, Dec 8, 2015 at 8:49 AM, Emilien Macchi wrote: > Hi, > > Back in "old days", Cody was already core on the modules, when they were > hosted by Puppetlabs namespace. > His contributions [1] are very valuable to the group: > * strong knowledge on Puppet and all dependencies in general. > * ve

Re: [openstack-dev] [glance][tempest][defcore] Process to imrpove tests coverge in temepest

On Tue, Dec 08, 2015 at 07:25:50PM +, Flavio Percoco wrote: > Greetings, > > I just reviewed a patch in tempest that proposed adding new tests for > the Glance's task API. While I believe it's awesome that folks in the > tempest team keep adding missing tests for projects, I think it'd be > be

Re: [openstack-dev] [nova] jsonschema for scheduler hints

On 12/06/15 at 02:49pm, Ken'ichi Ohmichi wrote: Hi Sean, 2015-12-02 23:23 GMT+09:00 Sean Dague : We have previously agreed that scheduler hints in Nova are an open ended thing. It's expected for sites to have additional scheduler filters which expose new hints. The way we handle that with our s

[openstack-dev] [TripleO][DIB] diskimage-builder and python 2/3 compatibility

Hello everyone, I am hoping for some feedback from our developers/users on a potential solution to a python 2/3 compatibility issue we are hitting in dib: We ran in to a couple issues adding Fedora 23 support to diskimage-builder caused by python2 not being installed by default. This can be solve

Re: [openstack-dev] Fwd: [Neutron] Team meeting this Monday at 2100 UTC

I actually found this week’s meeting more useful than normal. The typical agenda items feel rote and less useful to aligning things, sort of, thinking out loud. doug > On Dec 8, 2015, at 8:41 AM, Kyle Mestery wrote: > > On Tue, Dec 8, 2015 at 1:54 AM, Smigiel, Dariusz

Re: [openstack-dev] [nova] no user/project validation in "nova quota-show"?

On 12/7/2015 6:55 PM, Alex Xu wrote: 2015-12-08 8:38 GMT+08:00 Kevin L. Mitchell mailto:kevin.mitch...@rackspace.com>>: On Mon, 2015-12-07 at 18:21 -0600, Chris Friesen wrote: > Can someone explain why nova doesn't seem to be doing any validation in the > "nova quota-show" comma

[openstack-dev] [nova] stable/liberty 13.1.0 release planning

We've had a few high priority regression fixes in stable/liberty [1][2] so I think it's time to do a release. The current set of open reviews is: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/liberty,n,z We need to wait for a backport for [2] yet, but after

Re: [openstack-dev] [all] making project_id optional in API URLs

On 03/12/15 12:06 -0500, Sean Dague wrote: For folks that don't know, we've got an effort under way to look at some of what's happened with the service catalogue, how it's organically grown, and do some pruning and tuning to make sure it's going to support what we want to do with OpenStack for th

[openstack-dev] [all] using reno for release note management

This morning the Puppet OpenStack had the weekly meeting [1] and we discussed about using reno [2] for release note management. We saw three possibilities: 1/ we use reno and enforce each contributions (bugfix, feature, etc) to also edit a release note YAML file 2/ we use reno and the release not

[openstack-dev] [glance][tempest][defcore] Process to imrpove tests coverge in temepest

Greetings, I just reviewed a patch in tempest that proposed adding new tests for the Glance's task API. While I believe it's awesome that folks in the tempest team keep adding missing tests for projects, I think it'd be better for the tempest team, the project's team and defcore if we'd discuss t

Re: [openstack-dev] [neutron] Linux Bridge CI is now a voting gate job

Great work! -- Andreas (IRC: scheuran) On Mo, 2015-12-07 at 21:05 +, Sean M. Collins wrote: > It's been a couple months - the last time I posted on this subject we > were still working on getting Linux Bridge to become an experimental[1] > job. During the Liberty cycle, the Linux Bridge CI

[openstack-dev] [nova] stable/liberty 13.1.0 release planning

We've had a few high priority regression fixes in stable/liberty [1][2] so I think it's time to do a release. The current set of open reviews is: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/liberty,n,z We need to wait for a backport for [2] yet, but after

Re: [openstack-dev] Fwd: [Neutron] Team meeting this Monday at 2100 UTC

On Tue, Dec 8, 2015 at 1:54 AM, Smigiel, Dariusz wrote: > > > -Original Message- > > From: Kevin Benton [mailto:blak...@gmail.com] > > > > I liked using the meeting for it because it was a nice way for everyone > to get > > a snapshot of where each thing was at. > > +1 > The idea of discu

Re: [openstack-dev] [glance] Add Ian Cordasco back into glance-core

+1 Hooray! Welcome back :) On Dec 8, 2015 18:32, wrote: > +1 > > I'm delighted to hear this. > > Welcome back Ian. > > >> +1 from me! Glad to have Ian back. >> >> On 12/7/15, 11:36 AM, "Flavio Percoco" wrote: >> >> > Greetings, >> > > Not long ago, Ian Cordasco, sent an email out stepping down

[openstack-dev] [puppet] proposing Cody Herriges part of Puppet OpenStack core

Hi, Back in "old days", Cody was already core on the modules, when they were hosted by Puppetlabs namespace. His contributions [1] are very valuable to the group: * strong knowledge on Puppet and all dependencies in general. * very helpful to debug issues related to Puppet core or dependencies (be

Re: [openstack-dev] [nova] no user/project validation in "nova quota-show"?

On 12/7/2015 6:55 PM, Alex Xu wrote: 2015-12-08 8:38 GMT+08:00 Kevin L. Mitchell mailto:kevin.mitch...@rackspace.com>>: On Mon, 2015-12-07 at 18:21 -0600, Chris Friesen wrote: > Can someone explain why nova doesn't seem to be doing any validation in the > "nova quota-show" comma

Re: [openstack-dev] [all] [release] New Mitaka release schedule page

On 12/08/2015 04:41 AM, Thierry Carrez wrote: > Anita Kuno wrote: >> I often use the release schedule to reference the upcoming summit, so >> Austin in this case. Any thoughts on when we can expect an n.rst file in >> /releases? Any objection to me offering one up if only to put in the >> Austin su

Re: [openstack-dev] [oslo.db][sqlalchemy][mistral] Configuring default transaction isolation level

On 12/08/2015 07:28 AM, Renat Akhmerov wrote: > Hi, > > Moshe, thanks a lot for bringing this up. I remember I tried to find a > way to change isolation level per connection but also was unable to do that. Current SQLAlchemy has a lot of isolation level options.There is a complete guide to

[openstack-dev] [Neutron][Tricircle]The process for adding networking-tricircle

Hi Neutrinos, We the Tricircle team want to have a neutron-ovn like agent in Neutron for our networking management. I'm aware of the recent stadium model debate going on the mailinglist, so my question is what is the current procedure to propose such out of tree agent? Would it be something like

Re: [openstack-dev] [puppet] weekly meeting #62

On 12/07/2015 07:31 AM, Emilien Macchi wrote: > Hello! > > Here's an initial agenda for our weekly meeting, tomorrow at 1500 UTC > in #openstack-meeting-4: > > https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20151208 > > Thanks, > We did our

Re: [openstack-dev] [nova][doc][tempest] How to handle HTTP203

On Mon, Dec 7, 2015 at 11:07 PM, Ken'ichi Ohmichi wrote: > Hi, > > Today, we have virtual API document sprint and we are facing a problem > related to HTTP203 (Non-Authoritative Information). > The api-site(http://developer.openstack.org/api-ref-compute-v2.1.html) > contains HTTP203 as one of val

Re: [openstack-dev] [barbican] [cinder] New blog posts on using Barbican for Cinder Volume encryption

On 12/08/2015 09:43 AM, Ade Lee wrote: > Hi all, > > Just announcing a new blog for Barbican, including .. > - Barbican in RDO > - Barbican and Dogtag/IPA > - Securing Barbican behind haproxy > - Barbican and Volume Encryption > > Hopefully, some of the info here will be helpful to folks trying

Re: [openstack-dev] [neutron] Multiple locations for documentation of features

On Tue, Dec 08, 2015 at 09:03:10AM EST, Mike Spreitzer wrote: > Lots cheers from me too. Let me add one thing: "the spec is not > maintained" is a remaining process bug. A spec by itself is a very useful > thing. It is the first thing to read when trying to understand the > implementation. H

Re: [openstack-dev] [puppet] including openstacklib::openstackclient

Matt Fischer wrote: > I found this bug in the liberty branch [1] over the weekend in the > handling of openstack client between glance & keystone. As a part of > fixing that I've discussed with Clayton and Michael Chapman just what > the right way is to include the openstackclient. > > Keystone do

Re: [openstack-dev] [Fuel] FFE for Ubuntu bootstrap

Hi Folks, I would like to ask for FFE extension by 1 day. Reason: we didn't have green BVT today due to BUD network connectivity issue. Commits to merge: - https://review.openstack.org/#/c/250662/ - Switch itself. - https://review.openstack.org/#/c/251908/ - QA suite compatibility. - ht

Re: [openstack-dev] [oslo.db][sqlalchemy][mistral] Configuring default transaction isolation level

Hi Moshe, Feel free to submit a patch! This seems to be something we want to be able to configure. Thanks, Roman On Tue, Dec 8, 2015 at 9:41 AM, ELISHA, Moshe (Moshe) wrote: > Hi, > > > > We at Mistral want to move from the default transaction isolation level of > REPEATABLE READ to READ COMMIT

Re: [openstack-dev] [horizon] Proposal to add Timur Sufiev tohorizon-core

Since the results are unanimous, closing early. Welcome Timur! David On Thu, Dec 3, 2015 at 12:06 PM, Thai Q Tran wrote: > BIG +1 for me. Thanks for all of the great work Timur! > > > - Original message - > From: David Lyle > To: OpenStack Development Mailing List > Cc: > Subject: [ope

Re: [openstack-dev] [horizon] Proposal to add Richard Jones tohorizon-core

Since the results are unanimous, closing early. Welcome Richard! David On Thu, Dec 3, 2015 at 12:08 PM, Thai Q Tran wrote: > An equally BIG +1 from me! Thanks for all the reviews and patches from your > minions Richard! > > > - Original message - > From: David Lyle > To: OpenStack Devel

Re: [openstack-dev] [ironic]Ironic operations on nodes in maintenance mode

On 23 November 2015 at 18:35, Shraddha Pandhe wrote: > Hi, > > I would like to know how everyone is using maintenance mode and what is > expected from admins about nodes in maintenance. The reason I am bringing > up this topic is because, most of the ironic operations, including manual > cleaning

[openstack-dev] [barbican] [cinder] New blog posts on using Barbican for Cinder Volume encryption

Hi all, Just announcing a new blog for Barbican, including .. - Barbican in RDO - Barbican and Dogtag/IPA - Securing Barbican behind haproxy - Barbican and Volume Encryption Hopefully, some of the info here will be helpful to folks trying to set things up with Barbican. https://vakwetu.wordpress

Re: [openstack-dev] [heat] Rico Lin for heat-core

So looks like most part have agreement :) My congratulations, Rico!!! Good luck in this important work. I will add you to gerrit group. On 8 December 2015 at 06:30, Rabi Mishra wrote: > - Original Message - > > Hi all. > > > > I'd like to nominate Rico Lin for heat-core. He did awesome

Re: [openstack-dev] [neutron] Multiple locations for documentation of features

> From: Henry Gessau > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 12/04/2015 02:23 PM > Subject: Re: [openstack-dev] [neutron] Multiple locations for > documentation of features > > Sean M. Collins wrote: > > I've noticed that a lot of features are now being

Re: [openstack-dev] [release][all] bugs will now close automatically when patches merge

On Tue, Dec 08 2015, Doug Hellmann wrote: > Next cycle I expect us to be prepared to handle releases for all > official projects through the releases repository and the automation > we're currently building. That will still allow for doing extra > manual work in Launchpad, of course, but it will b

Re: [openstack-dev] [release][all] bugs will now close automatically when patches merge

Excerpts from Julien Danjou's message of 2015-12-08 12:35:38 +0100: > On Tue, Dec 08 2015, Thierry Carrez wrote: > > > You can read the previous thread (which you apparently missed) where we > > proposed and discussed this work, but TL;DR: is that this was highly > > unreliable (we turned every Fi

Re: [openstack-dev] [release][all] bugs will now close automatically when patches merge

Excerpts from Thierry Carrez's message of 2015-12-08 12:00:20 +0100: > Thierry Carrez wrote: > > Julien Danjou wrote: > >> On Mon, Dec 07 2015, Doug Hellmann wrote: > >>> As mentioned previously [1], as part of deprecating our use of Launchpad > >>> for tracking completed work we have changed the d

[openstack-dev] [app-catalog] IRC Meeting Thursday December 10th at 17:00UTC

Greetings! Our next OpenStack Community App Catalog meeting will take place this ThursdayDecember 10th at 17:00 UTC in #openstack-meeting-3 The agenda can be found here: https://wiki.openstack.org/wiki/Meetings/app-catalog Please add agenda items if there's anything specific you would like to dis

[openstack-dev] [TripleO] TripleO UI

Hi All, In this email[1], Tzu-Mainn summarized recent developments in TripleO regarding the workflow library and the REST API. I'd like to complement that email with some information about the future TripleO UI. The new REST API aims to unify the deployment workflow and has the tripleo client[2]

Re: [openstack-dev] Documentation containing external resource links & privacy breaches

Excerpts from Thomas Goirand's message of 2015-12-08 13:31:57 +0100: > On 12/08/2015 03:48 AM, Anne Gentle wrote: > > > > > > On Mon, Dec 7, 2015 at 3:18 PM, Cory Benfield > > wrote: > > > > > > > On 7 Dec 2015, at 18:37, Thomas Goirand >

Re: [openstack-dev] [oslo.db][sqlalchemy][mistral] Configuring default transaction isolation level

Thank you, Gordon for your reply. In your patch I see that you are setting the isolation_level to REPEATABLE_READ. We are trying to change the isolation level to READ_COMMITTED. I like to refer you to this performance article[1] that determines that READ_COMMITTED is usually better than REPEATAB

Re: [openstack-dev] Regarding Designate install through Openstack-Ansible

On 8 December 2015 at 08:26, Sharma Swati6 wrote: > Hi *Major, Jean, Jesse and Kevin,* Howdy! > I have been interacting with you lately on openstack mailing lists and IRC > chats regarding *Designate component inclusion in Openstack-Ansible*, so > that its deployment can be made similar to ot

Re: [openstack-dev] [midonet] Split up python-midonetclient

Hi Sandro, >> 1) (Downstream) packaging: midonet and python-midonetclient are two >> distinct packages, and therefore should have distinct upstream >> tarballs - which are compiled on a per repo basis. This is actually not accurate: there is no such thing as a midonet package. The midonet repo pr

Re: [openstack-dev] [TripleO] workflow

On Mon, 2015-12-07 at 16:00 +, Dougal Matthews wrote: > > > On 7 December 2015 at 14:59, Dan Prince wrote: > > > > > > > > On Thu, 2015-12-03 at 15:47 -0500, Dan Prince wrote: > > > On Tue, 2015-11-24 at 15:25 +, Dougal Matthews wrote: > > > > On 23 November 2015 at 14:37, Dan Prince

Re: [openstack-dev] [midonet] Split up python-midonetclient

Hi Sandro, On Tue, Dec 8, 2015 at 7:31 AM, Sandro Mathys wrote: > Hi, > > As Takashi Yamamoto raised in another thread [0], python-midonetclient > should be split out into its own repo I'm strongly against on this one. Stuff in the midonet/ repo is developed in sync with python-midonetclient (a

Re: [openstack-dev] [oslo.db][sqlalchemy][mistral] Configuring default transaction isolation level

we had this in ceilometer events. you can see it here: https://github.com/openstack/ceilometer/commit/898cd3d036c4358aa16f7b3e2028365dc9829213 note, that patch is removing it because it slowed everything way down because of locking. if you can avoid it, avoid it. On 08/12/2015 7:28 AM, Renat

Re: [openstack-dev] [nova][doc][tempest] How to handle HTTP203

On 12/08/2015 12:07 AM, Ken'ichi Ohmichi wrote: > Hi, > > Today, we have virtual API document sprint and we are facing a problem > related to HTTP203 (Non-Authoritative Information). > The api-site(http://developer.openstack.org/api-ref-compute-v2.1.html) > contains HTTP203 as one of valid status

Re: [openstack-dev] Documentation containing external resource links & privacy breaches

On 12/08/2015 03:48 AM, Anne Gentle wrote: > > > On Mon, Dec 7, 2015 at 3:18 PM, Cory Benfield > wrote: > > > > On 7 Dec 2015, at 18:37, Thomas Goirand > wrote: > > > > > > The reason why I'd like an env var, is that I could si

Re: [openstack-dev] [oslo.db][sqlalchemy][mistral] Configuring default transaction isolation level

Hi, Moshe, thanks a lot for bringing this up. I remember I tried to find a way to change isolation level per connection but also was unable to do that. An advice from oslo team would be very helpful. Renat Akhmerov @ Mirantis Inc. > On 08 Dec 2015, at 13:41, ELISHA, Moshe (Moshe) > wrote:

Re: [openstack-dev] [release][all] bugs will now close automatically when patches merge

On Tue, Dec 08 2015, Thierry Carrez wrote: > You can read the previous thread (which you apparently missed) where we > proposed and discussed this work, but TL;DR: is that this was highly > unreliable (we turned every FixCommitted bugs into FixReleased bugs > without checking that they all actuall

Re: [openstack-dev] [ironic] RFC: stop using launchpad milestones and blueprints

On 12/08/2015 11:32 AM, Pavlo Shchelokovskyy wrote: Hi Dmitry, not true, the gate-ironic-specs-python27 requires that LP blueprint is provided in a spec [0]. If we are to get away from LP blueprints and at least not register new ones, this must be fixed. I'll test if the job accepts a link to L

Re: [openstack-dev] [glance] Add Ian Cordasco back into glance-core

+1 I'm delighted to hear this. Welcome back Ian. +1 from me! Glad to have Ian back. On 12/7/15, 11:36 AM, "Flavio Percoco" wrote: > Greetings, > > Not long ago, Ian Cordasco, sent an email out stepping down from his > core roles as he didn't have the time to dedicate to the project > te

Re: [openstack-dev] [Fuel] [QA] [Tests] MOS integration tests in SWARM test suite

Hi Timur, Please take into account that Rally/Tempest tests should be added to fuel-qa/system_test/ folder instead of fuel-qa/fuelweb_test/. It is necessary for using template-based approach for this tests. It would be good to move there also sahara/murano tests. 08.12.2015 09:41, Timur Nurlyga

Re: [openstack-dev] [release][all] bugs will now close automatically when patches merge

Julien Danjou wrote: > On Tue, Dec 08 2015, Thierry Carrez wrote: > >> Quite a few projects were using the option to fix-release directly >> already and behavior there doesn't change. > > That makes sense, indeed. > >> Could you detail what your workflow is ? How are you using FixCommitted >> an

Re: [openstack-dev] [fuel][plugins]Security problem in Fuel 7.0

Vladimir, I want to emphasize that my main concern is not with arbitrary code execution on master node. I have no problem with that if there is only one OpenStack environment. What I am concerned about is this: 1) In general case user installs plugin for the one environment only. 2) But in o

Re: [openstack-dev] [release][all] bugs will now close automatically when patches merge

Thierry Carrez wrote: > Julien Danjou wrote: >> On Mon, Dec 07 2015, Doug Hellmann wrote: >>> As mentioned previously [1], as part of deprecating our use of Launchpad >>> for tracking completed work we have changed the default behavior so that >>> when a patch with "Fixes-Bug" in the commit message

Re: [openstack-dev] [release][all] bugs will now close automatically when patches merge

On Tue, Dec 08 2015, Thierry Carrez wrote: > Quite a few projects were using the option to fix-release directly > already and behavior there doesn't change. That makes sense, indeed. > Could you detail what your workflow is ? How are you using FixCommitted > and FixReleased on projects not manag

Re: [openstack-dev] [release][all] bugs will now close automatically when patches merge

Julien Danjou wrote: > On Mon, Dec 07 2015, Doug Hellmann wrote: >> As mentioned previously [1], as part of deprecating our use of Launchpad >> for tracking completed work we have changed the default behavior so that >> when a patch with "Fixes-Bug" in the commit message merges the bug will >> move

Re: [openstack-dev] [glance] Add Ian Cordasco back into glance-core

> -Original Message- > From: Flavio Percoco [mailto:fla...@redhat.com] > Sent: Monday, December 07, 2015 4:36 PM > To: openstack-dev@lists.openstack.org > Subject: [openstack-dev] [glance] Add Ian Cordasco back into glance-core > > Greetings, > > Not long ago, Ian Cordasco, sent an email

Re: [openstack-dev] [Fuel] Current Fuel CI status and issues related to CentOS7 migration

Hi, Mike, yes, it is about build environment only. On Fuel node we use standard kernel and docker packages from CentOS repositories and there are no issues I am aware of. On Tue, Dec 8, 2015 at 11:03 AM, Mike Scherbakov wrote: > Aleksandra, > Thanks for detailed status update on Infra/Tests sid

Re: [openstack-dev] [neutron] Multiple locations for documentation of features

On 08/12/15 10:04, Mathieu Rohon wrote: Hi all, thanks for the explanation. Can you also explain how does neutron team use blueprints? how it overlaps with RFE bugs? Hi Mathieu, This is all documented, in principle, at http://docs.openstack.org/developer/neutron/policies/blueprints.html.

Re: [openstack-dev] [neutron] Multiple locations for documentation of features

On 07/12/15 17:42, Sean M. Collins wrote: > On Mon, Dec 07, 2015 at 12:18:29PM EST, Carl Baldwin wrote: >> On Fri, Dec 4, 2015 at 12:22 PM, Henry Gessau wrote: >>> 1. RFE: "I want X" >>> 2. Spec: "I plan to implement X like this" >>> 3. devref: "How X is implemented and how to extend it" >>> 4. OS

  1   2   >