Re: [Openstack] centos5.5_64bit image for openstack

[Romil Gupta]

Hi Yanchen,

You can get it from the below link :
http://isoredirect.centos.org/centos/5/isos/x86_64/


On Fri, May 10, 2013 at 10:00 PM, yan ch yyan...@gmail.com wrote:

 Hello,

 Is there anyone build CentOS5.5_64bit image for openstack ?

 If someone own it, can you send it to my gmail.

 Thank you !

 Regards,

 yanchen




 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp




-- 
*Thanks  Regards,*
*Romil Gupta
*
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] centos5.5_64bit image for openstack

[Ray Sun]

Rakespace provide a lot of openstack images here:

https://github.com/rackerjoe/oz-image-build

You can create your own image followed document and install cloud-init,
that will be the same with Rakespace provide.

Best Regards
-- Ray


On Sat, May 11, 2013 at 12:30 AM, yan ch yyan...@gmail.com wrote:

 Hello,

 Is there anyone build CentOS5.5_64bit image for openstack ?

 If someone own it, can you send it to my gmail.

 Thank you !

 Regards,

 yanchen




 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] centos5.5_64bit image for openstack

[Razique Mahroua]

Thanks for the link :)
Razique Mahroua-Nuage  Corazique.mahr...@gmail.comTel: +33 9 72 37 94 15

Le 12 mai 2013 à 10:12, Romil Gupta romilgupt...@gmail.com a écrit :Hi Yanchen,You can get it from the below link :http://isoredirect.centos.org/centos/5/isos/x86_64/
On Fri, May 10, 2013 at 10:00 PM, yan ch yyan...@gmail.com wrote:
Hello,Is there anyone build CentOS5.5_64bit image for openstack ?
If someone own it, can you send it to my gmail.Thank you !
Regards,yanchen
___
Mailing list: https://launchpad.net/~openstack
Post to   : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help  : https://help.launchpad.net/ListHelp
-- Thanks  Regards,Romil Gupta

___Mailing list: https://launchpad.net/~openstackPost to : openstack@lists.launchpad.netUnsubscribe : https://launchpad.net/~openstackMore help : https://help.launchpad.net/ListHelp___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

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

[Mark McLoughlin]

On Sat, 2013-05-11 at 19:50 +, Jason Smith 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!

Yes, this was discussed at the summit:

  https://etherpad.openstack.org/ProjectsReNaming

The conclusion was that a number of choices for a new name would be put
forward and that Quantum's contributors would vote for one of those
choices.

Cheers,
Mark.


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

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

[Jason Smith]

Excellent! I was not aware of that discussion.  

Thanks,
-js

On May 12, 2013, at 8:14 AM, Mark McLoughlin mar...@redhat.com
 wrote:

 On Sat, 2013-05-11 at 19:50 +, Jason Smith 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!
 
 Yes, this was discussed at the summit:
 
  https://etherpad.openstack.org/ProjectsReNaming
 
 The conclusion was that a number of choices for a new name would be put
 forward and that Quantum's contributors would vote for one of those
 choices.
 
 Cheers,
 Mark.
 


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] A Grizzly GRE failure [SOLVED]

[Greg Chavez]

I've had a terrible time getting the community to help me with this
problem.  So special thanks to Darragh O'Reilly and rkeene on
#openstack who was mean and a bit of a wisenheimer (I'd use different
words elsewhere), but at least he talked to me and got me to think
twice about my GRE setup.

But enough of that, problem solved and a bug report has been
submitted: https://bugs.launchpad.net/quantum/+bug/1179223..  I added
an s to the front of persists in the subject, but whatever.  I
always leave one thing in the hotel room, and I always leave one
embarrassing typo.

Here's the part explaining how it was fixed:

SOLUTION:

mysql delete from ovs_tunnel_endpoints where id = 1;
Query OK, 1 row affected (0.00 sec)

mysql select * from ovs_tunnel_endpoints;
+-++
| ip_address | id |
+-++
| 192.168.239.110 | 3 |
| 192.168.239.114 | 4 |
| 192.168.239.115 | 5 |
| 192.168.239.99 | 2 |
+-++
4 rows in set (0.00 sec)

* After doing that, I simply restarted the quantum ovs agents on the
network and compute nodes. The old GRE tunnel is not re-created.
Thereafter, VM network traffic to and from the external network
proceeds without incident.

* Should these tables be cleaned up as well, I wonder:

mysql select * from ovs_network_bindings;
+--+--+--+-+
| network_id | network_type | physical_network | segmentation_id |
+--+--+--+-+
| 4e8aacca-8b38-40ac-a628-18cac3168fe6 | gre | NULL | 2 |
| af224f3f-8de6-4e0d-b043-6bcd5cb014c5 | gre | NULL | 1 |
+--+--+--+-+
2 rows in set (0.00 sec)

mysql select * from ovs_tunnel_allocations where allocated != 0;
+---+---+
| tunnel_id | allocated |
+---+---+
| 1 | 1 |
| 2 | 1 |
+---+---+
2 rows in set (0.00 sec)

Cheers, and happy openstacking.  Even you, rkeene!

--Greg Chavez

On Sat, May 11, 2013 at 2:28 PM, Greg Chavez greg.cha...@gmail.com wrote:
 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, one at the network node
 (192.168.239.99) and three on compute nodes
 (192.168.239.{110,114,115}), all with IDs 2-5.

 * I have a fifth GRE endpoint with id 1 to 192.168.241.99, the network
 node's management interface.  This was the first tunnel created when I
 deployed the network node because that is how I set the remote_ip in
 the ovs plugin ini.  I corrected the setting later, but the
 192.168.241.99 endpoint persists and,  as your response implies, *this
 extraneous endpoint is the cause of my troubles*.

 My next question then is what is happening? My guess:

 * I ping a guest from the external network using its floater (10.21.166.4).

 * It gets NAT'd at the tenant router on the network node to
 192.168.252.3, at which point an arp request is sent over the unified
 GRE broadcast domain.

 * On a compute node, the arp request is received by the VM, which then
 sends a reply to the tenant router's MAC (which I verified with
 tcpdumps).

 * There are four endpoints for the packet to go down:

 Bridge br-tun
 Port br-tun
 Interface br-tun
 type: internal
 Port gre-1
 Interface gre-1
 type: gre
 options: {in_key=flow, out_key=flow, 
 remote_ip=192.168.241.99}
 Port gre-4
 Interface gre-4
 type: gre
 options: {in_key=flow, out_key=flow,
 remote_ip=192.168.239.114}
 Port gre-3
 Interface gre-3
 type: gre
 options: {in_key=flow, out_key=flow,
 remote_ip=192.168.239.110}
 Port patch-int
 Interface patch-int
 type: patch
 options: {peer=patch-tun}
 Port gre-2
 Interface gre-2
 type: gre
 options: {in_key=flow, out_key=flow, 
 remote_ip=192.168.239.99}

 Here's where I get confused.  Does it know that gre-1 is a different
 broadcast domain than the others, or does is see all endpoints as the
 same domain?

 What happens here?  Is this the cause of my network timeouts on
 external connections to the VMs? Does this also explain the sporadic
 nature of the timeouts, why they aren't consistent in frequency or
 duration?

 Finally, what happens when I remove the oddball endpoint from the DB?
 Sounds risky!

 Thanks for your help
 --Greg Chavez

 On Fri, May 10, 2013 at 7:17 PM, Darragh O'Reilly
 dara2002-openst...@yahoo.com wrote:
 I'm not sure how to rectify that. You may have to delete the bad row from 
 the DB and 

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

[Mark Collier]

And the foundation will try to vet and filter the list before the vote to 
reduce the likelihood of a repeat of the Quantum situation.  You can use me as 
the point of contact for that and I'll work with our trademark legal team.
 
 
 
On Sunday, May 12, 2013 8:14am, Mark McLoughlin mar...@redhat.com said:



 On Sat, 2013-05-11 at 19:50 +, Jason Smith 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!
 
 Yes, this was discussed at the summit:
 
   https://etherpad.openstack.org/ProjectsReNaming
 
 The conclusion was that a number of choices for a new name would be put
 forward and that Quantum's contributors would vote for one of those
 choices.
 
 Cheers,
 Mark.
 
 
 ___
 Marketing mailing list
 market...@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/marketing
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Allocating dynamic IP to the VMs

[Chathura M. Sarathchandra Magurawalage]

any idea, anyone?

On 11 May 2013 10:37, Chathura M. Sarathchandra Magurawalage 
77.chath...@gmail.com wrote:

 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 00:00:00:00:00:00 brd 00:00:00:00:00:00
 inet 127.0.0.1/8 scope host lo
 inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc mq state UP qlen
 1000
 link/ether d4:ae:52:bb:aa:20 brd ff:ff:ff:ff:ff:ff
 inet 192.168.2.225/24 brd 192.168.2.255 scope global eth0
 inet6 fe80::d6ae:52ff:febb:aa20/64 scope link
valid_lft forever preferred_lft forever
 3: eth1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc mq state UP qlen
 1000
 link/ether d4:ae:52:bb:aa:21 brd ff:ff:ff:ff:ff:ff
 inet 10.10.10.1/24 brd 10.10.10.255 scope global eth1
 inet6 fe80::d6ae:52ff:febb:aa21/64 scope link
valid_lft forever preferred_lft forever
  31: br-int: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN
 link/ether e6:fe:c6:5e:73:47 brd ff:ff:ff:ff:ff:ff
 32: br-ex: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc noqueue state
 UNKNOWN
 link/ether f6:26:0f:0d:32:45 brd ff:ff:ff:ff:ff:ff
 inet6 fe80::f426:fff:fe0d:3245/64 scope link
valid_lft forever preferred_lft forever
 33: tapd648cfe0-f6: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc
 noqueue state UNKNOWN
 link/ether fa:16:3e:9a:2c:29 brd ff:ff:ff:ff:ff:ff
 inet 10.5.5.2/24 brd 10.5.5.255 scope global tapd648cfe0-f6
 inet6 fe80::f816:3eff:fe9a:2c29/64 scope link
valid_lft forever preferred_lft forever
 34: br-tun: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN
 link/ether 5e:2b:f9:ca:c6:40 brd ff:ff:ff:ff:ff:ff
 35: qr-9e818b07-92: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc
 noqueue state UNKNOWN
 link/ether fa:16:3e:01:48:1d brd ff:ff:ff:ff:ff:ff
 inet 10.5.5.1/24 brd 10.5.5.255 scope global qr-9e818b07-92
 inet6 fe80::f816:3eff:fe01:481d/64 scope link
