[openstack-dev] [Neutron] - Vendor specific erros

Hi Some of the DB entities in the LBaaS domain inherit from HasStatusDescription With this we can set the entity status (ACTIVE, PENDING_CREATE,etc) and a description for the status. There are flows in the Radware LBaa

[openstack-dev] [Neutron] New plug-ins requirements

Team, It has been decided during the Icehouse summit that all vendor specific plug-ins should enforce remote tempest tests: http://ci.openstack.org/third_party.html I would like to understand if we will apply this rule for any new plug-in during Icehouse or we will start applying this new require

Re: [openstack-dev] [Neutron]Good example of dev doc/docstrings in code.

Hi Anita, Is this an area where a new developer can help out? I've got a little time to spare (not a whole lot, best-effort...) and would like to help out. I'm very new to all of this though. I figure that documenting code is a good way to contribute and learn at the same time. Could anyone po

Re: [openstack-dev] Bad review patterns

On 11/11/13 23:35, Mark McLoughlin wrote: [...] > I make a habit of leaving comments in reviews - positive, negative, > neutral, whatever. If I have something to say which might be useful to > the author, other reviewers, my future self, whatever ... then I'll say > it. > > e.g. if I spend 10 mi

Re: [openstack-dev] [Horizon] Introduction of AngularJS in membership workflow

+1000 Excellent I am really excited about having a heavily tested proper client-side layer. This is very needed, given that amount of javascript in Horizon is rising. The hacked together libraries in JQuery, that are there now are very hard to orient in and will be hard to maintain in the fut

Re: [openstack-dev] Bad review patterns

On Fri, Nov 8, 2013 at 4:07 AM, Pedro Roque Marques < pedro.r.marq...@gmail.com> wrote: > Radomir, > An extra issue that i don't believe you've covered so far is about comment > ownership. I've just read an email on the list that follows a pattern that > i've heard many complaints about: >

Re: [openstack-dev] [Neutron] New plug-ins requirements

On 12 November 2013 21:15, Edgar Magana wrote: > Team, > > It has been decided during the Icehouse summit that all vendor specific > plug-ins should enforce remote tempest tests: > http://ci.openstack.org/third_party.html > > I would like to understand if we will apply this rule for any new plug-i

Re: [openstack-dev] [qa] Policy on spelling and grammar

On 11/11/13 20:47, Christopher Armstrong wrote: [...] > It would be so much nicer if there were some easy way for the reviewer > himself to fix the typos directly (in a way that can trivially be > accepted by the submitter of the patch into his own patch -- with a > click of a button). Well, you c

Re: [openstack-dev] [qa] Policy on spelling and grammar

On Mon 11 Nov 2013 (19:28), Tim Bell wrote: > > As a speaker of the Queen's English, I find flavor to be incorrect. > Does that mean I can -1 any patch that does not use flavour ? > > At CERN, we are working with 130 countries in a single community. > The value of the contribution of non-english

Re: [openstack-dev] [qa] Policy on spelling and grammar

Excerpts from Radomir Dopieralski's message of 2013-11-12 00:53:40 -0800: > On 11/11/13 20:47, Christopher Armstrong wrote: > [...] > > It would be so much nicer if there were some easy way for the reviewer > > himself to fix the typos directly (in a way that can trivially be > > accepted by the su

Re: [openstack-dev] revocation and duration times

I dont see how the account paymaster can tell when a user from an IDP has been revoked or had his privileges curtailed, but if he can, then cutting off the account is simply another type of revocation message. Whether revocation comes directly from the IDP or from the account paymaster is irrel

Re: [openstack-dev] Proposal to recognize indirect contributions to our code base

Nicolas Barcet wrote: > [...] > To enable this, we are proposing that the commit text of a patch may > include a >sponsored-by: > line which could be used by various tools to report on these commits. > [...] This proposal raises several questions. (1) Is it a good idea to allow giving cred

Re: [openstack-dev] [oslo][heat] oslo.db session and model_query()

Hi Steven, Thanks for pointing this out! Yep, those docs must be a hangover from moving this code from Nova. I'm really surprised, that we don't have model_query() in Oslo DB code. I think, we should provide a reference implementation of this function, which will be very similar to the one, which

Re: [openstack-dev] When is it okay for submitters to say 'I don't want to add tests' ?

