Re: [openstack-dev] Custom Nova scheduler based on CPU queue length

Excerpts from Rahul Nair's message of 2015-10-20 18:53:09 -0700: > ​Hi All, > > I am fairly new to the OpenStack community and is trying to create a custom > scheduler for Nova. A scheduler based on CPU queue length. Kindly apologize > if there are any inaccuracies in my statements. > > As I unde

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

Link: https://openstack.nimeyo.com/62868/?show=62868#q62868 From: marif82 Hi Asha, I am also getting the same error when I am executing the curl command to create secret. bash-4.2$ curl -X POST -H 'content-type:application/json' -H 'X-Project-Id:12345' -d '{"payload": "my-secret-here","payloa

Re: [openstack-dev] [Neutron] HenryG addition to the Neutron Drivers team

Congratulations Henry! On Wed, Oct 21, 2015 at 8:49 AM, Kevin Benton wrote: > Excellent addition! Remember everyone, if the feature you want doesn't > make it into Neutron, it's now Henry's fault. :) > > On Tue, Oct 20, 2015 at 8:14 PM, Armando M. wrote: > >> Hi folks, >> >> Henry has been inst

Re: [openstack-dev] [Heat] core team nomination

Rabi, Peter, my congradulations. You were elected by a unanimous vote :) I will add you to heat-core group. Enjoy and stay on this course ! :) On 21 October 2015 at 09:45, Qiming Teng wrote: > +1 to both. > > Qiming > > On Tue, Oct 20, 2015 at 04:38:12PM +0300, Sergey Kraynev wrote: >> I'd like t

[openstack-dev] [Magnum] Mitaka Design Summit Sessions in Tokyo

Magnum Team, For those of you attending the Mitaka Design Summit in Tokyo next week, here are the sessions that I respectfully request you attend: 2015-10-28, 11:15-11:55 http://sched.co/4Qck Heat Template Refactoring 2015-10-28, 12:05-12:45 http://sched.co/4Qdc Magnum Scalability (Work Session)

Re: [openstack-dev] [Heat] core team nomination

Congrats Rabi and Peter :) -Original Message- From: Sergey Kraynev [mailto:[email protected]] Sent: Wednesday, October 21, 2015 12:57 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Heat] core team nomination Rabi, Peter, my congradul

[openstack-dev] [Glance] Spec review sprint in Tokyo

Greetings, The drivers team will have a Spec Rewview sprint next friday at the Glance meetup in Tokyo (Friday Oct 30th). This email is a heads up for all spec authors[0] to address pending comments so that we can work on your specs and speed up the process. [0] https://review.openstack.org/#/q

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

Hi, Please help to take a look at this problem. I was trying to raise it in the spec discussion. But since we don't need a spec on this problem, so I want to discuss it here. It is about what the new state machine will be. http://paste.openstack.org/show/476954/ Thanks. _

Re: [openstack-dev] [infra][all] Reviews with a prio label?

Zaro wrote on 10/20/2015 07:49:13 PM: > From: Zaro > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 10/20/2015 07:54 PM > Subject: Re: [openstack-dev] [infra][all] Reviews with a prio label? > > Upstream Gerrit has been working on a tagging feature for a while no

Re: [openstack-dev] [release] establishing release liaisons for mitaka

Hi, Doug, After conversition with Mistral PTL(Renat), I'm willing to be mistral liaison to take participate in cross-project release effort on beharf of mistral team, so please count me in. On Wed, Oct 14, 2015 at 11:25 PM, Doug Hellmann wrote: > As with the other cross-project teams, the releas

Re: [openstack-dev] [Fuel] Assigning VIPs on network config serialization

Then we should close [1] as invalid, shoudn’t we? > 20 жовт. 2015 р. о 15:55 Igor Kalnitsky написав(ла): > > Roman, > >> This behavior is actually described in [1]. Should we allocate >> VIPs on network check as well? > > No, we shouldn't. We should check whether it's enough IPs for nodes / >

Re: [openstack-dev] [release] establishing release liaisons for mitaka

> On 21 Oct 2015, at 14:42, Lingxian Kong wrote: > > Hi, Doug, > > After conversition with Mistral PTL(Renat), I'm willing to be mistral > liaison to take participate in cross-project release effort on beharf > of mistral team, so please count me in. Yes, I confirm. Renat Akhmerov @ Mirantis

Re: [openstack-dev] [Fuel][Plugins] Plugin deployment questions

Hey Mike, AFAIK, there's no bug/blueprint on LP. The question I want to raise here is what will happen if I decide to deploy a cluster with one compute without controllers? It looks like a bad UX to me, though it may increase speed of CI gates where one node with one role is enough. Can we ignor

