[Openstack] [OpenStack][Swift] Error while starting container, account, object servers.

2013-02-12 Thread Sujay M
Hi all,

When i try to start the storage node I'm getting this error. Please help me
resolve it
root@vm2:~# swift-init all restart
Signal container-updater  pid: 298  signal: 15
Signal account-auditor  pid: 301  signal: 15
Signal object-replicator  pid: 297  signal: 15
No proxy-server running
Signal container-replicator  pid: 295  signal: 15
Signal object-auditor  pid: 302  signal: 15
No object-expirer running
Signal container-auditor  pid: 294  signal: 15
Signal container-server  pid: 530  signal: 15
No container-server running
Signal account-server  pid: 531  signal: 15
No account-server running
Signal account-reaper  pid: 304  signal: 15
Signal container-sync  pid: 448  signal: 15
Signal account-replicator  pid: 305  signal: 15
Signal object-updater  pid: 296  signal: 15
Signal object-server  pid: 532  signal: 15
No object-server running
container-updater (298) appears to have stopped
account-replicator (305) appears to have stopped
container-sync (448) appears to have stopped
object-updater (296) appears to have stopped
object-replicator (297) appears to have stopped
container-replicator (295) appears to have stopped
account-reaper (304) appears to have stopped
container-auditor (294) appears to have stopped
object-auditor (302) appears to have stopped
account-auditor (301) appears to have stopped
Starting container-updater...(/etc/swift/container-server.conf)
Starting account-auditor...(/etc/swift/account-server.conf)
Starting object-replicator...(/etc/swift/object-server.conf)
Unable to locate config for proxy-server
Starting container-replicator...(/etc/swift/container-server.conf)
Starting object-auditor...(/etc/swift/object-server.conf)
Unable to locate config for object-expirer
Starting container-auditor...(/etc/swift/container-server.conf)
Starting container-server...(/etc/swift/container-server.conf)
Starting account-server...(/etc/swift/account-server.conf)
Starting account-reaper...(/etc/swift/account-server.conf)
Starting container-sync...(/etc/swift/container-server.conf)
Starting account-replicator...(/etc/swift/account-server.conf)
Starting object-updater...(/etc/swift/object-server.conf)
Starting object-server...(/etc/swift/object-server.conf)
Traceback (most recent call last):
  File "/usr/bin/swift-container-server", line 22, in 
run_wsgi(conf_file, 'container-server', default_port=6001, **options)
  File "/usr/lib/python2.7/dist-packages/swift/common/wsgi.py", line 117,
in run_wsgi
sock = get_socket(conf, default_port=kwargs.get('default_port', 8080))
  File "/usr/lib/python2.7/dist-packages/swift/common/wsgi.py", line 73, in
get_socket
family=address_family)
  File "/usr/lib/python2.7/dist-packages/eventlet/convenience.py", line 38,
in listen
sock.bind(addr)
  File "/usr/lib/python2.7/socket.py", line 224, in meth
return getattr(self._sock,name)(*args)
socket.error: [Errno 99] Cannot assign requested address

Traceback (most recent call last):
  File "/usr/bin/swift-account-server", line 22, in 
run_wsgi(conf_file, 'account-server', default_port=6002, **options)
  File "/usr/lib/python2.7/dist-packages/swift/common/wsgi.py", line 117,
in run_wsgi
sock = get_socket(conf, default_port=kwargs.get('default_port', 8080))
  File "/usr/lib/python2.7/dist-packages/swift/common/wsgi.py", line 73, in
get_socket
family=address_family)
  File "/usr/lib/python2.7/dist-packages/eventlet/convenience.py", line 38,
in listen
sock.bind(addr)
  File "/usr/lib/python2.7/socket.py", line 224, in meth
return getattr(self._sock,name)(*args)
socket.error: [Errno 99] Cannot assign requested address

Traceback (most recent call last):
  File "/usr/bin/swift-object-server", line 22, in 
run_wsgi(conf_file, 'object-server', default_port=6000, **options)
  File "/usr/lib/python2.7/dist-packages/swift/common/wsgi.py", line 117,
in run_wsgi
sock = get_socket(conf, default_port=kwargs.get('default_port', 8080))
  File "/usr/lib/python2.7/dist-packages/swift/common/wsgi.py", line 73, in
get_socket
family=address_family)
  File "/usr/lib/python2.7/dist-packages/eventlet/convenience.py", line 38,
in listen
sock.bind(addr)
  File "/usr/lib/python2.7/socket.py", line 224, in meth
return getattr(self._sock,name)(*args)
socket.error: [Errno 99] Cannot assign requested address


-- 
Best Regards,

Sujay M
Final year B.Tech
Computer Engineering
NITK Surathkal

contact: +918971897571
___
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][Swift] Error while starting container, account, object servers.

2013-02-12 Thread Razique Mahroua
Hi, it's like the address you are trying to bind to either doesn't exist or the ports are already assigned.Can you provide us more infos on the setup?thanks 
Razique Mahroua - Nuage & Corazique.mahr...@gmail.comTel : +33 9 72 37 94 15

Le 12 févr. 2013 à 09:30, Sujay M  a écrit :Hi all,When i try to start the storage node I'm getting this error. Please help me resolve itroot@vm2:~# swift-init all restartSignal container-updater  pid: 298  signal: 15Signal account-auditor  pid: 301  signal: 15

Signal object-replicator  pid: 297  signal: 15No proxy-server runningSignal container-replicator  pid: 295  signal: 15Signal object-auditor  pid: 302  signal: 15No object-expirer runningSignal container-auditor  pid: 294  signal: 15

Signal container-server  pid: 530  signal: 15No container-server runningSignal account-server  pid: 531  signal: 15No account-server runningSignal account-reaper  pid: 304  signal: 15Signal container-sync  pid: 448  signal: 15

Signal account-replicator  pid: 305  signal: 15Signal object-updater  pid: 296  signal: 15Signal object-server  pid: 532  signal: 15No object-server runningcontainer-updater (298) appears to have stopped

account-replicator (305) appears to have stoppedcontainer-sync (448) appears to have stoppedobject-updater (296) appears to have stoppedobject-replicator (297) appears to have stoppedcontainer-replicator (295) appears to have stopped

account-reaper (304) appears to have stoppedcontainer-auditor (294) appears to have stoppedobject-auditor (302) appears to have stoppedaccount-auditor (301) appears to have stoppedStarting container-updater...(/etc/swift/container-server.conf)

Starting account-auditor...(/etc/swift/account-server.conf)Starting object-replicator...(/etc/swift/object-server.conf)Unable to locate config for proxy-serverStarting container-replicator...(/etc/swift/container-server.conf)

Starting object-auditor...(/etc/swift/object-server.conf)Unable to locate config for object-expirerStarting container-auditor...(/etc/swift/container-server.conf)Starting container-server...(/etc/swift/container-server.conf)

Starting account-server...(/etc/swift/account-server.conf)Starting account-reaper...(/etc/swift/account-server.conf)Starting container-sync...(/etc/swift/container-server.conf)Starting account-replicator...(/etc/swift/account-server.conf)

