Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

On 11/02/15 17:19 +, Amrith Kumar wrote: [snip] Mostly, I'm very happy to see Flavio's email which ends with this: All the above being said, I'd like to thank everyone who fights for the openness of our community and encourage everyone to make that a must have thing in each sub-community

Re: [openstack-dev] [nova] Priority resizing instance on same host

Yes, CONF.allow_resize_to_same_host exist, but the meaning is that the current host have chance to be selected in nova-scheduler, the final chosen host maybe not the current host, in this case, the instance will be migrated from current host to chosen host and the image will be copied to the chosen

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

On 11/02/15 09:37 -0800, Clint Byrum wrote: Excerpts from Stefano Maffulli's message of 2015-02-11 06:14:39 -0800: On Wed, 2015-02-11 at 10:55 +0100, Flavio Percoco wrote: > This email is dedicated to the openness of our community/project. It's good to have a reminder every now and then. Thank

Re: [openstack-dev] [nova] Priority resizing instance on same host

Hi, There is a patch on resize https://review.openstack.org/#/c/117116/ To address the resize, there are some suggestions and please refer the review comments on this patch. Regards Kanagaraj M From: Jesse Pretorius [mailto:jesse.pretor...@gmail.com] Sent: Thursday, February 12, 2015 1:25 PM T

Re: [openstack-dev] [nova] Priority resizing instance on same host

@Manickam, thank you for the information :) +1 for the use case -1 for the approach in patch https://review.openstack.org/#/c/117116/ I think we should try to filter the current host and auto fallback to select a host in nova-scheduler if the current host is no suitable. 2015-02-12 16:17 GMT+08:

Re: [openstack-dev] [devstack] Compute-node-only installation fails

On Wed, 11 Feb 2015 17:27:19 + "Daniel P. Berrange" wrote: > On Wed, Feb 11, 2015 at 08:32:31AM -0800, Clark Boylan wrote: > > On Wed, Feb 11, 2015, at 08:18 AM, Alexander Schmidt wrote: > > > Hi Daniel, > > > > > > with your recent change[1] to error handling in stack.sh, compute > > > node

Re: [openstack-dev] [nova] Priority resizing instance on same host

Hi, Rui, I think resize VM to the same host if the host could pass scheduler filters makes sense to me. 2015-02-12 15:01 GMT+08:00 Rui Chen : > Hi: > > Currently, resizing instance cause migrating from the host that the > instance run on to other host, but maybe the current host is suitable f

Re: [openstack-dev] [nova] Priority resizing instance on same host

Yes, @Lingxian, I agree with you. Only the host pass the scheduler filters, the resizing can success, 'force_hosts' is not enough IMO. 2015-02-12 16:41 GMT+08:00 Lingxian Kong : > Hi, Rui, > > I think resize VM to the same host if the host could pass scheduler > filters makes sense to me. > > 20

Re: [openstack-dev] [glance] File-backed glance scrubber queue

On 11/02/15 13:42 -0800, Chris St. Pierre wrote: I recently proposed a change to glance to turn the file-backed scrubber queue files into JSON: https://review.openstack.org/#/c/145223/ As I looked into it more, though, it turns out that the file-backed queue is no longer usable; it was killed by

[openstack-dev] [nova] Question about force_host skip filters

Hi: If we boot instance with 'force_hosts', the force host will skip all filters, looks like that it's intentional logic, but I don't know the reason. I'm not sure that the skipping logic is apposite, I think we should remove the skipping logic, and the 'force_hosts' should work with the sc

Re: [openstack-dev] [congress] following up on releasing kilo milestone 2

sean roberts wrote: > so > git checkout master > git pull https://git.openstack.org/stackforge/congress.git > dbef982ea72822e0b7acc16da9b6ac89d3cf3530 > git tag -s 2015.1.0b2 > git push gerrit 2015.1.0b2 You could also try to use the milestone.sh release script I use: http://git.openstack.org/cg

Re: [openstack-dev] [congress] following up on releasing kilo milestone 2

Thierry Carrez wrote: > You could also try to use the milestone.sh release script I use: > > http://git.openstack.org/cgit/openstack-infra/release-tools/tree/ Hrm... I now realize the script is forcing openstack/* namespace and won't work as-is for stackforge projects. That repo is accepting pat

Re: [openstack-dev] [blazar] currectly status

