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-Infra] FW: about move of stackforge - compass-install

Will submit it soon. Thanks. Xicheng On Wed, Nov 4, 2015 at 12:34 PM, Anita Kuno wrote: > On 11/03/2015 11:25 PM, Xicheng Chang wrote: > >>> This patch will allow the project to be moved to the openstack/ > >>> > >> namespace as active projects are no longer in stackforge:

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

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

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,

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

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

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

[Openstack-operators] [Large Deployments Team] Summit Meeting Notes & Actions

Thanks to everyone who was able to attend the LDT session in Tokyo! I wanted to just briefly summarize some of the key points and action items. * Neutron segmented/routed networks * Encourage you to follow & provide feedback on the Neutron spec [1] * Cells v1 Patches * Many of the patches

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

[openstack-announce] [release][trove] python-troveclient release 1.4.0 (mitaka)

We are amped to announce the release of: python-troveclient 1.4.0: Client library for OpenStack DBaaS API This release is part of the mitaka release series. With source available at: http://git.openstack.org/cgit/openstack/python-troveclient With package available at:

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

Re: [OpenStack-Infra] FW: about move of stackforge - compass-install

On 11/03/2015 11:25 PM, Xicheng Chang wrote: >>> This patch will allow the project to be moved to the openstack/ >>> > >> namespace as active projects are no longer in stackforge: >>> > >> https://review.openstack.org/#/c/237753/ This patch is also linked >> here: >>> > >> >>> > >>

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 >

[Openstack-operators] [Large Deployments Team] [nova] Cells v1 attach/detach blueprint

I reached out to nova today to see what is the best way forward on this patch [1]. mriedem had created a blueprint skeleton for this already [2]. It sounds like it’s unlikely that nova would accept it, because it will require a new CI job [3] and it goes against the philosophy of not adding to

