[Openstack] [Swift]

[Tomáš Šoltys]

Hi,

I am following the OpenStack WalkThrough instructions and I am failing to
verify my setup as described here:
http://docs.openstack.org/folsom/openstack-compute/install/yum/content/verify-swift-installation.html

In this forum I have found that the instructions are not exactly correct so
I tried what was suggested but without any success.

Following command always return '404 Not Found'

curl -k -v -H 'X-Storage-User: service:swift' -H 'X-Storage-Pass: 12345678'
-X 'POST' http://localhost:5000/v2.0/auth

But when for following it works:

curl -k -v -X 'POST' http://localhost:5000/v2.0/tokens -d
'{auth:{passwordCredentials:{username:swift,
password:12345678}, tenantName:service}}' -H 'Content-type:
application/json' -H 'Accept: application/xml'

What am I missing here?

Thanks

Tomáš Šoltys

tomas.sol...@gmail.com
http://www.range-software.com
(+420) 776-843-663
___
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] Why is 'subnet' introduced in Quantum API v2?

[Zd Yu]

I am confused by the existence of both 'network' and 'subnet'. According to
v2 API spec[1], subnet is introduced to support IPAM capabilities. Can
anyone elaborate it to me? For example, what is the benefit of creating 1
network and 2 subnets by comparison with creating 2 networks that
implicitly has one and only one subnet for each?

I do know that the original network did not support IP overlapping before
subnet is introduced. But it is just an implementation issue, right?

Thanks,
Zhidong

[1] https://wiki.openstack.org/wiki/Quantum/APIv2-specification
___
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]

[Tomáš Šoltys]

Forgot to attach /etc/swift/proxy-server.conf

[DEFAULT]
bind_port = 
user = swift

[pipeline:main]
pipeline = healthcheck cache authtoken keystone proxy-server

[app:proxy-server]
use = egg:swift#proxy
allow_account_management = true
account_autocreate = true

[filter:keystone]
paste.filter_factory = keystone.middleware.swift_auth:filter_factory
operator_roles = Member,admin, swiftoperator

[filter:authtoken]
paste.filter_factory = keystone.middleware.auth_token:filter_factory
# Delaying the auth decision is required to support token-less
# usage for anonymous referrers ('.r:*').
delay_auth_decision = 10
service_port = 5000
service_host = 127.0.0.1
auth_port = 35357
auth_host = 127.0.0.1
auth_protocol = http
auth_uri = http://127.0.0.1:5000/
auth_token = 12345678
admin_token = 12345678
admin_tenant_name = service
admin_user = swift
admin_password = 12345678

[filter:cache]
use = egg:swift#memcache
set log_name = cache

[filter:catch_errors]
use = egg:swift#catch_errors

[filter:healthcheck]
use = egg:swift#healthcheck


2013/3/15 Tomáš Šoltys tomas.sol...@gmail.com

 Hi,

 I am following the OpenStack WalkThrough instructions and I am failing to
 verify my setup as described here:

 http://docs.openstack.org/folsom/openstack-compute/install/yum/content/verify-swift-installation.html

 In this forum I have found that the instructions are not exactly correct
 so I tried what was suggested but without any success.

 Following command always return '404 Not Found'

 curl -k -v -H 'X-Storage-User: service:swift' -H 'X-Storage-Pass:
 12345678' -X 'POST' http://localhost:5000/v2.0/auth

 But when for following it works:

 curl -k -v -X 'POST' http://localhost:5000/v2.0/tokens -d
 '{auth:{passwordCredentials:{username:swift,
 password:12345678}, tenantName:service}}' -H 'Content-type:
 application/json' -H 'Accept: application/xml'

 What am I missing here?

 Thanks

 Tomáš Šoltys

 tomas.sol...@gmail.com
 http://www.range-software.com
 (+420) 776-843-663




-- 
Tomáš Šoltys
tomas.sol...@gmail.com
http://www.range-software.com
(+420) 776-843-663
___
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] Access problem to Metadata server

[Sammy Fung]

I am following this nice guide to configure Quantum.

https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/GRE/2NICs/OpenStack_Folsom_Install_Guide_WebVersion.rst

my ttylinux VM is successfully reaching internet, ping 8.8.8.8
successfully.

Although iptables got a DNAT rule by Quantum.

Chain quantum-l3-agent-PREROUTING (1 references)
target prot opt source   destination
DNAT   tcp  --  0.0.0.0/0169.254.169.254  tcp dpt:80 to:
1.2.3.4:8775

I got timeout on HTTP request to 169.254.169.254 connecting from VM.

$ wget http://169.254.169.254/2009-04-04/meta-data/instance-id
Connecting to 169.254.169.254 (169.254.169.254:80)
wget: can't connect to remote host (169.254.169.254): Connection timed out

But I got 404 Not Found if I connect to public IP port 8775 connecting from
VM.

$ wget http://1.2.3.4:8775/2009-04-04/meta-data/instance-id

Connecting to 1.2.3.4:8775 (1.2.3.4:8775)
wget: server returned error: HTTP/1.1 404 Not Found

Anything I can try for debug/solving it ?

Thanks.
___
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 PUT error

[Gareth]

rfile.readline().split(;, 1)[0] here is empty string.

Could give the size of object your uploaded, in bytes.


On Fri, Mar 15, 2013 at 7:02 AM, Lokare, Bageshree
bageshree.lok...@hp.comwrote:

  Hello Suchi,

 ** **

 We are doing some similar stress testing for Swift and its working fine
 for a normal 100 user (1sec ramp-up)/1MB object size.

 Can you please give some more details on your set-up like,

 **-  **Object size

 **-  **Load/concurrent users

 **-  **Size of cluster

 **-  **# of LG and ramp-up time

 **-  **LG and swift target set-up (both in-cloud/out of cloud)

 ** **

 

 Thanks,

 SHREE

  

 ** **

 *From:* openstack-bounces+nayna.patel=hp@lists.launchpad.net [
 mailto:openstack-bounces+nayna.patel=hp@lists.launchpad.netopenstack-bounces+nayna.patel=hp@lists.launchpad.net]
 *On Behalf Of *Suchi Sinha (susinha)
 *Sent:* Thursday, March 14, 2013 3:35 PM
 *To:* openstack@lists.launchpad.net
 *Subject:* [Openstack] Swift PUT error

 ** **

 We are seeing lot of this error when we do  load/ stress testing on our
 swift  cluster..

 Our assumption  connection  time between  proxy  and object  server is
 timeing out.

 We increase client time out option. Still  no luck..

 Anybody  else has seen  this erro.. 

 ** **

 ERROR __call__ error with PUT

 ** **

 Traceback (most recent call last):

   File /usr/lib/python2.7/dist-packages/swift/obj/server.py, line 932,
 in __call__

 res = method(req)

   File /usr/lib/python2.7/dist-packages/swift/common/utils.py, line
 1459, in wrapped

 return func(*a, **kw)

   File /usr/lib/python2.7/dist-packages/swift/obj/server.py, line 612,
 in PUT

 for chunk in iter(lambda: reader(self.network_chunk_size), ''):

   File /usr/lib/python2.7/dist-packages/swift/obj/server.py, line 612,
 in lambda

 for chunk in iter(lambda: reader(self.network_chunk_size), ''):

   File /usr/lib/python2.7/dist-packages/eventlet/wsgi.py, line 147, in
 read

 return self._chunked_read(self.rfile, length)

   File /usr/lib/python2.7/dist-packages/eventlet/wsgi.py, line 137, in
 _chunked_read

 self.chunk_length = int(rfile.readline().split(;, 1)[0], 16)

 ValueError: invalid literal for int() with base 16: ''

 ** **

 ** **

 ** **

 ~Suchi

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




-- 
Gareth
*Cloud Computing, Openstack, Fitness, Basketball
*
*Novice Openstack contributer*
*My promise: if you find any spelling or grammar mistake in my email from
Mar 1 2013, notice me *
*and I'll donate 1$ or 1￥ to open organization specified by you.*
___
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]

[Chmouel Boudjnah]

On Fri, Mar 15, 2013 at 8:02 AM, Tomáš Šoltys tomas.sol...@gmail.com wrote:
 curl -k -v -H 'X-Storage-User: service:swift' -H 'X-Storage-Pass: 12345678'
 -X 'POST' http://localhost:5000/v2.0/auth

 But when for following it works:

 curl -k -v -X 'POST' http://localhost:5000/v2.0/tokens -d
 '{auth:{passwordCredentials:{username:swift, password:12345678},
 tenantName:service}}' -H 'Content-type: application/json' -H 'Accept:
 application/xml'

 What am I missing here?

The first one is auth v1 style auth the second one is v2 it seems that
there is a bug in the manual (feel free to raise a bug in
openstack-manuals launchpad project).

To verify an installation with a keystone install (i.e: v2) the swift
-V2.0 command is enough above the curl command is enough.

Chmouel.

___
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] question on the GRE Communication

[Aru s]

Thanks Logan

On Thu, Mar 14, 2013 at 7:16 PM, Logan McNaughton lo...@bacoosta.comwrote:

 I'm not sure about verifying the GRE tunnels, so I can't be much help
 there.

 As far as understanding how the tunneling happens, GRE is an open
 protocol, not specific to OpenStack, or any vendor, and googling GRE should
 give you plenty of information about it.
 On Mar 14, 2013 5:21 AM, Aru s arumo...@gmail.com wrote:

 Hi  Logan,

 Thanks for the reply. I have one more question.
 How we will check whether the tunneling is established or not?
 I have gone through lot of documents of gre setup and all are says that
 the ovs-vsctl show command will show the tunnel info.
 Also is there a doc to understand how the magic happens for tunneling.

 Regards,
 Arumon


 On Tue, Mar 12, 2013 at 6:23 PM, Logan McNaughton lo...@bacoosta.comwrote:

 For Quantum GRE tunneling, the network node and compute nodes need a NIC
 on your data network. You assign each of those NIC's an IP (for instance,
 192.168.1.1-3). Then (assuming you are using openvswitch with GRE
 tunneling) you set up your quantum configs. Look at the Quantum
 administration guide for an example of GRE tunneling with openvswitch.

 After that you just let it work its magic. All VM traffic is
 encapsulated inside GRE packets traveling between the nodes, it'll all look
 like packets in that 192.168.1-3 network.

 Once the packet reaches its destination node, the GRE encapsulation is
 removed and the VM packet is read.
 On Mar 12, 2013 6:36 AM, Aru s arumo...@gmail.com wrote:

  Hi,

 I am trying to configuring openstack with one controller and one
 network and two compute nodes.
 I am not able to understand how the communication of the VM's happens
 which are for the same tenant with same ip range but on the different
 compute hosts.
 Please help me to understand how GRE communication happens.

 Regards,
 Arumon

 ___
 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] question on the GRE Communication

[Aru s]

Thanks Robert.

On Thu, Mar 14, 2013 at 7:25 PM, Robert van Leeuwen 
robert.vanleeu...@spilgames.com wrote:

  Thanks for the reply. I have one more question.
  How we will check whether the tunneling is established or not?

 tcpdump can show you the GRE traffic:
 tcpdump -i ethX proto gre

 Cheers,
 Robert
 ___
 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] [Quantum] Access problem to Metadata server

[Sylvain Bauza]

Le 15/03/2013 08:20, Sammy Fung a écrit :

I am following this nice guide to configure Quantum.

https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/GRE/2NICs/OpenStack_Folsom_Install_Guide_WebVersion.rst


SNIP

I got timeout on HTTP request to 169.254.169.254 connecting from VM.

$ wget http://169.254.169.254/2009-04-04/meta-data/instance-id
Connecting to 169.254.169.254 (169.254.169.254:80 
http://169.254.169.254:80)

wget: can't connect to remote host (169.254.169.254): Connection timed out

But I got 404 Not Found if I connect to public IP port 8775 connecting 
from VM.


$ wget http://1.2.3.4:8775/2009-04-04/meta-data/instance-id
Connecting to 1.2.3.4:8775 http://1.2.3.4:8775 (1.2.3.4:8775 
http://1.2.3.4:8775)

wget: server returned error: HTTP/1.1 404 Not Found





Anything I can try for debug/solving it ?



As said in the guide, make sure your host running nova-api (incl. 
metadata, ie. 1.2.3.4) does have a route to the public IPs of your VMs.


-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] Swift PUT error

[Gareth]

I just know some basic about chunked data.
Our codes build chunked data with '%x\r\n%s\r\n' and '0\r\n\r\n', but in
eventlet.wsgi, it split with ';' I found that and have no more ideas.


On Fri, Mar 15, 2013 at 3:35 PM, Gareth academicgar...@gmail.com wrote:

 rfile.readline().split(;, 1)[0] here is empty string.

 Could give the size of object your uploaded, in bytes.


 On Fri, Mar 15, 2013 at 7:02 AM, Lokare, Bageshree 
 bageshree.lok...@hp.com wrote:

  Hello Suchi,

 ** **

 We are doing some similar stress testing for Swift and its working fine
 for a normal 100 user (1sec ramp-up)/1MB object size.

 Can you please give some more details on your set-up like,

 **-  **Object size

 **-  **Load/concurrent users

 **-  **Size of cluster

 **-  **# of LG and ramp-up time

 **-  **LG and swift target set-up (both in-cloud/out of cloud)***
 *

 ** **

 

 Thanks,

 SHREE

  

 ** **

 *From:* openstack-bounces+nayna.patel=hp@lists.launchpad.net [
 mailto:openstack-bounces+nayna.patel=hp@lists.launchpad.netopenstack-bounces+nayna.patel=hp@lists.launchpad.net]
 *On Behalf Of *Suchi Sinha (susinha)
 *Sent:* Thursday, March 14, 2013 3:35 PM
 *To:* openstack@lists.launchpad.net
 *Subject:* [Openstack] Swift PUT error

 ** **

 We are seeing lot of this error when we do  load/ stress testing on our
 swift  cluster..

 Our assumption  connection  time between  proxy  and object  server is
 timeing out.

 We increase client time out option. Still  no luck..

 Anybody  else has seen  this erro.. 

 ** **

 ERROR __call__ error with PUT

 ** **

 Traceback (most recent call last):

   File /usr/lib/python2.7/dist-packages/swift/obj/server.py, line 932,
 in __call__

 res = method(req)

   File /usr/lib/python2.7/dist-packages/swift/common/utils.py, line
 1459, in wrapped

 return func(*a, **kw)

   File /usr/lib/python2.7/dist-packages/swift/obj/server.py, line 612,
 in PUT

 for chunk in iter(lambda: reader(self.network_chunk_size), ''):

   File /usr/lib/python2.7/dist-packages/swift/obj/server.py, line 612,
 in lambda

 for chunk in iter(lambda: reader(self.network_chunk_size), ''):

   File /usr/lib/python2.7/dist-packages/eventlet/wsgi.py, line 147, in
 read

 return self._chunked_read(self.rfile, length)

   File /usr/lib/python2.7/dist-packages/eventlet/wsgi.py, line 137, in
 _chunked_read

 self.chunk_length = int(rfile.readline().split(;, 1)[0], 16)

 ValueError: invalid literal for int() with base 16: ''

 ** **

 ** **

 ** **

 ~Suchi

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




 --
 Gareth
 *Cloud Computing, Openstack, Fitness, Basketball
 *
 *Novice Openstack contributer*
 *My promise: if you find any spelling or grammar mistake in my email from
 Mar 1 2013, notice me *
 *and I'll donate 1$ or 1￥ to open organization specified by you.*




-- 
Gareth
*Cloud Computing, Openstack, Fitness, Basketball
*
*Novice Openstack contributer*
*My promise: if you find any spelling or grammar mistake in my email from
Mar 1 2013, notice me *
*and I'll donate 1$ or 1￥ to open organization specified by you.*
___
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] [Quantum] Why is 'subnet' introduced in Quantum API v2?

[Salvatore Orlando]

Hi Zhidong,

Please look inline for answers to your questions.

On 15 March 2013 08:05, Zd Yu zdyu2...@gmail.com wrote:

 I am confused by the existence of both 'network' and 'subnet'. According to
 v2 API spec[1], subnet is introduced to support IPAM capabilities. Can
 anyone elaborate it to me? For example, what is the benefit of creating 1
 network and 2 subnets by comparison with creating 2 networks that implicitly
 has one and only one subnet for each?

Even if you're right that for most application you always have one
network and one subnet, conceptually they're different concepts, and
they have been kept separated to allow either L2-only networks (where
for instance, you might want to use your own IPAM system), or enable
multiple subnets on the same network, which is not an uncommon
scenario.


 I do know that the original network did not support IP overlapping before
 subnet is introduced. But it is just an implementation issue, right?


Folsom actually supported overlapping IPs, but they were switched off
by default because this created problem with nova's security groups
and metadata servers.
In the Grizzly release Quantum supports security groups natively, and
metadata can now work with overlapping IPs.
You just need to ensure that allow_overlapping_ips is set to True in
your quantum.conf.

 Thanks,
 Zhidong

 [1] https://wiki.openstack.org/wiki/Quantum/APIv2-specification


 ___
 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

[Openstack] questions on if openstack as a public cloud

[Aru s]

Hi,

I have some general questions which are mentioned below at the time of
considering openstack as a public cloud.
Please help to understand.

1. strategy of creating new tenents.
2. outside network connectivity from VPC.
3. Billing and monitoring mechanism.
4. Roles and privillages assignes to the tenant user. (believe admin role
cannot be given)
Let me know if you have any refference case study for this.

Regards,
Arumon
___
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] [OSSG] Security Note: Selecting LXC as Nova Virtualization Driver can lead to data compromise.

[Clark, Robert Graham]

The following is the first of a series of OpenStack Security Notes that will be 
issued by the OpenStack Security Group. Security notes are similar to 
advisories; they address vulnerabilities in 3rd party tools typically used 
within OpenStack deployments and provide guidance on common configuration 
mistakes that can result in an insecure operating environment. 

