date:20130709

Re: [Openstack] [SWIFT] raising network traffic on the storage node

2013-07-09 Thread Robert van Leeuwen

 If the replication traffic is responsible for this raising network traffic 
 for only 1.200.000 objects, how much traffic I can 
 expect if I have 100.000.000 objects stored?
 The average size of my mailobjects are 120 kB. 
 It's planned to use all 12 hard drive slots of my DELL R720xd with 4  TB 
 drives
. I have 5 storage nodes and 2 balanced proxy nodes. Will the replication 
traffic kill my system?

We are running with   400.000.000 objects  across 11 object storage nodes.
Total network traffic on any of those nodes is less then 10 MByte /second

However we have seen slowdowns with lots of small files and really big disks.
The issue is not related to the network but the local filesystem/disk.
When the inode cache gets insufficient you can see terrible slow-downs.
There have been a few threads about that in this list, having a lot of memory 
usually helps a bit.

Cheers,
Robert van Leeuwen
___
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] error while creating instance on nfs share

2013-07-09 Thread JuanFra Rodriguez Cardoso

Diablo release? I'd recommend you use the lastest release for live
migrations:

http://docs.openstack.org/trunk/openstack-compute/admin/content/configuring-live-migrations.html

Regards,
---
JuanFra


2013/7/8 Chathura M. Sarathchandra Magurawalage 77.chath...@gmail.com

 Hello al,

 I followed the Openstack instructions for enabling vm migration   (
 http://docs.openstack.org/diablo/openstack-compute/admin/content/configuring-live-migrations.html
  )

 But I can not get it working, since when I create an instance I get the
 following error on the compute node.

 2013-07-08 17:01:34 9329 ERROR nova.openstack.common.rpc.amqp [-]
 Exception during message handling
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp Traceback
 (most recent call last):
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/amqp.py, line
 276, in _process_data
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp rval =
 self.proxy.dispatch(ctxt, version, method, **args)
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/dispatcher.py,
 line 145, in dispatch
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp return
 getattr(proxyobj, method)(ctxt, **kwargs)
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/exception.py, line 117, in wrapped
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp
 temp_level, payload)
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/contextlib.py, line 24, in __exit__
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp
 self.gen.next()
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/exception.py, line 92, in wrapped
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp return
 f(*args, **kw)
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 176, in
 decorated_function
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp pass
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/contextlib.py, line 24, in __exit__
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp
 self.gen.next()
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 162, in
 decorated_function
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp return
 function(self, context, *args, **kwargs)
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 197, in
 decorated_function
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp
 kwargs['instance']['uuid'], e, sys.exc_info())
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/contextlib.py, line 24, in __exit__
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp
 self.gen.next()
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 191, in
 decorated_function
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp return
 function(self, context, *args, **kwargs)
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 839, in
 run_instance
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp
 do_run_instance()
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/utils.py, line 803, in inner
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp retval =
 f(*args, **kwargs)
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 838, in
 do_run_instance
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp
 admin_password, is_first_time, instance)
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 529, in
 _run_instance
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp
 self._set_instance_error_state(context, instance['uuid'])
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/contextlib.py, line 24, in __exit__
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp
 self.gen.next()
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 517, in
 _run_instance
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp
 is_first_time, request_spec, filter_properties)
 2013-07-08

[Openstack] which API can do these?

2013-07-09 Thread Peter Cheung

Hi All  which API can do these?
1) adjust the RAM size, no of CPU core to an instance2) enlarge a disk to an 
instance3) get the information about ram/cpu/disk size of an instance

Thanksfrom Peter  ___
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] error while creating instance on nfs share

2013-07-09 Thread Chathura M. Sarathchandra Magurawalage

I am using Folsom release.

I have followed the instruction on that page.


On 9 July 2013 10:57, JuanFra Rodriguez Cardoso 
juanfra.rodriguez.card...@gmail.com wrote:

 Diablo release? I'd recommend you use the lastest release for live
 migrations:


 http://docs.openstack.org/trunk/openstack-compute/admin/content/configuring-live-migrations.html

 Regards,
 ---
 JuanFra


 2013/7/8 Chathura M. Sarathchandra Magurawalage 77.chath...@gmail.com

  Hello al,

 I followed the Openstack instructions for enabling vm migration   (
 http://docs.openstack.org/diablo/openstack-compute/admin/content/configuring-live-migrations.html
  )

 But I can not get it working, since when I create an instance I get the
 following error on the compute node.

 2013-07-08 17:01:34 9329 ERROR nova.openstack.common.rpc.amqp [-]
 Exception during message handling
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp Traceback
 (most recent call last):
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/amqp.py, line
 276, in _process_data
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp rval =
 self.proxy.dispatch(ctxt, version, method, **args)
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/dispatcher.py,
 line 145, in dispatch
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp return
 getattr(proxyobj, method)(ctxt, **kwargs)
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/exception.py, line 117, in wrapped
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp
 temp_level, payload)
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/contextlib.py, line 24, in __exit__
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp
 self.gen.next()
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/exception.py, line 92, in wrapped
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp return
 f(*args, **kw)
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 176, in
 decorated_function
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp pass
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/contextlib.py, line 24, in __exit__
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp
 self.gen.next()
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 162, in
 decorated_function
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp return
 function(self, context, *args, **kwargs)
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 197, in
 decorated_function
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp
 kwargs['instance']['uuid'], e, sys.exc_info())
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/contextlib.py, line 24, in __exit__
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp
 self.gen.next()
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 191, in
 decorated_function
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp return
 function(self, context, *args, **kwargs)
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 839, in
 run_instance
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp
 do_run_instance()
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/utils.py, line 803, in inner
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp retval
 = f(*args, **kwargs)
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 838, in
 do_run_instance
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp
 admin_password, is_first_time, instance)
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 529, in
 _run_instance
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp
 self._set_instance_error_state(context, instance['uuid'])
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/contextlib.py, line 24, in __exit__
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp
 self.gen.next()
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File

[Openstack] Grizzly Compute gives error

2013-07-09 Thread raghavendra.lad



Hi,

I have tried the below link to install.
https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_MultiNode/OpenStack_Grizzly_Install_Guide.rst

In my Nova-conf I have substituted for 192.168.22.4 instead of 10.10.10.53 
under Vnc configuration

Vi /etc/nova/nova.conf   (My Compute node) All other nodes work fine.

Under the below para.

 *   # Vnc configuration
 *   novnc_enabled=true
 *   novncproxy_base_url=http://192.168.100.51:6080/vnc_auto.html
 *   novncproxy_port=6080
 *   vncserver_proxyclient_address=10.10.10.53
 *   vncserver_listen=0.0.0.0
 *




The screen shot of error message

[cid:image001.png@01CE7CBA.5DCC8990]



Regards,
Raghavendra Lad


This message is for the designated recipient only and may contain privileged, 
proprietary, or otherwise confidential information. If you have received it in 
error, please notify the sender immediately and delete the original. Any other 
use of the e-mail by you is prohibited.

