Re: [Openstack] Internet access within launched instances too slow

[Rahul Sharma]

Hi All,

I was able to resolve this issue by changing the MTU size within the
instances from 1500 to 1454. I got these pointers from this mailthread:-
https://lists.launchpad.net/openstack/msg24050.html

Thanks and Regards
Rahul Sharma


On Tue, May 28, 2013 at 5:00 PM, Rahul Sharma rahulsharma...@gmail.comwrote:

 Here is the content of my nova-compute.conf file:-

 root@compute1:~# cat /etc/nova/nova-compute.conf
 [DEFAULT]
 libvirt_type=kvm
 libvirt_ovs_bridge=br-int
 libvirt_vif_type=ethernet
 libvirt_vif_driver=nova.virt.libvirt.vif.LibvirtHybridOVSBridgeDriver
 libvirt_use_virtio_for_bridges=True
 libvirt_cpu_mode=host-passthrough


 -Regards
 Rahul


 On Tue, May 28, 2013 at 4:46 PM, Rahul Sharma rahulsharma...@gmail.comwrote:

 Yes, same issue after restarting the nova-compute daemon.

 -Regards
 Rahul


 On Tue, May 28, 2013 at 4:29 PM, JuanFra Rodriguez Cardoso 
 juanfra.rodriguez.card...@gmail.com wrote:

 Same issues after restarting nova-compute daemons and launching new
 instances?

 ---
 JuanFra


 2013/5/28 Rahul Sharma rahulsharma...@gmail.com

 Nope. Still the same problem.

 -Regards
 Rahul


 On Tue, May 28, 2013 at 4:15 PM, Rahul Sharma rahulsharma...@gmail.com
  wrote:

 Thanks JuanFra. I will use these and let you know the status.

 Thanks and Regards
 Rahul Sharma


 On Tue, May 28, 2013 at 4:04 PM, JuanFra Rodriguez Cardoso 
 juanfra.rodriguez.card...@gmail.com wrote:

 Have you tried configuring your compute nodes with the following
 options in file 'nova.conf'?

 These options could be improve your instance performance:

 libvirt_cpu_mode = host-passthrough
 libvirt_use_virtio_for_bridges = True



 PD: I suppose you are using:

 libvirt_type = kvm
 compute_driver = libvirt.LibvirtDriver


  ---
 JuanFra


 2013/5/28 Rahul Sharma rahulsharma...@gmail.com

 I checked, they are fine. nslookup is giving correct result.

 root@instance1:/home/ubuntu# nslookup www.google.com
 Server: 192.168.0.4
 Address:192.168.0.4#53

 Non-authoritative answer:
 Name:   www.google.com
 Address: 74.125.135.147
 Name:   www.google.com
 Address: 74.125.135.99
 Name:   www.google.com
 Address: 74.125.135.103
 Name:   www.google.com
 Address: 74.125.135.104
 Name:   www.google.com
 Address: 74.125.135.105
 Name:   www.google.com
 Address: 74.125.135.106

 -Regards
 Rahul


 On Tue, May 28, 2013 at 3:42 PM, Balamurugan V G 
 balamuruga...@gmail.com wrote:

 Check if you have the right DNS server settings on your VM.
 Sometimes
 even that can slow the access.

 Regards,
 Balu

 On Tue, May 28, 2013 at 3:31 PM, Rahul Sharma 
 rahulsharma...@gmail.com wrote:
  Yes, I am using KVM.
 
  -Regards
  Rahul Sharma
 
 
  On Tue, May 28, 2013 at 2:49 PM, JuanFra Rodriguez Cardoso
  juanfra.rodriguez.card...@gmail.com wrote:
 
  Hi:
 
  Which hypervisor are you using? KVM with virtio driver?
 
  ---
  JuanFra
 
 
  2013/5/28 Rahul Sharma rahulsharma...@gmail.com
 
  Hi All,
 
  I have a multinode setup of Openstack-Grizzly release with
 Networking
  node as a separate machine. I am able to successfully bring up
 instances and
  ping to google from within the instances. Everything is working
 fine except
  the speed of internet access from within the instances.
 
  When I try to wget file or do apt-get update, its taking
 a lot of
  time(1 hr 40 mins for apt-get update). However, if I do the
 same on the
  physical compute-nodes or on the network-node, it updates
 within seconds. I
  am not sure why the network access within the instances is so
 slow which on
  the other hand is quite fast on the hosts.
 
  Any pointers or steps to debug the issue would be really
 helpful. Please
  let me know how I can debug this scenario.
 
  Thanks and Regards
  Rahul Sharma
 
  ___
  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] How to assign External ip to vm without quantum L3 agent

[Veera Reddy]

Hi,

IS there any way to access VM from external network without using quantum
l3 agent.

-- 
Regards,
VeeraReddy.B
___
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 to assign External ip to vm without quantum L3 agent

[Aaron Rosen]

No but the provider network extention does provide a way to do this that
might work for your usecase:
http://docs.openstack.org/trunk/openstack-network/admin/content/provider_networks.html


On Wed, May 29, 2013 at 11:02 PM, Veera Reddy veerare...@gmail.com wrote:

 Hi,

 IS there any way to access VM from external network without using quantum
 l3 agent.

 --
 Regards,
 VeeraReddy.B


 ___
 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] Can I create a VM with 2 NICs while there is only one network?

[Aaron Rosen]

Hi,

I still don't see why you want to have two nics on the same L2?  We don't
allow this because we don't want  to allow a tenants to bridge them
creating a loop in the network.

Aaron


On Thu, May 23, 2013 at 8:18 PM, Liu Wenmao marvel...@gmail.com wrote:

 Hello:

 I have a network with a subnet, I want create a VM with one NIC connected
 with this subnet, with one or two extra NIC left, because I want to do some
 more things such as intrusion protection

 I wonder is it possible to create a VM with more NICs than its connected
 network?

 ___
 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] How to assign External ip to vm without quantum L3 agent

[Édouard Thuleau]

Yes, the provider network provide a way for that use case.

And I proposed a blueprint [1] to be able to isolate ports on a same
network/subnet.
So in you case, if you set a provider network as a public network and if
you like to share this network between tenants, you will be able to isolate
l2 traffic between ports on this network to respond to classical security
constraints (isolation between tenants).

[1] https://blueprints.launchpad.net/quantum/+spec/isolated-network

Édouard.


On Thu, May 30, 2013 at 8:07 AM, Aaron Rosen aro...@nicira.com wrote:

 No but the provider network extention does provide a way to do this that
 might work for your usecase:
 http://docs.openstack.org/trunk/openstack-network/admin/content/provider_networks.html


 On Wed, May 29, 2013 at 11:02 PM, Veera Reddy veerare...@gmail.comwrote:

 Hi,

 IS there any way to access VM from external network without using quantum
 l3 agent.

 --
 Regards,
 VeeraReddy.B


 ___
 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] Reg: Networking in VMs

[Nehal J. Wani]

I am testing openstack in my college LAN network. I am able to have
multiple nova compute nodes. But there is no networking in the VMs. what is
the best possible solution to test this out? Any suggestions?

I tried creating pools with the command

nova-manage floating create --pool=nova --ip_range=10.3.3.0/24

But then

nova floating-ip-pool-list

Returns nothing. Where am I going wrong?

-- 
Nehal J. Wani
UG2, BTech CS+MS(CL)
IIIT-Hyderabad
http://commanlinewani.blogspot.com
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Can I create a VM with 2 NICs while there is only one network?

[Liu Wenmao]

Rosen:

I want to implement a virutal IPS(intrusion protection system) on L2 layer,
so the input interface and the output interface should be on the same
network.

Now I manually modify the packet vlan using OpenFlow protocol at the two
NICs, so that the loop won't happen.


On Thu, May 30, 2013 at 2:11 PM, Aaron Rosen aro...@nicira.com wrote:

 I still don't see why you want to have two nics on the same L2?  We don't
 allow this because we don't want  to allow a tenants to bridge them
 creating a loop in the network.

 Aaron


 On Thu, May 23, 2013 at 8:18 PM, Liu Wenmao marvel...@gmail.com wrote:

 Hello:

 I have a network with a subnet, I want create a VM with one NIC connected
 with this subnet, with one or two extra NIC left, because I want to do some
 more things such as intrusion protection

 I wonder is it possible to create a VM with more NICs than its connected
 network?

 ___
 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] Reg: Nova System Architecture

[Dhanasekaran Anbalagan]

Hi Guys,

Nova actually developed based on sharing nothing arch. But in my question
is I have five computer node. each compute node 8 cores.

It's possible can I  start instance with  32 core machine.

Please guide me.

-Dhanasekaran
Did I learn something today? If not, I wasted it.
___
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] Multiple machines hosting cinder-volumes with Folsom ?

[Sylvain Bauza]

Hi,

It sounds quite unclear for me about the possibility *in Folsom* to have 
two distinct Cinder hosts having each one LVM backend called 
cinder-volumes ?


As per the doc [1], I would say the answer is no, but could you please 
confirm ?


If so, do you have any idea on how to trick a nearly full LVM 
cinder-volumes VG ? (I can't hardly add a new disk for adding a second PV).


Thanks,
-Sylvain

[1] : 
http://docs.openstack.org/grizzly/openstack-block-storage/admin/content/multi_backend.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] Reg: Nova System Architecture

[Salvatore Orlando]

Hi Dhanasekaran,

It seems to me that the 'shared nothing' architecture [1] probably has
little to do with your need, as it refers to the various nova nodes, rather
than instances.
It looks like you want to start an instance which is distributed across
several nodes. Is this your goal?

Salvatore

[1] http://en.wikipedia.org/wiki/Shared_nothing_architecture


On 30 May 2013 14:20, Dhanasekaran Anbalagan bugcy...@gmail.com wrote:

 Hi Guys,

 Nova actually developed based on sharing nothing arch. But in my question
 is I have five computer node. each compute node 8 cores.

 It's possible can I  start instance with  32 core machine.

 Please guide me.

 -Dhanasekaran
 Did I learn something today? If not, I wasted it.

 ___
 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] Fwd: [Grizzly][Quantum] Floating IP is not reachable

[Anil Vishnoi]

Forwarding again with some hope for response :)

-- Forwarded message --
From: Anil Vishnoi vishnoia...@gmail.com
Date: Thu, May 30, 2013 at 3:14 AM
Subject: [Grizzly][Quantum] Floating IP is not reachable
To: openstack@lists.launchpad.net openstack@lists.launchpad.net



Hi All,

I have a setup where controller/network node is running on one server and i
have another server as a compute node. I am able to launch the VM and VM
gets its private IP from its respective DHCP server as well. VM is
connected to its private network. Private network is attached to the router
and external network is set as a gateway for the router. I am able to
associate floating ip to the VM as well.

But when i ping this floating ip from internet, i am not able to ping.
Although i am able to ping the gateway ip of the router. I checked the ARP
entry for the floating ip, and its successfully resolving the arp for this
floating ip.

I can see this address in the router name space as well.

# ip netns exec qrouter-3d7dfce4-c19a-4448-b276-1631690a403c ip addr
14: lo: LOOPBACK,UP,LOWER_UP mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
15: qr-e018e6ed-37: BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP mtu 1500
qdisc noqueue state UNKNOWN
link/ether fa:16:3e:f5:73:c5 brd ff:ff:ff:ff:ff:ff
inet 1.1.1.1/24 brd 1.1.1.255 scope global qr-e018e6ed-37
inet6 fe80::f816:3eff:fef5:73c5/64 scope link
   valid_lft forever preferred_lft forever
19: qg-d75a619f-ac: BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP mtu 1500
qdisc noqueue state UNKNOWN
link/ether fa:16:3e:2e:c6:4b brd ff:ff:ff:ff:ff:ff
inet 9.126.108.126/24 brd 9.126.108.255 scope global qg-d75a619f-ac
inet 9.126.108.127/32 brd 9.126.108.127 scope global qg-d75a619f-ac  
inet6 fe80::f816:3eff:fe2e:c64b/64 scope link
   valid_lft forever preferred_lft forever


So i can ping 9.126.108.126 but i am not able to ping 9.126.108.127. Also
both of these IP actually resolves to the same MAC address, is it expected
? I added rules in the default security group to allow TCP/UDP/ICMP traffic.

Please let me know if anybody has any clue on whats going on here , and how
can i further debug it. Please let me know if you need any other details.
-- 
Thanks
Anil



-- 
Thanks
Anil
___
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] Fwd: [Grizzly][Quantum] Floating IP is not reachable

[Salvatore Orlando]

We will need to look at iptables on your network node.
If you run iptables -n -tnat --list you should see a couple of DNAT/SNAT
rules for forwarding traffic netween 9.126.108.127.

In any case, bear in mind that the default security group does not allow
ICMP. If you have not enabled it, it might as well be that this is reason
for your issue.

Salvatore


On 30 May 2013 15:36, Anil Vishnoi vishnoia...@gmail.com wrote:

 Forwarding again with some hope for response :)


 -- Forwarded message --
 From: Anil Vishnoi vishnoia...@gmail.com
 Date: Thu, May 30, 2013 at 3:14 AM
 Subject: [Grizzly][Quantum] Floating IP is not reachable
 To: openstack@lists.launchpad.net openstack@lists.launchpad.net



 Hi All,

 I have a setup where controller/network node is running on one server and
 i have another server as a compute node. I am able to launch the VM and VM
 gets its private IP from its respective DHCP server as well. VM is
 connected to its private network. Private network is attached to the router
 and external network is set as a gateway for the router. I am able to
 associate floating ip to the VM as well.

 But when i ping this floating ip from internet, i am not able to ping.
 Although i am able to ping the gateway ip of the router. I checked the ARP
 entry for the floating ip, and its successfully resolving the arp for this
 floating ip.

 I can see this address in the router name space as well.

 # ip netns exec qrouter-3d7dfce4-c19a-4448-b276-1631690a403c ip addr
 14: lo: LOOPBACK,UP,LOWER_UP mtu 16436 qdisc noqueue state UNKNOWN
 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
 inet 127.0.0.1/8 scope host lo
 inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
 15: qr-e018e6ed-37: BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP mtu 1500
 qdisc noqueue state UNKNOWN
 link/ether fa:16:3e:f5:73:c5 brd ff:ff:ff:ff:ff:ff
 inet 1.1.1.1/24 brd 1.1.1.255 scope global qr-e018e6ed-37
 inet6 fe80::f816:3eff:fef5:73c5/64 scope link
valid_lft forever preferred_lft forever
 19: qg-d75a619f-ac: BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP mtu 1500
 qdisc noqueue state UNKNOWN
 link/ether fa:16:3e:2e:c6:4b brd ff:ff:ff:ff:ff:ff
 inet 9.126.108.126/24 brd 9.126.108.255 scope global qg-d75a619f-ac
 inet 9.126.108.127/32 brd 9.126.108.127 scope global qg-d75a619f-ac
  
 inet6 fe80::f816:3eff:fe2e:c64b/64 scope link