Starting object-updater...(/etc/swift/object-server.conf)Starting object-server...(/etc/swift/object-server.conf)Traceback (most recent call last):  File "/usr/bin/swift-container-server", line 22, in 

    run_wsgi(conf_file, 'container-server', default_port=6001, **options)  File "/usr/lib/python2.7/dist-packages/swift/common/wsgi.py", line 117, in run_wsgi    sock = get_socket(conf, default_port=kwargs.get('default_port', 8080))

  File "/usr/lib/python2.7/dist-packages/swift/common/wsgi.py", line 73, in get_socket    family=address_family)  File "/usr/lib/python2.7/dist-packages/eventlet/convenience.py", line 38, in listen

    sock.bind(addr)  File "/usr/lib/python2.7/socket.py", line 224, in meth    return getattr(self._sock,name)(*args)socket.error: [Errno 99] Cannot assign requested addressTraceback (most recent call last):

  File "/usr/bin/swift-account-server", line 22, in     run_wsgi(conf_file, 'account-server', default_port=6002, **options)  File "/usr/lib/python2.7/dist-packages/swift/common/wsgi.py", line 117, in run_wsgi

    sock = get_socket(conf, default_port=kwargs.get('default_port', 8080))  File "/usr/lib/python2.7/dist-packages/swift/common/wsgi.py", line 73, in get_socket    family=address_family)  File "/usr/lib/python2.7/dist-packages/eventlet/convenience.py", line 38, in listen

    sock.bind(addr)  File "/usr/lib/python2.7/socket.py", line 224, in meth    return getattr(self._sock,name)(*args)socket.error: [Errno 99] Cannot assign requested addressTraceback (most recent call last):

  File "/usr/bin/swift-object-server", line 22, in     run_wsgi(conf_file, 'object-server', default_port=6000, **options)  File "/usr/lib/python2.7/dist-packages/swift/common/wsgi.py", line 117, in run_wsgi

    sock = get_socket(conf, default_port=kwargs.get('default_port', 8080))  File "/usr/lib/python2.7/dist-packages/swift/common/wsgi.py", line 73, in get_socket    family=address_family)  File "/usr/lib/python2.7/dist-packages/eventlet/convenience.py", line 38, in listen

    sock.bind(addr)  File "/usr/lib/python2.7/socket.py", line 224, in meth    return getattr(self._sock,name)(*args)socket.error: [Errno 99] Cannot assign requested address-- 

Best Regards,Sujay MFinal year B.TechComputer EngineeringNITK Surathkalcontact: +918971897571

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

Re: [Openstack] metadata issue

2013-02-12 Thread Razique Mahroua
Hi,what is your current network model?thanks
Razique Mahroua - Nuage & Corazique.mahr...@gmail.comTel : +33 9 72 37 94 15

Le 12 févr. 2013 à 00:25, Paras pradhan  a écrit :Hi,The packages I am using are from folsom ubuntu quantal branch.  When Irun an instance I see--wget: can't connect to remote host (169.254.169.254): Network is unreachable--this might be the network issue as well.nova list shows my instance .  I am running nova-network on computenode. nova-api is running on both controller and compute nodes.I have seen lot of ppl are having issues on this but i was not able tofind out the issue by looking at their posts.How do I start debugging?ThanksParas.___Mailing list: https://launchpad.net/~openstackPost to : openstack@lists.launchpad.netUnsubscribe : https://launchpad.net/~openstackMore help   : https://help.launchpad.net/ListHelp___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] glance-api and glance-registry startup error

2013-02-12 Thread Razique Mahroua
Hi,have you configured glance to use Keystone?Can you show us glance configuration files?thanks,
Razique Mahroua - Nuage & Corazique.mahr...@gmail.comTel : +33 9 72 37 94 15

Le 11 févr. 2013 à 23:39, Mohammed Amine SAYA  a écrit :Hi all,I am new to openstack and I managed to get two servers to manage and install openstack on debian distros.I managed to install MySQL, keystone and glance. The later still causes some headaches because this line keeps showing up in glance-api.log and glance-registry.log : 
2013-02-11 23:22:28 5440 ERROR eventlet.wsgi.server [-] SIGTERM or SIGINT receivedAny attempt to upload an image or list the empty list, results in this :
asaya@openstack0:~$ glance image-listUnable to communicate with identity service: {"error": {"message": "Invalid user / password", "code": 401, "title": "Not Authorized"}}. (HTTP 401)
When I try keystone commands, everything seems fine :asaya@openstack0:~$ keystone --token x --endpoint http://localhost:35357/v2.0 user-list
WARNING: Bypassing authentication using a token & endpoint (authentication credentials are being ignored).+--+-+-++|                id                |   name  | enabled |       email        |
+--+-+-++| 50d3ab1c81df43bc9c38d86db13d00e5 |  admin  |   True  |  ad...@domain.com  || e26e3f9d289c45da83753b2f0be28974 |  cinder |   True  | cin...@domain.com  |
| 85cb3c8e893147dba77f8f12c62fa54e |   demo  |   True  |  d...@domain.com   || 1b46e2b9b8b948af93344ef0a7f11036 |  glance |   True  | gla...@domain.com  |
| 377c160a261044ebbc00b23fa73b082d |   nova  |   True  |  n...@domain.com   || 351d22cc54ca47a2a1338d365b988d17 | quantum |   True  | quan...@domain.com |
| d70ea92f124e4f39a5f05a4ca50c059e |  swift  |   True  |  sw...@domain.com  |+--+-+-++asaya@openstack0:~$ keystone --token x --endpoint http://localhost:35357/v2.0 tenant-list
WARNING: Bypassing authentication using a token & endpoint (authentication credentials are being ignored).+--++-+|                id                |        name        | enabled |
+--++-+| 5690876e82414117b80e64167a3ee3f8 |       admin        |   True  || 28be43a159854b43ae3b3bdcec3f266a |        demo        |   True  |
| 32dfe85ac79e4e6ba51faa4bca45e9b2 | invisible_to_admin |   True  || 4691c9362747415eb85fa47aac0ccc66 |      service       |   True  |+--++-+
Any help on this please?Best regards,Amine.
___Mailing list: https://launchpad.net/~openstackPost to : openstack@lists.launchpad.netUnsubscribe : https://launchpad.net/~openstackMore help   : https://help.launchpad.net/ListHelp___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] [OpenStack][Swift] Error while starting container, account, object servers.

2013-02-12 Thread Sujay M
My account-server configuration (Similarly other servers on 6010, 6011)

root@vm0:~# cat /etc/swift/account-server.conf
[DEFAULT]
bind_ip = 10.0.2.16
bind_port = 6012
devices = /mnt
mount_check = false
disable_fallocate = true
user = ubuntu
eventlet_debug = true

[pipeline:main]
pipeline = account-server

[app:account-server]
use = egg:swift#account

[account-replicator]
vm_test_mode = yes

[account-auditor]

[account-reaper]


Output of netstat -pl

Proto Recv-Q Send-Q Local Address   Foreign Address
State   PID/Program name
tcp0  0 *:ssh   *:*
LISTEN  135/sshd
tcp6   0  0 [::]:ssh[::]:*
LISTEN  135/sshd
udp0  0 *:bootpc
*:* 184/dhclient3
Active UNIX domain sockets (only servers)
Proto RefCnt Flags   Type   State I-Node   PID/Program
namePath
unix  2  [ ACC ] STREAM LISTENING 12674
1/init  @/com/ubuntu/upstart
unix  2  [ ACC ] SEQPACKET  LISTENING 14327
143/udevd   /run/udev/control


ouput of ps -Al