Thanks for the info, I surely will let you know when I have doubts to dive deep into the code. Thanks -yuntong From: Nikolay Starodubtsev [mailto:nstarodubt...@mirantis.com] Sent: Wednesday, February 11, 2015 5:05 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [

Re: [openstack-dev] [nova] Question about force_host skip filters

Hi, I think that the filters should be applied to the list of hosts that are in 'force_hosts'. I am not sure if this is what you are suggesting. If this is not then case then it sounds like a bug. Thanks Gary From: Rui Chen mailto:chenrui.m...@gmail.com>> Reply-To: OpenStack List mailto:opensta

Re: [openstack-dev] [nova] Feature Freeze Exception Request (libvirt vhostuser vif driver)

On Mon, Feb 09, 2015 at 10:04:49AM +, Czesnowicz, Przemyslaw wrote: > Hi, > > I would like to request FFE for vhostuser vif driver. > > 2 reviews : > https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/libvirt-vif-vhost-user,n,z > > BP: https://bluepri

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

Flavio Percoco wrote: > On 11/02/15 17:19 +, Amrith Kumar wrote: >> Personally, I think the focus on password protected IRC channels is a >> distraction from the real issue that we need to ensure that the >> rapidly growing community is one where public discussion and decision >> making are sti

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

On Wed, Feb 11, 2015 at 1:55 AM, Flavio Percoco wrote: > [...] > > ## Keep discussions open > > I don't believe there's anything wrong about kicking off some > discussions in private channels about specs/bugs. I don't believe > there's anything wrong in having calls to speed up some discussions. >

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

Excerpts from Flavio Percoco's message of 2015-02-12 00:13:35 -0800: > On 11/02/15 09:37 -0800, Clint Byrum wrote: > >Excerpts from Stefano Maffulli's message of 2015-02-11 06:14:39 -0800: > >> On Wed, 2015-02-11 at 10:55 +0100, Flavio Percoco wrote: > >> > This email is dedicated to the openness o

Re: [openstack-dev] [nova] Question about force_host skip filters

Le 12/02/2015 10:05, Rui Chen a écrit : Hi: If we boot instance with 'force_hosts', the force host will skip all filters, looks like that it's intentional logic, but I don't know the reason. I'm not sure that the skipping logic is apposite, I think we should remove the skipping logic

Re: [openstack-dev] [QA] Question about EC2 Tempest tests

Joe, thank you for the note! Regards, Yaroslav Lobankov. On Thu, Feb 12, 2015 at 2:43 AM, Joe Gordon wrote: > > > On Wed, Feb 11, 2015 at 3:58 AM, Alexandre Levine < > alev...@cloudscaling.com> wrote: > >> Yaroslav, >> >> The bug: >> https://bugs.launchpad.net/nova/+bug/1410622 >> >> And the r

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

On 12/02/15 01:41 -0800, Nikhil Manchanda wrote: On Wed, Feb 11, 2015 at 1:55 AM, Flavio Percoco wrote: [...] ## Keep discussions open I don't believe there's anything wrong about kicking off some discussions in private channels about specs/bugs. I don't believe there's anything wrong in hav

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

> -Original Message- > From: Donald Stufft [mailto:don...@stufft.io] > Sent: Wednesday, February 11, 2015 4:34 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [all][tc] Lets keep our community open, lets > fight for it > > > > On Feb 11

Re: [openstack-dev] [all][oslo.db][nova] TL; DR Things everybody should know about Galera

- Original Message - > From: "Jay Pipes" > To: "Attila Fazekas" > Cc: "OpenStack Development Mailing List (not for usage questions)" > , "Pavel > Kholkin" > Sent: Wednesday, February 11, 2015 9:52:55 PM > Subject: Re: [openstack-dev] [all][oslo.db][nova] TL; DR Things everybody > s

Re: [openstack-dev] [devstack] [third-party] how to use a devstack external plugin in gate testing

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Following the conversation... We have seen that glusterfs[1] and ec2api[2] use different approach when it comes to repository managing: whereas glusterfs is a single 'devstack' directory repository, ec2api is a whole project with a 'devstack' direct

Re: [openstack-dev] [all][oslo.db][nova] TL; DR Things everybody should know about Galera

- Original Message - From: "Attila Fazekas" To: "Jay Pipes" Cc: "OpenStack Development Mailing List (not for usage questions)" , "Pavel Kholkin" Sent: Thursday, February 12, 2015 11:52:39 AM Subject: Re: [openstack-dev] [all][oslo.db][nova] TL; DR Things everybody should know about G

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

On 02/11/2015 06:20 PM, Clint Byrum wrote: > Excerpts from Nikola Đipanov's message of 2015-02-11 05:26:47 -0800: >> On 02/11/2015 02:13 PM, Sean Dague wrote: >>> >>> If core team members start dropping off external IRC where they are >>> communicating across corporate boundaries, then the local tr

[openstack-dev] [nova] Nova API meeting

Hi, Just a reminder that the weekly Nova API meeting is being held tomorrow Friday UTC . We encourage cloud operators and those who use the REST API such as SDK developers and others who and are interested in the future of the API to participate. In other timezones the meeting is at: EST 2

Re: [openstack-dev] [devstack] [third-party] how to use a devstack external plugin in gate testing

Jaume Devesa writes: > Following the conversation... > > We have seen that glusterfs[1] and ec2api[2] use different approach > when it comes to repository managing: whereas glusterfs is a single > 'devstack' directory repository, ec2api is a whole project with a > 'devstack' directory on it. > >

Re: [openstack-dev] [Fuel] Cache for packages on master node

On 02/10/2015 03:24 PM, Tomasz Napierala wrote: > Hi, > > We are currently redesigning our apporach to upstream distributions and > obviusly we will need some cache system for packages on master node. It > should work for deb and rpm packages, and be able to serve up to 200 nodes. > I know we ha

Re: [openstack-dev] [nova] Question about force_host skip filters

filters should be applied to the list of hosts that are in ‘force_hosts’. Yes, @Gray, it's my point. Operator can live-migrate a instance to a specified host and skip filters, it's apposite and important, I agree with you. But when we boot instance, we always want to launch a instance successf

[openstack-dev] [all] Ask for help with devstack error

Our CI failed when building devstack, the error is about “Unauthorized”. Following is the segment of the devstacklog: 2015-02-12 11:16:14.639 | + is_service_enabled c-api 2015-02-12 11:16:14.646 | + return 0 2015-02-12 11:16:14.646 | + is_service_enabled tls-proxy 2015-02-12 11:16:14.646 | + _ru

Re: [openstack-dev] [Fuel] Cache for packages on master node

> On 10 Feb 2015, at 23:02, Andrew Woodward wrote: > > previously we used squid in 3.0 and before. The main problem is that the > deployment would proceeded even if not all the packages where cached or even > available on the remote. This often lead to broken deployments that where > hard to

[openstack-dev] Feature Freeze Exception request for x509 keypairs

Hello. I would like to ask for a FFE for the x509 keypairs blueprint: https://blueprints.launchpad.net/nova/+spec/keypair-x509-certificates This blueprint is split up into 3 commits: [1] Database migration: previously merged, but had to be reverted because of a small issue. Everything is fixed

Re: [openstack-dev] [devstack] [third-party] how to use a devstack external plugin in gate testing

On 02/12/2015 06:10 AM, Jaume Devesa wrote: > Following the conversation... > > We have seen that glusterfs[1] and ec2api[2] use different approach > when it comes to repository managing: whereas glusterfs is a single > 'devstack' directory repository, ec2api is a whole project with a > 'devstack'

[openstack-dev] Feature Freeze Exception for hyper-v unit tests refactoring

Hello. I would like to request a FFE for the Hyper-V unit tests refactoring blueprint: https://blueprints.launchpad.net/nova/+spec/hyper-v-test-refactoring The point of the blueprint was to get rid of the ancient test_hypervapi.py tests, that use mox, as they prove more and more difficult to ma

Re: [openstack-dev] A question about strange behavior of oslo.config in eclipse

Hi Doug, Thank you very much for your reply. I don't have any codes, so no any special codes as well. Only thing I did is that: 1, use devstack to install a fresh openstack env, all are ok. 2, import neutron-vpnaas directory (no any my own codes) into eclipse as pydev project, for exam

[openstack-dev] [nova] Feature Freeze Exception request for x509 keypairs

Hello. I would like to ask for a FFE for the x509 keypairs blueprint: https://blueprints.launchpad.net/nova/+spec/keypair-x509-certificates This blueprint is split up into 3 commits: [1] Database migration: previously merged, but had to be reverted because of a small issue. Everything is fixe

[openstack-dev] [nova] Feature Freeze Exception for hyper-v unit tests refactoring

Hello. I would like to request a FFE for the Hyper-V unit tests refactoring blueprint: https://blueprints.launchpad.net/nova/+spec/hyper-v-test-refactoring The point of the blueprint was to get rid of the ancient test_hypervapi.py tests, that use mox, as they prove more and more difficult to m

[openstack-dev] [stable] expanding sahara maint team

Hi stable maint folks, I'd like to propose to add the following folks to the sahara stable maint team: * Trevor McKay (tmckay) * Ethan Gafford (egafford) * Andrew Lazarev (alazarev) * Sergey Reshetnyak (sreshetniak) Thanks. -- Sincerely yours, Sergey Lukjanov Sahara Technical Lead (OpenStack D

Re: [openstack-dev] Feature Freeze Exception for hyper-v unit tests refactoring

On Thu, Feb 12, 2015 at 12:18:49PM +, Claudiu Belu wrote: > Hello. > > I would like to request a FFE for the Hyper-V unit tests refactoring > blueprint: > https://blueprints.launchpad.net/nova/+spec/hyper-v-test-refactoring > > The point of the blueprint was to get rid of the ancient test_h

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

On Thu, 12 Feb 2015, Flavio Percoco wrote: The important bit, thoguh, is that email is meant for asynchronous communication and IRC isn't. If things that require the intervention of other folks from the community are being discussed and those folks are not on IRC, it'd be wrong to consider the t

Re: [openstack-dev] Feature Freeze Exception for hyper-v unit tests refactoring

On 02/12/2015 07:28 AM, Daniel P. Berrange wrote: > On Thu, Feb 12, 2015 at 12:18:49PM +, Claudiu Belu wrote: >> Hello. >> >> I would like to request a FFE for the Hyper-V unit tests refactoring >> blueprint: >> https://blueprints.launchpad.net/nova/+spec/hyper-v-test-refactoring >> >> The po

Re: [openstack-dev] [nova] Question about force_host skip filters

I understand the fact that an opertaor can and should be able to place the VM where she/he wants. The VM should just adhere to the scheduling constraints :) (which are defined in the filters) :) From: Rui Chen mailto:chenrui.m...@gmail.com>> Reply-To: OpenStack List mailto:openstack-dev@lists.o