valid_lft forever preferred_lft forever


 So i can ping 9.126.108.126 but i am not able to ping 9.126.108.127. Also
 both of these IP actually resolves to the same MAC address, is it expected
 ? I added rules in the default security group to allow TCP/UDP/ICMP traffic.

 Please let me know if anybody has any clue on whats going on here , and
 how can i further debug it. Please let me know if you need any other
 details.
 --
 Thanks
 Anil



 --
 Thanks
 Anil

 ___
 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] Reg: Nova System Architecture

[Dhanasekaran Anbalagan]

HI Salvatore,

It's possible start an instance which is distributed across several nodes.
it's my goal.

please guide me.

-Dhanasekaran.

Did I learn something today? If not, I wasted it.


On Thu, May 30, 2013 at 9:33 AM, Salvatore Orlando sorla...@nicira.comwrote:

 Hi Dhanasekaran,

 It seems to me that the 'shared nothing' architecture [1] probably has
 little to do with your need, as it refers to the various nova nodes, rather
 than instances.
 It looks like you want to start an instance which is distributed across
 several nodes. Is this your goal?

 Salvatore

 [1] http://en.wikipedia.org/wiki/Shared_nothing_architecture


 On 30 May 2013 14:20, Dhanasekaran Anbalagan bugcy...@gmail.com wrote:

 Hi Guys,

 Nova actually developed based on sharing nothing arch. But in my question
 is I have five computer node. each compute node 8 cores.

 It's possible can I  start instance with  32 core machine.

 Please guide me.

 -Dhanasekaran
 Did I learn something today? If not, I wasted it.

 ___
 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] [grizzly]Problems of qpid as rpcbackend

[minmin ren]

Hi all,

I think it is a bug of qpid as rpcbackend.

   Other service(nova-compute, cinder-scheduler, etc) use eventlet thead to
run service. They stop service use thread kill() method. The last step
rpc.cleanup() just did nothing, because the relative consume connection run
in thread and killed. I think it is unnecessary. All queue is auto-delete,
they will be removed when all receiver disappear.

However, cinder-volume use process to run service, so stop service need to
close connection and receiver (consumer) of the session of connection need
to close when call connection.close().
receiver close will sent MessageCancel and QueueDelete message to
broker(qpid server), so that all cinder-volume queue be removed.

I think that the reason of problem confused me.

But I don't know how to solve it.


2013/5/28 minmin ren rmm0...@gmail.com

 I think I found some problems of qpid as rpcbackend, however I'm not sure
 about it. Could anyone  try to test it with your environment?

 openstack grizzly version

 config file need debug=True

 1. service openstack-cinder-scheduler stop (nova-compute, nova-scheduler,
 etc)
 2.  vi /var/log/cinder/scheduler.log   some info will be found like
 this.

 I deployed two machines(node1 and dev202)

 2013-05-27 06:02:46 CRITICAL [cinder] need more than 0 values to unpack
 Traceback (most recent call last):
   File /usr/bin/cinder-scheduler, line 50, in module
 service.wait()
   File /usr/lib/python2.6/site-packages/cinder/service.py, line 613, in
 wait
 rpc.cleanup()
   File
 /usr/lib/python2.6/site-packages/cinder/openstack/common/rpc/__init__.py,
 line 240, in cleanup
 return _get_impl().cleanup()
   File
 /usr/lib/python2.6/site-packages/cinder/openstack/common/rpc/impl_qpid.py,
 line 649, in cleanup
 return rpc_amqp.cleanup(Connection.pool)
   File
 /usr/lib/python2.6/site-packages/cinder/openstack/common/rpc/amqp.py,
 line 671, in cleanup
 connection_pool.empty()
   File
 /usr/lib/python2.6/site-packages/cinder/openstack/common/rpc/amqp.py,
 line 80, in empty
 self.get().close()
   File
 /usr/lib/python2.6/site-packages/cinder/openstack/common/rpc/impl_qpid.py,
 line 386, in close
 self.connection.close()
   File string, line 6, in close
   File /usr/lib/python2.6/site-packages/qpid/messaging/endpoints.py,
 line 316, in close
 ssn.close(timeout=timeout)
   File string, line 6, in close
   File /usr/lib/python2.6/site-packages/qpid/messaging/endpoints.py,
 line 749, in close
 if not self._ewait(lambda: self.closed, timeout=timeout):
   File /usr/lib/python2.6/site-packages/qpid/messaging/endpoints.py,
 line 566, in _ewait
 result = self.connection._ewait(lambda: self.error or predicate(),
 timeout)
   File /usr/lib/python2.6/site-packages/qpid/messaging/endpoints.py,
 line 208, in _ewait
 result = self._wait(lambda: self.error or predicate(), timeout)
   File /usr/lib/python2.6/site-packages/qpid/messaging/endpoints.py,
 line 193, in _wait
 return self._waiter.wait(predicate, timeout=timeout)
   File /usr/lib/python2.6/site-packages/qpid/concurrency.py, line 57, in
 wait
 self.condition.wait(3)
   File /usr/lib/python2.6/site-packages/qpid/concurrency.py, line 96, in
 wait
 sw.wait(timeout)
   File /usr/lib/python2.6/site-packages/qpid/compat.py, line 53, in wait
 ready, _, _ = select([self], [], [], timeout)
 ValueError: need more than 0 values to unpack


 I put the problems with multi-cinder-volumes on launchpad
 https://answers.launchpad.net/cinder/+question/229456
 Because I encountered this problems, however others services except
 cinder-volume never appear this problems.
 Then I found other services log print some critical info, error at
 self.connection.close()
 So I delete self.connection.close() which should not be removed, I watch
 qpid queue infomation, the problem which I  confused on
 multi-cinder-volumes disappear.
 As a result, I think the problem I found may be a bug.

___
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 with Ceph, boot from volume

[Martin Mailand]

Hi Josh,

I am trying to use ceph with openstack (grizzly), I have a multi host setup.
I followed the instruction http://ceph.com/docs/master/rbd/rbd-openstack/.
Glance is working without a problem.
With cinder I can create and delete volumes without a problem.

But I cannot boot from volumes.
I doesn't matter if use horizon or the cli, the vm goes to the error state.

From the nova-compute.log I get this.

2013-05-30 16:08:45.224 ERROR nova.compute.manager
[req-5679ddfe-79e3-4adb-b220-915f4a38b532
8f9630095810427d865bc90c5ea04d35 43b2bbbf5daf4badb15d67d87ed2f3dc]
[instance: 059589a3-72fc-444d-b1f0-ab1567c725fc] Instance failed block
device setup
.
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc] ConnectionError: [Errno 101]
ENETUNREACH

What tries nova to reach? How could I debug that further?

Full Log included.

-martin

Log:

ceph --version
ceph version 0.61 (237f3f1e8d8c3b85666529860285dcdffdeda4c5)

root@compute1:~# dpkg -l|grep -e ceph-common -e cinder
ii  ceph-common  0.61-1precise
   common utilities to mount and interact with a ceph storage
cluster
ii  python-cinderclient  1:1.0.3-0ubuntu1~cloud0
   python bindings to the OpenStack Volume API


nova-compute.log

2013-05-30 16:08:45.224 ERROR nova.compute.manager
[req-5679ddfe-79e3-4adb-b220-915f4a38b532
8f9630095810427d865bc90c5ea04d35 43b2bbbf5daf4badb15d67d87ed2f3dc]
[instance: 059589a3-72fc-444d-b1f0-ab1567c725fc] Instance failed block
device setup
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc] Traceback (most recent call last):
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc]   File
/usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 1071,
in _prep_block_device
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc] return
self._setup_block_device_mapping(context, instance, bdms)
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc]   File
/usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 721, in
_setup_block_device_mapping
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc] volume =
self.volume_api.get(context, bdm['volume_id'])
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc]   File
/usr/lib/python2.7/dist-packages/nova/volume/cinder.py, line 193, in get
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc]
self._reraise_translated_volume_exception(volume_id)
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc]   File
/usr/lib/python2.7/dist-packages/nova/volume/cinder.py, line 190, in get
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc] item =
cinderclient(context).volumes.get(volume_id)
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc]   File
/usr/lib/python2.7/dist-packages/cinderclient/v1/volumes.py, line 180,
in get
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc] return self._get(/volumes/%s
% volume_id, volume)
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc]   File
/usr/lib/python2.7/dist-packages/cinderclient/base.py, line 141, in _get
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc] resp, body =
self.api.client.get(url)
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc]   File
/usr/lib/python2.7/dist-packages/cinderclient/client.py, line 185, in get
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc] return self._cs_request(url,
'GET', **kwargs)
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc]   File
/usr/lib/python2.7/dist-packages/cinderclient/client.py, line 153, in
_cs_request
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc] **kwargs)
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc]   File
/usr/lib/python2.7/dist-packages/cinderclient/client.py, line 123, in
request
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc] **kwargs)
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc]   File
/usr/lib/python2.7/dist-packages/requests/api.py, line 44, in request
2013-05-30 16:08:45.224 

[Openstack] [Cinder] Re: Multiple machines hosting cinder-volumes with Folsom ?

[Sylvain Bauza]

Le 30/05/2013 15:25, Sylvain Bauza a écrit :

Hi,

It sounds quite unclear for me about the possibility *in Folsom* to 
have two distinct Cinder hosts having each one LVM backend called 
cinder-volumes ?


As per the doc [1], I would say the answer is no, but could you please 
confirm ?


If so, do you have any idea on how to trick a nearly full LVM 
cinder-volumes VG ? (I can't hardly add a new disk for adding a second 
PV).


Thanks,
-Sylvain

[1] : 
http://docs.openstack.org/grizzly/openstack-block-storage/admin/content/multi_backend.html


Replying to myself. As per [2], it seems having a multiple cinder-volume 
setup in Folsom is achiveable. Could someone from Cinder confirm that 
this setup is OK ?


[2] : https://lists.launchpad.net/openstack/msg21825.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] Grizzly Multinode, but Quantum not working

[Nikola Pajtic]

Hi all,

I followed the Grizzly Multinode howto 
(https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_MultiNode/OpenStack_Grizzly_Install_Guide.rst), 
but could not make Quantum operational. I apologize in advance for the 
long email, but I was hoping that someone can help me with this setup.


To make it as easy as possible, my setup env is absolutely the same: I 
have the Controller, Compute and Network nodes, which are connected to 
each other as described. The only difference is VM Internet Access IP 
address. Instead of 192.168.100.0/24, my range is 192.168.0.0/16, and I 
gave 192.168.1.0/24 to OpenStack nodes. OS is Ubuntu Server 12.04 
x86_64. Just to make it clear, my company's network is organized like 
this:


[Public IP: 212.200.x.x] - Router (gateway: 192.168.0.3) - 
[192.168.0.0/16] - [our workstations: 192.168.0.0/24]


[openstack nodes: 192.168.1.0/24]

Regarding nodes' configuration, I followed the same steps as howto 
suggested, changing only IP addresses where needed (ie, 10.10.10.51 - 
10.10.10.201, etc). Everything went fine and without errors, so I came 
to 5. Your first VM. Since I'm still struggling to understand 
Quantum's fundamentals, I am not sure whether I did something wrong from 
now on. For this first steps with OpenStack, my goal is to be able to 
create a VM and to give it IP address from 192.168.1.0/24 pool, so I can 
ssh to it from my workstation, for example. Of course, it would be nice 
to allow that VM access to the Internet (public access to that VM is not 
necessary for now).


So, I created the new tenant and network for it. The subnet for tenant 
network I created like this:


# quantum subnet-create --tenant-id $put_id_of_project_one net_proj_one 
10.10.10.0/24


Next, I created the router and assigned it to the l3-agent and subnet. 
Then, I created ext_net and a subnet for the floating ips, like this:


# quantum subnet-create --tenant-id $put_id_of_admin_tenant 
--allocation-pool start=192.168.1.2,end=192.168.1.199 --gateway 
192.168.0.3 ext_net 192.168.1.0/24 --enable_dhcp=False


Is this correct? Internal network should be 10.10.10.0/24 and external 
192.168.1.0/24, so when I create an instance and associate the IP, lets 
say, 192.168.1.5, it should forward packets to 10.10.10.5..right?


Back to howto, I set the security rules like this (because in nova.conf 
I told it to use Quantum Sec.Groups, not Nova's):
# quantum security-group-rule-create --protocol icmp --direction 
ingress default
# quantum security-group-rule-create --protocol tcp --port-range-min 22 
--port-range-max 22 --direction ingress default


Finally, I logged in Dashboard and created new instance, which was 
successful. But, there are several networking problems:


1. Instance Console Log: wget: can't connect to remote host 
(169.254.169.254): Network is unreachable
2. VM did not receive its private IP (10.10.10.x), so it is not 
pingable


So, I would appreciate it if you could tell me what could be the 
potential problems, just to point me in some directions. Feel free to 
ask for logs and configs, I will gladly provide those.


Thanks in advance.
Best regards,

--
Nikola Pajtic

___
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]Problems of qpid as rpcbackend

[Ray Pekowski]

I am not familiar with impl_qpid,py, but am familiar with amqp.py and have
had problems around rpc_amqp.cleanup() the Pool.empty() method it calls.
It was a totally different problem, but I decided to take a look at your
problem.  I noticed that in impl_qpid.py the only other place a
connection.close() is done is surrounded by this code:

# Close the session if necessary
if self.connection.opened():
try:
self.connection.close()
except qpid_exceptions.ConnectionError:
pass

I suggest you wrap the close at line 386 of impl_qpid.py with the same code
and your problem will be fixed.  Here is the line identified from your call
stack:

  File /usr/lib/python2.6/site-
packages/cinder/openstack/common/rpc/impl_qpid.py, line 386, in close
self.connection.close()

If that works, open a bug report.

Good catch

Ray
___
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] Havana-1 development milestone available

[Thierry Carrez]

Hi everyone,

The first milestone of the Havana development cycle, havana-1 is now
available for Keystone, Glance, Nova, Horizon, Networking, Cinder,
Ceilometer, and Heat. It contains all the new features that have been
added since the Grizzly pre-release Feature Freeze in March.

You can see the full list of new features and fixed bugs, as well as
tarball downloads, at:

https://launchpad.net/keystone/havana/havana-1
https://launchpad.net/glance/havana/havana-1
https://launchpad.net/nova/havana/havana-1
https://launchpad.net/horizon/havana/havana-1
https://launchpad.net/quantum/havana/havana-1
https://launchpad.net/cinder/havana/havana-1
https://launchpad.net/ceilometer/havana/havana-1
https://launchpad.net/heat/havana/havana-1

Including the oslo libraries, 63 blueprints were implemented and 671
bugs were fixed during this milestone. The next development milestone,
havana-2, is scheduled for July 18th.

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] [ceilometer] support for older versions of ceilometer

[Doug Hellmann]