Where allowed by local law, electronic communications with Accenture and its 
affiliates, including e-mail and instant messaging (including content), may be 
scanned by our systems for the purposes of information security and assessment 
of internal compliance with Accenture policy.

__

www.accenture.com
inline: image001.png___
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] error while creating instance on nfs share

2013-07-09 Thread JuanFra Rodriguez Cardoso

and
http://openstack-folsom-install-guide.readthedocs.org/en/latest/#setup-live-migration?

---
JuanFra


2013/7/9 Chathura M. Sarathchandra Magurawalage 77.chath...@gmail.com

 I am using Folsom release.

 I have followed the instruction on that page.


 On 9 July 2013 10:57, JuanFra Rodriguez Cardoso 
 juanfra.rodriguez.card...@gmail.com wrote:

 Diablo release? I'd recommend you use the lastest release for live
 migrations:


 http://docs.openstack.org/trunk/openstack-compute/admin/content/configuring-live-migrations.html

 Regards,
 ---
 JuanFra


 2013/7/8 Chathura M. Sarathchandra Magurawalage 77.chath...@gmail.com

  Hello al,

 I followed the Openstack instructions for enabling vm migration   (
 http://docs.openstack.org/diablo/openstack-compute/admin/content/configuring-live-migrations.html
  )

 But I can not get it working, since when I create an instance I get the
 following error on the compute node.

 2013-07-08 17:01:34 9329 ERROR nova.openstack.common.rpc.amqp [-]
 Exception during message handling
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp Traceback
 (most recent call last):
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/amqp.py, line
 276, in _process_data
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp rval =
 self.proxy.dispatch(ctxt, version, method, **args)
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/dispatcher.py,
 line 145, in dispatch
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp return
 getattr(proxyobj, method)(ctxt, **kwargs)
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/exception.py, line 117, in wrapped
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp
 temp_level, payload)
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/contextlib.py, line 24, in __exit__
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp
 self.gen.next()
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/exception.py, line 92, in wrapped
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp return
 f(*args, **kw)
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 176, in
 decorated_function
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp pass
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/contextlib.py, line 24, in __exit__
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp
 self.gen.next()
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 162, in
 decorated_function
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp return
 function(self, context, *args, **kwargs)
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 197, in
 decorated_function
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp
 kwargs['instance']['uuid'], e, sys.exc_info())
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/contextlib.py, line 24, in __exit__
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp
 self.gen.next()
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 191, in
 decorated_function
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp return
 function(self, context, *args, **kwargs)
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 839, in
 run_instance
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp
 do_run_instance()
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/utils.py, line 803, in inner
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp retval
 = f(*args, **kwargs)
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 838, in
 do_run_instance
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp
 admin_password, is_first_time, instance)
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 529, in
 _run_instance
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp
 self._set_instance_error_state(context, instance['uuid'])
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/contextlib.py, line 24, in __exit__

Re: [Openstack] error while creating instance on nfs share

2013-07-09 Thread Razique Mahroua

What backend do you use?

Le 9 juil. 2013 à 12:20, JuanFra Rodriguez Cardoso 
juanfra.rodriguez.card...@gmail.com a écrit :

 and 
 http://openstack-folsom-install-guide.readthedocs.org/en/latest/#setup-live-migration
  ?
 
 ---
 JuanFra
 
 
 2013/7/9 Chathura M. Sarathchandra Magurawalage 77.chath...@gmail.com
 I am using Folsom release.
 
 I have followed the instruction on that page.
 
 
 On 9 July 2013 10:57, JuanFra Rodriguez Cardoso 
 juanfra.rodriguez.card...@gmail.com wrote:
 Diablo release? I'd recommend you use the lastest release for live migrations:
 
 http://docs.openstack.org/trunk/openstack-compute/admin/content/configuring-live-migrations.html
  
 
 Regards,
 ---
 JuanFra
 
 
 2013/7/8 Chathura M. Sarathchandra Magurawalage 77.chath...@gmail.com
 Hello al,
 
 I followed the Openstack instructions for enabling vm migration   ( 
 http://docs.openstack.org/diablo/openstack-compute/admin/content/configuring-live-migrations.html
  )
 
 But I can not get it working, since when I create an instance I get the 
 following error on the compute node.
 
 2013-07-08 17:01:34 9329 ERROR nova.openstack.common.rpc.amqp [-] Exception 
 during message handling
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp Traceback (most 
 recent call last):
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File 
 /usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/amqp.py, line 
 276, in _process_data
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp rval = 
 self.proxy.dispatch(ctxt, version, method, **args)
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File 
 /usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/dispatcher.py, 
 line 145, in dispatch
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp return 
 getattr(proxyobj, method)(ctxt, **kwargs)
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File 
 /usr/lib/python2.7/dist-packages/nova/exception.py, line 117, in wrapped
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp temp_level, 
 payload)
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File 
 /usr/lib/python2.7/contextlib.py, line 24, in __exit__
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp 
 self.gen.next()
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File 
 /usr/lib/python2.7/dist-packages/nova/exception.py, line 92, in wrapped
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp return 
 f(*args, **kw)
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File 
 /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 176, in 
 decorated_function
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp pass
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File 
 /usr/lib/python2.7/contextlib.py, line 24, in __exit__
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp 
 self.gen.next()
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File 
 /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 162, in 
 decorated_function
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp return 
 function(self, context, *args, **kwargs)
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File 
 /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 197, in 
 decorated_function
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp 
 kwargs['instance']['uuid'], e, sys.exc_info())
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File 
 /usr/lib/python2.7/contextlib.py, line 24, in __exit__
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp 
 self.gen.next()
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File 
 /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 191, in 
 decorated_function
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp return 
 function(self, context, *args, **kwargs)
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File 
 /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 839, in 
 run_instance
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp 
 do_run_instance()
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File 
 /usr/lib/python2.7/dist-packages/nova/utils.py, line 803, in inner
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp retval = 
 f(*args, **kwargs)
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File 
 /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 838, in 
 do_run_instance
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp 
 admin_password, is_first_time, instance)
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File 
 /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 529, in 
 _run_instance
 2013-07-08 17:01:34 9329 TRACE

Re: [Openstack] error while creating instance on nfs share

2013-07-09 Thread Michael Still

On Tue, Jul 9, 2013 at 3:27 AM, Chathura M. Sarathchandra Magurawalage
77.chath...@gmail.com wrote:
 Hello al,

 I followed the Openstack instructions for enabling vm migration   (
 http://docs.openstack.org/diablo/openstack-compute/admin/content/configuring-live-migrations.html
 )

 But I can not get it working, since when I create an instance I get the
 following error on the compute node.


