Re: [openstack-dev] [neutron] [QoS] QoS weekly meeting

Hi Miguel, Thank you for leading this. On Tue, Apr 7, 2015 at 8:45 AM, Miguel Ángel Ajo wrote: > On Tuesday, 7 de April de 2015 at 3:14, Kyle Mestery wrote: > > On Mon, Apr 6, 2015 at 6:04 PM, Salvatore Orlando > wrote: > > > > On 7 April 2015 at 00:33, Armando M. wrote: > > > On 6 April 2015

[openstack-dev] [docs] [End User Guide] [Keystone] keyring support for python-keystoneclient and python-openstackclient

Good day to everyone! My name is Olena, I am new in OpenStack (working as a tech writer). And I'm stuck on a bug https://launchpad.net/bugs/1419990 (patch https://review.openstack.org/#/c/163503/). I have 2 questions, please: Does the page http://docs.openstack.org/user-guide/content/cli_openrc.

Re: [openstack-dev] [Mistral] Upgrading to YAQL 1.0

Well, we’ve been ready to switch to YAQL-1.0 for a couple of months. We researched it, figured out how our integration would change etc. It’s pretty easy to do from our side. So let’s wait for the official YAQL-1.0.X release on pypi. Renat Akhmerov @ Mirantis Inc. > On 07 Apr 2015, at 00:56,

Re: [openstack-dev] [Mistral] Propose Winson Chan m4dcoder for core team

+1 with my both hands. Winson has been working on Mistral for about a year, was actively participating in the very first workflow engine version (what we called PoC) and keeps bringing his experience and excellent engineering skills to the project. Thanks Winson for your passionate work! Renat

[openstack-dev] [nova] How are vcpu's, ram mapped with an instance

Hi Folks, When we boot an instance and assign a flavor to it, how are the vcpu's, ram given to the instance. Actually the question is this while creating an instance we must be assigning it some Vcpu's according to the flavor we gave to the instance. So where are these Vcpu's placed and how are

Re: [openstack-dev] [Mistral] Propose Winson Chan m4dcoder for core team