Selecting LXC as Nova Virtualization Driver can lead to data compromise.
--

### Summary ###
LXC does not provide the same level of separation as hypervisors when chosen as 
the Nova 'virtualization driver'. Attempting to use LXC as a drop in 
replacement for a hypervisor can result in data exposure between tenants.

### Affected Services / Software ###
Nova, LXC, Libvirt, 'Virtualization Driver'

### Discussion ###
LXC (also known as Linux containers) is a virtualization technology that works 
at the operating system level. This is different from hardware virtualization, 
the approach used by other hypervisors such as KVM, Xen, and VMWare.
The quality of container isolation in LXC heavily depends on implementation. 
While pure LXC is generally well-isolated through various mechanisms (for 
example AppArmor in Ubuntu), LXC through libvirt is not. A guest who operates 
within one container is able to affect another containers cpu share, memory 
limit and block devices among other issues.
For more information on the effects of this issue see this [bug] 
(https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1088295)

### Recommended Actions ###
The OSSG advises that anyone deploying Nova in environments that require any 
level of separation use a hypervisor such as Xen, KVM, VMware or Hyper-V.

LXC security pivots on a system known as DAC (discretionary access control) 
which is not currently capable of providing strong isolation of guests. Work is 
underway to improve DAC but it's not ready for production use at this time.

The OSSG recommends against using LXC for enforcing secure separation of 
guests. Even with appropriate AppArmour policies applied.

### Contacts / References ###
Nova : http://docs.openstack.org/developer/nova/
LXC : http://lxc.sourceforge.net/
Libvirt : http://libvirt.org/
KVM : http://www.linux-kvm.org/page/Main_Page
Xen: http://xen.org/products/xenhyp.html
LXC DAC : https://wiki.ubuntu.com/UserNamespace
LXC LibVirt Discussion : 
https://www.berrange.com/posts/2011/09/27/getting-started-with-lxc-using-libvirt/
OpenStack Security Group : https://launchpad.net/~openstack-ossg

___
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] Call for help on Grizzly documentation

[Jérôme Gallard]

Hi Anne,

I'm a newbie in the documentation area but, I would like to give an help.

I haven't found any documentations (or open bug) regarding the cinder
multi-backend feature (
https://wiki.openstack.org/wiki/Cinder-multi-backend --
https://review.openstack.org/#/c/21815/ ).

Do you know if this documentation is planed to be written?
Can I open a bug for this?

Thanks a lot,
Jérôme

On Tue, Mar 12, 2013 at 3:27 PM, Anne Gentle a...@openstack.org wrote:
 Hi all,
 You all did great with DocImpact, but now that we're less than a month from
 release, the tiny doc team is facing a long list of doc bugs that won't be
 done by April 4th, many generated by DocImpact flags.

 We typically do a release of the docs about a month after the actual
 release date, to ensure packages are available and to try to get our doc bug
 backlog to a manageable level.

 As you can see from our backlog for operator docs in openstack-manuals [1]
 and API docs in api-site [2], there are over 50 confirmed doc bugs for
 Grizzly operator and admin docs and less than 20 for API docs. With those
 numbers we need all the help we can get.

 Please dive in, the patch process is just like code and fully documented.
 [3] We're on IRC in #openstack-doc and can answer any questions you have as
 you go.

 Thanks!
 Anne, Tom, Diane, Laura, Emilien, Daisy, and all the other doc peeps

 1. https://launchpad.net/openstack-manuals/+milestone/grizzly
 2. https://launchpad.net/openstack-api-site/+milestone/grizzly
 3. http://wiki.openstack.org/Documentation/HowTo

 ___
 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

[Openstack] OpenStack on OpenSuse 12.2

[Ashutosh Narayan]

Hi folks,

Has anybody on the list tried installing OpenStack [Folsom] on OpenSuSE
12.2 64 bit system ?
Is there any documentation available for the same ?

Thank you,
-- 
Ashutosh Narayan

http://ashutoshn.wordpress.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

[Openstack] User permissions on openstack compute nodes

[Nicolae Paladi]

Hi,

Could anyone please point me to a specification of user permissions
that OpenStack Nova requires when deployed on a compute node?

The installation
manualhttp://docs.openstack.org/trunk/openstack-compute/admin/content/manual-ubuntu-installation.html
directly
states that sudo/root permissions are required.

My question is, beyond installation of packages, are there any reasons for
Nova to be deployed within a user with root access on the compute nodes?

What I'm after is understanding whether a minimalistic set only consisting
of necessary user permissions (file access,etc) can be created for the user
that runs Nova
(hoping that the list will be a subset of the root's permissions).

cheers,
/Nicoae.
___
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] [OSSG] Security Note: Selecting LXC as Nova Virtualization Driver can lead to data compromise.

[Daniel P. Berrange]

On Fri, Mar 15, 2013 at 10:44:40AM +, Clark, Robert Graham wrote:
 The following is the first of a series of OpenStack Security Notes that will 
 be issued by the OpenStack Security Group. Security notes are similar to 
 advisories; they address vulnerabilities in 3rd party tools typically used 
 within OpenStack deployments and provide guidance on common configuration 
 mistakes that can result in an insecure operating environment. 
 
 Selecting LXC as Nova Virtualization Driver can lead to data compromise.
 --
 
 ### Summary ###
 LXC does not provide the same level of separation as hypervisors when chosen 
 as the Nova 'virtualization driver'. Attempting to use LXC as a drop in 
 replacement for a hypervisor can result in data exposure between tenants.
 
 ### Affected Services / Software ###
 Nova, LXC, Libvirt, 'Virtualization Driver'
 
 ### Discussion ###

 The quality of container isolation in LXC heavily depends on implementation. 
 While
 pure LXC is generally well-isolated through various mechanisms (for example 
 AppArmor
 in Ubuntu), LXC through libvirt is not. A guest who operates within one 
 container is
 able to affect another containers cpu share, memory limit and block devices 
 among other
 issues.

This is really wrong / misleading. Libvirt with LXC is perfectly capable of 
using
mandatory access control frameworks like SELinux  / AppArmour to isolate LXC
containers from each other. The issue is that such use of MAC whether with 
libvirt
LXC or other LXC impls is not practical when you want to be able to run full OS
installs in LXC. As such it is not possible to have OpenStack to make use of it.

I'd like this paragraph to be re-written to something like this


  ### Discussion ###

  The Libvirt LXC functionality exposed by OpenStack is built on the kernel
  namespace  cgroup technologies. Until Linux 3.8, there has been no support
  for separate user namespaces in the kernel. As such, there has been no way
  to securely isolate containers from each other or the host environment using
  DAC (discretionary access control). For example, they can escape their 
resource
  constraints by modifying cgroups settings, or attack the host via various 
files
  in the proc and sysfs filesystems. The use of MAC (mandatory access control)
  technologies like SELinux or AppArmour can mitigate these problems, but it is
  not practical to write MAC policies that would allow running full OS installs
  in LXC under OpenStack.

  Although initial user namespace support was merged in Linux 3.8, it is not
  yet complete, or mature enough to be considered secure. Work is ongoing to
  finish the kernel namespace support and enhance libvirt LXC to take advantage
  of it.

 For more information on the effects of this issue see this [bug]
 (https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1088295)
 
 ### Recommended Actions ###
 The OSSG advises that anyone deploying Nova in environments that require any 
 level of separation use a hypervisor such as Xen, KVM, VMware or Hyper-V.
 
 LXC security pivots on a system known as DAC (discretionary access control) 
 which is not currently capable of providing strong isolation of guests. Work 
 is underway to improve DAC but it's not ready for production use at this time.
 
 The OSSG recommends against using LXC for enforcing secure separation of 
 guests. Even with appropriate AppArmour policies applied.
 
 ### Contacts / References ###
 Nova : http://docs.openstack.org/developer/nova/
 LXC : http://lxc.sourceforge.net/
 Libvirt : http://libvirt.org/
 KVM : http://www.linux-kvm.org/page/Main_Page
 Xen: http://xen.org/products/xenhyp.html
 LXC DAC : https://wiki.ubuntu.com/UserNamespace
 LXC LibVirt Discussion : 
 https://www.berrange.com/posts/2011/09/27/getting-started-with-lxc-using-libvirt/
 OpenStack Security Group : https://launchpad.net/~openstack-ossg
 
 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp

-- 
|: http://berrange.com  -o-http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org  -o- http://virt-manager.org :|
|: http://autobuild.org   -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org   -o-   http://live.gnome.org/gtk-vnc :|

___
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 on OpenSuse 12.2

[Andreas Jaeger]

On 03/15/2013 12:20 PM, Ashutosh Narayan wrote:

Hi folks,

Has anybody on the list tried installing OpenStack [Folsom] on OpenSuSE
12.2 64 bit system ?
Is there any documentation available for the same ?


Hi Ashutosh,

yes, a couple of guys have, packages are available as documented at 
http://wiki.openstack.org/Packaging/SUSE

and also Vincent's blog post:
http://www.vuntz.net/journal/post/2012/12/21/DevStack-on-openSUSE%2C-or-how-to-quickly-setup-OpenStack-on-openSUSE

Please see http://en.opensuse.org/Portal:OpenStack for further information.

Btw. I suggest to use openSUSE 12.3 since openSUSE 12.3 comes with 
Folsom packages, see Vincent's blog post at:

http://www.vuntz.net/journal/post/2013/03/13/openSUSE-12.3-is-out%2C-with-OpenStack-love

Andreas
--
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126

___
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] How can I know the version if I installed from source code?

[Богдан До]

 You can try this
$sudo grep Version.*20 $(find 
{/opt/stack,/usr/local/lib/python2.{6,7}/dist-packages} -type f -name PKG-INFO)


Четверг,  7 марта 2013, 11:09 +08:00 от Ray Sun qsun01...@cienet.com.cn:
Is there any method to get the openstack version if I installed from openstack 
source code?

Thanks a lot.

- Ray Best Regards

CIeNET Technologies (Beijing) Co., Ltd
Technical Manager
Email:  qsun01...@cienet.com.cn
Office Phone: +86-01081470088-7079
Mobile Phone:  +86-13581988291
___
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] hostname change on hardware nodes

[JuanFra Rodriguez Cardoso]

Hi David:

Some useful tables for your needs: nova.services, nova.instances...

Regards,
---
JuanFra


2013/3/15 David Stearns dstea...@gnipcentral.com

 Hi all,
 I'm trying to recover from a mass renaming of our hardware nodes and have
 been having a bit of trouble.

 After changing the hostname on all of them nova-manage service list show
 all the old hostname (in the dead state) and all the new host names.  My
 first question is how do I remove old services from this list. (eg, if the
 hardware dies) and I just want to remove it from the list completely.

 My second question is what else do I need to change to get the hostname
 change to work correctly.  Right now I believe most operations on instances
 are broken because the host entry on the table points to the old host
 instead of the new one, so deleting a host will hang, etc.

 Thanks
 -David Stearns

 ___
 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] Call for help on Grizzly documentation

[Anne Gentle]

Yes, go ahead. Use the guidelines we have for Doc bug triage. [1]

Hey Bas, a DocImpact would have been ideal on that commit message so we
could already have a doc bug logged. [2]

Thanks,
Anne

1.
https://wiki.openstack.org/wiki/Documentation/HowTo#Doc_Bug_Triaging_Guidelines
2.
https://wiki.openstack.org/wiki/Documentation/HowTo#Using_the_DocImpact_Flag_in_a_Commit_Message




On Fri, Mar 15, 2013 at 6:11 AM, Jérôme Gallard jeronimo...@gmail.comwrote:

 Hi Anne,

 I'm a newbie in the documentation area but, I would like to give an help.

 I haven't found any documentations (or open bug) regarding the cinder
 multi-backend feature (
 https://wiki.openstack.org/wiki/Cinder-multi-backend --
 https://review.openstack.org/#/c/21815/ ).

 Do you know if this documentation is planed to be written?
 Can I open a bug for this?

 Thanks a lot,
 Jérôme

 On Tue, Mar 12, 2013 at 3:27 PM, Anne Gentle a...@openstack.org wrote:
  Hi all,
  You all did great with DocImpact, but now that we're less than a month
 from
  release, the tiny doc team is facing a long list of doc bugs that won't
 be
  done by April 4th, many generated by DocImpact flags.
 
  We typically do a release of the docs about a month after the actual
  release date, to ensure packages are available and to try to get our doc
 bug
  backlog to a manageable level.
 
  As you can see from our backlog for operator docs in openstack-manuals
 [1]
  and API docs in api-site [2], there are over 50 confirmed doc bugs for
  Grizzly operator and admin docs and less than 20 for API docs. With those
  numbers we need all the help we can get.
 
  Please dive in, the patch process is just like code and fully documented.
  [3] We're on IRC in #openstack-doc and can answer any questions you have
 as
  you go.
 
  Thanks!
  Anne, Tom, Diane, Laura, Emilien, Daisy, and all the other doc peeps
 
  1. https://launchpad.net/openstack-manuals/+milestone/grizzly
  2. https://launchpad.net/openstack-api-site/+milestone/grizzly
  3. http://wiki.openstack.org/Documentation/HowTo
 
  ___
  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

[Openstack] Cinder Multi-Backend Documentation

[Jérôme Gallard]

Hi John, Michael,

I would like to help for the Cinder documentation.

I have noticed that there is no open bug for the multi-backend documentation.
Anne allowed me to open a bug (
https://lists.launchpad.net/openstack/msg21938.html ).
Is it OK for you if I assign this bug to me or do you have any other
plans for the writing of this documentation?

If it's OK for you, I will write this documentation with the help of:
https://wiki.openstack.org/wiki/Cinder-multi-backend

Thanks a lot,
Jérôme

___
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] Call for help on Grizzly documentation

[Michael Basnight]

Of course... I spaced. I'd love to review the doc for this.

Sent from my digital shackles

On Mar 15, 2013, at 5:47 AM, Anne Gentle 
a...@openstack.orgmailto:a...@openstack.org wrote:

Yes, go ahead. Use the guidelines we have for Doc bug triage. [1]

Hey Bas, a DocImpact would have been ideal on that commit message so we could 
already have a doc bug logged. [2]

Thanks,
Anne

1. 
https://wiki.openstack.org/wiki/Documentation/HowTo#Doc_Bug_Triaging_Guidelines
2. 
https://wiki.openstack.org/wiki/Documentation/HowTo#Using_the_DocImpact_Flag_in_a_Commit_Message




On Fri, Mar 15, 2013 at 6:11 AM, Jérôme Gallard 
jeronimo...@gmail.commailto:jeronimo...@gmail.com wrote:
Hi Anne,

I'm a newbie in the documentation area but, I would like to give an help.

I haven't found any documentations (or open bug) regarding the cinder
multi-backend feature (
https://wiki.openstack.org/wiki/Cinder-multi-backend --
https://review.openstack.org/#/c/21815/ ).

Do you know if this documentation is planed to be written?
Can I open a bug for this?

Thanks a lot,
Jérôme

On Tue, Mar 12, 2013 at 3:27 PM, Anne Gentle 
a...@openstack.orgmailto:a...@openstack.org wrote:
 Hi all,
 You all did great with DocImpact, but now that we're less than a month from
 release, the tiny doc team is facing a long list of doc bugs that won't be
 done by April 4th, many generated by DocImpact flags.

 We typically do a release of the docs about a month after the actual
 release date, to ensure packages are available and to try to get our doc bug
 backlog to a manageable level.

 As you can see from our backlog for operator docs in openstack-manuals [1]
 and API docs in api-site [2], there are over 50 confirmed doc bugs for
 Grizzly operator and admin docs and less than 20 for API docs. With those
 numbers we need all the help we can get.

 Please dive in, the patch process is just like code and fully documented.
 [3] We're on IRC in #openstack-doc and can answer any questions you have as
 you go.

 Thanks!
 Anne, Tom, Diane, Laura, Emilien, Daisy, and all the other doc peeps

 1. https://launchpad.net/openstack-manuals/+milestone/grizzly
 2. https://launchpad.net/openstack-api-site/+milestone/grizzly
 3. http://wiki.openstack.org/Documentation/HowTo

 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : 
 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.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] PTL Election Results

[Monty Taylor]

The PTL elections for the Havana cycle have completed. The new PTL's are:

Nova: Russell Bryant
Ceilometer: Julien Danjou
Keystone: Dolph Matthews

Congratulations!

As a side note, we had over 50% participation in each of the three
elections, which I have been told is actually a really good turnout.

Monty

___
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] question on the GRE Performance

[小包]

Hi Guys，

*in my test, i found OVS GRE performance so lower, for example：*
*100Mbits Switch， GRE just 26Mbits speed，but use linux bridge 95Mbits,*
*
*
*so, my question is: why GRE speed low, or may be my config not right,*
*
*
*
*
*Thanks,*
*Tommy*
___
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] Technical Committee Nominations are Open

[Monty Taylor]

Now that the TC elections have ended, we now have three at-large seats open.

https://wiki.openstack.org/wiki/TC_Elections_Spring_2013

Mar 15 - 21: Open candidacy to directly-elected TC positions
Mar 22 - 28: TC elections

The persons ranking 1st and 2nd will get one-year seats on the TC, and
the person ranking 3rd will be elected for a 6-month seat as a
replacement for Russell Bryant who is now granted a PTL seat.

The electorate for the TC direct seats election are the Foundation
individual members that are also committers for an official OpenStack
project, over the Folsom-Grizzly timeframe, up to 23:59 PST on February
28, 2013.

Any member of the election electorate can propose his candidacy for this
election. No nomination is required. They do so by sending an email to
the openstack@lists.launchpad.net mailing-list, which the subject: TC
candidacy. The email can include a description of the candidate
platform. The candidacy is then confirmed by one of the election
officials, after verification of the electorate status of the candidate.