Re: [openstack-dev] [devstack] [third-party] how to use a devstack external plugin in gate testing

On 2/12/15, 1:33 PM, "Chmouel Boudjnah" wrote: >Jaume Devesa writes: > >> Following the conversation... >> >> We have seen that glusterfs[1] and ec2api[2] use different approach >> when it comes to repository managing: whereas glusterfs is a single >> 'devstack' directory repository, ec2api is

Re: [openstack-dev] [devstack] [third-party] how to use a devstack external plugin in gate testing

On 02/12/2015 07:49 AM, Gary Kotton wrote: > > > On 2/12/15, 1:33 PM, "Chmouel Boudjnah" wrote: > >> Jaume Devesa writes: >> >>> Following the conversation... >>> >>> We have seen that glusterfs[1] and ec2api[2] use different approach >>> when it comes to repository managing: whereas glusterfs

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

On Thu, 2015-02-12 at 10:35 +, Kuvaja, Erno wrote: > I'm not attacking against having summits, I think the face to face > time is incredibly valuable for all kind of things. My point was to > bring up general flaw of the flow between all inclusive decision > making vs. decided in summit session

Re: [openstack-dev] [devstack] [third-party] how to use a devstack external plugin in gate testing

Sean Dague writes: > I'm going to be -1ing most new or substantially redone drivers at this > point. External plugins are a better model for those. +1 Chnmouel __ OpenStack Development Mailing List (not for usage questions

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