Re: [openstack-dev] [Neutron] HenryG addition to the Neutron Drivers team

> On 21 Oct 2015, at 05:14, Armando M. wrote: > > Hi folks, > > Henry has been instrumental in many areas of the projects and his crazy > working hours makes even Kevin and I bow in awe. > > Jokes aside, I would like to announce HenryG as a new member of the Neutron > Drivers team. > > Havi

Re: [openstack-dev] [infra] Upgrade to Gerrit 2.11

On Tue, Oct 13, 2015 at 05:08:29PM -0700, Zaro wrote: > Hello All, > > The openstack-infra team would like to upgrade from our Gerrit 2.8 to > Gerrit 2.11. We are proposing to do the upgrade shortly after the > Mitaka summit. The main motivation behind the upgrade is to allow us > to take advant

Re: [openstack-dev] [Fuel][Plugins] Plugin deployment questions

Hi, Can we ignore the problem above and remove this limitation? Or should > we improve it somehow so it would work for one nodes, and will be > ignored for others? > I think that this validation needs to be accomplished in a different way, we don't need 1 controller for the sake of 1 controller, 1

Re: [openstack-dev] [mistral] How to call 3rd-party tools(such as Ansible) in Mistral

Renat, Thanks for your valuable suggestions! Tony From: Renat Akhmerov [mailto:[email protected]] Sent: Wednesday, October 21, 2015 2:35 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [mistral] How to call 3rd-party tools(such as Ansible) i

Re: [openstack-dev] [Fuel][Plugins] Plugin deployment questions

Hi Dmitry, > Insert required metadata into roles that relies on another roles, for > compute it will be something like: > > compute: > requires: controller > 1 Yeah, that's actually what I was thinking about when I wrote: > Or should we improve it somehow so it would work for one nod

Re: [openstack-dev] [Fuel][Plugins] Plugin deployment questions

But it will lead to situations, when certain plugins, like standalone_rabbitmq/standalone_mysql will need to overwrite settings on *all* dependent roles, and it might be a problem.. Because, how plugin developer will be able to know what are those roles? On Wed, Oct 21, 2015 at 1:01 PM, Igor Kalni

Re: [openstack-dev] [Fuel][Plugins] Plugin deployment questions

We can make bidirectional dependencies, just like our deployment tasks do. And, btw, standalone-* roles may have a restriction that at least one node is required. I think it's ok for the plugin is case, since if you don't want to use it - just disable it. On Wed, Oct 21, 2015 at 1:15 PM, Dmitriy

Re: [openstack-dev] [Neutron] HenryG addition to the Neutron Drivers team

Congratulations Henry! On Wed, Oct 21, 2015 at 5:03 AM Ihar Hrachyshka wrote: > > > On 21 Oct 2015, at 05:14, Armando M. wrote: > > > > Hi folks, > > > > Henry has been instrumental in many areas of the projects and his crazy > working hours makes even Kevin and I bow in awe. > > > > Jokes asi

[openstack-dev] [ANNOUNCE] [HA] [Pacemaker] new, maintained openstack-resource-agents repository

[cross-posting to openstack-dev and pacemaker user lists; please consider trimming the recipients list if your reply is not relevant to both communities] Hi all, Back in June I proposed moving the well-used but no longer maintained https://github.com/madkiss/openstack-resource-agents/ repository

[openstack-dev] [Manila] Share allow/deny by shared secret