+1 also. I spent less than half the time on my first fix (so far) understanding the problem, reproducing it, coding it and learning about the code review system. Much more than half the time was spent on reverse engineering existing tests to be able to add new ones (which had to use features not u

Re: [openstack-dev] When is it okay for submitters to say 'I don't want to add tests' ?

To be clear, that was a +1 for Mark's suggestion: > In cases like that, I'd be of a mind to go "+2 Awesome! Thanks for > catching this! It would be great to have a unit test for this, but it's > clear the current code is broken so I'm fine with merging the fix > without a test". You could say it's

Re: [openstack-dev] [Nova] Recent change breaks manual control of service enabled / disabled status - suggest it is backed out and re-worked

On Mon, Nov 11, 2013 at 11:34:10AM +, Day, Phil wrote: > Hi Folks, > > I'd like to get some eyes on a bug I just filed: > https://bugs.launchpad.net/nova/+bug/1250049 > > A recent change (https://review.openstack.org/#/c/52189/9 ) introduced the > automatic disable / re-enable of nova-comp

Re: [openstack-dev] [openstack][metering] Contributing to ceilometer while participating in GSoC

Hi Ajay, "Ajay Phogat" wrote: > Hello, all! > > I am a student of Computer Science and have learnt some basics of OpenStack > for implementing one of my projects in college. While learning about > OpenStack, I came to know about the metering project, ceilometer. > > I would love to contribute t

Re: [openstack-dev] Horizon PTL candidacy

> On 11/10/2013 11:53 PM, John Dickinson wrote: > > A random off-the-top-of-my-head use case would be to subscribe to > > events from creating or changing objects in a particular Swift > > account or container. This would allow much more efficient listings > > in Horizon for active containers (an

Re: [openstack-dev] Horizon PTL candidacy

On 11/12/2013 12:09 PM, Eoghan Glynn wrote: > Sounds reasonable, but just one caveat ... > > Notifications can either be disabled in the service config (e.g. by setting > the notifier_strategy to noop in the glance config) or mis-configured (e.g. > by not overriding control_exchange name in the ci

Re: [openstack-dev] [Mistral] really simple workflow for Heat configuration tasks

Hi Angus, that is an interesting idea. Since you mentioned the software config proposal in the beginning as a related item, I guess you are trying to solve some software config related issues with Mistral. So a few questions, looking at this purely from a software config perspect: Are you thinkin

Re: [openstack-dev] [Neutron]Good example of dev doc/docstrings in code.

Welcome Joris! I would enjoy helping you get started contributing to OpenStack. Are you on IRC yet? Talking on IRC is our most efficient means of communication. On the Freenode network I suggest joining #openstack, #openstack-dev, #openstack-101, #openstack-meeting, #openstack-meeting-alt as w

[openstack-dev] Future of Project/release meetings, and skipping today's one

Hi everyone, We'll be skipping the project/release status meeting today (usually happening at 21:00 UTC). Most PTLs are just back from the Design Summit week and catching up, and some are still in vacation, so there is little point in having one today. For this week they should work on filing, pri

Re: [openstack-dev] sqlalchemy-migrate needs a new release

I don't know what's all involved in putting out a release for sqlalchemy-migrate but if there is a way that I can help, please let me know. I'll try to catch dripton in IRC today. As for CI with DB2, it's in the blueprint as a work item, I just don't know enough about the infra side of things

Re: [openstack-dev] [Heat] Do we need to clean up resource_id after deletion?

On 02/11/13 05:30, Clint Byrum wrote: Excerpts from Christopher Armstrong's message of 2013-11-01 11:34:56 -0700: Vijendar and I are trying to figure out if we need to set the resource_id of a resource to None when it's being deleted. This is done in a few resources, but not everywhere. To me i

Re: [openstack-dev] [Mistral] really simple workflow for Heat configuration tasks

On 12 нояб. 2013 г., at 19:04, Thomas Spatzier wrote: > If yes, is there a way for passing data around - e.g. output produced by > one software config step is input for another software config step? Thomas, yes, we’re planning to have a data flow mechanism similar to what you described here.

Re: [openstack-dev] [Heat] HOT software configuration refined after design summit discussions

+1 This new proposal [1] looks like a very positive change on top of [2]. Simpler both to read and write. One minor suggestion is to consider using a special character (eg $) rather than reserved keywords. As I understand it the keywords are only interpreted when they exactly match the va

Re: [openstack-dev] [Nova] Recent change breaks manual control of service enabled / disabled status - suggest it is backed out and re-worked

I'll work on Daniel's suggestion and will send a patch for review. Vladik - Original Message - > From: "Daniel P. Berrange" > To: "OpenStack Development Mailing List (not for usage questions)" > > Sent: Tuesday, 12 November, 2013 5:32:28 AM > Subject: Re: [openstack-dev] [Nova] Recent

Re: [openstack-dev] [Trove][Savanna][Murano] Unified Agent proposal discussion at Summit

Just to summarize, there was an interest expressed from Murano, Trove, Savanna and Heat teams in regards with implementation of this unified agent. Nothing specific was decided expect suggestion to keep pushing. I'd suggest to keep pushing this way: - create an etherpad - each team interested in h

Re: [openstack-dev] [nova] Do we have some guidelines for mock, stub, mox when writing unit test?

On 11 November 2013 23:18, Mark McLoughlin wrote: > On Mon, 2013-11-11 at 12:07 +, John Garbutt wrote: >> On 11 November 2013 10:27, Rosa, Andrea (HP Cloud Services) >> wrote: >> > Hi >> > >> >>Generally mock is supposed to be used over mox now for python 3 support. >> > >> > That is my under

Re: [openstack-dev] [Nova] Configuration validation

On 11 November 2013 22:12, Joe Gordon wrote: > On Nov 11, 2013 9:53 AM, "Russell Bryant" wrote: >> On 11/11/2013 07:38 AM, Nikola Đipanov wrote: >> > On 11/11/13 12:55, John Garbutt wrote: >> >> I like the idea of a more general config validation phase to help >> >> people when first starting out

Re: [openstack-dev] [nova] Configure overcommit policy

On 11 November 2013 12:04, Alexander Kuznetsov wrote: > Hi all, > > While studying Hadoop performance in a virtual environment, I found an > interesting problem with Nova scheduling. In OpenStack cluster, we have > overcommit policy, allowing to put on one compute more vms than resources > availab

[openstack-dev] [Nova] Summary of Design Summit Session

Hi, I am attempting to extract the consensus we reached in all the design summit sessions here: https://etherpad.openstack.org/p/IcehouseNovaSummit Help to verify that I have not miss-represented things would be very gratefully received. John ___ Open

Re: [openstack-dev] [nova] Configure overcommit policy

You can consider having a separate host aggregate for Hadoop, and use a combination of AggregateInstanceExtraSpecFilter (with a special flavor mapped to this host aggregate) and AggregateCoreFilter (overriding cpu_allocation_ratio for this host aggregate to be 1). Regards, Alex From: John

Re: [openstack-dev] [Trove][Savanna][Murano] Unified Agent proposal discussion at Summit

Thinking in that direction, the Trove team had a design session about current status of agent in project. Just take a look https://etherpad.openstack.org/p/TroveGuestAgents With best regards, Ilya Sviridov On Tue, Nov 12, 2013 at 4:29 PM, Igor Marnat wrote: > Just

Re: [openstack-dev] [Neutron] IPv6 sub-team?

Thanks, Sean! I am on east coast, so Monday 20:00 UTC time and Thursday 21:00 UTC time work great for me. Hopefully we can find a timeslot working for everybody! Shixiong On Nov 11, 2013, at 1:23 PM, Collins, Sean (Contractor) wrote: > On Mon, Nov 11, 2013 at 01:16:43PM -0500, Shixiong Shan

Re: [openstack-dev] [Trove][Savanna][Murano] Unified Agent proposal discussion at Summit

Ilya, that's cool! Mind if Murano and Savanna teams join the same etherpad? Regards, Igor Marnat On Tue, Nov 12, 2013 at 6:58 PM, Ilya Sviridov wrote: > Thinking in that direction, the Trove team had a design session about > current status of agent in project. > > Just take a look https://ethe

[openstack-dev] [Neutron][LBaaS] LBaaS Subteam meeting

Hi neutron and lbaas folks! We have a plenty of work to do for the Icehouse, so I suggest we start having regular weekly meetings to track our progress. Let's meet at #neutron-lbaas on Thursday, 14 at 15-00 UTC The agenda for the meeting is the following: 1. Blueprint list to be proposed for the

[openstack-dev] Solum Weekly Meeting

Hello, Solum meets Tuesdays at 1600 UTC in #openstack-meeting-alt (formerly in #solum) Note: Due to the Nov 3rd change in Daylight Savings Time, this now happens at 08:00 US/Pacific (starts in about 50 minutes from now) Agenda: https://wiki.openstack.org/wiki/Meetings/Solum Regards, Adrian _

Re: [openstack-dev] [Neutron] New plug-ins requirements

On Nov 12, 2013, at 2:46 AM, Robert Collins wrote: > On 12 November 2013 21:15, Edgar Magana wrote: >> Team, >> >> It has been decided during the Icehouse summit that all vendor specific >> plug-ins should enforce remote tempest tests: >> http://ci.openstack.org/third_party.html >> >> I would l

[openstack-dev] [Solum] Weekly Team Meeting

Hello, Solum meets Tuesdays at 1600 UTC in #openstack-meeting-alt (formerly in #solum) Note: Due to the Nov 3rd change in Daylight Savings Time, this now happens at 08:00 US/Pacific (starts in about 45 minutes from now) Agenda: https://wiki.openstack.org/wiki/Meetings/Solum Regards, Adrian __

Re: [openstack-dev] [nova] Configure overcommit policy

FYI, by default Openstack overcommit CPU 1:16, meaning it can host 16 times number of cores it possesses. As mentioned Alex, you can change it by enabling AggregateCoreFilter in nova.conf: scheduler_default_filters = and modifying the overcommit ratio by adding: cpu_allocation_ratio=1.0 Ju

[openstack-dev] [Oslo] Using of oslo.config options in openstack.common modules

Hi all, Currently, many modules from openstack.common package register oslo.config options. And this is completely OK while these modules are copied to target projects using update.py script. But consider the situation, when we decide to split a new library from oslo-incubator - oslo.spam - and t

Re: [openstack-dev] [Neutron][LBaaS] LBaaS Subteam meeting

Hi Eugene, In my opinion, it is better the LBaaS meeting is held on #openstack-meeting or #openstack-meeting-alt as most OpenStack projects do. In addition, information on https://wiki.openstack.org/wiki/Meetings#LBaaS_meeting is not up-to-date. The time is 1400UTC and the channel is #openstack-m

Re: [openstack-dev] [Trove][Savanna][Murano] Unified Agent proposal discussion at Summit

Igor, better to create another one to track the requirements for such agent framework as far as this etherpad is official result of design session. With best regards, Ilya Sviridov On Tue, Nov 12, 2013 at 5:02 PM, Igor Marnat wrote: > Ilya, > that's cool! Mind if Mur

[openstack-dev] [Scheduler] Meeting

Hi, I am sorry but my calendar was a mess – daylight saving changes etc. So I did not make it to the meeting. Hopefully we can pick up next week and follow up on what was discussed at the summit. So humble apologies for not running the meeting this week and see you guys next week. Thanks Gary __

Re: [openstack-dev] [Neutron][LBaaS] LBaaS Subteam meeting

I agree that it would be better to hold it on a channel with a bot which keeps logs. I just found that most convenient slots are already taken on both openstack-meeting and openstack-meeting-alt. 14-00 UTC is convenient for me so I'd like to hear other opinions. Thanks, Eugene. On Tue, Nov 12

Re: [openstack-dev] Improvement of Cinder API wrt https://bugs.launchpad.net/nova/+bug/1213953

I'd like to get some sort of consensus on this before I start working on it. Now that people are back from Summit, what would you propose? Best Regards, Solly Ross - Original Message - From: "Solly Ross" To: "OpenStack Development Mailing List (not for usage questions)" Sent: Tuesday

Re: [openstack-dev] Improvement of Cinder API wrt https://bugs.launchpad.net/nova/+bug/1213953

On Tue, Nov 12, 2013 at 8:46 AM, Solly Ross wrote: > I'd like to get some sort of consensus on this before I start working on it. > Now that people are back from Summit, what would you propose? > > Best Regards, > Solly Ross > > - Original Message - > From: "Solly Ross" > To: "OpenStack

Re: [openstack-dev] [openstack-tc] Proposal to recognize indirect contributions to our code base

On Mon, Nov 11, 2013 at 6:56 PM, Sean Dague wrote: > On 11/11/2013 06:47 PM, John Griffith wrote: > > On Mon, Nov 11, 2013 at 10:44 AM, Daniel P. Berrange > > >> IMHO, lets call this what it is: "marketing". > >> > >> I'm fine with the idea of a company wanting to have recognition for work > >>

Re: [openstack-dev] [Heat] HOT software configuration refined after design summit discussions

On Tue, Nov 12, 2013 at 01:59:35PM +, Alex Heneveld wrote: > This new proposal [1] looks like a very positive change on top of > [2]. Simpler both to read and write. Agreed, thanks Thomas for taking the time to write this up, it looks like a good reflection of what was discussed last week to

Re: [openstack-dev] [Heat] HOT software configuration refined after design summit discussions

On 12/11/13 14:59, Alex Heneveld wrote: One minor suggestion is to consider using a special character (eg $) rather than reserved keywords. As I understand it the keywords are only interpreted when they exactly match the value of a key in a map, so it is already unlikely to be problematic. Howe

Re: [openstack-dev] [Heat] HOT software configuration refined after design summit discussions

Zane Bitter wrote on 11/12/2013 12:06:14 PM: > ... However, if > for any reason you have a dict key starting with "$" and we interpret > that specially, then you are basically hosed since you almost certainly > _needed_ it to actually start with "$" for a reason. So -1. > > cheers, > Zane. Y

Re: [openstack-dev] Improvement of Cinder API wrt https://bugs.launchpad.net/nova/+bug/1213953

On 11/12/2013 8:09 AM, John Griffith wrote: On Tue, Nov 12, 2013 at 8:46 AM, Solly Ross wrote: I'd like to get some sort of consensus on this before I start working on it. Now that people are back from Summit, what would you propose? Best Regards, Solly Ross - Original Message - Fro

[openstack-dev] [nova] [heat] Custom Flavor creation through Heat

Hi, In Telecom Cloud applications, the requirements for every application are different. One application might need 10 CPUs, 10GB RAM and no disk. Another application might need 1 CPU, 512MB RAM and 100GB Disk. This varied requirements directly affects the flavors which need to be created for

Re: [openstack-dev] [Heat] HOT software configuration refined after design summit discussions

Thanks Steve, Zane, Mike. I withdraw the $idea ... for now (*). As a user who wants to move away from fiddling with infrastructure I like where this is going. :) --A (*) If there start to be lots of get_param usages and other keywords then perhaps $this -- and requiring $$ escapes -- or

Re: [openstack-dev] [Heat] Do we need to clean up resource_id after deletion?

On Tue, Nov 12, 2013 at 7:47 AM, Zane Bitter wrote: > On 02/11/13 05:30, Clint Byrum wrote: > >> Excerpts from Christopher Armstrong's message of 2013-11-01 11:34:56 >> -0700: >> >>> Vijendar and I are trying to figure out if we need to set the resource_id >>> of a resource to None when it's bein

[openstack-dev] [qa] moratorium on new negative tests in Tempest

During the freeze phase of Havana we got a ton of new contributors coming on board to Tempest, which was super cool. However it meant we had this new influx of negative tests (i.e. tests which push invalid parameters looking for error codes) which made us realize that human creation and review of n

Re: [openstack-dev] [Nova] Configuration validation

Thanks folks for the interesting suggestions on this topic! I’ll b updating the BP this week with this and other info i am gathering. Please let me know if you are interested in being involved in brainstorming on this issue and I will set up an irc meeting to discuss it further On Nov 11, 201

Re: [openstack-dev] [Neutron] IPv6 sub-team?

As an IPv6 engineer interesting in helping Neutron get where it could be, I'd like to join in on this. I also like the Thursday 21:00 UTC slot. -Anthony -Original Message- From: Shixiong Shang Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Tuesday, Novem

Re: [openstack-dev] [Heat] HOT software configuration refined after design summit discussions

Excerpts from Thomas Spatzier's message of 2013-11-11 08:57:58 -0800: > > Hi all, > > I have just posted the following wiki page to reflect a refined proposal > for HOT software configuration based on discussions at the design summit > last week. Angus also put a sample up in an etherpad last wee

Re: [openstack-dev] [qa] moratorium on new negative tests in Tempest

Excerpts from Sean Dague's message of 2013-11-12 10:01:06 -0800: > During the freeze phase of Havana we got a ton of new contributors > coming on board to Tempest, which was super cool. However it meant we > had this new influx of negative tests (i.e. tests which push invalid > parameters looking f

Re: [openstack-dev] Improvement of Cinder API wrt https://bugs.launchpad.net/nova/+bug/1213953

On Tue, Nov 12, 2013 at 10:25 AM, Caitlin Bestler wrote: > On 11/12/2013 8:09 AM, John Griffith wrote: >> >> On Tue, Nov 12, 2013 at 8:46 AM, Solly Ross wrote: >>> >>> I'd like to get some sort of consensus on this before I start working on >>> it. Now that people are back from Summit, what woul

Re: [openstack-dev] [nova] [heat] Custom Flavor creation through Heat

On 11/12/2013 10:25 AM, Kodam, Vijayakumar (EXT-Tata Consultancy Ser - FI/Espoo) wrote: Hi, In Telecom Cloud applications, the requirements for every application are different. One application might need 10 CPUs, 10GB RAM and no disk. Another application might need 1 CPU, 512MB RAM and 100GB D

Re: [openstack-dev] [Nova] Configuration validation

Mark - does Oslo.config already do any duplicate config checking? If not that’s probably a good place for that part On Nov 12, 2013, at 10:06 AM, Tracy Jones wrote: > Thanks folks for the interesting suggestions on this topic! I’ll b updating > the BP this week with this and other info i am

[openstack-dev] [Ceilometer][qa]Tempest tests for Ceilometer

Hello, guys! I hope everybody has eventually got home after the summit and feeling ok :) So it's time to proceed thinking about integration, unit and performance testing in Ceilometer. First of all I'd like to appreciate your help in composing etherpad https://etherpad.openstack.org/p/icehouse-sum

[openstack-dev] Token Revocation using hash of token id

During the token revocation discussion at the summit, I suggested it would be possible to revoke tokens using a hash of the token id (which is already an MD5 hash). That way, the revocation file would be able to specify individual hashes for revocation without dangerously presenting secrets. I sho

Re: [openstack-dev] [Neutron][LBaaS] LBaaS Subteam meeting

> On Nov 12, 2013, at 10:27 AM, Akihiro Motoki wrote: > > Hi Eugene, > > In my opinion, it is better the LBaaS meeting is held on > #openstack-meeting or #openstack-meeting-alt > as most OpenStack projects do. > > ++ Holding sub team meetings in standard meeting channels is a must for build

Re: [openstack-dev] [Neutron][LBaaS] LBaaS Subteam meeting

Hi Eugene, LBaaS meeting on #openstack-meeting was previously schedule on Thursdays 1400UTC. And indeed it is still listed on https://wiki.openstack.org/wiki/Meetings as such, so I believe keeping it in that timeslot should be fine. - Stephen On Tue, Nov 12, 2013 at 7:40 AM, Eugene Nikanoro

[openstack-dev] [Savanna] Definition of template

Hi all, I want to raise the question "What template is". Answer to this question could influence UI, validation and user experience significantly. I see two possible answers: 1. Template is a simplification for object creation. It allows to keep common params in one place and not specify them each

Re: [openstack-dev] [Neutron][LBaaS] LBaaS Subteam meeting

Ok, I'll repost date and time to openstack-dev again. Thanks, Eugene. On Tue, Nov 12, 2013 at 11:15 PM, Stephen Wong wrote: > Hi Eugene, > > LBaaS meeting on #openstack-meeting was previously schedule on > Thursdays 1400UTC. And indeed it is still listed on > https://wiki.openstack.org/wik

Re: [openstack-dev] [nova] [heat] Custom Flavor creation through Heat

Excerpts from Kodam, Vijayakumar (EXT-Tata Consultancy Ser - FI/Espoo)'s message of 2013-11-12 09:25:19 -0800: > Hi, > > In Telecom Cloud applications, the requirements for every application are > different. One application might need 10 CPUs, 10GB RAM and no disk. Another > application might n

Re: [openstack-dev] New Pycharm License

Andrew, I'd like to try out PyCharms Pro. Can I get a license (I'm an ATC for Neutron area). Thanks! PCM (Paul Michali) MAIL p...@cisco.com IRC pcm_ (irc.freenode.net) TW @pmichali signature.asc Description: Message signed with OpenPGP using GPGMail ___