It would be good to see Winson as the core contributor in Mistral. +1 for Winson! On Tue, Apr 7, 2015 at 11:53 AM, Renat Akhmerov wrote: > +1 with my both hands. Winson has been working on Mistral for about a > year, was actively participating in the very first workflow engine version > (what

Re: [openstack-dev] [oslo] not running for PTL for liberty cycle

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/03/2015 02:50 PM, Doug Hellmann wrote: > Team, > > I have decided not to run for PTL for Oslo for the next cycle. > > Serving as PTL for the last three releases has been a rewarding > experience, and I think we’ve made some great strides togeth

Re: [openstack-dev] [TripleO][Heat] Overcloud software updates and ResourceGroups

On Thu, Apr 02, 2015 at 06:31:39PM -0400, Zane Bitter wrote: > A few of us have been looking for a way to perform software updates to > servers in a TripleO Heat/Puppet-based overcloud that avoids an impedance > mismatch with Heat concepts and how Heat runs its workflow. As many talented > TripleO-

Re: [openstack-dev] [neutron] Liberty mid-cycle coding sprint

Kyle Mestery wrote: > I know we're not even at the Liberty Design Summit in Vancouver yet, but > I wanted to take this time to announce the Neutron mid-cycle coding > sprint for Liberty. HP has been gracious enough to offer to host at it's > Fort Collins, CO offices. The dates are set for June 24-2

[openstack-dev] [Zaqar] PTL Candidacy

Greetings, You read it right, you've not burned out yet - I probably will. Here's a crazy idea, what if I run for 2 PTL positions on the projects I've been putting my focus on lately? Hopefully, by sending this out now, I'll be able to answer all your questions in time before the candidacy period

[openstack-dev] Skipping Cross-Project meeting today?

Hi! The agenda for the cross-project meeting is currently empty: https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting Unless someone has something to discuss (and adds it to the agenda docket), I propose we skip this one and focus on fixing release -critical bugs to issue a RC1 in the com

Re: [openstack-dev] [Fuel] PEP8 issues in Fuel-Web repo

This is also relevant for python-fuelclient. > 6 квіт. 2015 о 12:27 Nikolay Markov написав(ла): > > Hello everyone, > > I know this is really low priority and so on, but here is this bug about > moving to the newest version of "hacking" package: > https://bugs.launchpad.net/fuel/+bug/1410810

Re: [openstack-dev] [all][oslo][clients] Let's speed up start of OpenStack libs and clients by optimizing imports with profimp

> On 7/4/2015, at 0:43, Robert Collins wrote: > > On 7 April 2015 at 05:11, Joe Gordon wrote: >> >> >> On Mon, Apr 6, 2015 at 8:39 AM, Dolph Mathews >> wrote: >>> >>> >>> On Mon, Apr 6, 2015 at 10:26 AM, Boris Pavlovic wrote: Jay, > Not far, IMHO. 100ms differen

Re: [openstack-dev] [Mistral] Propose Winson Chan m4dcoder for core team

Although I have jumpped into Mistral just for a short time, but really appreciate Winson's vision about my patches, and his work is of great value to Mistral. I'm not in the core team of Mistral, but really hope to see Winson as a core member to bring more to Mistral. On Tue, Apr 7, 2015 at 5:08

Re: [openstack-dev] Developer survey questions

To the extent that it's useful to those suggesting the questions, it feels to me like this could be an ongoing resource rather than a one-off survey. Hence, perhaps a web page that all OpenStack members should occ

Re: [openstack-dev] [Mistral] Upgrading to YAQL 1.0

Hi Renat & Dmitry Today we released YAQL 1.0.0b2 and release is available on PyPI, I think it's better to start migration to YAQL 1.0.0 right now, we don't expect any major changes, only small bug-fixes that should not affect your integration. And we will release 1.0.0 before end of Kilo cycle. O

Re: [openstack-dev] [Ironic] [RFC/FFE] Finishing state machine work for Kilo

On 04/06/2015 05:15 PM, Devananda van der Veen wrote: Hi! The situation you describe is the same that concerned me with regards to stable/juno compatibility. As soon as the client library started passing a version header by default, it exposed Kilo changes to all users. Anyone testing from trunk

[openstack-dev] [all] Issues with pip 6.1

Hi, I tried to install a fresh DevStack but it doesn't work because of the new release of pip: pip 6.1 (probably released today, https://pip.pypa.io/en/stable/news.html still says "6.1.0 (unreleased)"...). (1) update.py of openstack/requirements uses req.InstallRequirement.url attribute, but t

Re: [openstack-dev] [Ironic] [RFC/FFE] Finishing state machine work for Kilo

On 04/06/2015 06:53 AM, Ramakrishnan G wrote: +1 from me. Since we don't have ENROLL state as per the state machine, I think it should be MANAGEABLE when we enroll a node. At least, it can also prevent nodes getting into a ready state even before an operator getting hands on it. One comment o

[openstack-dev] [docs][rally] Rally template tasks in a nutshell

Hi stackers, as you might remember, we have recently added a nice feature to Rally which is the support of *task templates*. Rally uses the template syntax based on *Jinja2*, and thus makes it simple to parameterize your benchmark task files. Our step-by-step tutorial has just been updated with a

Re: [openstack-dev] [Mistral] Upgrading to YAQL 1.0

Ok, sounds good! So if there aren’t any objections we can start doing it asap. Renat Akhmerov @ Mirantis Inc. > On 07 Apr 2015, at 16:00, Serg Melikyan wrote: > > Hi Renat & Dmitry > > Today we released YAQL 1.0.0b2 and release is available on PyPI, I > think it's better to start migration t

Re: [openstack-dev] [Heat] PTL Candidacy

+1 I am very happy to work with you:) At 2015-04-07 10:50:23, "Steve Baker" wrote: >I'd like to announce my candidacy for the Heat PTL in Liberty. > >As I was the PTL during Icehouse, this will be Heat's first rerun PTL >under our convention for rotating leaders. Even if elected I would hope >th

[openstack-dev] [neutron][lbaas] Horizon support for neutron-lbaas v2

Hi guys, LBaaS v2 has no horizon support as for now and I want to know if this work is planned to be done and , if yes, in what time frame. Is there a plan to develop it for Kilo or for L release? Thanks, Evg __ OpenStack De

Re: [openstack-dev] [stable] [nova] FFE for "libvirt: proper monitoring of live migration progress"

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 +344 new lines of code for an exception patch? No way. Let's take time to consider the patch outside the very next release. On 04/04/2015 01:31 AM, Billy Olsen wrote: > Hello, > > I would like to get a FFE for patch > https://review.openstack.org/#/

[openstack-dev] [Ironic] PTL Candidacy

Hi all, I'd like to announce my candidacy as PTL for Ironic for the Liberty cycle. I've been involved in OpenStack since the Essex cycle, and have served as PTL for Ironic since I started the project at the Havana summit. As the project has matured, my day-to-day activity within the project has ch

Re: [openstack-dev] [oslo] not running for PTL for liberty cycle