The ceilometer team has had a few requests for help with older versions of
ceilometer or running the grizzly version of ceilometer with older versions
of other OpenStack components lately. We appreciate the level of interest
in the project but, as much as we would like to, unfortunately we are not
always able to help everyone with these mixed configurations. During the
early phases of our development we tried to maintain compatibility with
folsom, even well into the grizzly development cycle. We are no longer
doing that, however, and so to make clear what support we can offer, the
ceilometer team has put together the statement below. It has been added to
our documentation, and we are posting here to make sure everyone has a
chance to see it.

Regards,
Doug


The ceilometer team has limited capacity to provide support for older
versions of the project. Because the project graduated from incubation
around the time of the grizzly release, that is the first version for which
we will provide regular ongoing support following the standard deprecation
cycle for OpenStack [1]. The grizzly version of ceilometer  cannot be
installed on the same server with earlier versions of OpenStack because of
conflicting package requirements, but is API compatible with the folsom
release if installed separately.

[1] https://wiki.openstack.org/wiki/StableBranch
___
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] Reg: Nova System Architecture

[Aaron Rosen]

No, you would have to start several instances one on each compute node and
implement that distribution in your application.


On Thu, May 30, 2013 at 6:46 AM, Dhanasekaran Anbalagan
bugcy...@gmail.comwrote:

 HI Salvatore,

 It's possible start an instance which is distributed across several
 nodes. it's my goal.

 please guide me.

 -Dhanasekaran.

 Did I learn something today? If not, I wasted it.


 On Thu, May 30, 2013 at 9:33 AM, Salvatore Orlando sorla...@nicira.comwrote:

 Hi Dhanasekaran,

 It seems to me that the 'shared nothing' architecture [1] probably has
 little to do with your need, as it refers to the various nova nodes, rather
 than instances.
 It looks like you want to start an instance which is distributed across
 several nodes. Is this your goal?

 Salvatore

 [1] http://en.wikipedia.org/wiki/Shared_nothing_architecture


 On 30 May 2013 14:20, Dhanasekaran Anbalagan bugcy...@gmail.com wrote:

 Hi Guys,

 Nova actually developed based on sharing nothing arch. But in my
 question is I have five computer node. each compute node 8 cores.

 It's possible can I  start instance with  32 core machine.

 Please guide me.

 -Dhanasekaran
 Did I learn something today? If not, I wasted it.

 ___
 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] Reg: Nova System Architecture

[Dhanasekaran Anbalagan]

HI Aaron,

I would like to know how the sharing of resources happening in OpenStack.
Assume that there are two compute nodes of 4 physical cores each with 16 GB
of Physical RAM each, would I be able to start an instance with 8 cores and
32 Gb of RAM. How this is handled in Openstack.

-Dhanasekaran.

Did I learn something today? If not, I wasted it.
___
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] Reg: Nova System Architecture

[Salvatore Orlando]

Hi again,

You would need a compute driver for a hypervisor supporting a distributed
virtual machine.
I have a very limited knowledge of server virtualization and nova drivers,
but I don't think such driver exists for nova.

In fact, I don't think a hypervisor which does that is generally available
at the moment.
You probably might look at tools such as PVM or OpenMP.

Salvatore


On 30 May 2013 19:54, Dhanasekaran Anbalagan bugcy...@gmail.com wrote:

 HI Aaron,

 I would like to know how the sharing of resources happening in OpenStack.
 Assume that there are two compute nodes of 4 physical cores each with 16 GB
 of Physical RAM each, would I be able to start an instance with 8 cores and
 32 Gb of RAM. How this is handled in Openstack.

 -Dhanasekaran.

 Did I learn something today? If not, I wasted it.



___
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] Baremetal deployment [Grizzly]

[Mikyung Kang]

Hello Chris,

This may help: (even though it's too late ^^;)

nova/virt/baremetal/db/sqlalchemy/migration.py

56 - from migrate import exceptions as versioning_exceptions
56 + try:
57 + # Try the more specific path first (migrate = 0.6)
58 + from migrate.versioning import exceptions as versioning_exceptions
59 + except ImportError:
60 + # Use the newer path (migrate = 0.7)
61 + from migrate import exceptions as versioning_exceptions

Thanks,
Mikyung


- Original Message -
From: cl...@yahoo.fr
To: openstack@lists.launchpad.net
Sent: Sunday, May 5, 2013 4:59:27 AM
Subject: [Openstack] Baremetal deployment [Grizzly]

HI all,
I am trying to setup a  nova compute node for baremetal deployment and I am
following the instructions from the wiki for that purpose.

https://wiki.openstack.org/wiki/Baremetal


I am confused by the step which explains how to setup the BM database 


A separate database schema must be created for the baremetal driver to
store information about the enrolled hardware. Create it first:

 mysql CREATE DATABASE nova_bm;
 mysql GRANT ALL ON nova_bm.* TO 'nova_user'@'some_host' IDENTIFIED BY
'$password';
Then initialize the database with:

 nova-baremetal-manage db sync

My nova compute node is not running mysql so I guess I should run the above
command on the nova controller, which is what I am doing then

mysql CREATE DATABASE nova_bm;
mysql GRANT ALL ON nova_bm.* TO 'nova'@'%' IDENTIFIED BY
'PasswordUsedForNova';

by PasswordUsedForNova I mean the password found in the nova.conf file on
the compute node in the sql_connection string taken fron the [baremetal]
section 

sql_connection =
mysql://nova:PasswordUsedForNova@IPofMyControllerNode/nova_bm

Now I run the db sync command and it produces the following

[root@nova-04 ~]# nova-baremetal-manage db sync
Command failed, please check log for more info
2013-05-04 22:04:10.899 2469 CRITICAL nova [-] 'module' object has no
attribute 'DatabaseNotControlledError'
2013-05-04 22:04:10.899 2469 TRACE nova Traceback (most recent call last):
2013-05-04 22:04:10.899 2469 TRACE nova   File
/usr/bin/nova-baremetal-manage, line 221, in module
2013-05-04 22:04:10.899 2469 TRACE nova main()
2013-05-04 22:04:10.899 2469 TRACE nova   File
/usr/bin/nova-baremetal-manage, line 213, in main
2013-05-04 22:04:10.899 2469 TRACE nova fn(*fn_args, **fn_kwargs)
2013-05-04 22:04:10.899 2469 TRACE nova   File
/usr/bin/nova-baremetal-manage, line 101, in sync
2013-05-04 22:04:10.899 2469 TRACE nova bmdb_migration.db_sync(version)
2013-05-04 22:04:10.899 2469 TRACE nova   File
/usr/lib/python2.6/site-packages/nova/virt/baremetal/db/migration.py, line
34, in db_sync
2013-05-04 22:04:10.899 2469 TRACE nova return
IMPL.db_sync(version=version)
2013-05-04 22:04:10.899 2469 TRACE nova   File
/usr/lib/python2.6/site-packages/nova/virt/baremetal/db/sqlalchemy/migratio
n.py, line 71, in db_sync
2013-05-04 22:04:10.899 2469 TRACE nova current_version = db_version()
2013-05-04 22:04:10.899 2469 TRACE nova   File
/usr/lib/python2.6/site-packages/nova/virt/baremetal/db/sqlalchemy/migratio
n.py, line 85, in db_version
2013-05-04 22:04:10.899 2469 TRACE nova except
versioning_exceptions.DatabaseNotControlledError:
2013-05-04 22:04:10.899 2469 TRACE nova AttributeError: 'module' object has
no attribute 'DatabaseNotControlledError'
2013-05-04 22:04:10.899 2469 TRACE nova

Any idea ?

Chris


___
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] Fwd: [Grizzly][Quantum] Floating IP is not reachable

[Anil Vishnoi]

This is how my iptable looks like

# iptables -n -tnat --list
Chain PREROUTING (policy ACCEPT)
target prot opt source   destination
nova-api-PREROUTING  all  --  0.0.0.0/00.0.0.0/0

Chain INPUT (policy ACCEPT)
target prot opt source   destination

Chain OUTPUT (policy ACCEPT)
target prot opt source   destination
nova-api-OUTPUT  all  --  0.0.0.0/00.0.0.0/0

Chain POSTROUTING (policy ACCEPT)
target prot opt source   destination
nova-api-POSTROUTING  all  --  0.0.0.0/00.0.0.0/0
nova-postrouting-bottom  all  --  0.0.0.0/00.0.0.0/0

Chain nova-api-OUTPUT (1 references)
target prot opt source   destination

Chain nova-api-POSTROUTING (1 references)
target prot opt source   destination

Chain nova-api-PREROUTING (1 references)
target prot opt source   destination

Chain nova-api-float-snat (1 references)
target prot opt source   destination

Chain nova-api-snat (1 references)
target prot opt source   destination
nova-api-float-snat  all  --  0.0.0.0/00.0.0.0/0

Chain nova-postrouting-bottom (1 references)
target prot opt source   destination
nova-api-snat  all  --  0.0.0.0/00.0.0.0/0

I do have rule in my default security group to allow tcp/udp/icmp traffic
to my VM.

Apart from this, i do not see private IP address in the qdhcp name space
# ip netns exec qdhcp-593574c7-2a27-4b5e-bd6d-ebd7282ffc08 ip addr list
32: tapc7622702-f7: BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP mtu 1500
qdisc noqueue state UNKNOWN
link/ether fa:16:3e:ec:d7:b8 brd ff:ff:ff:ff:ff:ff
inet 1.1.2.3/24 brd 1.1.2.255 scope global tapc7622702-f7
inet6 fe80::f816:3eff:feec:d7b8/64 scope link
   valid_lft forever preferred_lft forever
33: lo: LOOPBACK,UP,LOWER_UP mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever

Can it cause any issue ? Will it be helpful if i configure
use NoopFirewallDriver on controller/compute node ?

Please let me know if you need any other data.

Thanks
Anil


On Thu, May 30, 2013 at 7:13 PM, Salvatore Orlando sorla...@nicira.comwrote:

 We will need to look at iptables on your network node.
 If you run iptables -n -tnat --list you should see a couple of DNAT/SNAT
 rules for forwarding traffic netween 9.126.108.127.

 In any case, bear in mind that the default security group does not allow
 ICMP. If you have not enabled it, it might as well be that this is reason
 for your issue.

 Salvatore


 On 30 May 2013 15:36, Anil Vishnoi vishnoia...@gmail.com wrote:

 Forwarding again with some hope for response :)


 -- Forwarded message --
 From: Anil Vishnoi vishnoia...@gmail.com
 Date: Thu, May 30, 2013 at 3:14 AM
 Subject: [Grizzly][Quantum] Floating IP is not reachable
 To: openstack@lists.launchpad.net openstack@lists.launchpad.net



 Hi All,

 I have a setup where controller/network node is running on one server and
 i have another server as a compute node. I am able to launch the VM and VM
 gets its private IP from its respective DHCP server as well. VM is
 connected to its private network. Private network is attached to the router
 and external network is set as a gateway for the router. I am able to
 associate floating ip to the VM as well.

 But when i ping this floating ip from internet, i am not able to ping.
 Although i am able to ping the gateway ip of the router. I checked the ARP
 entry for the floating ip, and its successfully resolving the arp for this
 floating ip.

 I can see this address in the router name space as well.

 # ip netns exec qrouter-3d7dfce4-c19a-4448-b276-1631690a403c ip addr
 14: lo: LOOPBACK,UP,LOWER_UP mtu 16436 qdisc noqueue state UNKNOWN
 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
 inet 127.0.0.1/8 scope host lo
 inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
 15: qr-e018e6ed-37: BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP mtu 1500
 qdisc noqueue state UNKNOWN
 link/ether fa:16:3e:f5:73:c5 brd ff:ff:ff:ff:ff:ff
 inet 1.1.1.1/24 brd 1.1.1.255 scope global qr-e018e6ed-37
 inet6 fe80::f816:3eff:fef5:73c5/64 scope link
valid_lft forever preferred_lft forever
 19: qg-d75a619f-ac: BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP mtu 1500
 qdisc noqueue state UNKNOWN
 link/ether fa:16:3e:2e:c6:4b brd ff:ff:ff:ff:ff:ff
 inet 9.126.108.126/24 brd 9.126.108.255 scope global qg-d75a619f-ac
 inet 9.126.108.127/32 brd 9.126.108.127 scope global qg-d75a619f-ac
  
 inet6 fe80::f816:3eff:fe2e:c64b/64 scope link
valid_lft forever preferred_lft forever


 So i can ping 9.126.108.126 but i am not able to ping 9.126.108.127.
 Also both of these IP actually resolves to the same MAC address, is it
 expected ? I added 

Re: [Openstack] Openstack with Ceph, boot from volume

[Josh Durgin]

On 05/30/2013 07:37 AM, Martin Mailand wrote:

Hi Josh,

I am trying to use ceph with openstack (grizzly), I have a multi host setup.
I followed the instruction http://ceph.com/docs/master/rbd/rbd-openstack/.
Glance is working without a problem.
With cinder I can create and delete volumes without a problem.

But I cannot boot from volumes.
I doesn't matter if use horizon or the cli, the vm goes to the error state.

 From the nova-compute.log I get this.

2013-05-30 16:08:45.224 ERROR nova.compute.manager
[req-5679ddfe-79e3-4adb-b220-915f4a38b532
8f9630095810427d865bc90c5ea04d35 43b2bbbf5daf4badb15d67d87ed2f3dc]
[instance: 059589a3-72fc-444d-b1f0-ab1567c725fc] Instance failed block
device setup
.
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc] ConnectionError: [Errno 101]
ENETUNREACH

What tries nova to reach? How could I debug that further?


It's trying to talk to the cinder api, and failing to connect at all.
Perhaps there's a firewall preventing that on the compute host, or
it's trying to use the wrong endpoint for cinder (check the keystone
service and endpoint tables for the volume service).

Josh


Full Log included.

-martin

Log:

ceph --version
ceph version 0.61 (237f3f1e8d8c3b85666529860285dcdffdeda4c5)

root@compute1:~# dpkg -l|grep -e ceph-common -e cinder
ii  ceph-common  0.61-1precise
common utilities to mount and interact with a ceph storage
cluster
ii  python-cinderclient  1:1.0.3-0ubuntu1~cloud0
python bindings to the OpenStack Volume API


nova-compute.log