On Thu, 2015-02-12 at 10:37 +0100, Thierry Carrez wrote: > Right. You can't prevent occasional private discussions and pings, and > you shouldn't. It's when you encourage and officialize them (by for > example creating a channel for them) that things start to go bad. Yes, that's very bad. Private

Re: [openstack-dev] [nova] Feature Freeze Exception for "Add config drive support for PCS containers"

On Wed, Feb 11, 2015 at 03:28:49PM +0300, aburluka wrote: > Hello, > > I'd like to request a feature freeze exception for the change [1] > This change implements configuration drive support in Parallels containers. > It does not change existing Nova behaviour. > It's a last patch in parallels seri

[openstack-dev] [Neutron] Update on "DB" IPAM driver

Hi, I have updated the patch; albeit not complete yet it's kind of closer to be an allocator decent enough to replace the built-in logic. I will be unable to attend today's L3/IPAM meeting due to a conflict, so here are some highlights from me on which your feedback is more than welcome: - I agr

[openstack-dev] [sahara] Running HBase Jobs (was: About Sahara Oozie plan)

Hi Lu, folks, I've been investigating how to run Java actions in Sahara EDP that depend on HBase libraries (see snippet from the original question by Lu below). In a nutshell, we need to use Oozie sharelibs for this. I am working on a spec now, thinking about the best way to support this in Sah