Re: [openstack-dev] [nova] [heat] Custom Flavor creation through Heat

On 11/13/2013 07:50 AM, Steven Dake wrote: > On 11/12/2013 10:25 AM, Kodam, Vijayakumar (EXT-Tata Consultancy Ser - > FI/Espoo) wrote: >> Hi, >> >> In Telecom Cloud applications, the requirements for every application >> are different. One application might need 10 CPUs, 10GB RAM and no >> disk. An

[openstack-dev] [Neutron][LBaaS] LBaaS subteam meeting Thursday, 14, at 14-00 UTC

Hi folks, LBaaS subteam meeting will be held on Thursday, 14 at 14-00 UTC on #openstack-meeting irc channel on freenode, as specified in https://wiki.openstack.org/wiki/Meetings#LBaaS_meeting The agenda is the following: 1. Blueprint list to be proposed for the icehouse-1 2. QA & third-party test

Re: [openstack-dev] [qa] moratorium on new negative tests in Tempest

On 11/12/2013 01:36 PM, Clint Byrum wrote: Excerpts from Sean Dague's message of 2013-11-12 10:01:06 -0800: During the freeze phase of Havana we got a ton of new contributors coming on board to Tempest, which was super cool. However it meant we had this new influx of negative tests (i.e. tests w

