[openstack-dev] [nova] unit tests method

Hi There are 3 types of unit test existing now (stub, mox and mock) Several code reviewers suggest to use mock instead of using the other 2 and I am following it, but I want to know where can I find the suggestion and guide line? Thanks Best Regard

Re: [openstack-dev] TC candidacy

confirmed On 04/16/2014 04:53 AM, Joe Gordon wrote: > Hi All, > > I'd like to announce my candidacy for the Technical Committee election. > > About Me > -- > > I work full time on OpenStack on behalf of HP. And am part of nova-core, > nova-specs-core, hacking-core and elastic-rechec

Re: [openstack-dev] [neutron] Neutron Mid-Cycle Meeting

Great initiative. I added my name and also which location will work better, I would suggest all developers interested on this meeting to do the same. Edgar On 4/15/14, 6:54 PM, "Kyle Mestery" wrote: >Folks: > >Given all the talk of mid-cycle meetings, I'd like to propose that we >do one for Neu

[openstack-dev] [Openstack] About advice for Contribution

Howdy All, I need a small advice. I am working from last two years on Eucalyptus. Recently, switched to Openstack and trying to contribute to Code-Base. My skills are: *- I have good understanding of private Cloud* *- Total beginner in Python but somewhat good at Java*

Re: [openstack-dev] [neutron] Neutron Mid-Cycle Meeting

Yeah! Let¹s do it in Barcelona, maybe Midokura can host it. :-) Edgar On 4/15/14, 11:12 PM, "Gary Kotton" wrote: >Hi, >Any chance of doing this in Europe? >Thanks >Gary > >On 4/16/14 4:54 AM, "Kyle Mestery" wrote: > >>Folks: >> >>Given all the talk of mid-cycle meetings, I'd like to propose t

Re: [openstack-dev] [TripleO][design] review based conceptual design process

On 2014/15/04 23:15, James Slagle wrote: On Tue, Apr 15, 2014 at 2:44 PM, Robert Collins wrote: I've been watching the nova process, and I think its working out well - it certainly addresses: - making design work visible - being able to tell who has had input - and providing clear feedba

Re: [openstack-dev] [TripleO][design] review based conceptual design process

On 15/04/14 21:54, Ben Nemec wrote: > On 04/15/2014 01:44 PM, Robert Collins wrote: >> I've been watching the nova process, and I think its working out well >> - it certainly addresses: >> - making design work visible >> - being able to tell who has had input >> - and providing clear feedback

Re: [openstack-dev] [neutron] Neutron BP review process for Juno

On 16/04/14 00:07, Kyle Mestery wrote: > Given the success the Nova team has had in handling reviews using > their new nova-specs gerrit repository, I think it makes a lot of > sense for Neutron to do the same. With this in mind, I've added > instructions to the BP wiki [1] for how to do. Going for

Re: [openstack-dev] [TripleO][design] review based conceptual design process

On 15/04/14 20:44, Robert Collins wrote: > I've been watching the nova process, and I think its working out well > - it certainly addresses: > - making design work visible > - being able to tell who has had input > - and providing clear feedback to the designers > > I'd like to do the same thin

Re: [openstack-dev] [Neutron] [IPv6] Ubuntu PPA with IPv6 enabled, need help to achieve it

BTW, the "VNC Consoles" are now working in a Dual-Stacked fashion (both "vncserver 5900" and "novncproxy 6080" traffics goes via IPv6). ;-) Guide updated... Cheers! Thiago On 15 April 2014 19:57, Martinx - ジェームズ wrote: > Hello Stackers! > > I just finished the OpenStack IPv6 Quick Guide, i

Re: [openstack-dev] [nova][neutron] Changing to external events

> > > Is that right, and any reason why the default for > > vif_plugging_is_fatal shouldn't be False insated of True to make this > > sequence less dependent on matching config changes ? > > Yes, because the right approach to a new deployment is to have this > enabled. If it was disabled by defau

Re: [openstack-dev] 【openstack-dev】【nova】discussion about add support to SSD ephemeral storage

On Wed, Apr 16, 2014 at 02:17:13AM +, Yuzhou (C) wrote: > Hi Daniel, > > Thanks for your comments about this > BP：https://review.openstack.org/#/c/83727/ > > My initial thoughts is to do little changes then get better performance > of guest vm. So it is a bit too narrowly focused