[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

Re: [Openstack-operators] OpenStack Tuning Guide

Great Kevin. Thanks for honchoing and sharing. On Wed, Nov 4, 2015 at 3:56 PM, Kevin Bringard (kevinbri) < kevin...@cisco.com> wrote: > Hey all! > > Something that jumped out at me in Tokyo was how much it seemed that > "basic" tuning stuff wasn't common knowledge. This was especially prevalent

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

[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

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

[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] [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,

Re: [OpenStack-Infra] FW: about move of stackforge - compass-install

Anita, New change to move compass-install from stackforge to openstack namespace was submitted: https://review.openstack.org/#/c/241788/ Weidong, Please +2 https://review.openstack.org/#/c/241734/ ASAP to unretire compass-install. Thanks, Xicheng On Wed, Nov 4, 2015 at 12:43 PM, Anita Kuno

Re: [OpenStack-Infra] Failed release jobs for networking-arista

On Wed, Nov 4, 2015 at 2:32 PM, Jeremy Stanley wrote: > On 2015-11-04 12:34:11 -0600 (-0600), Kyle Mestery wrote: > > Yesterday I tried to release version 2015.2.0 of networking-arista, > > Looks like it's okay now though, correct? At least I see it up on > PyPI fine. > > I

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

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

Re: [OpenStack-Infra] FW: about move of stackforge - compass-install

On 11/04/2015 03:42 PM, Xicheng Chang wrote: > Will submit it soon. Thanks. > Xicheng Thank you, Anita. > > On Wed, Nov 4, 2015 at 12:34 PM, Anita Kuno wrote: > >> On 11/03/2015 11:25 PM, Xicheng Chang wrote: > This patch will allow the project to be moved to the

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

[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

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

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

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

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,

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

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

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

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

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

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

Re: [Openstack-operators] [Large Deployments Team] Summit Meeting Notes & Actions

Sorry, wrong link for [3] below. On 11/4/15, 3:05 PM, "Mike Dorman" wrote: >Thanks to everyone who was able to attend the LDT session in Tokyo! I wanted >to just briefly summarize some of the key points and action items. > >* Neutron segmented/routed networks > *

[openstack-announce] [release][nova] python-novaclient release 2.34.0 (mitaka)

We are pumped to announce the release of: python-novaclient 2.34.0: Client library for OpenStack Compute API This release is part of the mitaka release series. With source available at: http://git.openstack.org/cgit/openstack/python-novaclient With package available at:

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

Re: [Openstack-operators] OpenStack Tuning Guide

Awesome start. Rabbit fd tweaks are the bane of every install...including some of my own... -Original Message- From: Kevin Bringard (kevinbri) [mailto:kevin...@cisco.com] Sent: Wednesday, November 04, 2015 3:56 PM To: OpenStack Operators Subject: [Openstack-operators] OpenStack Tuning

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

Re: [OpenStack-Infra] [Testing Puppet Modules] Issues with beaker and bundler gem versions

On Wed, Nov 4, 2015 at 3:01 AM, Colleen Murphy wrote: > On Tue, Nov 3, 2015 at 1:04 PM, Maite Balhester > wrote: > >> Hey folks, let me introduce myself first, I’m Maitê and I’m currently >> working on adding tests in the puppet modules with my

Re: [Openstack-operators] OpenStack Tuning Guide

Hi Kevin, Oops, noticed I didn't reply to all the first time. I think it's great to see more people who want to collect and distil knowledge like this. :) Finally, I hate diverging resources, so if something like this already > exists please speak up so we can focus our efforts on making sure

Re: [Openstack-operators] OpenStack Tuning Guide

Hello there, Very interesting initiative ! I'm currently working on the performance side too on our (french astrophysics cloud) OpenStack deployment but to say so currently I'm just following what CERN did regarding to Nova/CPU configuration. It's essentially around KSM, NUMA, CPU pinning,

Re: [Openstack-operators] OpenStack Tuning Guide

The official documentation would greatly benefit from more practical information such as tuning... most likely in the administration or operations guide, at least for now. Ideally, I would like to see a operators contribute documentation for complete production deployments that others can use as a

[Openstack] running multiple mistral instances behind a load balancer

All For the purposes of load-sharing and high availability, we are trying to run multiple mistrals behind a load balancer. We found out, quite by accident that if there are multiple mistral processes running on the same box, they end up duplicating actions. I suspect it's because they were

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

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

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

[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

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

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

[OpenStack-Infra] 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

[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

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

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

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

[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

[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

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

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

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

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

[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

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] [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"

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

[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

[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

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,

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*

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

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=...

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

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

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

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

[Openstack-operators] 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

[openstack-dev] [Fuel] Default PostgreSQL server encoding is 'ascii'

Hi, folks! Recently I've been working on this bug [1] and have found that default encoding of database server used by FUEL infrastructure components (Nailgun, OSTF, etc) is ascii. At least this is true for environment set up via VirtualBox scripts. This situation may (and already does returning

[openstack-dev] [Neutron][Infra] "gate-neutron-lbaasv1-dsvm-api" blocking patch merge

Hi, Jenkins blocking patch merge due to " gate-neutron-lbaasv1-dsvm-api " failures which is unrelated to patch-set changes . Patch: https://review.openstack.org/#/c/237896/ Please help to resolve this issue .

[openstack-dev] [murano] Visibility consistency for packages and images

Hi all, Ekaterina Chernova suggested last week to discuss the matter of visibility consistency for murano packages and glance images, following my bug report on that subject [1]. The general idea is to make sure that if a murano package is public, it should be really available for all projects,

Re: [openstack-dev] [devstack] Logging - filling up my tiny SSDs

On 11/02/2015 10:36 AM, Sean M. Collins wrote: > On Sun, Nov 01, 2015 at 10:12:10PM EST, Davanum Srinivas wrote: >> Sean, >> >> I typically switch off screen and am able to redirect logs to a specified >> directory. Does this help? >> >> USE_SCREEN=False >> LOGDIR=/opt/stack/logs/ > > It's not

Re: [openstack-dev] [neutron] [networking-powervm] Please createnetworking-powervm on PyPI

Hi Kyle, My team owns the networking-powervm project. When we moved from the StackForge to OpenStack namespace we changed the name from neutron-powervm to networking-powervm. There is no reason for the PyPI project to have a different name and we were planning to publish an update shortly

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

Regarding Jay's proposal, this would be tantamount to defining an API action for retrieving instances, something currently being discussed here [1]. The only comment I have is that I am not entirely surely whether using the POST verb for operations which do no alter at all the server

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

On 11/04/2015 09:00 AM, Jay Pipes wrote: > On 11/03/2015 05:20 PM, Boris Pavlovic wrote: >> Hi stackers, >> >> Usually such projects like Heat, Tempest, Rally, Scalar, and other tool >> that works with OpenStack are working with resources (e.g. VM, Volumes, >> Images, ..) in the next way: >> >>

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

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 projects like Heat, Tempest, Rally,

Re: [openstack-dev] [Neutron][Infra] "gate-neutron-lbaasv1-dsvm-api" blocking patch merge

> > On 04/11/15 12:48, Mohan Kumar wrote: > > Hi, > > > > Jenkins blocking patch merge due to " > > gate-neutron-lbaasv1-dsvm-api > > dsvm- > api/f631adf/>" > > > > > failures which is unrelated to patch-set changes . > > > >

  1   2   >