valid_lft forever preferred_lft forever
 36: qg-550803ee-ce: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc
 noqueue state UNKNOWN
 link/ether fa:16:3e:fc:87:1c brd ff:ff:ff:ff:ff:ff
 inet 192.168.2.151/24 brd 192.168.2.255 scope global qg-550803ee-ce
 inet 192.168.2.152/32 brd 192.168.2.152 scope global qg-550803ee-ce
 inet6 fe80::f816:3eff:fefc:871c/64 scope link
valid_lft forever preferred_lft forever

 But I can not ping the floating ip.

 root@controller:~# quantum net-list -- --router:external True

 +-+--+---+
 | id  | name   |
  subnets   |

 ++---+---+
 | a83c3409-6c79-4bb7-9557-010f3b56024f  | ext_net |
 fb3439f4-2afa-4cdc-86a6-aaee2ce1a3a3  |

 ++---+---+

 root@controller:~# quantum floatingip-list

 +---+--+++
 | id  |
 fixed_ip_address | floating_ip_address | port_id
|

 ++-+++
 | 46311a66-5793-43af-be74-612580e505ca | 10.5.5.3  |
 192.168.2.152   | 529f6c56-8037-489a-a120-b97675d1745f  |
 +--
 -+-+++

 Any idea?


 On 25 March 2013 16:09, Sylvain Bauza sylvain.ba...@digimind.com wrote:

  Le 25/03/2013 16:00, Chathura M. Sarathchandra Magurawalage a écrit :


 I can not see anything going through qg- interface.


 Your iptables seem correct.
 Could you please ip a and make sure floating ip is bound to qg- ?

 Are you sure that floating IPs are working properly on your setup ?

 -Sylvain



___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] New code name for networks

[Monty Taylor]

On 05/11/2013 08:58 PM, Anne Gentle wrote:
 
 
 
 On Sat, May 11, 2013 at 6:43 PM, Monty Taylor mord...@inaugust..com
 mailto: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 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
   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) is
  seen with pre-incubation-incubation-integrated cycle.
 
  A project cannot call itself OpenStack Foo until it actually
 _is_
  openstack foo. So any new project by necessity has to start off as
  something else.
 
  But - if we then require them to drop that name and become
 openstack foo
  when they become incubated or integrated, then we've got
 what's become a
  stable project with a decent amount of contributors renaming
 itself.
 
  Every. Time.
 
  The code names aren't just cute. I kind of wish they were,
 because it
  would make several things much easier if we could just ditch
 them and do
  a pure openstack. code namespace. But the reality is that it
 gets really
  really tricky to deal with a bunch of things if they go away.
 
 
  I told Monty and the TC this at the Summit (sorry I couldn't
 attend the
  session about code names).
 
 I promise, it wasn't the world's most fun session. :)
 
 
 I'm sure. :) I think I don't have much regret but do feel sorry that I
 don't know more. 
  
 
 
  I find this trickiness a weak argument in the
  face of the invented names that are getting to be as bad as U.S.
  pharmaceuticals. Plus it forces us to put a lookup table in the docs
  forever. [1] Let's find a process for naming that meets a few reqs:
  - describes the service
  - goes through a legal review
  - enables new eyes to understanding it by reading the English word
 that
  the service represents (that can be translated into a meaningful
 word in
  other languages)
 
 I don't think it's a weak argument at all. There are real technical
 issues.
 
 
 The technical issues, to me, and I may be missing something, are when
 the name is used as:
 - service/daemon name
 - command/CLI name

And the directories in the code where those things live, and the name of
the python package that gets installed, and the name of the client
library used to connect to it.

 You can use any pet name you want for your team and project while
 addressing technical issues some other way? 
 
 Here's another way I'm looking at the naming autonomy/process. Why
 incubate? 
 - you get to pick your cool name
 OR
 - you get access to infrastructure, tools, events, community, and
 branding that is OpenStack
 
 The naming can't be THAT crucial. I get that we want projects to be fun
 to work on. But it can't be just the naming that brings the fun.

I don't think having a cool name is interesting or important at all.
Not one little bit. If any part of this was about esprit de corps or
team bonding or identity I'd be 100% on board with the no-codenames
approach.

Also, to be clear, I don't think there are any problems with using
non-codename for identification. Already, as part of the upgrade of our
build stuff to PBR I've been setting the project short description to
the non-codename. So, nova's is OpenStack Compute I think that's a
great idea, and it's important.

Equally as important, although harder, is that we should all try our
best to use the non-codenames when we're talking about official
projects. It's not going to work or be 100% covered - but we should all
make a best-effort.

(these are all things that did come out of that session - perhaps one of
us should do a writeup on that?)

The thing that _I'm_ sticking on is the above list of technical issues.
What is the daemon named? What is the command line tool named? What is
directory in which the code lives?

Those may seem trivial, but those are the primary interface that a
developer and deployer has with the project. And it's an issue because
of the lifecycle of these code projects before they are integrated. It's
not ok for moniker to call it's API daemon openstack-dns-api until
it's actually openstack DNS. It has to call itself something though.
That's where names come in. It's a practical thing that there must be a
name.

And let's be honest - it's my least favorite part of making a project.
So much so that our CI project which makes jenkins jobs from yaml files
is called jenkins-job-builder and the 

Re: [Openstack] New code name for networks

[Colin McNamara]

Exceedingly well put.

On Sunday, May 12, 2013, Monty Taylor wrote:



 On 05/11/2013 08:58 PM, Anne Gentle wrote:
 
 
 
  On Sat, May 11, 2013 at 6:43 PM, Monty Taylor mord...@inaugust..com
  mailto:mord...@inaugust.com javascript:; wrote:
 
 
 
  On 05/11/2013 05:48 PM, Anne Gentle wrote:
  
  
  
   On Sat, May 11, 2013 at 3:12 PM, Monty Taylor mordred@inaugust.
 .com
   mailto:mord...@inaugust.com javascript:; mailto:
 mord...@inaugust.com javascript:; 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 uptake.
  
   The problem with OpenStack Networking (or getting rid of
  codenames) is
   seen with pre-incubation-incubation-integrated cycle.
  
   A project cannot call itself OpenStack Foo until it actually
  _is_
   openstack foo. So any new project by necessity has to start
 off as
   something else.
  
   But - if we then require them to drop that name and become
  openstack foo
   when they become incubated or integrated, then we've got
  what's become a
   stable project with a decent amount of contributors renaming
  itself.
  
   Every. Time.
  
   The code names aren't just cute. I kind of wish they were,
  because it
   would make several things much easier if we could just ditch
  them and do
   a pure openstack. code namespace. But the reality is that it
  gets really
   really tricky to deal with a bunch of things if they go away.
  
  
   I told Monty and the TC this at the Summit (sorry I couldn't
  attend the
   session about code names).
 
  I promise, it wasn't the world's most fun session. :)
 
 
  I'm sure. :) I think I don't have much regret but do feel sorry that I
  don't know more.
 
 
 
   I find this trickiness a weak argument in the
   face of the invented names that are getting to be as bad as U.S.
   pharmaceuticals. Plus it forces us to put a lookup table in the
 docs
   forever. [1] Let's find a process for naming that meets a few reqs:
   - describes the service
   - goes through a legal review
   - enables new eyes to understanding it by reading the English word
  that
   the service represents (that can be translated into a meaningful
  word in
   other languages)
 
  I don't think it's a weak argument at all. There are real technical
  issues.
 
 
  The technical issues, to me, and I may be missing something, are when
  the name is used as:
  - service/daemon name
  - command/CLI name

 And the directories in the code where those things live, and the name of
 the python package that gets installed, and the name of the client
 library used to connect to it.

  You can use any pet name you want for your team and project while
  addressing technical issues some other way?
 
  Here's another way I'm looking at the naming autonomy/process. Why
  incubate?
  - you get to pick your cool name
  OR
  - you get access to infrastructure, tools, events, community, and
  branding that is OpenStack
 
  The naming can't be THAT crucial. I get that we want projects to be fun
  to work on. But it can't be just the naming that brings the fun.

 I don't think having a cool name is interesting or important at all.
 Not one little bit. If any part of this was about esprit de corps or
 team bonding or identity I'd be 100% on board with the no-codenames
 approach.

 Also, to be clear, I don't think there are any problems with using
 non-codename for identification. Already, as part of the upgrade of our
 build stuff to PBR I've been setting the project short description to
 the non-codename. So, nova's is OpenStack Compute I think that's a
 great idea, and it's important.

 Equally as important, although harder, is that we should all try our
 best to use the non-codenames when we're talking about official
 projects. It's not going to work or be 100% covered - but we should all
 make a best-effort.

 (these are all things that did come out of that session - perhaps one of
 us should do a writeup on that?)

 The thing that _I'm_ sticking on is the above list of technical issues.
 What is the daemon named? What is the command line tool named? What is
 directory in which the code lives?

 Those may seem trivial, but those are the primary interface that a
 developer and deployer has with the project. And it's an issue because
 of the lifecycle of these code projects before they are integrated. It's
 not ok for moniker to call it's API daemon openstack-dns-api until
 it's actually openstack DNS. It has to call itself something though.
 That's where names come in. It's a practical 

Re: [Openstack] New code name for networks

[Mac Innes, Kiall]

On 12/05/13 16:52, Monty Taylor wrote:
 I mention our erstwhile nascent DNSaaS project as an example
 of pre-incubation... hopefully someone in that project will do the thing
 I just mentioned and will come to us at incubation time with a name that
 is not a CLEAR violation. I mean, we can't be perfect, but we can at
 least try. Because if we try, then it keeps the lawyers out of our
 business - and that's really better for all of us.
sidetrackYup - That came to our attention just last week, we're
looking at a name change already :(/sidetrack

Thanks,
Kiall

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] New code name for networks

[Jacob Godin]