Re: [openstack-dev] [Nova] nova-specs

> On 04/15/2014 11:01 AM, Brian Elliott wrote: > >> * specs review. The new blueprint process is a work of genius, and I > >> think its already working better than what we've had in previous > >> releases. However, there are a lot of blueprints there in review, and > >> we need to focus on making s

Re: [openstack-dev] [Nova] Thoughts from the PTL

On Tue, Apr 15, 2014 at 10:01:32AM -0500, Brian Elliott wrote: > > * specs review. The new blueprint process is a work of genius, and I > > think its already working better than what we've had in previous > > releases. However, there are a lot of blueprints there in review, and > > we need to focus

Re: [openstack-dev] [Nova] Thoughts from the PTL -- possible mid cycle meetup dates

I think it's important to remember that not all mid cycle meetups are the same kind of thing. - the infra / havana one was a bootstrapping event - the nova / icehouse one was a mini design summit - the neutron / icehouse one was specifically focused on QA improvement - the tripleo / icehouse o

[openstack-dev] [Trove] Meeting Wednesday, 16 April @ 1800 UTC

Just a quick reminder for the weekly Trove meeting. https://wiki.openstack.org/wiki/Meetings#Trove_.28DBaaS.29_meeting Date/Time: Wednesday, 16 April - 1800 UTC / 1100 PDT / 1300 CDT IRC channel: #openstack-meeting-alt The Meeting Agenda can be found at https://wiki.openstack.org/wiki/Meetings/T

Re: [openstack-dev] [heat] computed package names?

> From: Steven Dake > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 16/04/2014 01:43 > Subject: Re: [openstack-dev] [heat] computed package names? > > On 04/15/2014 03:45 PM, Zane Bitter wrote: > > On 15/04/14 17:59, Mike Spreitzer wrote: > >> Clint Byrum wrote on

Re: [openstack-dev] [heat] computed package names?

> From: Zane Bitter > To: [email protected] > Date: 16/04/2014 00:46 > Subject: Re: [openstack-dev] [heat] computed package names? > > On 15/04/14 17:59, Mike Spreitzer wrote: > > Clint Byrum wrote on 04/15/2014 05:17:21 PM: > > > Excerpts from Zane Bitter's message of 2014-04-15

Re: [openstack-dev] [Heat] [Murano] [Solum] applications in the cloud

Hi Ruslan, > From: Ruslan Kamaldinov > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 16/04/2014 00:38 > Subject: Re: [openstack-dev] [Heat] [Murano] [Solum] applications inthe cloud > > Update: > Stan filed a blueprint [0] for type interfaces in HOT. > > > I would

Re: [openstack-dev] [neutron][chaining][policy] Port-oriented Network service chaining

Hi Balaji, Great! Thank you! Feel free to join us today at the Neutron Advanced Services sub-team IRC meeting[1] where we should continue discussing a bit more on this BP. Cheers, Carlos Goncalves [1] https://wiki.openstack.org/wiki/Meetings/AdvancedServices On 16 Apr 2014, at 06:11, balaj...

Re: [openstack-dev] deliver the vm-level HA to improve the business continuity with openstack

On 16 April 2014 03:33, Jay Pipes wrote: >> While I agree with the message, if cloud provider A has VM restarts >> every hour, and B has restarts every 6 months, all other things being >> equal I'm going to go with B. > > Pretty sure James wasn't saying that he restarts VMs every hour. The > idea

[openstack-dev] [Openstack][nova][Neutron] Launch VM with multiple Ethernet interfaces with I.P. of single subnet.

Hi, I want to launch one VM which will have two Ethernet interfaces with IP of single subnet. Is this supported now in openstack ? Any suggestion ? Thanx ___ OpenStack-dev mailing list [email protected] http://lists.openstack.org/c

Re: [openstack-dev] [Openstack][nova][Neutron] Launch VM with multiple Ethernet interfaces with I.P. of single subnet.

*With 'interfaces' I mean 'nics' of VM*. On Wed, Apr 16, 2014 at 4:18 PM, Vikash Kumar < [email protected]> wrote: > Hi, > > I want to launch one VM which will have two Ethernet interfaces with > IP of single subnet. Is this supported now in openstack ? Any suggestion ? > > >

Re: [openstack-dev] [heat] computed package names?