Thanks a lot for what you have done ! --- Mehdi Abaakouk mail: [email protected] irc: sileht Le 2015-04-03 14:50, Doug Hellmann a écrit : Team, I have decided not to run for PTL for Oslo for the next cycle. Serving as PTL for the last three releases has been a rewarding experience, and I th

Re: [openstack-dev] [neutron] [QoS] QoS weekly meeting

Hi  Miguel, I am interested to join this meeting. I assume that CC of this mail are from different time zones.Please provide time slot with common time zone. With Best Regards Raghunath Dudyala Tata Consultancy Services Limited Mailto: [email protected] Website: http://www.tcs.com _

Re: [openstack-dev] [Neutron]: partially update over REST APIs

Neutron PUT operations currently fulfil PATCH semantics in most cases. If you omit an attribute in a PUT request its value will stay unchanged. This behaviour, even if not strictly correct, will not change until a strategy for evolving the API is implemented. Salvatore On 7 April 2015 at 02:06,

Re: [openstack-dev] [all] Issues with pip 6.1

> (2) it's not more possible to install argparse on Python 2.7 (...) Donald Stufft released pip 6.1.1, he reverted the change which prevented to install argparse. Thanks for the quick fix! > (1) update.py of openstack/requirements uses req.InstallRequirement.url > attribute, but this attribute

Re: [openstack-dev] [Zaqar] PTL Candidacy

Obviously, where I said Juno, I meant Kilo :) On 07/04/15 11:35 +0200, Flavio Percoco wrote: Greetings, You read it right, you've not burned out yet - I probably will. Here's a crazy idea, what if I run for 2 PTL positions on the projects I've been putting my focus on lately? Hopefully, by send

Re: [openstack-dev] Multi Region Designate

Hey Anik, So, unlike Nova or other services which really are "region" aware, Designate, being designed to push data into the global DNS namespace, doesn't have the same concept of regions. Typically, you will either have regions which are "close enough" to run a Galera/Percona cluster across them

Re: [openstack-dev] [all] Issues with pip 6.1

On 2015-04-07 07:39:27 -0400 (-0400), Victor Stinner wrote: [...] > > => see https://bugs.launchpad.net/tempest/+bug/1440984 > > pip 6.1.1 reintroduced the url attribute but there is a bug in the > property :-/ > > According to pip developers, the problem is that OpenStack should > not use Python

Re: [openstack-dev] [all] Issues with pip 6.1

On 04/07/2015 07:39 AM, Victor Stinner wrote: >> (2) it's not more possible to install argparse on Python 2.7 (...) > > Donald Stufft released pip 6.1.1, he reverted the change which prevented to > install argparse. > > Thanks for the quick fix! > >> (1) update.py of openstack/requirements uses

Re: [openstack-dev] [qa] [devstack] Confusion about member roles in tempest/devstack

On 6 April 2015 at 21:27, David Kranz wrote: > On 04/06/2015 03:14 PM, Matthew Treinish wrote: > > On Mon, Apr 06, 2015 at 02:25:14PM -0400, David Kranz wrote: > > There have been a number of changes in tempest recently that seem to > coordinate with devstack that are a bit unclear. > > Well, the

Re: [openstack-dev] [Murano] Feature Freeze Exceptions

Hi folks, Only two days left until RC-1, but few features that were marked as FFE are still not finished: 1. Migrate to YAQL 1.0 [1] 2. Murano Versioning [2] Both of these features are moved to Liberty. References: [1] https://blueprints.launchpad.net/murano/+spec/migrate-to-yaql-vnext [2] http

[openstack-dev] [Ironic] How to deal with microversions in 3rdparty tools

Hi again, hope you're not tired of this topic :D I'm seeking for advice on what to do with microversions in discoverd. Basically I have the following options: 1. Do nothing. Get whatever behavior I can get from installed Ironic and Ironic client. Though unlikely, may get broken by future chan

Re: [openstack-dev] [neutron] [QoS] QoS weekly meeting

On Apr 6, 2015, at 11:56 , Miguel Ángel Ajo mailto:[email protected]>> wrote: I’d like to co-organized a QoS weekly meeting with Sean M. Collins, In the last few years, the interest for QoS support has increased, Sean has been leading this effort [1] and we believe we should get into a c

Re: [openstack-dev] [docs][rally] Rally template tasks in a nutshell

Great improvement! Thanks! On Tue, Apr 7, 2015 at 1:17 PM, Mikhail Dubov wrote: > Hi stackers, > > as you might remember, we have recently added a nice feature to Rally > which is the support of *task templates*. Rally uses the template syntax > based on *Jinja2*, and thus makes it simple to par

