Re: [Openstack] swift and disk usage

2013-05-11 Thread Christian Schwede
Hi Paras, Am 08.05.13 22:02, schrieb Paras pradhan: Thanks Christian. How do we keep track of the usage? For example with 5 nodes i.e 40TB. How do we know how much space has been consumed out of this 40TB? well, that depends on the used authentication scheme. If you are using swauth and don't

[Openstack] Devstack usage in Install Openstack

2013-05-11 Thread Mahzad Zahedi
Hi Dear All I had installed openstack using Devstack so dashboard (horizon) was shown. But how to add my ESXi servers and so on to it ? what is usage of dashboard? is it just a demo?? Or we must configure it to utilize?? Plz help me .if using Devstack is just a demo i should go to install real

Re: [Openstack] Allocating dynamic IP to the VMs

2013-05-11 Thread Chathura M. Sarathchandra Magurawalage
Hello Sylvain, I am sorry I got caught up with another project in the past few weeks, hence my late reply. Please bare with me. The floating ip is bound to the qg-550803ee-ce bridge. root@controller:~# ip a 1: lo: LOOPBACK,UP,LOWER_UP mtu 16436 qdisc noqueue state UNKNOWN link/loopback

Re: [Openstack] [openstack-community] [Ask] Guidelines for answering question on Ask

2013-05-11 Thread John Wong
Can we have a template? I think it would be really helpful if by default there is a template / form to fill out. Not sure if the underlying software has that mechanism. Basically to do support, it'd really important to know the version used, system. Thoughts? John On Fri, May 10, 2013 at

Re: [Openstack] Devstack usage in Install Openstack

2013-05-11 Thread Dean Troyer
On Sat, May 11, 2013 at 3:30 AM, Mahzad Zahedi ict.mywork2...@gmail.com wrote: But how to add my ESXi servers and so on to it ? what is usage of dashboard? is it just a demo?? ... Plz help me .if using Devstack is just a demo i should go to install real openstack. DevStack is designed to be a

Re: [Openstack] A Grizzly GRE failure

2013-05-11 Thread Greg Chavez
So to be clear: * I have a three nics on my network node. The VM traffic goes out the 1st nic on 192.168.239.99/24 to the other compute nodes, while management traffic goes out the 2nd nic on 192.168.241.99. The 3rd nic is external and has no IP. * I have four GRE endpoints on the VM network,

Re: [Openstack] API version in Grizzly

2013-05-11 Thread Devendra Gupta
Thanks! Gabriel. I understood. Devendra On 10-May-13 11:46 PM, Gabriel Hurley wrote: When you say Identity v3.0 development is going on side-by-side so I think if I have Grizzly setup with Identity v2.0 then it'll be upgraded to Identity v3.0 with Grizzly when new version is available in

[Openstack] New code name for networks

2013-05-11 Thread Jason Smith
Hello, I understand why we had to give up Quantum code name but rather than just refer to it as networking let's come up with a new code name! Thoughts? Thanks, -js ___ Mailing list: https://launchpad.net/~openstack Post to :

Re: [Openstack] New code name for networks

2013-05-11 Thread Mark Turner
Tubes ;-) On Sat, May 11, 2013 at 12:51 PM, Jason Smith jason.sm...@rackspace.com wrote: Hello, I understand why we had to give up Quantum code name but rather than just refer to it as networking let's come up with a new code name! Thoughts? Thanks, -js

Re: [Openstack] New code name for networks

2013-05-11 Thread Davanum Srinivas
Lattice -- dims On Sat, May 11, 2013 at 3:52 PM, Mark Turner m...@amerine.net wrote: Tubes ;-) On Sat, May 11, 2013 at 12:51 PM, Jason Smith jason.sm...@rackspace.com wrote: Hello, I understand why we had to give up Quantum code name but rather than just refer to it as networking

Re: [Openstack] New code name for networks

2013-05-11 Thread Matt Joyce
Tyronosaurus Rex Optimus Prime Super Happy Fun Network Times A.N.A.L. - Automated Networking and Logistics And with that I am out of ideas. On Sat, May 11, 2013 at 12:58 PM, Davanum Srinivas dava...@gmail.comwrote: Lattice -- dims On Sat, May 11, 2013 at 3:52 PM, Mark Turner

Re: [Openstack] New code name for networks

