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

This seems painful for a tenant workflow to get multiple addresses. I would like to improve this during the Juno cycle. What is the limitation that is blocking the multi-nic use cases? Is it Nova? On Wed, Apr 16, 2014 at 11:27 PM, Aaron Rosen wrote: > Hi Kevin, > > You'd would just create ports

[openstack-dev] [Heat][Nova][Neutron]Detach interface will delete the port

Hi all, Port is a resource define in Heat. And heat support the actions: create a port/delete a port/attach to a server/detach from a server. But we can't re-attach a port which once be detached. ---

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

Hi Kevin, You'd would just create ports that aren't attached to instances and steal their ip_addresses from those ports and put those in the allowed-address-pairs on a port OR you could change the allocation range on the subnet to ensure these ips were never handed out. That's probably the right a

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

Sorry not really. It's still not clear to me why multiple nics would be required on the same L2 domain. Would you mind drawing your use case here: http://asciiflow.com/ (or maybe google docs) labeling the different interfaces with ips and the flow of packets you want. Also perhaps their header valu

[openstack-dev] [nova] Nova API meeting

Hi, Chris has some days off now. I'd like to run the next meeting instead. Just a reminder that the weekly Nova API meeting is being held tomorrow Friday UTC . We encourage cloud operators and those who use the REST API such as SDK developers and others who and are interested in the future

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