[openstack-dev] [Designate] Documentation Sprint tomorrow @ 16.00 UTC

Hey Designate is having a 2 hour docs sprint this Friday @ 16.00 UTC List of topics is here - https://etherpad.openstack.org/p/designate-documentation-sprint If you are interested in helping out, please add your name to an unclaimed topic :) We will be co-ordinating via IRC in #openstack-dns T

[openstack-dev] [devstack] Devstack and Grenade futures

In the spirit of summarizing conversations that have been had, I'd like to point people that are interested at the Devstack FUTURE.rst document - https://github.com/openstack-dev/devstack/blob/master/FUTURE.rst This is an attempt by the Devstack team recently to write down a "where are we going" d

Re: [openstack-dev] [sahara] team meeting Feb 12 1400 UTC

Log: http://eavesdrop.openstack.org/meetings/sahara/2015/sahara.2015-02-12-14.00.txt Minutes: http://eavesdrop.openstack.org/meetings/sahara/2015/sahara.2015-02-12-14.00.html On Thu, Feb 12, 2015 at 1:26 AM, Andrew Lazarev wrote: > Hi guys, > > We'll be having the Sahara team meeting tomorrow at

Re: [openstack-dev] [api] Missing the next API WG meeting

I’ll be around so I’ll do this if no one else will be around to do it. On 2/11/15, 16:39, "Everett Toews" wrote: >I’ll be missing the next API WG meeting [1] as I’m in some all day >training. Someone else will have to #startmeeting api wg > >Cheers, >Everett > >[1] https://wiki.openstack.org/wik

Re: [openstack-dev] [glance] Metadef-tags create api change request.

On 2/11/15, 11:10, "Okuma, Wayne" wrote: >Hello, > >I would like to change the metadef-tags create API which was checked into >Kilo (cycle 1). >The python-glanceclient that would support metadef-tags has not been >released yet and I would like to make this change before doing so. >The details ar

Re: [openstack-dev] [nova] Question about force_host skip filters

On 02/12/2015 03:44 AM, Sylvain Bauza wrote: Any action done by the operator is always more important than what the Scheduler could decide. So, in an emergency situation, the operator wants to force a migration to an host, we need to accept it and do it, even if it doesn't match what the Schedul

Re: [openstack-dev] [nova] Question about force_host skip filters

On 02/12/2015 10:10 AM, Chris Friesen wrote: On 02/12/2015 03:44 AM, Sylvain Bauza wrote: Any action done by the operator is always more important than what the Scheduler could decide. So, in an emergency situation, the operator wants to force a migration to an host, we need to accept it and do

Re: [openstack-dev] The API WG mission statement

On 02/10/2015 08:01 AM, Everett Toews wrote: > On Feb 9, 2015, at 9:28 PM, Jay Pipes > wrote: > >> On 02/02/2015 02:51 PM, Stefano Maffulli wrote: >>> On Fri, 2015-01-30 at 23:05 +, Everett Toews wrote: To converge the OpenStack APIs to a consistent and pragmat

Re: [openstack-dev] [all] Ask for help with devstack error

Hi, Take a look at this commit, it broke a number of Trove tests last night: https://review.openstack.org/#/c/154391 Not sure if it’s related, but it seems similar (try manually backing out the change for cinder and see if it fixes your problem). Good luck! Peter From: liuxinguo [mailto:liuxi

Re: [openstack-dev] [Heat][API] Filtering by metadata values

On 02/10/2015 10:03 PM, Angus Salkeld wrote: > On Wed, Feb 11, 2015 at 8:20 AM, Miguel Grinberg > mailto:miguel.grinb...@gmail.com>> wrote: > > Hi, > > We had a discussion yesterday on the Heat channel regarding patterns > for searching or filtering entities by its metadata values. Th

[openstack-dev] [Murano] Environment status