2013-05-30 16:08:45.224 ERROR nova.compute.manager
[req-5679ddfe-79e3-4adb-b220-915f4a38b532
8f9630095810427d865bc90c5ea04d35 43b2bbbf5daf4badb15d67d87ed2f3dc]
[instance: 059589a3-72fc-444d-b1f0-ab1567c725fc] Instance failed block
device setup
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc] Traceback (most recent call last):
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc]   File
/usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 1071,
in _prep_block_device
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc] return
self._setup_block_device_mapping(context, instance, bdms)
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc]   File
/usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 721, in
_setup_block_device_mapping
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc] volume =
self.volume_api.get(context, bdm['volume_id'])
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc]   File
/usr/lib/python2.7/dist-packages/nova/volume/cinder.py, line 193, in get
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc]
self._reraise_translated_volume_exception(volume_id)
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc]   File
/usr/lib/python2.7/dist-packages/nova/volume/cinder.py, line 190, in get
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc] item =
cinderclient(context).volumes.get(volume_id)
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc]   File
/usr/lib/python2.7/dist-packages/cinderclient/v1/volumes.py, line 180,
in get
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc] return self._get(/volumes/%s
% volume_id, volume)
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc]   File
/usr/lib/python2.7/dist-packages/cinderclient/base.py, line 141, in _get
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc] resp, body =
self.api.client.get(url)
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc]   File
/usr/lib/python2.7/dist-packages/cinderclient/client.py, line 185, in get
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc] return self._cs_request(url,
'GET', **kwargs)
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc]   File
/usr/lib/python2.7/dist-packages/cinderclient/client.py, line 153, in
_cs_request
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc] **kwargs)
2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
059589a3-72fc-444d-b1f0-ab1567c725fc]   File
/usr/lib/python2.7/dist-packages/cinderclient/client.py, line 123, in
request
2013-05-30 

[Openstack] HA Tiered Storage

[Chris Bartels]

Hi,

 

I have plans to rent dedicated servers running on full server sized VMs
running on OpenStack, and the servers all will feature 2-tier storage
schemes, so that the customers can have both a 10k rpm SAS drive based disk
 another SSD based disk on their dedicated server.

 

Each server will have 6x 6Gb/s 10k rpm SAS disks in 3x3 RAID10,  2x 6Gb/s
SATAIII SSDs in 1x1 RAID1.

 

The SAS disks are each 300GB, and get divided into 584GB of space for use in
processing daily snapshots of both the SAS  SSD customer disk space, and
provide 228GB of SAS disk space for cinder-volumes image disk space for the
customer.

 

The SSDs are 64GB each  provides 64GB of cinder-volumes image disk space
for the customer.

 

My concern is with implementing HA, in that how will I be sure that when the
VM migrates between servers that the 2 disk images will make it to the right
disks on the target server? The 228GB disk image would need to stay on the
SAS disk  the 64GB disk image would need to stay on the SSD, regardless of
which server it migrates to.

 

Is there a way to be sure this happens, or will I be unable to use HA?

 

Regards,

Chris

___
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] [ceilometer] support for older versions of ceilometer

[Tim Bell]

 

Doug,

 

Can you advise on what the plan/policy will be for Havana ?

 

-  Will I be able to run Havana core components such as Nova with 
Grizzly ceilometer ?

-  Will I be able to run Havana ceilometer with Grizzly core components 
(with reduced functionality compared to the Havana
core components) ?

 

Tim

 

From: Openstack [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] 
On Behalf Of Doug Hellmann
Sent: 30 May 2013 18:59
To: openstack@lists.launchpad.net
Subject: [Openstack] [ceilometer] support for older versions of ceilometer

 

The ceilometer team has had a few requests for help with older versions of 
ceilometer or running the grizzly version of ceilometer
with older versions of other OpenStack components lately. We appreciate the 
level of interest in the project but, as much as we
would like to, unfortunately we are not always able to help everyone with these 
mixed configurations. During the early phases of
our development we tried to maintain compatibility with folsom, even well into 
the grizzly development cycle. We are no longer doing
that, however, and so to make clear what support we can offer, the ceilometer 
team has put together the statement below. It has been
added to our documentation, and we are posting here to make sure everyone has a 
chance to see it.

 

Regards,

Doug

 

 

The ceilometer team has limited capacity to provide support for older versions 
of the project. Because the project graduated from
incubation around the time of the grizzly release, that is the first version 
for which we will provide regular ongoing support
following the standard deprecation cycle for OpenStack [1]. The grizzly version 
of ceilometer  cannot be installed on the same
server with earlier versions of OpenStack because of conflicting package 
requirements, but is API compatible with the folsom release
if installed separately.

 

[1] https://wiki.openstack.org/wiki/StableBranch

 



smime.p7s
Description: S/MIME cryptographic signature
___
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] VM Issues on Grizzly Install on Ubuntu 12.04

[Darragh O'Reilly]

Hi Farhan and Rahul,

I think this issue would only be seen by people using the OVS plugin in a 
multinode setup with GRE tunnels and doing more than simple ping and ssh 
access. It seems some sites like github.com are either ignoring or not 
receiving the destination unreachable - need fragmentation ICMP to prevent 
DoS attackes.

Yes - cloud-init/metadata could run a script that sets the mtu.

An alternative workaound is to increase the mtu to 1546 on the interfaces on 
the network node and the computes nodes that have the GRE tunnel endpoint IPs. 
Then the instances can stay at their default 1500. This may be a more practical 
way as long as all the hardware between the endpoints can cope with this mtu 
size.

I can't say if this is a bug yet, but it needs to be documented.
  
Darragh.


 From: Farhan Patwa farhan.pa...@utsa.edu
To: Rahul Sharma rahulsharma...@gmail.com; Darragh O'Reilly 
dara2002-openst...@yahoo.com 
Cc: OpenStack Maillist openstack@lists.launchpad.net 
Sent: Thursday, 30 May 2013, 15:54
Subject: Re: [Openstack] VM Issues on Grizzly Install on Ubuntu 12.04
 


Hi Darragh,
Thanks a lot for your suggestion. It solved the issue for me also.
I also had the same issue on a Folsom install done by following the user guide:
http://docs.openstack.org/folsom/basic-install/content/index.html
At that time I thought it was an issue with my setup and so I decided to 
upgrade to Grizzly.


Wouldn't this be an issue that everyone doing a plain openstack install would 
face? Its hard to imagine why it has not been noticed before.


Is there a way I can add the changing of the MTU to the meta data so that it 
automatically applies to new Vms?


Thanks again Darragh for all your time and help.


-Farhan.

From: Rahul Sharma rahulsharma...@gmail.com
Date: Thursday, May 30, 2013 12:57 AM
To: Darragh O'Reilly dara2002-openst...@yahoo.com
Cc: Farhan Patwa farhan.pa...@utsa.edu, OpenStack Maillist 
openstack@lists.launchpad.net
Subject: Re: [Openstack] VM Issues on Grizzly Install on Ubuntu 12.04



Hi Darragh, 
 
Even I am facing the same issue of request getting timed out and even updates 
getting hanged up for very long time. I followed your step of reducing the MTU 
size from 1500 to 1454 and now everything works fine. I tried this on Ubuntu 
instances.
 
This seems to be an issue with the Grizzly release. I had already started 
email-thread earlier for this but was unable to find the root cause. Here is 
the link to it:-

https://lists.launchpad.net/openstack/msg23993.html


Thank you for your suggestion of reducing the MTU size as it solved the 
problem. You must file a bug for this so that this issue can be tracked.


Thanks and Regards
Rahul Sharma




On Thu, May 30, 2013 at 2:23 AM, Darragh O'Reilly 
dara2002-openst...@yahoo.com wrote:

Hi Farhan,

I was able to reproduce this with curl from the cirros 0.3.1 that supports 
ssl.

cirros$ curl -L github.com  # -L follow redirects

it just hangs and I get these ICMPs on the netnode's physical nic. 

20:33:10.811485 IP (tos 0xc0, ttl 63, id 13647, offset 0, flags [none], proto 
ICMP (1), length 576)
    192.168.101.2  204.232.175.90: ICMP 192.168.101.2 unreachable - need to 
frag (mtu 1454), length 556
IP (tos 0x0, ttl 51, id 54729, offset 0, flags [DF], proto TCP (6), length 
1500)
    204.232.175.90.443  192.168.101.2.41237: Flags [.], seq 1:1449, ack 225, 
win 7, options [nop,nop,TS val 4208725487 ecr 171322], length 1448

So I reduced the mtu from the default 1500 to 1454 on the instance and now 
'curl -L github.com' works

cirros$ sudo ip link set mtu 1454 dev eth0

Will need to look into this more. Maybe to do with the GRE tunnels 
(+~20bytes?) or iptables. Anyway try reducing the mtu for now.


Darragh.


- Original Message -
 From: Farhan Patwa farhan.pa...@utsa.edu

 To: Darragh O'Reilly dara2002-openst...@yahoo.com; OpenStack Maillist 
 openstack@lists.launchpad.net
 Cc:

 Sent: Wednesday, 29 May 2013, 18:14
 Subject: Re: [Openstack] VM Issues on Grizzly Install on Ubuntu 12.04

 Hi Darragh,
 Thank you soo Much! That was it! Now I am able to connect to the VM with
 no issues.

 But I am back to another network issue I had when I had Folsom installed
 on the same setup.
 I would really appreciate if you can provide any pointers here.


 I able to spawn VM get IP, set floating IP and now am trying to do some
 development within the VM.
 I am unable to connect to certain sites and ports:
 git clone https://github.com/openstack-dev/devstack.git - -- This just
 times out.

 ###
 #
 This is what works:
 Wget google.com
 Wget openstack.com
 ###
 #
 This is what hangs and times out:

 Wget yahoo.com
 Wget paypal.com
 Wget facebook.com
 Wget github.com
 ubuntu@fpatwa-1:~$ wget github.com
 --2013-05-10 19:08:19--  http://github.com/
 Resolving 

Re: [Openstack] [ceph-users] Openstack with Ceph, boot from volume

[Martin Mailand]

Hi Weiguo,

my answers are inline.

-martin

On 30.05.2013 21:20, w sun wrote:
 I would suggest on nova compute host (particularly if you have
 separate compute nodes),

 (1) make sure rbd ls -l -p  works and /etc/ceph/ceph.conf is
 readable by user nova!!
yes to both
 (2) make sure you can start up a regular ephemeral instance on the
 same nova node (ie, nova-compute is working correctly)
an ephemeral instance is working
 (3) if you are using cephx, make sure libvirt secret is set up correct
 per instruction at ceph.com
I do not use cephx
 (4) look at /var/lib/nova/instance/x/libvirt.xml and the
 disk file is pointing to the rbd volume
For an ephemeral instance the folder is create, for a volume bases
instance the folder is not created.

 (5) If all above look fine and you still couldn't perform nova boot
 with the volume,  you can try last thing to manually start up a kvm
 session with the volume similar to below. At least this will tell you
 if you qemu has the correct rbd enablement.

   /usr/bin/kvm -m 2048 -drive
 file=rbd:ceph-openstack-volumes/volume-3f964f79-febe-4251-b2ba-ac9423af419f,index=0,if=none,id=drive-virtio-disk0
 -boot c -net nic -net user -nographic  -vnc :1000 -device
 piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device
 virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1

If I start kvm by hand it is working.

 --weiguo

  Date: Thu, 30 May 2013 16:37:40 +0200
  From: mar...@tuxadero.com
  To: ceph-us...@ceph.com
  CC: openstack@lists.launchpad.net
  Subject: [ceph-users] Openstack with Ceph, boot from volume
 
  Hi Josh,
 
  I am trying to use ceph with openstack (grizzly), I have a multi
 host setup.
  I followed the instruction
 http://ceph.com/docs/master/rbd/rbd-openstack/.
  Glance is working without a problem.
  With cinder I can create and delete volumes without a problem.
 
  But I cannot boot from volumes.
  I doesn't matter if use horizon or the cli, the vm goes to the error
 state.
 
  From the nova-compute.log I get this.
 
  2013-05-30 16:08:45.224 ERROR nova.compute.manager
  [req-5679ddfe-79e3-4adb-b220-915f4a38b532
  8f9630095810427d865bc90c5ea04d35 43b2bbbf5daf4badb15d67d87ed2f3dc]
  [instance: 059589a3-72fc-444d-b1f0-ab1567c725fc] Instance failed block
  device setup
  .
  2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
  059589a3-72fc-444d-b1f0-ab1567c725fc] ConnectionError: [Errno 101]
  ENETUNREACH
 
  What tries nova to reach? How could I debug that further?
 
  Full Log included.
 
  -martin
 
  Log:
 
  ceph --version
  ceph version 0.61 (237f3f1e8d8c3b85666529860285dcdffdeda4c5)
 
  root@compute1:~# dpkg -l|grep -e ceph-common -e cinder
  ii ceph-common 0.61-1precise
  common utilities to mount and interact with a ceph storage
  cluster
  ii python-cinderclient 1:1.0.3-0ubuntu1~cloud0
  python bindings to the OpenStack Volume API
 
 
  nova-compute.log
 
  2013-05-30 16:08:45.224 ERROR nova.compute.manager
  [req-5679ddfe-79e3-4adb-b220-915f4a38b532
  8f9630095810427d865bc90c5ea04d35 43b2bbbf5daf4badb15d67d87ed2f3dc]
  [instance: 059589a3-72fc-444d-b1f0-ab1567c725fc] Instance failed block
  device setup
  2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
  059589a3-72fc-444d-b1f0-ab1567c725fc] Traceback (most recent call last):
  2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
  059589a3-72fc-444d-b1f0-ab1567c725fc] File
  /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 1071,
  in _prep_block_device
  2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
  059589a3-72fc-444d-b1f0-ab1567c725fc] return
  self._setup_block_device_mapping(context, instance, bdms)
  2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
  059589a3-72fc-444d-b1f0-ab1567c725fc] File
  /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 721, in
  _setup_block_device_mapping
  2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
  059589a3-72fc-444d-b1f0-ab1567c725fc] volume =
  self.volume_api.get(context, bdm['volume_id'])
  2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
  059589a3-72fc-444d-b1f0-ab1567c725fc] File
  /usr/lib/python2.7/dist-packages/nova/volume/cinder.py, line 193,
 in get
  2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
  059589a3-72fc-444d-b1f0-ab1567c725fc]
  self._reraise_translated_volume_exception(volume_id)
  2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
  059589a3-72fc-444d-b1f0-ab1567c725fc] File
  /usr/lib/python2.7/dist-packages/nova/volume/cinder.py, line 190,
 in get
  2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
  059589a3-72fc-444d-b1f0-ab1567c725fc] item =
  cinderclient(context).volumes.get(volume_id)
  2013-05-30 16:08:45.224 19614 TRACE nova.compute.manager [instance:
  059589a3-72fc-444d-b1f0-ab1567c725fc] File
  

[Openstack] Remote access to the windows virtual machine

[Narayanan, Krishnaprasad]

Hallo All,

Currently, I use VNC to access the windows virtual machine deployed in 
OpenStack. But this gives me a smaller view of the Windows GUI or Desktop. Is 
there any way from the Horizon GUI to have an enlarged view of the Windows 
Desktop?

Can I get any suggestions to connect to the windows virtual machine remotely 
apart from using VNC?

Thanks
Krishnaprasad
From: Narayanan, Krishnaprasad
Sent: Dienstag, 28. Mai 2013 02:42
To: 'JuanFra Rodriguez Cardoso'
Cc: openstack@lists.launchpad.net
Subject: RE: [Openstack] Windows Image 2008 in OpenStack

Hi JuanFra,

Thanks for the suggestion regarding the usage of cloudinit for windows 
instances.

For all Stackers - I found this URIhttp://www.cloudbase.it/ws2012/ useful 
where there is a Windows Server 2012 Evaluation image available for download 
and it can be directly deployed to OpenStack. I was able to download and deploy 
the image in our ESSEX cloud and create a VM successfully out of the image.