On 04/16/2014 02:53 AM, Thomas Spatzier wrote: From: Zane Bitter To: [email protected] Date: 16/04/2014 00:46 Subject: Re: [openstack-dev] [heat] computed package names? On 15/04/14 17:59, Mike Spreitzer wrote: Clint Byrum wrote on 04/15/2014 05:17:21 PM: > Excerpts from Zan

[openstack-dev] TC Candidacy

I would like to announce my TC candidacy. I work full time for HP where I am the architect and technical lead for the core OpenStack Engineering team, with responsibility for the architecture and deployment of the OpenStack Infrastructure projects (Nova, Neutron, Cinder, Glance, Swift) across

Re: [openstack-dev] TC Candidacy

confirmed On 04/16/2014 01:18 PM, Day, Phil wrote: > I would like to announce my TC candidacy. > > I work full time for HP where I am the architect and technical lead for the > core OpenStack Engineering team, with responsibility for the architecture and > deployment of the OpenStack Infrastruc

Re: [openstack-dev] [Murano] Working in devstack?

Hi Mark! Actually we have working Devstack scripts at [0]. We use these scripts to setup Murano in the dsvm (devstack/tempest) gate job which run Murano functional tests. It means that our Devstack scripts are in a good shape. Please use Devstack scripts from [0], all the other scripts are depreca

Re: [openstack-dev] [TripleO][design] review based conceptual design process

On 15/04/14 20:54, Ben Nemec wrote: On 04/15/2014 01:44 PM, Robert Collins wrote: I've been watching the nova process, and I think its working out well - it certainly addresses: - making design work visible - being able to tell who has had input - and providing clear feedback to the design

[openstack-dev] [infra] [nodepool] Modification for use clean KVM/QEMU

Hi community! I have a modification for Nodepool which allows to use it with a clean KVM/QEMU host while still support OpenStack. This allows parallel use KVM/QEMU and OpenStack hosts. As well, this saves computing resources required to perform OpenStack and time on its setting. Need this feature f

Re: [openstack-dev] [infra] [nodepool] Modification for use clean KVM/QEMU

On 04/16/2014 08:39 AM, Vladislav Kuzmin wrote: > Hi community! > I have a modification for Nodepool which allows to use it with a > clean KVM/QEMUhost while still support OpenStack. This allows parallel > use KVM/QEMUand OpenStackhosts. As well, this saves computing resources > required to perform

Re: [openstack-dev] Hyper-V CI is broken

Hey Joe, In response to your question around our plans.I will gladly shed some light in that area. I apologize for the delayed response as I was waiting to confirm information prior to responding. To start we have been stabilizing what we have in place today, and are in the process of add

Re: [openstack-dev] [neutron] Neutron Mid-Cycle Meeting

So, I'm glad there's interest in doing this. I would encourage folks who are interested in attending to please add their names to the etherpad, and to suggest locations there as well. We'll try to converge on those over the coming weeks. Also, as pointed out by ttx, we should hold off an settling o

Re: [openstack-dev] [nova] unit tests method

On Wed, 2014-04-16 at 14:55 +0800, Chen CH Ji wrote: > Hi > There are 3 types of unit test existing now (stub, mox > and mock) > Several code reviewers suggest to use mock instead of > using the other 2 and I am following it, but I want to know where can > I find th

[openstack-dev] [Nova][blueprint] Accelerate the booting process of a number of vms via VMThunder

Dear all, We would like to present an extension to the vm-booting functionality of Nova when a number of homogeneous vms need to be launched at the same time. The motivation for our work is to increase the speed of provisioning vms for large-scale scientific computing and big data processing

Re: [openstack-dev] [neutron] Neutron BP review process for Juno

I think the problem is that your spec should be at the toplevel of the juno directory, and that's why the UT is failing. Can you move your spec up a level, including the image? You can create a spec images directory to put them in there and reference it in the spec as well if you want. On Tue, Apr

Re: [openstack-dev] [heat] computed package names?

In the case of yum or apt package installation, I would recommend to give OS::Heat::CloudConfig a try, instead of sticking to cfn-init. The function you proposed (Fn::MemberListToMap) actually brings us back to the previous discussion whether a mapping section is really needed in the native HOT te

Re: [openstack-dev] [neutron] Neutron BP review process for Juno