Note: PTLs that just got elected in the previous election are
automatically granted a 6-month term seat on the TC, and therefore
cannot run for this election.

___
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] [Cinder] OpenStack Block Storage Grizzly RC1 available

[Thierry Carrez]

Hello everyone,

The second project to publish a release candidate in preparation for the
Grizzly release is OpenStack Block Storage (code named Cinder). The RC1
is available for download at:

https://launchpad.net/cinder/grizzly/grizzly-rc1

Congrats to the Cinder crew!

Unless release-critical issues are found that warrant a release
candidate respin, this RC1 will be formally released as the 2013.1 final
version on April 4. You are therefore strongly encouraged to test and
validate this tarball.

Alternatively, you can directly test the milestone-proposed branch at:
https://github.com/openstack/cinder/tree/milestone-proposed

If you find an issue that could be considered release-critical, please
file it at:

https://bugs.launchpad.net/cinder/+filebug

and tag it *grizzly-rc-potential* to bring it to the release crew's
attention.

Note that the master branch of Cinder is now open for Havana
development, and feature freeze restrictions no longer apply.

Regards,

-- 
Thierry Carrez (ttx)
Release Manager, OpenStack

___
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] TC candidacy

[Michael Still]

Hi. I'd like to run for the TC Spring 2013 election. I am a senior
software engineer at Rackspace in their OpenStack group, and have
worked in a variety of cloud devops roles for the last seven years.
I think my operations experience gives me an interesting perspective
into where OpenStack should be going in the next few years.

My basic platform is the same as for the Nova PTL election [1] -- I
think we need to get better at closing bugs, and selecting defaults
which work out of the box for OpenStack deployers. We are blessed
with a very engaged user community, and we need to focus us much as
possible on giving new users a good experience.

I am an active Nova and Oslo core reviewer and frequently appear in
the top ten contributors for Nova in a given month. I am a very active
code reviewer, especially for Nova. I am also serve on the OpenStack
Vulnerability Management Team. I strongly believe in the future of
OpenStack and want to be part of that success in any way I can. For
the last two years my non-OpenStack open source contributions have
mainly been as Director for linux.conf.au 2013, which was the largest
OpenStack event to be run in Australia so far.

Thanks,
Michael

1: http://lists.openstack.org/pipermail/openstack-dev/2013-March/006417.html

___
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] Cinder Multi-Backend Documentation

[John Griffith]

Jerome,

I would love for you to assign it to yourself :)  You've already done quite
a bit of work here with Tempest etc, so as long as hubcap has no objections
I say go for it.  Just make sure you put him on the review since he's the
master-mind.

John

On Fri, Mar 15, 2013 at 8:03 AM, Jérôme Gallard jeronimo...@gmail.comwrote:

 Hi John, Michael,

 I would like to help for the Cinder documentation.

 I have noticed that there is no open bug for the multi-backend
 documentation.
 Anne allowed me to open a bug (
 https://lists.launchpad.net/openstack/msg21938.html ).
 Is it OK for you if I assign this bug to me or do you have any other
 plans for the writing of this documentation?

 If it's OK for you, I will write this documentation with the help of:
 https://wiki.openstack.org/wiki/Cinder-multi-backend

 Thanks a lot,
 Jérôme

___
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] TC candidacy

[Thierry Carrez]

Hi everyone,

I'd like to run for reelection to one of the Technical Committee
directly-elected seats.

For those who don't know me, I've been handling release management
duties for OpenStack since November 2010, a work currently sponsored by
the OpenStack Foundation. My involvement is mostly around project
coordination, keeping a global view and trying to anticipate issues as
our development community grows even larger. I'm also heading the
Vulnerability Management team, which handles incoming security issues
reports. On the development side, I authored the rootwrap framework
which is being used by a few of our projects, and whenever I find some
free time, I'm working on improving it.

I've been regularly elected by our community to the Project Policy Board
and Technical Committee directly-elected seats for the last two years. I
was heavily involved in the transition to our new governance, authored
the Technical Committee charter, and have been chosen to chair it for
the past 6 months.

I think it's important that the Technical Committee contains
representation from the horizontal functions within the project (Docs,
QA, Infrastructure, Vulnerability management, Release management...),
since each project is already represented by the seats granted for all PTLs.

Over the last 30 months we grew from 2 projects to 10 projects, and I'm
proud to be part of this community which successfully managed to handle
growth and adoption while preserving our ideals of open design and open
development.

The challenges ahead of us include accommodating further growth, resist
fragmentation, and maintaining efficiency and coherence as we grow well
past Dunbar's number. I hope that you place me in a position where I can
help us through those challenges.

Thanks,

-- 
Thierry Carrez (ttx)

___
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] Cinder Multi-Backend Documentation

[Michael Basnight]

+my openstack email. 

I'd love to review. 

Sent from my digital shackles

On Mar 15, 2013, at 8:30 AM, John Griffith john.griff...@solidfire.com wrote:

 Jerome,
 
 I would love for you to assign it to yourself :)  You've already done quite a 
 bit of work here with Tempest etc, so as long as hubcap has no objections I 
 say go for it.  Just make sure you put him on the review since he's the 
 master-mind.
 
 John
 
 On Fri, Mar 15, 2013 at 8:03 AM, Jérôme Gallard jeronimo...@gmail.com wrote:
 Hi John, Michael,
 
 I would like to help for the Cinder documentation.
 
 I have noticed that there is no open bug for the multi-backend documentation.
 Anne allowed me to open a bug (
 https://lists.launchpad.net/openstack/msg21938.html ).
 Is it OK for you if I assign this bug to me or do you have any other
 plans for the writing of this documentation?
 
 If it's OK for you, I will write this documentation with the help of:
 https://wiki.openstack.org/wiki/Cinder-multi-backend
 
 Thanks a lot,
 Jérôme
 
 ___
 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] using vlan tagged ports in cluster

[Rain Li]

Hi, JR,

You should check your route. Before ovs-vsctl add-port br-ex p1p1.4, you
should have the route entry like:
192.168.251.0   0.0.0.0  255.255.255.0 U 0 0 0 p1p1.4
But after that, since p1p1.4 is plugged in br-ex, you should change the
above route to go through br-ex, and may also change other (default route)
to this interface as well, if they originally go through p1p1.4.

Regards,
Rain


On Thu, Mar 14, 2013 at 5:22 AM, JR botem...@gmail.com wrote:

 Greetings,

 I'm setting up openstack on some machines using

 https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst
 .

 I'm using 3 nodes: a controller, network node and compute node.  All the
 network interfaces are VLAN tagged use the same underlying physical 10G,
 e.g.,

 controller: p1p1.4 (public net: 192.168.251.*/24), p1p1.5 (management
 net: 10.10.10.*/24)
 network:p1p1.4 (public net: 192.168.251.*/24), p1p1.5 (management
 net: 10.10.10.*/24), p1p1.6 (vm net: 10.20.20.*/24)

 # I haven't gotten to the compute node yet but it should be
 compute:   p1p1.5 (management net: 10.10.10.*/24), p1p1.6 (vm net:
 10.20.20.*/24)

 When I bring up my openvswitch bridges on the network node, I can not
 longer get out to the public net (see *MORE* below).

 I'm running ubuntu 12.10 and have run apt-get dist-upgrade.  The 10G
 nics are intel 82599EB.  ubuntu seems a bit flakey; initially I'd
 created /etc/udev/rules/70-persistent-net.rules to map p1p1 to eth2,
 however, the config was ignored and eth2 wound up being a 1G NIC.

 Is it not allowed to use VLAN interfaces for my networks?

 If I remove, say, the br-ex bridge I can get out again:
 root@nebula03:~# ping 192.168.251.1
 PING 192.168.251.1 (192.168.251.1) 56(84) bytes of data.
 ^C
 --- 192.168.251.1 ping statistics ---
 1 packets transmitted, 0 received, 100% packet loss, time 0ms

 root@nebula03:~# ovs-vsctl del-port p1p1.4
 root@nebula03:~# ovs-vsctl del-br br-ex
 root@nebula03:~# ping 192.168.251.1
 PING 192.168.251.1 (192.168.251.1) 56(84) bytes of data.
 64 bytes from 192.168.251.1: icmp_req=1 ttl=64 time=0.650 ms
 ^C
 --- 192.168.251.1 ping statistics ---
 1 packets transmitted, 1 received, 0% packet loss, time 0ms
 rtt min/avg/max/mdev = 0.650/0.650/0.650/0.000 ms
 root@nebula03:~#


 Thanks for any help,
 JR

 
 *MORE*
 
 root@nebula03:~# ovs-vsctl show
 1bdf2f73-1a5d-4893-b745-7501557acaea
 Bridge br-int
 Port br-int
 Interface br-int
 type: internal
 Bridge br-ex
 Port br-ex
 Interface br-ex
 type: internal
 Port p1p1.4
 Interface p1p1.4
 Bridge br-vm
 Port br-vm
 Interface br-vm
 type: internal
 Port p1p1.6
 Interface p1p1.6
 ovs_version: 1.4.3
 root@nebula03:~# ifconfig p1.4
 p1.4: error fetching interface information: Device not found
 root@nebula03:~# ifconfig p1p1.4
 p1p1.4Link encap:Ethernet  HWaddr 90:e2:ba:2c:8a:08
   inet addr:192.168.251.92  Bcast:192.168.251.255
 Mask:255.255.255.0
   inet6 addr: fe80::92e2:baff:fe2c:8a08/64 Scope:Link
   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
   RX packets:20964 errors:0 dropped:0 overruns:0 frame:0
   TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:0
   RX bytes:22269341 (22.2 MB)  TX bytes:594 (594.0 B)

 root@nebula03:~# ping 192.168.251.1
 PING 192.168.251.1 (192.168.251.1) 56(84) bytes of data.
 ^C
 --- 192.168.251.1 ping statistics ---
 2 packets transmitted, 0 received, 100% packet loss, time 1007ms

 root@nebula03:~# ping 192.168.251.91`
  ^C
 root@nebula03:~# ping 192.168.251.91
 PING 192.168.251.91 (192.168.251.91) 56(84) bytes of data.
 ^C





 ___
 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

[Openstack] Horizon logging?

[Wyllys Ingersoll]

I want to put some debug logging statements in a custom overrides.py module 
for Horizon.  But I can't figure out where the messages will be logged.  They 
don't go in the apache logs and they don't appear in any of the nova logs.  
Horizon doesn't appear to have its own logging, so Im a little stumped.

Im using the standard LOGGING definition in 
/etc/openstack_dashboard/local_settings.py:

LOGGING = {
'version': 1,
# When set to True this will disable all logging except
# for loggers specified in this configuration dictionary. Note that
# if nothing is specified here and disable_existing_loggers is True,
# django.db.backends will still log unless it is disabled explicitly.
'disable_existing_loggers': False,
'handlers': {
'null': {
'level': 'DEBUG',
'class': 'django.utils.log.NullHandler',
},
'console': {
# Set the level to DEBUG for verbose output logging.
'level': 'DEBUG',
'class': 'logging.StreamHandler',
},
},
'loggers': {
# Logging from django.db.backends is VERY verbose, send to null
# by default.
'django.db.backends': {
'handlers': ['null'],
'propagate': False,
},
'horizon': {
'handlers': ['console'],
'propagate': False,
},
'openstack_dashboard': {
'handlers': ['console'],
'propagate': False,
},
'novaclient': {
'handlers': ['console'],
'propagate': False,
},
'keystoneclient': {
'handlers': ['console'],
'propagate': False,
},
'glanceclient': {
'handlers': ['console'],
'propagate': False,
},
'nose.plugins.manager': {
'handlers': ['console'],
'propagate': False,
}
}
}


My custom override module just uses 
LOG = logging.getLogger(__name__)

and then when I want to log something, I'm using:
LOG.debug(Some message…)

Ideally, I think I'd like to have horizon stuff go into its own log file, but 
if that's too involved, I'd be happy to have them in the standard syslog file 
or even one of the nova logs. Any suggestions here would be greatly appreciated.

thanks,
  Wyllys


___
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] TC candidacy

[Michael Still]

On Fri, Mar 15, 2013 at 11:27 AM, Michael Still mi...@stillhq.com wrote:
 Hi. I'd like to run for the TC Spring 2013 election. I am a senior
 software engineer at Rackspace in their OpenStack group, and have
 worked in a variety of cloud devops roles for the last seven years.
 I think my operations experience gives me an interesting perspective
 into where OpenStack should be going in the next few years.

I was just asked what my thoughts on integrated projects are, so I
figured I should address that in public.

First off, the TC has oversight on all technical matters [1], so
while project incubation and integration is a topic that the TC
handles, it isn't the only thing I'd expect a well running TC to
handle. Examples of other things that the TC should be caring about
are:

- what languages we develop in
- what libraries we standardise on and if the existing standards are
still the best choices (for example, is sqlalchemy still the best way
of handling database abstraction?)
- how our CI infrastructure helps us run the project

To specifically address the incubation / integration question, I think
that OpenStack runs the risk of becoming distracted with too many
projects. We need to remember that the foundation is still quite
young, as is our community in general. I personally think that
OpenStack should be focussing on Infrastructure as a Service problems
for now, with the intention of expanding that scope later when we have
a solid stable base of infrastructure projects.

I can see why it is attractive for projects to want to become
incubated, especially because it means they get a bunch of (mainly CI)
infrastructure for free, as well as a lot of mind share from the
association. We need to remember that our CI resources are limited
however, and we need to be careful not to overload that team.
Additionally, each project we add makes it hard for us to define who
is distributing OpenStack. Do they have to ship every integrated
project? Even if its not relevant to the product they're trying to
build?

We live in a complicated world though. I think each of these decisions
should be made on its individual merits based on the facts that are
true at the time. I also think the TC is on the right track here at
the moment, so I don't think we need to wrap a bunch of super formal
policy around this area at the moment.

Hopefully that helps.

Cheers,
Michael

1: https://wiki.openstack.org/wiki/Governance/TechnicalCommittee

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

[Kuo Hugo]

It should be a doc bug in the instruction .

The first one is v1.0 auth (legacy auth)
The URL suppose to be http://localhost:5000/auth/v1.0


Hope it help


2013/3/15 Tomáš Šoltys tomas.sol...@gmail.com

 Hi,

 I am following the OpenStack WalkThrough instructions and I am failing to
 verify my setup as described here:

 http://docs.openstack.org/folsom/openstack-compute/install/yum/content/verify-swift-installation.html

 In this forum I have found that the instructions are not exactly correct
 so I tried what was suggested but without any success.

 Following command always return '404 Not Found'

 curl -k -v -H 'X-Storage-User: service:swift' -H 'X-Storage-Pass:
 12345678' -X 'POST' http://localhost:5000/v2.0/auth

 But when for following it works:

 curl -k -v -X 'POST' http://localhost:5000/v2.0/tokens -d
 '{auth:{passwordCredentials:{username:swift,
 password:12345678}, tenantName:service}}' -H 'Content-type:
 application/json' -H 'Accept: application/xml'

 What am I missing here?

 Thanks

 Tomáš Šoltys

 tomas.sol...@gmail.com
 http://www.range-software.com
 (+420) 776-843-663

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




-- 
+Hugo Kuo+
h...@swiftstack.com
tonyt...@gmail.com
+886 935004793
___
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] [OSSG] Security Note: Selecting LXC as Nova Virtualization Driver can lead to data compromise.

[Bryan D. Payne]

 The quality of container isolation in LXC heavily depends on implementation. 
 While
 pure LXC is generally well-isolated through various mechanisms (for example 
 AppArmor
 in Ubuntu), LXC through libvirt is not. A guest who operates within one 
 container is
 able to affect another containers cpu share, memory limit and block devices 
 among other
 issues.

 This is really wrong / misleading. snip

   Although initial user namespace support was merged in Linux 3.8, it is not
   yet complete, or mature enough to be considered secure. Work is ongoing to
   finish the kernel namespace support and enhance libvirt LXC to take 
 advantage
   of it.

Point taken and thank you for the clarification.  As you note, doing
lxc securely is basically not possible on a current OpenStack
deployment.  This was the main take home point of the security note.
I'm happy to see that work is ongoing to help improve this feature,
and look forward to reviewing it when it is stable.

If you'd like to help with the wording of future notes, I encourage
you to take part in the weekly OSSG meetings:
https://wiki.openstack.org/wiki/Meetings/OpenStackSecurity

Cheers,
-bryan

___
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] [OSSG] Security Note: Selecting LXC as Nova Virtualization Driver can lead to data compromise.

[Daniel P. Berrange]

On Fri, Mar 15, 2013 at 09:05:30AM -0700, Bryan D. Payne wrote:
  The quality of container isolation in LXC heavily depends on 
  implementation. While
  pure LXC is generally well-isolated through various mechanisms (for 
  example AppArmor
  in Ubuntu), LXC through libvirt is not. A guest who operates within one 
  container is
  able to affect another containers cpu share, memory limit and block 
  devices among other
  issues.
 
  This is really wrong / misleading. snip
 
Although initial user namespace support was merged in Linux 3.8, it is not
yet complete, or mature enough to be considered secure. Work is ongoing to
finish the kernel namespace support and enhance libvirt LXC to take 
  advantage
of it.
 
 Point taken and thank you for the clarification.  As you note, doing
 lxc securely is basically not possible on a current OpenStack
 deployment.  This was the main take home point of the security note.
 I'm happy to see that work is ongoing to help improve this feature,
 and look forward to reviewing it when it is stable.
 
 If you'd like to help with the wording of future notes, I encourage
 you to take part in the weekly OSSG meetings:

Where/when was this wording discussed though ? I don't see anything about
LXC mentioned in the logs of the last two meetings in March ? While IRC
may be a good place for ad-hoc discussions around an issue, I don't really
think it is a good forum for reviewing of these final notices prior to an
announcement. Due to its real-time nature, IRC hits timezone problems
which can prevent relevant from people attending. A posting to an email
list gives time for all relevant parties to provide feedback.

Regards,
Daniel
-- 
|: http://berrange.com  -o-http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org  -o- http://virt-manager.org :|
|: http://autobuild.org   -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org   -o-   http://live.gnome.org/gtk-vnc :|

___
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] [OSSG] Security Note: Selecting LXC as Nova Virtualization Driver can lead to data compromise.

[Bryan D. Payne]

 Where/when was this wording discussed though ?

It was discussed at the meetings on Jan 24, Jan 31, and Feb 7.

 may be a good place for ad-hoc discussions around an issue, I don't really
 think it is a good forum for reviewing of these final notices prior to an

The notes are also tracked through launchpad.  For example, this note
was done here:
https://bugs.launchpad.net/osn/+bug/1098582

We are also actively working to setup an OSSG mailing list to allow
for asynchronous discussion of such topics.  The openstack dev mailing
list is also perfectly suitable (usually we put [OSSG] in the
subject).

Finally, you are always welcome to read the meeting minutes online and
open discussions on the mailing list.

Since you are a member of OSSG, it's really just a matter of getting
involved through one of these many avenues and making your voice heard
as we work on new notes.

Cheers,
-bryan

___
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] using vlan tagged ports in cluster

[JR]

Rain, I owe you a beer!  That did the trick.  Thanks.

JR

On 3/15/2013 11:32 AM, Rain Li wrote:
 Hi, JR, 
 
 You should check your route. Before ovs-vsctl add-port br-ex p1p1.4,
 you should have the route entry like:
 192.168.251.0   0.0.0.0  255.255.255.0 U 0 0 0 p1p1.4
 But after that, since p1p1.4 is plugged in br-ex, you should change the
 above route to go through br-ex, and may also change other (default
 route) to this interface as well, if they originally go through p1p1.4.
 
 Regards,
 Rain
 
 
 On Thu, Mar 14, 2013 at 5:22 AM, JR botem...@gmail.com
 mailto:botem...@gmail.com wrote:
 
 Greetings,
 
 I'm setting up openstack on some machines using
 
 https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst.
 
 I'm using 3 nodes: a controller, network node and compute node.  All the
 network interfaces are VLAN tagged use the same underlying physical 10G,
 e.g.,
 
 controller: p1p1.4 (public net: 192.168.251.*/24), p1p1.5 (management
 net: 10.10.10.*/24)
 network:p1p1.4 (public net: 192.168.251.*/24), p1p1.5 (management
 net: 10.10.10.*/24), p1p1.6 (vm net: 10.20.20.*/24)
 
 # I haven't gotten to the compute node yet but it should be
 compute:   p1p1.5 (management net: 10.10.10.*/24), p1p1.6 (vm net:
 10.20.20.*/24)
 
 When I bring up my openvswitch bridges on the network node, I can not
 longer get out to the public net (see *MORE* below).
 
 I'm running ubuntu 12.10 and have run apt-get dist-upgrade.  The 10G
 nics are intel 82599EB.  ubuntu seems a bit flakey; initially I'd
 created /etc/udev/rules/70-persistent-net.rules to map p1p1 to eth2,
 however, the config was ignored and eth2 wound up being a 1G NIC.
 
 Is it not allowed to use VLAN interfaces for my networks?
 
 If I remove, say, the br-ex bridge I can get out again:
 root@nebula03:~# ping 192.168.251.1
 PING 192.168.251.1 (192.168.251.1) 56(84) bytes of data.
 ^C
 --- 192.168.251.1 ping statistics ---
 1 packets transmitted, 0 received, 100% packet loss, time 0ms
 
 root@nebula03:~# ovs-vsctl del-port p1p1.4
 root@nebula03:~# ovs-vsctl del-br br-ex
 root@nebula03:~# ping 192.168.251.1
 PING 192.168.251.1 (192.168.251.1) 56(84) bytes of data.
 64 bytes from 192.168.251.1 http://192.168.251.1: icmp_req=1
 ttl=64 time=0.650 ms
 ^C
 --- 192.168.251.1 ping statistics ---
 1 packets transmitted, 1 received, 0% packet loss, time 0ms
 rtt min/avg/max/mdev = 0.650/0.650/0.650/0.000 ms
 root@nebula03:~#
 
 
 Thanks for any help,
 JR
 
 
 *MORE*
 
 root@nebula03:~# ovs-vsctl show
 1bdf2f73-1a5d-4893-b745-7501557acaea
 Bridge br-int
 Port br-int
 Interface br-int
 type: internal
 Bridge br-ex
 Port br-ex
 Interface br-ex
 type: internal
 Port p1p1.4
 Interface p1p1.4
 Bridge br-vm
 Port br-vm
 Interface br-vm
 type: internal
 Port p1p1.6
 Interface p1p1.6
 ovs_version: 1.4.3
 root@nebula03:~# ifconfig p1.4
 p1.4: error fetching interface information: Device not found
 root@nebula03:~# ifconfig p1p1.4
 p1p1.4Link encap:Ethernet  HWaddr 90:e2:ba:2c:8a:08
   inet addr:192.168.251.92  Bcast:192.168.251.255
 Mask:255.255.255.0
   inet6 addr: fe80::92e2:baff:fe2c:8a08/64 Scope:Link
   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
   RX packets:20964 errors:0 dropped:0 overruns:0 frame:0
   TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
   collisions:0 txqueuelen:0
   RX bytes:22269341 (22.2 MB)  TX bytes:594 (594.0 B)
 
 root@nebula03:~# ping 192.168.251.1
 PING 192.168.251.1 (192.168.251.1) 56(84) bytes of data.
 ^C
 --- 192.168.251.1 ping statistics ---
 2 packets transmitted, 0 received, 100% packet loss, time 1007ms
 
 root@nebula03:~# ping 192.168.251.91`
  ^C
 root@nebula03:~# ping 192.168.251.91
 PING 192.168.251.91 (192.168.251.91) 56(84) bytes of data.
 ^C
 
 
 
 
 
 ___
 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

Re: [Openstack] [Swift]

[Gareth]

Kuo's answering is the point. But v1.0 is not the answer because keystone
use v2.0 now.
Look at your docuement, http://AUTH_HOSTNAME:5000/auth/v2.0 and
http://AUTH_HOSTNAME:5000/v2.0
have been used.

The second works for me. Try these two yourself.


On Fri, Mar 15, 2013 at 11:55 PM, Kuo Hugo tonyt...@gmail.com wrote:

 It should be a doc bug in the instruction .

 The first one is v1.0 auth (legacy auth)
 The URL suppose to be http://localhost:5000/auth/v1.0


 Hope it help


 2013/3/15 Tomáš Šoltys tomas.sol...@gmail.com

 Hi,

 I am following the OpenStack WalkThrough instructions and I am failing to
 verify my setup as described here:

 http://docs.openstack.org/folsom/openstack-compute/install/yum/content/verify-swift-installation.html

 In this forum I have found that the instructions are not exactly correct
 so I tried what was suggested but without any success.

 Following command always return '404 Not Found'

 curl -k -v -H 'X-Storage-User: service:swift' -H 'X-Storage-Pass:
 12345678' -X 'POST' http://localhost:5000/v2.0/auth

 But when for following it works:

 curl -k -v -X 'POST' http://localhost:5000/v2.0/tokens -d
 '{auth:{passwordCredentials:{username:swift,
 password:12345678}, tenantName:service}}' -H 'Content-type:
 application/json' -H 'Accept: application/xml'

 What am I missing here?

 Thanks

 Tomáš Šoltys

 tomas.sol...@gmail.com
 http://www.range-software.com
 (+420) 776-843-663

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




 --
 +Hugo Kuo+
 h...@swiftstack.com
 tonyt...@gmail.com
 +886 935004793

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




-- 
Gareth
*Cloud Computing, Openstack, Fitness, Basketball
*
*Novice Openstack contributer*
*My promise: if you find any spelling or grammar mistake in my email from
Mar 1 2013, notice me *
*and I'll donate 1$ or 1￥ to open organization specified by you.*
___
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]

[Kuo Hugo]

As I know that legacy auth was been removed from ESSEX release in Keystone.





2013/3/15 Gareth academicgar...@gmail.com

 Kuo's answering is the point. But v1.0 is not the answer because keystone
 use v2.0 now.
 Look at your docuement, http://AUTH_HOSTNAME:5000/auth/v2.0 and 
 http://AUTH_HOSTNAME:5000/v2.0
 have been used.

 The second works for me. Try these two yourself.


 On Fri, Mar 15, 2013 at 11:55 PM, Kuo Hugo tonyt...@gmail.com wrote:

 It should be a doc bug in the instruction .

 The first one is v1.0 auth (legacy auth)
 The URL suppose to be http://localhost:5000/auth/v1.0


 Hope it help


 2013/3/15 Tomáš Šoltys tomas.sol...@gmail.com

 Hi,

 I am following the OpenStack WalkThrough instructions and I am failing
 to verify my setup as described here:

 http://docs.openstack.org/folsom/openstack-compute/install/yum/content/verify-swift-installation.html

 In this forum I have found that the instructions are not exactly correct
 so I tried what was suggested but without any success.

 Following command always return '404 Not Found'

 curl -k -v -H 'X-Storage-User: service:swift' -H 'X-Storage-Pass:
 12345678' -X 'POST' http://localhost:5000/v2.0/auth

 But when for following it works:

 curl -k -v -X 'POST' http://localhost:5000/v2.0/tokens -d
 '{auth:{passwordCredentials:{username:swift,
 password:12345678}, tenantName:service}}' -H 'Content-type:
 application/json' -H 'Accept: application/xml'

 What am I missing here?

 Thanks

 Tomáš Šoltys

 tomas.sol...@gmail.com
 http://www.range-software.com
 (+420) 776-843-663

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




 --
 +Hugo Kuo+
 h...@swiftstack.com
 tonyt...@gmail.com
 +886 935004793

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




 --
 Gareth
 *Cloud Computing, Openstack, Fitness, Basketball
 *
 *Novice Openstack contributer*
 *My promise: if you find any spelling or grammar mistake in my email from
 Mar 1 2013, notice me *
 *and I'll donate 1$ or 1￥ to open organization specified by you.*




-- 
+Hugo Kuo+
h...@swiftstack.com
tonyt...@gmail.com
+886 935004793
___
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] download ec2 creds fails consistently in horizon

[Jay Pipes]

It's actually not nova-cert that you need. It is the Keystone EC2
credentials API extension that is the problem. It only works for users
with admin role.

I logged a bug on it and am working on a fix:

https://bugs.launchpad.net/keystone/+bug/1136190

Best,
-jay

On 03/14/2013 10:57 AM, Wyllys Ingersoll wrote:
 
 I figured it out - nova-cert was not installed and running.  I need to add 
 this to my setup when EC2 is enabled, I wasn't aware of the dependency.
 
 -Wyllys
 
 
 
 On Mar 14, 2013, at 10:35 AM, Wyllys Ingersoll wyllys.ingers...@evault.com 
 wrote:
 

 I have EC2 configured correctly as far as I can tell because I am able to 
 view my containers using the S3 APIs and S3 tools such as CyberDuck or 
 s3curl.pl, using ec2 credentials returned by the keystone command line tool.

 However, when I use the Horizon user settings interface and select Download 
 EC2 Credentials, nothing happens and it eventually returns yet another 
 System Error.  

 According to the logs, the failure is because the call to request 
 os-certificates is timing out.  I know this is probably because some other 
 nova service is not running, but Im not sure which one it needs to complete 
 this transaction.  It'd be nice if the error message somewhere that 
 indicated which service was not responding or what to do about it.   Can 
 someone tell me which nova service I need to have running and configured to 
 issue os-certificates?

 Also, I really only want the EC2 credentials to be created and downloaded, 
 Im not so much interested in the X509 certificates at this point.  It'd be 
 nice if the user settings EC2 panel had more options, such as just creating 
 and/or listing the EC2 access ID and Key for a particular user rather than 
 assuming you want/need everything all at once.

 thanks,
  Wyllys Ingersoll
  EVault



 ___
 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] Unauthenticated service probe for OpenStack components

[Jay Pipes]

Or, alternately, you can post to the endpoint root (without the version)
and that should respond with a 300 Multiple Choice for most of the
OpenStack service endpoints.

Best,
-jay

On 03/14/2013 04:52 PM, Dean Troyer wrote:
 On Thu, Mar 14, 2013 at 3:40 PM, Tim Bell tim.b...@cern.ch wrote:
 Currently, curl to the service URL just gives 401 error.
 
 Check the exit code, it should be 0 because that 401 error is
 generated by the api server.  It's alive and responding, just not with
 200 codes.  If the server doesn't respond curl's exit code is non-zero
 (7 I think?).
 
 We did the same thing in DevStack for checking api server responses.
 
 dt
 

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

[Gareth]

I'm not familiar with that legacy auth =,=
In my experience, v1.0 works for tempauth, and v2.0 works for keystone.
The format of two kinds of url is not totally same.
My keystone env use http://AUTH_HOSTNAME:5000/v2.0 in this case.
And my tempauth use http://127.0.0.1:8080/auth/v1.0

I think Tomáš Šoltys has misused path as /auth/v2.0. It should be /v2.0 or
/auth/v2.0
BTW, I use newest codes.

Any misunderstanding from me?


On Sat, Mar 16, 2013 at 12:48 AM, Kuo Hugo tonyt...@gmail.com wrote:

 As I know that legacy auth was been removed from ESSEX release in
 Keystone.





 2013/3/15 Gareth academicgar...@gmail.com

 Kuo's answering is the point. But v1.0 is not the answer because keystone
 use v2.0 now.
 Look at your docuement, http://AUTH_HOSTNAME:5000/auth/v2.0 and 
 http://AUTH_HOSTNAME:5000/v2.0
 have been used.

 The second works for me. Try these two yourself.


 On Fri, Mar 15, 2013 at 11:55 PM, Kuo Hugo tonyt...@gmail.com wrote:

 It should be a doc bug in the instruction .

 The first one is v1.0 auth (legacy auth)
 The URL suppose to be http://localhost:5000/auth/v1.0


 Hope it help


 2013/3/15 Tomáš Šoltys tomas.sol...@gmail.com

 Hi,

 I am following the OpenStack WalkThrough instructions and I am failing
 to verify my setup as described here:

 http://docs.openstack.org/folsom/openstack-compute/install/yum/content/verify-swift-installation.html

 In this forum I have found that the instructions are not exactly
 correct so I tried what was suggested but without any success.

 Following command always return '404 Not Found'

 curl -k -v -H 'X-Storage-User: service:swift' -H 'X-Storage-Pass:
 12345678' -X 'POST' http://localhost:5000/v2.0/auth

 But when for following it works:

 curl -k -v -X 'POST' http://localhost:5000/v2.0/tokens -d
 '{auth:{passwordCredentials:{username:swift,
 password:12345678}, tenantName:service}}' -H 'Content-type:
 application/json' -H 'Accept: application/xml'

 What am I missing here?

 Thanks

 Tomáš Šoltys

 tomas.sol...@gmail.com
 http://www.range-software.com
 (+420) 776-843-663

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




 --
 +Hugo Kuo+
 h...@swiftstack.com
 tonyt...@gmail.com
 +886 935004793

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




 --
 Gareth
 *Cloud Computing, Openstack, Fitness, Basketball
 *
 *Novice Openstack contributer*
 *My promise: if you find any spelling or grammar mistake in my email
 from Mar 1 2013, notice me *
 *and I'll donate 1$ or 1￥ to open organization specified by you.*




 --
 +Hugo Kuo+
 h...@swiftstack.com
 tonyt...@gmail.com
 +886 935004793




-- 
Gareth
*Cloud Computing, Openstack, Fitness, Basketball
*
*Novice Openstack contributer*
*My promise: if you find any spelling or grammar mistake in my email from
Mar 1 2013, notice me *
*and I'll donate 1$ or 1￥ to open organization specified by you.*
___
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] download ec2 creds fails consistently in horizon

[Wyllys Ingersoll]

I am able to login as a non-admin user and access the containers.  

In addition to missing nova-cert, I also had to change the keystoneauth 
settings in /etc/swift/proxy-server.conf to add Member to the operator_roles 
list, which I suppose is equivalent to making a Member user the equivalent of 
an administrator for Swift.

-Wyllys


On Mar 15, 2013, at 1:02 PM, Jay Pipes jaypi...@gmail.com wrote:

 It's actually not nova-cert that you need. It is the Keystone EC2
 credentials API extension that is the problem. It only works for users
 with admin role.
 
 I logged a bug on it and am working on a fix:
 
 https://bugs.launchpad.net/keystone/+bug/1136190
 
 Best,
 -jay
 
 On 03/14/2013 10:57 AM, Wyllys Ingersoll wrote:
 
 I figured it out - nova-cert was not installed and running.  I need to add 
 this to my setup when EC2 is enabled, I wasn't aware of the dependency.
 
 -Wyllys
 
 
 
 On Mar 14, 2013, at 10:35 AM, Wyllys Ingersoll wyllys.ingers...@evault.com 
 wrote:
 
 
 I have EC2 configured correctly as far as I can tell because I am able to 
 view my containers using the S3 APIs and S3 tools such as CyberDuck or 
 s3curl.pl, using ec2 credentials returned by the keystone command line tool.
 
 However, when I use the Horizon user settings interface and select 
 Download EC2 Credentials, nothing happens and it eventually returns yet 
 another System Error.  
 
 According to the logs, the failure is because the call to request 
 os-certificates is timing out.  I know this is probably because some 
 other nova service is not running, but Im not sure which one it needs to 
 complete this transaction.  It'd be nice if the error message somewhere 
 that indicated which service was not responding or what to do about it.   
 Can someone tell me which nova service I need to have running and 
 configured to issue os-certificates?
 
 Also, I really only want the EC2 credentials to be created and downloaded, 
 Im not so much interested in the X509 certificates at this point.  It'd be 
 nice if the user settings EC2 panel had more options, such as just creating 
 and/or listing the EC2 access ID and Key for a particular user rather than 
 assuming you want/need everything all at once.
 
 thanks,
 Wyllys Ingersoll
 EVault
 
 
 
 ___
 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