Aaron, The idea is to steer packets coming from source S1 ( belong to net1) destined to destination D1 (belong to net1) through bunch of L2 appliances (like firewall) without modifying packet headers. The core idea is to keep appliances (on net1), source S1 (VM on net1) and destination D1(VM on

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

Kevin , this can be one approach but not sure. But certainly won't solve all cases. :) On Thu, Apr 17, 2014 at 10:33 AM, Kevin Benton wrote: > Yeah, I was aware of allowed address pairs, but that doesn't help with the > IP allocation part. > > Is this the tenant workflow for this use case? >

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

Yeah, I was aware of allowed address pairs, but that doesn't help with the IP allocation part. Is this the tenant workflow for this use case? 1. Create an instance. 2. Wait to see what which subnet it gets an allocation from. 3. Pick an IP from that subnet that doesn't currently appear to be in u

[openstack-dev] TC candidacy

I'd like to announce my Technical Committee candidacy. I've been involved with OpenStack since it began. I'm one of the original authors of Swift, and I have been serving as PTL since the position was established. I'm employed by SwiftStack, a company building management and integration tools f

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

Whoops Akihiro beat me to it :) On Wed, Apr 16, 2014 at 9:46 PM, Aaron Rosen wrote: > The allowed-address-pair extension that was added here ( > https://review.openstack.org/#/c/38230/) allows us to add arbitrary ips > to an interface to allow them. This is useful if you want to run something >

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

The allowed-address-pair extension that was added here ( https://review.openstack.org/#/c/38230/) allows us to add arbitrary ips to an interface to allow them. This is useful if you want to run something like VRRP between two instances. On Wed, Apr 16, 2014 at 9:39 PM, Kevin Benton wrote: > I w

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

Hi Vikash, Sorry I don't really follow your example. You're saying you have have two hosts S1 and S2 that are connected to the same network. Would you mind explaining this example in a little more details, what ip's do they have how many interfaces, etc? I've quite curious to hear. Best, Aaron

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

To cope with such cases, allowed-address-pairs extension was implemented. http://docs.openstack.org/api/openstack-network/2.0/content/allowed_address_pair_ext_ops.html (2014/04/17 13:39), Kevin Benton wrote: > I was under the impression that the security group rules blocked > addresses not assigne

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

I was under the impression that the security group rules blocked addresses not assigned by neutron[1]. 1. https://github.com/openstack/neutron/blob/master/neutron/agent/linux/iptables_firewall.py#L188 On Wed, Apr 16, 2014 at 9:20 PM, Aaron Rosen wrote: > You can do it with ip aliasing and use

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

Lets say I have source S1 on n/w net1, destination S2 on net1 and i want to firewall traffic coming from S1 destined to S2. I can use L3 firewall but in that case the packet headers will have different values, not the same source and destination. Instead, we can divide network in L2 segments and st

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

I'd like to see your use case too. I heard a similar demand recently. It is a case of migration of legacy applicaitons to virtual platform and the applications which manages redandunt NICs directly and they just want not to change the applcations itself. It is just server consolidation and not a

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

Ooh, I confused the day of meeting :(. My apologies, I’m in a completely different timezone (for me it’s in the middle of night) so I strongly believed it was on a different day. I’ll be there next time. Renat Akhmerov @ Mirantis Inc. On 17 Apr 2014, at 11:28, Renat Akhmerov wrote: > Ok. The

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

On 17/04/14 14:20, Aaron Rosen wrote: > You can do it with ip aliasing and use one interface: > > ifconfig eth0 10.0.0.22/24 > ifconfig eth0:1 10.0.0.23/24 > ifconfig eth0:2 10.0.0.24/24 The 'ip' command can also do it. ip addres

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

Ok. The reason I asked about it is because I recognize you guys may be very busy now for pre-summit activities going on. :) Thanks! Renat Akhmerov @ Mirantis Inc. On 16 Apr 2014, at 22:18, Zane Bitter wrote: > On 16/04/14 10:29, Renat Akhmerov wrote: >> Can we include action item “Heat/Mist

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

You can do it with ip aliasing and use one interface: ifconfig eth0 10.0.0.22/24 ifconfig eth0:1 10.0.0.23/24 ifconfig eth0:2 10.0.0.24/24 2: eth0: mtu 1500 qdisc mq state DOWN qlen 1000 link/ether 40:6c:8f:1a:a9:31 brd ff:ff:ff:ff:ff:ff inet 10.0.0.22/24 brd 10.0.0.255 scope global eth0

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

Web server running multiple SSL sites that wants to be compatible with clients that don't support the SNI extension. There is no way for a server to get multiple IP addresses on the same interface is there? On Wed, Apr 16, 2014 at 5:50 PM, Aaron Rosen wrote: > This is true. Several people have

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

Hi all, In order to ease confusion I think I might create use case walk-throughs to show how the API would work. There's only been one week to work on this (minus other work) so I haven't had enough time to create them. I'll try to capture most of them in this form over the following week as I

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

Yes please... I don't see why one would need two interfaces on the same L2 to do that though. On Wed, Apr 16, 2014 at 8:29 PM, Vikash Kumar < vikash.ku...@oneconvergence.com> wrote: > Aaron, > >One of the use case is to create L2 segments in a network. I can > elaborate this use case if u wa

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

On Apr 16, 2014, at 7:56 PM, Stephen Balukoff mailto:sbaluk...@bluebox.net>> wrote: Hi y'all! This is actually a pretty good start for a revision of the Neutron LBaaS API. My feedback on your proposed API v2.0 is actually pretty close to Eugene's, with a couple additions: You say 'only one

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

As a fresh guy on nova(Have about 1+ year in nova but less than 0.5 year experience to contribute to community) I'd like to share my feeling on using nova-specs 1) let me know what we are going to do for next release,it wider my understand of whole nova since I am able to take a look at the desig

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

Aaron, One of the use case is to create L2 segments in a network. I can elaborate this use case if u want. On Thu, Apr 17, 2014 at 6:20 AM, Aaron Rosen wrote: > This is true. Several people have asked this same question over the years > though I've yet to hear a use case why one really nee

Re: [openstack-dev] [OpenStack][VMWare] "qemu-img convert" problems for VM creation

Good timing. I just tried this today for the first time. Here's what worked for me: wget http://cloud-images.ubuntu.com/saucy/current/saucy-server-cloudimg-i386-disk1.img qemu-img convert -f qcow2 saucy-server-cloudimg-i386-disk1.img -O vmdk saucy-server-cloudimg-i386-disk1.vmdk glance image

[openstack-dev] TC candidacy - not running

Hi, just to avoid any confusion - I'm not putting my hat in the ring for the TC this cycle - I think I helped make a difference as a member of the TC over the last 6 months, but TripleO is maturing and growing rapidly and the TC is (rightly) taking on more and deeper analysis and coordination work

[openstack-dev] [openstack-sdk-php] Questions about user-facing documentation

Hi folks, As part of working on https://blueprints.launchpad.net/openstack-sdk-php/+spec/sphinx-docs, I’ve been looking at http://git.openstack.org/cgit/stackforge/openstack-sdk-php/tree/doc. Before I start making any changes toward that BP, however, I wanted to put forth a couple of overarchi

[openstack-dev] [glance] Release notes for Icehouse

Hi, Is someone working on release notes for glance? At the moment it's looking pretty bare :) https://wiki.openstack.org/wiki/ReleaseNotes/Icehouse Regards, Tom ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openst

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

Hi, Comments inline: On Tue, Apr 8, 2014 at 3:16 PM, Salvatore Orlando wrote: > I have been recently investigating reports of slowness for list responses > in the Neutron API. > This was first reported in [1], and then recently was observed with both > the ML2 and the NSX plugins. > The root ca

[openstack-dev] [OpenStack][VMWare] "qemu-img convert" problems for VM creation

Hi, Does anyone ever create VMWare image using "qemu-img convert" from a QCOW2 image? I did some test according to the following guide but the VM creation always failed. I tried to logon to the console of the VM and found the console is reporting the VM was boot from PXE and no operating systems.

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

Hi y'all! This is actually a pretty good start for a revision of the Neutron LBaaS API. My feedback on your proposed API v2.0 is actually pretty close to Eugene's, with a couple additions: You say 'only one port and protocol per load balancer', yet I don't know how this works. Could you define w

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

This is true. Several people have asked this same question over the years though I've yet to hear a use case why one really need to do this. Do you have one? On Wed, Apr 16, 2014 at 3:12 PM, Ronak Shah wrote: > Hi Vikash, > Currently this is not supported. the NIC not only needs to be in differ

Re: [openstack-dev] Running neutron in child cells

Hi Ramkumar, Today there is no type of cells integration or cells like logic in neutron. If using nova cells, each cell must share the same neturon deployment. This neutron deployment though can be scaled out across several neutron servers behind a loadbalancer though. Another scaling option could

Re: [openstack-dev] [Ironic] Merging the agent driver

All, If anyone has a chance to do some review, we really want to get this one merged: https://review.openstack.org/#/c/81919/ This will clear the way for us to work on getting the driver reviewed, followed by a series of smaller patches. Thanks, Russell On Tue, Apr 8, 2014 at 4:58 PM, Jim Roll

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

On Apr 16, 2014, at 4:31 PM, Eugene Nikanorov mailto:enikano...@mirantis.com>> wrote: Hi folks, I've briefly looked over the doc. I think whole idea to base the API on Atlas misses the content switching use case, which is very important: We need multiple pools within loadbalancer, and API doe

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

On 17/04/14 09:11, Thomas Spatzier wrote: >> From: Mike Spreitzer >> To: "OpenStack Development Mailing List \(not for usage questions\)" >> >> Date: 16/04/2014 19:58 >> Subject: Re: [openstack-dev] [heat] [heat-templates] [qa] [tempest] >> Questions about images >> >> Steven Hardy wrote answers

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

Excerpts from Zane Bitter's message of 2014-04-16 08:39:56 -0700: > 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 includ

Re: [openstack-dev] [Openstack-operators] Quota Templates

Adding the dev list. I would to see also the devs opinion in this blueprint, we need to discuss the approach for this. https://review.openstack.org/#/c/84432/9 -Original Message- From: Cazzolato, Sergio J Sent: Wednesday, April 16, 2014 5:47 PM To: Cazzolato, Sergio J; James Penick;

[openstack-dev] Quotas: per-flavor-quotas

Sergio J Cazzolato wrote: > I would to see the operators opinion in this blueprint, we need to > understand if it is useful or it is confusing for you. > > https://review.openstack.org/#/c/84432/9 Sergio, I'm reposting this in a new thread since this isn't about quota templates. Also I'm postin

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

Hi folks My bad,, Issue (1) was my mistake, and fixed 2014-04-16 15:16 GMT-07:00 Nachi Ueno : > Hi folks > > I submitted a wip patch which has diagram examples for both of ascii > flow and blockdiag. > > https://review.openstack.org/#/c/88095/1 > > This is both output from ascii flow and blockdia

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

Hi folks I submitted a wip patch which has diagram examples for both of ascii flow and blockdiag. https://review.openstack.org/#/c/88095/1 This is both output from ascii flow and blockdiag. https://wiki.openstack.org/wiki/File:Screenshot.png I faced two issue in ascii flow. May be, I'm missing

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

Hi Vikash, Currently this is not supported. the NIC not only needs to be in different subnet, they have to be in different network as well (container for the subnet) Thanks Ronak On Wed, Apr 16, 2014 at 3:51 AM, Vikash Kumar < vikash.ku...@oneconvergence.com> wrote: > *With 'interfaces' I mean '

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

Eugene, Towards the bottom of that document it does mention content switching and how it would work with this. I know its a huge text document and hard to navigate but it is there. The point of the one pool on a load balancer is because other than content switching there aren't any other use c

Re: [openstack-dev] [barbican] Barbican 2014.1 ("Icehouse") is released

Hi Eugene, Currently, all of our documentation is in GitHub, which can be found at: https://github.com/cloudkeep/barbican/wiki We’re working on moving the docs to docbook format, so stay tuned for updated docs in the future. Regards, Douglas Mendizábal From: Eugene Nikanorov Reply-To: "OpenS

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

On 16/04/14 21:53, Thomas Spatzier wrote: >> From: Zane Bitter >> To: openstack-dev@lists.openstack.org >> 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: >>> > E

Re: [openstack-dev] [barbican] Barbican 2014.1 ("Icehouse") is released

Hi Douglas, could you please point to the project docs? Thanks, Eugene. On Thu, Apr 17, 2014 at 1:48 AM, Douglas Mendizabal < douglas.mendiza...@rackspace.com> wrote: > Hi everybody! > > It is my pleasure to announce the final release of Barbican for Icehouse > 2014.1 > > Information on the m

[openstack-dev] [barbican] Barbican 2014.1 ("Icehouse") is released

Hi everybody! It is my pleasure to announce the final release of Barbican for Icehouse 2014.1 Information on the milestone and its associated tar ball are available at: https://launchpad.net/barbican/icehouse/icehouse Many thanks to all the contributors who made this first incubated milestone po

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

On Wed, Apr 16, 2014 at 4:26 PM, Carl Baldwin wrote: > Neutron (and Nova), > > I have had one thing come up as I've been using the template. I find > that I would like to add just a little document structure in the form > of a sub-heading or two under the "Proposed change" heading but before > th

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

Hi folks, Our regular meeting is going to be on Thursday, 17, at 14-00 UTC We have some data and requirements to discuss. Also, we'll discuss the API proposal by Jorge & Brandon Thanks, Eugene. ___ OpenStack-dev mailing list OpenStack-dev@lists.opensta

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

Hi folks, I've briefly looked over the doc. I think whole idea to base the API on Atlas misses the content switching use case, which is very important: We need multiple pools within loadbalancer, and API doesn't seem to allow that. If it would, then you'll face another problem: you need to refere

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

> From: Mike Spreitzer > To: "OpenStack Development Mailing List \(not for usage questions\)" > > Date: 16/04/2014 19:58 > Subject: Re: [openstack-dev] [heat] [heat-templates] [qa] [tempest] > Questions about images > > Steven Hardy wrote answers to most of my questions. > > To clarify, my conce

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

Neutron (and Nova), I have had one thing come up as I've been using the template. I find that I would like to add just a little document structure in the form of a sub-heading or two under the "Proposed change" heading but before the required "Alternatives" sub-heading. However, this is not allo

[openstack-dev] How to add a property to the API extension?

Hi, Christopher, I have some question to the API changes related to https://review.openstack.org/#/c/80707/4/nova/api/openstack/compute/plugins/v3/hypervisors.py , which adds a property to the hypervisor information. a) I checked the https://wiki.openstack.org/wiki/APIChangeGuidelines bu

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

Sorry about that. It should be readable now. From: Eugene Nikanorov [enikano...@mirantis.com] Sent: Wednesday, April 16, 2014 3:51 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron][LBaaS] Requirements and API

Re: [openstack-dev] [Fuel] Code merge policy

I don't think requiring a +1 from every single reviewer listed on the review before merging it is reasonable. Every day a review that is ready to be merged spends waiting means more time spent rebasing, redoing the reviews, dealing with immediate and hidden problems caused by changes in master bra

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

Hi Brandon, Seems that doc has not been made public, so please share. Thanks, Eugene. On Thu, Apr 17, 2014 at 12:39 AM, Brandon Logan wrote: > Here is Jorge and team’s API proposal based on Atlas. The document has > some questions and answers about why decisions were made. Feel free to > o

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

Here is Jorge and team’s API proposal based on Atlas. The document has some questions and answers about why decisions were made. Feel free to open up a discussion about these questions and answers and really about anything. This can be changed up to fit any flaws or use cases we missed that

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

I would prefer not to be strict on the requirements for diagrams. If it looks ok in ascii - that's fine, nwdiag is fine as well. I think both of tools worth mentioning in bp template. Thanks, Eugene. On Thu, Apr 17, 2014 at 12:06 AM, Alan Kavanagh wrote: > Tend to agree Nachi, that would be my

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

Tend to agree Nachi, that would be my preference, especially when the diagrams are fairly complex which is the case most of the time in Neutron. However if the BP is long lived then I think it makes sense to use ASCII, but if its short for a small feature to be included in next release then I ag

[openstack-dev] [Neutron][L3] Team Meeting Thursday at 1500 UTC

Tomorrow's meeting will be at 1500 UTC in #openstack-meeting-3. The current agenda can be found on the subteam meeting page [1]. As discussed in the Neutron meeting on Monday, there is a new agenda item this week: "L3 Vendor plugins". Paul Michali (pcm) has proposed a summit topic on this [2].

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

I think Ascii diagrams do make sense if the Blueprint is a major architecture input and will be long lived through many Os cycles, if it's a small short feature and the diagram is useful to describe the architecture then I think its overly painful, speaking from experience! Alan -Original

Re: [openstack-dev] [infra][nova][docker]

Hi Eric, 2014-04-16 21:06 GMT+02:00 Eric Windisch : > >> > As I really would like to keep a 1:1 matching with my current Devstack >> > installation, have you tried to trick Dockenstack by modifying the >> > localrc file to say Qemu as the driver ? >> > > Not yet, but I'd like to. It has been a s

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

On 04/16/2014 11:07 AM, Mike Spreitzer wrote: 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 t

Re: [openstack-dev] [infra][nova][docker]

On 04/16/2014 03:06 PM, Eric Windisch wrote: > > > As I really would like to keep a 1:1 matching with my current Devstack > > installation, have you tried to trick Dockenstack by modifying the > > localrc file to say Qemu as the driver ? > > > Not yet, but I'd like to. It has been a

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

On 04/16/2014 09:24 AM, Fox, Kevin M wrote: 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

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

I thought that OpenStack just support one release backwards, if we have to support three versions, this is not useful. There are already ways to enable/disable modules in tempest to adapt to each deployment needs. Just wanted to avoid more configuration options. On 16 April 2014 21:14, David K

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

Nice!! nwdiag would make things really easy. -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

Hi folks I don't think to use ASCII digrams is good idea because it is hard to maintenance & update diagrams.. so I would like to recommend Blockdiag & Netdiag which are plugins for sphinx. Blockdiag http://blockdiag.com/en/blockdiag/ blockdiag { A -> B -> C -> D; A -> E -> F -> G; } wil

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 not and

Re: [openstack-dev] [oslo] starting regular meetings

bnemec pointed out that the 18th is Good Friday, and many people are likely to have the day off, so we should start this next week on 25 April. It appears that we have a consensus that 1600 UTC works as a new time, so let's make both moves at the same time. Our next meeting will be Friday 25 April

[openstack-dev] [QA] Meeting Thursday April 17th at 22:00UTC

Just a quick reminder that the weekly OpenStack QA team IRC meeting will be tomorrow Thursday, April 17th at 22:00 UTC in the #openstack-meeting channel. The agenda for tomorrow's meeting can be found here: https://wiki.openstack.org/wiki/Meetings/QATeamMeeting Anyone is welcome to add an item to

Re: [openstack-dev] [infra][nova][docker]

> > > > As I really would like to keep a 1:1 matching with my current Devstack > > installation, have you tried to trick Dockenstack by modifying the > > localrc file to say Qemu as the driver ? > Not yet, but I'd like to. It has been a secondary goal at this point. I have successfully tested with

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

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] 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

[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

[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

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

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] 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] [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] [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] [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] [Neutron][LBaaS] Requirements and API revision progress

On Apr 14, 2014, at 8:20 PM, Stephen Balukoff mailto:sbaluk...@bluebox.net>> 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

> 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] 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] 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 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] [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] [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: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

[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] [neutron] Neutron BP review process for Juno

On Wed, Apr 16, 2014 at 11:05 AM, trinath.soman...@freescale.com 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].

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] [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] [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] [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

  1   2   >