I like this, +1
On 2013-05-11 8:08 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
 OpenStack).

 http://en.wikipedia.org/wiki/Quark

 -Dave


 On May 11, 2013, at 4:13 PM, Monty Taylor mord...@inaugust.com wrote:

  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
  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 an
  homage, and it should be super easy to bulk cut/replace.
 
  On 05/11/2013 03:58 PM, Davanum Srinivas wrote:
  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 let's come up with a new code name!
 
  Thoughts?
 
  Thanks,
  -js
  ___
  Mailing list: https://launchpad.net/~openstack
  Post to : openstack@lists.launchpad.net
  Unsubscribe : https://launchpad.net/~openstack
  More help : https://help.launchpad.net/ListHelp
 
 
 
  ___
  Mailing list: https://launchpad.net/~openstack
  Post to : openstack@lists.launchpad.net
  Unsubscribe : https://launchpad.net/~openstack
  More help   : https://help.launchpad.net/ListHelp
 
 
 
 
 
  ___
  Mailing list: https://launchpad.net/~openstack
  Post to : openstack@lists.launchpad.net
  Unsubscribe : https://launchpad.net/~openstack
  More help   : https://help.launchpad.net/ListHelp
 
 
  ___
  Mailing list: https://launchpad.net/~openstack
  Post to : openstack@lists.launchpad.net
  Unsubscribe : https://launchpad.net/~openstack
  More help   : https://help.launchpad.net/ListHelp


 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] New code name for networks

[Sean Dague]

Quark is also the trademark of a computer software company - 
http://tess2.uspto.gov/bin/showfield?f=docstate=4808:7k4xqd.2.44


This stuff is trickier than you might realize. Hence why car names are 
now all made-ity-up words.


-Sean

On 05/12/2013 12:21 PM, Jacob Godin wrote:

I like this, +1

On 2013-05-11 8:08 PM, David Shrewsbury shrewsbury.d...@gmail.com
mailto: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
OpenStack).

http://en.wikipedia.org/wiki/Quark

-Dave


On May 11, 2013, at 4:13 PM, Monty Taylor mord...@inaugust.com
mailto:mord...@inaugust.com wrote:

  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
  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 an
  homage, and it should be super easy to bulk cut/replace.
 
  On 05/11/2013 03:58 PM, Davanum Srinivas wrote:
  Lattice
 
  -- dims
 
  On Sat, May 11, 2013 at 3:52 PM, Mark Turner m...@amerine.net
mailto:m...@amerine.net wrote:
  Tubes
 
  ;-)
 
 
  On Sat, May 11, 2013 at 12:51 PM, Jason Smith
jason.sm...@rackspace.com mailto: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
  ___
  Mailing list: https://launchpad.net/~openstack
  Post to : openstack@lists.launchpad.net
mailto:openstack@lists.launchpad.net
  Unsubscribe : https://launchpad.net/~openstack
  More help : https://help.launchpad.net/ListHelp
 
 
 
  ___
  Mailing list: https://launchpad.net/~openstack
  Post to : openstack@lists.launchpad.net
mailto:openstack@lists.launchpad.net
  Unsubscribe : https://launchpad.net/~openstack
  More help   : https://help.launchpad.net/ListHelp
 
 
 
 
 
  ___
  Mailing list: https://launchpad.net/~openstack
  Post to : openstack@lists.launchpad.net
mailto:openstack@lists.launchpad.net
  Unsubscribe : https://launchpad.net/~openstack
  More help   : https://help.launchpad.net/ListHelp
 
 
  ___
  Mailing list: https://launchpad.net/~openstack
  Post to : openstack@lists.launchpad.net
mailto:openstack@lists.launchpad.net
  Unsubscribe : https://launchpad.net/~openstack
  More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
mailto:openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp




--
Sean Dague
http://dague.net

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] New code name for networks

[John Wong]

Cool.
I think I did a search here:
http://tmsearch.uspto.gov/bin/gate.exe?f=searchssstate=4804:3j8874.1.1
for Netpune.

Are we only concern with registered trademark? I am sure a lot of names we
come up with are either full or partial of some company's name. What's the
bottom line?
Who's going to come up the list of names? Where do we put our suggestion?
For the next OS release we have a Wiki page setup. Do we have a Wiki page
setup yet?

Best,
John


On Sun, May 12, 2013 at 12:27 PM, Sean Dague s...@dague.net wrote:

 Quark is also the trademark of a computer software company -
 http://tess2.uspto.gov/bin/**showfield?f=docstate=4808:**7k4xqd.2.44http://tess2.uspto.gov/bin/showfield?f=docstate=4808:7k4xqd.2.44

 This stuff is trickier than you might realize. Hence why car names are now
 all made-ity-up words.

 -Sean


 On 05/12/2013 12:21 PM, Jacob Godin wrote:

 I like this, +1

 On 2013-05-11 8:08 PM, David Shrewsbury shrewsbury.d...@gmail.com
 mailto:shrewsbury.dave@gmail.**com 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
 OpenStack).

 http://en.wikipedia.org/wiki/**Quarkhttp://en.wikipedia.org/wiki/Quark

 -Dave


 On May 11, 2013, at 4:13 PM, Monty Taylor mord...@inaugust.com
 mailto:mord...@inaugust.com wrote:

   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
   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 an
   homage, and it should be super easy to bulk cut/replace.
  
   On 05/11/2013 03:58 PM, Davanum Srinivas wrote:
   Lattice
  
   -- dims
  
   On Sat, May 11, 2013 at 3:52 PM, Mark Turner m...@amerine.net
 mailto:m...@amerine.net wrote:
   Tubes
  
   ;-)
  
  
   On Sat, May 11, 2013 at 12:51 PM, Jason Smith
 jason.sm...@rackspace.com 
 mailto:jason.smith@rackspace.**comjason.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
   __**_
   Mailing list: 
 https://launchpad.net/~**openstackhttps://launchpad.net/~openstack
   Post to : openstack@lists.launchpad.net
 mailto:openstack@lists.**launchpad.netopenstack@lists.launchpad.net
 

   Unsubscribe : 
 https://launchpad.net/~**openstackhttps://launchpad.net/~openstack
   More help : 
 https://help.launchpad.net/**ListHelphttps://help.launchpad.net/ListHelp
  
  
  
   __**_
   Mailing list: 
 https://launchpad.net/~**openstackhttps://launchpad.net/~openstack
   Post to : openstack@lists.launchpad.net
 mailto:openstack@lists.**launchpad.netopenstack@lists.launchpad.net
 

   Unsubscribe : 
 https://launchpad.net/~**openstackhttps://launchpad.net/~openstack
   More help   : 
 https://help.launchpad.net/**ListHelphttps://help.launchpad.net/ListHelp
  
  
  
  
  
   __**_
   Mailing list: 
 https://launchpad.net/~**openstackhttps://launchpad.net/~openstack
   Post to : openstack@lists.launchpad.net
 mailto:openstack@lists.**launchpad.netopenstack@lists.launchpad.net
 

   Unsubscribe : 
 https://launchpad.net/~**openstackhttps://launchpad.net/~openstack
   More help   : 
 https://help.launchpad.net/**ListHelphttps://help.launchpad.net/ListHelp
  
  
   __**_
   Mailing list: 
 https://launchpad.net/~**openstackhttps://launchpad.net/~openstack
   Post to : openstack@lists.launchpad.net
 mailto:openstack@lists.**launchpad.netopenstack@lists.launchpad.net
 

   Unsubscribe : 
 https://launchpad.net/~**openstackhttps://launchpad.net/~openstack
   More help   : 
 https://help.launchpad.net/**ListHelphttps://help.launchpad.net/ListHelp


 __**_
 Mailing list: 
 https://launchpad.net/~**openstackhttps://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 mailto:openstack@lists.**launchpad.netopenstack@lists.launchpad.net
 

 Unsubscribe : 
 

[Openstack] Swift questions.

[Mark Brown]

Hello guys,
Been looking at Swift for some projects, and had some very basic questions.

1. How does Swift determine a certain partition is full? And when it does 
detect that, what does it do? Does it return an error to the client?

2. Regarding container sync, has anyone used container sync in their 
implementations? It would be great to know your experiences, because real world 
use case studies are scarce:)


-- Mark

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] I release naming (calling APAC community)

[John Wong]

Yeah, I am too waiting for the ballot. The 'F' release was the craziest one
with 20+ candidates. I favor to vote on a subset of all the names we have
came up with so far. Seven is not bad, but we need a rule to pick 7. If we
adhere to the official naming convention, we probably have six with one or
two from Other Suggestions. Of course, I think we have to wait for the
committee to come up with the candidates.

John