[snip]

 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py, line 1310,
 in _create_image
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp
 utils.ensure_tree(basepath(suffix=''))
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/dist-packages/nova/utils.py, line 1367, in ensure_tree
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp
 os.makedirs(path)
 2013-07-08 17:01:34 9329 TRACE nova.openstack.common.rpc.amqp   File
 /usr/lib/python2.7/os.py, line 157, in makedirs

Thanks heaps for including the traceback in your message, it makes
these things much easier to debug.

This looks to me like a permissions problem. The code has tried to
make a directory on your NFS share, and that has failed. Specifically,
this looks like the directory the instance files go into.

What happens if you try to create a directory on the NFS share as the
user that nova is running as?

Cheers,
Michael

--
Rackspace Australia

___
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] [UX] phabriactor/pholio as a possible UX option

2013-07-09 Thread Jaromir Coufal



On 2013/27/06 09:37, Thierry Carrez wrote:

As a data point, Discourse could also be a solution:
http://www.discourse.org/

It's clearly a discussion tool (including pretty advanced threading,
post likes, etc.), and messages can contain images.

See a design discussion for example at:
http://test.ubuntu-discourse.org/t/a-ubuntu-ish-theme-for-the-site/177



Discourse actually looks pretty good. I was playing around that a little 
bit and like it. We can consider labels as categories - not optimal, but 
can work if we have only design discussions. Only problem is that we 
might want to extend the tool for other discussions as well and then it 
will be less optimal.


Do you guys see any other possibilities apart from this one?

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

Re: [Openstack] [SWIFT] raising network traffic on the storage node

2013-07-09 Thread Klaus Schürmann

I measured the network traffic with darkstat:

server  In  Out Total

storagenode1699,118,562 679,077,971 1,378,196,533   
storagenode2168,636,360 165,050,575 333,686,935 
storagenode3166,583,442 164,405,402 330,988,844 
storagenode4164,282,250 163,051,416 327,333,666 
storagenode5164,000,162 162,840,370 326,840,532 
proxynode1  7,339,629   31,253,205  38,592,834  
proxynode2  8,236,128   12,517,594  20,753,722

This is a part of traffic to server storagenode3:

PortIn  Out Total   Syns
600021,055,732  347,350,916 368,406,648 47,388
600119,717,608  18,090,656  37,808,264  31,549
6002494,124 316,830 810,954 883
36905   39,660  2,263   41,923  0
44687   33,056  1,944   35,000  0
47388   31,691  2,467   34,158  0
41999   30,626  1,788   32,414  0
34228   26,552  3,345   29,897  0

Is this correct configured?


-Ursprüngliche Nachricht-
Von: Openstack 
[mailto:openstack-bounces+klaus.schuermann=mediabeam@lists.launchpad.net] 
Im Auftrag von Robert van Leeuwen
Gesendet: Dienstag, 9. Juli 2013 09:09
An: openstack@lists.launchpad.net
Betreff: Re: [Openstack] [SWIFT] raising network traffic on the storage node

 If the replication traffic is responsible for this raising network traffic 
 for only 1.200.000 objects, how much traffic I can 
 expect if I have 100.000.000 objects stored?
 The average size of my mailobjects are 120 kB. 
 It's planned to use all 12 hard drive slots of my DELL R720xd with 4  TB 
 drives
. I have 5 storage nodes and 2 balanced proxy nodes. Will the replication 
traffic kill my system?

We are running with   400.000.000 objects  across 11 object storage nodes.
Total network traffic on any of those nodes is less then 10 MByte /second

However we have seen slowdowns with lots of small files and really big disks.
The issue is not related to the network but the local filesystem/disk.
When the inode cache gets insufficient you can see terrible slow-downs.
There have been a few threads about that in this list, having a lot of memory 
usually helps a bit.

Cheers,
Robert van Leeuwen
___
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] Networking with Nova

2013-07-09 Thread othmane

Hi all,

 

Im newbie to openstack, my question is: when I create an instance via nova,
can I specify which network the instance should e attached to? For example,
suppose that I have three VM in a compute node each of them is attached to a
network 1,2,3, I want to add the fourth one and specify that this VM should
be attached in network 2. How can I do that?

 

I have another question about understanding Openstack: what is the
difference between the compute node and the openstack controller in the case
of Nova? According to my understanding, the compute node is the physical or
virtual machine where the virtual servers are running, right? 

 

Thinks a lot, any help would be appreciated.

___
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 kernel parameters

2013-07-09 Thread Hao Wang

Hi experts,

I am thinking there is a situation when OpenStack has been deployed but the
performance is not satisfying. If I would like to tune some certain
parameters of Linux kernel, how could I know which parameter is needed to
be changed? Is there a document explaining the list of the output of
command sysctl?

Please share what is on your mind and that would be appreciated by all of
the stackers.

Thanks,
Howard
___
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 kernel parameters

2013-07-09 Thread Matthew Thode

On 07/09/2013 10:49 AM, Hao Wang wrote:
 Hi experts,
 
 I am thinking there is a situation when OpenStack has been deployed but the
 performance is not satisfying. If I would like to tune some certain
 parameters of Linux kernel, how could I know which parameter is needed to
 be changed? Is there a document explaining the list of the output of
 command sysctl?
 
 Please share what is on your mind and that would be appreciated by all of
 the stackers.
 
 Thanks,
 Howard
 
 
 
 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp
 
What package is being slow and in what way?

-- 
-- Matthew Thode (prometheanfire)



signature.asc
Description: OpenPGP digital 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] Networking with Nova

2013-07-09 Thread Ritesh Nanda

Hello,

It is very much possible to specify the network to which you want vm to
attach, but for that you need to use quantum. You can even do it from the
horizon web interface.



On Tue, Jul 9, 2013 at 9:01 PM, othmane douiriothm...@gmail.com wrote:

 Hi all,

 ** **

 Im newbie to openstack, my question is: when I create an instance via
 nova, can I specify which network the instance should e attached to? For
 example, suppose that I have three VM in a compute node each of them is
 attached to a network 1,2,3, I want to add the fourth one and specify that
 this VM should be attached in network 2. How can I do that?

 ** **

 I have another question about understanding Openstack: what is the
 difference between the compute node and the openstack controller in the
 case of Nova? According to my understanding, the compute node is the
 physical or virtual machine where the virtual servers are running, right?
 

 ** **

 Thinks a lot, any help would be appreciated.

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




-- 

* With Regards
*

* Ritesh Nanda
*

***
*
http://www.ericsson.com/
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] Grizzly GRE tunneling network set up problems

2013-07-09 Thread Haitao Jiang

I just set up a multi-node Grizzly release 2013.2 with 1 controller
node, 1 network node and 1 compute node. I use GRE tunneling.

I create one VM on the compute node and was not able to ssh to it using netns.

One thing I noticed is that on my compute node, I do not have br-int
and br-tun in the list, nor do I find any GRE tunnels. Am I supposed
to create the GRE tunnels manually or they should be set up
automatically by Quantum? Any idea or suggestion to make it work?

Thanks in advance!