root@vm0:~# ps -Al
F S   UID   PID  PPID  C PRI  NI ADDR SZ WCHAN  TTY  TIME CMD
4 S 0 1 0  0  80   0 -  6083 poll_s ?00:00:00 init
1 S 070 1  0  80   0 -  3797 poll_s ?00:00:00
upstart-socket
1 S 0   117 1  0  80   0 -  4308 poll_s ?00:00:00
upstart-udev-b
4 S 0   135 1  0  80   0 - 12489 poll_s ?00:00:00 sshd
5 S 0   143 1  0  80   0 -  5334 ep_pol ?00:00:00 udevd
5 S   101   151 1  0  80   0 - 45982 poll_s ?00:00:00 rsyslogd
1 S 0   184 1  0  80   0 -  1816 poll_s ?00:00:00 dhclient3
4 S 0   229 1  0  80   0 -  3188 n_tty_ lxc/tty4 00:00:00 getty
4 S 0   240 1  0  80   0 -  3188 n_tty_ lxc/tty2 00:00:00 getty
4 S 0   241 1  0  80   0 -  3188 n_tty_ lxc/tty3 00:00:00 getty
1 S 0   249 1  0  80   0 -  4778 hrtime ?00:00:00 cron
4 S 0   307 1  0  80   0 - 13613 wait   lxc/console 00:00:00 login
4 S 0   309 1  0  80   0 -  3188 n_tty_ lxc/tty1 00:00:00 getty
5 S 0   387   143  0  80   0 -  5333 ep_pol ?00:00:00 udevd
5 S 0   388   143  0  80   0 -  5333 ep_pol ?00:00:00 udevd
4 S  1000   400   307  0  80   0 -  4525 wait   lxc/console 00:00:00 bash
4 S 0   430   400  0  80   0 -  9075 poll_s lxc/console 00:00:00 sudo
4 S 0   431   430  0  80   0 -  4525 wait   lxc/console 00:00:00 bash
4 S  1000   443 1  2  80   0 - 18943 poll_s ?00:00:04
swift-containe
4 S  1000   444 1  0  80   0 - 18435 poll_s ?00:00:00
swift-account-
4 S  1000   445 1  2  80   0 - 188691 poll_s ?   00:00:04
swift-object-r
4 S  1000   446 1  2  80   0 - 18932 poll_s ?00:00:05
swift-containe
4 S  1000   447 1  0  80   0 - 17677 poll_s ?00:00:00
swift-object-a
4 S  1000   448 1  0  80   0 - 18434 poll_s ?00:00:00
swift-containe
4 S  1000   451 1  0  80   0 - 18559 poll_s ?00:00:00
swift-account-
4 S  1000   452 1  4  80   0 - 20978 poll_s ?00:00:10
swift-containe
4 S  1000   453 1  2  80   0 - 18898 poll_s ?00:00:05
swift-account-
4 S  1000   454 1  0  80   0 - 17673 poll_s ?00:00:00
swift-object-u
1 S  1000   496   447  0  80   0 - 17715 poll_s ?00:00:00
swift-object-a
4 R 0   540   431  0  80   0 -  1712 -  lxc/console 00:00:00 ps

On 12 February 2013 14:06, Razique Mahroua wrote:

> Hi,
> it's like the address you are trying to bind to either doesn't exist or
> the ports are already assigned.
> Can you provide us more infos on the setup?
> thanks
>
> *Razique Mahroua** - **Nuage & Co*
> razique.mahr...@gmail.com
> Tel : +33 9 72 37 94 15
>
>
> Le 12 févr. 2013 à 09:30, Sujay M  a écrit :
>
> Hi all,
>
> When i try to start the storage node I'm getting this error. Please help
> me resolve it
> root@vm2:~# swift-init all restart
> Signal container-updater  pid: 298  signal: 15
> Signal account-auditor  pid: 301  signal: 15
> Signal object-replicator  pid: 297  signal: 15
> No proxy-server running
> Signal container-replicator  pid: 295  signal: 15
> Signal object-auditor  pid: 302  signal: 15
> No object-expirer running
> Signal container-auditor  pid: 294  signal: 15
> Signal container-server  pid: 530  signal: 15
> No container-server running
> Signal account-server  pid: 531  signal: 15
> No account-server running
> Signal account-reaper  pid: 304  signal: 15
> Signal container-sync  pid: 448  signal: 15
> Signal account-replicator  pid: 305  signal: 15
> Signal object-updater  pid: 296  signal: 15
> Signal object-server  pid: 532  signal: 15
> No object-server running
> container-updater (298) appears to have stopped
> account-replicator (305) appears to have stopped
> container-sync (448) appears to have stopped
> object-updater (296) appears to have stopped
> object-replicator (297) appears to have stopped
> containe

Re: [Openstack] Folsom - Volume attach to a server in second compute node

2013-02-12 Thread Богдан До
 I believe you should check this one  
https://bugs.launchpad.net/nova/+bug/922232/comments/11
You should search compute logs for :3260 and ensure iSCSI target server is 
accessible:

iscsiadm --mode discovery --type sendtargets --portal :3260 -d 8 


Пятница,  8 февраля 2013, 12:42 -05:00 от AK Sathiya :
>Hello Openstackers, I have setup the openstack folsom and added additional 
>compute node. I am successfully able to create a VM on the second compute 
>node, but could not attach a volume (I have configured Cinder) to the VM 
>created on the second compute node.
> 
>When I attach the volume, the status still says 'Attaching' when I do the 
>cinder list. No errors in cinder logs or nova compute logs. No errors in Nova 
>compute logs in the second compute node. 
> 
>What am I missing?
> 
>Is there a document explaining how I could attach a volume to a VM on the 
>secondary node?
> 
>Any help is appreciated.
> 
>AK
>___
>Mailing list:  https://launchpad.net/~openstack
>Post to :  openstack@lists.launchpad.net
>Unsubscribe :  https://launchpad.net/~openstack
>More help   :  https://help.launchpad.net/ListHelp
>

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


[Openstack] Horizon Keystone Endpoint Issue

2013-02-12 Thread Trinath Somanchi
Hi Stackers-

I have successfully installed folsom in my test setup.
But when I browse Horison, with admin/password as credentials, I get this
error.