Thanks
Krishnaprasad
From: JuanFra Rodriguez Cardoso [mailto:juanfra.rodriguez.card...@gmail.com]
Sent: Montag, 27. Mai 2013 23:41
To: Narayanan, Krishnaprasad
Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
Subject: Re: [Openstack] Windows Image 2008 in OpenStack

I think a great tool would be Cloudbase's cloud-init for windows instances:

http://www.cloudbase.it/cloud-init-for-windows-instances/
Regards,
---
JuanFra

2013/5/27 Narayanan, Krishnaprasad 
naray...@uni-mainz.demailto:naray...@uni-mainz.de
Hallo All,

Can somebody guide me to create a virtual machine using Windows 2008 image?

Thanks
Krishnaprasad

___
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

Re: [Openstack] Openstack with Ceph, boot from volume

[Martin Mailand]

Hi Josh,

On 30.05.2013 21:17, Josh Durgin wrote:
 It's trying to talk to the cinder api, and failing to connect at all.
 Perhaps there's a firewall preventing that on the compute host, or
 it's trying to use the wrong endpoint for cinder (check the keystone
 service and endpoint tables for the volume service).

the keystone endpoint looks like this:

| dd21ed74a9ac4744b2ea498609f0a86e | RegionOne |
http://xxx.xxx.240.10:8776/v1/$(tenant_id)s |
http://192.168.192.2:8776/v1/$(tenant_id)s |
http://192.168.192.2:8776/v1/$(tenant_id)s |
5ad684c5a0154c13b54283b01744181b

where 192.168.192.2 is the IP from the controller node.

And from the compute node a telnet 192.168.192.2 8776 is working.

-martin

___
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] [ceilometer] support for older versions of ceilometer

[Doug Hellmann]

From what I understand, it is unusual to support mixing components from
different releases like that. Am I wrong?

Doug


On Thu, May 30, 2013 at 3:29 PM, Tim Bell tim.b...@cern.ch wrote:

 ** **

 Doug,

 ** **

 Can you advise on what the plan/policy will be for Havana ?

 ** **

 **-  **Will I be able to run Havana core components such as Nova
 with Grizzly ceilometer ?

 **-  **Will I be able to run Havana ceilometer with Grizzly core
 components (with reduced functionality compared to the Havana core
 components) ?

 ** **

 Tim

 ** **

 *From:* Openstack [mailto:openstack-bounces+tim.bell=
 cern...@lists.launchpad.net] *On Behalf Of *Doug Hellmann
 *Sent:* 30 May 2013 18:59
 *To:* openstack@lists.launchpad.net
 *Subject:* [Openstack] [ceilometer] support for older versions of
 ceilometer

 ** **

 The ceilometer team has had a few requests for help with older versions of
 ceilometer or running the grizzly version of ceilometer with older versions
 of other OpenStack components lately. We appreciate the level of interest
 in the project but, as much as we would like to, unfortunately we are not
 always able to help everyone with these mixed configurations. During the
 early phases of our development we tried to maintain compatibility with
 folsom, even well into the grizzly development cycle. We are no longer
 doing that, however, and so to make clear what support we can offer, the
 ceilometer team has put together the statement below. It has been added to
 our documentation, and we are posting here to make sure everyone has a
 chance to see it.

 ** **

 Regards,

 Doug

 ** **

 ** **

 The ceilometer team has limited capacity to provide support for older
 versions of the project. Because the project graduated from incubation
 around the time of the grizzly release, that is the first version for which
 we will provide regular ongoing support following the standard deprecation
 cycle for OpenStack [1]. The grizzly version of ceilometer  cannot be
 installed on the same server with earlier versions of OpenStack because of
 conflicting package requirements, but is API compatible with the folsom
 release if installed separately.

 ** **

 [1] https://wiki.openstack.org/wiki/StableBranch

 ** **

___
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] [ceph-users] Openstack with Ceph, boot from volume

[Martin Mailand]

Hi Josh,

I found the problem, nova-compute tries to connect to the publicurl
(xxx.xxx.240.10) of the keytone endpoints, this ip is not reachable from
the management network.
I thought the internalurl is the one, which is used for the internal
communication of the openstack components and the publicurl is the ip
for customer of the cluster?
Am I wrong here?

-martin

On 30.05.2013 22:22, Martin Mailand wrote:
 Hi Josh,
 
 On 30.05.2013 21:17, Josh Durgin wrote:
 It's trying to talk to the cinder api, and failing to connect at all.
 Perhaps there's a firewall preventing that on the compute host, or
 it's trying to use the wrong endpoint for cinder (check the keystone
 service and endpoint tables for the volume service).
 
 the keystone endpoint looks like this:
 
 | dd21ed74a9ac4744b2ea498609f0a86e | RegionOne |
 http://xxx.xxx.240.10:8776/v1/$(tenant_id)s |
 http://192.168.192.2:8776/v1/$(tenant_id)s |
 http://192.168.192.2:8776/v1/$(tenant_id)s |
 5ad684c5a0154c13b54283b01744181b
 
 where 192.168.192.2 is the IP from the controller node.
 
 And from the compute node a telnet 192.168.192.2 8776 is working.
 
 -martin
 ___
 ceph-users mailing list
 ceph-us...@lists.ceph.com
 http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 

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

Re: [Openstack] [ceph-users] Openstack with Ceph, boot from volume

[Josh Durgin]

On 05/30/2013 01:50 PM, Martin Mailand wrote:

Hi Josh,

I found the problem, nova-compute tries to connect to the publicurl
(xxx.xxx.240.10) of the keytone endpoints, this ip is not reachable from
the management network.
I thought the internalurl is the one, which is used for the internal
communication of the openstack components and the publicurl is the ip
for customer of the cluster?
Am I wrong here?


I'd expect that too, but it's determined in nova by the 
cinder_catalog_info option, which defaults to volume:cinder:publicURL.


You can also override it explicitly with
cinder_endpoint_template=http://192.168.192.2:8776/v1/$(tenant_id)s
in your nova.conf.

Josh


-martin

On 30.05.2013 22:22, Martin Mailand wrote:

Hi Josh,

On 30.05.2013 21:17, Josh Durgin wrote:

It's trying to talk to the cinder api, and failing to connect at all.
Perhaps there's a firewall preventing that on the compute host, or
it's trying to use the wrong endpoint for cinder (check the keystone
service and endpoint tables for the volume service).


the keystone endpoint looks like this:

| dd21ed74a9ac4744b2ea498609f0a86e | RegionOne |
http://xxx.xxx.240.10:8776/v1/$(tenant_id)s |
http://192.168.192.2:8776/v1/$(tenant_id)s |
http://192.168.192.2:8776/v1/$(tenant_id)s |
5ad684c5a0154c13b54283b01744181b

where 192.168.192.2 is the IP from the controller node.

And from the compute node a telnet 192.168.192.2 8776 is working.

-martin
___
ceph-users mailing list
ceph-us...@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com




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

Re: [Openstack] Remote access to the windows virtual machine

[Brian Schott]

For windows, you could add TCP port 3389 to your security group and enable 
remote desktop access in windows.  The VNC console access in Horizon is really 
intended for administrative/management access rather than production usage.

Brian

-
Brian Schott, CTO
Nimbis Services, Inc.
brian.sch...@nimbisservices.com
ph: 443-274-6064  fx: 443-274-6060



On May 30, 2013, at 3:58 PM, Narayanan, Krishnaprasad naray...@uni-mainz.de 
wrote:

 Hallo All,
  
 Currently, I use VNC to access the windows virtual machine deployed in 
 OpenStack. But this gives me a smaller view of the Windows GUI or Desktop. Is 
 there any way from the Horizon GUI to have an enlarged view of the Windows 
 Desktop?
  
 Can I get any suggestions to connect to the windows virtual machine remotely 
 apart from using VNC?
  
 Thanks
 Krishnaprasad
 From: Narayanan, Krishnaprasad 
 Sent: Dienstag, 28. Mai 2013 02:42
 To: 'JuanFra Rodriguez Cardoso'
 Cc: openstack@lists.launchpad.net
 Subject: RE: [Openstack] Windows Image 2008 in OpenStack
  
 Hi JuanFra,
  
 Thanks for the suggestion regarding the usage of cloudinit for windows 
 instances.
  
 For all Stackers - I found this URI useful where there is a Windows Server 
 2012 Evaluation image available for download and it can be directly deployed 
 to OpenStack. I was able to download and deploy the image in our ESSEX cloud 
 and create a VM successfully out of the image.
  
 Thanks
 Krishnaprasad
 From: JuanFra Rodriguez Cardoso [mailto:juanfra.rodriguez.card...@gmail.com] 
 Sent: Montag, 27. Mai 2013 23:41
 To: Narayanan, Krishnaprasad
 Cc: openstack@lists.launchpad.net
 Subject: Re: [Openstack] Windows Image 2008 in OpenStack
  
 I think a great tool would be Cloudbase's cloud-init for windows instances:
 
 http://www.cloudbase.it/cloud-init-for-windows-instances/
 
 Regards,
 ---
 JuanFra
  
 
 2013/5/27 Narayanan, Krishnaprasad naray...@uni-mainz.de
 Hallo All,
  
 Can somebody guide me to create a virtual machine using Windows 2008 image?
  
 Thanks
 Krishnaprasad
 
 ___
 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] [ceilometer] support for older versions of ceilometer

[Tim Bell]

 

The difficulties of upgrading OpenStack while running production services was 
one of the major feedbacks from the user survey at
Portland. Core components are including N/N+1 upgrades into their plans for 
Havana so big bang (and high risk of extended downtime)
upgrades are no longer the default processes.

 

As a component matures through incubation to core, we also need to have these 
operational requirements covered. Upgrading 100s of
hypervisors and their controllers require staged upgrades.

 

I hope that ceilometer can also include this within the Havana timeframe as it 
becomes a key component of production, large scale
clouds.

 

Tim

 

From: Doug Hellmann [mailto:doug.hellm...@dreamhost.com] 
Sent: 30 May 2013 22:35
To: Tim Bell
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] [ceilometer] support for older versions of ceilometer

 

From what I understand, it is unusual to support mixing components from 
different releases like that. Am I wrong?

 

Doug

 

On Thu, May 30, 2013 at 3:29 PM, Tim Bell tim.b...@cern.ch 
mailto:tim.b...@cern.ch  wrote:

 

Doug,

 

Can you advise on what the plan/policy will be for Havana ?

 

-  Will I be able to run Havana core components such as Nova with 
Grizzly ceilometer ?

-  Will I be able to run Havana ceilometer with Grizzly core components 
(with reduced functionality compared to the Havana
core components) ?

 

Tim

 

From: Openstack [mailto:openstack-bounces+tim.bell 
mailto:openstack-bounces%2Btim.bell =cern...@lists.launchpad.net
mailto:cern...@lists.launchpad.net ] On Behalf Of Doug Hellmann
Sent: 30 May 2013 18:59
To: openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net 
Subject: [Openstack] [ceilometer] support for older versions of ceilometer

 

The ceilometer team has had a few requests for help with older versions of 
ceilometer or running the grizzly version of ceilometer
with older versions of other OpenStack components lately. We appreciate the 
level of interest in the project but, as much as we
would like to, unfortunately we are not always able to help everyone with these 
mixed configurations. During the early phases of
our development we tried to maintain compatibility with folsom, even well into 
the grizzly development cycle. We are no longer doing
that, however, and so to make clear what support we can offer, the ceilometer 
team has put together the statement below. It has been
added to our documentation, and we are posting here to make sure everyone has a 
chance to see it.

 

Regards,

Doug

 

 

The ceilometer team has limited capacity to provide support for older versions 
of the project. Because the project graduated from
incubation around the time of the grizzly release, that is the first version 
for which we will provide regular ongoing support
following the standard deprecation cycle for OpenStack [1]. The grizzly version 
of ceilometer  cannot be installed on the same
server with earlier versions of OpenStack because of conflicting package 
requirements, but is API compatible with the folsom release
if installed separately.

 

[1] https://wiki.openstack.org/wiki/StableBranch

 

 



smime.p7s
Description: S/MIME cryptographic signature
___
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] [ceph-users] Openstack with Ceph, boot from volume

[Martin Mailand]

Hi Josh,

that's working.

I have to more things.
1. The volume_driver=cinder.volume.driver.RBDDriver is deprecated,
update your configuration to the new path. What is the new path?

2. I have in the glance-api.conf show_image_direct_url=True, but the
volumes are not clones of the original which are in the images pool.

That's what I did.

root@controller:~/vm_images# !1228
glance add name=Precise Server is_public=true container_format=ovf
disk_format=raw  ./precise-server-cloudimg-amd64-disk1.raw
Added new image with ID: 6fbf4dfd-adce-470b-87fe-9b6ddb3993c8
root@controller:~/vm_images# rbd -p images -l ls
NAMESIZE PARENT FMT PROT LOCK
6fbf4dfd-adce-470b-87fe-9b6ddb3993c8   2048M  2
6fbf4dfd-adce-470b-87fe-9b6ddb3993c8@snap  2048M  2 yes
root@controller:~/vm_images# cinder create --image-id
6fbf4dfd-adce-470b-87fe-9b6ddb3993c8 --display-name volcli1
10+-+--+
|   Property  |Value |
+-+--+
| attachments |  []  |
|  availability_zone  | nova |
|   bootable  |false |
|  created_at |  2013-05-30T21:08:16.506094  |
| display_description | None |
| display_name|   volcli1|
|  id | 34838911-6613-4140-93e0-e1565054a2d3 |
|   image_id  | 6fbf4dfd-adce-470b-87fe-9b6ddb3993c8 |
|   metadata  |  {}  |
| size|  10  |
| snapshot_id | None |
| source_volid| None |
|status   |   creating   |
| volume_type | None |
+-+--+
root@controller:~/vm_images# cinder list
+--+-+--+--+-+--+-+
|  ID  |Status   | Display Name |
Size | Volume Type | Bootable | Attached to |
+--+-+--+--+-+--+-+
| 34838911-6613-4140-93e0-e1565054a2d3 | downloading |   volcli1|
10  | None|  false   | |
+--+-+--+--+-+--+-+
root@controller:~/vm_images# rbd -p volumes -l ls
NAME   SIZE PARENT FMT PROT LOCK
volume-34838911-6613-4140-93e0-e1565054a2d3  10240M  2

root@controller:~/vm_images#

-martin