-- Compute node 
-- /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini  --
tunnel_id_ranges=1:1000
integration_bridge=br-int
tunneling_bridge=br-tun
tenant_network_type=gre
enable_tunneling=True
local_ip = host IP

# brctl show
bridge name bridge id   STP enabled interfaces
qbr5a9800b9-26  8000.5242b197c3d3   no  qvb5a9800b9-26
tap5a9800b9-26
virbr0  8000.525400198a10   yes virbr0-nic

# ovs-vsctl show
1d554b19-2a2b-493d-a123-0efb0aabc7d1
Bridge br-tun
Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
Port br-tun
Interface br-tun
type: internal
Bridge br-int
Port br-int
Interface br-int
type: internal
Port patch-tun
Interface patch-tun
type: patch
options: {peer=patch-int}
Port qvo5a9800b9-26
tag: 1
Interface qvo5a9800b9-26
ovs_version: 1.10.0

 network node ---
# brctl show
bridge name bridge id   STP enabled interfaces

# ovs-vsctl show
b9f0e822-cfc1-4b70-ac5b-abc4e5c258a4
Bridge br-int
Port br-int
Interface br-int
type: internal
Port tap9536e146-c2
Interface tap9536e146-c2
Bridge br-ex
Port br-ex
Interface br-ex
type: internal
ovs_version: 1.10.0

___
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] which API can do these?

2013-07-09 Thread Anne Gentle

Hi Peter,

Some doc links below.

On Tue, Jul 9, 2013 at 4:59 AM, Peter Cheung mcheun...@hotmail.com wrote:

 Hi All
   which API can do these?

 1) adjust the RAM size, no of CPU core to an instance


For 1) the keyword you want to look for in the docs is flavors. You can
read more at
http://docs.openstack.org/trunk/openstack-ops/content/flavors.html. It
indicates that you can use nova flavor-create -- note that you're
technically not modifying an existing flavor, you're creating a new flavor
and renaming it.

Use nova --debug flavor-create to see the API commands associated with
these adjustments to flavors.


 2) enlarge a disk to an instance


This is also specified in flavors.



 3) get the information about ram/cpu/disk size of an instance


You want this I believe.
http://api.openstack.org/api-ref.html#ext-os-flavorextradata


 Thanks
 from Peter

 ___
 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] Devstack + nginx + scalability

2013-07-09 Thread Geronimo Orozco

Hi, I am very interested in scalabity and HA with horizon is there any
effort to provide nginx to devstack ?

Where can I join to that effort ?


I just joined to this blueprint:
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-webscale


Any other interested ?

-Geronimo
___
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] [Nova] CPU Scalling, Quota for Disk I/O

2013-07-09 Thread Bruno Oliveira ~lychinus

Hello, any thoughts on this ?

Thank you
--

Bruno Oliveira
Developer, Software Engineer
irc: lychinus | skype: brunnop.oliveira
brunnop.olive...@gmail.com





On Mon, Jul 1, 2013 at 4:22 PM, Bruno Oliveira ~lychinus
brunnop.olive...@gmail.com wrote:
 Hello Stackers,

 Today morning I saw an interesting question regarding CPU Scaling
 in the list, which got me to ask the following:

 Currently (or in the roadmap) do we have any feature on Nova
 (regardless of the hypervisor underneath) to set maximum disk I/O
 throughput a VM can have ?

 I mean, let's say we have hundreds of VMs under the same host as
 in production, and for some reason we're lacking performance due to
 one (or a few of them) being too hungry/greedy for disk reads/writes.

 Question 1) Is there a way we can set quotas for disk I/O for a (group of)
 instances ? Like: for this one (or this group), don't exceed the threshold
 of 50 MB/seg

 Question 2) Also, do we have anything like vertical scalling ?
 I mean, like defining CPU and Memory Balloons as extra resources
 that a set of VMs can make use of (temporarily), if they're demanding to ?

 Note: I've seen some of the videos of Heat talking about increasing
 horizontally  the number of instances behind a load balancer to attend
 an increasing number of user requests, for instances...

 Thank you so much.

 --

 Bruno Oliveira
 Developer, Software Engineer
 irc: lychinus | skype: brunnop.oliveira
 brunnop.olive...@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] Grizzly Compute gives error

2013-07-09 Thread Adrian Smith

I'm guessing you've checked all the basic stuff but without anything else
to go on I'd check,

i) is MySQL up and running?
ii) is MySQL bound to 0.0.0.0 (as per the instructions on the setup page,
i.e.  sed -i 's/127.0.0.1/0.0.0.0/g' /etc/mysql/my.cnf
iii) can you connect to MySQL from another host using the regular mysql
client
iv) is the 'sql_connection' in nova.conf (and everywhere else it's
referenced) correct?


On 9 July 2013 11:08, raghavendra@accenture.com wrote:

  

 ** **

 ** **

 Hi,

 ** **

 I have tried the below link to install.


 https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_MultiNode/OpenStack_Grizzly_Install_Guide.rst
 

 ** **

 In my Nova-conf I have substituted for 192.168.22.4 instead of 10.10.10.53
 under Vnc configuration

 ** **

 *Vi /etc/nova/nova.conf   (My Compute node) All other nodes work fine.*

 ** **

 Under the below para.

- # Vnc configuration
- novnc_enabled=true
- novncproxy_base_url=http://192.168.100.51:6080/vnc_auto.html
- novncproxy_port=6080
- vncserver_proxyclient_address=*10.10.10.53*
- vncserver_listen=0.0.0.0
- ** **

 ** **

 ** **

 ** **

 ** **

 The screen shot of error message

 ** **

 

 ** **

 ** **

 ** **

 Regards,

 Raghavendra Lad

 --
 This message is for the designated recipient only and may contain
 privileged, proprietary, or otherwise confidential information. If you have
 received it in error, please notify the sender immediately and delete the
 original. Any other use of the e-mail by you is prohibited.

 Where allowed by local law, electronic communications with Accenture and
 its affiliates, including e-mail and instant messaging (including content),
 may be scanned by our systems for the purposes of information security and
 assessment of internal compliance with Accenture policy.


 __

 www.accenture.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


image001.png___
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] Networking with Nova

2013-07-09 Thread Adrian Smith

when I create an instance via nova, can I specify which network the instance
should e attached to? For example, suppose that I have
three VM in a compute node each of them is attached to a network 1,2,3, I
want to add the fourth one and specify that this VM
should be attached in network 2. How can I do that?

This documentation should be of use in relation to creating a VM and
attaching it to a particular network,
http://docs.openstack.org/trunk/openstack-network/admin/content/advanceed_vm_creation.html.
It describes the various means of attaching a VM to a network/networks
using the 'nova' and 'quantum' command line tools.

what is the difference between the compute node and the openstack controller
in the case of Nova? According to my understanding,
the compute node is the physical or virtual machine where the virtual servers
are running, right?