if the image you're adding is a diagram, I would think about asciiflow.comfirst! On 16 April 2014 15:09, Kyle Mestery wrote: > I think the problem is that your spec should be at the toplevel of the > juno directory, and that's why the UT is failing. Can you move your > spec up a level, includin

Re: [openstack-dev] [neutron] Neutron Mid-Cycle Meeting

Kyle Mestery wrote: > So, I'm glad there's interest in doing this. I would encourage folks > who are interested in attending to please add their names to the > etherpad, and to suggest locations there as well. We'll try to > converge on those over the coming weeks. Also, as pointed out by ttx, > we

Re: [openstack-dev] [heat] computed package names?

+1 on porting the templates. What I would suggest also is to restructure the heat-templates directory layout. Most of the templates are not so different between OS distros. Besides this, what the heat-templates project really helps is that the templates are the best teaching materials for new us

Re: [openstack-dev] [neutron] Neutron BP review process for Juno

Actually, +1 to that Salvatore! I've found asciiflow.com to be superb for these types of things. On Wed, Apr 16, 2014 at 8:39 AM, Salvatore Orlando wrote: > if the image you're adding is a diagram, I would think about asciiflow.com > first! > > > On 16 April 2014 15:09, Kyle Mestery wrote: >> >>

Re: [openstack-dev] [neutron] Neutron BP review process for Juno

On 04/16/2014 09:39 AM, Salvatore Orlando wrote: > if the image you're adding is a diagram, I would think about > asciiflow.com first! In all seriousness, I think that's a very nice solution for simple diagrams. :-) For other diagrams, I wonder if it makes sense to just up

Re: [openstack-dev] [Nova] nova-specs

I love that we are getting feedback from deployers/operations/etc. Thanks to all who have spoken up in support from that perspective. On 4/16/14 4:02 AM, "Day, Phil" wrote: >> >They are intended to be high level designs rather than low level designs, >so no they don't have to include all of th

[openstack-dev] [openstack][nova][specs] Where to store images used in the spec

Hi, I've just uploaded a new BP proposal to gerrit https://review.openstack.org/#/c/87978, but the gate failed as I included an image along with the .rst file in my patch. What is the good place to store the images that are used in the specs? Cheers, Gibi

[openstack-dev] [heat][mistral] Mistral agenda item for Heat community meeting on Apr 17

Hi, Can we include action item “Heat/Mistral collaboration” into the agenda of tomorrow’s Heat community meeting? I’d like to take a few minutes and discuss this a little bit. If you think it’s not a suitable time/way to discuss it please let me know your preferences. Thanks Renat Akhmerov @

Re: [openstack-dev] [TripleO] [Tuskar] Undercloud Ceilometer

No response so far, but -1 on the image element for making Ceilometer optional. OK, so what about having variable in devtest_variables: USE_TRIPLEO_UI. It would add Undercloud Ceilometer, Tuskar-UI and Horizon. And Overcloud SNMPd. Defaulted to USE_TRIPLEO_UI=1 so we have UI stuff in CI. How

Re: [openstack-dev] [neutron] Neutron Mid-Cycle Meeting

I just want to quickly caution about having these meetings in person since not everyone will be able to attend - the summits are probably where we will have the most Neutron developers able to attend. It's not that I oppose the idea - but there must be adequate facilities for people to attend and

Re: [openstack-dev] [Nova] nova-specs

> There may be some consistency work needed. I spent some time/text in > justification around no security impact in a spec. I was guided > specifically that None was a better statement. I think you're referring to me. What I said was, you went into a lot of depth explaining why there was no secu

Re: [openstack-dev] [Nova] nova-specs

On 04/16/2014 10:13 AM, Christopher Lefelhocz wrote: > I love that we are getting feedback from deployers/operations/etc. Thanks > to all who have spoken up in support from that perspective. > > On 4/16/14 4:02 AM, "Day, Phil" wrote: > >>> >> They are intended to be high level designs rather th

[openstack-dev] [Devstack] [IPv6]

Hi folks, If you want to use IPv6 with devstack, Check this out https://review.openstack.org/87987. The commit message has all the details on how to use it. thanks, Robert ___ OpenStack-dev mailing list [email protected] http://lists.o

Re: [openstack-dev] [openstack][nova][specs] Where to store images used in the spec