Hi, (I wanted to put this in an email ahead of Tokyo, where I hope we'll find time to discuss it. This is a follow up to http://osdir.com/ml/openstack-dev/2015-10/msg00381.html) With the current code, there doesn't appear to be a proper way to expose Ceph's native authentication system via Manil

Re: [openstack-dev] [Fuel][Plugins] Plugin deployment questions

On 21 Oct 2015 at 12:21:57, Igor Kalnitsky ([email protected]) wrote: We can make bidirectional dependencies, just like our deployment tasks do. Just to make sure we are on the same page… We don’t want to be in a situation where a role needs to know about the its reverse dependencies. De

Re: [openstack-dev] Custom Nova scheduler based on CPU queue length

Hi Rahul, > As I understand a weigher for the filter scheduler that weighs filtered host > machines based on the host weight option, 'cpu.percent' can be > configured to prioritize the hosts based on CPU percentage, but there are > only limited options when it comes to filtering of machines in t

Re: [openstack-dev] [Neutron] Gerrit permissions and Merge rights

Do we also want to consider Project Kuryr part of this? We already started sending Kuryr spec to the Neutron repository and I think it would make sense to manage it as part of Neutron spec process. Any opinions on that? Gal. On Tue, Oct 20, 2015 at 11:10 PM, Armando M. wrote: > Hi folks, > > D

[openstack-dev] [release][stable][ironic] ironic-inspector release 2.2.2 (liberty)

We are gleeful to announce the release of: ironic-inspector 2.2.2: Hardware introspection for OpenStack Bare Metal With source available at: http://git.openstack.org/cgit/openstack/ironic-inspector The most important change is a fix for CVE-2015-5306, all users (including users of ironic-

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

Hi Arif-- Are you using Keystone for authentication? If so, you need to get an authentication token from Keystone and add it as a header to your curl command: -H "X-Auth-Token:$TOKEN". You do not need to specify the project ID (-H 'X-Project-Id:12345'). The project ID will be based o

[openstack-dev] [magnum] k8s api tls_enabled mode testing

Hello, I need your help on k8s api tls_enabled mode. Here’s my patch https://review.openstack.org/232421 It is always failed on gate, but it works in my setup. Debug more I found that the ca cert return api return length with difference: On my setup： 10.238.157.49 - - [21/Oct/2015 19:16:17] "POST

Re: [openstack-dev] [Fuel][Plugins] Plugin deployment questions

On Wed, Oct 21, 2015 at 1:21 PM, Igor Kalnitsky wrote: > We can make bidirectional dependencies, just like our deployment tasks do. I'm not sure that we are on the same page regarding problem definition. Imagine the case when we have environment with next set of roles: 1. standalone-rabbitmq 2

[openstack-dev] [Fuel] shotgun code freeze

Dear colleagues, As you might know I'm working on splitting multiproject fuel-web repository into several sub-projects. Shotgun is one of directories that are to be moved to a separate git project. Checklist for this to happen is as follows: - Launchpad bug https://bugs.launchpad.net/fuel/+bu

Re: [openstack-dev] [neutron] Neutron rolling upgrade - are we there yet?

Hi folks, I see there is significant interest in neutron upgrade strategy. I suggest we meet on summit on Fri during ‘unplugged’ track in a small group and come up with a plan for Mitaka and beyond. I start to think that the work we can expect is quite enormous, and some coordination is due. Ma

[openstack-dev] [tc] [watcher] New project: Watcher

We are pleased to introduce Watcher, a new project in the OpenStack ecosystem. We believe that a "resource optimization" service in an OpenStack-based cloud is a crucial component that has been missing to date and we have started working towards filling that gap. OpenStack Watcher provides a fl

[openstack-dev] [Ceilometer] Meeting cancelled for this week

Hi All, I would like to inform you that we cancel the Ceilometer meeting for this week in favor of Summit travels and preparation. We finished to organize our sessions for next week, you can find the schedule here: https://mitakadesignsummit.sched.org/overview/type/ceilometer The etherpads for

[openstack-dev] [nova] Change from Mitaka: Expected UNIX signal to generate Guru Meditation (error) Reports

Background -- Oslo Guru Meditation (error) Reports (GMR)[*] are a useful debugging mechanism that allows one to capture the current state of a Nova process/executable (e.g. `nova-compute`, `nova-api`, etc). The way to generate the error report is to supply the 'User-defined signal', SIGUS

Re: [openstack-dev] [Fuel] Assigning VIPs on network config serialization

> Then we should close [1] as invalid, shoudn’t we? AFAIC, no. We should check whether there is enough IPs for nodes / VIPs with current network configuration. I'd propose to add a handler for allocation of VIPs if VIPs can be useful before deployment. I'm not sure what are the cases. Aleksey

Re: [openstack-dev] [infra] Upgrade to Gerrit 2.11

"Daniel P. Berrange" wrote on 10/21/2015 11:29:50 AM: > From: "Daniel P. Berrange" > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 10/21/2015 11:42 AM > Subject: Re: [openstack-dev] [infra] Upgrade to Gerrit 2.11 > > On Tue, Oct 13, 2015 at 05:08:29PM -0700, Za

Re: [openstack-dev] [Heat] core team nomination

- Original Message - > Congrats Rabi and Peter :) > > -Original Message- > From: Sergey Kraynev [mailto:[email protected]] > Sent: Wednesday, October 21, 2015 12:57 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [Heat] core

Re: [openstack-dev] [Neutron] HenryG addition to the Neutron Drivers team

On Wed, Oct 21, 2015 at 4:01 AM, Ihar Hrachyshka wrote: > > > On 21 Oct 2015, at 05:14, Armando M. wrote: > > > > Hi folks, > > > > Henry has been instrumental in many areas of the projects and his crazy > working hours makes even Kevin and I bow in awe. > > > > Jokes aside, I would like to anno