On Fri, May 10, 2013 at 11:30 AM, John Hebert johnalexheb...@gmail.comwrote:

 I agree. The naming convention should not be a barrier to adoption of the
 new release. However, we should consider a name that has significance for
 the hosting community. Naming releases alphabetically is a convenience for
 speakers of Western languages, and the Openstack community is global. I
 don't think a slight deviation from previous naming convention will confuse
 anyone.

 It has been pointed out the Hong Kong Openstack summit could attract
 thousands of new developers, and so the name of the release should be
 something that this new community can easily identify. I'm sure a large
 number of Openstack community members wondered what the heck Bexar meant
 at first (I'm from San Antonio). :)

 In short, I think we should defer to the suggestions made by our hosts in
 Hong Kong and China.

 I move we set a deadline to pick the most popular 7 names (a common lucky
 number (七, Pinyin https://en.wikipedia.org/wiki/Pinyin: qī) symbolizes
 togetherness - wikipedia.org) and then vote soon on them after.

 John Hebert

 On Fri, May 10, 2013 at 8:24 AM, Eric Windisch e...@cloudscaling.comwrote:

 Extending the rules to those things of cultural or political significance
 would have established precedence with the 'Grizzly exception'.

 If such an exception were useful in naming this release, I'd suggest it
 become a standard part of the naming scheme.
 On May 10, 2013 6:40 AM, Matt Joyce matt.jo...@cloudscaling.com
 wrote:

 Alternatively... we name it after a kung fu movie.

 Invincible Fist for instance was a Shaw Brothers film.  Hong Kong is
 famous for it's Kung Fu films =P


 On Thu, May 9, 2013 at 8:57 PM, Wang, Shane shane.w...@intel.comwrote:

   If the next release summit is going to be held in “Japan”, it should
 be easier to give a nameJ

 ** **

 --

 Shane Wang

 *From:* Openstack [mailto:openstack-bounces+shane.wang=
 intel@lists.launchpad.net] *On Behalf Of *Rajesh Vellanki
 *Sent:* Friday, May 10, 2013 3:50 AM
 *To:* Atul Jha; Matt Joyce; John Wong

 *Cc:* Thierry Carrez; openstack@lists.launchpad.net
 *Subject:* Re: [Openstack] I release naming (calling APAC community)***
 *

  ** **

 +1 

 ** **

 Rajesh
  --

 *From:* Openstack [openstack-bounces+rvellank=
 rackspace@lists.launchpad.net] on behalf of Atul Jha [
 atul@csscorp.com]
 *Sent:* Thursday, May 09, 2013 2:31 PM
 *To:* Matt Joyce; John Wong
 *Cc:* Thierry Carrez; openstack@lists.launchpad.net
 *Subject:* Re: [Openstack] I release naming (calling APAC community)***
 *

 Hi all,

 I was too late to respond here i would love to see next release name as
 India.  I am saying because India is in APAC still i have need to find
 out rule book for release.

 Just my 1$ suggestion. :)

 Cheers!!

 Atul 
  --

 *From:* Openstack [openstack-bounces+atul.jha=
 csscorp@lists.launchpad.net] on behalf of Matt Joyce [
 matt.jo...@cloudscaling.com]
 *Sent:* Friday, May 10, 2013 12:58 AM
 *To:* John Wong
 *Cc:* Thierry Carrez; openstack@lists.launchpad.net
 *Subject:* Re: [Openstack] I release naming (calling APAC community)***
 *

 'Impossible' might be a good name... seeing as how impossible it is
 becoming to find a word beginning with I in the region.

 ** **

 On Thu, May 9, 2013 at 12:04 PM, John Wong gokoproj...@gmail.com
 wrote:

 Good point. A long time ago we used to call Beijing as Peking, but
 the journalists now will always pick up the pinyin version: Beijing. Since
 we are after I, we are pretty much down to either Ichang or Ili. Should
 either one be chosen, I think that we should document the pinyin version as
 well. The difference of Y and I is due to historical difference, which we
 are all familiar with. For example, there are more Wong than Wang, Chan
 than Chen in HK. 

 ** **

 John

 ** **

 On Thu, May 9, 2013 at 2:21 PM, Yi Yang yyos1...@gmail.com wrote:

 AS the official translation of the citiy names are Yichang and Yili, we
 are facing a risk to pick up a Chinese city name that most Chinese won't
 recognize.

 If we really have to choose a city, IMO, Yichang (ichang) would be a
 better choice, as the Yili(ili) is more than 2300 miles away from Hong
 Kong, while Yichang (ichang) is (only) 600 miles away.

 Just my $.02

 Yi 




 On 5/6/13 5:00 AM, Thierry Carrez wrote:

 Jacob Godin wrote:

 +1 Ili

 Thanks for all the suggestions ! We probably have enough place names so
 that we don't need to extend 

Re: [Openstack] Swift questions.

[David Hadas]

Mark, Regarding your first Q:Swift evenly balance the hard-drives such that in a correctly configured system, you should expect one hard-drive being more full than the other. There is manual a mechanism in swift to balance hard-drives by moving partitions to/from hard-drive but you should need to use it under normal conditions, it is likely that if your had-drives get full the right thing to do would be to add more hard-drives.In any case you should care not about individual partitions 'getting full' as partitions are not allocated any specific space and can grow and shrink as needed as long as the hard-drive they are in have space.DHRegards, David HadasResearch Staff Member, Master InventorIBM Research Labs, HaifaTel:Int+972-4-829-6104Fax:   Int+972-4-829-6112-"Openstack" openstack-bounces+davidh=il.ibm@lists.launchpad.net wrote: -To: "openstack@lists.launchpad.net" openstack@lists.launchpad.netFrom: Mark Brown Sent by: "Openstack" Date: 05/12/2013 07:50PMSubject: [Openstack] Swift questions.Hello guys,Been looking at Swift for some projects, and had some very basic questions.1. How does Swift determine a certain partition is full? And when it does detect that, what does it do? Does it return an error to the client?2. Regarding container sync, has anyone used container sync in their implementations? It would be great to know your experiences, because real world use case studies are scarce:)-- Mark___Mailing list: https://launchpad.net/~openstackPost to   : openstack@lists.launchpad.netUnsubscribe : https://launchpad.net/~openstackMore help  : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Swift questions.

[David Hadas]

Mark, It would mark the server as having insufficient storage (to avoid retrying the same server for a while) and try to place the object in an alternative node - same as it would do with any other error. Once the object is placed in an alternative node, the alternative node would try to send the object back to its originated place every once in a while such that if the problem is reolved, it will move to the right place. This being said, there are N replicas - and this would repeat for each of the N replicas. So if one server is full you can still access the data using the other N-1 replicas and you still maintain N replicas in your system of the object (although one of them is misplaced until the administrator would resolve the space issue). Swift doe snot use df, it would try to allocate the space on the disk and if it fails it fails.Failure is just a natural part of live as far as swift is concerned ;)Hope this helps. DHRegards, David HadasResearch Staff Member, Master InventorIBM Research Labs, HaifaTel:Int+972-4-829-6104Fax:   Int+972-4-829-6112-Mark Brown ntdeveloper2...@yahoo.com wrote: -To: David Hadas/Haifa/IBM@IBMILFrom: Mark Brown ntdeveloper2...@yahoo.comDate: 05/12/2013 08:27PMCc: "openstack@lists.launchpad.net" openstack@lists.launchpad.netSubject: Re: [Openstack] Swift questions.Thanks for the response David.I do understand Swift, by its design, tries to keep things in balance among various nodes. I was curious what it does when it encounters a full partition(say hard disk is full)? Lets just say it is balanced and the all nodes are nearing capacity. If I dont add any nodes, what happens when it tries to write on a specific node (which it was directed to based on the hashing ring) and there is not enough space to write the object?Also, what does it use to determine a full partition? Does it use a df?MarkFrom: David Hadas dav...@il.ibm.com To: Mark Brown ntdeveloper2...@yahoo.com Cc: "openstack@lists.launchpad.net" openstack@lists.launchpad.net  Sent: Sunday, May 12, 2013 10:36 PM Subject: Re: [Openstack] Swift questions.   Mark, Regarding your first Q:Swift evenly balance the hard-drives such that in a correctly configured system, you should expect one hard-drive being more full than the other. There is manual a mechanism in swift to balance hard-drives by moving partitions
 to/from hard-drive but you should need to use it under normal conditions, it is likely that if your had-drives get full the right thing to do would be to add more hard-drives.In any case you should care not about individual partitions 'getting full' as partitions are not allocated any specific space and can grow and shrink as needed as long as the hard-drive they are in have space.DHRegards, David HadasResearch Staff Member, Master InventorIBM Research Labs, HaifaTel:Int+972-4-829-6104Fax:   Int+972-4-829-6112-"Openstack" openstack-bounces+davidh=il.ibm@lists.launchpad.net wrote: -To: "openstack@lists.launchpad.net" openstack@lists.launchpad.netFrom: Mark Brown Sent by: "Openstack" Date:
 05/12/2013 07:50PMSubject: [Openstack] Swift questions.Hello guys,Been looking at Swift for some projects, and had some very basic questions.1. How does Swift determine a certain partition is full? And when it does detect that, what does it do? Does it return an error to the client?2. Regarding container sync, has anyone used container sync in their implementations? It would be great to know your experiences, because real world use case studies are scarce:)-- Mark___Mailing list: https://launchpad.net/~openstackPost to   : openstack@lists.launchpad.netUnsubscribe : https://launchpad.net/~openstackMore help  : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Swift questions.

[Mark Brown]

Thanks again, David. Definitely helps.

Is the alternative node you refer to here the handoff node? Is the handoff 
node something that is in the ring database? I am trying to piece together 
where in the stack this would happen. If it is transparent, it would probably 
happen in the object server somehow, but it would need to know where the 
handoff node is.

-- Mark.



 From: David Hadas dav...@il.ibm.com
To: Mark Brown ntdeveloper2...@yahoo.com 
Cc: openstack@lists.launchpad.net openstack@lists.launchpad.net 
Sent: Sunday, May 12, 2013 11:13 PM
Subject: Re: [Openstack] Swift questions.
 


Mark, 

It would mark the server as having insufficient storage (to avoid retrying the 
same server for a while) and try to place the object in an alternative node -  
same as it would do with any other error. Once the object is placed in an 
alternative node, the alternative node would try to send the object back to its 
originated place every once in a while such that if the problem is reolved, it 
will move to the right place. 

This being said, there are N replicas - and this would repeat for each of the N 
replicas. So if one server is full you can still access the data using the 
other N-1 replicas and you still maintain N replicas in your system of the 
object (although one of them is misplaced until the administrator would resolve 
the space issue). 

Swift doe snot use df, it would try to allocate the space on the disk and if it 
fails it fails.
Failure is just a natural part of live as far as swift is concerned ;)

Hope this helps. 

DH



Regards, 
David Hadas
Research Staff Member, Master Inventor

IBM Research Labs, Haifa
Tel:Int+972-4-829-6104
Fax:   Int+972-4-829-6112

-Mark Brown ntdeveloper2...@yahoo.com wrote: -
To: David Hadas/Haifa/IBM@IBMIL
From: Mark Brown ntdeveloper2...@yahoo.com
Date: 05/12/2013 08:27PM
Cc: openstack@lists.launchpad.net openstack@lists.launchpad.net
Subject: Re: [Openstack] Swift questions.


Thanks for the response David.

I do understand Swift, by its design, tries to keep things in balance among 
various nodes. I was curious what it does when it encounters a full 
partition(say hard disk is full)? Lets just say it is balanced and the all 
nodes are nearing capacity. If I dont add any nodes, what happens when it tries 
to write on a specific node (which it was directed to based on the hashing 
ring) and there is not enough space to write the object?

Also, what does it use to determine a full partition? Does it use a df? 

Mark



 From: David Hadas dav...@il.ibm.com
To: Mark Brown ntdeveloper2...@yahoo.com 
Cc: openstack@lists.launchpad.net openstack@lists.launchpad.net 
Sent: Sunday, May 12, 2013 10:36 PM
Subject: Re: [Openstack] Swift questions.
 


Mark, 

Regarding your first Q:

Swift evenly balance the hard-drives such that in a correctly configured 
system, you should expect one hard-drive being more full than the other. 
There is manual a mechanism in swift to balance hard-drives by moving partitions
 to/from hard-drive but you should need to use it under normal conditions, it 
is likely that if your had-drives get full the right thing to do would be to 
add more hard-drives.

In any case you should care not about individual partitions 'getting full' as 
partitions are not allocated any specific space and can grow and shrink as 
needed as long as the hard-drive they are in have space.


DH



Regards, 
David Hadas
Research Staff Member, Master Inventor

IBM Research Labs, Haifa
Tel:Int+972-4-829-6104
Fax:   Int+972-4-829-6112