[Openstack] TC candidacy

[Gary Kotton]

Hi,

I'd like to run for the Technical Committee in the up and coming elections.

I am a Principle Software Engineer at Red Hat. I have been actively 
developing OpenStack since the Essex release. I am currently a Quantum 
core developer. In addition to this I am also core on the Stable 
Maintenance team. I also have contribute to Nova, OSLO, documentation 
and devstack. In Nova the work was mainly focused on the Quantum 
integrations. My latest contribution was the VM ensembles, part of 
which was added in Grizzly release and hopefully will be completed in 
the up and coming Havana release. I spend most of my days reviewing, 
testing, debugging, documenting and developing with the goal of making 
OpenStack better. I am thankful to my employer Red Hat to have the 
opportunity and time to work on such and amazing project.


I have close to 18 years of experience in the industry. Over that course 
of time I have strived to produce quality, usable, robust and optimal 
solutions. I would like to bring all that experience to the table to 
ensure that we have a better product. We are working in a very healthy, 
dynamic and vibrant community. A few things that I would like to improve 
are the following:

- cross project interaction
- growth of the community
- sharing of ideas and information

In my spare time I run.

Thanks
Gary




___
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] question on the GRE Performance

[Rick Jones]

On 03/15/2013 08:05 AM, tommy(小包) wrote:

Hi Guys，

in my test, i found OVS GRE performance so lower, for example：
100Mbits Switch， GRE just 26Mbits speed，but use linux bridge
95Mbits,

so, my question is: why GRE speed low, or may be my config not right,/


95 and 26 Mbit/s measured at what level?  On the wire (including all 
the protocol headers) or to user level (after all the protocol headers)? 
That you were seeing 95 Mbit/s suggests user level but I'd like to make 
certain.


GRE adds header overhead, but I wouldn't think enough to take one from 
95 down to 26 Mbit/s to user level.  I would suggest looking at, in no 
particular order:


*) Netstat stats on your sender - is it retransmitting in one case and 
not the other?


*) per-CPU CPU utilization - is any one CPU on the sending, receiving or 
intervening iron saturating in one case and not the other?


and go from there. I'm guessing your tests are all bulk-transfer - you 
might want to consider adding some latency and/or aggregate small-packet 
performance tests.


happy benchmarking,

rick jones
the applicability varies,  but attached is some boilerplate I've 
built-up over time, on the matter of why is my network performance 
slow?  PS - the beforeafter utility mentioned is no longer available 
via ftp.cup.hp.com because ftp.cup.hp.com no longer exists.  I probably 
aught to put it up on ftp.netperf.org...



Some of my checklist items when presented with assertions of poor
network performance, in no particular order, numbered only for
convenience of reference:

1) Is *any one* CPU on either end of the transfer at or close to 100%
   utilization?  A given TCP connection cannot really take advantage
   of more than the services of a single core in the system, so
   average CPU utilization being low does not a priori mean things are
   OK.

2) Are there TCP retransmissions being registered in netstat
   statistics on the sending system?  Take a snapshot of netstat -s -t
   from just before the transfer, and one from just after and run it
   through beforeafter from
   ftp://ftp.cup.hp.com/dist/networking/tools:

   netstat -s -t  before
   transfer or wait 60 or so seconds if the transfer was already going
   netstat -s -t  after
   beforeafter before after  delta

3) Are there packet drops registered in ethtool -S statistics on
   either side of the transfer?  Take snapshots in a manner similar to
   that with netstat.

4) Are there packet drops registered in the stats for the switch(es)
   being traversed by the transfer?  These would be retrieved via
   switch-specific means.

5) What is the latency between the two end points.  Install netperf on
   both sides, start netserver on one side and on the other side run:

   netperf -t TCP_RR -l 30 -H remote

   and invert the transaction/s rate to get the RTT latency.  There
   are caveats involving NIC interrupt coalescing settings defaulting
   in favor of throughput/CPU util over latency:

   ftp://ftp.cup.hp.com/dist/networking/briefs/nic_latency_vs_tput.txt

   but when the connections are over a WAN latency is important and
   may not be clouded as much by NIC settings.

   This all leads into:

6) What is the *effective* TCP (or other) window size for the
   connection.  One limit to the performance of a TCP bulk transfer
   is:

   Tput = W(eff)/RTT

   The effective window size will be the lesser of:

   a) The classic TCP window advertised by the receiver. This is the
  value in the TCP header's window field shifted by the window
  scaling factor which was exchanged during connection
  establishment. The window scale factor is why one wants to get
  traces including the connection establishment.
   
  The size of the classic window will depend on whether/what the
  receiving application has requested via a setsockopt(SO_RCVBUF)
  call and the sysctl limits set in the OS.  If the receiving
  application does not call setsockopt(SO_RCVBUF) then under Linux
  the stack will autotune the advertised window based on other
  sysctl limits in the OS.  Other stacks may or may not autotune.
 
   b) The computed congestion window on the sender - this will be
  affected by the packet loss rate over the connection, hence the
  interest in the netstat and ethtool stats.

   c) The quantity of data to which the sending TCP can maintain a
  reference while waiting for it to be ACKnowledged by the
  receiver - this will be akin to the classic TCP window case
  above, but on the sending side, and concerning
  setsockopt(SO_SNDBUF) and sysctl settings.

   d) The quantity of data the sending application is willing/able to
  send at any one time before waiting for some sort of
  application-level acknowledgement.  FTP and rcp will just blast
  all the data of the file into the socket as fast as the socket
  will take it.  Scp has some application-layer windowing which
  may cause it to put less data out onto the connection 

Re: [Openstack] download ec2 creds fails consistently in horizon

[Jay Pipes]

On 03/15/2013 01:12 PM, Wyllys Ingersoll wrote:
 I am able to login as a non-admin user and access the containers.  

Your original post talked about the Download EC2 Credentials link not
working. That's what I was referring to. Nothing to do with Swift
containers.

-jay

 In addition to missing nova-cert, I also had to change the keystoneauth 
 settings in /etc/swift/proxy-server.conf to add Member to the 
 operator_roles list, which I suppose is equivalent to making a Member user 
 the equivalent of an administrator for Swift.
 
 -Wyllys
 
 
 On Mar 15, 2013, at 1:02 PM, Jay Pipes jaypi...@gmail.com wrote:
 
 It's actually not nova-cert that you need. It is the Keystone EC2
 credentials API extension that is the problem. It only works for users
 with admin role.

 I logged a bug on it and am working on a fix:

 https://bugs.launchpad.net/keystone/+bug/1136190

 Best,
 -jay

 On 03/14/2013 10:57 AM, Wyllys Ingersoll wrote:

 I figured it out - nova-cert was not installed and running.  I need to add 
 this to my setup when EC2 is enabled, I wasn't aware of the dependency.

 -Wyllys



 On Mar 14, 2013, at 10:35 AM, Wyllys Ingersoll 
 wyllys.ingers...@evault.com wrote:


 I have EC2 configured correctly as far as I can tell because I am able to 
 view my containers using the S3 APIs and S3 tools such as CyberDuck or 
 s3curl.pl, using ec2 credentials returned by the keystone command line 
 tool.

 However, when I use the Horizon user settings interface and select 
 Download EC2 Credentials, nothing happens and it eventually returns yet 
 another System Error.  

 According to the logs, the failure is because the call to request 
 os-certificates is timing out.  I know this is probably because some 
 other nova service is not running, but Im not sure which one it needs to 
 complete this transaction.  It'd be nice if the error message somewhere 
 that indicated which service was not responding or what to do about it.   
 Can someone tell me which nova service I need to have running and 
 configured to issue os-certificates?

 Also, I really only want the EC2 credentials to be created and downloaded, 
 Im not so much interested in the X509 certificates at this point.  It'd be 
 nice if the user settings EC2 panel had more options, such as just 
 creating and/or listing the EC2 access ID and Key for a particular user 
 rather than assuming you want/need everything all at once.

 thanks,
 Wyllys Ingersoll
 EVault



 ___
 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] download ec2 creds fails consistently in horizon

[Wyllys Ingersoll]

Yup, you are correct, I confused 2 different issues.  sorry for the confusion…




On Mar 15, 2013, at 2:58 PM, Jay Pipes jaypi...@gmail.com wrote:

 On 03/15/2013 01:12 PM, Wyllys Ingersoll wrote:
 I am able to login as a non-admin user and access the containers.  
 
 Your original post talked about the Download EC2 Credentials link not
 working. That's what I was referring to. Nothing to do with Swift
 containers.
 
 -jay
 
 In addition to missing nova-cert, I also had to change the keystoneauth 
 settings in /etc/swift/proxy-server.conf to add Member to the 
 operator_roles list, which I suppose is equivalent to making a Member user 
 the equivalent of an administrator for Swift.
 
 -Wyllys
 
 
 On Mar 15, 2013, at 1:02 PM, Jay Pipes jaypi...@gmail.com wrote:
 
 It's actually not nova-cert that you need. It is the Keystone EC2
 credentials API extension that is the problem. It only works for users
 with admin role.
 
 I logged a bug on it and am working on a fix:
 
 https://bugs.launchpad.net/keystone/+bug/1136190
 
 Best,
 -jay
 
 On 03/14/2013 10:57 AM, Wyllys Ingersoll wrote:
 
 I figured it out - nova-cert was not installed and running.  I need to add 
 this to my setup when EC2 is enabled, I wasn't aware of the dependency.
 
 -Wyllys
 
 
 
 On Mar 14, 2013, at 10:35 AM, Wyllys Ingersoll 
 wyllys.ingers...@evault.com wrote:
 
 
 I have EC2 configured correctly as far as I can tell because I am able to 
 view my containers using the S3 APIs and S3 tools such as CyberDuck or 
 s3curl.pl, using ec2 credentials returned by the keystone command line 
 tool.
 
 However, when I use the Horizon user settings interface and select 
 Download EC2 Credentials, nothing happens and it eventually returns yet 
 another System Error.  
 
 According to the logs, the failure is because the call to request 
 os-certificates is timing out.  I know this is probably because some 
 other nova service is not running, but Im not sure which one it needs to 
 complete this transaction.  It'd be nice if the error message somewhere 
 that indicated which service was not responding or what to do about it.   
 Can someone tell me which nova service I need to have running and 
 configured to issue os-certificates?
 
 Also, I really only want the EC2 credentials to be created and 
 downloaded, Im not so much interested in the X509 certificates at this 
 point.  It'd be nice if the user settings EC2 panel had more options, 
 such as just creating and/or listing the EC2 access ID and Key for a 
 particular user rather than assuming you want/need everything all at once.
 
 thanks,
 Wyllys Ingersoll
 EVault
 
 
 
 ___
 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] Rebooted, now can't ping my guest

[The King in Yellow]

Perhaps somebody could give me the contents of their quantum node's ovs-ofctl
dump-flows br-tun and I could figure out what mine *should* look like?


On Tue, Mar 12, 2013 at 4:24 PM, The King in Yellow yellowk...@gmail.comwrote:

 Okay, I have worked around my problem-- but I don't quite understand it,
 and hope somebody can help me.  It appears to be a problem with the Open
 vSwitch flows in br-tun on both compute and network.  Here are the flows as
 they are now, working.  I have manually added the priority=5 lines.
 Without those added manually on both sides, traffic from the guest's
 doesn't work properly.

 root@os-network:~# ovs-ofctl dump-flows br-tun
 NXST_FLOW reply (xid=0x4):
  cookie=0x0, duration=5331.934s, table=0, n_packets=, n_bytes=171598,
 priority=3,tun_id=0x1,dl_dst=01:00:00:00:00:00/01:00:00:00:00:00
 actions=mod_vlan_vid:1,output:1
  cookie=0x0, duration=3.119s, table=0, n_packets=6, n_bytes=496,
 priority=5,dl_vlan=1 actions=NORMAL
  cookie=0x0, duration=10.759s, table=0, n_packets=0, n_bytes=0,
 priority=4,in_port=1,dl_vlan=1 actions=set_tunnel:0x1,NORMAL
  cookie=0x0, duration=5331.725s, table=0, n_packets=0, n_bytes=0,
 priority=3,tun_id=0x1,dl_dst=fa:16:3e:36:2e:54 actions=mod_vlan_vid:1,NORMAL
  cookie=0x0, duration=5331.898s, table=0, n_packets=0, n_bytes=0,
 priority=3,tun_id=0x1,dl_dst=fa:16:3e:e2:38:da actions=mod_vlan_vid:1,NORMAL
  cookie=0x0, duration=5332.499s, table=0, n_packets=3502, n_bytes=286312,
 priority=1 actions=drop
 root@os-network:~#

 root@os-compute-01:~# ovs-ofctl dump-flows br-tun
 NXST_FLOW reply (xid=0x4):
  cookie=0x0, duration=22348.618s, table=0, n_packets=20165,
 n_bytes=991767,
 priority=3,tun_id=0x1,dl_dst=01:00:00:00:00:00/01:00:00:00:00:00
 actions=mod_vlan_vid:1,output:1
  cookie=0x0, duration=177.949s, table=0, n_packets=151, n_bytes=21830,
 priority=5,dl_vlan=1 actions=NORMAL
  cookie=0x0, duration=411.826s, table=0, n_packets=80, n_bytes=9566,
 priority=4,in_port=1,dl_vlan=1 actions=set_tunnel:0x1,NORMAL
  cookie=0x0, duration=22348.567s, table=0, n_packets=, n_bytes=252718,
 priority=3,tun_id=0x1,dl_dst=fa:16:3e:ee:9e:b2 actions=mod_vlan_vid:1,NORMAL
  cookie=0x0, duration=22348.128s, table=0, n_packets=1107, n_bytes=123234,
 priority=3,tun_id=0x1,dl_dst=fa:16:3e:8d:6d:13 actions=mod_vlan_vid:1,NORMAL
  cookie=0x0, duration=22348.353s, table=0, n_packets=1494, n_bytes=124036,
 priority=3,tun_id=0x1,dl_dst=fa:16:3e:95:94:9c actions=mod_vlan_vid:1,NORMAL
  cookie=0x0, duration=22347.912s, table=0, n_packets=3334, n_bytes=425776,
 priority=3,tun_id=0x1,dl_dst=fa:16:3e:7b:e3:ee actions=mod_vlan_vid:1,NORMAL
  cookie=0x0, duration=22349.47s, table=0, n_packets=879, n_bytes=75279,
 priority=1 actions=drop
 root@os-compute-01:~#

 Here is a sample packet that would have been blocked, sniffed in GRE.  The
 yellow background (if you can see the color) is the GRE header.  Inside the
 GRE payload, MAC (red) is1272.590f.cf56, and MAC (orange) is fa16.3e7b.e3ee
 are exchanging ping packets.

    00 50 56 81 44 e7 00 50 56 81 25 73 08 00 45 00  .PV.D..PV.%s..E.
 0010   00 82 64 93 40 00 40 2f ad a3 0a 0a 0a 02 0a 0a  ..d.@.@/
 0020   0a 01 20 00 65 58 00 00 00 00 12 72 59 0f cf 56  .. .eX.rY..V
 0030   fa 16 3e 95 94 9c 81 00 00 01 08 00 45 00 00 54  ...E..T
 0040   00 00 40 00 40 01 1d 00 0a 05 05 04 0a 2a 04 77  ..@.@*.w
 0050   08 00 00 9f 0e 17 00 08 17 87 3f 51 00 00 00 00  ..?Q
 0060   d3 96 00 00 00 00 00 00 10 11 12 13 14 15 16 17  
 0070   18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27   !#$%'
 0080   28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36 37  ()*+,-./01234567

    00 50 56 81 25 73 00 50 56 81 44 e7 08 00 45 00  .PV.%s.PV.D...E.
 0010   00 82 95 e3 40 00 40 2f 7c 53 0a 0a 0a 01 0a 0a  @.@/|S..
 0020   0a 02 20 00 65 58 00 00 00 00 fa 16 3e 95 94 9c  .. .eX.
 0030   12 72 59 0f cf 56 81 00 00 01 08 00 45 00 00 54  .rY..V..E..T
 0040   1e 24 00 00 3e 01 40 dc 0a 2a 04 77 0a 05 05 04  .$...@..*.w
 0050   00 00 08 9f 0e 17 00 08 17 87 3f 51 00 00 00 00  ..?Q
 0060   d3 96 00 00 00 00 00 00 10 11 12 13 14 15 16 17  
 0070   18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27   !#$%'
 0080   28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36 37  ()*+,-./01234567

 The source MAC does match the MAC for his gateway, 10.5.5.1:

 root@os-network:~# ovs-ofctl show br-int
 OFPT_FEATURES_REPLY (xid=0x1): ver:0x1, dpid:862cf391d546

 n_tables:255, n_buffers:256
 features: capabilities:0xc7, actions:0xfff
  1(qr-9f9041ce-65): addr:12:72:59:0f:cf:56
  config: 0
  state:  0
 :

 ...which is the understandable problem.  That MAC address is not
 specifically entered in the OVS bridge br-tun.  Any clue why?  This is
 across reboots, service restarts, etc...  I guess it is the
 /etc/openswitch/conf.db that is corrupted?

 What I don't understand at this point is why removing the priority 5 flow
 on the compute 