[openstack-dev] Code Review (Jenkins-job-builder, BlameUpstreamCommitters plugin support)

Hi, Could someone review this please: https://review.openstack.org/#/c/54085/ Regards, Peter ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Token Revocation using hash of token id

Relevant etherpad - https://etherpad.openstack.org/p/icehouse-token-revocation In the etherpad, we reverted the example for "explicit token revocation called on a single token" to use "expires_at" as the identifier for the event (rather than a hash of the token). Because rescoping tokens maintains

Re: [openstack-dev] Token Revocation using hash of token id

On Tue, Nov 12, 2013 at 2:47 PM, Dolph Mathews wrote: > Relevant etherpad - > https://etherpad.openstack.org/p/icehouse-token-revocation Thank you. I had presumed the etherpad was out of date as the discussion at the summit centered around what appeared to be a text editor (vim or emacs), rather

[openstack-dev] [TRIPLEO] meeting minutes

-- http://eavesdrop.openstack.org/meetings/tripleo/2013/tripleo.2013-11-12-19.00.html -- http://eavesdrop.openstack.org/meetings/tripleo/2013/tripleo.2013-11-12-19.00.log.html Cheers, rob Robert Collins Distinguished Technologist HP Converged Cloud

[openstack-dev] [infra] Meeting Tuesday November 12th at 19:00 UTC minutes and logs