2013-05-11 Thread Monty Taylor
I have been arguing for: mutnuaq Granted, it takes a minute to learn how to type, but it's just a little snarky, and it takes up the exact same number of letter. However, it does screw with sorting. SO - what about: qumutna It's a little bit easier to wrap your head around, it's still clearly

Re: [Openstack] New code name for networks

2013-05-11 Thread Asher Newcomer
Or even better, just continue to call it openstack networking. The code names only serve to confuse the uninitiated. They needlessly steepen the learning curve and slow uptake. On May 11, 2013 3:59 PM, Davanum Srinivas dava...@gmail.com wrote: Lattice -- dims On Sat, May 11, 2013 at 3:52 PM,

Re: [Openstack] New code name for networks

2013-05-11 Thread Monty Taylor
On 05/11/2013 04:07 PM, Asher Newcomer wrote: Or even better, just continue to call it openstack networking. The code names only serve to confuse the uninitiated. They needlessly steepen the learning curve and slow uptake. The problem with OpenStack Networking (or getting rid of codenames)

Re: [Openstack] New code name for networks

2013-05-11 Thread Monty Taylor
Jeremy Stanly on IRC just suggested kumquat... but to that I respond: qumkuat Same benefits as qumutna - except it's more pronouncable. On 05/11/2013 04:07 PM, Monty Taylor wrote: I have been arguing for: mutnuaq Granted, it takes a minute to learn how to type, but it's just a little

Re: [Openstack] New code name for networks

2013-05-11 Thread MoE ElBaz
Réseaux or a translation for networks in some other language (maybe networks in Chinese as Havana will be released in HKG) -- just thinking international ;-) Best Regards MoE/// On May 11, 2013, at 4:07 PM, Monty Taylor mord...@inaugust.com wrote: I have been arguing for: mutnuaq

Re: [Openstack] Guest PXE Boot

2013-05-11 Thread Monty Taylor
Neat! Have you seen any of the work around nova baremetal (which is transitioning to be called ironic?) Related to that is a set of virtual power drivers which allow for treating virtual machines like real machines - so that you can use nova to pxe boot a kvm or a virtualbox or a vmware instance.

Re: [Openstack] [OpenStack Marketing] New code name for networks

2013-05-11 Thread Sean Roberts
Octopus ~sean On May 11, 2013, at 12:57 PM, Jason Smith jason.sm...@rackspace.com wrote: Hello, I understand why we had to give up Quantum code name but rather than just refer to it as networking let's come up with a new code name! Thoughts? Thanks, -js

Re: [Openstack] New code name for networks

2013-05-11 Thread Anne Gentle
On Sat, May 11, 2013 at 3:12 PM, Monty Taylor mord...@inaugust.com wrote: On 05/11/2013 04:07 PM, Asher Newcomer wrote: Or even better, just continue to call it openstack networking. The code names only serve to confuse the uninitiated. They needlessly steepen the learning curve and slow

Re: [Openstack] New code name for networks

2013-05-11 Thread Jeremy Stanley
On 2013-05-11 16:13:39 -0400 (-0400), Monty Taylor wrote: Jeremy Stanly on IRC just suggested kumquat... [...] Only because I find them extremely tasty and fun to pronounce. -- Jeremy Stanley ___ Mailing list: https://launchpad.net/~openstack Post to

Re: [Openstack] New code name for networks

2013-05-11 Thread Davanum Srinivas
Anne, Here's the guidance provided by ASF for their Incubator Podlings which can be used to come up with a process of our own. http://incubator.apache.org/guides/names.html -- dims On Sat, May 11, 2013 at 5:48 PM, Anne Gentle a...@openstack.org wrote: On Sat, May 11, 2013 at 3:12 PM, Monty

Re: [Openstack] New code name for networks

2013-05-11 Thread David Shrewsbury
quark Keeps the sciency theme going, same first two letters, and represents something fundamental to other sciency stuff (much like networking is fundamental to OpenStack). http://en.wikipedia.org/wiki/Quark -Dave On May 11, 2013, at 4:13 PM, Monty Taylor mord...@inaugust.com wrote: Jeremy

Re: [Openstack] New code name for networks