[Tue Feb 12 10:03:16 2013] [error] unable to retrieve service catalog with
token
[Tue Feb 12 10:03:16 2013] [error] Traceback (most recent call last):
[Tue Feb 12 10:03:16 2013] [error]   File
"/usr/lib/python2.7/dist-packages/keystoneclient/v2_0/client.py", line 132,
in _extract_service_catalog
[Tue Feb 12 10:03:16 2013] [error] endpoint_type='adminURL')
[Tue Feb 12 10:03:16 2013] [error]   File
"/usr/lib/python2.7/dist-packages/keystoneclient/service_catalog.py", line
62, in url_for
[Tue Feb 12 10:03:16 2013] [error] raise
exceptions.EndpointNotFound('Endpoint not found.')
[Tue Feb 12 10:03:16 2013] [error] EndpointNotFound: Endpoint not found.
[Tue Feb 12 10:03:17 2013] [error] \x1b[31;1mUnauthorized: n/a (HTTP
401)\x1b[0m
[Tue Feb 12 10:03:17 2013] [error] Traceback (most recent call last):
[Tue Feb 12 10:03:17 2013] [error]   File
"/usr/lib/python2.7/dist-packages/horizon/usage/base.py", line 93, in
summarize
[Tue Feb 12 10:03:17 2013] [error] self.usage_list =
self.get_usage_list(start, end)
[Tue Feb 12 10:03:17 2013] [error]   File
"/usr/lib/python2.7/dist-packages/horizon/usage/base.py", line 128, in
get_usage_list
[Tue Feb 12 10:03:17 2013] [error] return api.usage_list(self.request,
start, end)
[Tue Feb 12 10:03:17 2013] [error]   File
"/usr/lib/python2.7/dist-packages/horizon/api/nova.py", line 418, in
usage_list
[Tue Feb 12 10:03:17 2013] [error] return [Usage(u) for u in
novaclient(request).usage.list(start, end, True)]
[Tue Feb 12 10:03:17 2013] [error]   File
"/usr/lib/python2.7/dist-packages/novaclient/v1_1/usage.py", line 35, in
list
[Tue Feb 12 10:03:17 2013] [error] "tenant_usages")
[Tue Feb 12 10:03:17 2013] [error]   File
"/usr/lib/python2.7/dist-packages/novaclient/base.py", line 62, in _list
[Tue Feb 12 10:03:17 2013] [error] _resp, body =
self.api.client.get(url)
[Tue Feb 12 10:03:17 2013] [error]   File
"/usr/lib/python2.7/dist-packages/novaclient/client.py", line 239, in get
[Tue Feb 12 10:03:17 2013] [error] return self._cs_request(url, 'GET',
**kwargs)
[Tue Feb 12 10:03:17 2013] [error]   File
"/usr/lib/python2.7/dist-packages/novaclient/client.py", line 236, in
_cs_request
[Tue Feb 12 10:03:17 2013] [error] raise ex
[Tue Feb 12 10:03:17 2013] [error] Unauthorized: n/a (HTTP 401)

It says , I missed some End point Configuration.

But then, I have configured it correctly.

Can any one guide me resolving this issue.

Thanks in advance.

-- 
Regards,
--
Trinath Somanchi,
+91 9866 235 130
___
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 brctl addbr not supported on RHEL 6.3

2013-02-12 Thread Gary Kotton

On 02/11/2013 06:58 PM, Pádraig Brady wrote:

A quick search suggests that kernel has CONFIG_BRIDGE=n set.
So I presume there another method is possible through config.
Gary any ideas?


Please look at https://bugzilla.redhat.com/show_bug.cgi?id=877704. For 
some reason the the bridge module is not loaded. I hope that if you 
follow what is listed in the bug then it will all work and the 
experience will improve.


Thanks
Gary



On 02/11/2013 04:33 PM, Greg Chavez wrote:


Running latest EPEL Folsom packages on RHEL 6.3.  Three nodes right 
now, one controller, one network node, one compute node.  The network 
node has three NICs, one for external net, one for management net, 
one for VM network traffic.  It has been a miserable journey so far.


The lastest calamity began with a failed spawn of the Cirros test 
image.  I booted it like this:


# nova --os-username demo --os-password demo --os-tenant-name 
demoProject boot --image aefa581f-47b0-4d46-8dbc-1a1f7f02dfa0 
--flavor 2  --nic net-id=3de1e780-07d1-42af-89cc-0feaf1ece6e9 server-01


This succeeded but went directly into an ERROR state.  The compute 
node's /var/log/nova/compute.log showed this:


ProcessExecutionError: Unexpected error while running command.
Command: sudo nova-rootwrap /etc/nova/rootwrap.conf brctl addbr 
qbr2218b8c4-7d

Exit code: 1
Stdout: ''
Stderr: 'add bridge failed: Package not installed\n'

Hrm.  So then I ran this:

# brctl show
bridge namebridge idSTP enabledinterfaces
br-eth1/sys/class/net/br-eth1/bridge: No such file or directory
/sys/class/net/br-eth1/bridge: No such file or directory
/sys/class/net/br-eth1/bridge: No such file or directory
/sys/class/net/br-eth1/bridge: No such file or directory
/sys/class/net/br-eth1/bridge: No such file or directory
/sys/class/net/br-eth1/bridge: No such file or directory
/sys/class/net/br-eth1/bridge: No such file or directory
/sys/class/net/br-eth1/bridge: No such file or directory
/sys/class/net/br-eth1/bridge: No such file or directory
/sys/class/net/br-eth1/bridge: No such file or directory
/sys/class/net/br-eth1/bridge: No such file or directory
/sys/class/net/br-eth1/bridge: No such file or directory
.bc305befedd1no
br-int/sys/class/net/br-int/bridge: No such file or directory
/sys/class/net/br-int/bridge: No such file or directory
/sys/class/net/br-int/bridge: No such file or directory
/sys/class/net/br-int/bridge: No such file or directory
/sys/class/net/br-int/bridge: No such file or directory
/sys/class/net/br-int/bridge: No such file or directory
/sys/class/net/br-int/bridge: No such file or directory
/sys/class/net/br-int/bridge: No such file or directory
/sys/class/net/br-int/bridge: No such file or directory
/sys/class/net/br-int/bridge: No such file or directory
/sys/class/net/br-int/bridge: No such file or directory
/sys/class/net/br-int/bridge: No such file or directory
.7e1636f42c4bno

GAH!   What!!! First of all, bridge capability is set by default in 
the RHEL 6.3 kernel.  Secondly, nova knows that it's supposed to be 
using openvswitch.  The ProcessExecutionError's trace showed that the 
offending code came from 
/usr/lib/python2.6/site-packages/nova/virt/libvirt/vif.py line 216 
which has this comment:


 def plug(self, instance, vif):
 """Plug using hybrid strategy

 Create a per-VIF linux bridge, then link that bridge to the OVS
 integration bridge via a veth device, setting up the other end
 of the veth device just like a normal OVS port.  Then boot the
 VIF on the linux bridge using standard libvirt mechanisms
 """

Thirdly, ovs-vsctrl is happy:

# ovs-vsctl show
44435595-8cc8-469c-ace4-ded76a7b864d
 Bridge "br-eth1"
 Port "br-eth1"
 Interface "br-eth1"
 type: internal
 Port "phy-br-eth1"
 Interface "phy-br-eth1"
 Port "eth1"
 Interface "eth1"
 Bridge br-int
 Port "int-br-eth1"
 Interface "int-br-eth1"
 Port br-int
 Interface br-int
 type: internal
 ovs_version: "1.7.3"

Final note, my network node fails the same way, but the controller 
does not.


I hope so much that somebody knows what is going on here.  This is 
very terrible for me as I am struggling to achieve minimal 
functionality.  Thanks.



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


Re: [Openstack] brctl meltdown on RHEL 6.3

2013-02-12 Thread Gary Kotton

On 02/11/2013 07:26 PM, Greg Chavez wrote:

Solution:

[root@kvm-cs-sn-10i nova]# modprobe -r brcompat
[root@kvm-cs-sn-10i nova]# modprobe bridge
[root@kvm-cs-sn-10i nova]# brctl show
bridge namebridge idSTP enabledinterfaces

Still can't boot a VM... looking into the reasons now.


Could this be related to SELinux. Can you please look at the 
nova-compute logfile - /var/log/nova/compute.log.

Thanks
Gary




On Mon, Feb 11, 2013 at 11:33 AM, Greg Chavez > wrote:



Running latest EPEL Folsom packages on RHEL 6.3.  Three nodes
right now, one controller, one network node, one compute node.
 The network node has three NICs, one for external net, one for
management net, one for VM network traffic.  It has been a
miserable journey so far.

The lastest calamity began with a failed spawn of the Cirros test
image.  I booted it like this:

# nova --os-username demo --os-password demo --os-tenant-name
demoProject boot --image aefa581f-47b0-4d46-8dbc-1a1f7f02dfa0
--flavor 2  --nic net-id=3de1e780-07d1-42af-89cc-0feaf1ece6e9
server-01

This succeeded but went directly into an ERROR state.  The compute
node's /var/log/nova/compute.log showed this:

ProcessExecutionError: Unexpected error while running command.
Command: sudo nova-rootwrap /etc/nova/rootwrap.conf brctl addbr
qbr2218b8c4-7d
Exit code: 1
Stdout: ''
Stderr: 'add bridge failed: Package not installed\n'

Hrm.  So then I ran this:

# brctl show
bridge namebridge idSTP enabledinterfaces
br-eth1/sys/class/net/br-eth1/bridge: No such file or directory
/sys/class/net/br-eth1/bridge: No such file or directory
/sys/class/net/br-eth1/bridge: No such file or directory
/sys/class/net/br-eth1/bridge: No such file or directory
/sys/class/net/br-eth1/bridge: No such file or directory
/sys/class/net/br-eth1/bridge: No such file or directory
/sys/class/net/br-eth1/bridge: No such file or directory
/sys/class/net/br-eth1/bridge: No such file or directory
/sys/class/net/br-eth1/bridge: No such file or directory
/sys/class/net/br-eth1/bridge: No such file or directory
/sys/class/net/br-eth1/bridge: No such file or directory
/sys/class/net/br-eth1/bridge: No such file or directory
.bc305befedd1no
br-int/sys/class/net/br-int/bridge: No such file or directory
/sys/class/net/br-int/bridge: No such file or directory
/sys/class/net/br-int/bridge: No such file or directory
/sys/class/net/br-int/bridge: No such file or directory
/sys/class/net/br-int/bridge: No such file or directory
/sys/class/net/br-int/bridge: No such file or directory
/sys/class/net/br-int/bridge: No such file or directory
/sys/class/net/br-int/bridge: No such file or directory
/sys/class/net/br-int/bridge: No such file or directory
/sys/class/net/br-int/bridge: No such file or directory
/sys/class/net/br-int/bridge: No such file or directory
/sys/class/net/br-int/bridge: No such file or directory
.7e1636f42c4bno

GAH!   What!!! First of all, bridge capability is set by default
in the RHEL 6.3 kernel.  Secondly, nova knows that it's supposed
to be using openvswitch.  The ProcessExecutionError's trace showed
that the offending code came
from /usr/lib/python2.6/site-packages/nova/virt/libvirt/vif.py
line 216 which has this comment:

def plug(self, instance, vif):
"""Plug using hybrid strategy

Create a per-VIF linux bridge, then link that bridge to
the OVS
integration bridge via a veth device, setting up the other end
of the veth device just like a normal OVS port.  Then boot the
VIF on the linux bridge using standard libvirt mechanisms
"""

Thirdly, ovs-vsctrl is happy:

# ovs-vsctl show
44435595-8cc8-469c-ace4-ded76a7b864d
Bridge "br-eth1"
Port "br-eth1"
Interface "br-eth1"
type: internal
Port "phy-br-eth1"
Interface "phy-br-eth1"
Port "eth1"
Interface "eth1"
Bridge br-int
Port "int-br-eth1"
Interface "int-br-eth1"
Port br-int
Interface br-int
type: internal
ovs_version: "1.7.3"

Final note, my network node fails the same way, but the controller
does not.

I hope so much that somebody knows what is going on here.  This is
very terrible for me as I am struggling to achieve
minimal functionality.  Thanks.

-- 
\*..+.-

--Greg Chavez
+//..;};




--
\*..+.-
--Greg Chavez
+//..;};


___
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] [SWIFT] code reading