On 30.05.2013 22:56, Josh Durgin wrote:
 On 05/30/2013 01:50 PM, Martin Mailand wrote:
 Hi Josh,

 I found the problem, nova-compute tries to connect to the publicurl
 (xxx.xxx.240.10) of the keytone endpoints, this ip is not reachable from
 the management network.
 I thought the internalurl is the one, which is used for the internal
 communication of the openstack components and the publicurl is the ip
 for customer of the cluster?
 Am I wrong here?
 
 I'd expect that too, but it's determined in nova by the
 cinder_catalog_info option, which defaults to volume:cinder:publicURL.
 
 You can also override it explicitly with
 cinder_endpoint_template=http://192.168.192.2:8776/v1/$(tenant_id)s
 in your nova.conf.
 
 Josh
 
 -martin

 On 30.05.2013 22:22, Martin Mailand wrote:
 Hi Josh,

 On 30.05.2013 21:17, Josh Durgin wrote:
 It's trying to talk to the cinder api, and failing to connect at all.
 Perhaps there's a firewall preventing that on the compute host, or
 it's trying to use the wrong endpoint for cinder (check the keystone
 service and endpoint tables for the volume service).

 the keystone endpoint looks like this:

 | dd21ed74a9ac4744b2ea498609f0a86e | RegionOne |
 http://xxx.xxx.240.10:8776/v1/$(tenant_id)s |
 http://192.168.192.2:8776/v1/$(tenant_id)s |
 http://192.168.192.2:8776/v1/$(tenant_id)s |
 5ad684c5a0154c13b54283b01744181b

 where 192.168.192.2 is the IP from the controller node.

 And from the compute node a telnet 192.168.192.2 8776 is working.

 -martin
 ___
 ceph-users mailing list
 ceph-us...@lists.ceph.com
 http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

 

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

Re: [Openstack] [ceph-users] Openstack with Ceph, boot from volume

[Josh Durgin]

On 05/30/2013 02:18 PM, Martin Mailand wrote:

Hi Josh,

that's working.

I have to more things.
1. The volume_driver=cinder.volume.driver.RBDDriver is deprecated,
update your configuration to the new path. What is the new path?


cinder.volume.drivers.rbd.RBDDriver


2. I have in the glance-api.conf show_image_direct_url=True, but the
volumes are not clones of the original which are in the images pool.


Set glance_api_version=2 in cinder.conf. The default was changed in
Grizzly.


That's what I did.

root@controller:~/vm_images# !1228
glance add name=Precise Server is_public=true container_format=ovf
disk_format=raw  ./precise-server-cloudimg-amd64-disk1.raw
Added new image with ID: 6fbf4dfd-adce-470b-87fe-9b6ddb3993c8
root@controller:~/vm_images# rbd -p images -l ls
NAMESIZE PARENT FMT PROT LOCK
6fbf4dfd-adce-470b-87fe-9b6ddb3993c8   2048M  2
6fbf4dfd-adce-470b-87fe-9b6ddb3993c8@snap  2048M  2 yes
root@controller:~/vm_images# cinder create --image-id
6fbf4dfd-adce-470b-87fe-9b6ddb3993c8 --display-name volcli1
10+-+--+
|   Property  |Value |
+-+--+
| attachments |  []  |
|  availability_zone  | nova |
|   bootable  |false |
|  created_at |  2013-05-30T21:08:16.506094  |
| display_description | None |
| display_name|   volcli1|
|  id | 34838911-6613-4140-93e0-e1565054a2d3 |
|   image_id  | 6fbf4dfd-adce-470b-87fe-9b6ddb3993c8 |
|   metadata  |  {}  |
| size|  10  |
| snapshot_id | None |
| source_volid| None |
|status   |   creating   |
| volume_type | None |
+-+--+
root@controller:~/vm_images# cinder list
+--+-+--+--+-+--+-+
|  ID  |Status   | Display Name |
Size | Volume Type | Bootable | Attached to |
+--+-+--+--+-+--+-+
| 34838911-6613-4140-93e0-e1565054a2d3 | downloading |   volcli1|
10  | None|  false   | |
+--+-+--+--+-+--+-+
root@controller:~/vm_images# rbd -p volumes -l ls
NAME   SIZE PARENT FMT PROT LOCK
volume-34838911-6613-4140-93e0-e1565054a2d3  10240M  2

root@controller:~/vm_images#

-martin

On 30.05.2013 22:56, Josh Durgin wrote:

On 05/30/2013 01:50 PM, Martin Mailand wrote:

Hi Josh,

I found the problem, nova-compute tries to connect to the publicurl
(xxx.xxx.240.10) of the keytone endpoints, this ip is not reachable from
the management network.
I thought the internalurl is the one, which is used for the internal
communication of the openstack components and the publicurl is the ip
for customer of the cluster?
Am I wrong here?


I'd expect that too, but it's determined in nova by the
cinder_catalog_info option, which defaults to volume:cinder:publicURL.

You can also override it explicitly with
cinder_endpoint_template=http://192.168.192.2:8776/v1/$(tenant_id)s
in your nova.conf.

Josh


-martin

On 30.05.2013 22:22, Martin Mailand wrote:

Hi Josh,

On 30.05.2013 21:17, Josh Durgin wrote:

It's trying to talk to the cinder api, and failing to connect at all.
Perhaps there's a firewall preventing that on the compute host, or
it's trying to use the wrong endpoint for cinder (check the keystone
service and endpoint tables for the volume service).


the keystone endpoint looks like this:

| dd21ed74a9ac4744b2ea498609f0a86e | RegionOne |
http://xxx.xxx.240.10:8776/v1/$(tenant_id)s |
http://192.168.192.2:8776/v1/$(tenant_id)s |
http://192.168.192.2:8776/v1/$(tenant_id)s |
5ad684c5a0154c13b54283b01744181b

where 192.168.192.2 is the IP from the controller node.

And from the compute node a telnet 192.168.192.2 8776 is working.

-martin
___
ceph-users mailing list
ceph-us...@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com






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

Re: [Openstack] Remote access to the windows virtual machine

[Staicu Gabriel]

Hi,

From the openstack documentation: 
(http://docs.openstack.org/folsom/openstack-compute/install/apt/content/faq-about-vnc.html)

A: These values are hard-coded in a Django HTML template. To alter them, you 
must edit the template file _detail_vnc.html. The location of this file will 
vary based on Linux distribution. On Ubuntu 12.04, the file can be found 
at/usr/share/pyshared/horizon/dashboards/nova/templates/nova/instances_and_volumes/instances/_detail_vnc.html.
Modify the width and height parameters:
iframe src={{ vnc_url }} width=720 height=430/iframe

Regards,
Gabriel


 From: Brian Schott brian.sch...@nimbisservices.com
To: Narayanan, Krishnaprasad naray...@uni-mainz.de 
Cc: openstack@lists.launchpad.net openstack@lists.launchpad.net 
Sent: Friday, May 31, 2013 12:02 AM
Subject: Re: [Openstack] Remote access to the windows virtual machine
 


For windows, you could add TCP port 3389 to your security group and enable 
remote desktop access in windows.  The VNC console access in Horizon is really 
intended for administrative/management access rather than production usage.

Brian



-
Brian Schott, CTO
Nimbis Services, Inc.
brian.sch...@nimbisservices.com
ph: 443-274-6064  fx: 443-274-6060



On May 30, 2013, at 3:58 PM, Narayanan, Krishnaprasad naray...@uni-mainz.de 
wrote:

Hallo All,
 
Currently, I use VNC to access the windows virtual machine deployed in 
OpenStack. But this gives me a smaller view of the Windows GUI or Desktop. Is 
there any way from the Horizon GUI to have an enlarged view of the Windows 
Desktop?
 
Can I get any suggestions to connect to the windows virtual machine remotely 
apart from using VNC?
 
Thanks
Krishnaprasad
From: Narayanan, Krishnaprasad 
Sent: Dienstag, 28. Mai 2013 02:42
To: 'JuanFra Rodriguez Cardoso'
Cc: openstack@lists.launchpad.net
Subject: RE: [Openstack] Windows Image 2008 in OpenStack
 
Hi JuanFra,
 
Thanks for the suggestion regarding the usage of cloudinit for windows 
instances.
 
For all Stackers - I found this URI useful where there is a Windows Server 
2012 Evaluation image available for download and it can be directly deployed 
to OpenStack. I was able to download and deploy the image in our ESSEX cloud 
and create a VM successfully out of the image.
 
Thanks
Krishnaprasad
From: JuanFra Rodriguez Cardoso [mailto:juanfra.rodriguez.card...@gmail.com] 
Sent: Montag, 27. Mai 2013 23:41
To: Narayanan, Krishnaprasad
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] Windows Image 2008 in OpenStack
 
I think a great tool would be Cloudbase's cloud-init for windows instances:

http://www.cloudbase.it/cloud-init-for-windows-instances/
Regards,

---
JuanFra
 
2013/5/27 Narayanan, Krishnaprasad naray...@uni-mainz.de
Hallo All,
 
Can somebody guide me to create a virtual machine using Windows 2008 image?
 
Thanks
Krishnaprasad

___
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] [ceph-users] Openstack with Ceph, boot from volume

[Martin Mailand]

Hi Josh,

now everything is working, many thanks for your help, great work.

-martin

On 30.05.2013 23:24, Josh Durgin wrote:
 I have to more things.
 1. The volume_driver=cinder.volume.driver.RBDDriver is deprecated,
 update your configuration to the new path. What is the new path?
 
 cinder.volume.drivers.rbd.RBDDriver
 
 2. I have in the glance-api.conf show_image_direct_url=True, but the
 volumes are not clones of the original which are in the images pool.
 
 Set glance_api_version=2 in cinder.conf. The default was changed in
 Grizzly.

___
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] [ceph-users] Openstack with Ceph, boot from volume

[Josh Durgin]

On 05/30/2013 02:50 PM, Martin Mailand wrote:

Hi Josh,

now everything is working, many thanks for your help, great work.


Great! I added those settings to 
http://ceph.com/docs/master/rbd/rbd-openstack/ so it's easier to figure 
out in the future.



-martin

On 30.05.2013 23:24, Josh Durgin wrote:

I have to more things.
1. The volume_driver=cinder.volume.driver.RBDDriver is deprecated,
update your configuration to the new path. What is the new path?


cinder.volume.drivers.rbd.RBDDriver


2. I have in the glance-api.conf show_image_direct_url=True, but the
volumes are not clones of the original which are in the images pool.


Set glance_api_version=2 in cinder.conf. The default was changed in
Grizzly.



___
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] Remote access to the windows virtual machine

[Narayanan, Krishnaprasad]

Hi Gabriel,

The path to the file was correct and I had changed it to 1024 * 768 and I could 
see the change in the VNC window size. Thanks for your suggestion and it is 
working.

Regards,
Krishnaprasad
From: Staicu Gabriel [mailto:gabriel_sta...@yahoo.com]
Sent: Donnerstag, 30. Mai 2013 23:28
To: Brian Schott; Narayanan, Krishnaprasad
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] Remote access to the windows virtual machine

Hi,

From the openstack documentation: 
(http://docs.openstack.org/folsom/openstack-compute/install/apt/content/faq-about-vnc.html)

A: These values are hard-coded in a Django HTML template. To alter them, you 
must edit the template file _detail_vnc.html. The location of this file will 
vary based on Linux distribution. On Ubuntu 12.04, the file can be found 
at/usr/share/pyshared/horizon/dashboards/nova/templates/nova/instances_and_volumes/instances/_detail_vnc.html.
Modify the width and height parameters:

 iframe src={{ vnc_url }} width=720 height=430/iframe

Regards,
Gabriel

From: Brian Schott 
brian.sch...@nimbisservices.commailto:brian.sch...@nimbisservices.com
To: Narayanan, Krishnaprasad 
naray...@uni-mainz.demailto:naray...@uni-mainz.de
Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net 
openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
Sent: Friday, May 31, 2013 12:02 AM
Subject: Re: [Openstack] Remote access to the windows virtual machine

For windows, you could add TCP port 3389 to your security group and enable 
remote desktop access in windows.  The VNC console access in Horizon is really 
intended for administrative/management access rather than production usage.

Brian

-
Brian Schott, CTO
Nimbis Services, Inc.
brian.sch...@nimbisservices.commailto:brian.sch...@nimbisservices.com
ph: 443-274-6064  fx: 443-274-6060



On May 30, 2013, at 3:58 PM, Narayanan, Krishnaprasad 
naray...@uni-mainz.demailto:naray...@uni-mainz.de wrote:


Hallo All,

Currently, I use VNC to access the windows virtual machine deployed in 
OpenStack. But this gives me a smaller view of the Windows GUI or Desktop. Is 
there any way from the Horizon GUI to have an enlarged view of the Windows 
Desktop?

Can I get any suggestions to connect to the windows virtual machine remotely 
apart from using VNC?

Thanks
Krishnaprasad
From: Narayanan, Krishnaprasad
Sent: Dienstag, 28. Mai 2013 02:42
To: 'JuanFra Rodriguez Cardoso'
Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
Subject: RE: [Openstack] Windows Image 2008 in OpenStack

Hi JuanFra,

Thanks for the suggestion regarding the usage of cloudinit for windows 
instances.

For all Stackers - I found this URIhttp://www.cloudbase.it/ws2012/ useful 
where there is a Windows Server 2012 Evaluation image available for download 
and it can be directly deployed to OpenStack. I was able to download and deploy 
the image in our ESSEX cloud and create a VM successfully out of the image.

Thanks
Krishnaprasad
From: JuanFra Rodriguez Cardoso [mailto:juanfra.rodriguez.card...@gmail.com]
Sent: Montag, 27. Mai 2013 23:41
To: Narayanan, Krishnaprasad
Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
Subject: Re: [Openstack] Windows Image 2008 in OpenStack

I think a great tool would be Cloudbase's cloud-init for windows instances:

http://www.cloudbase.it/cloud-init-for-windows-instances/
Regards,
---
JuanFra

2013/5/27 Narayanan, Krishnaprasad 
naray...@uni-mainz.demailto:naray...@uni-mainz.de
Hallo All,

Can somebody guide me to create a virtual machine using Windows 2008 image?

Thanks
Krishnaprasad

___
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.netmailto:openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~openstack
Post to: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
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] Remote access to the windows virtual machine

[Narayanan, Krishnaprasad]

Hi Brian,

The Windows server 2012 OpenStack edition comes with TCP port 3389 enabled. I 
don't think we should specify it in the security groups as this is already 
taken care in the Windows firewall.

Thanks
Krishnaprasad
From: Brian Schott [mailto:brian.sch...@nimbisservices.com]
Sent: Donnerstag, 30. Mai 2013 23:03
To: Narayanan, Krishnaprasad
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] Remote access to the windows virtual machine

For windows, you could add TCP port 3389 to your security group and enable 
remote desktop access in windows.  The VNC console access in Horizon is really 
intended for administrative/management access rather than production usage.

Brian

-
Brian Schott, CTO
Nimbis Services, Inc.
brian.sch...@nimbisservices.commailto:brian.sch...@nimbisservices.com
ph: 443-274-6064  fx: 443-274-6060



On May 30, 2013, at 3:58 PM, Narayanan, Krishnaprasad 
naray...@uni-mainz.demailto:naray...@uni-mainz.de wrote:


Hallo All,

Currently, I use VNC to access the windows virtual machine deployed in 
OpenStack. But this gives me a smaller view of the Windows GUI or Desktop. Is 
there any way from the Horizon GUI to have an enlarged view of the Windows 
Desktop?