Re: [openstack-dev] [Fuel][QA][Plugins] Move functional tests from fuel-qa to the plugins

Mike, thanks for the clarification! I've filed a bug against fuel-qa [0] and submitted a patch [1]. Note that after a quick look, many Fuel projects have the same issue with the format of the MAINTAINERS file. Do you think we need one bug per project or do we piggy-back on the fuel-qa bug? BR, Simo

Re: [openstack-dev] [Neutron] Gerrit permissions and Merge rights

On Wed, Oct 21, 2015 at 6:12 AM, Gal Sagie wrote: > Do we also want to consider Project Kuryr part of this? > We already started sending Kuryr spec to the Neutron repository and I > think it would make sense to manage it > as part of Neutron spec process. > > Any opinions on that? > > I think thi

Re: [openstack-dev] [Neutron] HenryG addition to the Neutron Drivers team

Congratulations Henry! On Wed, Oct 21, 2015 at 6:33 PM, Kyle Mestery wrote: > On Wed, Oct 21, 2015 at 4:01 AM, Ihar Hrachyshka > wrote: > >> >> > On 21 Oct 2015, at 05:14, Armando M. wrote: >> > >> > Hi folks, >> > >> > Henry has been instrumental in many areas of the projects and his crazy >>

[openstack-dev] [Fuel] [CI] Running fuelclient tests against review requests for fuel-web repo

Hi, It's yet another time we broke fuelclient by merging a change in fuel-web repo. Since we are considering moving Fuel UI to a separate repo, and we need to run UI functional tests against changes in nailgun anyway, I think we should start to change our

[openstack-dev] [Nova] Scheduler based on CPU queue length

Hi All, I am fairly new to the OpenStack community and is trying to create a custom scheduler for Nova. A scheduler based on CPU queue length of the physical hosts. Kindly apologize if there are any inaccuracies in my statements. As I understand a weigher for the filter scheduler that weighs filt

[openstack-dev] [Fuel] Changing APIs and API versioning

Hi folks, I’d like to touch the aspect of Fuel development process that seems to be as wrong as possible. That aspect is how we change the API. The issue is that in Fuel anyone can change API at any point of time without even warning the rest of the same component’s team. Relying on this kind o

[openstack-dev] [puppet] Incompatible default parameters

Greetings, I'd like to discuss bug 1506061 ([1]). The main problem I'm trying to solve here is that using default parameters of classes cinder::api and nova::keystone::auth migration won't work, because Cinder will search for endpoint with different name ('Compute service' instead of 'nova')

Re: [openstack-dev] [Fuel] [CI] Running fuelclient tests against review requests for fuel-web repo

Vitaliy, Why do merge API changes without: 1. Fixing documentation? 2. bumping API version? -- Best regards, Sergii Golovatiuk, Skype #golserge IRC #holser On Wed, Oct 21, 2015 at 3:08 PM, Vitaly Kramskikh wrote: > Hi, > > It's yet another time we broke fuelclient by merging a change >

Re: [openstack-dev] [tc] [watcher] New project: Watcher

hi, seems like a neat idea, i had a few questions after watching the presentation from Vancouver. - is Watcher streaming the data captured by Ceilometer or is it querying the Ceilometer db? - is it utilising the Event data captured by Ceilometer or metric data? both? - i notice there's a ts

Re: [openstack-dev] [puppet] Incompatible default parameters

I think the only people that would be affected by the puppet-openstack module default not matching the keystone default are people that are trying to retrofit puppet into an already running environment. Those people already have a ton of work laid out in front of them, so I’m ok with making it ver

[openstack-dev] [release] release freeze until after the summit

The release management team is going to hold off on releasing anything else until at least Nov 2, unless there's an emergency, so we can focus on summit-related preparation and activities. Doug __ OpenStack Development Mailin

Re: [openstack-dev] [infra] Upgrade to Gerrit 2.11

On 10/21/2015 08:37 AM, Markus Zoeller wrote: > "Daniel P. Berrange" wrote on 10/21/2015 11:29:50 > AM: > >> From: "Daniel P. Berrange" >> To: "OpenStack Development Mailing List (not for usage questions)" >> >> Date: 10/21/2015 11:42 AM >> Subject: Re: [openstack-dev] [infra] Upgrade to Gerr

Re: [openstack-dev] [puppet] Incompatible default parameters

This change [1] introduced the nova_catalog_info and nova_catalog_admin_info parameters. Martin Mágr also mentioned that default values were wrong but the change got merged anyway. I agree that those default values should be changed to "nova" like initially suggested as the 2nd field is the servi