2013-02-12 Thread Kun Huang
Hi, Chmouel and Darrell

I know you're working on /swift/proxy/controllers/base.py for this bug:
https://review.openstack.org/#/c/21563/
I didn't know the
https://github.com/openstack/swift/blob/master/swift/proxy/controllers/base.py#L371
to
#372. Could you show me a simple understanding?

elif resp.status == HTTP_NOT_FOUND:
if result_code == 0:
result_code = HTTP_NOT_FOUND
elif result_code != HTTP_NOT_FOUND:
result_code = -1

In this part, given a 404 response, we should reset the variable
result_code. If result_code is 0, reset it 404, 404 do nothing, and
others set -1.


What's the case for the "-1"?

Furthermore, I simply think resp.status is sufficient condition to set
result_code, so why these judgement need the result_code value in last
loop (while attempts_left loop).



Gareth
___
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] Filter Scheduler options implemented by default

2013-02-12 Thread hate
Hi, Atul

You are right, If you just put 
> compute_scheduler_driver = nova.scheduler.filter_scheduler.FilterScheduler
in nova.conf. And not explicitly set 'scheduler_default_filters', it's value 
will be ['RetryFilter', …,'ImagePropertiesFilter'] default. 

So all your host should pass these Filters.

Best regards,
Adir Gao
在 2013-2-11,下午5:31,Atul Jha  写道:

> Hi All,
> 
> I wanted help regarding the nova scheduler options. If i am not passing any 
> options inside my nova.conf apart from
> 
> compute_scheduler_driver = nova.scheduler.filter_scheduler.FilterScheduler
> 
> As per the default options 
> https://github.com/openstack/nova/blob/master/nova/scheduler/host_manager.py#L32
>  (thanks garyk)
> 
> will all these filter rules will be processed
> 
> 
> fg.ListOpt('scheduler_default_filters',
>default=[
>  'RetryFilter',
>  'AvailabilityZoneFilter',
>  'RamFilter',
>  'ComputeFilter',
>  'ComputeCapabilitiesFilter',
>  'ImagePropertiesFilter'
>  ],
>help='Which filter class names to use for filtering hosts '
>  'when not specified in the request.'),
> 
> Let me know if am understanding it correctly. So by default my all host will 
> go through all above filtering types. :)
> 
> Thanks!!
> 
> Atul Jha
> http://www.csscorp.com/common/email-disclaimer.php
> 
> ___
> 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] Getting the 2012.2.3 release in Ubuntu

2013-02-12 Thread Logan McNaughton
Yep I know how to use the Ubuntu Cloud Archive, however according to
openstack.org the latest version is 2012.2.3, the Ubuntu Cloud Archive has:

2012.2.1+stable-20121212-a99a802e-0ubuntu1.1~cloud0

So I'm wondering why the Ubuntu Cloud Archive doesn't have 2012.2.3?



On Tue, Feb 12, 2013 at 5:47 AM, Silvan Kaiser  wrote:

> Hello!
> We use the same setup, 12.04 and cloud archive. Following the instructions
> on https://wiki.ubuntu.com/ServerTeam/CloudArchive works ok here.
>
> If you updated sources.list, did you install the ubuntu-cloud-keyring?
> (see the url above)
>
> Cheers
> Silvan
>
>
>
> Am 11.02.2013 um 21:48 schrieb Logan McNaughton :
>
> Hi,
>
> I've added the Ubuntu Cloud Archive to my apt sources, however it looks
> like the latest release there is 2012.2.1.
>
> How can I get the latest 2012.2.3 release in Ubuntu 12.04?
>  ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
> *
>
> *
> *-- *
> *Silvan Kaiser*
> Dipl.-Inform.
> ** **
> Researcher
> Competence Center Agent Core Technologies
> ** **
> silvan.kaiser 
> @dai-labor.de
> Fon +49 (0) 30/314 -74 035
> Fax +49 (0) 30/314 -74 003
> ** **
> *Future in touch.*
> ** **
> *DAI-Labor*
> Technische Universität Berlin
> Fakultät IV – Elektrotechnik & Informatik
> Sekretariat TEL 14
> Ernst-Reuter-Platz 7
> 10587 Berlin, Germany
> ** **
> www.dai-labor.de
> ** **
> DAI-Labor - Distributed Artificial Intelligence Laboratory
> Chief Executive Director: Prof. Dr. Dr. h.c. Sahin Albayrak
>
>
___
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] Horizon Keystone Endpoint Issue

2013-02-12 Thread Logan McNaughton
I've had this problem before, in my experience it's not a problem with
keystone, it's a problem with nova (by the looks of the traceback). I
believe it's a bug in Horizon because you'll find a lot of people with this
issue if you Google it. I don't have an answer on how to fix it, other than
don't fixate on the "EndpointNotFound", look to your nova configs for a
solution.


On Tue, Feb 12, 2013 at 5:03 AM, Trinath Somanchi <
trinath.soman...@gmail.com> wrote:

> Hi Stackers-
>
> I have successfully installed folsom in my test setup.
> But when I browse Horison, with admin/password as credentials, I get this
> error.
>
> [Tue Feb 12 10:03:16 2013] [error] unable to retrieve service catalog with
> token
> [Tue Feb 12 10:03:16 2013] [error] Traceback (most recent call last):
> [Tue Feb 12 10:03:16 2013] [error]   File
> "/usr/lib/python2.7/dist-packages/keystoneclient/v2_0/client.py", line 132,
> in _extract_service_catalog
> [Tue Feb 12 10:03:16 2013] [error] endpoint_type='adminURL')
> [Tue Feb 12 10:03:16 2013] [error]   File
> "/usr/lib/python2.7/dist-packages/keystoneclient/service_catalog.py", line
> 62, in url_for
> [Tue Feb 12 10:03:16 2013] [error] raise
> exceptions.EndpointNotFound('Endpoint not found.')
> [Tue Feb 12 10:03:16 2013] [error] EndpointNotFound: Endpoint not found.
> [Tue Feb 12 10:03:17 2013] [error] \x1b[31;1mUnauthorized: n/a (HTTP
> 401)\x1b[0m
> [Tue Feb 12 10:03:17 2013] [error] Traceback (most recent call last):
> [Tue Feb 12 10:03:17 2013] [error]   File
> "/usr/lib/python2.7/dist-packages/horizon/usage/base.py", line 93, in
> summarize
> [Tue Feb 12 10:03:17 2013] [error] self.usage_list =
> self.get_usage_list(start, end)
> [Tue Feb 12 10:03:17 2013] [error]   File
> "/usr/lib/python2.7/dist-packages/horizon/usage/base.py", line 128, in
> get_usage_list
> [Tue Feb 12 10:03:17 2013] [error] return api.usage_list(self.request,
> start, end)
> [Tue Feb 12 10:03:17 2013] [error]   File
> "/usr/lib/python2.7/dist-packages/horizon/api/nova.py", line 418, in
> usage_list
> [Tue Feb 12 10:03:17 2013] [error] return [Usage(u) for u in
> novaclient(request).usage.list(start, end, True)]
> [Tue Feb 12 10:03:17 2013] [error]   File
> "/usr/lib/python2.7/dist-packages/novaclient/v1_1/usage.py", line 35, in
> list
> [Tue Feb 12 10:03:17 2013] [error] "tenant_usages")
> [Tue Feb 12 10:03:17 2013] [error]   File
> "/usr/lib/python2.7/dist-packages/novaclient/base.py", line 62, in _list
> [Tue Feb 12 10:03:17 2013] [error] _resp, body =
> self.api.client.get(url)
> [Tue Feb 12 10:03:17 2013] [error]   File
> "/usr/lib/python2.7/dist-packages/novaclient/client.py", line 239, in get
> [Tue Feb 12 10:03:17 2013] [error] return self._cs_request(url, 'GET',
> **kwargs)
> [Tue Feb 12 10:03:17 2013] [error]   File
> "/usr/lib/python2.7/dist-packages/novaclient/client.py", line 236, in
> _cs_request
> [Tue Feb 12 10:03:17 2013] [error] raise ex
> [Tue Feb 12 10:03:17 2013] [error] Unauthorized: n/a (HTTP 401)
>
> It says , I missed some End point Configuration.
>
> But then, I have configured it correctly.
>
> Can any one guide me resolving this issue.
>
> Thanks in advance.
>
> --
> Regards,
> --
> Trinath Somanchi,
> +91 9866 235 130
>
> ___
> 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] Filter Scheduler options implemented by default

2013-02-12 Thread Atul Jha
Thanks a lot Adir Gao



From: hate [gtt...@126.com]
Sent: Tuesday, February 12, 2013 9:03 PM
To: Atul Jha
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] Filter Scheduler options implemented by default

Hi, Atul

You are right, If you just put
> compute_scheduler_driver = nova.scheduler.filter_scheduler.FilterScheduler
in nova.conf. And not explicitly set 'scheduler_default_filters', it's value 
will be ['RetryFilter', …,'ImagePropertiesFilter'] default.

So all your host should pass these Filters.

Best regards,
Adir Gao
在 2013-2-11,下午5:31,Atul Jha  写道:

> Hi All,
>
> I wanted help regarding the nova scheduler options. If i am not passing any 
> options inside my nova.conf apart from
>
> compute_scheduler_driver = nova.scheduler.filter_scheduler.FilterScheduler
>
> As per the default options 
> https://github.com/openstack/nova/blob/master/nova/scheduler/host_manager.py#L32
>  (thanks garyk)
>
> will all these filter rules will be processed
>
>
> fg.ListOpt('scheduler_default_filters',
>default=[
>  'RetryFilter',
>  'AvailabilityZoneFilter',
>  'RamFilter',
>  'ComputeFilter',
>  'ComputeCapabilitiesFilter',
>  'ImagePropertiesFilter'
>  ],
>help='Which filter class names to use for filtering hosts '
>  'when not specified in the request.'),
>
> Let me know if am understanding it correctly. So by default my all host will 
> go through all above filtering types. :)
>
> Thanks!!
>
> Atul Jha
> http://www.csscorp.com/common/email-disclaimer.php
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp

http://www.csscorp.com/common/email-disclaimer.php

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

2013-02-12 Thread Paras pradhan
Hi,

I have two nodes. A controller node and a compute. Both has 2 nics , eth0
is public and eth1 is private with no ip on it.  Compute node has
nova-network and nova-compute . nova-api runs on both servers. I can see
br100 up in compute node.

Thanks in advance.
Paras.

On Tue, Feb 12, 2013 at 2:38 AM, Razique Mahroua
wrote:

> Hi,
> what is your current network model?
> thanks
>
> *Razique Mahroua** - **Nuage & Co*
> razique.mahr...@gmail.com
> Tel : +33 9 72 37 94 15
>
>
> Le 12 févr. 2013 à 00:25, Paras pradhan  a écrit :
>
> Hi,
>
> The packages I am using are from folsom ubuntu quantal branch.  When I
> run an instance I see
>
> --
> wget: can't connect to remote host (169.254.169.254): Network is
> unreachable
> --
>
> this might be the network issue as well.
>
> nova list shows my instance .  I am running nova-network on compute
> node. nova-api is running on both controller and compute nodes.
>
> I have seen lot of ppl are having issues on this but i was not able to
> find out the issue by looking at their posts.
>
> How do I start debugging?
>
> Thanks
> Paras.
>
> ___
> 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] change: Saturday 2/16 wiki migration date

2013-02-12 Thread Anne Gentle
Hi all,

We are moving the migration to 2/16 instead of 2/17 due to scheduling
constraints. We'll continue clean up on Sunday and Monday.

Thanks,
Anne


On Tue, Jan 29, 2013 at 4:13 PM, Anne Gentle  wrote:

> Hi all -
> The wiki migration date is set for Sunday February 17. The Infrastructure
> team will perform the changeover that day, then cleanup begins. We don't
> expect downtime other than DNS change over, but we are asking you all to
> take part in a clean up on Sunday and Monday  (which happens to be a U.S.
> President's day, so if your kids are home  from school, put them to work!
> Just kidding.)
>
> On any wiki page you care for, here's a checklist for the migration:
>
>  - Ensure table formats are correct. This task may require some manual
> cleanup, though these look clean to me at a glance.
>  - The Table of Contents macro must be replaced with "__TOC__" or you can
> further customize it, see
> https://www.mediawiki.org/wiki/Manual:Table_of_contents.
>  - Columns with the column macro will not migrate -- you must convert to
> table markup with border=0.
>  - Ensure your videos play back correctly - Ryan is implementing a macro
> for the embedded YouTube videos. Other videos are simply linked, not
> embedded.
>  - Ensure images display correctly. For example, embedded JPGs using {{
> http://link.to.image/image.jpg}} links will not migrate correctly.
>  - Some links will not migrate correctly, for example Moin was more
> forgiving with spaces after the | symbol indicating a link. So, the top
> link example migrates incorrectly, the bottom does link correctly after
> migration:
>* [[HowToContribute | How to Contribute ]]
>* Sign the [[CLA|Contributor agreement]]
>
> If you have any questions, don't hesitate to ask.
>
> Thanks,
> Anne
>
>
>
___
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] Chicago-land Stackers

2013-02-12 Thread Steve Loving
Hi - If you are in the Chicago-land area, please join the Chicago-land
OpenStack Group Meetup.

http://www.meetup.com/meetup-group-NjZdcegA/

We have an outstanding meeting planned for Feb 28th !

-- 
Best Regards,



 Steven Loving
 818-725-1329 X5683
 847.736.3111 (mobile)
 http://www.metacloud.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] metadata issue

2013-02-12 Thread Paras pradhan
iptables -A POSTROUTING -t mangle -p udp --dport 68 -j CHECKSUM
--checksum-fill

fixed the issue.

Paras.


On Tue, Feb 12, 2013 at 10:03 AM, Paras pradhan wrote:

> Hi,
>
> I have two nodes. A controller node and a compute. Both has 2 nics , eth0
> is public and eth1 is private with no ip on it.  Compute node has
> nova-network and nova-compute . nova-api runs on both servers. I can see
> br100 up in compute node.
>
> Thanks in advance.
> Paras.
>
>
> On Tue, Feb 12, 2013 at 2:38 AM, Razique Mahroua <
> razique.mahr...@gmail.com> wrote:
>
>> Hi,
>> what is your current network model?
>> thanks
>>
>> *Razique Mahroua** - **Nuage & Co*
>> razique.mahr...@gmail.com
>> Tel : +33 9 72 37 94 15
>>
>>
>> Le 12 févr. 2013 à 00:25, Paras pradhan  a écrit
>> :
>>
>> Hi,
>>
>> The packages I am using are from folsom ubuntu quantal branch.  When I
>> run an instance I see
>>
>> --
>> wget: can't connect to remote host (169.254.169.254): Network is
>> unreachable
>> --
>>
>> this might be the network issue as well.
>>
>> nova list shows my instance .  I am running nova-network on compute
>> node. nova-api is running on both controller and compute nodes.
>>
>> I have seen lot of ppl are having issues on this but i was not able to
>> find out the issue by looking at their posts.
>>
>> How do I start debugging?
>>
>> Thanks
>> Paras.
>>
>> ___
>> 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] openstack client question

