[openstack-dev] [all] Recording little everyday OpenStack successes

Hello everyone, OpenStack has become quite big, and it's easier than ever to feel lost, to feel like nothing is really happening. It's more difficult than ever to feel part of a single community, and to celebrate little successes and progress. In a (small) effort to help with that, I suggested

Re: [openstack-dev] [CI] Try to introduce RFC mechanism to CI.

Hi, On Fri, Oct 9, 2015 at 11:00 AM, Tang Chen wrote: > Hi, > > CI systems will run tests for each patch once it is submitted or modified. > But most CI systems occupy a lot of resource, and take a long time to > run tests (1 or 2 hours for one patch). > > I think, not

Re: [openstack-dev] [CI] Try to introduce RFC mechanism to CI.

On 10/09/2015 05:48 PM, Jordan Pittier wrote: Hi, On Fri, Oct 9, 2015 at 11:00 AM, Tang Chen > wrote: Hi, CI systems will run tests for each patch once it is submitted or modified. But most CI systems occupy a lot of

[openstack-dev] [CI] Try to introduce RFC mechanism to CI.

Hi, CI systems will run tests for each patch once it is submitted or modified. But most CI systems occupy a lot of resource, and take a long time to run tests (1 or 2 hours for one patch). I think, not all the patches submitted need to be tested. Even those patches with an approved BP and

[openstack-dev] [Magnum] Testing result of new atomic-6 image

Testing result of new atomic-6 image [1] built by Tango atomic-5 image has issue to start a container instance(docker version is 1.7.1), Tango built a new atomic-6 image with docker 1.8.1 version. eghobo and I (eliqiao) did some testing works (eghobo_ did most of them) Here is the summary: *

Re: [openstack-dev] [swift] Plan to port Swift to Python 3

Victor, I appreciate for your effort. However I was just checking if you considered using 2to3. I can understand that translation using this tool might not cover every area in the code more specifically custom/3rd party libraries (non-standard python libraries) but IMO it can do fixer

Re: [openstack-dev] [Fuel] Plugins related functionality in Fuel Client

>> I’d say even if it will be a separate service it’s better to proxy requests through Nailgun’s API to have a single entry point. I don't think that application such as Nailgun should be responsible for proxying requests, we solved similar problem for OSTF with adding proxy rule in Nginx.

Re: [openstack-dev] [Fuel] Plugins related functionality in Fuel Client

+1, that would allow to install plugins from Fuel UI 2015-10-09 15:53 GMT+07:00 Sergii Golovatiuk : > +1 to Roman. > > -- > Best regards, > Sergii Golovatiuk, > Skype #golserge > IRC #holser > > On Fri, Oct 9, 2015 at 10:45 AM, Roman Prykhodchenko >

Re: [openstack-dev] [Fuel] Plugins related functionality in Fuel Client

In that case I would suggest to also use Keystone service directory for discovering services. > 9 жовт. 2015 р. о 11:00 Evgeniy L написав(ла): > > >> I’d say even if it will be a separate service it’s better to proxy > >> requests through Nailgun’s API to have a single

[openstack-dev] [ceilometer] Inconsistent timestamping of polled data

Hi all, As Gordon descriped in https://bugs.launchpad.net/ceilometer/+bug/1491509 , many of pollsters define the timestamp individually for each sample that is generated rather than basing on when the data was polled. I agree with Gordon on that the timestamping of samples should base on when

Re: [openstack-dev] [Fuel] Plugins related functionality in Fuel Client

Hi, +1, but I think it's better to spawn separate service, instead of adding it to Nailgun. Thanks, On Fri, Oct 9, 2015 at 1:40 AM, Roman Prykhodchenko wrote: > Folks, > > it’s time to speak about Fuel Plugins and the way they are managed. > > Currently we have some methods

Re: [openstack-dev] [Fuel] Plugins related functionality in Fuel Client

I’d say even if it will be a separate service it’s better to proxy requests through Nailgun’s API to have a single entry point. > 9 жовт. 2015 р. о 10:23 Evgeniy L написав(ла): > > Hi, > > +1, but I think it's better to spawn separate service, instead of adding it > to

Re: [openstack-dev] [Fuel] Plugins related functionality in Fuel Client