Can I get any suggestions to connect to the windows virtual machine remotely 
apart from using VNC?

Thanks
Krishnaprasad
From: Narayanan, Krishnaprasad
Sent: Dienstag, 28. Mai 2013 02:42
To: 'JuanFra Rodriguez Cardoso'
Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
Subject: RE: [Openstack] Windows Image 2008 in OpenStack

Hi JuanFra,

Thanks for the suggestion regarding the usage of cloudinit for windows 
instances.

For all Stackers - I found this URIhttp://www.cloudbase.it/ws2012/ useful 
where there is a Windows Server 2012 Evaluation image available for download 
and it can be directly deployed to OpenStack. I was able to download and deploy 
the image in our ESSEX cloud and create a VM successfully out of the image.

Thanks
Krishnaprasad
From: JuanFra Rodriguez Cardoso [mailto:juanfra.rodriguez.card...@gmail.com]
Sent: Montag, 27. Mai 2013 23:41
To: Narayanan, Krishnaprasad
Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
Subject: Re: [Openstack] Windows Image 2008 in OpenStack

I think a great tool would be Cloudbase's cloud-init for windows instances:

http://www.cloudbase.it/cloud-init-for-windows-instances/
Regards,
---
JuanFra

2013/5/27 Narayanan, Krishnaprasad 
naray...@uni-mainz.demailto:naray...@uni-mainz.de
Hallo All,

Can somebody guide me to create a virtual machine using Windows 2008 image?

Thanks
Krishnaprasad

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

Re: [Openstack] [grizzly]Problems of qpid as rpcbackend

[minmin ren]

Hi Ray,
Thanks for your reply.
try  except  change to line 386 only solve cinder-scheduler or
nova-compute service which is the similar implementation stop raise
exception.
However,  all cinder-volume queue be removed when one of
multi-cinder-volume service stop. It is another problem.
I use pdb module to trace two different sevice stop(cinder-scheduler and
cinder-volume).
I describe two different implemention stop service
cinder-scheduler catch the signal to stop will to call _launcher.stop()
cinder/service.py line 612
_launcher.stop() will kill all service thread which run service.start and
service.wait .
After thread killed, I found that connection.session.recievers is [], that
means all consumer released. I'm not sure connection closed or not.
I found that the method kill() of class service not be called.

cinder-volume launch two processes,  service run in child process
(service.py line 227) and parent process watch the status of child.
When parent process catch to stop signal, it send the stop signal to child
process.
child process will catch signal and call service.stop (service.py  line 239)

And I use pdb to trace stop steps. I found that
connection.session.receivers is not [] and including three
receivers(cinder-volume, cinder-volume.node1, cinder-volume_fanout)
qpid will remove receivers of session, then MessageCancel and QueueDelete
will set to qpidd.
I think QueueDelete told the qpidd to delete all cinder-volume queues.






2013/5/30 Ray Pekowski pekow...@gmail.com

 I am not familiar with impl_qpid,py, but am familiar with amqp.py and have
 had problems around rpc_amqp.cleanup() the Pool.empty() method it calls.
 It was a totally different problem, but I decided to take a look at your
 problem.  I noticed that in impl_qpid.py the only other place a
 connection.close() is done is surrounded by this code:

 # Close the session if necessary
 if self.connection.opened():
 try:
 self.connection.close()
 except qpid_exceptions.ConnectionError:
 pass

 I suggest you wrap the close at line 386 of impl_qpid.py with the same
 code and your problem will be fixed.  Here is the line identified from your
 call stack:

   File /usr/lib/python2.6/site-
 packages/cinder/openstack/common/rpc/impl_qpid.py, line 386, in close
 self.connection.close()

 If that works, open a bug report.

 Good catch

 Ray

___
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] Remote access to the windows virtual machine

[Brian Schott]

I don't think the default security groups (visible in Horizon or nova 
secgroup-list-rules) has 3389 open, unless maybe you are running Windows Server 
2012 and Hyper-V as the hypervisor?  There are 2 layers of firewalls.  The 
OpenStack security groups outside the windows guest and the windows firewall 
inside the guest.  Both have to allow those packets to pass.
—
Sent from Mailbox for iPad

On Thu, May 30, 2013 at 7:53 PM, Narayanan, Krishnaprasad
naray...@uni-mainz.de wrote:

 Hi Brian,
 The Windows server 2012 OpenStack edition comes with TCP port 3389 enabled. I 
 don't think we should specify it in the security groups as this is already 
 taken care in the Windows firewall.
 Thanks
 Krishnaprasad
 From: Brian Schott [mailto:brian.sch...@nimbisservices.com]
 Sent: Donnerstag, 30. Mai 2013 23:03
 To: Narayanan, Krishnaprasad
 Cc: openstack@lists.launchpad.net
 Subject: Re: [Openstack] Remote access to the windows virtual machine
 For windows, you could add TCP port 3389 to your security group and enable 
 remote desktop access in windows.  The VNC console access in Horizon is 
 really intended for administrative/management access rather than production 
 usage.
 Brian
 -
 Brian Schott, CTO
 Nimbis Services, Inc.
 brian.sch...@nimbisservices.commailto:brian.sch...@nimbisservices.com
 ph: 443-274-6064  fx: 443-274-6060
 On May 30, 2013, at 3:58 PM, Narayanan, Krishnaprasad 
 naray...@uni-mainz.demailto:naray...@uni-mainz.de wrote:
 Hallo All,
 Currently, I use VNC to access the windows virtual machine deployed in 
 OpenStack. But this gives me a smaller view of the Windows GUI or Desktop. Is 
 there any way from the Horizon GUI to have an enlarged view of the Windows 
 Desktop?
 Can I get any suggestions to connect to the windows virtual machine remotely 
 apart from using VNC?
 Thanks
 Krishnaprasad
 From: Narayanan, Krishnaprasad
 Sent: Dienstag, 28. Mai 2013 02:42
 To: 'JuanFra Rodriguez Cardoso'
 Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
 Subject: RE: [Openstack] Windows Image 2008 in OpenStack
 Hi JuanFra,
 Thanks for the suggestion regarding the usage of cloudinit for windows 
 instances.
 For all Stackers - I found this URIhttp://www.cloudbase.it/ws2012/ useful 
 where there is a Windows Server 2012 Evaluation image available for download 
 and it can be directly deployed to OpenStack. I was able to download and 
 deploy the image in our ESSEX cloud and create a VM successfully out of the 
 image.
 Thanks
 Krishnaprasad
 From: JuanFra Rodriguez Cardoso [mailto:juanfra.rodriguez.card...@gmail.com]
 Sent: Montag, 27. Mai 2013 23:41
 To: Narayanan, Krishnaprasad
 Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
 Subject: Re: [Openstack] Windows Image 2008 in OpenStack
 I think a great tool would be Cloudbase's cloud-init for windows instances:
 http://www.cloudbase.it/cloud-init-for-windows-instances/
 Regards,
 ---
 JuanFra
 2013/5/27 Narayanan, Krishnaprasad 
 naray...@uni-mainz.demailto:naray...@uni-mainz.de
 Hallo All,
 Can somebody guide me to create a virtual machine using Windows 2008 image?
 Thanks
 Krishnaprasad
 ___
 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.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-ubuntu-testing-notifications] Build Still Failing: precise_havana_quantum_trunk #161

[openstack-testing-bot]

 text/html; charset=UTF-8: Unrecognized 
-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

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

[openstack-testing-bot]

Title: saucy_havana_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/saucy_havana_quantum_trunk/93/Project:saucy_havana_quantum_trunkDate of build:Thu, 30 May 2013 03:30:23 -0400Build duration:6 min 57 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 3 out of the last 5 builds failed.40ChangesFix ml2 stack trace when logging.by rkukuraeditquantum/plugins/ml2/db.pyConsole Output[...truncated 25800 lines...]Job: quantum_2013.2+git201305300330~saucy-0ubuntu1.dscMachine Architecture: amd64Package: quantumPackage-Time: 275Source-Version: 1:2013.2+git201305300330~saucy-0ubuntu1Space: 89288Status: attemptedVersion: 1:2013.2+git201305300330~saucy-0ubuntu1Finished at 20130530-0337Build needed 00:04:35, 89288k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'saucy-havana', '-n', '-A', 'quantum_2013.2+git201305300330~saucy-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'saucy-havana', '-n', '-A', 'quantum_2013.2+git201305300330~saucy-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/quantum/havana /tmp/tmpvxycbv/quantummk-build-deps -i -r -t apt-get -y /tmp/tmpvxycbv/quantum/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 3d0e0c554f22cc122c32d8dfa99509c9b432a62d..HEAD --no-merges --pretty=format:[%h] %sdch -b -D saucy --newversion 1:2013.2+git201305300330~saucy-0ubuntu1 Automated Ubuntu testing build:dch -a [b345dbb] Fix ml2 stack trace when logging.dch -a [f572a5e] Initial Modular L2 plugin implementation.dch -a [3102bd7] Revert dependency on oslo.config 1.2.0dch -a [e2e2c62] Refactor db_base_plugin_v2 and to remove code duplicationdch -a [9f1d2e0] Configurable external gateway modesdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC quantum_2013.2+git201305300330~saucy-0ubuntu1_source.changessbuild -d saucy-havana -n -A quantum_2013.2+git201305300330~saucy-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'saucy-havana', '-n', '-A', 'quantum_2013.2+git201305300330~saucy-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'saucy-havana', '-n', '-A', 'quantum_2013.2+git201305300330~saucy-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_havana_ceilometer_trunk #87

[openstack-testing-bot]

 text/html; charset=UTF-8: Unrecognized 
-- 
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_grizzly_glance_trunk #299

[openstack-testing-bot]

Title: precise_grizzly_glance_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_glance_trunk/299/Project:precise_grizzly_glance_trunkDate of build:Thu, 30 May 2013 07:00:22 -0400Build duration:10 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 3 out of the last 5 builds failed.40ChangesDont raise HTTPForbidden on a multitenant environmentby flaper87editglance/tests/unit/test_swift_store.pyeditglance/store/swift.pyCall monkey_patch before other modules are loadedby flaper87editbin/glance-apieditglance/common/wsgi.pyeditbin/glance-registryeditglance/tests/unit/test_wsgi.pyConsole Output[...truncated 4823 lines...]Build-Time: 449Distribution: precise-grizzlyFail-Stage: buildHost Architecture: amd64Install-Time: 44Job: glance_2013.1+git201305300700~precise-0ubuntu1.dscMachine Architecture: amd64Package: glancePackage-Time: 502Source-Version: 1:2013.1+git201305300700~precise-0ubuntu1Space: 19388Status: attemptedVersion: 1:2013.1+git201305300700~precise-0ubuntu1Finished at 20130530-0710Build needed 00:08:22, 19388k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'glance_2013.1+git201305300700~precise-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'glance_2013.1+git201305300700~precise-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/glance/grizzly /tmp/tmp3VNywe/glancemk-build-deps -i -r -t apt-get -y /tmp/tmp3VNywe/glance/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hdch -b -D precise --newversion 1:2013.1+git201305300700~precise-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC glance_2013.1+git201305300700~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A glance_2013.1+git201305300700~precise-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'glance_2013.1+git201305300700~precise-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-grizzly', '-n', '-A', 'glance_2013.1+git201305300700~precise-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Failure: raring_grizzly_glance_trunk #312

[openstack-testing-bot]

Title: raring_grizzly_glance_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_glance_trunk/312/Project:raring_grizzly_glance_trunkDate of build:Thu, 30 May 2013 07:00:22 -0400Build duration:10 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 2 out of the last 5 builds failed.60ChangesDont raise HTTPForbidden on a multitenant environmentby flaper87editglance/tests/unit/test_swift_store.pyeditglance/store/swift.pyCall monkey_patch before other modules are loadedby flaper87editglance/tests/unit/test_wsgi.pyeditbin/glance-apieditglance/common/wsgi.pyeditbin/glance-registryConsole Output[...truncated 5486 lines...]Build-Time: 433Distribution: raring-grizzlyFail-Stage: buildHost Architecture: amd64Install-Time: 43Job: glance_2013.1+git201305300700~raring-0ubuntu1.dscMachine Architecture: amd64Package: glancePackage-Time: 486Source-Version: 1:2013.1+git201305300700~raring-0ubuntu1Space: 19392Status: attemptedVersion: 1:2013.1+git201305300700~raring-0ubuntu1Finished at 20130530-0711Build needed 00:08:06, 19392k disc spaceERROR:root:Error occurred during package creation/build: Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'glance_2013.1+git201305300700~raring-0ubuntu1.dsc']' returned non-zero exit status 2ERROR:root:Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'glance_2013.1+git201305300700~raring-0ubuntu1.dsc']' returned non-zero exit status 2INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/glance/grizzly /tmp/tmp3m4qZK/glancemk-build-deps -i -r -t apt-get -y /tmp/tmp3m4qZK/glance/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hdch -b -D raring --newversion 1:2013.1+git201305300700~raring-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC glance_2013.1+git201305300700~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A glance_2013.1+git201305300700~raring-0ubuntu1.dscTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'glance_2013.1+git201305300700~raring-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'raring-grizzly', '-n', '-A', 'glance_2013.1+git201305300700~raring-0ubuntu1.dsc']' returned non-zero exit status 2Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Fixed: precise_grizzly_glance_trunk #300

[openstack-testing-bot]

Title: precise_grizzly_glance_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_glance_trunk/300/Project:precise_grizzly_glance_trunkDate of build:Thu, 30 May 2013 07:30:22 -0400Build duration:10 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 3 out of the last 5 builds failed.40ChangesCall os.kill for each child instead of the process groupby flaper87editglance/common/wsgi.pyConsole Output[...truncated 6322 lines...]Finished at 20130530-0740Build needed 00:08:26, 28804k disc spaceINFO:root:Uploading package to ppa:openstack-ubuntu-testing/grizzly-trunk-testingDEBUG:root:['dput', 'ppa:openstack-ubuntu-testing/grizzly-trunk-testing', 'glance_2013.1+git201305300730~precise-0ubuntu1_source.changes']gpg: Signature made Thu May 30 07:31:57 2013 EDT using RSA key ID 9935ACDCgpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) <ja...@shingle-house.org.uk>"gpg: Signature made Thu May 30 07:31:57 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/tmpglUIyb/glance_2013.1+git201305300730~precise-0ubuntu1_source.changes.Checking signature on .dscGood signature on /tmp/tmpglUIyb/glance_2013.1+git201305300730~precise-0ubuntu1.dsc.Uploading to ppa (via ftp to ppa.launchpad.net):  Uploading glance_2013.1+git201305300730~precise-0ubuntu1.dsc: done.  Uploading glance_2013.1+git201305300730~precise.orig.tar.gz: done.  Uploading glance_2013.1+git201305300730~precise-0ubuntu1.debian.tar.gz: done.  Uploading glance_2013.1+git201305300730~precise-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', 'precise-grizzly', 'glance_2013.1+git201305300730~precise-0ubuntu1_amd64.changes']Exporting indices...Successfully created '/var/lib/jenkins/www/apt/dists/precise-grizzly/Release.gpg.new'Successfully created '/var/lib/jenkins/www/apt/dists/precise-grizzly/InRelease.new'Deleting files no longer referenced...deleting and forgetting pool/main/g/glance/glance-api_2013.1+git201305170642~precise-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/glance-common_2013.1+git201305170642~precise-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/glance-registry_2013.1+git201305170642~precise-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/glance_2013.1+git201305170642~precise-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/python-glance-doc_2013.1+git201305170642~precise-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/python-glance_2013.1+git201305170642~precise-0ubuntu1_all.debINFO:root:Storing current commit for next build: 4b1f8039ad26ec9a193feb7689c4440b553113b8INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/glance/grizzly /tmp/tmpglUIyb/glancemk-build-deps -i -r -t apt-get -y /tmp/tmpglUIyb/glance/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hdch -b -D precise --newversion 1:2013.1+git201305300730~precise-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC glance_2013.1+git201305300730~precise-0ubuntu1_source.changessbuild -d precise-grizzly -n -A glance_2013.1+git201305300730~precise-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing glance_2013.1+git201305300730~precise-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-grizzly glance_2013.1+git201305300730~precise-0ubuntu1_amd64.changesEmail 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_glance_trunk #313