[Openstack] TC candidacy

[Vishvananda Ishaya]

Hello all,

I would like to run for a seat on The Technical Comittee. I have been working 
on Nova since it was a project as Nasa and I have been heavily involved in 
openstack since it was founded. I was elected to the precursor to TC (the 
Project Oversight Committee, later named the Project Policy Board) when it was 
first created.

I was also elected as the first PTL for Nova and have been filling that role 
for the last two years. I am the top contributor to Nova over the lifetime of 
the project, and the third most frequent contributor over the past 12 months. I 
helped to create Devstack, Keystone, and Cinder. In addition, I have 
contributed to Oslo and I am a member of the stable-maintenance team.

Despite passing on the mantle of Nova PTL, I am still deeply involved with 
OpenStack and I want to make sure that it continues to be a huge success. As 
OpenStack grows, one of the most important challenges we face is integration. 
It is vital that we have technical leaders that are focused cross-project and 
dedicated to making OpenStack as a whole successful.

I currently work as the Director of Open Source at Nebula, Inc. Previously I 
was a principal engineer on the private cloud team at Rackspace, and before 
that I was a senior developer on the Nebula project at NASA where Nova was 
created.

Thanks,
Vish
___
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] TC candidacy

[Carl Perry]

Greetings -

I would like to run for a TC seat as well. My platform is a focus on 
deployment and operations for OpenStack. I'm not going to mince words: 
deploying OpenStack is hard. Maintaining it is even harder. I don't 
think it needs to be this way. I spent two years designing and deploying 
a cloud based on OpenStack and it really seemed much harder to do than 
it should have been, especially when you factor in configuration 
management tools.


I would like to promote a more operational approach to the decisions 
made inside the OpenStack community. Some of it is easy, some of it is 
hard. I don't expect things to change overnight, but I do feel that a 
course correction is needed, that it's going to need to come from a 
whole project approach as well as code contribution, and that now is the 
time to make it.


As I said, I spent the last two years as an implementor of OpenStack 
with the DreamCompute project at DreamHost and have now moved on to a 
new position as a solutions architect at Midokura. These positions have 
given (and continue to give) me a customer perspective of what it takes 
to deploy, maintain, and upgrade OpenStack in production. While my 
company supports me and my desire to run for the TC, I'm running 
independent of my company in order to keep a vendor neutral approach.


Thanks for your time!
  -Carl

___
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] Grizzly Dashboard Quota Problem...

[Martinx - ジェームズ]

Hi!

 Finally I have my Grizzly G3 + RC1 working!

 But, when I tried to setup the Project quotas, an error appear on the
Dashboard and at Apache error.log.

 The error appear even when creating a Project, with default quota
settings...

 Dashboard message:

 Error: Unable to set project quotas.

 error.log:

 [Fri Mar 15 23:35:57 2013] [error] \x1b[31;1mRecoverable error: Bad
key(s) gigabytes,volumes in quota_set (HTTP 400) (Request-ID:
req-555844dc-3cdc-4a33-a7e8-c1836b8f)\x1b[0m

 Is this a know BUG?

 Can I do something about it?

Thanks!
Thiago
___
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] Testing Grizzly - What repository is the recommended?

[Martinx - ジェームズ]

Hi!

 Just for the record, Ubuntu PPA grizzly-trunk-testing repository is
working (with Ubuntu 12.04)!

Best,
Thiago


On 14 March 2013 19:35, Martinx - ジェームズ thiagocmarti...@gmail.com wrote:

 Guys,

  I'm about to test Grizzly but, I'm seeing two alternatives:

  1- Install Ubuntu 12.04 and add 
 http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/grizzly
 main  /etc/apt/sources.list.d/grizzly.list (
 http://docs.openstack.org/trunk/openstack-compute/install/apt/content/osfolubuntu-prerquisite.html
 )

  2- Install Ubuntu 12.04 and add 
 https://launchpad.net/~openstack-ubuntu-testing/+archive/grizzly-trunk-testing?field.series_filter=precise
 

  ... From what I'm seeing, the PPA grizzly-trunk-testing is more
 updated... Right?

  BTW, even if I'm going to try it with Raring, the PPA seems more updated
 for it too, if I'm not wrong...

  Is Quantum RC1 at this PPA ?

 Thanks!
 Thiago

___
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] Grizzly Dashboard Quota Problem...

[Martinx - ジェームズ]

Hi!

 I don't know if it is related to this issue but, when I Terminate an
Instance, nova-conductor.log shows:

2013-03-15 20:56:33.739 ERROR nova.quota
[req-558f180c-4092-4dad-9be0-04b105e6a51b 773fad6638fe4def95dd996db7af5161
7428cb7265d04ff398202b45f84d96bf] Failed to commit reservations
[u'73a2da17-7b5a-4913-87f2-33bf47b7ab02',
u'd2e4334a-679d-4664-bdc9-abff1247c89c',
u'b284d408-2788-4fad-b191-9fc6f857cdee']
2013-03-15 20:56:33.739 6218 TRACE nova.quota Traceback (most recent call
last):
2013-03-15 20:56:33.739 6218 TRACE nova.quota   File
/usr/lib/python2.7/dist-packages/nova/quota.py, line 982, in commit
2013-03-15 20:56:33.739 6218 TRACE nova.quota
self._driver.commit(context, reservations, project_id=project_id)
2013-03-15 20:56:33.739 6218 TRACE nova.quota   File
/usr/lib/python2.7/dist-packages/nova/quota.py, line 370, in commit
2013-03-15 20:56:33.739 6218 TRACE nova.quota
db.reservation_commit(context, reservations, project_id=project_id)
2013-03-15 20:56:33.739 6218 TRACE nova.quota   File
/usr/lib/python2.7/dist-packages/nova/db/api.py, line 972, in
reservation_commit
2013-03-15 20:56:33.739 6218 TRACE nova.quota project_id=project_id)
2013-03-15 20:56:33.739 6218 TRACE nova.quota   File
/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.py, line 112, in
wrapper
2013-03-15 20:56:33.739 6218 TRACE nova.quota return f(*args, **kwargs)
2013-03-15 20:56:33.739 6218 TRACE nova.quota   File
/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.py, line 2681, in
reservation_commit
2013-03-15 20:56:33.739 6218 TRACE nova.quota usage =
usages[reservation.resource]
2013-03-15 20:56:33.739 6218 TRACE nova.quota KeyError: u'instances'
2013-03-15 20:56:33.739 6218 TRACE nova.quota


Tks,
Thiago