2013-02-12 Thread Dean Troyer
On Tue, Feb 12, 2013 at 5:32 PM, Miller, Mark M (EB SW Cloud - R&D -
Corvallis)  wrote:

>   I recently installed the latest openstackclient hoping to find support
> for the new Grizzly V3 Keystone commands (i.e. groups, domains,
> credentials, etc.). Will these commands be added to the client in the
> future or will we need to use the curl command to execute REST calls
> against the Keystone APIs?
>

openstackclient is very much a work-in-progress overall, as are the
Identity v3 commands. group and project are present but you have to specify
the Identity API version 3 to use them: --os-identity-api-version=3 on the
command line or OS_IDENTITY_API_VERSION=3 in the environment).

Steve has a proposal at https://review.openstack.org/20854 that supports
credential, domain and policy objects but IIRC it needs some updates for
both the entrypoint changes from last week and possibly some recent API
changes.

dt

-- 

Dean Troyer
dtro...@gmail.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] brctl meltdown on RHEL 6.3

2013-02-12 Thread Fr34k8
Greetz all

Same here on gentoo

Am 12.02.2013 um 11:38 schrieb Gary Kotton :

> On 02/11/2013 07:26 PM, Greg Chavez wrote:
>> 
>> Solution:
>> 
>> [root@kvm-cs-sn-10i nova]# modprobe -r brcompat
>> [root@kvm-cs-sn-10i nova]# modprobe bridge
>> [root@kvm-cs-sn-10i nova]# brctl show
>> bridge name bridge id STP enabled interfaces
>> 
>> Still can't boot a VM... looking into the reasons now.
> 
> Could this be related to SELinux. Can you please look at the nova-compute 
> logfile - /var/log/nova/compute.log.
> Thanks
> Gary
> 
>> 
>> 
>> On Mon, Feb 11, 2013 at 11:33 AM, Greg Chavez  wrote:
>>> 
>>> Running latest EPEL Folsom packages on RHEL 6.3.  Three nodes right now, 
>>> one controller, one network node, one compute node.  The network node has 
>>> three NICs, one for external net, one for management net, 
>>> one for VM network traffic.  It has been a miserable journey so far.
>>> 
>>> The lastest calamity began with a failed spawn of the Cirros test image.  I 
>>> booted it like this:
>>> 
>>> # nova --os-username demo --os-password demo --os-tenant-name demoProject 
>>> boot --image aefa581f-47b0-4d46-8dbc-1a1f7f02dfa0 --flavor 2  --nic 
>>> net-id=3de1e780-07d1-42af-89cc-0feaf1ece6e9 server-01
>>> 
>>> This succeeded but went directly into an ERROR state.  The compute node's 
>>> /var/log/nova/compute.log showed this:
>>> 
>>> ProcessExecutionError: Unexpected error while running command.
>>> Command: sudo nova-rootwrap /etc/nova/rootwrap.conf brctl addbr 
>>> qbr2218b8c4-7d
>>> Exit code: 1
>>> Stdout: ''
>>> Stderr: 'add bridge failed: Package not installed\n'
>>> 
>>> Hrm.  So then I ran this:
>>> 
>>> # brctl show
>>> bridge name bridge id STP enabled interfaces
>>> br-eth1 /sys/class/net/br-eth1/bridge: No such file or directory
>>> /sys/class/net/br-eth1/bridge: No such file or directory
>>> /sys/class/net/br-eth1/bridge: No such file or directory
>>> /sys/class/net/br-eth1/bridge: No such file or directory
>>> /sys/class/net/br-eth1/bridge: No such file or directory
>>> /sys/class/net/br-eth1/bridge: No such file or directory
>>> /sys/class/net/br-eth1/bridge: No such file or directory
>>> /sys/class/net/br-eth1/bridge: No such file or directory
>>> /sys/class/net/br-eth1/bridge: No such file or directory
>>> /sys/class/net/br-eth1/bridge: No such file or directory
>>> /sys/class/net/br-eth1/bridge: No such file or directory
>>> /sys/class/net/br-eth1/bridge: No such file or directory
>>> .bc305befedd1
>>>   no 
>>> br-int /sys/class/net/br-int/bridge: No such file or directory
>>> /sys/class/net/br-int/bridge: No such file or directory
>>> /sys/class/net/br-int/bridge: No such file or directory
>>> /sys/class/net/br-int/bridge: No such file or directory
>>> /sys/class/net/br-int/bridge: No such file or directory
>>> /sys/class/net/br-int/bridge: No such file or directory
>>> /sys/class/net/br-int/bridge: No such file or directory
>>> /sys/class/net/br-int/bridge: No such file or directory
>>> /sys/class/net/br-int/bridge: No such file or directory
>>> /sys/class/net/br-int/bridge: No such file or directory
>>> /sys/class/net/br-int/bridge: No such file or directory
>>> /sys/class/net/br-int/bridge: No such file or directory
>>> .7e1636f42c4b
>>>   no
>>> 
>>> GAH!   What!!! First of all, bridge capability is set by default in the 
>>> RHEL 6.3 kernel.  Secondly, nova   knows that it's supposed 
>>> to be using openvswitch.  The ProcessExecutionError's trace showed that the 
>>> offending code came from 
>>> /usr/lib/python2.6/site-packages/nova/virt/libvirt/vif.py line 216 which 
>>> has this comment:
>>> 
>>> def plug(self, instance, vif):
>>> """Plug using hybrid strategy
>>> 
>>> Create a per-VIF linux bridge, then link that bridge to the OVS
>>> integration bridge via a veth device, setting up the other end
>>> of the veth device just like a normal OVS port.  Then boot the
>>> VIF on the linux bridge using standard libvirt mechanisms
>>> """
>>> 
>>> Thirdly, ovs-vsctrl is happy:
>>> 
>>> # ovs-vsctl show
>>> 44435595-8cc8-469c-ace4-ded76a7b864d
>>> Bridge "br-eth1"
>>> Port "br-eth1"
>>> Interface "br-eth1"
>>> type: internal
>>> Port "phy-br-eth1"
>>> Interface "phy-br-eth1"
>>> Port "eth1"
>>> Interface "eth1"
>>> Bridge br-int
>>> Port "int-br-eth1"
>>> Interface "int-br-eth1"
>>> Port br-int
>>> Interface br-int
>>> type: internal
>>> ovs_version: "1.7.3"
>>> 
>>> Final note, my network node fails the same way, but the controller does not.
>>> 
>>> I hope so much that somebody knows what is going on here.  This is very 
>>> terrible for me as I am struggling to achieve minimal functionality.  
>>> Thanks.
>>> 
>>> -- 
>>> \*..+.-
>>> --Greg Chavez
>>> +//..;};
>> 
>> 
>> 
>> -- 
>> \*..+.-
>> --Greg Chavez
>> +//..;};
>