2013-05-11 Thread David Shrewsbury
Same first THREE letters actually. Bonus points. On May 11, 2013, at 7:07 PM, David Shrewsbury shrewsbury.d...@gmail.com wrote: quark Keeps the sciency theme going, same first two letters, and represents something fundamental to other sciency stuff (much like networking is fundamental to

Re: [Openstack] New code name for networks

2013-05-11 Thread Monty Taylor
On 05/11/2013 05:48 PM, Anne Gentle wrote: On Sat, May 11, 2013 at 3:12 PM, Monty Taylor mord...@inaugust..com mailto:mord...@inaugust.com wrote: On 05/11/2013 04:07 PM, Asher Newcomer wrote: Or even better, just continue to call it openstack networking. The code

Re: [Openstack] New code name for networks

2013-05-11 Thread Rick Jones
On 05/11/2013 01:07 PM, Monty Taylor wrote: I have been arguing for: mutnuaq As someone who named a netperf test MAERTS because it transfered data the opposite direction as the STREAM test, I'm good with that. If that does not work, with Quantum being something of Spooky networking at a

Re: [Openstack] New code name for networks

2013-05-11 Thread Anne Gentle
On Sat, May 11, 2013 at 6:43 PM, Monty Taylor mord...@inaugust.com wrote: On 05/11/2013 05:48 PM, Anne Gentle wrote: On Sat, May 11, 2013 at 3:12 PM, Monty Taylor mord...@inaugust..com mailto:mord...@inaugust.com wrote: On 05/11/2013 04:07 PM, Asher Newcomer wrote:

Re: [Openstack] New code name for networks

2013-05-11 Thread Sumit Naiksatam
How about netstack? We had originally coined this name for the collection of quantum, melange, and donabe services. Melange got folded into Quantum, so we stopped using netstack. But Quantum today is actually a collection of network services, both for network connectivity, and also for more

Re: [Openstack] New code name for networks

2013-05-11 Thread Brad Knowles
On May 11, 2013, at 10:02 PM, Sumit Naiksatam sumitnaiksa...@gmail.com wrote: How about netstack? We had originally coined this name for the collection of quantum, melange, and donabe services. Melange got folded into Quantum, so we stopped using netstack. If you want to start re-naming

Re: [Openstack] New code name for networks

2013-05-11 Thread Brad Knowles
On May 11, 2013, at 10:02 PM, Sumit Naiksatam sumitnaiksa...@gmail.com wrote: How about netstack? We had originally coined this name for the collection of quantum, melange, and donabe services. Melange got folded into Quantum, so we stopped using netstack. If you want to start re-naming

Re: [Openstack] New code name for networks

2013-05-11 Thread John Wong
Hi all: I actually like Quantum. I think that name has embedded into my brain for so long that I often refuse to look at an alternative name. What's the reason? Did I miss out the actual reason behind it? Anyway, I propose *Neptune.* 1. It has the net sound in it, and 2. Neptune as God of Sea.

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_havana_cinder_trunk #49

2013-05-11 Thread openstack-testing-bot
Title: precise_havana_cinder_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_cinder_trunk/49/Project:precise_havana_cinder_trunkDate of build:Sat, 11 May 2013 02:00:22 -0400Build duration:1 min 21 secBuild cause:Started by an SCM changeBuilt

[Openstack-ubuntu-testing-notifications] Build Still Failing: saucy_havana_cinder_trunk #17

2013-05-11 Thread openstack-testing-bot
Title: saucy_havana_cinder_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/saucy_havana_cinder_trunk/17/Project:saucy_havana_cinder_trunkDate of build:Sat, 11 May 2013 02:00:23 -0400Build duration:1 min 52 secBuild cause:Started by an SCM changeBuilt

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_havana_quantum_trunk #107

2013-05-11 Thread openstack-testing-bot
Title: precise_havana_quantum_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_quantum_trunk/107/Project:precise_havana_quantum_trunkDate of build:Sat, 11 May 2013 04:00:22 -0400Build duration:2 min 46 secBuild cause:Started by an SCM changeBuilt

[Openstack-ubuntu-testing-notifications] Build Still Failing: saucy_havana_quantum_trunk #37

2013-05-11 Thread openstack-testing-bot
Title: saucy_havana_quantum_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/saucy_havana_quantum_trunk/37/Project:saucy_havana_quantum_trunkDate of build:Sat, 11 May 2013 04:00:23 -0400Build duration:6 min 30 secBuild cause:Started by an SCM changeBuilt