+1 to Roman. -- Best regards, Sergii Golovatiuk, Skype #golserge IRC #holser On Fri, Oct 9, 2015 at 10:45 AM, Roman Prykhodchenko wrote: > I’d say even if it will be a separate service it’s better to proxy > requests through Nailgun’s API to have a single entry point. > > 9

Re: [openstack-dev] [Fuel] Plugins related functionality in Fuel Client

Actually it's an old issue https://blueprints.launchpad.net/fuel/+spec/plugin-manager-as-separate-service On 10/09/2015 11:53 AM, Sergii Golovatiuk wrote: +1 to Roman. -- Best regards, Sergii Golovatiuk, Skype #golserge IRC #holser On Fri, Oct 9, 2015 at 10:45 AM, Roman Prykhodchenko

Re: [openstack-dev] [swift] Plan to port Swift to Python 3

Victor Stinner wrote: > Good news, we made good progress last weeks on porting Swift to Python > 3, a few changes were merged and all dependencies now work on Python 3. > We only need two more simple changes to have a working pyhon34 check job: > > * "py3: Update pbr and dnspython requirements" >

Re: [openstack-dev] [Murano] py26 support in python-muranoclient

Hi Vahid, unfortunately we don't plan to remove support for py26 from the python-muranoclient, most of the python-client support py26 in order to work out of the box on different OS including CentOS 6.5 and so on. >So the options are: >1. support py26 in tosca-parser Support for py26 is pretty

Re: [openstack-dev] [ironic] Nominating two new core reviewers

+2 for both, Vladyslav and John. On 10/09/2015 12:47 AM, Jim Rollenhagen wrote: Hi all, I've been thinking a lot about Ironic's core reviewer team and how we might make it better. I'd like to grow the team more through trust and mentoring. We should be able to promote someone to core based on

Re: [openstack-dev] [ironic] Nominating two new core reviewers

+1 From: Jim Rollenhagen Sent: Thursday, October 8, 2015 2:47 PM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [ironic] Nominating two new core reviewers Hi all, I've been thinking a lot about Ironic's core

[openstack-dev] [All][Elections] Results of the TC Election

Please join me in congratulating the 6 newly elected members of the TC. * Doug Hellmann (dhellmann) * Monty Taylor (mordred) * Anne Gentle (annegentle) * Sean Dague (sdague) * Russell Bryant (russellb) * Kyle Mestery (mestery) Full results:

Re: [openstack-dev] Scheduler proposal

On 10/09/2015 03:36 PM, Ian Wells wrote: On 9 October 2015 at 12:50, Chris Friesen > wrote: Has anybody looked at why 1 instance is too slow and what it would take to make 1 scheduler instance work fast enough? This

Re: [openstack-dev] [keystone] Let's get together and fix all the bugs

Great idea! core reviewer’s advice is definitely much important and valuable before proposing a fixing. I was always thinking it will help save us if we can get some agreement at some point. Best Regards, Dave Chen From: David Stanek [mailto:dsta...@dstanek.com] Sent: Saturday,

Re: [openstack-dev] [all] service catalog: TNG

Excerpts from Sean Dague's message of 2015-10-09 14:00:40 -0700: > On 10/09/2015 02:52 PM, Jonathan D. Proulx wrote: > > On Fri, Oct 09, 2015 at 02:17:26PM -0400, Monty Taylor wrote: > > :On 10/09/2015 01:39 PM, David Stanek wrote: > > :> > > :>On Fri, Oct 9, 2015 at 1:28 PM, Jonathan D. Proulx

Re: [openstack-dev] Different OpenStack components

The official list is http://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml Thanks, Kevin From: Amrith Kumar [amr...@tesora.com] Sent: Friday, October 09, 2015 3:20 PM To: OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] Scheduler proposal

On 9 October 2015 at 18:29, Clint Byrum wrote: > Instead of having the scheduler do all of the compute node inspection > and querying though, you have the nodes push their stats into something > like Zookeeper or consul, and then have schedulers watch those stats > for changes

Re: [openstack-dev] [Horizon] Suggestions for handling new panels and refactors in the future

Hi Doug! I think the is a great discussion topic and you summarize your points very nicely! I wish you’d responded to this thread, though: https://openstack.nimeyo.com/58582/openstack-dev-horizon-patterns-for-angular-panels, because it is talking about the same problem. This is option 3 I

Re: [openstack-dev] [magnum] New Core Reviewers

Thanks everyone! It is my pleasure to be a magnum core reviewer. Let's make magnum better together. Thanks Wanghua On Wed, Oct 7, 2015 at 1:19 AM, Vilobh Meshram < vilobhmeshram.openst...@gmail.com> wrote: > Thanks everyone! > > I really appreciate this. Happy to join Magnum-Core :) > > We

[openstack-dev] [fuel] Nominate Svetlana Karslioglu for fuel-docs core

Hi all, Svetlana is doing great work and I hope our Fuel documentation will become even better; +1 from me -- Best regards, Irina *Business Analyst* *unloc...@mirantis.com * __ OpenStack

[openstack-dev] What's Up, Doc? 9 Oct 2015

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi everyone, We're hurtling head first to Liberty, with only about a week left to go. I've been working on Summit preparations, and making sure we're ready to go when the time hits. This week, I'm working on Release Notes, keeping an eye on the

Re: [openstack-dev] Requests + urllib3 + distro packages

Robert Collins writes: > The problem that occurs is the result of a few interacting things: > - requests has very very specific versions of urllib3 it works with. > So specific they aren't always released yet. This should no longer be true. Our downstream redistributors pointed out

[openstack-dev] [All][Glance] Feedback on the proposed refactor to the image import process required

Greetings, There was recently a discussion[0] on the mailing list, started by Doug Hellman, to discuss some issues related to Glance's API, the conflicts between v1 and v2 and how this is making some pandas sad. The above served as a starting point for a discussion around the current API, how

Re: [openstack-dev] [fuel] Nominate Svetlana Karslioglu for fuel-docs core

+1 Svetlana, thank you for your contribution, and looking forward to working with you on the Fuel documentation improvement! Best, Olga On Thu, Oct 8, 2015 at 11:13 AM, Alexander Adamov wrote: > +1 to Svetlana's nomination. > > On Tue, Sep 29, 2015 at 4:58 AM, Dmitry

Re: [openstack-dev] [Openstack-operators] Scheduler proposal

On 10/08/2015 01:37 AM, Clint Byrum wrote: Excerpts from Maish Saidel-Keesing's message of 2015-10-08 00:14:55 -0700: Forgive the top-post. Cross-posting to openstack-operators for their feedback as well. Ed the work seems very promising, and I am interested to see how this evolves. With my

Re: [openstack-dev] [ironic] Nominating two new core reviewers

On 10/08/2015 11:47 PM, Jim Rollenhagen wrote: Hi all, I've been thinking a lot about Ironic's core reviewer team and how we might make it better. I'd like to grow the team more through trust and mentoring. We should be able to promote someone to core based on a good knowledge of *some* of the

Re: [openstack-dev] We should move strutils.mask_password back into oslo-incubator

On 08/10/15 16:49, Doug Hellmann wrote: Excerpts from Matt Riedemann's message of 2015-10-07 14:38:07 -0500: Here's why: https://review.openstack.org/#/c/220622/ That's marked as fixing an OSSA which means we'll have to backport the fix in nova but it depends on a change to

[openstack-dev] Metadata via dhcp namespace not working for icehouse release

Hii Guys, I am trying to run Metadata via the DHCP namespace by following blog post mentioned below: http://techbackground.blogspot.in/2013/06/metadata-via-dhcp-namespace.html Commands mentioned on above link for debugging o/p is exactly same for my setup. Also i am able to ping 169.254.169.254

Re: [openstack-dev] [stable][horizon] adding Doug Fish to horizon stable-maint

On 01/10/15 11:21, Matthias Runge wrote: > Hello, > > I would like to propose to add > > Doug Fish (doug-fish) > > to horizon-stable-maint team. > > I'd volunteer and introduce him to stable branch policy. A week has passed, no negative votes. Doug, I'll request to add you to

Re: [openstack-dev] Metadata via dhcp namespace not working for icehouse release

Hi Pradeep, see inline please... On 10/09/2015 09:00 AM, Pradeep kumar wrote: Hii Guys, and girls :) I am trying to run Metadata via the DHCP namespace by following blog post mentioned below: http://techbackground.blogspot.in/2013/06/metadata-via-dhcp-namespace.html Commandsmentioned

Re: [openstack-dev] [TripleO] review priorities etherpad

On Thu, 2015-10-08 at 09:17 -0400, James Slagle wrote: > At the TripleO meething this week, we talked about using an etherpad > to help get some organization around reviews for the high priority > themes in progress. > > I started on one: >

Re: [openstack-dev] [all] service catalog: TNG

Well said! On Fri, Oct 9, 2015 at 5:00 PM, Sean Dague wrote: > On 10/09/2015 02:52 PM, Jonathan D. Proulx wrote: > > On Fri, Oct 09, 2015 at 02:17:26PM -0400, Monty Taylor wrote: > > :On 10/09/2015 01:39 PM, David Stanek wrote: > > :> > > :>On Fri, Oct 9, 2015 at 1:28 PM,

Re: [openstack-dev] Scheduler proposal

Gregory Haynes wrote: Excerpts from Joshua Harlow's message of 2015-10-08 15:24:18 +: On this point, and just thinking out loud. If we consider saving compute_node information into say a node in said DLM backend (for example a znode in zookeeper[1]); this information would be updated

Re: [openstack-dev] Different OpenStack components

A google search produced this as result #2. http://governance.openstack.org/reference/projects/index.html Looks pretty complete to me. -amrith -- Amrith Kumar, CTO | amr...@tesora.com Tesora, Inc | @amrithkumar 125 CambridgePark Drive, Suite 400 |

Re: [openstack-dev] [all] service catalog: TNG

On Oct 9, 2015, at 9:39 AM, Sean Dague wrote: > > It looks like some great conversation got going on the service catalog > standardization spec / discussion at the last cross project meeting. > Sorry I wasn't there to participate. > > A lot of that ended up in here (which was an

Re: [openstack-dev] [all] service catalog: TNG

On 10/09/2015 02:52 PM, Jonathan D. Proulx wrote: > On Fri, Oct 09, 2015 at 02:17:26PM -0400, Monty Taylor wrote: > :On 10/09/2015 01:39 PM, David Stanek wrote: > :> > :>On Fri, Oct 9, 2015 at 1:28 PM, Jonathan D. Proulx :>> wrote: > :>As an

Re: [openstack-dev] [keystone] Let's get together and fix all the bugs

Dave, thanks for much for organizing this recurring event. I'll definitely be there to help squash some bugs this Friday! Thanks, Steve Martinelli OpenStack Keystone Project Team Lead From: David Stanek To: OpenStack Development Mailing List

Re: [openstack-dev] Scheduler proposal

And one last reply with more code: http://paste.openstack.org/show/475941/ (a creator of services that dynamically creates services, and destroys them after a set amount of time is included in here, along with the prior resource watcher). Works locally, should work for u as well. Output

[openstack-dev] [app-catalog] Tokyo Summit Sessions

Hello! I wanted to send a note letting people know about the two sessions we have planned for the Tokyo Summit coming up. Both of them are on Thursday, with a Fishbowl session followed by a working session. I'm eager to get feedback and input while we're in Tokyo. We are interested not only in

[openstack-dev] Feedback about Swift API - Especially about Large Objects