Initiall my interest to that problem was caused by the bug [1] due to whose once environment was deployed with failure it stays forever with that status even if it have been deployed sucessfully later. For now status determination happens in three stages: - If at least one of all sessions of env,

[openstack-dev] [Designate] Core reviewer update

Hello Designate folks, Betsy Luzader (betsy) resigned from her core reviewer position on Designate. In order to keep the momentum of reviews in Designate going, I'd like to propose adding Tim Simmons (timsim) to designate-core. For context on Designate reviews and who has been active, please se

Re: [openstack-dev] [keystone] [nova]

A trust token cannot be used to get another token: https://github.com/openstack/keystone/blob/master/keystone/token/controllers.py#L154-L156 You have to make your Nova client use the very same trust scoped token obtained from authentication using trust without trying to authenticate with it one mor

Re: [openstack-dev] [glance] Metadef-tags create api change request.

On 2/12/15, 9:57 AM, "Ian Cordasco" wrote: >On 2/11/15, 11:10, "Okuma, Wayne" wrote: > >>Hello, >> >>I would like to change the metadef-tags create API which was checked into >>Kilo (cycle 1). >>The python-glanceclient that would support metadef-tags has not been >>released yet and I would like

Re: [openstack-dev] [Designate] Core reviewer update

+1 - Tim has been giving good reviews over the last few months and will make a good addition.. Thanks, Kiall On 12/02/15 15:40, Vinod Mangalpally wrote: > Hello Designate folks, > > Betsy Luzader (betsy) resigned from her core reviewer position on > Designate. In order to keep the momentum of re

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

On 2015-02-12 10:35:18 + (+), Kuvaja, Erno wrote: [...] > I'd like to point out that that this discussion has been pushing > all inclusive open approach. Not ATC, not specially approved > individuals, but everyone. Mailing list can easily facilitate > participation of everyone who wishes to

Re: [openstack-dev] [Designate] Core reviewer update

On 12/02/15 15:50, Kiall Mac Innes wrote: > +1 - Tim has been giving good reviews over the last few months and will > make a good addition.. > > Thanks, > Kiall > > On 12/02/15 15:40, Vinod Mangalpally wrote: >> Hello Designate folks, >> >> Betsy Luzader (betsy) resigned from her core reviewer po

Re: [openstack-dev] [Murano] [API WG] Environment status

I think this is a good case for API WG as statuses of entities should be consistent among OpenStack APIs. As I recall, we are mixing two different statuses for environments. The first dimension for environment status is its content status: NEW, CONFIGURING, READY The second dimension is deployment

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

Flavio, Thanks for your email. I've read your response as well as those from all the others who responded and one thing is very unclear to me in the position being advanced. You write, and other respondents appear to share the following sentiment: | I personally don't care if you have private

[openstack-dev] [vmware-api] Weekly meeting

Hi, Over the last few IRC meetings we have discussed the following: 1. Providing a platform for people other than those working on the Nova driver to take part. There are efforts with the Glance, Cinder, Ceilometer and Neutron projects. Hopefully people working on those can also take part and

Re: [openstack-dev] [Designate] Core reviewer update

On 02/12/2015 08:51 AM, Hayes, Graham wrote: On 12/02/15 15:50, Kiall Mac Innes wrote: +1 - Tim has been giving good reviews over the last few months and will make a good addition.. Thanks, Kiall On 12/02/15 15:40, Vinod Mangalpally wrote: Hello Designate folks, Betsy Luzader (betsy) resigne

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

>> I think there's a place for >> private conversation (eg. discussing a security issue that corresponds >> to a CVE... > CVE's are a special exception and I'd even argue on the need of > private conversations there. Discussing CVEs in private came up few times but I'm not sure IRC is secure enou

[openstack-dev] [Fuel][Plugins] Versioning, branching, tagging

Hello! I would like to discuss which policy we want to recommend for the versioning, branching and tagging for FUEL plugins and how it should correlate with FUEL/MOS versions/releases. According Fuel Plug-in Guide

Re: [openstack-dev] [Designate] Core reviewer update

Changes have been applied, welcome Tim :) On 12/02/15 16:18, Rich Megginson wrote: > On 02/12/2015 08:51 AM, Hayes, Graham wrote: >> On 12/02/15 15:50, Kiall Mac Innes wrote: >>> +1 - Tim has been giving good reviews over the last few months and will >>> make a good addition.. >>> >>> Thanks, >>>

[openstack-dev] SDN Security in OpenStack

Hi all, I am a software developer working at HP, I do not work with OpenStack @HP though, only worked with it privately. I am finishing up a Masters and for my dissertation research I am focusing on SDN Security. I wanted to align my research to current SDN uses in the industry and was interest

Re: [openstack-dev] [Designate] Core reviewer update

Thanks all, I’m honored :) —Tim On Feb 12, 2015, at 10:31 AM, Kiall Mac Innes mailto:ki...@macinnes.ie>> wrote: Changes have been applied, welcome Tim :) On 12/02/15 16:18, Rich Megginson wrote: On 02/12/2015 08:51 AM, Hayes, Graham wrote: On 12/02/15 15:50, Kiall Mac Innes wrote: +1 - Tim has

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

On 2015-02-12 17:20:37 +0100 (+0100), Alan Pevec wrote: > Discussing CVEs in private came up few times but I'm not sure IRC > is secure enough for that. IMHO discussion about embargoed issues > must be kept in private Launchpad bugs but I'd like to hear from > VMT team. I do from time to time /msg

Re: [openstack-dev] [Murano] [API WG] Environment status

On 02/12/2015 10:52 AM, Georgy Okrokvertskhov wrote: > I think this is a good case for API WG as statuses of entities should be > consistent among OpenStack APIs. As I recall, we are mixing two > different statuses for environments. The first dimension for environment > status is its content status

Re: [openstack-dev] [Openstack-operators] [Ceilometer] Real world experience with Ceilometer deployments - Feedback requested

Hi Mash, we dropped Ceilometer as the core tool to gather metrics for our rating and billing system. I must admit it has improved, but I think it's broken by design: a metering and monitoring system is not the same thing. We have built a component that directly listens from rabbit notification to

[openstack-dev] [nova] issues with fakelibvirt in tests

Looking recently at the following failure - http://logs.openstack.org/04/154804/1/gate/gate-nova-python27/1fe94bf/console.html#_2015-02-12_15_02_19_593 It appears that the fakelibvirt fixture is potentially causing races in tests because after the first test in a worker starts a libvirt connection

Re: [openstack-dev] [glance] File-backed glance scrubber queue

Yeah, that commit definitely disables the file-backed queue -- it certainly *looks* like we want to be rid of it, but all of the code is left in place and even updated to support the new format. So my confusion remains. Hopefully Zhi Yan can clarify. Link added. Thanks. On Thu, Feb 12, 2015 at 12

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

On 12/02/15 16:01 +, Amrith Kumar wrote: Flavio, Thanks for your email. I've read your response as well as those from all the others who responded and one thing is very unclear to me in the position being advanced. You write, and other respondents appear to share the following sentiment:

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

On 11/02/15 11:24 +, Chris Dent wrote: On Wed, 11 Feb 2015, Flavio Percoco wrote: During the last two cycles, I've had the feeling that some of the things I love the most about this community are degrading and moving to a state that I personally disagree with. With the hope of seeing these

[openstack-dev] [defcore] Proposal for new openstack/defcore repository

In the most recent Defcore committee meeting we discussed the need for a repository to host artifacts related to the Defcore process[1]. These artifacts will include documentation of the Defcore process, lists of advisory and required capabilities for releases, and useful tools and instructions

Re: [openstack-dev] [nova] issues with fakelibvirt in tests

On 2/12/2015 11:32 AM, Sean Dague wrote: Looking recently at the following failure - http://logs.openstack.org/04/154804/1/gate/gate-nova-python27/1fe94bf/console.html#_2015-02-12_15_02_19_593 It appears that the fakelibvirt fixture is potentially causing races in tests because after the first

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

On 12/02/15 12:04 +, Chris Dent wrote: On Thu, 12 Feb 2015, Flavio Percoco wrote: The important bit, thoguh, is that email is meant for asynchronous communication and IRC isn't. If things that require the intervention of other folks from the community are being discussed and those folks are

Re: [openstack-dev] [defcore] Proposal for new openstack/defcore repository

On 02/12/2015 12:47 PM, Chris Hoge wrote: > In the most recent Defcore committee meeting we discussed the need > for a repository to host artifacts related to the Defcore process[1]. > These artifacts will include documentation of the Defcore process, > lists of advisory and required capabilities f

[openstack-dev] [API] Do we need to specify "follow the HTTP RFCs"?