On 15 March 2013 20:37, Martinx - ジェームズ thiagocmarti...@gmail.com wrote:

 Hi!

  Finally I have my Grizzly G3 + RC1 working!

  But, when I tried to setup the Project quotas, an error appear on the
 Dashboard and at Apache error.log.

  The error appear even when creating a Project, with default quota
 settings...

  Dashboard message:

  Error: Unable to set project quotas.

  error.log:

  [Fri Mar 15 23:35:57 2013] [error] \x1b[31;1mRecoverable error: Bad
 key(s) gigabytes,volumes in quota_set (HTTP 400) (Request-ID:
 req-555844dc-3cdc-4a33-a7e8-c1836b8f)\x1b[0m

  Is this a know BUG?

  Can I do something about it?

 Thanks!
 Thiago

___
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] Grizzly Dashboard Quota Problem...

[Kieran Spear]

Hi Thiago,

I haven't seen that before. Can you file a bug for it?

https://bugs.launchpad.net/horizon/+filebug

It may be something to do with a missing volume service, but that
service should be optional.

Cheers,
Kieran

On 16 March 2013 10:37, Martinx - ジェームズ thiagocmarti...@gmail.com wrote:
 Hi!

  Finally I have my Grizzly G3 + RC1 working!

  But, when I tried to setup the Project quotas, an error appear on the
 Dashboard and at Apache error.log.

  The error appear even when creating a Project, with default quota
 settings...

  Dashboard message:

  Error: Unable to set project quotas.

  error.log:

  [Fri Mar 15 23:35:57 2013] [error] \x1b[31;1mRecoverable error: Bad key(s)
 gigabytes,volumes in quota_set (HTTP 400) (Request-ID:
 req-555844dc-3cdc-4a33-a7e8-c1836b8f)\x1b[0m

  Is this a know BUG?

  Can I do something about it?

 Thanks!
 Thiago

 ___
 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

[Openstack] Unable to successfully create instances with horizon

[AJ Schroeder]

Hello list,

 

I've been following along with these instructions to get an openstack
environment setup:
http://docs.openstack.org/folsom/basic-install/content/basic-install_intro.h
tml - I am a total newbie with openstack.

 

I am using virtualbox with Ubuntu 12.04 LTS guests and I have all three
nodes setup and operational. After some troubleshooting I was finally able
to create volumes in cinder, but now I can't successfully create any
instances. I use horizon and navigate through the process of setting up the
instance, and when I click launch the instance shows up in the list, but the
status is always error. I'm not sure what to post that would be relevant,
but here are some log entries and output:

 

# -- nova-scheduler.log --#

2013-03-15 09:40:13 1475 DEBUG nova.openstack.common.rpc.amqp [-] received
{u'_context_roles': [u'Member', u'admin'], u'_context_request_id':
u'req-cccd3bed-8a37-4166-be5d-02f74221a2b6', u'_context_quota_class': None,
u'_context_project_name': u'demo', u'_context_service_catalog':
[{u'endpoints': [{u'adminURL':
u'http://192.168.1.1:8774/v2/ef28e5b6b9d143c4baa15b271440586a', u'region':
u'RegionOne', u'internalURL':
u'http://192.168.1.1:8774/v2/ef28e5b6b9d143c4baa15b271440586a', u'id':
u'110f0468149c42c88256f02a01aa54d0', u'publicURL':
u'http://192.168.1.1:8774/v2/ef28e5b6b9d143c4baa15b271440586a'}],
u'endpoints_links': [], u'type': u'compute', u'name': u'nova'},
{u'endpoints': [{u'adminURL': u'http://192.168.1.1:9696/', u'region':
u'RegionOne', u'internalURL': u'http://192.168.1.1:9696/', u'id':
u'45faf59eb6c747daaae2ef16a68e7eef', u'publicURL':
u'http://192.168.1.1:9696/'}], u'endpoints_links': [], u'type': u'network',
u'name': u'quantum'}, {u'endpoints': [{u'adminURL':
u'http://192.168.1.1:9292/v2', u'region': u'RegionOne', u'internalURL':
u'http://192.168.1.1:9292/v2', u'id': u'16938ca8049446688ce57f7f98a71c32',
u'publicURL': u'http://192.168.1.1:9292/v2'}], u'endpoints_links': [],
u'type': u'image', u'name': u'glance'}, {u'endpoints': [{u'adminURL':
u'http://192.168.1.1:8776/v1/ef28e5b6b9d143c4baa15b271440586a', u'region':
u'RegionOne', u'internalURL':
u'http://192.168.1.1:8776/v1/ef28e5b6b9d143c4baa15b271440586a',
u'serviceName': u'cinder', u'id': u'f7a1448a776c4aa2b6a5843f38c33022',
u'publicURL':
u'http://192.168.1.1:8776/v1/ef28e5b6b9d143c4baa15b271440586a'}],
u'endpoints_links': [], u'type': u'volume', u'name': u'cinder'},
{u'endpoints': [{u'adminURL': u'http://192.168.1.1:8773/services/Admin',
u'region': u'RegionOne', u'internalURL':
u'http://192.168.1.1:8773/services/Cloud', u'id':
u'0bb938dbb76d44ae94fa24998c3c8a94', u'publicURL':
u'http://192.168.1.1:8773/services/Cloud'}], u'endpoints_links': [],
u'type': u'ec2', u'name': u'ec2'}, {u'endpoints': [{u'adminURL':
u'http://192.168.1.1:8080/v1', u'region': u'RegionOne', u'internalURL':
u'http://192.168.1.1:8080/v1/AUTH_ef28e5b6b9d143c4baa15b271440586a', u'id':
u'169ad8d8a930442ba189b626e1f574f7', u'publicURL':
u'http://192.168.1.1:8080/v1/AUTH_ef28e5b6b9d143c4baa15b271440586a'}],
u'endpoints_links': [], u'type': u'object-store', u'name': u'swift'},
{u'endpoints': [{u'adminURL': u'http://192.168.1.1:35357/v2.0', u'region':
u'RegionOne', u'internalURL': u'http://192.168.1.1:5000/v2.0', u'id':
u'457ce03d6aa5479e819cae931760ab62', u'publicURL':
u'http://192.168.1.1:5000/v2.0'}], u'endpoints_links': [], u'type':
u'identity', u'name': u'keystone'}], u'_context_user_name': u'demo',
u'_context_auth_token': 'SANITIZED', u'args': {u'request_spec':
{u'block_device_mapping': [{u'volume_size': u'', u'device_name': u'vda',
u'delete_on_termination': False, u'volume_id':
u'b26596e4-f142-4692-9507-5bcdd44ea0ca'}], u'image': {u'status': u'active',
u'name': u'Ubuntu', u'deleted': False, u'container_format': u'bare',
u'created_at': u'2013-03-13T02:48:56.00', u'disk_format': u'qcow2',
u'updated_at': u'2013-03-13T02:48:57.00', u'properties': {},
u'min_disk': 0, u'min_ram': 0, u'checksum': None, u'owner': None,
u'is_public': True, u'deleted_at': None, u'id':
u'dd89f63f-4b2a-44c5-96f2-084e198dd9aa', u'size': 251068416},
u'instance_type': {u'memory_mb': 512, u'root_gb': 0, u'deleted_at': None,
u'name': u'm1.tiny', u'deleted': False, u'created_at': None,
u'ephemeral_gb': 0, u'updated_at': None, u'disabled': False, u'vcpus': 1,
u'extra_specs': {}, u'swap': 0, u'rxtx_factor': 1.0, u'is_public': True,
u'flavorid': u'1', u'vcpu_weight': None, u'id': 2}, u'instance_properties':
{u'vm_state': u'building', u'availability_zone': None, u'ramdisk_id': u'',
u'instance_type_id': 2, u'user_data': None, u'vm_mode': None,
u'reservation_id': u'r-q3z7lbct', u'user_id':
u'f02218d004cc4f978be0720a55cbb2e7', u'display_description': u'demo',
u'key_data': u'ssh-rsa

B3NzaC1yc2EDAQABgQDfL7KX8Sc3J2qpM4Rqc4vvGxj0bo/eGTtNOKQX4IpPcaJB
dvFjy8Zhayr+9wT49ygYelvqFQAdeCwAvsRmmKFffGeXf/BmcfoIiIVjpU4fFgnflenfGPu5seK5
v+SKbHnzURZd8MDie51OjvieAjEwd3KxGKJRdG/rSDd8DvpfZQ== Generated by Nova\n',
u'power_state': 0, u'progress': 0, u'project_id':

[Openstack] Allocating dynamic IP to the VMs

[Chathura M. Sarathchandra Magurawalage]

Hello,

I want to know how I can allocate a dynamic IP to the VM from the same
network as the openstack hosts (controller/network-node/compute node)
network/management network . For example, in virtual box you can give your
VM an IP from the host's network using a Bridge adapter. How can I do this
in openstack?

From what I understand floating IP's are used when you have a public IP
 (which is static) to be allocated to VM's.

My openstack installation architecture:
http://docs.openstack.org/folsom/basic-install/content/basic-install_architecture.html

Quantum use case:
http://docs.openstack.org/trunk/openstack-network/admin/content/use_cases_single_router.html
___
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] ssh from VM to VM

[Chathura M. Sarathchandra Magurawalage]

Hello,

I can't ssh from Ubuntu cloud VM to other VM. I get following

ubuntu@master:~$ ssh cirros@10.5.5.6 -v
OpenSSH_5.9p1 Debian-5ubuntu1, OpenSSL 1.0.1 14 Mar 2012
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to 10.5.5.6 [10.5.5.6] port 22.
debug1: Connection established.
debug1: identity file /home/ubuntu/.ssh/id_rsa type -1
debug1: identity file /home/ubuntu/.ssh/id_rsa-cert type -1
debug1: identity file /home/ubuntu/.ssh/id_dsa type -1
debug1: identity file /home/ubuntu/.ssh/id_dsa-cert type -1
debug1: identity file /home/ubuntu/.ssh/id_ecdsa type -1
debug1: identity file /home/ubuntu/.ssh/id_ecdsa-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.9p1
Debian-5ubuntu1
debug1: match: OpenSSH_5.9p1 Debian-5ubuntu1 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server-client aes128-ctr hmac-md5 none
debug1: kex: client-server aes128-ctr hmac-md5 none
debug1: sending SSH2_MSG_KEX_ECDH_INIT
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ECDSA
7b:8f:6a:ee:ba:e5:0a:c5:04:01:ca:bd:e5:38:69:55
debug1: Host '10.5.5.6' is known and matches the ECDSA host key.
debug1: Found key in /home/ubuntu/.ssh/known_hosts:4
debug1: ssh_ecdsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Trying private key: /home/ubuntu/.ssh/id_rsa
debug1: Trying private key: /home/ubuntu/.ssh/id_dsa
debug1: Trying private key: /home/ubuntu/.ssh/id_ecdsa
debug1: No more authentication methods to try.
Permission denied (publickey).

But I can ssh from to my Cirros VMs. Also I can ssh from Ubuntu VM to
Cirros VM.

Any Idea?

Thanks.
___
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] Testing Grizzly - What repository is the recommended?

[Brad Knowles]

On Mar 14, 2013, at 5:35 PM, Martinx - ジェームズ thiagocmarti...@gmail.com wrote:

  I'm about to test Grizzly but, I'm seeing two alternatives:
 
  1- Install Ubuntu 12.04 and add 
 http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/grizzly 
 main  /etc/apt/sources.list.d/grizzly.list 
 (http://docs.openstack.org/trunk/openstack-compute/install/apt/content/osfolubuntu-prerquisite.html)

That's the route that I started down, see 
https://review.openstack.org/#/c/23231/.

I have yet to get a successful deployment with grizzly using that 
documentation, but I do have a whole bunch more updates that have yet to be fed 
back in.  I got side-tracked from doing a normal Grizzly install to trying to 
do one so that we could get the latest vmwareapi stuff, and didn't get to 
completion in that area, either.

I'll see if I can get more of my documentation changes fed back into the 
project over the next week.

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

[Openstack-ubuntu-testing-notifications] Build failed in Jenkins: cloud-archive_folsom_version-drift #10744

[openstack-testing-bot]

See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10744/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson4608827232399682076.sh
+ OS_RELEASE=folsom
+ /var/lib/jenkins/tools/ca-versions/gather-versions.py folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ /var/lib/jenkins/tools/ca-versions/ca-versions.py -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

glance:
Ubuntu: 2012.2.1-0ubuntu1.2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #10745

[openstack-testing-bot]

See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10745/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson1082781972039052860.sh
+ OS_RELEASE=folsom
+ /var/lib/jenkins/tools/ca-versions/gather-versions.py folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ /var/lib/jenkins/tools/ca-versions/ca-versions.py -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

glance:
Ubuntu: 2012.2.1-0ubuntu1.2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #10746

[openstack-testing-bot]

See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10746/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson4019720240313741875.sh
+ OS_RELEASE=folsom
+ /var/lib/jenkins/tools/ca-versions/gather-versions.py folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ /var/lib/jenkins/tools/ca-versions/ca-versions.py -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

glance:
Ubuntu: 2012.2.1-0ubuntu1.2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #10747

[openstack-testing-bot]

See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10747/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson6035295873391508515.sh
+ OS_RELEASE=folsom
+ /var/lib/jenkins/tools/ca-versions/gather-versions.py folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ /var/lib/jenkins/tools/ca-versions/ca-versions.py -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

glance:
Ubuntu: 2012.2.1-0ubuntu1.2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #10748

[openstack-testing-bot]

See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10748/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson7035313701834319433.sh
+ OS_RELEASE=folsom
+ /var/lib/jenkins/tools/ca-versions/gather-versions.py folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ /var/lib/jenkins/tools/ca-versions/ca-versions.py -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

glance:
Ubuntu: 2012.2.1-0ubuntu1.2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #10752

[openstack-testing-bot]

See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10752/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson5930659491456241156.sh
+ OS_RELEASE=folsom
+ /var/lib/jenkins/tools/ca-versions/gather-versions.py folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ /var/lib/jenkins/tools/ca-versions/ca-versions.py -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

glance:
Ubuntu: 2012.2.1-0ubuntu1.2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #10753

[openstack-testing-bot]

See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10753/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson3893602428236954354.sh
+ OS_RELEASE=folsom
+ /var/lib/jenkins/tools/ca-versions/gather-versions.py folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ /var/lib/jenkins/tools/ca-versions/ca-versions.py -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

glance:
Ubuntu: 2012.2.1-0ubuntu1.2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #10754

[openstack-testing-bot]

See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10754/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson1263047260215971610.sh
+ OS_RELEASE=folsom
+ /var/lib/jenkins/tools/ca-versions/gather-versions.py folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ /var/lib/jenkins/tools/ca-versions/ca-versions.py -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

glance:
Ubuntu: 2012.2.1-0ubuntu1.2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 failed in Jenkins: cloud-archive_folsom_version-drift #10756

[openstack-testing-bot]

See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10756/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson3750960399223013421.sh
+ OS_RELEASE=folsom
+ /var/lib/jenkins/tools/ca-versions/gather-versions.py folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ /var/lib/jenkins/tools/ca-versions/ca-versions.py -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

glance:
Ubuntu: 2012.2.1-0ubuntu1.2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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 Fixed: raring_grizzly_swift_trunk #157

[openstack-testing-bot]

Title: raring_grizzly_swift_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_swift_trunk/157/Project:raring_grizzly_swift_trunkDate of build:Fri, 15 Mar 2013 05:09:34 -0400Build duration:4 min 35 secBuild cause:Started by user James PageBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesNo ChangesConsole Output[...truncated 4959 lines...]Good signature on /tmp/tmpdtnLiD/swift_1.7.7+git201303150509~raring-0ubuntu1_source.changes.Checking signature on .dscGood signature on /tmp/tmpdtnLiD/swift_1.7.7+git201303150509~raring-0ubuntu1.dsc.Uploading to ppa (via ftp to ppa.launchpad.net):  Uploading swift_1.7.7+git201303150509~raring-0ubuntu1.dsc: done.  Uploading swift_1.7.7+git201303150509~raring.orig.tar.gz: done.  Uploading swift_1.7.7+git201303150509~raring-0ubuntu1.debian.tar.gz: done.  Uploading swift_1.7.7+git201303150509~raring-0ubuntu1_source.changes: done.Successfully uploaded packages.INFO:root:Installing build artifacts into /var/lib/jenkins/www/aptDEBUG:root:['reprepro', '--waitforlock', '10', '-Vb', '/var/lib/jenkins/www/apt', 'include', 'raring-grizzly', 'swift_1.7.7+git201303150509~raring-0ubuntu1_amd64.changes']Exporting indices...Successfully created '/var/lib/jenkins/www/apt/dists/raring-grizzly/Release.gpg.new'Successfully created '/var/lib/jenkins/www/apt/dists/raring-grizzly/InRelease.new'Deleting files no longer referenced...deleting and forgetting pool/main/s/swift/python-swift_1.7.7+git201303131902~raring-0ubuntu1_all.debdeleting and forgetting pool/main/s/swift/swift-account_1.7.7+git201303131902~raring-0ubuntu1_all.debdeleting and forgetting pool/main/s/swift/swift-container_1.7.7+git201303131902~raring-0ubuntu1_all.debdeleting and forgetting pool/main/s/swift/swift-doc_1.7.7+git201303131902~raring-0ubuntu1_all.debdeleting and forgetting pool/main/s/swift/swift-object_1.7.7+git201303131902~raring-0ubuntu1_all.debdeleting and forgetting pool/main/s/swift/swift-proxy_1.7.7+git201303131902~raring-0ubuntu1_all.debdeleting and forgetting pool/main/s/swift/swift_1.7.7+git201303131902~raring-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/swift/raring-grizzly']Pushed up to revision 138.INFO:root:Storing current commit for next build: f6e29b81d03508deabd43a48e5e417d8ba9a7f1aINFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/swift/grizzly /tmp/tmpdtnLiD/swiftmk-build-deps -i -r -t apt-get -y /tmp/tmpdtnLiD/swift/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 35acd5912ff9478b18c0466fac1184fa3cd6600a..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/swift/raring-grizzly --forcedch -b -D raring --newversion 1.7.7+git201303150509~raring-0ubuntu1 Automated Ubuntu testing build:dch -a [f6e29b8] Remove check for valid Origin for the "actual request".dch -a [ebcd60f] Add a region tier to Swift's ring.dch -a [b373278] Add missing CONTRIBUTING.md to source tarballdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC swift_1.7.7+git201303150509~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A swift_1.7.7+git201303150509~raring-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing swift_1.7.7+git201303150509~raring-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include raring-grizzly swift_1.7.7+git201303150509~raring-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/swift/raring-grizzlyEmail was triggered for: FixedTrigger Success was overridden by another trigger and will not send an email.Sending email for trigger: Fixed-- 
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 Fixed: raring_grizzly_cinder_trunk #238

[openstack-testing-bot]

Title: raring_grizzly_cinder_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_cinder_trunk/238/Project:raring_grizzly_cinder_trunkDate of build:Fri, 15 Mar 2013 05:11:17 -0400Build duration:4 min 59 secBuild cause:Started by user James PageBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesNo ChangesConsole Output[...truncated 7170 lines...]gpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) "gpg: Signature made Fri Mar 15 05:14:01 2013 EDT using RSA key ID 9935ACDCgpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) "Checking signature on .changesGood signature on /tmp/tmptPgh_w/cinder_2013.1+git201303150511~raring-0ubuntu1_source.changes.Checking signature on .dscGood signature on /tmp/tmptPgh_w/cinder_2013.1+git201303150511~raring-0ubuntu1.dsc.Uploading to ppa (via ftp to ppa.launchpad.net):  Uploading cinder_2013.1+git201303150511~raring-0ubuntu1.dsc: done.  Uploading cinder_2013.1+git201303150511~raring.orig.tar.gz: done.  Uploading cinder_2013.1+git201303150511~raring-0ubuntu1.debian.tar.gz: done.  Uploading cinder_2013.1+git201303150511~raring-0ubuntu1_source.changes: done.Successfully uploaded packages.INFO:root:Installing build artifacts into /var/lib/jenkins/www/aptDEBUG:root:['reprepro', '--waitforlock', '10', '-Vb', '/var/lib/jenkins/www/apt', 'include', 'raring-grizzly', 'cinder_2013.1+git201303150511~raring-0ubuntu1_amd64.changes']Exporting indices...Successfully created '/var/lib/jenkins/www/apt/dists/raring-grizzly/Release.gpg.new'Successfully created '/var/lib/jenkins/www/apt/dists/raring-grizzly/InRelease.new'Deleting files no longer referenced...deleting and forgetting pool/main/c/cinder/cinder-api_2013.1+git201303150001~raring-0ubuntu1_all.debdeleting and forgetting pool/main/c/cinder/cinder-backup_2013.1+git201303150001~raring-0ubuntu1_all.debdeleting and forgetting pool/main/c/cinder/cinder-common_2013.1+git201303150001~raring-0ubuntu1_all.debdeleting and forgetting pool/main/c/cinder/cinder-scheduler_2013.1+git201303150001~raring-0ubuntu1_all.debdeleting and forgetting pool/main/c/cinder/cinder-volume_2013.1+git201303150001~raring-0ubuntu1_all.debdeleting and forgetting pool/main/c/cinder/python-cinder_2013.1+git201303150001~raring-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/cinder/raring-grizzly']Pushed up to revision 88.INFO:root:Storing current commit for next build: 4b52b1481e3cb6c358252826785228638b0f717dINFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/cinder/grizzly /tmp/tmptPgh_w/cindermk-build-deps -i -r -t apt-get -y /tmp/tmptPgh_w/cinder/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/cinder/raring-grizzly --forcedch -b -D raring --newversion 1:2013.1+git201303150511~raring-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC cinder_2013.1+git201303150511~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A cinder_2013.1+git201303150511~raring-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing cinder_2013.1+git201303150511~raring-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include raring-grizzly cinder_2013.1+git201303150511~raring-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/cinder/raring-grizzlyEmail was triggered for: FixedTrigger Success was overridden by another trigger and will not send an email.Sending email for trigger: Fixed-- 
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 failed in Jenkins: cloud-archive_folsom_version-drift #10757

[openstack-testing-bot]

See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10757/

--
Started by timer
Building remotely on pkg-builder in workspace 
http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/ws/
[cloud-archive_folsom_version-drift] $ /bin/bash -xe 
/tmp/hudson1508977013671033564.sh
+ OS_RELEASE=folsom
+ /var/lib/jenkins/tools/ca-versions/gather-versions.py folsom
INFO:root:Querying package list and versions from staging PPA.
INFO:root:Initializing connection to LP...
INFO:root:Querying Ubuntu versions for all packages.
INFO:root:Scraping Packages list for CA pocket: proposed
INFO:root:Scraping Packages list for CA pocket: updates
+ /var/lib/jenkins/tools/ca-versions/ca-versions.py -c -r folsom
---
The following Cloud Archive packages for folsom
have been superseded newer versions in Ubuntu!

glance:
Ubuntu: 2012.2.1-0ubuntu1.2
Cloud Archive staging: 2012.2.1-0ubuntu1.1~cloud0

--
Build step 'Execute shell' marked build as 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] Jenkins build is back to normal : cloud-archive_folsom_version-drift #10758

[openstack-testing-bot]

See http://10.189.74.7:8080/job/cloud-archive_folsom_version-drift/10758/


-- 
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 Failure: precise_grizzly_glance_trunk #174

[openstack-testing-bot]

Title: precise_grizzly_glance_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_glance_trunk/174/Project:precise_grizzly_glance_trunkDate of build:Fri, 15 Mar 2013 07:37:36 -0400Build duration:57 minBuild cause:Started by user James PageBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 3 out of the last 5 builds failed.40ChangesNo ChangesConsole Output[...truncated 6422 lines...]Searching for duplicated docs in dependency glance-common...  symlinking changelog.Debian.gz in glance-api to file in python-glancepkgstripfiles: PNG optimization for package glance-api took 0 sdpkg-deb: building package `glance-api' in `../glance-api_2013.1+git201303150737~precise-0ubuntu1_all.deb'.pkgstripfiles: processing control file: debian/glance-registry/DEBIAN/control, package glance-registry, directory debian/glance-registrySearching for duplicated docs in dependency glance-common...  symlinking changelog.Debian.gz in glance-registry to file in python-glancepkgstripfiles: PNG optimization for package glance-registry took 0 sdpkg-deb: building package `glance-registry' in `../glance-registry_2013.1+git201303150737~precise-0ubuntu1_all.deb'. dpkg-genchanges -b >../glance_2013.1+git201303150737~precise-0ubuntu1_amd64.changesdpkg-genchanges: binary-only upload - not including any source code dpkg-source --after-build glance-2013.1+git201303150737~precisedpkg-buildpackage: binary only upload (no source included)ERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'glance_2013.1+git201303150737~precise-0ubuntu1.dsc']' returned non-zero exit status -9ERROR:root:Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'glance_2013.1+git201303150737~precise-0ubuntu1.dsc']' returned non-zero exit status -9INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/glance/grizzly /tmp/tmp8UbGJM/glancemk-build-deps -i -r -t apt-get -y /tmp/tmp8UbGJM/glance/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log e75764eee34915f8bc5b664ac18e47a556c9d3dd..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/glance/precise-grizzly --forcedch -b -D precise --newversion 1:2013.1+git201303150737~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [157cce7] Segmented images not deleted cleanly from swift.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC glance_2013.1+git201303150737~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A glance_2013.1+git201303150737~precise-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'glance_2013.1+git201303150737~precise-0ubuntu1.dsc']' returned non-zero exit status -9Error 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 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'glance_2013.1+git201303150737~precise-0ubuntu1.dsc']' returned non-zero exit status -9Process leaked file descriptors. See http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for more informationBuild 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 Failure: precise_essex_quantum_stable #12

[openstack-testing-bot]

Title: precise_essex_quantum_stable
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_essex_quantum_stable/12/Project:precise_essex_quantum_stableDate of build:Fri, 15 Mar 2013 09:01:30 -0400Build duration:24 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole OutputStarted by an SCM changeBuilding remotely on pkg-builder in workspace /var/lib/jenkins/slave/workspace/precise_essex_quantum_stableCheckout:precise_essex_quantum_stable / /var/lib/jenkins/slave/workspace/precise_essex_quantum_stable - hudson.remoting.Channel@2c824005:pkg-builderUsing strategy: DefaultCheckout:quantum / /var/lib/jenkins/slave/workspace/precise_essex_quantum_stable/quantum - hudson.remoting.LocalChannel@18da3e94Wiping out workspace first.Cloning the remote Git repositoryCloning repository originFetching upstream changes from https://github.com/openstack/quantum.gitCommencing build of Revision 753730aaf12585d81038ad3e3988c1294d9ad25b (remotes/origin/stable/essex)Checking out Revision 753730aaf12585d81038ad3e3988c1294d9ad25b (remotes/origin/stable/essex)No change to record in branch remotes/origin/stable/essexNo emails were triggered.[precise_essex_quantum_stable] $ /bin/sh -xe /tmp/hudson6372285767159873474.sh+ /var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package -jINFO:root:Creating tarball using sdistERROR:root:Error occurred during package creation/build: argument of type 'float' is not iterableERROR:root:argument of type 'float' is not iterableINFO:root:Complete command log:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise eTypeError: argument of type 'float' is not iterableError 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 141, in raise eTypeError: argument of type 'float' is not iterableBuild 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 Failure: precise_essex_swift_stable #11

[openstack-testing-bot]

Title: precise_essex_swift_stable
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_essex_swift_stable/11/Project:precise_essex_swift_stableDate of build:Fri, 15 Mar 2013 09:01:30 -0400Build duration:2 min 28 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 1211 lines...]patching file test/probe/test_object_failures.pypatching file test/probe/test_object_handoff.pypatching file test/probe/test_running_with_each_type_down.pypatching file test/unit/account/test_server.pypatching file test/unit/common/middleware/test_swift3.pypatching file test/unit/common/test_daemon.pypatching file test/unit/container/test_server.pypatching file test/unit/obj/test_auditor.pypatching file test/unit/obj/test_server.pypatching file test/unit/proxy/test_server.pyPatch fix-ubuntu-unittests.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-9d990ea7-1780-4a53-8531-dec9d0856827', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-9d990ea7-1780-4a53-8531-dec9d0856827', '-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/swift/precise-essex-proposed /tmp/tmpLb6W2r/swiftmk-build-deps -i -r -t apt-get -y /tmp/tmpLb6W2r/swift/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log -n5 --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/swift/precise-essex-stable --forcedch -b -D precise --newversion 1.4.8+git201303150902~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [4a6fead] Final 1.4.8 versioningdch -a [d41ad0a] changelog for 1.4.8dch -a [1ecf5eb] updated copyright date for all filesdch -a [8945423] updated authors file and added .mailmapdch -a [cb84214] Add sphinx to test-requires.debcommitbzr 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 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-9d990ea7-1780-4a53-8531-dec9d0856827', '-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 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-9d990ea7-1780-4a53-8531-dec9d0856827', '-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 Fixed: precise_essex_horizon_stable #36

[openstack-testing-bot]

Title: precise_essex_horizon_stable
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_essex_horizon_stable/36/Project:precise_essex_horizon_stableDate of build:Fri, 15 Mar 2013 09:02:35 -0400Build duration:5 min 22 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 2 builds failed.50ChangesNo ChangesConsole Output[...truncated 5271 lines...]Finished at 20130315-0907Build needed 00:02:07, 21328k disc spaceINFO:root:Uploading package to ppa:openstack-ubuntu-testing/essex-stable-testinggpg: Signature made Fri Mar 15 09:05:40 2013 EDT using RSA key ID 9935ACDCgpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) <ja...@shingle-house.org.uk>"gpg: Signature made Fri Mar 15 09:05:40 2013 EDT using RSA key ID 9935ACDCgpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) <ja...@shingle-house.org.uk>"Checking signature on .changesGood signature on /tmp/tmpTUpZTe/horizon_2012.1.4+git201303150902~precise-0ubuntu1_source.changes.Checking signature on .dscGood signature on /tmp/tmpTUpZTe/horizon_2012.1.4+git201303150902~precise-0ubuntu1.dsc.Uploading to ppa (via ftp to ppa.launchpad.net):  Uploading horizon_2012.1.4+git201303150902~precise-0ubuntu1.dsc: done.  Uploading horizon_2012.1.4+git201303150902~precise.orig.tar.gz: done.  Uploading horizon_2012.1.4+git201303150902~precise-0ubuntu1.debian.tar.gz: done.  Uploading horizon_2012.1.4+git201303150902~precise-0ubuntu1_source.changes: done.Successfully uploaded packages.INFO:root:Installing build artifacts into /var/lib/jenkins/www/aptExporting indices...Successfully created '/var/lib/jenkins/www/apt/dists/precise-essex/Release.gpg.new'Successfully created '/var/lib/jenkins/www/apt/dists/precise-essex/InRelease.new'Deleting files no longer referenced...deleting and forgetting pool/main/h/horizon/openstack-dashboard-ubuntu-theme_2012.1.4+git201303110401~precise-0ubuntu1_all.debdeleting and forgetting pool/main/h/horizon/openstack-dashboard_2012.1.4+git201303110401~precise-0ubuntu1_all.debdeleting and forgetting pool/main/h/horizon/python-django-horizon_2012.1.4+git201303110401~precise-0ubuntu1_all.debdeleting and forgetting pool/main/h/horizon/python-django-openstack_2012.1.4+git201303110401~precise-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchPushed up to revision 108.INFO:root:Storing current commit for next build: 5ce394226a5333285d89cc8163bb4039a0c0e773INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/horizon/precise-essex-proposed /tmp/tmpTUpZTe/horizonmk-build-deps -i -r -t apt-get -y /tmp/tmpTUpZTe/horizon/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/horizon/precise-essex-stable --forcedch -b -D precise --newversion 2012.1.4+git201303150902~precise-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC horizon_2012.1.4+git201303150902~precise-0ubuntu1_source.changessbuild -d precise-essex -n -A horizon_2012.1.4+git201303150902~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/essex-stable-testing horizon_2012.1.4+git201303150902~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-essex horizon_2012.1.4+git201303150902~precise-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/horizon/precise-essex-stableEmail was triggered for: FixedTrigger Success was overridden by another trigger and will not send an email.Sending email for trigger: Fixed-- 
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 Fixed: precise_folsom_cinder_stable #150

[openstack-testing-bot]

Title: precise_folsom_cinder_stable
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_cinder_stable/150/Project:precise_folsom_cinder_stableDate of build:Fri, 15 Mar 2013 09:03:58 -0400Build duration:5 min 9 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 2 builds failed.50ChangesNo ChangesConsole Output[...truncated 5385 lines...]Build needed 00:02:41, 35592k disc spaceINFO:root:Uploading package to ppa:openstack-ubuntu-testing/folsom-stable-testinggpg: Signature made Fri Mar 15 09:06:14 2013 EDT using RSA key ID 9935ACDCgpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) "gpg: Signature made Fri Mar 15 09:06:13 2013 EDT using RSA key ID 9935ACDCgpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) "Checking signature on .changesGood signature on /tmp/tmpFczalt/cinder_2012.2.4+git201303150904~precise-0ubuntu1_source.changes.Checking signature on .dscGood signature on /tmp/tmpFczalt/cinder_2012.2.4+git201303150904~precise-0ubuntu1.dsc.Uploading to ppa (via ftp to ppa.launchpad.net):  Uploading cinder_2012.2.4+git201303150904~precise-0ubuntu1.dsc: done.  Uploading cinder_2012.2.4+git201303150904~precise.orig.tar.gz: done.  Uploading cinder_2012.2.4+git201303150904~precise-0ubuntu1.debian.tar.gz: done.  Uploading cinder_2012.2.4+git201303150904~precise-0ubuntu1_source.changes: done.Successfully uploaded packages.INFO:root:Installing build artifacts into /var/lib/jenkins/www/aptExporting indices...Successfully created '/var/lib/jenkins/www/apt/dists/precise-folsom/Release.gpg.new'Successfully created '/var/lib/jenkins/www/apt/dists/precise-folsom/InRelease.new'Deleting files no longer referenced...deleting and forgetting pool/main/c/cinder/cinder-api_2012.2.4+git201303112301~precise-0ubuntu1_all.debdeleting and forgetting pool/main/c/cinder/cinder-common_2012.2.4+git201303112301~precise-0ubuntu1_all.debdeleting and forgetting pool/main/c/cinder/cinder-scheduler_2012.2.4+git201303112301~precise-0ubuntu1_all.debdeleting and forgetting pool/main/c/cinder/cinder-volume_2012.2.4+git201303112301~precise-0ubuntu1_all.debdeleting and forgetting pool/main/c/cinder/python-cinder_2012.2.4+git201303112301~precise-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchPushed up to revision 67.INFO:root:Storing current commit for next build: cbad3e33b5a76e2ae427b943bb4453934d11ed30INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/cinder/folsom /tmp/tmpFczalt/cindermk-build-deps -i -r -t apt-get -y /tmp/tmpFczalt/cinder/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/cinder/precise-folsom --forcedch -b -D precise --newversion 2012.2.4+git201303150904~precise-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC cinder_2012.2.4+git201303150904~precise-0ubuntu1_source.changessbuild -d precise-folsom -n -A cinder_2012.2.4+git201303150904~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/folsom-stable-testing cinder_2012.2.4+git201303150904~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-folsom cinder_2012.2.4+git201303150904~precise-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/cinder/precise-folsomEmail was triggered for: FixedTrigger Success was overridden by another trigger and will not send an email.Sending email for trigger: Fixed-- 
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_folsom_glance_stable #209

[openstack-testing-bot]

Title: precise_folsom_glance_stable
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_glance_stable/209/Project:precise_folsom_glance_stableDate of build:Fri, 15 Mar 2013 09:07:42 -0400Build duration:2 min 37 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 3 out of the last 5 builds failed.40ChangesDo not return location in headersby stuart.mclareneditglance/api/middleware/cache.pyConsole Output[...truncated 2286 lines...]patching file glance/tests/functional/test_bin_glance.pyHunk #2 FAILED at 309.Hunk #3 succeeded at 327 (offset 8 lines).1 out of 3 hunks FAILED -- rejects in file glance/tests/functional/test_bin_glance.pypatching file glance/tests/functional/v1/test_multiprocessing.pypatching file glance/tests/functional/v2/test_images.pypatching file glance/tests/unit/test_clients.pypatching file glance/tests/unit/test_swift_store.pypatching file glance/tests/unit/v2/test_image_data_resource.pyPatch disable-swift-tests.patch does not apply (enforce with -f)ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-2d822b13-982e-4ee0-bca5-61fdd4a67a49', '-u', 'jenkins', '--', 'bzr', 'builddeb', '-S', '--', '-sa', '-us', '-uc']' returned non-zero exit status 3ERROR:root:Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-2d822b13-982e-4ee0-bca5-61fdd4a67a49', '-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/glance/folsom /tmp/tmp4jSsjX/glancemk-build-deps -i -r -t apt-get -y /tmp/tmp4jSsjX/glance/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log afe61664ac5f933622e349da1c0a92d134a81230..HEAD --no-merges --pretty=format:[%h] %sbzr merge lp:~openstack-ubuntu-testing/glance/precise-folsom --forcedch -b -D precise --newversion 2012.2.4+git201303150907~precise-0ubuntu1 Automated Ubuntu testing build:dch -a [dd849a9] Do not return location in headersdch -a [04f88c8] Fixes deletion of invalid image memberdch -a [5597697] Wait in TestBinGlance.test_update_copying_from until image is activedch -a [12d28c3] Swallow UserWarning from glance-cache-managedch -a [5183360] Clean dangling image fragments in filesystem storedch -a [03dc862] Avoid dangling partial image on size/checksum mismatchdebcommitbzr 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 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-2d822b13-982e-4ee0-bca5-61fdd4a67a49', '-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 141, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-2d822b13-982e-4ee0-bca5-61fdd4a67a49', '-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: precise_folsom_deploy #404

[openstack-testing-bot]

Title: precise_folsom_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_deploy/404/Project:precise_folsom_deployDate of build:Fri, 15 Mar 2013 09:23:16 -0400Build duration:1 min 41 secBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesBuild Artifactslogs/syslog.tar.gzlogs/test-02.os.magners.qa.lexington-log.tar.gzlogs/test-03.os.magners.qa.lexington-log.tar.gzlogs/test-04.os.magners.qa.lexington-log.tar.gzlogs/test-05.os.magners.qa.lexington-log.tar.gzlogs/test-06.os.magners.qa.lexington-log.tar.gzlogs/test-07.os.magners.qa.lexington-log.tar.gzlogs/test-08.os.magners.qa.lexington-log.tar.gzlogs/test-09.os.magners.qa.lexington-log.tar.gzlogs/test-10.os.magners.qa.lexington-log.tar.gzlogs/test-11.os.magners.qa.lexington-log.tar.gzlogs/test-12.os.magners.qa.lexington-log.tar.gzConsole Output[...truncated 63 lines...]DEBUG: Loading config.yaml from /var/lib/jenkins/jobs/precise_folsom_deploy/workspace/precise/nova-compute/config.yamlDEBUG: Charm 'nova-cloud-controller' - using charm path '/var/lib/jenkins/jobs/precise_folsom_deploy/workspace/precise/nova-cloud-controller'DEBUG: Branch: lp:~openstack-ubuntu-testing/charms/precise/nova-cloud-controller/trunk, revision: DEBUG: Charm path exists @ /var/lib/jenkins/jobs/precise_folsom_deploy/workspace/precise/nova-cloud-controller.DEBUG: Updating charm branch 'nova-cloud-controller'No revisions or tags to pull.DEBUG: Loading metadata from /var/lib/jenkins/jobs/precise_folsom_deploy/workspace/precise/nova-cloud-controller/metadata.yamlDEBUG: Loading config.yaml from /var/lib/jenkins/jobs/precise_folsom_deploy/workspace/precise/nova-cloud-controller/config.yamlDEBUG: Charm 'ceph' - using charm path '/var/lib/jenkins/jobs/precise_folsom_deploy/workspace/precise/ceph'DEBUG: Branch: lp:~openstack-ubuntu-testing/charms/precise/ceph/trunk, revision: DEBUG: Charm path exists @ /var/lib/jenkins/jobs/precise_folsom_deploy/workspace/precise/ceph.DEBUG: Updating charm branch 'ceph'No revisions or tags to pull.DEBUG: Loading metadata from /var/lib/jenkins/jobs/precise_folsom_deploy/workspace/precise/ceph/metadata.yamlDEBUG: Loading config.yaml from /var/lib/jenkins/jobs/precise_folsom_deploy/workspace/precise/ceph/config.yamlDEBUG: Charm 'keystone' - using charm path '/var/lib/jenkins/jobs/precise_folsom_deploy/workspace/precise/keystone'DEBUG: Branch: lp:~openstack-ubuntu-testing/charms/precise/keystone/trunk, revision: DEBUG: Charm path exists @ /var/lib/jenkins/jobs/precise_folsom_deploy/workspace/precise/keystone.DEBUG: Updating charm branch 'keystone'Unable to obtain lock file:///var/lib/jenkins/jobs/precise_folsom_deploy/workspace/precise/keystone/ held by ja...@shingle-house.org.uk on test-01 (process #26450), acquired 1381 hours, 36 minutes ago.Will continue to try until 09:24:49, unless you press Ctrl-C.See "bzr help break-lock" for more.bzr: ERROR: Could not acquire lock "(local)": file:///var/lib/jenkins/jobs/precise_folsom_deploy/workspace/precise/keystone/ERROR: Could not update branch at /var/lib/jenkins/jobs/precise_folsom_deploy/workspace/precise/keystone from lp:~openstack-ubuntu-testing/charms/precise/keystone/trunk+ rc=3+ echo 'Deployer returned: 3'Deployer returned: 3+ [[ 3 != 0 ]]+ echo 'Collating logs...'Collating logs...+ /var/lib/jenkins/tools/jenkins-scripts/collate-test-logs.py -o logs2013-03-15 09:24:49,515 INFO Connecting to environment...2013-03-15 09:24:50,933 INFO Connected to environment.2013-03-15 09:24:51,402 INFO 'status' command finished successfullyINFO:root:Setting up connection to test-12.os.magners.qa.lexingtonINFO:paramiko.transport:Connected (version 2.0, client OpenSSH_5.9p1)INFO:paramiko.transport:Authentication (publickey) failed.INFO:paramiko.transport:Authentication (publickey) successful!INFO:paramiko.transport:Secsh channel 1 opened.INFO:paramiko.transport.sftp:[chan 1] Opened sftp connection (server version 3)INFO:root:Archiving logs on test-12.os.magners.qa.lexingtonINFO:paramiko.transport:Secsh channel 2 opened.INFO:root:Grabbing information from test-12.os.magners.qa.lexingtonINFO:paramiko.transport.sftp:[chan 1] sftp session closed.+ exit 1Build step 'Execute shell' marked build as failureArchiving artifactsEmail 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: test_tempest_smoke #2

[openstack-testing-bot]

Title: test_tempest_smoke
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/test_tempest_smoke/2/Project:test_tempest_smokeDate of build:Fri, 15 Mar 2013 22:00:29 -0400Build duration:48 secBuild cause:Started by command line by jenkinsBuilt on:masterHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 491 lines...]Setting up python-nose (1.1.2-3ubuntu4) ...Setting up python-iso8601 (0.1.4-2) ...Setting up python-prettytable (0.6.1-1ubuntu1) ...Setting up python-simplejson (2.6.2-1) ...Setting up python-six (1.2.0-1) ...Setting up python-urllib3 (1.5-0ubuntu1) ...Setting up python-requests (1.1.0-1) ...Setting up python-novaclient (1:2.11.1-0ubuntu1) ...Setting up python-openssl (0.13-2ubuntu3) ...Setting up python-oslo.config (1:1.1.0-0ubuntu1) ...Setting up python-paramiko (1.7.7.1-3.1) ...Setting up python-sqlalchemy (0.7.9-1) ...Setting up python-sqlalchemy-ext (0.7.9-1) ...Setting up python-subunit (0.0.8+bzr176-1ubuntu4) ...Setting up python-testrepository (0.0.13-0ubuntu1) ...Setting up python-testresources (0.2.4-1ubuntu1) ...Setting up python-unittest2 (0.5.1-1ubuntu1) ...Setting up testrepository (0.0.13-0ubuntu1) ...Setting up xml-core (0.13+nmu2) ...Setting up python-keystoneclient (1:0.2.2-0ubuntu2) ...Setting up python-glanceclient (1:0.8.0-0ubuntu1) ...Processing triggers for libc-bin ...ldconfig deferred processing now taking placeProcessing triggers for ca-certificates ...Updating certificates in /etc/ssl/certs... 158 added, 0 removed; done.Running hooks in /etc/ca-certificates/update.ddone.Processing triggers for sgml-base ...[run_tempest.sh] Running setup scripts in tests/tempest.**Configuring Tempest users and tenants in Keystone.**[tests/tempest/setup/01-setup_users] Deleting user tempest-1 with id 4498684642cc447eb5848f36a3f8d4e4.WARNING: Bypassing authentication using a token & endpoint (authentication credentials are being ignored).[tests/tempest/setup/01-setup_users] Deleting user tempest-2 with id 0a6cf3f6cf9d49d5b82f0dfc09736179.WARNING: Bypassing authentication using a token & endpoint (authentication credentials are being ignored).[tests/tempest/setup/01-setup_users] Deleting tenant tempest-tenant-1 with id 4c754548390c4ac999190c26e4b3ec85WARNING: Bypassing authentication using a token & endpoint (authentication credentials are being ignored).[tests/tempest/setup/01-setup_users] Deleting tenant tempest-tenant-2 with id 042905f8504541f6856a90428be968e9WARNING: Bypassing authentication using a token & endpoint (authentication credentials are being ignored).[tests/tempest/setup/01-setup_users] Creating two users in Keystone for Tempst run...[tests/tempest/setup/01-setup_users] Created tenant #1 tempest-tenant-1 with id 9a3beb0ed55a4f02bdf94a2fd1430621.[tests/tempest/setup/01-setup_users] Created tenant #2 tempest-tenant-2 with id 765690775b9749c98dd67a4b6c7f30b1.fatal: repository '%TEMPEST_REPO%' does not existERROR:root:Test run failed.Recording test resultsNo test report files were found. Configuration error?Build step 'Publish JUnit test result report' changed build result to 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