On 04/16/2014 10:31 AM, Balázs Gibizer wrote: > Hi, > > > > I’ve just uploaded a new BP proposal to gerrit > https://review.openstack.org/#/c/87978, but the gate failed as I > included an image along with the .rst file in my patch. What is the good > place to store the images that are used in

Re: [openstack-dev] [Nova] nova-specs

On 4/16/14 10:00 AM, "Dan Smith" wrote: > >Remember that just because someone -1s a patch, doesn't mean that every >single comment they made was -1 worthy on its own. Often times I will -1 >for a spelling mistake and then make a bunch of other purely-opinion >comments which don't necessarily ne

Re: [openstack-dev] [heat][mistral] Mistral agenda item for Heat community meeting on Apr 17

On 16/04/14 10:29, Renat Akhmerov wrote: Can we include action item “Heat/Mistral collaboration” into the agenda of tomorrow’s Heat community meeting? I’d like to take a few minutes and discuss this a little bit. If you think it’s not a suitable time/way to discuss it please let me know your p

[openstack-dev] [python-openstacksdk] Minutes from 15 April Meeting

Minutes: http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-04-15-19.00.html Minutes (text): http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-04-15-19.00.txt Log: http://eavesdrop.openstack.org/meetings/python_opens

Re: [openstack-dev] [heat] computed package names?

On 16/04/14 05:53, Thomas Spatzier wrote: IMO, it would be desirable to not have things like yum or apt appear in the template explicitly. For many packages it seems like at least the top level package names (not including distro specific versioning strings) are equal across distros so when speci

[openstack-dev] [heat] [heat-templates] [qa] [tempest] Questions about images