The OpenStack Infrastructure (Infra) team hosted our weekly meeting today, Tuesday November 12th, at 19:00 UTC in #openstack-meeting Meeting minutes and logs here: Minutes: http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-11-12-19.03.html Minutes (text): http://eavesdrop.openstack.o

Re: [openstack-dev] [nova][api] Is this a potential issue

On 11/11/13 at 05:27pm, Jiang, Yunhong wrote: Resend after the HK summit, hope someone can give me hint on it. Thanks --jyh -Original Message- From: Jiang, Yunhong [mailto:yunhong.ji...@intel.com] Sent: Thursday, November 07, 2013 5:39 PM To: openstack-dev@lists.openstack.org Subject:

Re: [openstack-dev] Code Review (Jenkins-job-builder, BlameUpstreamCommitters plugin support)

Please read http://lists.openstack.org/pipermail/openstack-dev/2013-September/015264.html On Tue, Nov 12, 2013 at 11:35 AM, Peter Liljenberg wrote: > Hi, > > Could someone review this please: > > https://review.openstack.org/#/c/54085/ > > Regards, > Peter > > ___

Re: [openstack-dev] [qa] moratorium on new negative tests in Tempest

On 11/12/2013 02:33 PM, David Kranz wrote: > On 11/12/2013 01:36 PM, Clint Byrum wrote: >> Excerpts from Sean Dague's message of 2013-11-12 10:01:06 -0800: >>> During the freeze phase of Havana we got a ton of new contributors >>> coming on board to Tempest, which was super cool. However it meant