That's it. In general the compute node(s) host the VMs while the
controller node hosts the nova/quantum/etc services. You can also have
a separate Network node hosting the quantum services. Appendix A in
the Networking Guide outlines a few deployment options.
http://docs.openstack.org/trunk/openstack-network/admin/content/app_demo.html

On 9 July 2013 16:31, othmane douiriothm...@gmail.com wrote:
Hi all,

Im newbie to openstack, my question is: when I create an instance via nova,
can I specify which network the instance should e attached to? For example,
suppose that I have three VM in a compute node each of them is attached to a
network 1,2,3, I want to add the fourth one and specify that this VM should
be attached in network 2. How can I do that?

I have another question about understanding Openstack: what is the
difference between the compute node and the openstack controller in the case
of Nova? According to my understanding, the compute node is the physical or
virtual machine where the virtual servers are running, right?

Thinks a lot, any help would be appreciated.

___
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 kernel parameters

2013-07-09 Thread Hao Wang

I have got this concern for the path of ip packets will traverse many
interfaces to get out and in. I don't know if any one has this kind of
environment to have a comparison test on performance among different
visualization technologies.

Even not for performance, it is helpful to know the details of kernel
parameters, for example, when people troubleshooting network connections,
run this command, sysctl -w net.bridge.bridge-nf-call-arptables=0 (
http://docs.openstack.org/trunk/openstack-compute/admin/content/network-troubleshooting.html).
How could I know the command is what I should run? Is that a concern for
some people?

Regards,
Howard


On Tue, Jul 9, 2013 at 11:56 AM, Matthew Thode prometheanf...@gentoo.orgwrote:

 On 07/09/2013 10:49 AM, Hao Wang wrote:
  Hi experts,
 
  I am thinking there is a situation when OpenStack has been deployed but
 the
  performance is not satisfying. If I would like to tune some certain
  parameters of Linux kernel, how could I know which parameter is needed to
  be changed? Is there a document explaining the list of the output of
  command sysctl?
 
  Please share what is on your mind and that would be appreciated by all of
  the stackers.
 
  Thanks,
  Howard
 
 
 
  ___
  Mailing list: https://launchpad.net/~openstack
  Post to : openstack@lists.launchpad.net
  Unsubscribe : https://launchpad.net/~openstack
  More help   : https://help.launchpad.net/ListHelp
 
 What package is being slow and in what way?

 --
 -- Matthew Thode (prometheanfire)


 ___
 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] [Nova] CPU Scalling, Quota for Disk I/O

2013-07-09 Thread Shake Chen

https://blueprints.launchpad.net/nova/+spec/quota-instance-resource

In my view the instance recourse  like cpu, network, disk io quota feature
have in Grizzly. we just need to add the feature to Horizon.


On Wed, Jul 10, 2013 at 3:53 AM, Bruno Oliveira ~lychinus 
brunnop.olive...@gmail.com wrote:

 Hello, any thoughts on this ?

 Thank you
 --

 Bruno Oliveira
 Developer, Software Engineer
 irc: lychinus | skype: brunnop.oliveira
 brunnop.olive...@gmail.com





 On Mon, Jul 1, 2013 at 4:22 PM, Bruno Oliveira ~lychinus
 brunnop.olive...@gmail.com wrote:
  Hello Stackers,
 
  Today morning I saw an interesting question regarding CPU Scaling
  in the list, which got me to ask the following:
 
  Currently (or in the roadmap) do we have any feature on Nova
  (regardless of the hypervisor underneath) to set maximum disk I/O
  throughput a VM can have ?
 
  I mean, let's say we have hundreds of VMs under the same host as
  in production, and for some reason we're lacking performance due to
  one (or a few of them) being too hungry/greedy for disk reads/writes.
 
  Question 1) Is there a way we can set quotas for disk I/O for a (group
 of)
  instances ? Like: for this one (or this group), don't exceed the
 threshold
  of 50 MB/seg
 
  Question 2) Also, do we have anything like vertical scalling ?
  I mean, like defining CPU and Memory Balloons as extra resources
  that a set of VMs can make use of (temporarily), if they're demanding to
 ?
 
  Note: I've seen some of the videos of Heat talking about increasing
  horizontally  the number of instances behind a load balancer to attend
  an increasing number of user requests, for instances...
 
  Thank you so much.
 
  --
 
  Bruno Oliveira
  Developer, Software Engineer
  irc: lychinus | skype: brunnop.oliveira
  brunnop.olive...@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




-- 
Shake Chen
___
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] HA in Quantum

2013-07-09 Thread Hathaway.Jon

All

I was wondering whether my current understanding of HA in Quantum is currently 
correct or not as there does seem to be a little confusion.

From what I understand, the Quantum Service, DHCP and L3 agents are all 
supported through Pacemaker RA's or using the native messaging in Openstack 
Grizzly. Using the Grizzly Quantum messaging heartbeats, the Quantum service 
will keep deploying configurations until a point in time the agents are not 
responding. When this occurs it will look to deploy configurations on other 
available Network nodes running the agents.

However, the bit I am really fuzzy about it as follows. What happens if the 
network node completely fails? How would I recover the current networking 
configuration from the failed network node and re-deploy it on a working 
network node automatically?

I also see from reading multiple sources, that it would be possible to deploy 
the same configuration to multiple network nodes at the same time using the 
Quantum API, but it isn't supported currently through the normal GUI API calls 
so it would be an enhancement or a separate orchestration step.

If possible, would someone be able to point me in the right direction of how I 
can provide full HA Quantum based services for not only new configurations, but 
how I would re-deploy and recover configurations from a failed network node. 
I'm looking at this from an SLA perspective as well - is it possible to achieve 
failover between two active network nodes?

Thanks in advance to the great community out there.

Jon

___
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] [HyperV][Quantum] Quantum dhcp agent not working for Hyper-V

2013-07-09 Thread Hathaway.Jon

Thanks Alessandro - I'll add it our test processes!

Jon Hathaway
Distinguished Architect

International Game Technology (UK)

Office (US): +1 702 669 8185, (x698185)
Mobile (UK): +44 7799 711 981
jon.hatha...@igt.commailto:jon.hatha...@igt.com

From: Openstack 
[mailto:openstack-bounces+jon.hathaway=igt@lists.launchpad.net] On Behalf 
Of Alessandro Pilotti
Sent: 06 July 2013 17:28
To: OpenStack
Subject: Re: [Openstack] [HyperV][Quantum] Quantum dhcp agent not working for 
Hyper-V

Hi Jon,

Thanks for your help! Both the kernel and the iproute packages are updated. RDO 
does a great job with this. Beside the 2.6.32 + netns kernel provided by RDO I 
also tested it with a 3.9.8, with the same results. I'd add to your 
troubleshooting steps a very simple test to check if netns is enabled in the 
kernel: checking if the /proc/self/ns path exists.

Back to the original issue, there are no errors on the Quantum side.


Thanks,

Alessandro