Many of the templates in the heat-templates project have built-in expectations of image names; here is an example excerpt: F18: {'32': F18-i386-cfntools, '64': F18-x86_64-cfntools} F17: {'32': F17-i386-cfntools, '64': F17-x86_64-cfntools} U10: {'32': U10-i386-cfntools, '64': U10-x86_6

[openstack-dev] Seeking interest in an open Content Delivery Network (CDN) API

OpenStack, Our team is currently seeking partners who share an interest and enthusiasm for exploring the possibility of Content Delivery Network (CDN) capabilities within the open ecosystem. Our desire is to create a unified and open API that leverages existing CDN providers in an open source-frie

Re: [openstack-dev] [neutron] Neutron BP review process for Juno

Additionally, storing lots of binary blobs in a Git repo is sub-optimal, as the repo size ballons very quickly. Storing images on the Wiki, or elsewhere that has stable image hosting, is a much better solution, IMHO (but try asciiflow or asciiflow traditional first!). Best Regards, Solly Ross --

Re: [openstack-dev] [heat] computed package names?

Zane Bitter wrote on 04/16/2014 11:39:56 AM: > In any event, though, my impression is that we are trying to get out of > the cfn-init business as much as possible and leave the task to some > combination of custom images, software config and configuration > management. Hopefully someone will c

Re: [openstack-dev] [all] Branchless Tempest QA Spec - final draft

Hi Sean, for what I understood, we will need a new feature flag for each new feature, and a feature flag (default to false) for each deprecated one. My concern is: since the goal is make tempest a confident tool to test any installation and not and 'tempest.conf' will not be auto-generated from an

Re: [openstack-dev] [Openstack] About advice for Contribution

If you start contributing to Nova, my advice would be to start small -- find a part of Nova that you get to know well, and then branch out. Nova is a large project with complex paths through the code (RPC vs REST API vs normal method calling), so it can take a bit of time to get used to. You c

Re: [openstack-dev] Vagrant Devstack projects - time to consolidate?

On Tue, Apr 15, 2014 at 04:30:53PM EDT, Joe Gordon wrote: > One of my biggest issues with running devstack in vagrant is how slow > it is The vagrant_devstack project (github.com/bcwaldon/vagrant_devstack) has some Chef recipes to cache pip and apt - so it's only the first run that is slow, and re

Re: [openstack-dev] [neutron] Neutron Mid-Cycle Meeting

+1 to Sean Fawad Khaliq (m) +1 408.966.2214 On Wed, Apr 16, 2014 at 7:54 AM, Collins, Sean < [email protected]> wrote: > I just want to quickly caution about having these meetings in person > since not everyone will be able to attend - the summits are probably > where we will have

Re: [openstack-dev] [Nova] nova-specs

On 4/16/14 10:00 AM, "Dan Smith" wrote: >> There may be some consistency work needed. I spent some time/text in >> justification around no security impact in a spec. I was guided >> specifically that None was a better statement. > >I think you're referring to me. What I said was, you went int

Re: [openstack-dev] [openstack][nova][specs] Where to store images used in the spec

Thanks for the pointer to the Neutron thread. After reading it through I decided to move the image to wiki. Thanks, Gibi -Original Message- From: Russell Bryant [mailto:[email protected]] Sent: Wednesday, April 16, 2014 5:09 PM To: [email protected] Subject: Re: [opensta

Re: [openstack-dev] [Neutron] API list operations are not fast as they could because they're dumb

Checking whether a policy used for visibility depends on an attribute value is possible. I just don't think it's right. For instance, one could define the following policies: "the_funny_one": "field:networks:name=Funny" "get_network:provider:physical_network": "rule:admin_only or rule:the_funny_on

Re: [openstack-dev] [Nova][blueprint] Accelerate the booting process of a number of vms via VMThunder

Hello Yongquan Fu, My thoughts: 1. Currently Nova has already supported image caching mechanism. It could caches the image on compute host which VM had provisioning from it before, and next provisioning (boot same image) doesn't need to transfer it again only if cache-manger clear it up. 2. P2P t

Re: [openstack-dev] [neutron] Neutron BP review process for Juno

Hi Mestery With respect to the new BP review process, can we start submitting the BPs in the review system and in the launchpad. Since, BP is a thought process of the developer either for core dev or for vendor specific dev, can you give some light on how the review process of the BP can be ?

Re: [openstack-dev] [nova] unit tests method

On 04/16/2014 08:11 AM, Jay Pipes wrote: On Wed, 2014-04-16 at 14:55 +0800, Chen CH Ji wrote: Hi There are 3 types of unit test existing now (stub, mox and mock) Several code reviewers suggest to use mock instead of using the other 2 and I am following it, but I

Re: [openstack-dev] [Openstack] About advice for Contribution

Thanks Solly for Guidance. I also hope to get familiar with NOVA internals soon. Thanks ! On Wed, Apr 16, 2014 at 9:20 PM, Solly Ross wrote: > If you start contributing to Nova, my advice would be to start small -- > find a part of Nova > that you get to know well, and then branch out. Nova i

Re: [openstack-dev] [Nova] nova-specs

> I'm not asking for 100% consistency. I'm just raising it since it seems > to be early in the process change and want to work out these kinds of > things. If it turns out to be an outlier then great. Sure, and the spec reviewers are learning in this process as well. It takes a certain amount of

[openstack-dev] open question about keystone-configuration

Hello there, My name is Min Wang, and I am working in HP cloud compute team. I got a question regarding keystone configuration and need guidance. So I am following the instruction in this pdf file: http://docs.openstack.org/havana/install-guide/install/apt/openstack-install-guide-apt-havana.pd

Re: [openstack-dev] [openstack][nova][specs] Where to store images used in the spec

On 04/16/2014 12:00 PM, Balázs Gibizer wrote: > Thanks for the pointer to the Neutron thread. After reading it through > I decided to move the image to wiki. OK. I think your diagram is probably doable in ascii, though. :-) -- Russell Bryant ___ Ope

Re: [openstack-dev] open question about keystone-configuration

On 04/16/2014 12:15 PM, Wang, Min wrote: Hello there, My name is Min Wang, and I am working in HP cloud compute team. I got a question regarding keystone configuration and need guidance. So I am following the instruction in this pdf file: http://docs.openstack.org/havana/install-guide/insta

Re: [openstack-dev] [heat] computed package names?

Different distro's move the binaries and services too. ubuntu/debian does: /usr/sbin/apache2, not httpd. The service is also named apache2, not httpd. So, I think distro specific sets of packages are somewhat unavoidable. Now, this use case might be a good case for supporting: https://blueprints.

Re: [openstack-dev] [Openstack] open question about keystone-configuration

Hi Min Wang, This is error might be due to permission problem you *must run *these commands from root. The command * openssh rand -hex 10* will create the token which you have to put in /etc/keystone/keystone.conf in admin section. the mentioned command # export

Re: [openstack-dev] [openstack][nova][specs] Where to store images used in the spec

The only downside to putting it on the wiki is that it no longer has a shared fate with the specification in the repo. If someone deletes it or replaces it on the wiki, information for the spec is lost. External connectivity is also required just to view a template as well. On Wed, Apr 16, 2014

Re: [openstack-dev] [Devstack] [IPv6]

Awesome!! I'll check this today! Tks! On 16 April 2014 12:03, Robert Li (baoli) wrote: > Hi folks, > > If you want to use IPv6 with devstack, Check this out > https://review.openstack.org/87987. The commit message has all the details > on how to use it. > > thanks, > Robert > > > __

Re: [openstack-dev] Hyper-V CI is broken

On Wed, Apr 16, 2014 at 6:04 AM, Peter Pouliot wrote: > Hey Joe, > > In response to your question around our plans.I will gladly shed > some light in that area. > > I apologize for the delayed response as I was waiting to confirm > information prior to responding. > > To start we have been

Re: [openstack-dev] [neutron] Neutron BP review process for Juno

On Wed, Apr 16, 2014 at 11:05 AM, [email protected] wrote: > Hi Mestery > > With respect to the new BP review process, can we start submitting the BPs in > the review system and in the launchpad. > Yes, the repository is open and in fact we have our first review posted already [1].

[openstack-dev] TC Candidacy

Hi folks, I'd like to announce my candidacy for the TC. I have been actively involved in OpenStack for about last two years, and before that I was in observer mode since Diablo timeframe. I’m PTL of OpenStack Data Processing program (Sahara project) from its very beginning. Additionally, I’m the

Re: [openstack-dev] [openstack][nova][specs] Where to store images used in the spec

On 04/16/2014 12:42 PM, Kevin Benton wrote: > The only downside to putting it on the wiki is that it no longer has a > shared fate with the specification in the repo. If someone deletes it or > replaces it on the wiki, information for the spec is lost. External > connectivity is also required just

Re: [openstack-dev] [heat] [heat-templates] [qa] [tempest] Questions about images

Hi Mike, On Wed, Apr 16, 2014 at 11:39:59AM -0400, Mike Spreitzer wrote: > Many of the templates in the heat-templates project have built-in > expectations of image names; here is an example excerpt: > > F18: {'32': F18-i386-cfntools, '64': F18-x86_64-cfntools} > F17: {'32': F17-i386-cfn

Re: [openstack-dev] [openstack][nova][specs] Where to store images used in the spec

On 04/16/2014 12:55 PM, Russell Bryant wrote: > On 04/16/2014 12:42 PM, Kevin Benton wrote: >> The only downside to putting it on the wiki is that it no longer has a >> shared fate with the specification in the repo. If someone deletes it or >> replaces it on the wiki, information for the spec is l

Re: [openstack-dev] [neutron] Neutron BP review process for Juno

On 04/16/2014 09:51 AM, Russell Bryant wrote: > On 04/16/2014 09:39 AM, Salvatore Orlando wrote: >> if the image you're adding is a diagram, I would think about >> asciiflow.com first! > > In all seriousness, I think that's a very nice solution for simple > diagrams. :-) >

Re: [openstack-dev] [nova] unit tests method

On Wed, 2014-04-16 at 11:05 -0500, Ben Nemec wrote: > On 04/16/2014 08:11 AM, Jay Pipes wrote: > > On Wed, 2014-04-16 at 14:55 +0800, Chen CH Ji wrote: > >> Hi > >> There are 3 types of unit test existing now (stub, mox > >> and mock) > >> Several code reviewers su

Re: [openstack-dev] [neutron] Neutron BP review process for Juno

On Wed, Apr 16, 2014 at 12:23 PM, Russell Bryant wrote: > On 04/16/2014 09:51 AM, Russell Bryant wrote: >> On 04/16/2014 09:39 AM, Salvatore Orlando wrote: >>> if the image you're adding is a diagram, I would think about >>> asciiflow.com first! >> >> In all seriousness, I t

Re: [openstack-dev] [Nova] nova-specs

> single comment they made was -1 worthy on its own. Often times I will -1 > for a spelling mistake and then make a bunch of other purely-opinion > comments which don't necessarily need to change. Do we really want to -1 for spelling mistake in nova-specs? This is really a bad news for non-native

Re: [openstack-dev] [Neutron][LBaaS] Requirements and API revision progress

On Apr 14, 2014, at 8:20 PM, Stephen Balukoff mailto:[email protected]>> wrote: Hello y'all! Over the last few months, I feel like we've seen a renewed vigor for participation in making the LBaaS project successful. After the (still unresolved) object model discussion started in January,

Re: [openstack-dev] [Nova] nova-specs

> Do we really want to -1 for spelling mistake in nova-specs? I do, yes. These documents are intended to be read by deployers and future developers. I think it's really important that they're useful in that regard. > This is really a bad news for non-native speaker like me because I'm > really n

Re: [openstack-dev] [heat] [heat-templates] [qa] [tempest] Questions about images

Steven Hardy wrote answers to most of my questions. To clarify, my concern about URLs and image names is not so much for the sake of a person browsing/writing but rather because I want programs, scripts, templates, and config files (e.g., localrc for DevStack) to all play nice together (e.g.,

Re: [openstack-dev] [heat] [heat-templates] [qa] [tempest] Questions about images

Steven Hardy wrote on 04/16/2014 01:05:14 PM: > On Wed, Apr 16, 2014 at 11:39:59AM -0400, Mike Spreitzer wrote: > > http://fedorapeople.org/groups/heat/prebuilt-jeos-images/F19- > x86_64-cfntools.qcow2 > > seems to be broken; I get failures every time I try to use it. Has > > anybody had succ

Re: [openstack-dev] TC Candidacy

confirmed On 04/16/2014 12:47 PM, Sergey Lukjanov wrote: > Hi folks, > > I'd like to announce my candidacy for the TC. > > I have been actively involved in OpenStack for about last two years, > and before that I was in observer mode since Diablo timeframe. I’m PTL > of OpenStack Data Processing

Re: [openstack-dev] [Nova] nova-specs

On 04/16/2014 01:56 PM, Dan Smith wrote: >> Do we really want to -1 for spelling mistake in nova-specs? > > I do, yes. These documents are intended to be read by deployers and > future developers. I think it's really important that they're useful in > that regard. > >> This is really a bad news f

Re: [openstack-dev] [Nova] nova-specs

On Wed, Apr 16, 2014 at 1:56 PM, Dan Smith wrote: >> Do we really want to -1 for spelling mistake in nova-specs? > > I do, yes. These documents are intended to be read by deployers and > future developers. I think it's really important that they're useful in > that regard. > >> This is really a ba

Re: [openstack-dev] [heat] computed package names?

Hello, A few folks give me some suggestion, and I followed it, it seems that the problem is not solved yet, anyone can tell what steps here is not correct? openstack@ubuntu:~$ keystone-manage db_sync openstack@ubuntu:~$ openssl rand -hex 10 2c3a6bb5b3b8880f44f2 openstack@ubuntu:~$ sudo vi /etc/k

[openstack-dev] openstack cinder policy error while installing cinder

Hi, While installing cinder in openstack i was encountered the following error: root@openstackvm00:~# cinder type-create lvm ERROR: Policy doesn't allow volume_extension:types_manage to be performed. When i Checked tail -f /var/log/cinder/cinder-api i got the following issue http 403 2

[openstack-dev] Running neutron in child cells

Hello, I am trying to figure out if an instance of neutron can be run on the controllers of each child cell and if neutron commands sent to the master node would then be routed to the child cell similar to how the nova commands get routed. I have searched online and as well as in the documentat

Re: [openstack-dev] openstack cinder policy error while installing cinder

This is a development list, and your question sounds more appropriate for the users list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Thanks. -Ben On 04/16/2014 01:35 PM, Arunkumar Achutha wrote: Hi, While installing cinder in openstack i was encountered the followin

Re: [openstack-dev] [Nova] nova-specs

As a native English speaker who works in two Francophone countries for an international organisation, I would suggest tolerance in this area. Where there are sufficient language difficulties that the blueprint is difficult to read and understand, this should be a -1. Where someone accidentally

Re: [openstack-dev] [all] Branchless Tempest QA Spec - final draft

On 04/16/2014 11:48 AM, Jaume Devesa wrote: > Hi Sean, > > for what I understood, we will need a new feature flag for each new > feature, and a feature flag (default to false) for each deprecated one. > My concern is: since the goal is make tempest a confident tool to test > any installation and n

  1   2   >