Re: [openstack-dev] Token Revocation using hash of token id

On Tue, Nov 12, 2013 at 1:57 PM, Eric Windisch wrote: > On Tue, Nov 12, 2013 at 2:47 PM, Dolph Mathews > wrote: > > Relevant etherpad - > > https://etherpad.openstack.org/p/icehouse-token-revocation > > Thank you. I had presumed the etherpad was out of date as the > discussion at the summit cente

Re: [openstack-dev] [Heat] HOT software configuration refined after design summit discussions

On Tue, Nov 12, 2013 at 10:32 AM, Clint Byrum wrote: > Excerpts from Thomas Spatzier's message of 2013-11-11 08:57:58 -0800: > > > > Hi all, > > > > I have just posted the following wiki page to reflect a refined proposal > > for HOT software configuration based on discussions at the design summi

Re: [openstack-dev] [Heat] HOT software configuration refined after design summit discussions

Hi, I agree with Clint that component placement specified inside component configuration is not a right thing. I remember that mostly everyone agreed that "hosted_on" should not be in HOT templates. When one specify placement explicitly inside a component definition it prevents the following: 1.

Re: [openstack-dev] [Nova] [Climate] Reservation service called Climate

On 11/06/13 at 09:47am, Sylvain Bauza wrote: Hi, During the Design session https://etherpad.openstack.org/p/NovaIcehouse-Instance-Group-API we discussed the fact that this is not the role of Nova for doing atomic reservations in order to ensure the user needs will be met. We discussed that