On Jul 7, 2013, at 02:36 , Hathaway.Jon 
jon.hatha...@igt.commailto:jon.hatha...@igt.com
 wrote:


Hi Allessandro

I know this is probably something you have probably already tested for the RDO 
installation, but have you upgraded the CentOS kernel and the iproute package 
as both are missing the NetNS support required for Quantum. Ubuntu fixed this 
issue back in 10.04 but for whatever reason the current production kernel for 
CentOS still hasn't.

We had to update the kernel and the iproute package. If you check the log files 
for l3-agent, especially the dhcp logs you may find errors like command not 
recognised as the shipped iproute cor CentOS 6.4 doesn't support the netns 
extensions.

https://www.redhat.com/archives/rdo-list/2013-May/msg00015.html

My workaround was:

If installing on a EPEL6 distribution like Centos 6.4, there is a bug in the 
Kernel release which has disabled the Network Names (netns) support that is 
required to create overlapping networks in Quantum and is required to run the 
DHCP agent that assigns IP addresses on boot, and also setup the l3-agent that 
is responsible for forwarding requests from the instances to the API to 
retrieve any specific instance meta data.

A quick check on the node configured with Quantum in 
/var/log/quantum/dhcp-agent.log will show something like:

RuntimeError:
Command: ['sudo', 'quantum-rootwrap', '/etc/quantum/rootwrap.conf', 'ip', '-o', 
'netns', 'list']
Exit code: 255
Stdout: ''
Stderr: 'Object netns is unknown, try ip help.\n'

If you try and run 'ip netns' from the command and it fails, you will need to 
update the kernel and possibly the iproute2 package:

[root@oscontroller ~]# ip nets
Object nets is unknown, try ip help.

Netns is available in the iproute2 package , but it requires additional support 
from the kernel. A new kernel has been released for testing only by Redhat 
version kernel-2.6.32-358.6.2.openstack.el6.x86_64 whilst the installed version 
is kernel- 2.6.32-358.el6.x86_64 that comes with Centos 6.4.

To add the new kernel and iproute2 packages requires updating the kernel and 
kernel-firmware packages from the Grizzly repository.

yum install 
http://repos.fedorapeople.org/repos/openstack/openstack-grizzly/epel-6/kernel-firmware-2.6.32-358.6.2.openstack.el6.noarch.rpm

yum install 
http://repos.fedorapeople.org/repos/openstack/openstack-grizzly/epel-6/kernel-2.6.32-358.6.2.openstack.el6.x86_64.rpm

yum install 
http://repos.fedorapeople.org/repos/openstack/openstack-grizzly/epel-6/iproute-2.6.32-23.el6_4.netns.1.x86_64.rpm

Check in /etc/grub.conf that the new kernel is being reference and then restart 
the node running Quantum.

After reboot, try and run the 'ip netns' it should run without an error.

If you have previously added an instance before upgrading the packages, you 
will need to remove the networks, routers and ports and re-add them before 
continuing. However - it is likely that you will end up with stake ports on the 
Quantum Server. As shown below:

[root@oscontroller quantum]# ovs-vsctl show
e4b86f82-2d16-49b1-9077-93abf2b32400
Bridge br-ex
Port qg-3d8f69e7-5d
Interface qg-3d8f69e7-5d
type: internal
Port br-ex
Interface br-ex
type: internal
Bridge br-int
Port qr-c7145535-d1
tag: 1
Interface qr-c7145535-d1
type: internal
Port tapc4fb5d73-3e
tag: 1
Interface tapc4fb5d73-3e
type: internal
Port br-int
Interface br-int
type: internal
Port tape76c5e3c-1b
tag: 2
Interface tape76c5e3c-1b
type: internal
ovs_version: 1.10.0

These ports/interfaces will need to be deleted before the networking will work 
successfully.

Just a thought.

Jon

From: Openstack 
[mailto:openstack-bounces+jon.hathaway=igt@lists.launchpad.netmailto:bounces+jon.hathaway=igt@lists.launchpad.net]
 On Behalf Of Alessandro Pilotti
Sent: 06

Re: [Openstack] Grizzly GRE tunneling network set up problems

2013-07-09 Thread Chandler Li

Hi Haitao,

There should be GRE full mesh links being created in br-tun while you
created a VM successfully in Quantum ovs plugin GRE mode, just like:

Bridge br-tun
Port gre-x
Interface gre-x
type: gre
options: {in_key=flow, out_key=flow,
remote_ip=xx.xx.xx.xx}

Maybe you can check if there any error in log file
(/var/log/quantum/openvswitch-agent.log in compute node and network node),
perhaps you have wrong setting in quantum.conf (rabbit_host or others)

Chandler


2013/7/10 Haitao Jiang jianghai...@gmail.com

 I just set up a multi-node Grizzly release 2013.2 with 1 controller
 node, 1 network node and 1 compute node. I use GRE tunneling.

 I create one VM on the compute node and was not able to ssh to it using
 netns.

 One thing I noticed is that on my compute node, I do not have br-int
 and br-tun in the list, nor do I find any GRE tunnels. Am I supposed
 to create the GRE tunnels manually or they should be set up
 automatically by Quantum? Any idea or suggestion to make it work?

 Thanks in advance!

 -- Compute node 
 -- /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini  --
 tunnel_id_ranges=1:1000
 integration_bridge=br-int
 tunneling_bridge=br-tun
 tenant_network_type=gre
 enable_tunneling=True
 local_ip = host IP

 # brctl show
 bridge name bridge id   STP enabled interfaces
 qbr5a9800b9-26  8000.5242b197c3d3   no
  qvb5a9800b9-26
 tap5a9800b9-26
 virbr0  8000.525400198a10   yes virbr0-nic

 # ovs-vsctl show
 1d554b19-2a2b-493d-a123-0efb0aabc7d1
 Bridge br-tun
 Port patch-int
 Interface patch-int
 type: patch
 options: {peer=patch-tun}
 Port br-tun
 Interface br-tun
 type: internal
 Bridge br-int
 Port br-int
 Interface br-int
 type: internal
 Port patch-tun
 Interface patch-tun
 type: patch
 options: {peer=patch-int}
 Port qvo5a9800b9-26
 tag: 1
 Interface qvo5a9800b9-26
 ovs_version: 1.10.0

  network node ---
 # brctl show
 bridge name bridge id   STP enabled interfaces

 # ovs-vsctl show
 b9f0e822-cfc1-4b70-ac5b-abc4e5c258a4
 Bridge br-int
 Port br-int
 Interface br-int
 type: internal
 Port tap9536e146-c2
 Interface tap9536e146-c2
 Bridge br-ex
 Port br-ex
 Interface br-ex
 type: internal
 ovs_version: 1.10.0

 ___
 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 GRE tunneling network set up problems

2013-07-09 Thread Aaron Rosen

I'd check the quantum openvswitch agent log files. I'd guess the reason
this isn't working is because your kernel isn't using the openvswitch
kernel module that has tunnel support.