[openstack-testing-bot]

Title: raring_grizzly_glance_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_glance_trunk/313/Project:raring_grizzly_glance_trunkDate of build:Thu, 30 May 2013 07:30:26 -0400Build duration:10 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 1 out of the last 5 builds failed.80ChangesCall os.kill for each child instead of the process groupby flaper87editglance/common/wsgi.pyConsole Output[...truncated 6993 lines...]Finished at 20130530-0741Build needed 00:08:18, 28832k disc spaceINFO:root:Uploading package to ppa:openstack-ubuntu-testing/grizzly-trunk-testingDEBUG:root:['dput', 'ppa:openstack-ubuntu-testing/grizzly-trunk-testing', 'glance_2013.1+git201305300730~raring-0ubuntu1_source.changes']gpg: Signature made Thu May 30 07:33:02 2013 EDT using RSA key ID 9935ACDCgpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) <ja...@shingle-house.org.uk>"gpg: Signature made Thu May 30 07:33:01 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/tmpwziIQ4/glance_2013.1+git201305300730~raring-0ubuntu1_source.changes.Checking signature on .dscGood signature on /tmp/tmpwziIQ4/glance_2013.1+git201305300730~raring-0ubuntu1.dsc.Uploading to ppa (via ftp to ppa.launchpad.net):  Uploading glance_2013.1+git201305300730~raring-0ubuntu1.dsc: done.  Uploading glance_2013.1+git201305300730~raring.orig.tar.gz: done.  Uploading glance_2013.1+git201305300730~raring-0ubuntu1.debian.tar.gz: done.  Uploading glance_2013.1+git201305300730~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', 'glance_2013.1+git201305300730~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/g/glance/glance-api_2013.1+git201305290800~raring-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/glance-common_2013.1+git201305290800~raring-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/glance-registry_2013.1+git201305290800~raring-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/glance_2013.1+git201305290800~raring-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/python-glance-doc_2013.1+git201305290800~raring-0ubuntu1_all.debdeleting and forgetting pool/main/g/glance/python-glance_2013.1+git201305290800~raring-0ubuntu1_all.debINFO:root:Storing current commit for next build: 4b1f8039ad26ec9a193feb7689c4440b553113b8INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/glance/grizzly /tmp/tmpwziIQ4/glancemk-build-deps -i -r -t apt-get -y /tmp/tmpwziIQ4/glance/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hdch -b -D raring --newversion 1:2013.1+git201305300730~raring-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC glance_2013.1+git201305300730~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A glance_2013.1+git201305300730~raring-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing glance_2013.1+git201305300730~raring-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include raring-grizzly glance_2013.1+git201305300730~raring-0ubuntu1_amd64.changesEmail 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_havana_cinder_trunk #101

[openstack-testing-bot]

 text/html; charset=UTF-8: Unrecognized 
-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_havana_nova_trunk #252

[openstack-testing-bot]

Title: precise_havana_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_nova_trunk/252/Project:precise_havana_nova_trunkDate of build:Thu, 30 May 2013 08:44:26 -0400Build duration:5 min 16 secBuild cause:Started by user Chuck ShortBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 797 lines...]Download error on http://pypi.python.org/simple/pbr/: timed out -- Some packages may not be found!Couldn't find index page for 'pbr' (maybe misspelled?)Download error on http://pypi.python.org/simple/: timed out -- Some packages may not be found!No local packages or download links found for pbrTraceback (most recent call last):  File "setup.py", line 21, in d2to1=True)  File "/usr/lib/python2.7/distutils/core.py", line 112, in setup_setup_distribution = dist = klass(attrs)  File "/usr/lib/python2.7/dist-packages/setuptools/dist.py", line 221, in __init__self.fetch_build_eggs(attrs.pop('setup_requires'))  File "/usr/lib/python2.7/dist-packages/setuptools/dist.py", line 245, in fetch_build_eggsparse_requirements(requires), installer=self.fetch_build_egg  File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 576, in resolvedist = best[req.key] = env.best_match(req, self, installer)  File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 821, in best_matchreturn self.obtain(req, installer) # try and download/install  File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 833, in obtainreturn installer(requirement)  File "/usr/lib/python2.7/dist-packages/setuptools/dist.py", line 294, in fetch_build_eggreturn cmd.easy_install(req)  File "/usr/lib/python2.7/dist-packages/setuptools/command/easy_install.py", line 602, in easy_installraise DistutilsError(msg)distutils.errors.DistutilsError: Could not find suitable distribution for Requirement.parse('pbr')ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-3088c9a1-4ad2-49b8-b0c5-b609b803e2cf', '-u', 'jenkins', '--', 'python', 'setup.py', 'sdist']' returned non-zero exit status 1ERROR:root:Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-3088c9a1-4ad2-49b8-b0c5-b609b803e2cf', '-u', 'jenkins', '--', 'python', 'setup.py', 'sdist']' returned non-zero exit status 1INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/havana /tmp/tmpxVVsON/novamk-build-deps -i -r -t apt-get -y /tmp/tmpxVVsON/nova/debian/controlpython setup.py sdistTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-3088c9a1-4ad2-49b8-b0c5-b609b803e2cf', '-u', 'jenkins', '--', 'python', 'setup.py', 'sdist']' returned non-zero exit status 1Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-3088c9a1-4ad2-49b8-b0c5-b609b803e2cf', '-u', 'jenkins', '--', 'python', 'setup.py', 'sdist']' returned non-zero exit status 1Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_havana_python-swiftclient_trunk #15

[openstack-testing-bot]

 text/html; charset=UTF-8: Unrecognized 
-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_havana_python-swiftclient_trunk #16

[openstack-testing-bot]

Title: precise_havana_python-swiftclient_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_havana_python-swiftclient_trunk/16/Project:precise_havana_python-swiftclient_trunkDate of build:Thu, 30 May 2013 10:46:49 -0400Build duration:3 min 35 secBuild cause:Started by user Chuck ShortBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole Output[...truncated 694 lines...]Download error on http://pypi.python.org/simple/pbr/: timed out -- Some packages may not be found!Couldn't find index page for 'pbr' (maybe misspelled?)Download error on http://pypi.python.org/simple/: timed out -- Some packages may not be found!No local packages or download links found for pbrTraceback (most recent call last):  File "setup.py", line 21, in d2to1=True)  File "/usr/lib/python2.7/distutils/core.py", line 112, in setup_setup_distribution = dist = klass(attrs)  File "/usr/lib/python2.7/dist-packages/setuptools/dist.py", line 221, in __init__self.fetch_build_eggs(attrs.pop('setup_requires'))  File "/usr/lib/python2.7/dist-packages/setuptools/dist.py", line 245, in fetch_build_eggsparse_requirements(requires), installer=self.fetch_build_egg  File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 576, in resolvedist = best[req.key] = env.best_match(req, self, installer)  File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 821, in best_matchreturn self.obtain(req, installer) # try and download/install  File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 833, in obtainreturn installer(requirement)  File "/usr/lib/python2.7/dist-packages/setuptools/dist.py", line 294, in fetch_build_eggreturn cmd.easy_install(req)  File "/usr/lib/python2.7/dist-packages/setuptools/command/easy_install.py", line 602, in easy_installraise DistutilsError(msg)distutils.errors.DistutilsError: Could not find suitable distribution for Requirement.parse('pbr')ERROR:root:Error occurred during package creation/build: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-f2014a6c-6911-4452-8ff7-f17b6bca64bb', '-u', 'jenkins', '--', 'python', 'setup.py', 'sdist']' returned non-zero exit status 1ERROR:root:Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-f2014a6c-6911-4452-8ff7-f17b6bca64bb', '-u', 'jenkins', '--', 'python', 'setup.py', 'sdist']' returned non-zero exit status 1INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/python-swiftclient/havana /tmp/tmpvE4bVo/python-swiftclientmk-build-deps -i -r -t apt-get -y /tmp/tmpvE4bVo/python-swiftclient/debian/controlpython setup.py sdistTraceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-f2014a6c-6911-4452-8ff7-f17b6bca64bb', '-u', 'jenkins', '--', 'python', 'setup.py', 'sdist']' returned non-zero exit status 1Error in sys.excepthook:Traceback (most recent call last):  File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwd(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last):  File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 139, in raise esubprocess.CalledProcessError: Command '['/usr/bin/schroot', '-p', '-r', '-c', 'precise-amd64-f2014a6c-6911-4452-8ff7-f17b6bca64bb', '-u', 'jenkins', '--', 'python', 'setup.py', 'sdist']' returned non-zero exit status 1Build step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_havana_python-novaclient_trunk #45

[openstack-testing-bot]

 text/html; charset=UTF-8: Unrecognized 
-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_havana_ceilometer_trunk #88

[openstack-testing-bot]

 text/html; charset=UTF-8: Unrecognized 
-- 
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: saucy_havana_python-novaclient_trunk #23

[openstack-testing-bot]

Title: saucy_havana_python-novaclient_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/saucy_havana_python-novaclient_trunk/23/Project:saucy_havana_python-novaclient_trunkDate of build:Thu, 30 May 2013 11:33:40 -0400Build duration:4 min 49 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: 4 out of the last 5 builds failed.20ChangesFix shell tests for older prettytable versions.by Adam Gandelmaneditnovaclient/tests/test_shell.pyConsole Output[...truncated 2669 lines...]DEBUG:root:['dput', 'ppa:openstack-ubuntu-testing/havana', 'python-novaclient_2.13.0.66.gdef5df2+git201305301133~saucy-0ubuntu1_source.changes']gpg: Signature made Thu May 30 11:36:20 2013 EDT using RSA key ID 9935ACDCgpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) "gpg: Signature made Thu May 30 11:36:20 2013 EDT using RSA key ID 9935ACDCgpg: Good signature from "Openstack Ubuntu Testing Bot (Jenkins Key) "Checking signature on .changesGood signature on /tmp/tmp3bTlJR/python-novaclient_2.13.0.66.gdef5df2+git201305301133~saucy-0ubuntu1_source.changes.Checking signature on .dscGood signature on /tmp/tmp3bTlJR/python-novaclient_2.13.0.66.gdef5df2+git201305301133~saucy-0ubuntu1.dsc.Uploading to ppa (via ftp to ppa.launchpad.net):  Uploading python-novaclient_2.13.0.66.gdef5df2+git201305301133~saucy-0ubuntu1.dsc: done.  Uploading python-novaclient_2.13.0.66.gdef5df2+git201305301133~saucy.orig.tar.gz: done.  Uploading python-novaclient_2.13.0.66.gdef5df2+git201305301133~saucy-0ubuntu1.debian.tar.gz: done.  Uploading python-novaclient_2.13.0.66.gdef5df2+git201305301133~saucy-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', 'saucy-havana', 'python-novaclient_2.13.0.66.gdef5df2+git201305301133~saucy-0ubuntu1_amd64.changes']Exporting indices...Successfully created '/var/lib/jenkins/www/apt/dists/saucy-havana/Release.gpg.new'Successfully created '/var/lib/jenkins/www/apt/dists/saucy-havana/InRelease.new'Deleting files no longer referenced...deleting and forgetting pool/main/p/python-novaclient/python-novaclient_2.13.0.54.g9d4db6f+git20130528~saucy-0ubuntu1_all.debINFO:root:Storing current commit for next build: def5df2760b38b1493548722ddd49082f3773c31INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/python-novaclient/havana /tmp/tmp3bTlJR/python-novaclientmk-build-deps -i -r -t apt-get -y /tmp/tmp3bTlJR/python-novaclient/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hgit log 9d4db6f740fe00f50c77920b5ef7a4fbd08d181f..HEAD --no-merges --pretty=format:[%h] %sdch -b -D saucy --newversion 1:2.13.0.66.gdef5df2+git201305301133~saucy-0ubuntu1 Automated Ubuntu testing build:dch -a [def5df2] Fix shell tests for older prettytable versions.dch -a [37da28c] Provide nova CLI man page.dch -a [a8ed2f2] Improve error messages for invalid --nic / --file.dch -a [ff85bd4] 100% test coverage for security groups and rulesdch -a [f2559c4] Add MethodNotAllowed and Conflict exception classesdch -a [c34c371] Move tests into the novaclient package.dch -a [51f0596] Add CONTRIBUTING file.dch -a [3bbdcda] Rename requires files to standard names.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC python-novaclient_2.13.0.66.gdef5df2+git201305301133~saucy-0ubuntu1_source.changessbuild -d saucy-havana -n -A python-novaclient_2.13.0.66.gdef5df2+git201305301133~saucy-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/havana python-novaclient_2.13.0.66.gdef5df2+git201305301133~saucy-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include saucy-havana python-novaclient_2.13.0.66.gdef5df2+git201305301133~saucy-0ubuntu1_amd64.changesEmail 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_havana_cinder_trunk #103

[openstack-testing-bot]

 text/html; charset=UTF-8: Unrecognized 
-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

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

[openstack-testing-bot]

 text/html; charset=UTF-8: Unrecognized 
-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_havana_keystone_trunk #75

[openstack-testing-bot]

 text/html; charset=UTF-8: Unrecognized 
-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_havana_keystone_trunk #76

[openstack-testing-bot]

 text/html; charset=UTF-8: Unrecognized 
-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_havana_keystone_trunk #78

[openstack-testing-bot]

 text/html; charset=UTF-8: Unrecognized 
-- 
Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications
Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications
More help   : https://help.launchpad.net/ListHelp

[Openstack-ubuntu-testing-notifications] Build Still Failing: precise_havana_keystone_trunk #79

[openstack-testing-bot]

 text/html; charset=UTF-8: Unrecognized 
-- 
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