Re: [openstack-dev] [nova] [heat] Custom Flavor creation through Heat

On 11/12/2013 11:50 AM, Steven Dake wrote: On 11/12/2013 10:25 AM, Kodam, Vijayakumar (EXT-Tata Consultancy Ser - FI/Espoo) wrote: Hi, In Telecom Cloud applications, the requirements for every application are different. One application might need 10 CPUs, 10GB RAM and no disk. Another applica

[openstack-dev] Motion - Amend TC charter language to reflect Gender Parity

Currently some of the language found in the TC charter does not yet reflect gender parity[0]. I encountered this myself while officiating the TC election, particularly the section on Candidates for PTL seats[1]. I move that the language of the TC charter reflect gender parity. [0] https://w

Re: [openstack-dev] [nova] [heat] Custom Flavor creation through Heat

My concern with proliferating custom flavors is that it might play havoc with the underlying root-case for flavors. My understanding of flavors is that they are used to solve the resource packing problem in elastic cloud scenarios. That way you know that 256 "tiny" VMs fit cleanly into your har

Re: [openstack-dev] Improvement of Cinder API wrt https://bugs.launchpad.net/nova/+bug/1213953

On 11/12/2013 10:42 AM, John Griffith wrote: Sorry, but I'm not seeing where you're going with this in relation to the question being asked? The question is how to deal with creating a new bootable volume from nova boot command and be able to tell whether it's timed out, or errored while waiti