-Openstack openstack-bounces+davidh=il.ibm@lists.launchpad.net 
wrote: -
To: openstack@lists.launchpad.net openstack@lists.launchpad.net
From: Mark Brown 
Sent by: Openstack 
Date:
 05/12/2013 07:50PM
Subject: [Openstack] Swift questions.


Hello guys,
Been looking at Swift for some projects, and had some very basic questions.

1. How does Swift determine a certain partition is full? And when it does 
detect that, what does it do? Does it return an error to the client?

2. Regarding container sync, has anyone used container sync in their 
implementations? It would be great to know your experiences, because real world 
use case studies are scarce:)


-- Mark

___
Mailing list: https://launchpad.net/~openstack
Post to     : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Swift questions.

[David Hadas]

 Handoff is chosen based on the Ring at the proxy, after the object server responding that it had failed to store the data or after any other error while attempting to approach the object sever (e.g. timeout). DHRegards, David HadasResearch Staff Member, Master InventorIBM Research Labs, HaifaTel:Int+972-4-829-6104Fax:   Int+972-4-829-6112-Mark Brown ntdeveloper2...@yahoo.com wrote: -To: David Hadas/Haifa/IBM@IBMILFrom: Mark Brown ntdeveloper2...@yahoo.comDate: 05/12/2013 08:55PMCc: "openstack@lists.launchpad.net" openstack@lists.launchpad.netSubject: Re: [Openstack] Swift questions.Thanks again, David. Definitely helps.Is the alternative node you refer to here the "handoff" node? Is the handoff node something that is in the ring database? I am trying to piece together where in the stack this would happen. If it is transparent, it would probably happen in the object server somehow, but it would need to know where the handoff node is.-- Mark.From: David Hadas dav...@il.ibm.com To: Mark Brown ntdeveloper2...@yahoo.com Cc: "openstack@lists.launchpad.net" openstack@lists.launchpad.net  Sent: Sunday, May 12, 2013 11:13 PM Subject: Re: [Openstack] Swift questions.   Mark, It would mark the server as having insufficient storage (to avoid retrying the same server for a while) and try to place the object in an alternative node - same as it would do with any other error. Once the object is placed in an alternative node, the alternative node would try to send the object back to its originated place every once in a while such that if the problem is reolved, it will move to the right place. This being said, there are N replicas - and this would repeat for each of the N replicas. So if one server is full you can still access the data using the other N-1 replicas and you still maintain N replicas in your system of the object (although one of them is misplaced until the administrator would
 resolve the space issue). Swift doe snot use df, it would try to allocate the space on the disk and if it fails it fails.Failure is just a natural part of live as far as swift is concerned ;)Hope this helps. DHRegards, David HadasResearch Staff Member, Master InventorIBM Research Labs, HaifaTel:Int+972-4-829-6104Fax:   Int+972-4-829-6112-Mark Brown ntdeveloper2...@yahoo.com wrote: -To: David Hadas/Haifa/IBM@IBMILFrom: Mark Brown ntdeveloper2...@yahoo.comDate: 05/12/2013 08:27PMCc: "openstack@lists.launchpad.net" openstack@lists.launchpad.netSubject: Re: [Openstack] Swift questions.Thanks for the response David.I do understand Swift, by its design, tries to keep things in balance among various nodes. I was curious what it does when it encounters a full partition(say hard disk is full)? Lets just say it is balanced and the all nodes are nearing capacity. If I dont add any nodes, what happens when it tries to write on a specific node (which it was directed to based on the hashing ring) and there is not enough space to write the object?Also, what does it use to determine a full partition? Does it use a df?MarkFrom: David Hadas dav...@il.ibm.com To: Mark Brown ntdeveloper2...@yahoo.com Cc: "openstack@lists.launchpad.net" openstack@lists.launchpad.net  Sent: Sunday, May 12, 2013 10:36 PM Subject: Re: [Openstack] Swift questions.   Mark, Regarding your first Q:Swift evenly balance the hard-drives such that in a correctly configured system, you should expect one hard-drive being more full than the other. There is manual a mechanism in swift to balance hard-drives by moving partitions
 to/from hard-drive but you should need to use it under normal conditions, it is likely that if your had-drives get full the right thing to do would be to add more hard-drives.In any case you should care not about individual partitions 'getting full' as partitions are not allocated any specific space and can grow and shrink as needed as long as the hard-drive they are in have space.DHRegards, David HadasResearch Staff Member, Master InventorIBM Research Labs, HaifaTel:Int+972-4-829-6104Fax:   Int+972-4-829-6112-"Openstack" openstack-bounces+davidh=il.ibm@lists.launchpad.net wrote: -To: "openstack@lists.launchpad.net" openstack@lists.launchpad.netFrom: Mark Brown Sent by: "Openstack" Date:
 05/12/2013 07:50PMSubject: [Openstack] Swift questions.Hello guys,Been looking at Swift for some projects, and had some very basic questions.1. How does Swift determine a certain partition is full? And when it does detect that, what does it do? Does it return an error to the client?2. Regarding container sync, has anyone used container sync in their implementations? It would be great to know your experiences, because real world use case studies are scarce:)-- Mark___Mailing list: https://launchpad.net/~openstackPost to   : openstack@lists.launchpad.netUnsubscribe : https://launchpad.net/~openstackMore help  : https://help.launchpad.net/ListHelp

Re: [Openstack] ConnectQuantum to VLAN-tagged physical network

[Angelo Olivera]

Salvatore, thanks for your reply. It took me a few tries but I finally
solved this issue by creating the vlan devices on the respective
interfaces, adding them to the corresponding bridges with ovs-vsctl
and configuring two external networks with quantum.

This would correspond to the Multiple Flat Network use case
described in the Grizzly Networking Administration Guide[1], although
the configuration is not explained. Quantum provides DHCP with default
routes 10.33.8.1 (vlan 108) and 10.33.9.1 (vlan 109). Namespaces are
used and there is one instance of the metadata proxy per each
namespace.

[1] 
http://docs.openstack.org/grizzly/openstack-network/admin/content/use_cases_multi_flat.html

/etc/network/interfaces
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address 10.33.10.210
netmask 255.255.255.0
gateway 10.33.10.1

auto eth1
iface eth1 inet manual

auto eth1.108
iface eth1.108 inet manual
vlan-raw-device eth1
up /sbin/ifconfig eth1.108 up

auto eth1.109
iface eth1.109 inet manual
vlan-raw-device eth1
up /sbin/ifconfig eth1.109 up

/etc/quantum/quantum.conf
[DEFAULT]
lock_path = $state_path/lock
bind_host = 0.0.0.0
bind_port = 9696
core_plugin = quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2
api_paste_config = /etc/quantum/api-paste.ini
control_exchange = quantum
rabbit_host = 10.33.10.210
notification_driver = quantum.openstack.common.notifier.rpc_notifier
default_notification_level = INFO
notification_topics = notifications
[QUOTAS]
[DEFAULT_SERVICETYPE]
[AGENT]
root_helper = sudo quantum-rootwrap /etc/quantum/rootwrap.conf
[keystone_authtoken]
auth_host = 127.0.0.1
auth_port = 35357
auth_protocol = http
admin_tenant_name = service
admin_user = quantum
admin_password = ###
signing_dir = /var/lib/quantum/keystone-signing

/etc/quantum/dhcp_agent.ini
[DEFAULT]
interface_driver = quantum.agent.linux.interface.OVSInterfaceDriver
dhcp_driver = quantum.agent.linux.dhcp.Dnsmasq
use_namespaces = True
enable_isolated_metadata = True

/etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini
[DATABASE]
sql_connection = mysql://quantum##@10.33.10.210/quantum?charset=utf8
reconnect_interval = 2
[OVS]
# even when using flat networking these two variables had to be
defined for the multiple physical networks to work
tenant_network_type = vlan
network_vlan_ranges = physdev:2048:4094,physqa:2048:4094
bridge_mappings = physdev:br-dev,physqa:br-qa
[AGENT]
polling_interval = 2
[SECURITYGROUP]
firewall_driver =
quantum.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver

# ovs-vsctl add-br br-int
# ovs-vsctl add-br br-dev
# ovs-vsctl add-port br-dev eth1.108
# ovs-vsctl add-br br-qa
# ovs-vsctl add-port br-qa eth1.109
# quantum net-create --shared dev --provider:network_type flat
--router:external=True --provider:physical_network physdev
# quantum net-create --shared qa --provider:network_type flat
--router:external=True --provider:physical_network physqa
# quantum subnet-create dev 10.33.8.0/24 --name dev-subnet
--allocation-pool start=10.33.8.10,end=10.33.8.254
# quantum subnet-create qa 10.33.9.0/24 --name qa-subnet
--allocation-pool start=10.33.9.10,end=10.33.9.254