Re: [openstack-dev] [Ceilometer] Meeting cancelled for this week

thanks Ildiko it's also safe to assume the meeting will be cancelled for October 29 and November 5. please use the mailing list (it's actually preferred) for any discussion items. On 21/10/2015 8:22 AM, Ildikó Váncsa wrote: Hi All, I would like to inform you that we cancel the Ceilometer me

Re: [openstack-dev] [Fuel] [CI] Running fuelclient tests against review requests for fuel-web repo

Sergii, Let's move this discussion to the thread "[Fuel] Changing APIs and API versioning". We need to have this mechanism regardless of our decision on API versioning. 2015-10-21 20:31 GMT+07:00 Sergii Golovatiuk : > Vitaliy, > > Why do merge API changes without: > > 1. Fixing documentation? >

Re: [openstack-dev] [nova-compute][nova][libvirt] Extending Nova-Compute for image prefetching

Lingxian Kong wrote on 10/21/2015 06:44:27 AM: > From: Lingxian Kong > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 10/21/2015 06:44 AM > Subject: Re: [openstack-dev] [nova-compute][nova][libvirt] Extending > Nova-Compute for image prefetching > > Hi, Alberto,

Re: [openstack-dev] [Fuel] Changing APIs and API versioning

JFYI: (re-)start of this discussion was instigated by merge of this change (and here is revert ). And this is actually not the first time when we make backward incompatible changes in our API. AFAIR, the last time

[openstack-dev] [NFV][Telco] FYI telcowg-usecases is now in the openstack/ namespace on git.openstack.org

Hi all, Just an FYI as I had some questions about this, pursuant to a notice James sent out in August [1] the repository has moved from the stackforge/ namespace in git to the openstack/ namespace. Open reviews can now be found here: https://review.openstack.org/#/q/status:open+project:ope

Re: [openstack-dev] [Fuel] [CI] Running fuelclient tests against review requests for fuel-web repo

Sergii, 1. We only have auto-doc for developers which should be changed automatically. 2. We do not have proper API versioning. We didn't decide yet how to resolve it. Let's discuss versioning in "[Fuel] Changing APIs and API versioning" thread. Aleksey Kasatkin On Wed, Oct 21, 2015 at 5:26 PM

Re: [openstack-dev] [infra] Upgrade to Gerrit 2.11

On 2015-10-21 10:18:31 -0400 (-0400), Anita Kuno wrote: [...] > If folks are willing to help build Gerrit v3, that is wonderful. > If you would like to talk to Khai on how to get started > contributing to Gerrit, I'm going out on a limb here and will > guess he will be supportive of your efforts.

[openstack-dev] [Ironic] BIOS Configuration

Hi all, I am interested in remote BIOS configuration. There is "New driver interface for BIOS configuration specification" https://review.openstack.org/#/c/209612/ Is it possible to implement this without REST API endpoint? It would be great to access and configure the stuff without any addition

[openstack-dev] [Fuel] [Puppet] Potential critical issue, due Puppet mix stderr and stdout while execute commands

Hi, guys! Now I observe potential-dangerous situation in the providers of puppet-neutron module. I want share details, because not only puppet-neutron module may be broken by warnings from Openstack CLI utilities. After updating urllib3 library on my lab, commands like 'neutron net list' began

[openstack-dev] [Monasca] Congress + Monasca Meeting

Guys, We have half slot on Wed 3:40 with the Congress folks: https://wiki.openstack.org/wiki/Design_Summit/Mitaka/Etherpads#Congress These are the topics I proposed: 1. how to integrate Monasca with Congress so then Monasca can provide metrics, logs and event data for policy evaluation/enf

Re: [openstack-dev] [neutron][sriov] SRIOV-VM could not work well with normal VM

> -Original Message- > From: yujie [mailto:[email protected]] > Sent: Tuesday, October 20, 2015 5:34 AM > To: Moshe Levi > Cc: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [neutron][sriov] SRIOV-VM could not work well > with normal VM >

Re: [openstack-dev] [Neutron] HenryG addition to the Neutron Drivers team

Well deserved Henry! Edgar From: "Armando M." mailto:[email protected]>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:[email protected]>> Date: Tuesday, October 20, 2015 at 8:14 PM To: "OpenStack Development Mailing List (not for usage questions

Re: [openstack-dev] [Fuel] [Puppet] Potential critical issue, due Puppet mix stderr and stdout while execute commands

I spoken with Sergii about this and prepared a patch for get rid of SecurityWarning [0] - it was easy. But we can't get rid from InsecurePlatformWarning so easy way. I see next options: 1. Update python version as [1] said - should be hard task 2. Downgrade urllib version to one without such warnin