Re: [openstack-dev] [Ironic] How to deal with microversions in 3rdparty tools

I’m not sure that recommending one or the other is best. We should lay out the options (as you just did) and let folks decide what works best for them. For things like discoverd, where you have many users, perhaps you should allow the user to pass a version (for example, option 2 depends on the us

Re: [openstack-dev] [neutron] Liberty mid-cycle coding sprint

On 04/07/2015 12:33 AM, Ben Pfaff wrote: > On Mon, Apr 06, 2015 at 03:00:17PM -0500, Kyle Mestery wrote: >> I know we're not even at the Liberty Design Summit in Vancouver yet, but I >> wanted to take this time to announce the Neutron mid-cycle coding sprint >> for Liberty. HP has been gracious eno

Re: [openstack-dev] [Neutron]: partially update over REST APIs

Hi Salvatore, Thanks for your quick response. In that case, how to remove a property? set it as None in the update? Yi On 4/7/15 7:28 AM, Salvatore Orlando wrote: Neutron PUT operations currently fulfil PATCH semantics in most cases. If you omit an attribute in a PUT request its value will s

Re: [openstack-dev] [Ironic] How to deal with microversions in 3rdparty tools

On 04/07/2015 03:15 PM, Jim Rollenhagen wrote: I’m not sure that recommending one or the other is best. We should lay out the options (as you just did) and let folks decide what works best for them. For things like discoverd, where you have many users, perhaps you should allow the user to pass a

Re: [openstack-dev] [Mistral] Propose Winson Chan m4dcoder for core team

Hello all, As a QA Engineer of Mistral, I also appreciate Winson's contribution to the project, his ideas and I will be glad to see him as a core engineer of Mistral project. On Tue, Apr 7, 2015 at 12:56 PM, Lingxian Kong wrote: > Although I have jumpped into Mistral just for a short time, but

Re: [openstack-dev] [neutron] Liberty mid-cycle coding sprint

On Tue, Apr 7, 2015 at 8:15 AM, Russell Bryant wrote: > On 04/07/2015 12:33 AM, Ben Pfaff wrote: > > On Mon, Apr 06, 2015 at 03:00:17PM -0500, Kyle Mestery wrote: > >> I know we're not even at the Liberty Design Summit in Vancouver yet, > but I > >> wanted to take this time to announce the Neutro

Re: [openstack-dev] [docs] [End User Guide] [Keystone] keyring support for python-keystoneclient and python-openstackclient

On Tue, Apr 7, 2015 at 3:52 AM, Olena Logvinova wrote: > Good day to everyone! > > My name is Olena, I am new in OpenStack (working as a tech writer). And > I'm stuck on a bug https://launchpad.net/bugs/1419990 (patch > https://review.openstack.org/#/c/163503/). > > I have 2 questions, please: >

Re: [openstack-dev] [docs][rally] Rally template tasks in a nutshell

Mikhail, Nice work! Best regards, Boris Pavlovic On Tue, Apr 7, 2015 at 4:08 PM, Aleksandr Maretskiy wrote: > Great improvement! Thanks! > > On Tue, Apr 7, 2015 at 1:17 PM, Mikhail Dubov wrote: > >> Hi stackers, >> >> as you might remember, we have recently added a nice feature to Rally >>

Re: [openstack-dev] [nova] How are vcpu's, ram mapped with an instance

Hi Abhishek, You can change it directly using KVM/Qemu command line. However, nova probably won't be notified and the information on the database will be outdated. Em ter, 7 de abr de 2015 às 06:04, Abhishek Talwar/HYD/TCS < [email protected]> escreveu: > Hi Folks, > > When we boot an inst

Re: [openstack-dev] [all] how to send messages (and events) to our users

> - Specific user oriented log messages (distinct from our normal operator > logs)> - Deprecation messages (if they are using old resource > properties/template features)> - Progress and resource state changes (an > application doesn't want to poll an api for a state change) > - Automated actio

Re: [openstack-dev] [nova] How are vcpu's, ram mapped with an instance

- Original Message - > From: "Abhishek Talwar/HYD/TCS" > To: [email protected] > > Hi Folks, > > When we boot an instance and assign a flavor to it, how are the vcpu's, ram > given to the instance. Actually the question is this while creating an > instance we must be assi

[openstack-dev] [Heat] Kilo RC1 available

Hello everyone, Heat is the first project to produce a release candidate for the Kilo release! The RC1 tarball, as well as a list of last-minute features and fixed bugs since kilo-3 are available at: https://launchpad.net/heat/kilo/kilo-rc1 Unless release-critical issues are found that warrant a

Re: [openstack-dev] [neutron] [QoS] QoS weekly meeting

Hi Raghunath, feel free to look at: https://wiki.openstack.org/wiki/Meetings and suggest other timeslots with a free meeting room, this is a very wide community, and it’s impossible to get a timeslot in everybody working hours. Please note that option

[openstack-dev] [nova] [stringfreeze] request for SFE

Nova cores, I would like to request a SFE for the below fix: https://review.openstack.org/#/c/170190/ https://bugs.launchpad.net/nova/+bug/1438226 This change adds a useful error message to help users debug incompatibilities with some versions of a dependency (libvirt). Without

[openstack-dev] [horizon] - Access to project info in horizon/base.py

Hi all, I would like to know if it's possible to get project info inside this function https://github.com/openstack/horizon/blob/stable/juno/horizon/base.py#L839 I don't know if this function is executed before or after login action, so I don't know if is possible to get the scoped token and, t

Re: [openstack-dev] [neutron][lbaas] Horizon support for neutron-lbaas v2

?Hey Evgeny, I believe Vivek is working on Horizon lbaasv2 support. We werent given a timeline or anything but sounds like its being actively worked on. I would reach out to him to get better timelines if concerned. Phillip V. Toohill III Software Developer [http://600a2794aa4ab5bae6bd-8d3014

Re: [openstack-dev] [Zaqar] PTL Candidacy

On 04/07/2015 04:43 AM, Flavio Percoco wrote: Obviously, where I said Juno, I meant Kilo :) You sure you're not burned out? :P -jay On 07/04/15 11:35 +0200, Flavio Percoco wrote: Greetings, You read it right, you've not burned out yet - I probably will. Here's a crazy idea, what if I run f

Re: [openstack-dev] [nova][ec2-api] Need advice about running Tempest against stackforge/ec2-api

Hi Sean On Mon, Apr 6, 2015 at 7:34 PM, Sean Dague wrote: > On 04/06/2015 12:13 PM, Andrey M. Pavlov wrote: > > Hi, > > > > We've got a couple of problems running original Tempest EC2 API test > against new standalone stackforge/ec2-api project and > > I wanted to ask for some advice about how

Re: [openstack-dev] [neutron] [QoS] QoS weekly meeting

Hi Anthony, nice to hear about it! :) Is the implementation available somewhere?, IMHO, the design should be what’s best for the whole neutron project looking into future extension of the design, by this I mean that we should not influence the design by what was already designed D/S, *but*,

Re: [openstack-dev] [all] how to send messages (and events) to our users

On 04/07/2015 10:10 AM, gordon chung wrote: > >> - Specific user oriented log messages (distinct from our normal > operator logs) >> - Deprecation messages (if they are using old resource > properties/template features) >> - Progress and resource state changes (an application doesn't want to > pol

Re: [openstack-dev] [neutron] [QoS] QoS weekly meeting

On Apr 7, 2015, at 10:50 , Miguel Angel Ajo Pelayo mailto:[email protected]>> wrote: Hi Anthony, nice to hear about it! :) Is the implementation available somewhere?, Yes, it’s been posted on github[1]. IMHO, the design should be what’s best for the whole neutron project looking into futur

Re: [openstack-dev] [stable] [Cinder] FFE for "Clear migration_status from a destination volume if migration fails"

Mitsuhiro, I had already put a +2 on this, so I am agreeable to an FFE. Mike or John, what are your thoughts? Jay On 04/06/2015 06:27 PM, Mitsuhiro Tanino wrote: Hello, I would like to get a FFE for patch https://review.openstack.org/#/c/161328/. This patch fixes the volume migration probl

Re: [openstack-dev] [all] how to send messages (and events) to our users

Notifications were added for this very purpose. At Rax, we have a downstream consumer (yagi) that routes notifications to an appropriate ATOM/pubsub feed (based on tenant-id). Notifications are only as heavy as you want to make them. The only required fields are event_type and timestamp. ?

Re: [openstack-dev] [neutron] [QoS] QoS weekly meeting

On Apr 7, 2015, at 11:05 , Veiga, Anthony mailto:[email protected]>> wrote: On Apr 7, 2015, at 10:50 , Miguel Angel Ajo Pelayo mailto:[email protected]>> wrote: Hi Anthony, nice to hear about it! :) Is the implementation available somewhere?, Yes, it’s been posted on github[

Re: [openstack-dev] [barbican] Utilizing the KMIP plugin

Hello Christopher, Just checking, but is that barbican-api.conf file located in your local system's /etc/barbican folder? If not that is the preferred place for local development. Modifying the copy that is in your local git repository will have no effect. Also, please double check that your l

Re: [openstack-dev] [nova] [stringfreeze] request for SFE

Finucane, Stephen wrote: > Nova cores, > > I would like to request a SFE for the below fix: > > https://review.openstack.org/#/c/170190/ > https://bugs.launchpad.net/nova/+bug/1438226 > > This change adds a useful error message to help users debug incompatibilities > with some versi

Re: [openstack-dev] [Murano] PTL Candidacy

Confirmed. On Sun, Apr 5, 2015 at 11:56 AM, Serg Melikyan wrote: > Hi folks, > > I'd like to announce my candidacy as PTL for Murano [1]. > > I was handling PTL responsibilities in this release cycle so far, > after Ruslan Kamaldinov (who was handling them in Juno cycle) hand > over them to me on

Re: [openstack-dev] [Documentation] PTL Candidacy

Confirmed. On Sun, Apr 5, 2015 at 2:42 PM, Lana Brindley wrote: > Hi everyone, > > I am announcing my candidacy for Documentation PTL. > > I have been contributing to the OpenStack documentation project since 2013, > and have been a core contributor since early 2014. During that time I have > bee

Re: [openstack-dev] [Oslo] Common Libraries PTL Candidacy

confirmed On Sun, Apr 5, 2015 at 4:21 PM, Davanum Srinivas wrote: > Hi Everyone, > > After shadowing Doug for a while, It's going to be a really hard job > filling Doug's shoes. I am very thankful and very glad we had him so > long to guide us. I'd like to continue his good work going forward. >

Re: [openstack-dev] [Manila] PTL Candidacy

confirmed On Mon, Apr 6, 2015 at 1:30 PM, Ben Swartzlander wrote: > Hello all, > > I'm announcing my candidacy for Manila PTL for the Liberty release. > > I've been leading the Manila project since its inception back in 2013, and > I'm excited and humbled by how much the community around the pro

Re: [openstack-dev] PTL Candidacy

confirmed On Mon, Apr 6, 2015 at 9:57 AM, Dean Troyer wrote: > I would like to announce my candidacy for OpenStackClient PTL. I started > this project nearly three years ago in order to give CLI users a uniform > experience in interacting with OpenStack clouds. OSC was recently the first > pro

Re: [openstack-dev] [Congress] PTL candidacy

confirmed On Mon, Apr 6, 2015 at 1:42 PM, Tim Hinrichs wrote: > Hi all, > > I'm writing to announce my candidacy for PTL of Congress for the Liberty > cycle. We've made a lot of progress in Kilo, and I'm excited by what we'll > achieve in Liberty! To give us some perspective, I compiled a (par

Re: [openstack-dev] [Zaqar] PTL Candidacy

confirmed On 04/07/2015 05:35 AM, Flavio Percoco wrote: > Greetings, > > You read it right, you've not burned out yet - I probably will. Here's > a crazy idea, what if I run for 2 PTL positions on the projects I've > been putting my focus on lately? Hopefully, by sending this out now, > I'll be a

Re: [openstack-dev] [TripleO] PTL Candidacy

confirmed On 04/06/2015 11:42 PM, James Slagle wrote: > Hi, > > I'm running for TripleO PTL for the Liberty cycle. I've been an active > TripleO developer and contributor for going on 2 years now. > > I'm really excited about all the great progress TripleO made during Kilo. > The puppet integrat

Re: [openstack-dev] [neutron][lbaas] Horizon support for neutron-lbaas v2

Hi Evgeny, We have just started working on Horizon lbaasv2 support. I have to sync up with my team on the time-line but it is not targeted for Kilo release. Since it is a major effort, we will need more hands. Let me know if anyone is interested to contribute. On a related note, Do we have a sam

Re: [openstack-dev] [Ironic] PTL Candidacy

confirmed On 04/07/2015 06:58 AM, Devananda van der Veen wrote: > Hi all, > > I'd like to announce my candidacy as PTL for Ironic for the Liberty cycle. > I've been involved in OpenStack since the Essex cycle, and have served as > PTL for Ironic since I started the project at the Havana summit. A

[openstack-dev] OpenStack in the classroom

CS and EE schools today use open source software as the basis for a lot of coursework and as the practical example for several concepts. Most often the exemplar system is Linux. Yet if students are even taught about the cloud, they often learn about that other cloud company from Seattle. I thin

Re: [openstack-dev] [Heat] PTL Candidacy

confirmed On 04/06/2015 10:50 PM, Steve Baker wrote: > I'd like to announce my candidacy for the Heat PTL in Liberty. > > As I was the PTL during Icehouse, this will be Heat's first rerun PTL > under our convention for rotating leaders. Even if elected I would hope > that we continue to find Heat

Re: [openstack-dev] [neutron] [QoS] QoS weekly meeting

Hi Miguel, Both time slots work for me. Thanks for rekindling this effort. Thanks, Sandhya From: Miguel Ángel Ajo mailto:[email protected]>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:[email protected]>> Date: Tuesday, April 7, 2015 1:45

[openstack-dev] BUG:Adding more tenants access to flavor with limited access causes already existing instance "size" in that tenant to "Not available" and this error pops up "Error: Unable to retrieve

-- Forwarded message -- From: mad Engineer Date: Tue, Apr 7, 2015 at 8:50 PM Subject: BUG:Adding more tenants access to flavor with limited access causes already existing instance "size" in that tenant to "Not available" and this error pops up "Error: Unable to retrieve instance si

[openstack-dev] I/O (PCIe) based NUMA scheduling

I understand that this feature automatically schedules the guest to be on a NUMA node to which the PCI device is associated. For a guest that spans multiple NUMA nodes, is the NUMA node information associated to PCI devices passed to the guest? Say a guest is configured to use 2 PCI devices(associ

[openstack-dev] [nova] [stringfreeze] request for SFE for live-migration on system z (review 166130)

I'd like to request a string freeze exception for this review: https://review.openstack.org/#/c/166130/ Justification: This fix would enable the live-migration on the system z platform. This platform (arch=s390x) doesn't currently support the CPU comparison but is working on patch sets in qe

[openstack-dev] [Manila] Question on documentation reviews

Hi guys, I have been reviewing https://review.openstack.org/#/c/171166/, but I am concerned that I provided more of a hindrance than assistance. Instead I would like to propose the method used by Swift for document reviews, where reviewers provide a patch to the author as in https://review.ope

[openstack-dev] Fixing the Nova Core Reviewer Frustration [was Re: [Nova] PTL Candidacy]

On Tue, 2015-04-07 at 11:27 +1000, Michael Still wrote: > Additionally, we have consistently asked for non-cores to help cover > the review load. It doesn't have to be a core that notices a problem > with a patch -- anyone can do that. There are many people who do help > out with non-core reviews,

Re: [openstack-dev] [nova] Host maintenance notification

On 4/6/2015 2:07 PM, Chris Friesen wrote: On 04/06/2015 12:52 PM, Matthew Treinish wrote: On Mon, Apr 06, 2015 at 01:17:20PM -0500, Matt Riedemann wrote: On 4/6/2015 9:46 AM, Chris Friesen wrote: On 04/06/2015 07:56 AM, Ed Leafe wrote: On Apr 6, 2015, at 1:21 AM, Chris Friesen wrote: Ple

Re: [openstack-dev] Barbican : Unable to reterieve asymmetric order request for rsa algorithm type

Hi All , I would like someone to provide the pointer so that I would look into this issue and confirm whether asymmetric order retrieval would be supported in Barbican. Any help would be appreciated! Thanks in advance, Asha Seshagiri On Fri, Apr 3, 2015 at 11:06 AM, Asha Seshagiri wrote: > Hi

[openstack-dev] [puppet] Meeting notes for April 7 and PTL update

Hi all, The minutes from today's meeting are here: http://eavesdrop.openstack.org/meetings/puppet_openstack/2015/puppet_openstack.2015-04-07-15.00.html One outcome of this meeting is that we plan to close the PTL nomination process on April 9, 2015 at 05:59 UTC. If you would like to nominate you

Re: [openstack-dev] [oslo.utils] allow strutils.mask_password to mask keys dynamically

On 03/20/2015 11:43 AM, Doug Hellmann wrote: > Excerpts from Matthew Van Dijk's message of 2015-03-20 15:06:08 +: >> I’ve come across a use case for allowing dynamic keys to be made >> secret. The hardcoded list is good for common keys, but there will be >> cases where masking a custom value is

Re: [openstack-dev] [Ironic] How to deal with microversions in 3rdparty tools

On 04/07/2015 07:25 AM, Dmitry Tantsur wrote: On 04/07/2015 03:15 PM, Jim Rollenhagen wrote: I’m not sure that recommending one or the other is best. We should lay out the options (as you just did) and let folks decide what works best for them. For things like discoverd, where you have many use

Re: [openstack-dev] Fixing the Nova Core Reviewer Frustration

On 04/07/2015 01:02 PM, James Bottomley wrote: > On Tue, 2015-04-07 at 11:27 +1000, Michael Still wrote: >> Additionally, we have consistently asked for non-cores to help cover >> the review load. It doesn't have to be a core that notices a problem >> with a patch -- anyone can do that. There are m

Re: [openstack-dev] Fixing the Nova Core Reviewer Frustration

On Tue, 2015-04-07 at 13:35 -0400, Anita Kuno wrote: > On 04/07/2015 01:02 PM, James Bottomley wrote: > > On Tue, 2015-04-07 at 11:27 +1000, Michael Still wrote: > >> Additionally, we have consistently asked for non-cores to help cover > >> the review load. It doesn't have to be a core that notices

Re: [openstack-dev] [all] how to send messages (and events) to our users

> This could be extended to richer JSON events that include the stack, > resources affected in the update, stats like "num-deleted-resources" or > "num-replaced-resources", autoscaling actions, and info about stack errors. > > Is there a way for users as-is to view those raw notifications, not just

Re: [openstack-dev] [Zaqar] PTL Candidacy

Hi all, Flavio, thanks for submitting your candidacy for Zaqar. As one of the developers working on the Zaqar project, I wanted to say that your guidance will be truly appreciated for the next cycle. The status for the project is really good, and there is a lot to do, great ideas for new features,

Re: [openstack-dev] Fixing the Nova Core Reviewer Frustration [was Re: [Nova] PTL Candidacy]

> -Original Message- > From: James Bottomley [mailto:[email protected]] > Sent: 07 April 2015 19:03 > To: Michael Still > Cc: OpenStack Development Mailing List (not for usage questions) > Subject: [openstack-dev] Fixing the Nova Core Reviewer Frustration [was Re: > [Nov

Re: [openstack-dev] The Evolution of core developer to maintainer?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 04/02/2015 02:26 PM, Joe Gordon wrote: > So, let me take a step back here. I would like to see at least 2 to > 3x more people in a given project to feel empowered and have > badges, and make it possible for part time upstream developers to > hold

[openstack-dev] Barbican : Unable to authenticate with keystone V3 for Barbican curl command

Hi All , Could anyone please help me on this integration issue. I am unable to authenticate with keystone V3 for Barbican curl command .I have followed the procedure given in the following link : https://github.com/cloudkeep/barbican/wiki/Integration-with-Keystone-V3-API I was unable to authent

Re: [openstack-dev] [all] how to send messages (and events) to our users

>Tooling in general seems to be moving towards richer event data as well. >The logging tools (Loggly/Logstash/PaperTrail/zillions of others) are >intended to take your unstructured logs and turn them into events, so >why not have Heat output structured events that we can present to the >user with

Re: [openstack-dev] Barbican : Unable to reterieve asymmetric order request for rsa algorithm type

Hello Asha, The root error here is that the stock plugin does not support generating 256 bit length asymmetric keys, rather only 1024, 2048 or 4096. Ideally you would have received a validation error when you POST-ed the order, but we have not yet integrated plugins with our validation process.

Re: [openstack-dev] Barbican : Unable to authenticate with keystone V3 for Barbican curl command

Hello Asha, We are in the process of migrating our documentation to Sphinx, so I'd suggest following this link for Keystone configuration options [1]. I'd also note that a CR is pending with a bit more details to setup via a Docker Keystone here [2]. Thanks, John [1] http://docs.openstack.o

Re: [openstack-dev] Barbican : Unable to authenticate with keystone V3 for Barbican curl command

Nothing stands out as obviously-wrong in your configuration, so I'd suggest starting with the following to debug: Enable debug mode in keystone.conf and watch the log files in both keystone and barbican (those produced by auth_token) and attempt your request against barbican again. Next, ensure t

Re: [openstack-dev] [all] how to send messages (and events) to our users

On 04/07/2015 11:34 AM, Sandy Walsh wrote: log({'message':"The %(foo)s did %(thing)s", 'foo':'x', 'thing':'action'}) I pity the foo that did that thing. -jay __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] Fixing the Nova Core Reviewer Frustration [was Re: [Nova] PTL Candidacy]

On Tue, 2015-04-07 at 18:12 +, Tim Bell wrote: > > -Original Message- > > From: James Bottomley [mailto:[email protected]] > > Sent: 07 April 2015 19:03 > > To: Michael Still > > Cc: OpenStack Development Mailing List (not for usage questions) > > Subject: [openstack

  1   2   >