(Question also posted on
https://answers.launchpad.net/quantum/+question/228437/)

Regards,

--
Angelo

On Thu, May 9, 2013 at 8:07 AM, Salvatore Orlando sorla...@nicira.com wrote:
 Your configuration looks correct, and provider networks are what you need
 for implementing this use case.

 Is the traffic for your subnets improperly tagged, or are you unable at all
 to forward traffic?
 If you're not using GRE overlays it might make sense verifying that VLAN
 108/109 are allowed on physical switch ports or that the physical switch
 ports are in trunk mode.


 Regards,
 Salvatore


 On 8 May 2013 20:21, Ashok Kumaran ashokkumara...@gmail.com wrote:

 Hi Angelo,

 This should be possible. Make sure that eth1 is connected to the Vlan
 trunk with necessary port configurations.

 Create 2 network with segmentation's ID as 108 and 109 respectively.
 Create the respective subnets for both network and then proceed with further
 configurations as needed. Are you facing any specific issues here?

 -Ashok


 On Wed, May 8, 2013 at 9:57 PM, Angelo Olivera aoliv...@gmail.com wrote:

 Hello,

 I am using Ubuntu 12.04 and OpenStack Grizzly from the Ubuntu Cloud
 archive. I am trying to get instances to get an IP address from dnsmasq in
 the 10.33.8.0/24 or 10.33.9.0/24 space and use physical routers at .1 as
 gateways. Furthermore, these two subnets should be tagged with VLANs 108 and
 109, respectively.

 Is this doable? I have been trying different configurations with Open
 vSwitch to no avail. My network layout is as follows:

 Nodes
 =

 Controller, network, compute node (32-core system)
 [eth0] 10.33.10.210. gateway: 10.33.10.1 (physical router)
 [eth1] connected to VLAN port on switch

 Compute nodes
 [eth0] 10.33.10.X
 [eth1] connected to VLAN port on switch

 Logical networks
 

Re: [Openstack] New code name for networks

[Brad Knowles]

On May 12, 2013, at 9:52 AM, Monty Taylor mord...@inaugust.com wrote:

 I would really like to keep the marketing/business folks out of our
 source code.
 
 Most importantl, I would really like to keep the lawyers out of our
 source code.

My wife is a lawyer, so maybe I'm particularly sensitive to this issue.  
However, I don't believe that the lawyers themselves are the problem.  I think 
the problem is that maybe you haven't gotten the *RIGHT* lawyers involved.

The RIGHT lawyers can help you spot potential problems while they're still just 
mole hills in the distance, and can help you avoid having them get turned into 
mountains.  But they can't just give you a set of rules and have you follow 
them blindly -- the reason they are the RIGHT lawyers is because of all their 
experiences and the lessons they've learned, and the places where they've seen 
clients trip up in the past, and therefore they know what to look for.  They 
can't necessarily tell you what to look for, they'll just know it when they see 
it.  Sure, they have rules that will cover the easy 80%, but it's the hard 20% 
that you have to really worry about.

The RIGHT lawyers will know when they look at a contract what kinds of things 
don't need to be written down, because they're covered by laws on the books, or 
by existing case law.  And when they look at contracts in a foreign country, 
they'll have some idea of what kinds of questions to ask -- and the different 
kind of legal systems around the world, how they differ, etc

This is the kind of thing that got BazaarVoice in trouble -- they went out of 
their way to structure the buyout of their major competitor in such a way that 
it didn't need to be approved in advance by the regulators.  But then they got 
hit with a lawsuit by the federal government, and they ended up having to 
divest themselves of most of the assets they had bought.  Had they structured 
the deal differently, they could have at least known in advance whether or not 
the regulators would have approved it, and if approved would never had to 
divest themselves of their acquisition.


The RIGHT lawyers can help you see and avoid these problems before you ever get 
there, but even they can't necessarily help you if you take the attitude that 
all lawyers are bad and therefore you have to keep them out of your business 
until there is simply no other choice.

Ask yourself this -- do you want the first time you turn to a lawyer to be when 
you're in the dock for a crime you committed even if you didn't know it was a 
crime, or do you want to have advice in advance that can help you avoid 
committing the crime in the first place?


You're in the business of doing certain technical things.  You can't keep the 
business people completely out of the technical stuff, and you can't keep the 
technical people completely out of the business stuff.  These things are not 
totally unrelated or orthogonal.  Likewise with the lawyers.

You need all three of those groups equally involved in helping to make your 
business platform stable so that you can have long-term success.  There is no 
path to success if you don't have everyone on your team helping to propel the 
business along the desired path, and there definitely is no path to success if 
you are actively avoiding getting certain people (or types of people) involved 
until you absolutely have no other possible choice.

Everyone should be fully and completely engaged in moving forward the success 
of your group, at all stages.

--
Brad Knowles bknow...@momentumsi.com
Senior Consultant


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] New code name for networks

[Monty Taylor]

Don't get me wrong... I don't disagree with you. I think lawyers are super 
important. At the risk of some of my best friends are... I took the lsat a 
few years ago (did quite well ;) ) with a view towards law school and my 
girlfriend is in law school. TOTALLY respect for lawyers.

I don't want to keep lawyers away from the project any more than I want to keep 
business people away. What I do want to do is keep random lawyers away from 
implementation details of our source code repositories.

Here's the rub... The technical leadership of the project has no body from 
which it can receive legal counsel. The foundation has counsel, but that is 
different than the TC having actual counsel to whom we can give intent 
direction and receive advice. We have many interested and involved parties who 
are top lawyers, and I regularly talk with them. But they're all quite clear 
that they cannot directly advise us as the collected technical leadership.

So we are in a sticky situation of needing to make decisions that have actual 
technical ramifications, and that may have legal consequences, but no counsel 
to whom we can give priorities and direct to help us find solutions.

From the foundation perspective, the risk/reward is clear, and from that 
perspective discussions with counsel can proceed. But in addition to a board 
who can have an executive session with counsel to which privilege attaches, 
the foundation has executive director who can also have privileged 
discussions. Those are from a particular POV, and it's a totally valid one.

The technical leadership, OTOH, does not have this ability, nor are we 
interested in doing things in private. We are tasked with technical leadership, 
which is what we intend to do.

So, with all due respect to the many awesome lawyers who are involved with the 
project, what I'm getting at is that we need to do the right thing as best we 
can based on unofficial advice from well meaning people who may or may not have 
legal backgrounds as well as input and help from Jonathan Bryce and the 
foundation board where appropriate.

I wish there was a more straightforward way to approach this, but it's not a 
straightforward situation. However, maybe if we play our cards right and are 
conscientious in our approach to the problems we can help forge ground for more 
people who want to run a thing like we are without getting into too much 
trouble along the way.

Brad Knowles bknow...@momentumsi.com wrote:

On May 12, 2013, at 9:52 AM, Monty Taylor mord...@inaugust.com wrote:

 I would really like to keep the marketing/business folks out of our
 source code.
 
 Most importantl, I would really like to keep the lawyers out of our
 source code.

My wife is a lawyer, so maybe I'm particularly sensitive to this issue.  
However, I don't believe that the lawyers themselves are the problem.  I think 
the problem is that maybe you haven't gotten the *RIGHT* lawyers involved..

The RIGHT lawyers can help you spot potential problems while they're still 
just mole hills in the distance, and can help you avoid having them get turned 
into mountains.  But they can't just give you a set of rules and have you 
follow them blindly -- the reason they are the RIGHT lawyers is because of all 
their experiences and the lessons they've learned, and the places where 
they've seen clients trip up in the past, and therefore they know what to look 
for.  They can't necessarily tell you what to look for, they'll just know it 
when they see it.  Sure, they have rules that will cover the easy 80%, but 
it's the hard 20% that you have to really worry about.

The RIGHT lawyers will know when they look at a contract what kinds of things 
don't need to be written down, because they're covered by laws on the books, 
or by existing case law.  And when they look at contracts in a foreign 
country, they'll have some idea of what kinds of questions to ask -- and the 
different kind of legal systems around the world, how they differ, etc.

This is the kind of thing that got BazaarVoice in trouble -- they went out of 
their way to structure the buyout of their major competitor in such a way that 
it didn't need to be approved in advance by the regulators.  But then they got 
hit with a lawsuit by the federal government, and they ended up having to 
divest themselves of most of the assets they had bought.  Had they structured 
the deal differently, they could have at least known in advance whether or not 
the regulators would have approved it, and if approved would never had to 
divest themselves of their acquisition.


The RIGHT lawyers can help you see and avoid these problems before you ever 
get there, but even they can't necessarily help you if you take the attitude 
that all lawyers are bad and therefore you have to keep them out of your 
business until there is simply no other choice.

Ask yourself this -- do you want the first time you turn to a lawyer to be 
when you're in the dock for a crime you committed 

[Openstack] DevStack Question

[Arindam Choudhury]

Hi,

If the script is updated to use cloud repository instead of source code, it can 
be used as an automatic installer. Have anybody done it yet? 

Regards,
Arindam
  ___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] DevStack Question

[Matt Joyce]

most folks would use puppet or chef to accomplish that task.


On Sun, May 12, 2013 at 2:46 PM, Arindam Choudhury arin...@live.com wrote:

 Hi,

 If the script is updated to use cloud repository instead of source code,
 it can be used as an automatic installer. Have anybody done it yet?

 Regards,
 Arindam

 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] DevStack Question

[arindam]

hi,
Any prescribed auto installer for grizzly with quantum gre tunneling support?

--- Original Message ---

From: Matt Joyce matt.jo...@cloudscaling.com
Sent: May 12, 2013 11:57 PM
To: Arindam Choudhury arin...@live.com
Cc: openstack openstack@lists.launchpad.net
Subject: Re: [Openstack] DevStack Question

most folks would use puppet or chef to accomplish that task.


On Sun, May 12, 2013 at 2:46 PM, Arindam Choudhury arin...@live.com wrote:

 Hi,

 If the script is updated to use cloud repository instead of source code,
 it can be used as an automatic installer. Have anybody done it yet?

 Regards,
 Arindam

 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] New code name for networks

[Joshua Harlow]

I vote for calling it spacetime since spacetime binds us all together in the 
same way networks bind computers together. Doubt it's copyrightable if that's 
needed, unless Einstein holds the copyright :P

Sent from my really tiny device...

On May 12, 2013, at 10:43 AM, John Wong 
gokoproj...@gmail.commailto:gokoproj...@gmail.com wrote:

Cool.
I think I did a search here: 
http://tmsearch.uspto.gov/bin/gate.exe?f=searchssstate=4804:3j8874.1.1  for 
Netpune.

Are we only concern with registered trademark? I am sure a lot of names we come 
up with are either full or partial of some company's name. What's the bottom 
line?
Who's going to come up the list of names? Where do we put our suggestion? For 
the next OS release we have a Wiki page setup. Do we have a Wiki page setup yet?

Best,
John


On Sun, May 12, 2013 at 12:27 PM, Sean Dague 
s...@dague.netmailto:s...@dague.net wrote:
Quark is also the trademark of a computer software company - 
http://tess2.uspto.gov/bin/showfield?f=docstate=4808:7k4xqd.2.44

This stuff is trickier than you might realize. Hence why car names are now all 
made-ity-up words.

-Sean


On 05/12/2013 12:21 PM, Jacob Godin wrote:
I like this, +1

On 2013-05-11 8:08 PM, David Shrewsbury 
shrewsbury.d...@gmail.commailto:shrewsbury.d...@gmail.com
mailto:shrewsbury.d...@gmail.commailto: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
OpenStack).

http://en.wikipedia.org/wiki/Quark

-Dave


On May 11, 2013, at 4:13 PM, Monty Taylor 
mord...@inaugust.commailto:mord...@inaugust.com
mailto:mord...@inaugust.commailto:mord...@inaugust.com wrote:

  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
  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 an
  homage, and it should be super easy to bulk cut/replace.
 
  On 05/11/2013 03:58 PM, Davanum Srinivas wrote:
  Lattice
 
  -- dims
 
  On Sat, May 11, 2013 at 3:52 PM, Mark Turner 
