[openstack-dev] [Ceilometer] [Bug#1497073]The return sample body of sample-list is different when use -m and not

Hi,Here is an open bug : https://bugs.launchpad.net/ceilometer/+bug/1497073Is it a bug or not?For the command "ceilometer sample-list --meter cpu", it calls "/v2/meter" API and return the OldSample objectswhich return body is different from "ceilometer sample-list --query 'meter=cpu'".To fix this i

[openstack-dev] [mistral] Planning and prioritizing session for Mitaka

Team, We’ve done a great job at the summit discussing our most hot topics within the project and a lot of important decisions were made. I would like to have though one more session in IRC to wrap up this by going over all the BPs/bugs we created in order to scope and prioritize them. I’m prop

[openstack-dev] [kuryr] external-network-connectivity

Hi All, Would appreciate your views on https://blueprints.launchpad.net/kuryr/+spec/external-network-connectivity . -Vikas Choudhary __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev

[openstack-dev] [kuryr] mutihost networking with nova vm as docker host

Hi All, I would appreciate inputs on following queries: 1. Are we assuming nova bm nodes to be docker host for now? If Not: - Assuming nova vm as docker host and ovs as networking plugin: This line is from the etherpad[1], "Eachdriver would have an executable that receives th

Re: [openstack-dev] [neutron] Stepping Down from Neutron Core Responsibilities

On Thu, Nov 5, 2015 at 1:28 AM, Edgar Magana wrote: > Dear Colleagues, > > I have been part of this community from the very beginning when in Santa > Clara, CA back in 2011 a bunch of we crazy people decided to work on this > networking project. > Neutron has become is a very unique piece of code

[openstack-dev] [oslo_messaging] Regarding " WARNING [oslo_messaging.server] wait() should have been called after stop() as wait() ...

Hi, I'm seeing the below warning message continuously: 2015-11-04 21:09:38 WARNING [oslo_messaging.server] wait() should have been called after stop() as wait() waits for existing messages to finish processing, it has been 692.98 seconds and stop() still has not been called How to avoid this wa

[openstack-dev] [kuryr] network control plane (libkv role)

Hi all, By network control plane i specifically mean here sharing network state across docker daemons sitting on different hosts/nova_vms in multi-host networking. libnetwork provides flexibility where vendors have a choice between network control plane to be handled by libnetwork(libkv) or remot

[openstack-dev] [senlin] Mitaka summit meetup - a summary

Hi, Thanks for joining the senlin meetup last week at Tokyo summit. We know some of you were not able to make it for various reasons. I'm trying to summarize things we discussed during the meetup and some preliminary conclusions we got. Please feel free to reply to this email or find the team on #

Re: [openstack-dev] [requirements] [infra] speeding up gate runs?

On 11/05/2015 01:43 AM, Matthew Thode wrote: python wheel repo could help maybe? So I think we've (i.e. greghaynes) got that mostly in place, we just got a bit side-tracked. [1] adds mirror slaves, that build the wheels using pypi-mirror [2], and then [3] adds the jobs. This should give us wh

Re: [openstack-dev] [kuryr] competing implementations

If we see from the angle of the contributor whose approach would not be better than other competing one, it will be far easy for him to accept logic at discussion stage rather after weeks of tracking review request and addressing review comments. On 5 Nov 2015 08:24, "Vikas Choudhary" wrote: > @T

Re: [openstack-dev] [kuryr] competing implementations

@Toni , In scenarios where two developers, with different implementation approaches, are not able to reach any consensus over gerrit or ml, IMO, other core members can do a voting or discussion and then PTL should take a call which one to accept and allow for implementation. Anyways community has

Re: [openstack-dev] [nova][api] Pagination in thre API

On Thu, Nov 05, 2015 at 01:09:36PM +1100, Tony Breeds wrote: > Hi All, > Around the middle of October a spec [1] was uploaded to add pagination > support to the os-hypervisors API. While I recognize the use case it seemed > like adding another pagination implementation wasn't an awesome idea.

[openstack-dev] [nova][api]

Hi All, Around the middle of October a spec [1] was uploaded to add pagination support to the os-hypervisors API. While I recognize the use case it seemed like adding another pagination implementation wasn't an awesome idea. Today I see 3 more requests to add pagination to APIs [2] Perhaps I

Re: [openstack-dev] [neutron] Stepping Down from Neutron Core Responsibilities

On 11/04/2015 07:28 PM, Edgar Magana wrote: > Dear Colleagues, > > I have been part of this community from the very beginning when in Santa > Clara, CA back in 2011 a bunch of we crazy people decided to work on this > networking project. > Neutron has become is a very unique piece of code and it

Re: [openstack-dev] openstack-barbican-authenticate-keystone-barbican-command

Hi Arif-- Maybe using the OpenStack client would be easier for you. It will take care of authenticating with Keystone, setting the HTTP headers, and providing reasonable defaults. It looks like you have installed OpenStack with DevStack. If this is the case: $ cd ~/devstack $

Re: [openstack-dev] [Neutron][IPAM] Arbitrary JSON blobs in ipam db tables

Shraddha Pandhe wrote: On Wed, Nov 4, 2015 at 3:12 PM, Kevin Benton mailto:blak...@gmail.com>> wrote: >If we add our own database for internal stuff, we go back to the same problem of allowing bad design. I'm not sure I understand what you are saying here. A JSON blob that onl

[openstack-dev] [neutron] Stepping Down from Neutron Core Responsibilities

Dear Colleagues, I have been part of this community from the very beginning when in Santa Clara, CA back in 2011 a bunch of we crazy people decided to work on this networking project. Neutron has become is a very unique piece of code and it requires an approval team that will always be on the t

Re: [openstack-dev] [all][api][tc][perfromance] API for getting only status of resources

On 5 November 2015 at 13:06, Boris Pavlovic wrote: > Robert, > > I don't have the exactly numbers, but during the real testing of real > deployments I saw the impact of polling resource, this is one of the reason > why we have to add quite big sleep() during polling in Rally to reduce > amount of

Re: [openstack-dev] [all][ironic] How to proceed about deprecation of untagged code?

Em 04.11.2015 17:19, Jim Rollenhagen escreveu: On Wed, Nov 04, 2015 at 02:55:49PM -0500, Sean Dague wrote: On 11/04/2015 02:42 PM, Jim Rollenhagen wrote: > On Wed, Nov 04, 2015 at 04:08:18PM -0300, Gabriel Bezerra wrote: >> Em 04.11.2015 11:32, Jim Rollenhagen escreveu: >>> On Wed, Nov 04, 2015 a

Re: [openstack-dev] [all][api][tc][perfromance] API for getting only status of resources

Robert, I don't have the exactly numbers, but during the real testing of real deployments I saw the impact of polling resource, this is one of the reason why we have to add quite big sleep() during polling in Rally to reduce amount of GET requests and avoid DDoS of OpenStack.. In any case it does

Re: [openstack-dev] [Neutron][IPAM] Arbitrary JSON blobs in ipam db tables

On Wed, Nov 4, 2015 at 3:12 PM, Kevin Benton wrote: > >If we add our own database for internal stuff, we go back to the same > problem of allowing bad design. > > I'm not sure I understand what you are saying here. A JSON blob that only > one driver knows how to interpret is worse than a vendor t

Re: [openstack-dev] [all][api][tc][perfromance] API for getting only status of resources

Sean, This seems like a fundamental abuse of HTTP honestly. If you find > yourself creating a ton of new headers, you are probably doing it wrong. I totally agree on this. We shouldn't add a lot of HTTP headers. Imho why not just return in body string with status (in my case). > I think longer

Re: [openstack-dev] [all][api][tc][perfromance] API for getting only status of resources

John, > Our resources are not. We've also had specific requests to prevent > > header bloat because it impacts the HTTP caching systems. Also, it's > > pretty clear that headers are really not where you want to put volatile > > information, which this is. > Hmm, you do make a good point about cach

Re: [openstack-dev] [neutron][stable] should we open gate for per sub-project stable-maint teams?

On 3 November 2015 at 08:49, Ihar Hrachyshka wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi all, > > currently we have a single neutron-wide stable-maint gerrit group that > maintains all stable branches for all stadium subprojects. I believe > that in lots of cases it would be b

Re: [openstack-dev] Announcing a new library: requestsexceptions

On 11/04/2015 06:30 PM, James E. Blair wrote: Hi, I'm pleased to announce the availability of a new micro-library named requestsexceptions. Now the task of convincing the requests library not to fill up your filesystem with warnings about SSL requests has never been easier! Over in infra-land,

[openstack-dev] [Designate] Mitaka Summit Notes

Here are my rough notes I wrote up about the Mitaka design summit, and what designate covered during the week. Design Summit = This was a much more relaxed summit for Designate. We had done a huge amount of work in Vancouver, and we were nailing down details and doing cross project wo

[openstack-dev] Announcing a new library: requestsexceptions

Hi, I'm pleased to announce the availability of a new micro-library named requestsexceptions. Now the task of convincing the requests library not to fill up your filesystem with warnings about SSL requests has never been easier! Over in infra-land, we use the requests library a lot, whether it's

Re: [openstack-dev] [Neutron][IPAM] Arbitrary JSON blobs in ipam db tables

>If we add our own database for internal stuff, we go back to the same problem of allowing bad design. I'm not sure I understand what you are saying here. A JSON blob that only one driver knows how to interpret is worse than a vendor table. They both are specific to one driver but at least with a

Re: [openstack-dev] [Neutron][IPAM] Arbitrary JSON blobs in ipam db tables

On Wed, Nov 4, 2015 at 1:38 PM, Armando M. wrote: > > > On 4 November 2015 at 13:21, Shraddha Pandhe > wrote: > >> Hi Salvatore, >> >> Thanks for the feedback. I agree with you that arbitrary JSON blobs will >> make IPAM much more powerful. Some other projects already do things like >> this. >>

Re: [openstack-dev] [puppet] acceptance: run WSGI for API services

Hi, mod_wsgi has some limitations so making order for WSGI services. Reloading and restarting processes is well documented at [1]. Creating ordering is a problem. There are several options: 1. Use uwsgi instead of mod_wsgi 2. Use several apache instances (one instance for one service) 3. Ignore or

[openstack-dev] [trove][release] python-troveclient 1.4.0 release

Hello everyone, We have released the 1.4.0 version of the python-troveclient. In liberty Trove had added more datastores to support clustering but the client was missing an attribute to allow you to set the network and availability zone for each of the instances in the cluster. This troveclient v

Re: [openstack-dev] [all] Outcome of distributed lock manager discussion @ the summit

To clarify that statement a little more, Speaking only for myself as an op, I don't want to support yet one more snowflake in a sea of snowflakes, that works differently then all the rest, without a very good reason. Java has its own set of issues associated with the JVM. Care, and feeding sort

Re: [openstack-dev] [oslo][oslo.config][oslo.service] Dynamic Reconfiguration of OpenStack Services

Excerpts from Joshua Harlow's message of 2015-11-04 14:13:33 -0800: > Agreed, it'd be nice to have an 'audit' of the various projects configs > and try to categorize which ones should be reloadable (and the priority > to make it reloadable) and which ones are service discovery configs (and > pro

Re: [openstack-dev] [oslo][oslo.config][oslo.service] Dynamic Reconfiguration of OpenStack Services

Agreed, it'd be nice to have an 'audit' of the various projects configs and try to categorize which ones should be reloadable (and the priority to make it reloadable) and which ones are service discovery configs (and probably shouldn't be in config in the first place) and which ones are nice to

Re: [openstack-dev] [all] Outcome of distributed lock manager discussion @ the summit

I will be working on adding the Consul driver to Tooz [1]. -Vilobh [1] https://blueprints.launchpad.net/python-tooz/+spec/add-consul-driver On Wed, Nov 4, 2015 at 2:05 PM, Mark Voelker wrote: > On Nov 4, 2015, at 4:41 PM, Gregory Haynes wrote: > > > > Excerpts from Clint Byrum's message of 201

Re: [openstack-dev] [oslo][oslo.config][oslo.service] Dynamic Reconfiguration of OpenStack Services

Ah, I hadn't considered the rabbit_hosts (discovery) case. yeah, that would be a useful thing to be able to tweak live. I haven't needed that feature yet, but could see how that flexibility could come in handy. Thanks, Kevin From: Joshua Harlow [harlo...@

Re: [openstack-dev] [all] Outcome of distributed lock manager discussion @ the summit

On Nov 4, 2015, at 4:41 PM, Gregory Haynes wrote: > > Excerpts from Clint Byrum's message of 2015-11-04 21:17:15 +: >> Excerpts from Joshua Harlow's message of 2015-11-04 12:57:53 -0800: >>> Ed Leafe wrote: On Nov 3, 2015, at 6:45 AM, Davanum Srinivas wrote: > Here's a Devstack revi

Re: [openstack-dev] [oslo][oslo.config][oslo.service] Dynamic Reconfiguration of OpenStack Services

As an Op, I can say the only time I've really wanted to change the config file and felt pain restarting a service was when I needed to adjust the logging level. If that one thing could be done, or it could be done in a completely different way (mgmt unix socket?), I think that would go a very lo

Re: [openstack-dev] [requirements] [infra] speeding up gate runs?

Excerpts from Jeremy Stanley's message of 2015-11-04 21:31:58 +: > On 2015-11-04 15:34:26 -0500 (-0500), Sean Dague wrote: > > This seems like incorrect logic. We should test devstack can do all the > > things on a devstack change, not on every neutron / trove / nova change. > > I'm fine if we

Re: [openstack-dev] [all] Outcome of distributed lock manager discussion @ the summit

On 11/04/2015 03:57 PM, Joshua Harlow wrote: > Ed Leafe wrote: >> On Nov 3, 2015, at 6:45 AM, Davanum Srinivas wrote: >>> Here's a Devstack review for zookeeper in support of this initiative: >>> >>> https://review.openstack.org/241040 >>> >>> Thanks, >>> Dims >> >> I thought that the operators at

Re: [openstack-dev] [all] Outcome of distributed lock manager discussion @ the summit

Excerpts from Clint Byrum's message of 2015-11-04 21:17:15 +: > Excerpts from Joshua Harlow's message of 2015-11-04 12:57:53 -0800: > > Ed Leafe wrote: > > > On Nov 3, 2015, at 6:45 AM, Davanum Srinivas wrote: > > >> Here's a Devstack review for zookeeper in support of this initiative: > > >>

Re: [openstack-dev] [Neutron][IPAM] Arbitrary JSON blobs in ipam db tables

On 4 November 2015 at 13:21, Shraddha Pandhe wrote: > Hi Salvatore, > > Thanks for the feedback. I agree with you that arbitrary JSON blobs will > make IPAM much more powerful. Some other projects already do things like > this. > > e.g. In Ironic, node has driver_info, which is JSON. it also has

Re: [openstack-dev] [requirements] [infra] speeding up gate runs?

On 2015-11-04 15:34:26 -0500 (-0500), Sean Dague wrote: > This seems like incorrect logic. We should test devstack can do all the > things on a devstack change, not on every neutron / trove / nova change. > I'm fine if we want to have a slow version of this for devstack testing > which starts from

Re: [openstack-dev] [kolla][tripleo] Mesos orchestration as discussed at mid cycle (action required from core reviewers)

On 11/03/2015 10:27 PM, Zane Bitter wrote: I think we all agree that using something _like_ Kubernetes would be extremely interesting for controller services, where you have a bunch of heterogeneous services with scheduling constraints (HA), that may need to be scaled out at different rates, &c.

[openstack-dev] [telemetry][ceilometer][aodh][gnocchi] Tokyo summit roundup

hi folks, i want to start off by thanking everyone for joining the telemetry related discussions at the Tokyo summit -- we got some great feedback and ideas. similar to the last summit, here's a rundown of items that we talked about[1] and will be tracking in the upcoming cycle. as before, th

[openstack-dev] [Neutron] Mid-cycle meetup for Mitaka

Hi folks, After some consideration, I am proposing a change for the Mitaka release cycle in relation to the mid-cycle meetup event. My proposal is to defer the gathering to later in the release cycle [1], and assess whether we have it or not based on the course of events in the cycle. If we feel

[openstack-dev] [Cinder] Mitaka Design Summit Recap

Cinder Mitaka Design Summit Summary Will the Real Block Storage Service Please Stand Up === Should Cinder be usable outside of a full OpenStack environment. There are several solutions out there for providing a Software Defined Storage service with p

Re: [openstack-dev] [all] Outcome of distributed lock manager discussion @ the summit

On Nov 4, 2015, at 3:17 PM, Clint Byrum wrote: > What I don't want to see happen is we get into a deadlock where there's > a large portion of users who can't upgrade and no driver to support them. > So lets stay ahead of the problem, and get a set of drivers that works > for everybody! I think t

Re: [openstack-dev] [Neutron][IPAM] Arbitrary JSON blobs in ipam db tables

Hi Salvatore, Thanks for the feedback. I agree with you that arbitrary JSON blobs will make IPAM much more powerful. Some other projects already do things like this. e.g. In Ironic, node has driver_info, which is JSON. it also has an 'extras' arbitrary JSON field. This allows us to put any inform

Re: [openstack-dev] [all] Outcome of distributed lock manager discussion @ the summit

Excerpts from Joshua Harlow's message of 2015-11-04 12:57:53 -0800: > Ed Leafe wrote: > > On Nov 3, 2015, at 6:45 AM, Davanum Srinivas wrote: > >> Here's a Devstack review for zookeeper in support of this initiative: > >> > >> https://review.openstack.org/241040 > >> > >> Thanks, > >> Dims > > > >

Re: [openstack-dev] [all] Outcome of distributed lock manager discussion @ the summit

On 11/04/2015 04:09 PM, Davanum Srinivas wrote: Graham, Agree. Hence the Tooz as the abstraction layer. Folks are welcome to write new drivers or fix existing drivers for Tooz where needed. Yes. This is correct. We cannot grow a hard depend on a Java thing, but optional depends are ok - and i

Re: [openstack-dev] [all] Outcome of distributed lock manager discussion @ the summit

On 5 November 2015 at 09:02, Ed Leafe wrote: > On Nov 3, 2015, at 6:45 AM, Davanum Srinivas wrote: >> >> Here's a Devstack review for zookeeper in support of this initiative: >> >> https://review.openstack.org/241040 >> >> Thanks, >> Dims > > I thought that the operators at that session made it v

Re: [openstack-dev] [all] Outcome of distributed lock manager discussion @ the summit

Graham, Agree. Hence the Tooz as the abstraction layer. Folks are welcome to write new drivers or fix existing drivers for Tooz where needed. -- Dims On Wed, Nov 4, 2015 at 3:04 PM, Hayes, Graham wrote: > On 04/11/15 20:04, Ed Leafe wrote: >> On Nov 3, 2015, at 6:45 AM, Davanum Srinivas wrote:

Re: [openstack-dev] [Neutron][IPAM] Arbitrary JSON blobs in ipam db tables

Arbitrary blobs are a powerful tools to circumvent limitations of an API, as well as other constraints which might be imposed for versioning or portability purposes. The parameters that should end up in such blob are typically specific for the target IPAM driver (to an extent they might even identi

Re: [openstack-dev] [all] Outcome of distributed lock manager discussion @ the summit

On 04/11/15 20:04, Ed Leafe wrote: > On Nov 3, 2015, at 6:45 AM, Davanum Srinivas wrote: >> >> Here's a Devstack review for zookeeper in support of this initiative: >> >> https://review.openstack.org/241040 >> >> Thanks, >> Dims > > I thought that the operators at that session made it very clear

Re: [openstack-dev] [Neutron][IPAM] Arbitrary JSON blobs in ipam db tables

If you have custom data you want to keep for your driver, you should create your own database tables to track that information. For example, the reference driver creates its own tables to track its data in ipam* tables. John On Nov 4, 2015, at 3:46 PM, Shraddha Pandhe mailto:spandhe.openst...@

Re: [openstack-dev] [all] Outcome of distributed lock manager discussion @ the summit

Ed Leafe wrote: On Nov 3, 2015, at 6:45 AM, Davanum Srinivas wrote: Here's a Devstack review for zookeeper in support of this initiative: https://review.openstack.org/241040 Thanks, Dims I thought that the operators at that session made it very clear that they would *not* run any Java appl

[openstack-dev] [Neutron][IPAM] Arbitrary JSON blobs in ipam db tables

Hi folks, I have a small question/suggestion about IPAM. With IPAM, we are allowing users to have their own IPAM drivers so that they can manage IP allocation. The problem is, the new ipam tables in the database have the same columns as the old tables. So, as a user, if I want to have my own logi

Re: [openstack-dev] [requirements] [infra] speeding up gate runs?

On 11/04/2015 03:27 PM, Clark Boylan wrote: > On Wed, Nov 4, 2015, at 09:14 AM, Sean Dague wrote: >> On 11/04/2015 12:10 PM, Jeremy Stanley wrote: >>> On 2015-11-04 08:43:27 -0600 (-0600), Matthew Thode wrote: On 11/04/2015 06:47 AM, Sean Dague wrote: >>> [...] > Is there a nodepool cache

Re: [openstack-dev] [requirements] [infra] speeding up gate runs?

On Wed, Nov 4, 2015, at 09:14 AM, Sean Dague wrote: > On 11/04/2015 12:10 PM, Jeremy Stanley wrote: > > On 2015-11-04 08:43:27 -0600 (-0600), Matthew Thode wrote: > >> On 11/04/2015 06:47 AM, Sean Dague wrote: > > [...] > >>> Is there a nodepool cache strategy where we could pre build these? A 25%

Re: [openstack-dev] [Fuel][Plugins] Role for Fuel Master Node

Thanks Igor, Alex. Guess there isn't any support for running tasks directly on the Fuel Master node for now. I did try moving to deployment_tasks.yaml, however it leads to other issues such as "/etc/fuel/plugins// does not exist" failing on deployments. I'm trying to move back to using the former

Re: [openstack-dev] [all][ironic] How to proceed about deprecation of untagged code?

On Wed, Nov 04, 2015 at 02:55:49PM -0500, Sean Dague wrote: > On 11/04/2015 02:42 PM, Jim Rollenhagen wrote: > > On Wed, Nov 04, 2015 at 04:08:18PM -0300, Gabriel Bezerra wrote: > >> Em 04.11.2015 11:32, Jim Rollenhagen escreveu: > >>> On Wed, Nov 04, 2015 at 08:44:36AM -0500, Jay Pipes wrote: > >>

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

Thanks to everyone who has commented on the spec and/or participated in the discussions at the summit last week. I've uploaded a new patch set that describes my interpretation of the image import workflow and API calls that were discussed. Please take a look and leave comments. -- cheers, brian

Re: [openstack-dev] [all] Outcome of distributed lock manager discussion @ the summit

On Nov 3, 2015, at 6:45 AM, Davanum Srinivas wrote: > > Here's a Devstack review for zookeeper in support of this initiative: > > https://review.openstack.org/241040 > > Thanks, > Dims I thought that the operators at that session made it very clear that they would *not* run any Java applicati

Re: [openstack-dev] [all][ironic] How to proceed about deprecation of untagged code?

On 11/04/2015 02:42 PM, Jim Rollenhagen wrote: > On Wed, Nov 04, 2015 at 04:08:18PM -0300, Gabriel Bezerra wrote: >> Em 04.11.2015 11:32, Jim Rollenhagen escreveu: >>> On Wed, Nov 04, 2015 at 08:44:36AM -0500, Jay Pipes wrote: >>> On 11/03/2015 11:40 PM, Gabriel Bezerra wrote: Hi, Th

Re: [openstack-dev] [all][ironic] How to proceed about deprecation of untagged code?

On Wed, Nov 04, 2015 at 04:08:18PM -0300, Gabriel Bezerra wrote: > Em 04.11.2015 11:32, Jim Rollenhagen escreveu: > >On Wed, Nov 04, 2015 at 08:44:36AM -0500, Jay Pipes wrote: > >On 11/03/2015 11:40 PM, Gabriel Bezerra wrote: > >>Hi, > >> > >>The change in https://review.openstack.org/237122 touche

[openstack-dev] Cinder mid-cycle planning survey

Hi Folks The Cinder team is trying to plan our mid-cycle meetup again. Can anybody interested in attending please fill out this quick survey to help with planning, please? https://www.surveymonkey.com/r/Q5FZX68 Closing date is 11th November. Thanks -- -- Duncan Thomas ___

Re: [openstack-dev] [oslo][oslo.config][oslo.service] Dynamic Reconfiguration of OpenStack Services

Along this line, thinks like the following are likely more changeable (and my guess is operators would want to change them when things start going badly), for example from a nova.conf that I have laying around... [DEFAULT] rabbit_hosts=... rpc_response_timeout=... default_notification_level=..

Re: [openstack-dev] [oslo][oslo.config][oslo.service] Dynamic Reconfiguration of OpenStack Services

gord chung wrote: we actually had a solution implemented in Ceilometer to handle this[1]. that said, based on the results of our survey[2], we found that most operators *never* update configuration files after the initial setup and if they did it was very rarely (monthly updates). the question r

Re: [openstack-dev] [all][ironic] How to proceed about deprecation of untagged code?

Em 04.11.2015 11:32, Jim Rollenhagen escreveu: On Wed, Nov 04, 2015 at 08:44:36AM -0500, Jay Pipes wrote: On 11/03/2015 11:40 PM, Gabriel Bezerra wrote: >Hi, > >The change in https://review.openstack.org/237122 touches a feature from >ironic that has not been released in any tag yet. > >At first,

Re: [openstack-dev] [requirements] [infra] speeding up gate runs?

On 5 November 2015 at 07:37, Sean Dague wrote: > It only really will screw when upper-constraints.txt gets updated on a > branch. Bah, yes. > I honestly think it's ok to not be perfect here. In the base case we'll > speed up a good chunk, and we'll be slower (though not as slow as today) > for

Re: [openstack-dev] [all][api][tc][perfromance] API for getting only status of resources

On 5 November 2015 at 04:42, Sean Dague wrote: > On 11/04/2015 10:13 AM, John Garbutt wrote: > I think longer term we probably need a dedicated event service in > OpenStack. A few of us actually had an informal conversation about this > during the Nova notifications session to figure out if there

Re: [openstack-dev] Troubleshooting cross-project comms

Especially given the pervasiveness of discussion topics. +1 Lee > On Nov 4, 2015, at 12:44 PM, Brad Topol wrote: > > +1 That's an extremely good suggestion!!! > > --Brad > > > Brad Topol, Ph.D. > IBM Distinguished Engineer > OpenStack > (919) 543-0646 > Internet: bto...@us.ibm.com > Assistan

Re: [openstack-dev] Troubleshooting cross-project comms

+1 That's an extremely good suggestion!!! --Brad Brad Topol, Ph.D. IBM Distinguished Engineer OpenStack (919) 543-0646 Internet: bto...@us.ibm.com Assistant: Kendra Witherspoon (919) 254-0680 From: Sean McGinnis To: "OpenStack Development Mailing List (not for usage questions)"

Re: [openstack-dev] [puppet] Match type checking from oslo.config.

> Ouha! I didn't know that property could have parent class defined. > This is nice. Does it work also for parameter ? I haven't tried, but property is just a subclass of parameter so truthy could probably be made a parameter then become a parent of either a property or a parameter. > > The Net

Re: [openstack-dev] [Nova] Migration state machine proposal.

On Wed, Nov 04, 2015 at 06:17:17PM +, Murray, Paul (HP Cloud) wrote: :> From: Jay Pipes [mailto:jaypi...@gmail.com] :> A fair point. However, I think that a generic update VM API, which would :> allow changes to the resources consumed by the VM along with capabiities :> like CPU model or local

Re: [openstack-dev] [requirements] [infra] speeding up gate runs?

On 11/04/2015 01:26 PM, Robert Collins wrote: > On 5 November 2015 at 06:21, Morgan Fainberg > wrote: >> > ... >> >> If it is that easy, what a fantastic win in speeding things up! > > It'll help, but skew as new things are released - so e.g. after a > release of numpy until the next image build

Re: [openstack-dev] [puppet] Match type checking from oslo.config.

Hunter Haugen writes: > I have some code that is similar to this in the F5 and Netscaler > modules. I make a generic "truthy" property that accepts various > truthy/falsy values > (https://github.com/puppetlabs/puppetlabs-netscaler/blob/master/lib/puppet/property/netscaler_ > truthy.rb) then just

Re: [openstack-dev] [requirements] [infra] speeding up gate runs?

On 5 November 2015 at 06:21, Morgan Fainberg wrote: > ... > > If it is that easy, what a fantastic win in speeding things up! It'll help, but skew as new things are released - so e.g. after a release of numpy until the next image builds and is enabled successfully. We could have a network mirror

Re: [openstack-dev] [Nova] Migration state machine proposal.

> From: Jay Pipes [mailto:jaypi...@gmail.com] > On 10/27/2015 01:16 PM, Chris Friesen wrote: > > On 10/26/2015 06:02 PM, Jay Pipes wrote: > > > >> I believe strongly that we should deprecate the existing migrate, > >> resize, an live-migrate APIs in favor of a single consolidated, > >> consistent

[openstack-dev] [release] mitaka release schedule

PTLs and release liaisons, The mitaka release schedule is in the wiki at https://wiki.openstack.org/wiki/Mitaka_Release_Schedule Please note that there are only 5 weeks between Feature Freeze and the final release, instead of the usual 6. This means we have more time before the freeze for feature

Re: [openstack-dev] [oslo][oslo.config][oslo.service] Dynamic Reconfiguration of OpenStack Services

we actually had a solution implemented in Ceilometer to handle this[1]. that said, based on the results of our survey[2], we found that most operators *never* update configuration files after the initial setup and if they did it was very rarely (monthly updates). the question related to Ceilom

Re: [openstack-dev] [neutron][stable] should we open gate for per sub-project stable-maint teams?

This seems we will get some more velocity which is good!! +1 German From: Gary Kotton mailto:gkot...@vmware.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Wednesday, November 4, 2015 at 5:24 AM To: OpenStack Develop

Re: [openstack-dev] [all][api][tc][perfromance] API for getting only status of resources

apologies, if the below was mentioned at some point in this thread. On 04/11/2015 10:42 AM, Sean Dague wrote: This seems like a fundamental abuse of HTTP honestly. If you find yourself creating a ton of new headers, you are probably doing it wrong. if we want to explore the HTTP path, did we con

Re: [openstack-dev] [requirements] [infra] speeding up gate runs?

On Nov 4, 2015 09:14, "Sean Dague" wrote: > > On 11/04/2015 12:10 PM, Jeremy Stanley wrote: > > On 2015-11-04 08:43:27 -0600 (-0600), Matthew Thode wrote: > >> On 11/04/2015 06:47 AM, Sean Dague wrote: > > [...] > >>> Is there a nodepool cache strategy where we could pre build these? A 25% > >>> p

Re: [openstack-dev] [requirements] [infra] speeding up gate runs?

On 11/04/2015 12:10 PM, Jeremy Stanley wrote: > On 2015-11-04 08:43:27 -0600 (-0600), Matthew Thode wrote: >> On 11/04/2015 06:47 AM, Sean Dague wrote: > [...] >>> Is there a nodepool cache strategy where we could pre build these? A 25% >>> performance win comes out the other side if there is a str

Re: [openstack-dev] [requirements] [infra] speeding up gate runs?

On 2015-11-04 08:43:27 -0600 (-0600), Matthew Thode wrote: > On 11/04/2015 06:47 AM, Sean Dague wrote: [...] > > Is there a nodepool cache strategy where we could pre build these? A 25% > > performance win comes out the other side if there is a strategy here. > > python wheel repo could help maybe

Re: [openstack-dev] [infra][dsvm] openstack packages pre-installed dsvm node?

On 2015-11-04 18:14:43 +0800 (+0800), Gareth wrote: > When choosing nodes to run a gate job, is there a liberty-trusty node? > The liberty core services is installed and well setup. It is helpful > for development on non-core projects and saves much time. Integration tests really do need to instal

Re: [openstack-dev] [Fuel][Plugins][Ironic] Deploy Ironic with fuel ?

Pavlo, I tried to deploy Ironic from Fuel 8.0 release (iso build fuel-community-8.0-83-2015-11-02_05-42-11) 4b1f91ad496c571e4cbc5931134db6479e582c8b After creating a fuel network-group as You suggested to Loic and configuring an Ironic deployment (4 nodes including controller, compute, cind

Re: [openstack-dev] [requirements] [infra] speeding up gate runs?

On 11/04/2015 07:47 AM, Sean Dague wrote: > I was spot checking the grenade multinode job to make sure it looks like > it was doing the correct thing. In doing so I found that ~15minutes of > it's hour long build time is compiling lxml and numpy 3 times each. > > Due to our exact calculations by u

Re: [openstack-dev] [TripleO] Proposing Ian Wienand as core reviewer on diskimage-builder

On Wed, Nov 4, 2015 at 12:25 AM, Gregory Haynes wrote: > Hello everyone, > > I would like to propose adding Ian Wienand as a core reviewer on the > diskimage-builder project. Ian has been making a significant number of > contributions for some time to the project, and has been a great help in > re

Re: [openstack-dev] [requirements] [infra] speeding up gate runs?

On 11/04/2015 10:50 AM, Brant Knudson wrote: > > > On Wed, Nov 4, 2015 at 6:47 AM, Sean Dague > wrote: > > I was spot checking the grenade multinode job to make sure it looks like > it was doing the correct thing. In doing so I found that ~15minutes of > it's

Re: [openstack-dev] [puppet] Creating puppet-keystone-core and proposing Richard Megginson core-reviewer

On 11/03/2015 03:56 PM, Matt Fischer wrote: > Sorry I replied to this right away but used the wrong email address and > it bounced! > >> I've appreciated all of richs v3 contributions to keystone. +1 from me. 2 positives votes from our core-reviewer team. No negative vote at all. I guess that'

Re: [openstack-dev] [release] new change management tools and processes for stable/liberty and mitaka

Excerpts from Louis Taylor's message of 2015-11-04 08:05:44 +: > On Wed, Nov 04, 2015 at 03:03:29PM +1300, Fei Long Wang wrote: > > Hi Doug, > > > > Thanks for posting this. I'm working on this for Zaqar now and there is a > > question. As for the stable/liberty patch, where does the "60fdcaba

Re: [openstack-dev] [api][nova] Handling lots of GET query string parameters?

Inline, Salvatore On 4 November 2015 at 15:11, Cory Benfield wrote: > > > On 4 Nov 2015, at 13:13, Salvatore Orlando > wrote: > > > > Regarding Jay's proposal, this would be tantamount to defining an API > action for retrieving instances, something currently being discussed here > [1]. > > The

Re: [openstack-dev] [requirements] [infra] speeding up gate runs?

On Wed, Nov 4, 2015 at 6:47 AM, Sean Dague wrote: > I was spot checking the grenade multinode job to make sure it looks like > it was doing the correct thing. In doing so I found that ~15minutes of > it's hour long build time is compiling lxml and numpy 3 times each. > > I've always wondered why

Re: [openstack-dev] [all][api][tc][perfromance] API for getting only status of resources

On 11/04/2015 10:13 AM, John Garbutt wrote: > On 4 November 2015 at 14:49, Jay Pipes wrote: >> On 11/04/2015 09:32 AM, Sean Dague wrote: >>> >>> On 11/04/2015 09:00 AM, Jay Pipes wrote: On 11/03/2015 05:20 PM, Boris Pavlovic wrote: > > Hi stackers, > > Usually such projec

Re: [openstack-dev] [oslo][oslo.config][oslo.service] Dynamic Reconfiguration of OpenStack Services

Excerpts from Marian Horban's message of 2015-11-04 17:00:55 +0200: > Hi guys, > > Unfortunately I haven't been on Tokio summit but I know that there was > discussion about dynamic reloading of configuration. > Etherpad refs: > https://etherpad.openstack.org/p/mitaka-cross-project-dynamic-config-s

Re: [openstack-dev] [nova] Adding a new feature in Kilo. Is it possible?

Hi John, Just to let you know, I have just filled in the blueprint here: https://blueprints.launchpad.net/nova/+spec/libvirt-vhostuser-vrouter-vif Regards, Michal On 4 November 2015 at 12:20, John Garbutt wrote: > In terms of adding this into master, we can go for a spec-less > blueprint in No

Re: [openstack-dev] Troubleshooting cross-project comms

On Wed, Nov 04, 2015 at 07:30:51AM -0500, Sean Dague wrote: > On 10/28/2015 07:15 PM, Anne Gentle wrote: > > Has anyone considered using #openstack-dev, instead of a new meeting > room? #openstack-dev is mostly a ghost town at this point, and deciding > that instead it would be the dedicated cross

  1   2   >