Re: [Openstack] brctl meltdown on RHEL 6.3

2013-02-12 Thread vvdbzhi
Before a found this problem, it is said that is rhel (centos) 6.3 does not 
support the openvswitch brcompat module and bridge module used at the same time

在 2013-2-13,上午10:08,Fr34k8  写道:

> Greetz all
> 
> Same here on gentoo
> 
> Am 12.02.2013 um 11:38 schrieb Gary Kotton :
> 
>> On 02/11/2013 07:26 PM, Greg Chavez wrote:
>>> 
>>> Solution:
>>> 
>>> [root@kvm-cs-sn-10i nova]# modprobe -r brcompat
>>> [root@kvm-cs-sn-10i nova]# modprobe bridge
>>> [root@kvm-cs-sn-10i nova]# brctl show
>>> bridge name bridge id STP enabled interfaces
>>> 
>>> Still can't boot a VM... looking into the reasons now.
>> 
>> Could this be related to SELinux. Can you please look at the nova-compute 
>> logfile - /var/log/nova/compute.log.
>> Thanks
>> Gary
>> 
>>> 
>>> 
>>> On Mon, Feb 11, 2013 at 11:33 AM, Greg Chavez  wrote:
>>> 
>>> Running latest EPEL Folsom packages on RHEL 6.3.  Three nodes right now, 
>>> one controller, one network node, one compute node.  The network node has 
>>> three NICs, one for external net, one for management net, one for VM 
>>> network traffic.  It has been a miserable journey so far.
>>> 
>>> The lastest calamity began with a failed spawn of the Cirros test image.  I 
>>> booted it like this:
>>> 
>>> # nova --os-username demo --os-password demo --os-tenant-name demoProject 
>>> boot --image aefa581f-47b0-4d46-8dbc-1a1f7f02dfa0 --flavor 2  --nic 
>>> net-id=3de1e780-07d1-42af-89cc-0feaf1ece6e9 server-01
>>> 
>>> This succeeded but went directly into an ERROR state.  The compute node's 
>>> /var/log/nova/compute.log showed this:
>>> 
>>> ProcessExecutionError: Unexpected error while running command.
>>> Command: sudo nova-rootwrap /etc/nova/rootwrap.conf brctl addbr 
>>> qbr2218b8c4-7d
>>> Exit code: 1
>>> Stdout: ''
>>> Stderr: 'add bridge failed: Package not installed\n'
>>> 
>>> Hrm.  So then I ran this:
>>> 
>>> # brctl show
>>> bridge name bridge id STP enabled interfaces
>>> br-eth1 /sys/class/net/br-eth1/bridge: No such file or directory
>>> /sys/class/net/br-eth1/bridge: No such file or directory
>>> /sys/class/net/br-eth1/bridge: No such file or directory
>>> /sys/class/net/br-eth1/bridge: No such file or directory
>>> /sys/class/net/br-eth1/bridge: No such file or directory
>>> /sys/class/net/br-eth1/bridge: No such file or directory
>>> /sys/class/net/br-eth1/bridge: No such file or directory
>>> /sys/class/net/br-eth1/bridge: No such file or directory
>>> /sys/class/net/br-eth1/bridge: No such file or directory
>>> /sys/class/net/br-eth1/bridge: No such file or directory
>>> /sys/class/net/br-eth1/bridge: No such file or directory
>>> /sys/class/net/br-eth1/bridge: No such file or directory
>>> .bc305befedd1
>>>   no 
>>> br-int /sys/class/net/br-int/bridge: No such file or directory
>>> /sys/class/net/br-int/bridge: No such file or directory
>>> /sys/class/net/br-int/bridge: No such file or directory
>>> /sys/class/net/br-int/bridge: No such file or directory
>>> /sys/class/net/br-int/bridge: No such file or directory
>>> /sys/class/net/br-int/bridge: No such file or directory
>>> /sys/class/net/br-int/bridge: No such file or directory
>>> /sys/class/net/br-int/bridge: No such file or directory
>>> /sys/class/net/br-int/bridge: No such file or directory
>>> /sys/class/net/br-int/bridge: No such file or directory
>>> /sys/class/net/br-int/bridge: No such file or directory
>>> /sys/class/net/br-int/bridge: No such file or directory
>>> .7e1636f42c4b
>>>   no
>>> 
>>> GAH!   What!!! First of all, bridge capability is set by default in the 
>>> RHEL 6.3 kernel.  Secondly, nova knows that it's supposed to be using 
>>> openvswitch.  The ProcessExecutionError's trace showed that the offending 
>>> code came from /usr/lib/python2.6/site-packages/nova/virt/libvirt/vif.py 
>>> line 216 which has this comment:
>>> 
>>> def plug(self, instance, vif):
>>> """Plug using hybrid strategy
>>> 
>>> Create a per-VIF linux bridge, then link that bridge to the OVS
>>> integration bridge via a veth device, setting up the other end
>>> of the veth device just like a normal OVS port.  Then boot the
>>> VIF on the linux bridge using standard libvirt mechanisms
>>> """
>>> 
>>> Thirdly, ovs-vsctrl is happy:
>>> 
>>> # ovs-vsctl show
>>> 44435595-8cc8-469c-ace4-ded76a7b864d
>>> Bridge "br-eth1"
>>> Port "br-eth1"
>>> Interface "br-eth1"
>>> type: internal
>>> Port "phy-br-eth1"
>>> Interface "phy-br-eth1"
>>> Port "eth1"
>>> Interface "eth1"
>>> Bridge br-int
>>> Port "int-br-eth1"
>>> Interface "int-br-eth1"
>>> Port br-int
>>> Interface br-int
>>> type: internal
>>> ovs_version: "1.7.3"
>>> 
>>> Final note, my network node fails the same way, but the controller does not.
>>> 
>>> I hope so much that somebody knows what is going on here.  This is very 
>>> terrible for me a

[Openstack] [nova] python-novaclient 2.11.0 release

2013-02-12 Thread Vishvananda Ishaya
Hello Everyone,

I just pushed version 2.11.0 of python-novaclient to Pypi. There are a lot of 
fixes and features in this release. Here is a brief overview:

Bug Fixes
-

private key files now created with 400 permissions
nova quota-show now uses current tenant by default
nova live-migration supports automatic dest host
fixed bash completion on osx
simplified keyring support
fixed for keypair-add to expand homedir
improved instance fault printing
fixed for prettytable 6.1
fixed tls support
fixed alphanumeric flavor ids
improved search by name for nova list
added support for missing quota types
fixed nova boot nics support with bdm

Feature Support
---
nova usage (folsom)
nova boot --image-with (folsom)
nova boot --num-instances (folsom)
nova availability-zone-list (grizzly)
nova get-spice-console (grizzly)
nova get-password (grizzly)
nova net-list (grizzly)
nova evacuate (grizzly admin)
nova coverage-report (grizzly admin)
nova manage agent-* (grizzly admin)
nova network-create/(dis)associate/ (grizzly admin)
nova floating-ip-bulk-* (grizzly admin)
nova scrub (grizzly admin)
nova baremetal-* (grizzly admin)

As always bugs can be reported at: https://bugs.launchpad.net/python-novaclient

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