m...@amerine.netmailto:m...@amerine.net
mailto:m...@amerine.netmailto:m...@amerine.net wrote:
  Tubes
 
  ;-)
 
 
  On Sat, May 11, 2013 at 12:51 PM, Jason Smith
jason.sm...@rackspace.commailto:jason.sm...@rackspace.com 
mailto:jason.sm...@rackspace.commailto: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
  ___
  Mailing list: https://launchpad.net/~openstack
  Post to : 
openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
mailto:openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net

  Unsubscribe : https://launchpad.net/~openstack
  More help : https://help.launchpad.net/ListHelp
 
 
 
  ___
  Mailing list: https://launchpad.net/~openstack
  Post to : 
openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
mailto:openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net

  Unsubscribe : https://launchpad.net/~openstack
  More help   : https://help.launchpad.net/ListHelp
 
 
 
 
 
  ___
  Mailing list: https://launchpad.net/~openstack
  Post to : 
openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
mailto:openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net

  Unsubscribe : https://launchpad.net/~openstack
  More help   : https://help.launchpad.net/ListHelp
 
 
  ___
  Mailing list: https://launchpad.net/~openstack
  Post to : 
openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
mailto:openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net

  Unsubscribe : https://launchpad.net/~openstack
  More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~openstack
Post to : 
openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
mailto:openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net

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

[Sean Dague]

On 05/12/2013 09:14 AM, Mark McLoughlin wrote:

On Sat, 2013-05-11 at 19:50 +, Jason Smith 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!


Yes, this was discussed at the summit:

   https://etherpad.openstack.org/ProjectsReNaming

The conclusion was that a number of choices for a new name would be put
forward and that Quantum's contributors would vote for one of those
choices.


Just as a consideration to the Nova project (and probably others), it 
would be *really* nice if the new name was also 7 characters.


There are currently 351 occurrences of the word quantum in the Nova code 
in current master, some of them will have pep8 implications after 
changing, if the length of the word changes.


This probably bites quantum internally as well, but it's worth making 
sure it's highlighted.


-Sean

--
Sean Dague
http://dague.net

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

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

[Matt Joyce]

to say nothing of the localization that will need complete re-translating.


On Sun, May 12, 2013 at 6:27 PM, Sean Dague s...@dague.net wrote:

 On 05/12/2013 09:14 AM, Mark McLoughlin wrote:

 On Sat, 2013-05-11 at 19:50 +, Jason Smith 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!


 Yes, this was discussed at the summit:


 https://etherpad.openstack.**org/ProjectsReNaminghttps://etherpad.openstack.org/ProjectsReNaming

 The conclusion was that a number of choices for a new name would be put
 forward and that Quantum's contributors would vote for one of those
 choices.


 Just as a consideration to the Nova project (and probably others), it
 would be *really* nice if the new name was also 7 characters.

 There are currently 351 occurrences of the word quantum in the Nova code
 in current master, some of them will have pep8 implications after changing,
 if the length of the word changes.

 This probably bites quantum internally as well, but it's worth making sure
 it's highlighted.

 -Sean


 --
 Sean Dague
 http://dague.net

 __**_
 Mailing list: 
 https://launchpad.net/~**openstackhttps://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : 
 https://launchpad.net/~**openstackhttps://launchpad.net/~openstack
 More help   : 
 https://help.launchpad.net/**ListHelphttps://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] [Quantum] Floodlight plugin: request for doc assistance

[Lorin Hochstein]

All:

I'm trying to figure out how the Floodlight plugin for Quantum works, so we
can document it fully. Unfortunately, I haven't been able to get it working.

I've started a wiki page on how to set up Floodlight at
https://wiki.openstack.org/wiki/Quantum/FloodlightPluginSetup. If somebody
has been successful with Floodlight and could help complete this, please
let me know. Once this is working, I can transfer it to the DocBook docs.

Lorin

-- 
Lorin Hochstein
Lead Architect - Cloud Services
Nimbis Services, Inc.
www.nimbisservices.com
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

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

[Stefano Maffulli]

Hi Jason,

thank you for picking up this topic: some people may not be aware of the 
work that is happening.


Remember that cross-posting is *evil*: please just don't do it. The best 
way is to pick one list, the one you think is the best place to start a 
conversation, and start there. If it's the wrong place, somebody will 
tell you that and give suggestions.


On 05/11/2013 12:50 PM, Jason Smith 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!

This could have been a topic for openstack-dev, IMHO: it needs to be 
discussed among the developers because it has lots of technical 
implications for future of the project.


Anyway, there is a blueprint filed:

https://blueprints.launchpad.net/quantum/+spec/remove-use-of-quantum

and the progress is tracked at the weekly meetings. I encourage you to
participate to them:

https://wiki.openstack.org/wiki/Meetings#OpenStack_Project_.26_Release_Status_meeting

In the past meeting

http://eavesdrop.openstack.org/meetings/project/2013/project.2013-05-07-21.02.log.html

Mark McClain said:

21:31:18 markmcclain for naming? yes.. will submit a list of name for 
vetting


I guess the marketing team can be consulted to help pick the final name 
from the list, together with the other groups involved in this important 
decisions.


Cheers,
stef

--
Ask and answer questions on https://ask.openstack.org

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

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

[openstack-testing-bot]

Title: precise_havana_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_quantum_trunk/108/Project:precise_havana_quantum_trunkDate of build:Sun, 12 May 2013 02:30:22 -0400Build duration:2 min 51 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesImported Translations from Transifexby Jenkinseditquantum/locale/quantum.poteditquantum/locale/ko_KR/LC_MESSAGES/quantum.poeditquantum/locale/ka_GE/LC_MESSAGES/quantum.poeditquantum/locale/ja/LC_MESSAGES/quantum.poConsole Output[...truncated 3338 lines...]dch -a [01a977b] Send 400 error if device specification contains unexpected attributesdch -a [62017cd] Imported Translations from Transifexdch -a [26b98b7] lbaas: check object state before update for pools, members, health monitorsdch -a [49c1c98] Metadata agent: reuse authentication info across eventlet threadsdch -a [11639a2] Imported Translations from Transifexdch -a [35988f1] Make the 'admin' role configurabledch -a [ee50162] Simplify delete_health_monitor() using cascadesdch -a [765baf8] Imported Translations from Transifexdch -a [15a1445] Update latest OSLO codedch -a [343ca18] Imported Translations from Transifexdch -a [c117074] Remove locals() from strings substitutionsdch -a [fb66e24] Imported Translations from Transifexdch -a [e001a8d] Add string 'quantum'/ version to scope/tag in NVPdch -a [5896322] Changed DHCPV6_PORT from 467 to 547, the correct port for DHCPv6.dch -a [80ffdde] Imported Translations from Transifexdch -a [929cbab] Imported Translations from Transifexdch -a [2a24058] Imported Translations from Transifexdch -a [b6f0f68] Imported Translations from Transifexdch -a [1e1c513] Imported Translations from Transifexdch -a [6bbcc38] Imported Translations from Transifexdch -a [bd702cb] Imported Translations from Transifexdch -a [a13295b] Enable automatic validation of many HACKING rules.dch -a [91bed75] Ensure unit tests work with all interface typesdch -a [0446eac] Shorten the path of the nicira nvp plugin.dch -a [8354133] Implement LB plugin delete_pool_health_monitor().dch -a [147038a] Parallelize quantum unit testing:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC quantum_2013.2+git201305120230~precise-0ubuntu1_source.changessbuild -d precise-havana -n -A quantum_2013.2+git201305120230~precise-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-havana', '-n', '-A', 'quantum_2013.2+git201305120230~precise-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-havana', '-n', '-A', 'quantum_2013.2+git201305120230~precise-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

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

[openstack-testing-bot]

Title: saucy_havana_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/saucy_havana_quantum_trunk/38/Project:saucy_havana_quantum_trunkDate of build:Sun, 12 May 2013 02:30:23 -0400Build duration:6 min 33 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesImported Translations from Transifexby Jenkinseditquantum/locale/ja/LC_MESSAGES/quantum.poeditquantum/locale/quantum.poteditquantum/locale/ko_KR/LC_MESSAGES/quantum.poeditquantum/locale/ka_GE/LC_MESSAGES/quantum.poConsole Output[...truncated 14707 lines...]dch -a [6a5edbc] Create a common function for method _parse_network_vlan_ranges used by plugins.dch -a [791e220] Imported Translations from Transifexdch -a [a397df3] Don't run metadata proxy when it is not neededdch -a [8a9e7ac] in dhcp_agent, always use quantum.conf root_helperdch -a [6d26dd5] Fix usage of SQLAlchemy Query.first() methoddch -a [f8f2a7f] Fix usage of NexusPortBindingNotFound exceptiondch -a [0e49ad3] Imported Translations from Transifexdch -a [9751562] Avoid extra queries when retrieving routersdch -a [3640328] Log a warning if dnsmasq version is below the minimum requireddch -a [6db5b0b] Change Daemon class to better match process command lines.dch -a [fa69228] Improve checking of return values for functions in linuxbridge agent plugindch -a [3bf88f4] Imported Translations from Transifexdch -a [09dd1ec] Validate that netaddr does not receive a string with whitespacedch -a [4056e8e] Import recent rootwrap features in local rootwrapdch -a [17336b9] Fix 500 raised on disassociate_floatingips when out of syncdch -a [9b2fb56] Update import of oslo's processutils.dch -a [6acbc05] Calculate nicira plugin NAT rules order according to CIDR prefixdch -a [ea29aeb] Log msg for load policy file only if the file is actually loadeddch -a [0fee496] Fetch routers ports for metadata access from DBdch -a [31946eb] update-port error if port does not exist in nvpdch -a [3ba9b98] blueprint cisco-plugin-exception-handlingdch -a [2db451d] Imported Translations from Transifexdch -a [87d0f81] Duplicate line in Brocade plugindch -a [9051f68] Imported Translations from Transifexdch -a [6f01194] Perform a joined query for ports and security group associationsdch -a [9581e5b]  Copy the RHEL6 eventlet workaround from Oslodebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC quantum_2013.2+git201305120230~saucy-0ubuntu1_source.changessbuild -d saucy-havana -n -A quantum_2013.2+git201305120230~saucy-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'saucy-havana', '-n', '-A', 'quantum_2013.2+git201305120230~saucy-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'saucy-havana', '-n', '-A', 'quantum_2013.2+git201305120230~saucy-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

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

[openstack-testing-bot]