Re: [openstack-dev] [rally] Rally boot tests fails with Error Forbidden: It is not allowed to create an interface on external networks

Thanks Yair, I will dig into this more. I did try the "network" context, but same error. regards Behzad On Tue, Oct 20, 2015 at 12:53 PM, Yair Fried wrote: > > > On Tue, Oct 20, 2015 at 8:39 PM, Behzad Dastur > wrote: > >> Hi Yair, >> The rally version I am using is 0.1.2 >> >> > rally --versi

[openstack-dev] [Neutron][Kuryr] IRC Meeting - Canceled for next week (10/26)

Hello Everyone, Just wanted to share with anyone that wasn't in the meeting this week, that we decided to cancel the IRC meeting on the 10/26. See you all in the summit. Gal. __ OpenStack Development Mailing List (not for us

Re: [openstack-dev] [rally] Rally boot tests fails with Error Forbidden: It is not allowed to create an interface on external networks

Behzad, please run rally task start with `--debug' option and then provide us with some details (traceback, etc) about this error. Also Yair suggested to put `"auto_assign_nic": true' into scenario config - that is good idea. Get rid of `use_floatingip' - this parameter is not used for this scenar

Re: [openstack-dev] [release] establishing release liaisons for mitaka

Excerpts from Lingxian Kong's message of 2015-10-21 16:42:32 +0800: > Hi, Doug, > > After conversition with Mistral PTL(Renat), I'm willing to be mistral > liaison to take participate in cross-project release effort on beharf > of mistral team, so please count me in. Great, thank you for voluntee

Re: [openstack-dev] [Fuel] [CI] Running fuelclient tests against review requests for fuel-web repo

Hi, Vitaly, there is nothing to prevent us from triggering test based on event in one project but checking out the code from another. So you can setup job triggered for patchset-created event in commit to fuel-web/ repo. Then in this job you checkout both: code from fuel-web and code from python-

Re: [openstack-dev] [ceilometer][aodh] proposal to add Ryota Mibu to Aodh core

thanks for the feedback folks. i'd like to welcome Ryota to the Aodh core team. thank you for all the continued effort in building alarming functionality in OpenStack! On 16/10/2015 8:59 AM, gord chung wrote: sorry, as we usually do, please comment on gerrit[1]. if you cannot, then please com

Re: [openstack-dev] [security] The first version of the Logo for Openstack Security Project

On 10/21/2015 03:54 AM, Michael Xin wrote: Hi, guys: Thanks for your help. We are designing a logo and a flyer for Openstack Security Project. Rachel helped us with the task. Attached is her first version of the logo. Please let us know your feedback. http://5d100f09242e1d85fe65-9262bad2bd2ce9d8

Re: [openstack-dev] [security] The first version of the Logo for Openstack Security Project

I had looped some people into a previous version of the thread but they've not replied yet. I think we ran into this problem before and got a firm "maybe, depending on what it is" from the powers-that-be. Perhaps we should look at a rough-draft alternative logo while we await a verdict? > ---

Re: [openstack-dev] [Neutron] Gerrit permissions and Merge rights

On 21 October 2015 at 04:12, Gal Sagie wrote: > Do we also want to consider Project Kuryr part of this? > No, why would we? > We already started sending Kuryr spec to the Neutron repository and I > think it would make sense to manage it > as part of Neutron spec process. > No, unless what you

Re: [openstack-dev] [Magnum] Coe components status

Vikas, Could you clarify what do you mean under ’status’? I don’t seed this command in kubectl, so I assume it is get or describe? Also for Docker, is it info, inspect or stats? We can get app/container details through Marathon API in Mesos, but it’s very depend what information we are looking

Re: [openstack-dev] [Neutron] HenryG addition to the Neutron Drivers team

On 21 October 2015 at 02:01, Ihar Hrachyshka wrote: > > > On 21 Oct 2015, at 05:14, Armando M. wrote: > > > > Hi folks, > > > > Henry has been instrumental in many areas of the projects and his crazy > working hours makes even Kevin and I bow in awe. > > > > Jokes aside, I would like to announce

Re: [openstack-dev] [Neutron] Gerrit permissions and Merge rights

On Wed, Oct 21, 2015 at 7:37 PM, Armando M. wrote: > > > On 21 October 2015 at 04:12, Gal Sagie wrote: > >> Do we also want to consider Project Kuryr part of this? >> > > No, why would we? > [Gal] Because Kuryr is a special project which was created in order to expose Neutron and its services t

Re: [openstack-dev] [Neutron] Gerrit permissions and Merge rights