Aaron


On Tue, Jul 9, 2013 at 9:19 AM, Haitao Jiang jianghai...@gmail.com wrote:

 I just set up a multi-node Grizzly release 2013.2 with 1 controller
 node, 1 network node and 1 compute node. I use GRE tunneling.

 I create one VM on the compute node and was not able to ssh to it using
 netns.

 One thing I noticed is that on my compute node, I do not have br-int
 and br-tun in the list, nor do I find any GRE tunnels. Am I supposed
 to create the GRE tunnels manually or they should be set up
 automatically by Quantum? Any idea or suggestion to make it work?

 Thanks in advance!

 -- Compute node 
 -- /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini  --
 tunnel_id_ranges=1:1000
 integration_bridge=br-int
 tunneling_bridge=br-tun
 tenant_network_type=gre
 enable_tunneling=True
 local_ip = host IP

 # brctl show
 bridge name bridge id   STP enabled interfaces
 qbr5a9800b9-26  8000.5242b197c3d3   no
  qvb5a9800b9-26
 tap5a9800b9-26
 virbr0  8000.525400198a10   yes virbr0-nic

 # ovs-vsctl show
 1d554b19-2a2b-493d-a123-0efb0aabc7d1
 Bridge br-tun
 Port patch-int
 Interface patch-int
 type: patch
 options: {peer=patch-tun}
 Port br-tun
 Interface br-tun
 type: internal
 Bridge br-int
 Port br-int
 Interface br-int
 type: internal
 Port patch-tun
 Interface patch-tun
 type: patch
 options: {peer=patch-int}
 Port qvo5a9800b9-26
 tag: 1
 Interface qvo5a9800b9-26
 ovs_version: 1.10.0

  network node ---
 # brctl show
 bridge name bridge id   STP enabled interfaces

 # ovs-vsctl show
 b9f0e822-cfc1-4b70-ac5b-abc4e5c258a4
 Bridge br-int
 Port br-int
 Interface br-int
 type: internal
 Port tap9536e146-c2
 Interface tap9536e146-c2
 Bridge br-ex
 Port br-ex
 Interface br-ex
 type: internal
 ovs_version: 1.10.0

 ___
 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 GRE tunneling network set up problems

2013-07-09 Thread Haitao Jiang

Aaron  Chandler

Thanks a lot for the help. I should have mentioned that the host OS is
CentOS 6.4 (specifically the kernel from RedHat RDO). I googled and
found that it may not have gre tunneling support. Is there anyone who
has successfully set up gre with RDO's kernel or it is just can not be
done and I should use the VLAN.

As Aaron suspected, there are errprs in the OVS agent log:

system@ovs-system: failed to add gre-3 as port: Address family not
supported by protocol

More details below

Any pointer will be highly appreciated!

Haitao
==
Here are some outputs on my compute node (.46, .42 is the control node
and .44 is the network node):


# ovs-vsctl show
1d554b19-2a2b-493d-a123-0efb0aabc7d1
Bridge br-int
Port br-int
Interface br-int
type: internal
Port qvo8108425f-ef
tag: 1
Interface qvo8108425f-ef
Port patch-tun
Interface patch-tun
type: patch
options: {peer=patch-int}
Bridge br-tun
Port br-tun
Interface br-tun
type: internal
Port gre-3
Interface gre-3
type: gre
options: {in_key=flow, out_key=flow, remote_ip=10.18.250.44}
Port gre-4
Interface gre-4
type: gre
options: {in_key=flow, out_key=flow, remote_ip=10.18.250.42}
Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
ovs_version: 1.10.0

# ovs-ofctl dump-ports br-tun
OFPST_PORT reply (xid=0x2): 2 ports
  port  1: rx pkts=50, bytes=3300, drop=0, errs=0, frame=0, over=0, crc=0
   tx pkts=0, bytes=0, drop=0, errs=0, coll=0
  port LOCAL: rx pkts=0, bytes=0, drop=0, errs=0, frame=0, over=0, crc=0
   tx pkts=140, bytes=9800, drop=0, errs=0, coll=0

# uname -r
2.6.32-358.111.1.openstack.el6.x86_64

# modinfo openvswitch
filename:
/lib/modules/2.6.32-358.111.1.openstack.el6.x86_64/extra/openvswitch/openvswitch.ko
version:1.10.0
license:GPL
description:Open vSwitch switching datapath
srcversion: 480D55A9BB0E8B000E32010
depends:
vermagic:   2.6.32-358.111.1.openstack.el6.x86_64 SMP mod_unload
modversions
parm:   vlan_tso:Enable TSO for VLAN packets (int)

# tail ovs-vswitchd.log
2013-07-09T23:28:18Z|2|reconnect|INFO|unix:/var/run/openvswitch/db.sock:
connecting...
2013-07-09T23:28:18Z|3|reconnect|INFO|unix:/var/run/openvswitch/db.sock:
connected
2013-07-09T23:28:18Z|4|bridge|INFO|bridge br-int: added interface
patch-tun on port 1
2013-07-09T23:28:18Z|5|bridge|INFO|bridge br-tun: added interface
patch-int on port 1
2013-07-09T23:28:18Z|6|dpif|WARN|system@ovs-system: failed to add
gre-3 as port: Address family not supported by protocol
2013-07-09T23:28:18Z|7|dpif|WARN|system@ovs-system: failed to add
gre-4 as port: Address family not supported by protocol
2013-07-09T23:28:18Z|8|bridge|INFO|bridge br-int: using datapath
ID dacb49a63448
2013-07-09T23:28:18Z|9|connmgr|INFO|br-int: added service
controller punix:/var/run/openvswitch/br-int.mgmt
2013-07-09T23:28:18Z|00010|bridge|INFO|bridge br-tun: using datapath
ID 9a14eee01941
2013-07-09T23:28:18Z|00011|connmgr|INFO|br-tun: added service
controller punix:/var/run/openvswitch/br-tun.mgmt
2013-07-09T23:28:18Z|00012|bridge|INFO|ovs-vswitchd (Open vSwitch) 1.10.0
2013-07-09T23:28:28Z|00013|memory|INFO|7848 kB peak resident set size
after 10.0 seconds
2013-07-09T23:28:28Z|00014|memory|INFO|ports:5 rules:11
2013-07-09T23:28:28Z|00015|ofproto|INFO|br-int: 2 flow_mods in the 4 s
starting 10 s ago (1 adds, 1 deletes)
2013-07-09T23:28:28Z|00016|ofproto|INFO|br-tun: 5 flow_mods in the 3 s
starting 10 s ago (5 adds)
2013-07-09T23:53:25Z|00017|netdev|WARN|failed to set flags for network
device patch-int: Operation not supported

On Tue, Jul 9, 2013 at 8:59 PM, Aaron Rosen aro...@nicira.com wrote:
 I'd check the quantum openvswitch agent log files. I'd guess the reason this
 isn't working is because your kernel isn't using the openvswitch kernel
 module that has tunnel support.

 Aaron


 On Tue, Jul 9, 2013 at 9:19 AM, Haitao Jiang jianghai...@gmail.com wrote:

 I just set up a multi-node Grizzly release 2013.2 with 1 controller
 node, 1 network node and 1 compute node. I use GRE tunneling.

 I create one VM on the compute node and was not able to ssh to it using
 netns.

 One thing I noticed is that on my compute node, I do not have br-int
 and br-tun in the list, nor do I find any GRE tunnels. Am I supposed
 to create the GRE tunnels manually or they should be set up
 automatically by Quantum? Any idea or suggestion to make it work?

 Thanks in advance!

 -- Compute node 
 -- /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini  --
 tunnel_id_ranges=1:1000
 integration_bridge=br-int
 tunneling_bridge=br-tun
 tenant_network_type=gre

Re: [Openstack] Grizzly GRE tunneling network set up problems

2013-07-09 Thread Aaron Rosen

You should be able to compile openvswitch from source here :
http://openvswitch.org/download/ and then you'll get tunnel support.

Aaron


On Tue, Jul 9, 2013 at 10:21 PM, Haitao Jiang jianghai...@gmail.com wrote:

 Aaron  Chandler

 Thanks a lot for the help. I should have mentioned that the host OS is
 CentOS 6.4 (specifically the kernel from RedHat RDO). I googled and
 found that it may not have gre tunneling support. Is there anyone who
 has successfully set up gre with RDO's kernel or it is just can not be
 done and I should use the VLAN.

 As Aaron suspected, there are errprs in the OVS agent log:

 system@ovs-system: failed to add gre-3 as port: Address family not
 supported by protocol

 More details below

 Any pointer will be highly appreciated!

 Haitao
 ==
 Here are some outputs on my compute node (.46, .42 is the control node
 and .44 is the network node):


 # ovs-vsctl show
 1d554b19-2a2b-493d-a123-0efb0aabc7d1
 Bridge br-int
 Port br-int
 Interface br-int
 type: internal
 Port qvo8108425f-ef
 tag: 1
 Interface qvo8108425f-ef
 Port patch-tun
 Interface patch-tun
 type: patch
 options: {peer=patch-int}
 Bridge br-tun
 Port br-tun
 Interface br-tun
 type: internal
 Port gre-3
 Interface gre-3
 type: gre
 options: {in_key=flow, out_key=flow,
 remote_ip=10.18.250.44}
 Port gre-4
 Interface gre-4
 type: gre
 options: {in_key=flow, out_key=flow,
 remote_ip=10.18.250.42}
 Port patch-int
 Interface patch-int
 type: patch
 options: {peer=patch-tun}
 ovs_version: 1.10.0

 # ovs-ofctl dump-ports br-tun
 OFPST_PORT reply (xid=0x2): 2 ports
   port  1: rx pkts=50, bytes=3300, drop=0, errs=0, frame=0, over=0, crc=0
tx pkts=0, bytes=0, drop=0, errs=0, coll=0
   port LOCAL: rx pkts=0, bytes=0, drop=0, errs=0, frame=0, over=0, crc=0
tx pkts=140, bytes=9800, drop=0, errs=0, coll=0

 # uname -r
 2.6.32-358.111.1.openstack.el6.x86_64

 # modinfo openvswitch
 filename:

 /lib/modules/2.6.32-358.111.1.openstack.el6.x86_64/extra/openvswitch/openvswitch.ko
 version:1.10.0
 license:GPL
 description:Open vSwitch switching datapath
 srcversion: 480D55A9BB0E8B000E32010
 depends:
 vermagic:   2.6.32-358.111.1.openstack.el6.x86_64 SMP mod_unload
 modversions
 parm:   vlan_tso:Enable TSO for VLAN packets (int)

 # tail ovs-vswitchd.log

 2013-07-09T23:28:18Z|2|reconnect|INFO|unix:/var/run/openvswitch/db.sock:
 connecting...

 2013-07-09T23:28:18Z|3|reconnect|INFO|unix:/var/run/openvswitch/db.sock:
 connected
 2013-07-09T23:28:18Z|4|bridge|INFO|bridge br-int: added interface
 patch-tun on port 1
 2013-07-09T23:28:18Z|5|bridge|INFO|bridge br-tun: added interface
 patch-int on port 1
 2013-07-09T23:28:18Z|6|dpif|WARN|system@ovs-system: failed to add
 gre-3 as port: Address family not supported by protocol
 2013-07-09T23:28:18Z|7|dpif|WARN|system@ovs-system: failed to add
 gre-4 as port: Address family not supported by protocol
 2013-07-09T23:28:18Z|8|bridge|INFO|bridge br-int: using datapath
 ID dacb49a63448
 2013-07-09T23:28:18Z|9|connmgr|INFO|br-int: added service
 controller punix:/var/run/openvswitch/br-int.mgmt
 2013-07-09T23:28:18Z|00010|bridge|INFO|bridge br-tun: using datapath
 ID 9a14eee01941
 2013-07-09T23:28:18Z|00011|connmgr|INFO|br-tun: added service
 controller punix:/var/run/openvswitch/br-tun.mgmt
 2013-07-09T23:28:18Z|00012|bridge|INFO|ovs-vswitchd (Open vSwitch) 1.10.0
 2013-07-09T23:28:28Z|00013|memory|INFO|7848 kB peak resident set size
 after 10.0 seconds
 2013-07-09T23:28:28Z|00014|memory|INFO|ports:5 rules:11
 2013-07-09T23:28:28Z|00015|ofproto|INFO|br-int: 2 flow_mods in the 4 s
 starting 10 s ago (1 adds, 1 deletes)
 2013-07-09T23:28:28Z|00016|ofproto|INFO|br-tun: 5 flow_mods in the 3 s
 starting 10 s ago (5 adds)
 2013-07-09T23:53:25Z|00017|netdev|WARN|failed to set flags for network
 device patch-int: Operation not supported

 On Tue, Jul 9, 2013 at 8:59 PM, Aaron Rosen aro...@nicira.com wrote:
  I'd check the quantum openvswitch agent log files. I'd guess the reason
 this
  isn't working is because your kernel isn't using the openvswitch kernel
  module that has tunnel support.
 
  Aaron
 
 
  On Tue, Jul 9, 2013 at 9:19 AM, Haitao Jiang jianghai...@gmail.com
 wrote:
 
  I just set up a multi-node Grizzly release 2013.2 with 1 controller
  node, 1 network node and 1 compute node. I use GRE tunneling.
 
  I create one VM on the compute node and was not able to ssh to it using
  netns.
 
  One thing I noticed is that on my compute node, I do not have br-int
  and br-tun in the list, nor do I find any GRE tunnels. Am I supposed
  to create the GRE

82 matches

Mail list logo