Title: precise_havana_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_quantum_trunk/109/Project:precise_havana_quantum_trunkDate of build:Sun, 12 May 2013 14:30:22 -0400Build duration:3 min 4 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesUpdate flake8 pinned versions.by mordrededittools/test-requiresImported Translations from Transifexby Jenkinseditquantum/locale/ja/LC_MESSAGES/quantum.poeditquantum/locale/ko_KR/LC_MESSAGES/quantum.poeditquantum/locale/ka_GE/LC_MESSAGES/quantum.poeditquantum/locale/quantum.potConsole Output[...truncated 3344 lines...]dch -a [01a977b] Send 400 error if device specification contains unexpected attributesdch -a [62017cd] Imported Translations from Transifexdch -a [26b98b7] lbaas: check object state before update for pools, members, health monitorsdch -a [49c1c98] Metadata agent: reuse authentication info across eventlet threadsdch -a [11639a2] Imported Translations from Transifexdch -a [35988f1] Make the 'admin' role configurabledch -a [ee50162] Simplify delete_health_monitor() using cascadesdch -a [765baf8] Imported Translations from Transifexdch -a [15a1445] Update latest OSLO codedch -a [343ca18] Imported Translations from Transifexdch -a [c117074] Remove locals() from strings substitutionsdch -a [fb66e24] Imported Translations from Transifexdch -a [e001a8d] Add string 'quantum'/ version to scope/tag in NVPdch -a [5896322] Changed DHCPV6_PORT from 467 to 547, the correct port for DHCPv6.dch -a [80ffdde] Imported Translations from Transifexdch -a [929cbab] Imported Translations from Transifexdch -a [2a24058] Imported Translations from Transifexdch -a [b6f0f68] Imported Translations from Transifexdch -a [1e1c513] Imported Translations from Transifexdch -a [6bbcc38] Imported Translations from Transifexdch -a [bd702cb] Imported Translations from Transifexdch -a [a13295b] Enable automatic validation of many HACKING rules.dch -a [91bed75] Ensure unit tests work with all interface typesdch -a [0446eac] Shorten the path of the nicira nvp plugin.dch -a [8354133] Implement LB plugin delete_pool_health_monitor().dch -a [147038a] Parallelize quantum unit testing:debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC quantum_2013.2+git201305121430~precise-0ubuntu1_source.changessbuild -d precise-havana -n -A quantum_2013.2+git201305121430~precise-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-havana', '-n', '-A', 'quantum_2013.2+git201305121430~precise-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-havana', '-n', '-A', 'quantum_2013.2+git201305121430~precise-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

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

[openstack-testing-bot]

Title: saucy_havana_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/saucy_havana_quantum_trunk/39/Project:saucy_havana_quantum_trunkDate of build:Sun, 12 May 2013 14:30:23 -0400Build duration:6 min 39 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesUpdate flake8 pinned versions.by mordrededittools/test-requiresImported Translations from Transifexby Jenkinseditquantum/locale/quantum.poteditquantum/locale/ko_KR/LC_MESSAGES/quantum.poeditquantum/locale/ja/LC_MESSAGES/quantum.poeditquantum/locale/ka_GE/LC_MESSAGES/quantum.poConsole Output[...truncated 14713 lines...]dch -a [6a5edbc] Create a common function for method _parse_network_vlan_ranges used by plugins.dch -a [791e220] Imported Translations from Transifexdch -a [a397df3] Don't run metadata proxy when it is not neededdch -a [8a9e7ac] in dhcp_agent, always use quantum.conf root_helperdch -a [6d26dd5] Fix usage of SQLAlchemy Query.first() methoddch -a [f8f2a7f] Fix usage of NexusPortBindingNotFound exceptiondch -a [0e49ad3] Imported Translations from Transifexdch -a [9751562] Avoid extra queries when retrieving routersdch -a [3640328] Log a warning if dnsmasq version is below the minimum requireddch -a [6db5b0b] Change Daemon class to better match process command lines.dch -a [fa69228] Improve checking of return values for functions in linuxbridge agent plugindch -a [3bf88f4] Imported Translations from Transifexdch -a [09dd1ec] Validate that netaddr does not receive a string with whitespacedch -a [4056e8e] Import recent rootwrap features in local rootwrapdch -a [17336b9] Fix 500 raised on disassociate_floatingips when out of syncdch -a [9b2fb56] Update import of oslo's processutils.dch -a [6acbc05] Calculate nicira plugin NAT rules order according to CIDR prefixdch -a [ea29aeb] Log msg for load policy file only if the file is actually loadeddch -a [0fee496] Fetch routers ports for metadata access from DBdch -a [31946eb] update-port error if port does not exist in nvpdch -a [3ba9b98] blueprint cisco-plugin-exception-handlingdch -a [2db451d] Imported Translations from Transifexdch -a [87d0f81] Duplicate line in Brocade plugindch -a [9051f68] Imported Translations from Transifexdch -a [6f01194] Perform a joined query for ports and security group associationsdch -a [9581e5b]  Copy the RHEL6 eventlet workaround from Oslodebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC quantum_2013.2+git201305121430~saucy-0ubuntu1_source.changessbuild -d saucy-havana -n -A quantum_2013.2+git201305121430~saucy-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'saucy-havana', '-n', '-A', 'quantum_2013.2+git201305121430~saucy-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'saucy-havana', '-n', '-A', 'quantum_2013.2+git201305121430~saucy-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

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

[openstack-testing-bot]

Title: precise_havana_cinder_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_cinder_trunk/50/Project:precise_havana_cinder_trunkDate of build:Mon, 13 May 2013 01:00:22 -0400Build duration:1 min 22 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesImplement copy_image_to_volume and copy_volume_to_image on nfs backendsby mehdi.abaakoukeditcinder/volume/drivers/nfs.pySet default values for NFS/GlusterFS share_config filesby eharneyeditcinder/volume/drivers/nfs.pyeditetc/cinder/cinder.conf.sampleeditcinder/volume/drivers/glusterfs.pyConsole Output[...truncated 1412 lines...]1 out of 1 hunk FAILED -- rejects in file tools/pip-requiresPatch fix_cinder_dependencies.patch can be reverse-appliedERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-cd9bb65e-17ea-42ec-bafa-c0db01b741d3', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-cd9bb65e-17ea-42ec-bafa-c0db01b741d3', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/cinder/havana /tmp/tmpFvnxgI/cindermk-build-deps -i -r -t apt-get -y /tmp/tmpFvnxgI/cinder/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log d0b5b93fe7611b35a8c6a9b09f46641f4fb859f4..HEAD --no-merges --pretty=format:[%h] %sdch -b -D precise --newversion 1:2013.2+git201305130100~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [59fc6cb] Change the type of "free_capacity_gb" to be floatdch -a [6d2d88c] Set default values for NFS/GlusterFS share_config filesdch -a [4580ee9] Add missing spaces to iscsi_iotype helpdch -a [caeb4a2] Fix missing spaces in Huawei Loggingdch -a [d75fafa] Add pylint-based lintstack test to tox environmentdch -a [7dad062] Remove outdated cinder test docdch -a [7ad6ac4] Implement copy_image_to_volume and copy_volume_to_image on nfs backendsdch -a [7996aaa] Update import of oslo's processutils.dch -a [54a2ee4] Fix ability to add custom volume_backend_namedch -a [cb3fb51] Add db client packages to dev env setup doc.dch -a [db991e6] Remove old_name from kwargs when using IET helper.dch -a [d52a0f2] Copy the RHEL6 eventlet workaround from Oslodch -a [7546682] Remove setuptools-git as run time dependencydch -a [006d673] Fix LHN driver to allow backend name configurationdch -a [0ee20a0] Fixes 3par driver methods that were double lockingdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-cd9bb65e-17ea-42ec-bafa-c0db01b741d3', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-cd9bb65e-17ea-42ec-bafa-c0db01b741d3', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

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

[openstack-testing-bot]

Title: saucy_havana_cinder_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/saucy_havana_cinder_trunk/18/Project:saucy_havana_cinder_trunkDate of build:Mon, 13 May 2013 01:00:23 -0400Build duration:1 min 53 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesImplement copy_image_to_volume and copy_volume_to_image on nfs backendsby mehdi.abaakoukeditcinder/volume/drivers/nfs.pySet default values for NFS/GlusterFS share_config filesby eharneyeditetc/cinder/cinder.conf.sampleeditcinder/volume/drivers/glusterfs.pyeditcinder/volume/drivers/nfs.pyConsole Output[...truncated 2096 lines...]1 out of 1 hunk FAILED -- rejects in file tools/pip-requiresPatch fix_cinder_dependencies.patch can be reverse-appliedERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'saucy-amd64-cc3ef4ba-d1b5-406e-90c7-88f1738114a1', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-p', '-r', '-c', 'saucy-amd64-cc3ef4ba-d1b5-406e-90c7-88f1738114a1', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/cinder/havana /tmp/tmpHuLOfh/cindermk-build-deps -i -r -t apt-get -y /tmp/tmpHuLOfh/cinder/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log d0b5b93fe7611b35a8c6a9b09f46641f4fb859f4..HEAD --no-merges --pretty=format:[%h] %sdch -b -D saucy --newversion 1:2013.2+git201305130100~saucy-0ubuntu1 Automated Ubuntu testing build:dch -a [59fc6cb] Change the type of "free_capacity_gb" to be floatdch -a [6d2d88c] Set default values for NFS/GlusterFS share_config filesdch -a [4580ee9] Add missing spaces to iscsi_iotype helpdch -a [caeb4a2] Fix missing spaces in Huawei Loggingdch -a [d75fafa] Add pylint-based lintstack test to tox environmentdch -a [7dad062] Remove outdated cinder test docdch -a [7ad6ac4] Implement copy_image_to_volume and copy_volume_to_image on nfs backendsdch -a [7996aaa] Update import of oslo's processutils.dch -a [54a2ee4] Fix ability to add custom volume_backend_namedch -a [cb3fb51] Add db client packages to dev env setup doc.dch -a [db991e6] Remove old_name from kwargs when using IET helper.dch -a [d52a0f2] Copy the RHEL6 eventlet workaround from Oslodch -a [7546682] Remove setuptools-git as run time dependencydch -a [006d673] Fix LHN driver to allow backend name configurationdch -a [0ee20a0] Fixes 3par driver methods that were double lockingdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'saucy-amd64-cc3ef4ba-d1b5-406e-90c7-88f1738114a1', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'saucy-amd64-cc3ef4ba-d1b5-406e-90c7-88f1738114a1', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp