Re: [openstack-dev] Scheduler proposal

On 10/09/2015 07:29 PM, Clint Byrum wrote: Even if you figured out how to make the in-memory scheduler crazy fast, There's still value in concurrency for other reasons. No matter how fast you make the scheduler, you'll be slave to the response time of a single scheduling request. If you take 1ms

Re: [openstack-dev] Ceilometer, New measurements, Types

Meters are measurable value. So it cannot be a string. If you really need to have notifications about event that is exist but cannot be measured you can use Events. http://docs.openstack.org/admin-guide-cloud/telemetry-events.html Cheers, Igor Degtiarov Software Engineer Mirantis Inc. www.miran

Re: [openstack-dev] Ceilometer, New measurements, Types

Meters are measurable value. So it cannot be a string. If you really need to have notifications about event that is exist but cannot be measured you can use Events. http://docs.openstack.org/admin-guide-cloud/telemetry-events.html Cheers, Igor Degtiarov Software Engineer Mirantis Inc. www.miran

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 > > > wrote: >> > >> > Has anybody looked at why 1

[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] [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 [mailto:dsta

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, Octob

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 to keep their in-me

Re: [openstack-dev] Scheduler proposal

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 > > wrote: > > > > Has anybody looked at why 1 instance is too slow and what it would take > > to >

Re: [openstack-dev] Scheduler proposal

On 10/09/2015 03:36 PM, Ian Wells wrote: On 9 October 2015 at 12:50, Chris Friesen mailto:chris.frie...@windriver.com>> 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 us

[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: http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_4ef58

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 reviewer team and how we might

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) Subjec

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 >

[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

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 from

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 o

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 | http

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 Date: 2015/10/09 03:55 PM Sub

[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 fo

[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 determ

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 resources:

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 periodi

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. >> > > Currently we pull data

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, Jonathan D. Proulx > :

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 python

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 t

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: > https://etherpad.openstack.org/p/tripleo-review-prioriti

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 se

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 com

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 th

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 operator I'd be happy to

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 ether pad stevem

[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 Dash

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 me

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 thi

Re: [openstack-dev] Scheduler proposal

And also we should probably deprecate/not recommend: http://docs.openstack.org/developer/nova/api/nova.scheduler.filters.json_filter.html#nova.scheduler.filters.json_filter.JsonFilter That filter IMHO basically disallows optimizations like forming SQL statements for each filter (and then lettin

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

I would like to start running a recurring bug squashing day. The general idea is to get more focus on bugs and stability. You can find the details here: https://etherpad.openstack.org/p/keystone-office-hours -- David blog: http://www.traceback.org twitter: http://twitter.com/dstanek www: http://

[openstack-dev] Different OpenStack components

Hi Folks,I have been working with OpenStack from a while now, I know that other than the main componets (nova, neutron, glance, cinder, horizon, tempest, keystone etc) there are many more components in OpenStack (like Sahara, Trove).So, where can I see the list of all existing OpenStack components

Re: [openstack-dev] Scheduler proposal

On 10/09/2015 12:25 PM, Alec Hothan (ahothan) wrote: Still the point from Chris is valid. I guess the main reason openstack is going with multiple concurrent schedulers is to scale out by distributing the load between multiple instances of schedulers because 1 instance is too slow. This discussi

Re: [openstack-dev] Scheduler proposal

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 the best, attempt to schedule at your choice, retry on failure. As long as you have

Re: [openstack-dev] Blueprint to change (expand) traditional Ethernet interface naming schema in Fuel

> > >I would like to pay your attention to the changing interface naming > >schema, which is proposed to be implemented in FuelA [1].A In brief, > >Ethernet network interfaces may not be named as ethX, and there is a > >reported bug about itA [2] > >There are a lot of reasons to

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

On 10/09/2015 02:16 PM, Matt Riedemann wrote: On 10/9/2015 12:03 PM, Jay Pipes wrote: I had a proposal [1] to completely rework the whole shadow table mess and db archiving functionality. I continue to believe that is the appropriate solution for this, and that we should rip out the existing fun

Re: [openstack-dev] Scheduler proposal

Excerpts from Zane Bitter's message of 2015-10-09 17:09:46 +: > On 08/10/15 21:32, Ian Wells wrote: > > > > > 2. if many hosts suit the 5 VMs then this is *very* unlucky,because > > we should be choosing a host at random from the set of > > suitable hosts and that's a huge coincidence

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

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 operator I'd be happy to use SRV records to define endpoints, :>though multiple regi

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

There is a need to distinguish between server side py26 support which is generally under the control of the service provider and py26 support on the client side. For a service provider to push all of their hypervisors and service machines to RHEL 7 is under their control but requiring all of their

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

Hey Kyle, We are down to couple of patches that are awaiting approval/merge. As soon as it is done, I will let you know. Thanks -Sukhdev On Fri, Oct 9, 2015 at 9:39 AM, Kyle Mestery wrote: > On Fri, Oct 9, 2015 at 10:13 AM, Gary Kotton wrote: > >> Hi, >> Who will be creating the stable/liber

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

Excerpts from Matt Riedemann's message of 2015-10-09 09:51:28 -0500: > > On 10/9/2015 1:49 AM, Paul Carlton wrote: > > > > 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/#/

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

> From: Clark Boylan > To: openstack-dev@lists.openstack.org > Date: 10/09/2015 02:00 PM > Subject: Re: [openstack-dev] [Murano] py26 support in python-muranoclient > > > > On Fri, Oct 9, 2015, at 10:32 AM, Vahid S Hashemian wrote: > > Serg, Jeremy, > > > > Thank you for your response, so the

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

 Hi, Neutrons, We have desire to have an API for neutron to return ip-margin, or the number of IP still available for use, for each network belong to a tenant. I have filed a launchpad issue 1503462. This is now marked as duplicate of 1457986. I am glad to see there are more parties that are inte

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

On 10 October 2015 at 03:57, Cory Benfield wrote: > >> On 9 Oct 2015, at 15:18, Jeremy Stanley wrote: >> >> 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

Re: [openstack-dev] Scheduler proposal

Still the point from Chris is valid. I guess the main reason openstack is going with multiple concurrent schedulers is to scale out by distributing the load between multiple instances of schedulers because 1 instance is too slow. This discussion is about coordinating the many instances of schedu

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

On 10/09/2015 01:39 PM, David Stanek wrote: On Fri, Oct 9, 2015 at 1:28 PM, Jonathan D. Proulx mailto:j...@csail.mit.edu>> wrote: On Fri, Oct 09, 2015 at 01:01:20PM -0400, Shamail wrote: :> On Oct 9, 2015, at 12:28 PM, Monty Taylor mailto:mord...@inaugust.com>> wrote: :> :>> On

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

On 10/9/2015 12:03 PM, Jay Pipes wrote: 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 th

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

Thank Clark. That really helps. We'll consider this timeline and make a decision on which way to go bearing in mind that waiting for 2.6 phase out would mean a 2 months delay in getting this blueprint implemented. Regards, -

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

This sounds good, I was hoping it'd be acceptable to use etherpad. I filed a blueprint [1] but I'm anticipating using the etherpad much more regularly to track which files are being worked or completed. [1] https://blueprints.launchpad.net/heat/+spec/mox-to-mock-conversion [2] https://etherpad.

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

As an Op, that sounds reasonable so long as they aren't defaulted on. In theory it shouldn't be much different then a distro adding additional packages. The new packages don't affect existing systems unless the op requests them to be installed. With my App Catalog hat on, I'm curious how horizo

Re: [openstack-dev] Scheduler proposal

Excerpts from Chris Friesen's message of 2015-10-09 10:54:36 -0700: > On 10/09/2015 11:09 AM, Zane Bitter wrote: > > > The optimal way to do this would be a weighted random selection, where the > > probability of any given host being selected is proportional to its > > weighting. > > (Obviously t

Re: [openstack-dev] Scheduler proposal

On 10/09/2015 11:09 AM, Zane Bitter wrote: The optimal way to do this would be a weighted random selection, where the probability of any given host being selected is proportional to its weighting. (Obviously this is limited by the accuracy of the weighting function in expressing your actual pref

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

On Fri, Oct 9, 2015, at 10:32 AM, Vahid S Hashemian wrote: > 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

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

On Fri, Oct 9, 2015 at 1:28 PM, Jonathan D. Proulx wrote: > On Fri, Oct 09, 2015 at 01:01:20PM -0400, Shamail wrote: > :> 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: > :>>> >

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 message here] > > The

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 readi

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] service catalog: TNG

On Fri, Oct 09, 2015 at 01:01:20PM -0400, Shamail wrote: :> 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 catal

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 the service catalo

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 ended and so we have an

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 promote someone to core bas

Re: [openstack-dev] Scheduler proposal

On 08/10/15 21:32, Ian Wells wrote: > 2. if many hosts suit the 5 VMs then this is *very* unlucky,because we should be choosing a host at random from the set of suitable hosts and that's a huge coincidence - so this is a tiny corner case that we shouldn't be designing around He

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 spec / discussion at the last cross proj

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 eve

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 wit

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. Sorry I wasn't there

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 1:2

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 m

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 if this is a ques

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] [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 community, and to celebrate littl

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 ever > > to feel part of

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] service catalog: TNG

On 10/09/2015 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. Just so folks know, the collection of existing service catalogs has been up

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

> 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 if this is a question that has already been addr

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

>-Original Message- >From: Jeremy Stanley [mailto:fu...@yuggoth.org] >Sent: Friday, October 9, 2015 1:17 PM >To: OpenStack Development Mailing List (not for usage questions) > >Subject: Re: [openstack-dev] [infra] Try to introduce RFC mechanism to CI. > >On 2015-10-09 18:06:55 +0800

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

On 10/09/2015 11:07 AM, David Lyle wrote: I'm in too. Yes please. On Fri, Oct 9, 2015 at 8:51 AM, Dean Troyer wrote: On Fri, Oct 9, 2015 at 9:39 AM, Sean Dague wrote: Lastly, I think it's pretty clear we probably need a dedicated workgroup meeting to keep this ball rolling, come to a rea

[openstack-dev] [Neutron] L2 gateway project

Hi, Who will be creating the stable/liberty branch? Thanks Gary __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.o

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

> On Oct 9, 2015, at 10:49 AM, John Griffith wrote: > > ​Great idea Thierry, great to promote some positive things! Thanks for > putting this together.​ +1 Great indeed... thanks Thierry. Regards, Shamail __ OpenStack

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

I'm in too. David On Fri, Oct 9, 2015 at 8:51 AM, Dean Troyer wrote: > On Fri, Oct 9, 2015 at 9:39 AM, Sean Dague wrote: >> >> Lastly, I think it's pretty clear we probably need a dedicated workgroup >> meeting to keep this ball rolling, come to a reasonable plan that >> doesn't break any exist

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

> On 9 Oct 2015, at 15:18, Jeremy Stanley wrote: > > 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 sy

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

On 10/9/2015 1:49 AM, Paul Carlton wrote: 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

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

On Fri, Oct 9, 2015 at 9:39 AM, Sean Dague wrote: > Lastly, I think it's pretty clear we probably need a dedicated workgroup > meeting to keep this ball rolling, come to a reasonable plan that > doesn't break any existing deployed code, but lets us get to a better > world in a few cycles. annegen

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

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 community, and to celebrate little successes > a

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

I have two suggestions for handling both new panels and refactoring existing panels that I think could benefit us in the future: 1) When we are creating a panel that's a major refactor of an existing it should be a new separate panel, not a direct code replacement of the existing panel 2) New panel

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

For those who are interested in more of the historical aspect around this, https://github.com/kennethreitz/requests/issues/1811 https://github.com/kennethreitz/requests/pull/1812 My own thoughts are varied here, I get the angle of vendoring, but I don't get the resistance to unvendoring it (whi

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

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 ether pad stevemar and I started working on the other day) - https://etherpa

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 _at_leas

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 server service to Ans

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 o

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 released yet. > > > > This shou

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

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 ever > to feel part of a single community, and to celebrate little successes > and progre

  1   2   >