On Wed, Oct 21, 2015 at 11:37 AM, Armando M. wrote: > > > On 21 October 2015 at 04:12, Gal Sagie wrote: > >> Do we also want to consider Project Kuryr part of this? >> > > No, why would we? > > The reason to consider it is because Kuryr is a sub-project of Neutron, and they are doing their spec

Re: [openstack-dev] [ironic] [horizon] ironic panels

On 21/10/2015 01:48, Jim Rollenhagen wrote: On Tue, Oct 20, 2015 at 04:50:04PM +0100, Beth Elwell wrote: Hi Jim, I have replied inline to your comments below: On 19/10/2015 19:38, Jim Rollenhagen wrote: On Mon, Oct 19, 2015 at 07:05:04PM +0100, Beth Elwell wrote: Hi all, I am currently in

Re: [openstack-dev] [Neutron] Gerrit permissions and Merge rights

On 21 October 2015 at 09:53, Kyle Mestery wrote: > On Wed, Oct 21, 2015 at 11:37 AM, Armando M. wrote: > >> >> >> On 21 October 2015 at 04:12, Gal Sagie wrote: >> >>> Do we also want to consider Project Kuryr part of this? >>> >> >> No, why would we? >> >> > The reason to consider it is because

Re: [openstack-dev] [Neutron] Gerrit permissions and Merge rights

On 21 October 2015 at 09:52, Gal Sagie wrote: > > > On Wed, Oct 21, 2015 at 7:37 PM, Armando M. wrote: > >> >> >> On 21 October 2015 at 04:12, Gal Sagie wrote: >> >>> Do we also want to consider Project Kuryr part of this? >>> >> >> No, why would we? >> > > [Gal] Because Kuryr is a special proj

Re: [openstack-dev] [nova] Change from Mitaka: Expected UNIX signal to generate Guru Meditation (error) Reports

On Wed, Oct 21, 2015 at 02:43:39PM +0200, Kashyap Chamarthy wrote: > Background > -- > > Oslo Guru Meditation (error) Reports (GMR)[*] are a useful debugging > mechanism that allows one to capture the current state of a Nova > process/executable (e.g. `nova-compute`, `nova-api`, etc). > >

Re: [openstack-dev] [Neutron] Gerrit permissions and Merge rights

On Wed, Oct 21, 2015 at 12:08 PM, Armando M. wrote: > > > On 21 October 2015 at 09:53, Kyle Mestery wrote: > >> On Wed, Oct 21, 2015 at 11:37 AM, Armando M. wrote: >> >>> >>> >>> On 21 October 2015 at 04:12, Gal Sagie wrote: >>> Do we also want to consider Project Kuryr part of this?

Re: [openstack-dev] [Neutron] Gerrit permissions and Merge rights

On 21 October 2015 at 10:29, Kyle Mestery wrote: > On Wed, Oct 21, 2015 at 12:08 PM, Armando M. wrote: > >> >> >> On 21 October 2015 at 09:53, Kyle Mestery wrote: >> >>> On Wed, Oct 21, 2015 at 11:37 AM, Armando M. wrote: >>> On 21 October 2015 at 04:12, Gal Sagie wrote: >

[openstack-dev] [cinder] No meeting Oct 28th

It seems someone always asks during the Summit, so this is an attempt to make sure it is known. Due to the Design Summit taking place next week, Cinder will not be holding its regular Wednesday meeting. We will resume normal meetings the following week. Thanks! Sean McGinnis (smcginnis) ___

Re: [openstack-dev] [Neutron] Gerrit permissions and Merge rights

On Wed, Oct 21, 2015 at 12:34 PM, Armando M. wrote: > > > On 21 October 2015 at 10:29, Kyle Mestery wrote: > >> On Wed, Oct 21, 2015 at 12:08 PM, Armando M. wrote: >> >>> >>> >>> On 21 October 2015 at 09:53, Kyle Mestery wrote: >>> On Wed, Oct 21, 2015 at 11:37 AM, Armando M. wrote:

Re: [openstack-dev] [nova] Change from Mitaka: Expected UNIX signal to generate Guru Meditation (error) Reports

Sean, If you are using the GMR code from oslo-incubator, please switch over to the new oslo.service. I don't see any pending reviews. Thanks, -- Dims On Wed, Oct 21, 2015 at 1:29 PM, Sean McGinnis wrote: > On Wed, Oct 21, 2015 at 02:43:39PM +0200, Kashyap Chamarthy wrote: > > Background > > --

[openstack-dev] [Neutron][networking-sfc] no IRC project meeting for service function chaining project this week and next week