I meant to get to this in today's meeting[1] but we ran out of time and based on the rest of the conversation it was likely to lead to a spiral of different interpretations, so I thought I'd put it up here. $SUBJECT says it all: When writing guidelines to what extent do we think we should be rec

Re: [openstack-dev] [Openstack-operators] [Ceilometer] Real world experience with Ceilometer deployments - Feedback requested

Hi, My experience with Ceilometer is that MongoDB is/was a major bottleneck. You need sharding + servers with lot of RAM. You need to set TTL on your samples, and only save in DB the metrics that really mater to you. MongoDB v3 should also help. Regarding RabbitMQ pressure, I think this blueprint

Re: [openstack-dev] [Congress][Delegation] Google doc for working notes

Hi Debo and Yathiraj, I took a third look at the solver-scheduler docs and code with your comments in mind. A few things jumped out. 1) Choice of LP solver. I see solver-scheduler uses Pulp, which was on the Congress short list as well. So we’re highly aligned on the choice of underlying so

Re: [openstack-dev] [API] Do we need to specify "follow the HTTP RFCs"?

On 02/12/2015 01:01 PM, Chris Dent wrote: I meant to get to this in today's meeting[1] but we ran out of time and based on the rest of the conversation it was likely to lead to a spiral of different interpretations, so I thought I'd put it up here. $SUBJECT says it all: When writing guidelines t

Re: [openstack-dev] [all][tc] Lets keep our community open, lets fight for it

On 2015-02-12 18:34:56 +0100 (+0100), Flavio Percoco wrote: [...] > we *don't* have a public voip channel [...] Well, technically we do if you want one. https://wiki.openstack.org/wiki/Infrastructure/Conferencing But of course the logistics around all the project connecting in and talking at onc

Re: [openstack-dev] [nova] issues with fakelibvirt in tests

On Thu, Feb 12, 2015 at 12:32:10PM -0500, Sean Dague wrote: > Looking recently at the following failure - > http://logs.openstack.org/04/154804/1/gate/gate-nova-python27/1fe94bf/console.html#_2015-02-12_15_02_19_593 > > It appears that the fakelibvirt fixture is potentially causing races in > test

Re: [openstack-dev] [nova] issues with fakelibvirt in tests

On Thu, Feb 12, 2015 at 11:49:12AM -0600, Matt Riedemann wrote: > > > On 2/12/2015 11:32 AM, Sean Dague wrote: > >Looking recently at the following failure - > >http://logs.openstack.org/04/154804/1/gate/gate-nova-python27/1fe94bf/console.html#_2015-02-12_15_02_19_593 > > > >It appears that the f

Re: [openstack-dev] [nova] issues with fakelibvirt in tests

On 02/12/2015 01:09 PM, Daniel P. Berrange wrote: > On Thu, Feb 12, 2015 at 12:32:10PM -0500, Sean Dague wrote: >> Looking recently at the following failure - >> http://logs.openstack.org/04/154804/1/gate/gate-nova-python27/1fe94bf/console.html#_2015-02-12_15_02_19_593 >> >> It appears that the fak

[openstack-dev] [nova] FFE Request: Proxy neutron configuration to guest instance

Hi Nova cores, We’d like to request an FFE for this added nova feature. It gives a real interface - a JSON file - to network data inside the instance. This is a patch Rackspace carries downstream, and we’ve had lots of interested users, including the OpenStack Infra team and upstream cloud-init

Re: [openstack-dev] [nova] issues with fakelibvirt in tests

On Thu, Feb 12, 2015 at 01:17:55PM -0500, Sean Dague wrote: > On 02/12/2015 01:09 PM, Daniel P. Berrange wrote: > > On Thu, Feb 12, 2015 at 12:32:10PM -0500, Sean Dague wrote: > >> Looking recently at the following failure - > >> http://logs.openstack.org/04/154804/1/gate/gate-nova-python27/1fe94bf

[openstack-dev] [oslo.messaging] notification listener; same target with multiple executors

Is it possible to have multiple oslo messaging notification listeners using different executors on the same target? For example, I was to create multiple notification listeners [1] each using a different executor for the same set of targets (e.g. glance/notifications). When I try this [2], only

Re: [openstack-dev] [Neutron] Update on "DB" IPAM driver

From: Salvatore Orlando mailto:sorla...@nicira.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Thursday, February 12, 2015 at 8:36 AM To: OpenStack Development Mailing List mailto:openstack-dev@lists.openstack.org>>

  1   2   >