Hi Swift Developpers, We have been using Swift as a IAAS provider for more than two years now, but this mail is about feedback on the API side. I think it would be great to include some of the ideas in future revisions of API. I’ve been developping a few Swift clients in HTML (in Cloudwatt

Re: [openstack-dev] Scheduler proposal

FWIW - and somewhat ironically given what you said just before - I couldn't parse your last sentence below... You might like to follow up with a corrected version. (On the broad point, BTW, I really agree with you. So much OpenStack discussion is rendered difficult to get into by use of wrong

Re: [openstack-dev] Feedback about Swift API - Especially about Large Objects

A lot of these deficiencies are drastically improved with static large objects - and non-trivial to address (impossible?) with DLO's because of their dynamic nature. It's unfortunate, but DLO's don't really serve your use-case very well - and you should find a way to transition to SLO's [1]. We

Re: [openstack-dev] Scheduler proposal

Further example stuff, Get kazoo installed (http://kazoo.readthedocs.org/) Output from my local run (with no data) $ python test.py Kazoo client has changed to state: CONNECTED Got data: '' for new resource /node/compute_nodes/h1.hypervisor.yahoo.com Idling (ran for 0.00s). Known

[openstack-dev] [TripleO] Auto-abandon bot

Hi OoOers, As discussed in the meeting a week or two ago, we would like to bring back the auto-abandon functionality for old, unloved gerrit reviews. I've got a first implementation of a tool to do that: https://github.com/cybertron/tripleo-auto-abandon It currently follows these rules for

[openstack-dev] [Rally][Meeting][Agenda]

Hi, its a friendly reminder that if you what to discuss some topics at Rally meetings, please add you topic to our Meeting agenda https://wiki.openstack.org/wiki/Meetings/Rally#Agenda. Don't forget to specify who will lead topic discussion. Add some information about topic(links, etc.) Thank you

Re: [openstack-dev] Scheduler proposal

Excerpts from Chris Friesen's message of 2015-10-09 19:36:03 +: > On 10/09/2015 12:55 PM, Gregory Haynes wrote: > > > There is a more generalized version of this algorithm for concurrent > > scheduling I've seen a few times - Pick N options at random, apply > > heuristic over that N to pick

Re: [openstack-dev] [neutron] REST API to return ip-margin

>Network names are not guaranteed to be unique. This could cause >problems. If >I recall correctly we had a similar discussion about one of the >plugins (One >of the IBM ones?) where they ran into the issue of network >names and >uniqueness. My proposal is to use network-uuid as the key, and

Re: [openstack-dev] Scheduler proposal

On 9 October 2015 at 12:50, Chris Friesen wrote: > Has anybody looked at why 1 instance is too slow and what it would take to > >> make 1 scheduler instance work fast enough? This does not preclude the >> use of >> concurrency for finer grain tasks in the background.

Re: [openstack-dev] Scheduler proposal

On 10/9/15, 6:29 PM, "Clint Byrum" wrote: >Excerpts from Chris Friesen's message of 2015-10-09 17:33:38 -0700: >> On 10/09/2015 03:36 PM, Ian Wells wrote: >> > On 9 October 2015 at 12:50, Chris Friesen > > >

Re: [openstack-dev] [keystone] Let's get together and fix all the bugs

On 10/09/2015 11:04 PM, Chen, Wei D wrote: Great idea! core reviewer’s advice is definitely much important and valuable before proposing a fixing. I was always thinking it will help save us if we can get some agreement at some point. Best Regards, Dave Chen *From:*David Stanek

[openstack-dev] Ceilometer, New measurements, Types

There are three type of meters are defined in Ceilometer, including Cumulative, Gauge, Delta. In fact, these three types are numeric, but i need string. How could i make ceilometer to support string. Doc: http://docs.openstack.org/developer/ceilometer/new_meters.html image: phot...@126.com

Re: [openstack-dev] [neutron] REST API to return ip-margin

On Fri, Oct 09, 2015 at 02:38:03PM EDT, Aihua Li wrote: > For this use-case, we need to return network name in the response.We also > have the implementation and accompanying tempest test scripts.The issue > 1457986 is currently assigned to Mike Dorman. I am curious to see where we > are on

Re: [openstack-dev] Scheduler proposal

Excerpts from Joshua Harlow's message of 2015-10-08 15:24:18 +: > On this point, and just thinking out loud. If we consider saving > compute_node information into say a node in said DLM backend (for > example a znode in zookeeper[1]); this information would be updated > periodically by that

Re: [openstack-dev] Scheduler proposal

There are several ways to make python code that deals with a lot of data faster, especially when it comes to operating on DB fields from SQL tables (and that is not limited to the nova scheduler). Pulling data from large SQL tables and operating on them through regular python code (using

Re: [openstack-dev] [all] Recording little everyday OpenStack successes

On Fri, Oct 9, 2015 at 8:52 AM, Russell Bryant wrote: > On 10/09/2015 05:42 AM, Thierry Carrez wrote: > > Hello everyone, > > > > OpenStack has become quite big, and it's easier than ever to feel lost, > > to feel like nothing is really happening. It's more difficult than

Re: [openstack-dev] [all] jobs that make break when we remove Devstack extras.d in 10 weeks

On 10/09/2015 12:58 PM, Dmitry Tantsur wrote: On 10/09/2015 12:35 PM, Sean Dague wrote: From now until the removal of devstack extras.d support I'm going to send a weekly email of jobs that may break. A warning was added that we can track in logstash. Here are the top 25 jobs (by volume) that

Re: [openstack-dev] [all] Recording little everyday OpenStack successes

+1 Great idea! On Fri, Oct 9, 2015 at 3:42 AM, Thierry Carrez wrote: > Hello everyone, > > OpenStack has become quite big, and it's easier than ever to feel lost, > to feel like nothing is really happening. It's more difficult than ever > to feel part of a single

Re: [openstack-dev] [Neutron] L2 gateway project

On Fri, Oct 9, 2015 at 10:13 AM, Gary Kotton wrote: > Hi, > Who will be creating the stable/liberty branch? > Thanks > Gary > > I'll be doing this once someone from the L2GW team lets me know a commit SHA to create it from. Thanks, Kyle >

Re: [openstack-dev] [all] service catalog: TNG

On 10/09/2015 11:21 AM, Shamail wrote: On Oct 9, 2015, at 10:39 AM, Sean Dague wrote: It looks like some great conversation got going on the service catalog standardization spec / discussion at the last cross project meeting. Sorry I wasn't there to participate. Apologize

Re: [openstack-dev] [all] Recording little everyday OpenStack successes

This is AWESOME! And I've already found useful resources on the list of successes. Beautiful job, and fantastic idea! Nick On 10/09/2015 05:42 AM, Thierry Carrez wrote: > Hello everyone, > > OpenStack has become quite big, and it's easier than ever to feel lost,

Re: [openstack-dev] [Heat] mox to mock migration

On Fri, Oct 09, 2015 at 09:06:57AM -0400, Jay Dobies wrote: > I forget where we left things at the last meeting with regard to whether or > not there should be a blueprint on this. I was going to work on some during > some downtime but I wanted to make sure I wasn't overlapping with what > others

Re: [openstack-dev] Metadata via dhcp namespace not working for icehouse release

> On 09 Oct 2015, at 09:00, Pradeep kumar wrote: > > > Hii Guys, > I am trying to run Metadata via the DHCP namespace by following blog post > mentioned below: > > http://techbackground.blogspot.in/2013/06/metadata-via-dhcp-namespace.html > > Commands mentioned

Re: [openstack-dev] [CI] Try to introduce RFC mechanism to CI.

On 2015-10-09 17:00:27 +0800 (+0800), Tang Chen wrote: [...] > I'm not sure if it is a good idea. Please help to review the > following BP. > > https://blueprints.launchpad.net/openstack-ci/+spec/ci-rfc-mechanism The Infra team doesn't rely on blueprints, and instead uses

Re: [openstack-dev] [stable][horizon] adding stable reviewer

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 09/10/15 13:44, Thierry Carrez wrote: > Ihar Hrachyshka wrote: >> Welcome Doug! > > Please (re)read and apply the policy at: > https://wiki.openstack.org/wiki/StableBranch#Stable_branch_policy Thank you Ihar! Best, Matthias -BEGIN PGP

Re: [openstack-dev] [Fuel] py.test vs testrepository

Thank you guys for all your help! Special thanks to Robert who helped to find a workaround for an issue [1] that didn’t let us use testr for Fuel Client. The patch [2] was merged and both unit and functional tests are launched by subunit and the data is maintained by testrepository. Please

Re: [openstack-dev] [all] Recording little everyday OpenStack successes

> On 09 Oct 2015, at 11:42, Thierry Carrez wrote: > > Hello everyone, > > OpenStack has become quite big, and it's easier than ever to feel lost, > to feel like nothing is really happening. It's more difficult than ever > to feel part of a single community, and to

[openstack-dev] [all] jobs that make break when we remove Devstack extras.d in 10 weeks

>From now until the removal of devstack extras.d support I'm going to send a weekly email of jobs that may break. A warning was added that we can track in logstash. Here are the top 25 jobs (by volume) that are currently tripping the warning: gate-murano-devstack-dsvm

Re: [openstack-dev] [all] jobs that make break when we remove Devstack extras.d in 10 weeks

On 10/09/2015 12:35 PM, Sean Dague wrote: From now until the removal of devstack extras.d support I'm going to send a weekly email of jobs that may break. A warning was added that we can track in logstash. Here are the top 25 jobs (by volume) that are currently tripping the warning:

Re: [openstack-dev] [swift] Plan to port Swift to Python 3

Hi, Le 09/10/2015 12:12, vishal yadav a écrit : However I was just checking if you considered using 2to3. I can understand that translation using this tool might not cover every area in the code more specifically custom/3rd party libraries (non-standard python libraries) but IMO it can do fixer

Re: [openstack-dev] [ceilometer] Inconsistent timestamping of polled data

Hi! Looks good to me, especially for cases when after some incident we gather a great amount of notifications in queue and stated to work with it so some data will have incorrect timestamp if it set only when sample is created. Cheers, Igor Degtiarov Software Engineer Mirantis Inc.

Re: [openstack-dev] [mistral] [heat] Mistral Workflow resource type - resource signal handling

> On 08 Oct 2015, at 23:27, ELISHA, Moshe (Moshe) > wrote: > > Hi, > > I would like to propose a change in the behavior of the OS::Mistral::Workflow > resource signal. > > CURRENT: > The OS::Mistral::Workflow resource type is expecting the following

[openstack-dev] [stable][horizon] adding stable reviewer

Hello, who would be the person to talk to, to add a new reviewer to horizon-stable-maint I would like Doug Fish aka drfish (on launchpad) added. Unfortunately, the fields on https://review.openstack.org/#/admin/groups/537,members are greyed out for me. Thanks, Matthias

Re: [openstack-dev] [stable][horizon] adding stable reviewer

> On 09 Oct 2015, at 12:44, Matthias Runge wrote: > > Hello, > > who would be the person to talk to, to add a new reviewer to > horizon-stable-maint > > I would like Doug Fish aka drfish (on launchpad) added. > > Unfortunately, the fields on >

Re: [openstack-dev] [stable][horizon] adding stable reviewer

Ihar Hrachyshka wrote: > Welcome Doug! Please (re)read and apply the policy at: https://wiki.openstack.org/wiki/StableBranch#Stable_branch_policy -- Thierry Carrez (ttx) signature.asc Description: OpenPGP digital signature

Re: [openstack-dev] [CI] Try to introduce RFC mechanism to CI.

On 10/09/2015 12:06 PM, Tang Chen wrote: On 10/09/2015 05:48 PM, Jordan Pittier wrote: Hi, On Fri, Oct 9, 2015 at 11:00 AM, Tang Chen > wrote: Hi, CI systems will run tests for each patch once it is submitted or modified.

Re: [openstack-dev] [infra] Try to introduce RFC mechanism to CI.

On 2015-10-09 18:06:55 +0800 (+0800), Tang Chen wrote: [...] > It is just a waste of resource if reviewers are discussing about > where this function should be, or what the function should be > named. After all these details are agreed on, run the CI. [...] As one of the people maintaining the

Re: [openstack-dev] [all] Recording little everyday OpenStack successes

On 2015-10-09 15:53:17 +0200 (+0200), Ihar Hrachyshka wrote: [...] > There are already multiple karmabot implementations that could be > reused, like https://github.com/chromakode/karmabot > > Can we just adopt one of those? Perhaps, though we're trying to reduce rather than increase the number

Re: [openstack-dev] [kolla] Backport policy for Liberty

On Thu, Oct 8, 2015 at 2:47 PM, Steven Dake (stdake) wrote: > Kolla operators and developers, > > The general consensus of the Core Reviewer team for Kolla is that we > should embrace a liberal backport policy for the Liberty release. An > example of liberal -> We add a new

Re: [openstack-dev] Requests + urllib3 + distro packages

On 2015-10-09 14:58:36 +0100 (+0100), Cory Benfield wrote: [...] > IMO, what OpenStack needs is a decision about where it’s getting > its packages from, and then to refuse to mix the two. I have yet to find a Python-based operating system installable in whole via pip. There will always be

Re: [openstack-dev] [stable][horizon] adding stable reviewer

Hi Matthias That group is owned by stable-maint-core So you should look at members there (https://review.openstack.org/#/admin/groups/530,members) and ask some of them to add Doug. Best Yolanda El 09/10/15 a las 12:44, Matthias Runge escribió: Hello, who would be the person to talk to, to

[openstack-dev] [All][Elections] Vote Vote Vote in the TC election!

We are coming down the the last hours for voting in the TC election. Search your gerrit preferred email address[0] for the following subject: Poll: OpenStack Technical Committee (TC) Election - October 2015 That is your ballot and links you to the voting application. Please vote. If you have

Re: [openstack-dev] Requests + urllib3 + distro packages

> On 9 Oct 2015, at 14:40, William M Edmonds wrote: > > Cory Benfield writes: > > > The problem that occurs is the result of a few interacting things: > > > - requests has very very specific versions of urllib3 it works with. > > > So specific they aren't always

Re: [openstack-dev] [all] service catalog: TNG

On 10/09/2015 12:28 PM, Monty Taylor wrote: On 10/09/2015 11:21 AM, Shamail wrote: On Oct 9, 2015, at 10:39 AM, Sean Dague wrote: It looks like some great conversation got going on the service catalog standardization spec / discussion at the last cross project meeting.

Re: [openstack-dev] [ironic] Nominating two new core reviewers

++ on both counts! On Thu, Oct 8, 2015 at 2:47 PM, Jim Rollenhagen wrote: > Hi all, > > I've been thinking a lot about Ironic's core reviewer team and how we might > make it better. > > I'd like to grow the team more through trust and mentoring. We should be > able to

Re: [openstack-dev] [Murano] py26 support in python-muranoclient

Serg, Jeremy, Thank you for your response, so the issue I ran into with my patch is the gate job failing on python26. You can see it here: https://review.openstack.org/#/c/232271/ Serg suggested that we add 2.6 support to tosca-parser, which is fine with us. But I got a bit confused after

Re: [openstack-dev] [congress] Symantec's security group management policies

Hi Su, This looks very good. Will it be possible to put your usecase as part of the Usecase VM. Have you tried it out on the Usecase VM that I published earlier. I can help if you get stuck. LMK, Thanks, -Shiv From: Su Zhang [mailto:westlif...@gmail.com] Sent: Thursday, October 08, 2015

Re: [openstack-dev] [nova] nova-manage db archive_deleted_rows broken

On 10/07/2015 11:04 AM, Matt Riedemann wrote: I'm wondering why we don't reverse sort the tables using the sqlalchemy metadata object before processing the tables for delete? That's the same thing I did in the 267 migration since we needed to process the tree starting with the leafs and then

Re: [openstack-dev] [fuel] PTL & Component Leads elections

Congratulations to Dmitry! Now you are officially titled with PTL. It won't be easy, but we will support you! 118 contributors voted. Thanks everyone! Thank you Sergey for organizing elections for us. On Thu, Oct 8, 2015 at 3:52 PM Sergey Lukjanov wrote: > Voting period

Re: [openstack-dev] [Openstack-operators] Scheduler proposal

Excerpts from Chris Friesen's message of 2015-10-08 23:52:41 -0700: > On 10/08/2015 01:37 AM, Clint Byrum wrote: > > Excerpts from Maish Saidel-Keesing's message of 2015-10-08 00:14:55 -0700: > >> Forgive the top-post. > >> > >> Cross-posting to openstack-operators for their feedback as well. > >>

Re: [openstack-dev] [all] Recording little everyday OpenStack successes

Thierry Carrez wrote on 10/09/2015 05:42:49 AM: ... > So whenever you feel like you made progress, or had a little success in > your OpenStack adventures, or have some joyful moment to share, just > throw the following message on your local IRC channel: > > #success [Your

Re: [openstack-dev] [kolla] Backport policy for Liberty

Hello, Since we have little actual logic, and ansible itself is pretty pluggable by its very nature, backporting should be quite easy and would not affect existing deployment much. We will make sure that it will be safe to have stable/liberty code and will keep working at all times. I agree

Re: [openstack-dev] [all] service catalog: TNG

> On Oct 9, 2015, at 12:28 PM, Monty Taylor wrote: > >> On 10/09/2015 11:21 AM, Shamail wrote: >> >> >>> On Oct 9, 2015, at 10:39 AM, Sean Dague wrote: >>> >>> It looks like some great conversation got going on the service catalog >>> standardization

Re: [openstack-dev] [all] service catalog: TNG

Excerpts from Adam Young's message of 2015-10-09 09:51:55 -0700: > On 10/09/2015 12:28 PM, Monty Taylor wrote: > > On 10/09/2015 11:21 AM, Shamail wrote: > >> > >> > >>> On Oct 9, 2015, at 10:39 AM, Sean Dague wrote: > >>> > >>> It looks like some great conversation got going on

  1   2   >