Hi, Since most of us are very busy with presentation preparation for the Summit, let's cancel this week's project meeting. We will resume the meeting on 11/5. Thanks, Cathy __ OpenStack Development Mailing List (not for usag

[openstack-dev] AUTO: Alon Marx is out of the office (returning 11/02/2015)

I am out of the office until 11/02/2015. I will be available occasionally on email. For any urgent matters please contact Ohad Atia. Note: This is an automated response to your message "OpenStack-dev Digest, Vol 42, Issue 56" sent on 10/21/15 5:10:27 AM. This is the only notification you wil

[openstack-dev] [Nova][Cinder] Multi-attach volume help needed

Hi Folks, The work has been ongoing for a while now to implement the feature to support attaching a single volume to multiple VM instances. This work impacts both Nova and Cinder. We are in quite good shape with the implementation, but it is still far for completion and we temporarily ran out

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

On Wed, Oct 21, 2015 at 6:26 AM, Dave McCowan (dmccowan) wrote: > Hi Arif-- > Are you using Keystone for authentication? > If so, you need to get an authentication token from Keystone and add > it as a header to your curl command: -H "X-Auth-Token:*$TOKEN*". > You do not need to speci

Re: [openstack-dev] [Fuel] [CI] Running fuelclient tests against review requests for fuel-web repo

Can we do it in OpenStack Infra.. ? On Wed, Oct 21, 2015 at 9:27 AM Aleksandra Fedorova wrote: > Hi, Vitaly, > > there is nothing to prevent us from triggering test based on event in > one project but checking out the code from another. > > So you can setup job triggered for patchset-created eve

Re: [openstack-dev] [Fuel][QA][Plugins] Move functional tests from fuel-qa to the plugins

We should fix it everyone. I don't think we need to be too heavy with the process, so I'd just update a single bug vs creating so many bugs... Fuel Infra team - please provide an estimate when script is going to be ready (which adds people automatically to gerrit review). Thanks, On Wed, Oct 21,

Re: [openstack-dev] [release] establishing release liaisons for mitaka

Doug, I updated the liaisons for Trove on the wiki page. Thanks, -Craig On Wed, Oct 21, 2015 at 11:26 AM Doug Hellmann wrote: > Excerpts from Lingxian Kong's message of 2015-10-21 16:42:32 +0800: > > Hi, Doug, > > > > After conversition with Mistral PTL(Renat), I'm willing to be mistral > > li

[openstack-dev] [fuel] Tests and feedback needed: Fuel ISO with Liberty support

All, In case you've missed the announcement from Alexandra [0], Fuel now supports OpenStack Liberty, and the nightly ISO images [1] are passing our Build Verification Test [2]. [0] http://lists.openstack.org/pipermail/openstack-dev/2015-October/077309.html [1] https://ci.fuel-infra.org/ [2] https

[openstack-dev] [cinder] meeting place for event Monday night in Tokyo ...

All, As has been our custom during previous summits, the Cinder team would will be getting together for dinner and drinks on Monday night (11/26) at the Tokyo Summit. Not sure where the evening will take us, but we are planning to meet by registration at the Convention Center. Looking at th

[openstack-dev] [Trove] Mitaka Design Summit Sessions

We've updated the Trove Sessions to include some great topics. https://wiki.openstack.org/wiki/Design_Summit/Mitaka/Etherpads#Trove http://mitakadesignsummit.sched.org/overview/type/trove Thanks to everyone involved and looking forward to seeing everyone next week! -Craig Vyvial (cp16net) __

Re: [openstack-dev] [cinder] meeting place for event Monday night in Tokyo ...

On 10/21/2015 04:54 PM, Jay S. Bryant wrote: > All, > > As has been our custom during previous summits, the Cinder team would > will be getting together for dinner and drinks on Monday night (11/26) > at the Tokyo Summit. > > Not sure where the evening will take us, but we are planning to meet by

Re: [openstack-dev] [cinder] meeting place for event Monday night in Tokyo ...

On 10/21/2015 04:00 PM, Anita Kuno wrote: On 10/21/2015 04:54 PM, Jay S. Bryant wrote: All, As has been our custom during previous summits, the Cinder team would will be getting together for dinner and drinks on Monday night (11/26) at the Tokyo Summit. Not sure where the evening will take u

Re: [openstack-dev] [security] The first version of the Logo for Openstack Security Project

Rob and Michael: Thanks for the update. We will probably not use any Openstack Logo. Here is the first draft of the flyer: http://5a6aa6580e900b8e8020-e5e45c5cb10329ebc9fb69948bb1b1a5.r65.cf1.rackcdn.com/ossp-flag-flyer.pdf Please send us your feedback. Yours, Michael On 10/21/15, 11:

  1   2   >