Re: [openstack-dev] [Nova] Configuration validation

Gary, Nikola, The diagnostics service being developed by our labs could be of interest for you [1] The first use case we're working on is exactly what you suggest: validation of configuration parameters across services before running them [2] We now use a mix of approaches: 1. introduce extended

Re: [openstack-dev] Future of Project/release meetings, and skipping today's one

Thierry- Would it be possible to use [PTL] as the subject prefix for these messages? It should make it easier for everyone to tag/filter them. mark On Nov 12, 2013, at 7:57 AM, Thierry Carrez wrote: > Hi everyone, > > We'll be skipping the project/release status meeting today (usually > hap

Re: [openstack-dev] [nova] Do we have some guidelines for mock, stub, mox when writing unit test?

Maybe we should have some 60% rule... that is: If you change more than half of a test... you should *probably* rewrite the test in Mock. # Shawn Hartsock - Original Message - > From: "John Garbutt" > To: "Mark McLoughlin" , "OpenStack Development Mailing > List (not for usage question

Re: [openstack-dev] [Nova] Configuration validation

Is there anything preventing these techniques from being included in a library that could be re-used between a stand-alone tool or a service init-hook? # Shawn Hartsock - Original Message - > From: "Oleg Gelbukh" > To: "OpenStack Development Mailing List (not for usage questions)" >

Re: [openstack-dev] [nova] Do we have some guidelines for mock, stub, mox when writing unit test?

On Tue, 2013-11-12 at 13:11 -0800, Shawn Hartsock wrote: > Maybe we should have some 60% rule... that is: If you change more than > half of a test... you should *probably* rewrite the test in Mock. A rule needs a reasoning attached to it :) Why do we want people to use mock? Is it really for Pyt

Re: [openstack-dev] [nova] Do we have some guidelines for mock, stub, mox when writing unit test?

Good point. I assume someone made a comparison similar to this: * http://garybernhardt.github.io/python-mock-comparison/ ... and evangelized a choice. I had assumed that Mock vs mox was not merely based on Python3 support but had something to do with Mock versus Mox. Does anyone have that conte

Re: [openstack-dev] Motion - Amend TC charter language to reflect Gender Parity

Hi Anita, On Tue, 2013-11-12 at 15:50 -0500, Anita Kuno wrote: > Currently some of the language found in the TC charter does not yet > reflect gender parity[0]. > > I encountered this myself while officiating the TC election, > particularly the section on Candidates for PTL seats[1]. > > I mov

[openstack-dev] [Glance] Meeting Reminder Thursday at 2000 UTC

Hi folks, We'll have a Glance team meeting this Thursday at 2000 UTC (don't forget that UTC applies to both the time and the date!). In your timezone that is http://www.timeanddate.com/worldclock/fixedtime.html?msg=Glance+Meeting&iso=20131114T20&ah=1. As usual the meeting room is #openstack-meeti

Re: [openstack-dev] [nova] Do we have some guidelines for mock, stub, mox when writing unit test?

Hi On Tue, Nov 12, 2013 at 4:24 PM, Mark McLoughlin wrote: > On Tue, 2013-11-12 at 13:11 -0800, Shawn Hartsock wrote: > > Maybe we should have some 60% rule... that is: If you change more than > > half of a test... you should *probably* rewrite the test in Mock. > > A rule needs a reasoning atta

  1   2   >