Ask Your Question

Bada's profile - activity

2014-03-06 05:14:38 -0500 commented answer Nova Compute - question about cpu_allocation_ratio

Well yes :) and it could be nice to know and view where you are between : physical Cpu/allocated vCpu/Overcommit vCpu

2014-03-05 08:16:19 -0500 commented answer Nova Compute - question about cpu_allocation_ratio

And is there a way to check if the "cpu_allocation_ratio" parameter is really apply ? Thanks

2014-03-05 08:15:55 -0500 answered a question Nova Compute - question about cpu_allocation_ratio

And is there a way to check if the "cpu_allocation_ratio" parameter is really apply ?

Thanks

2014-01-23 18:42:16 -0500 marked best answer Unable to load Nexenta volume on Cinder

Hi,

I am trying to use a nexenta storage with Grizzly relase.

Cinder.conf :

[DEFAULT]
rootwrap_config=/etc/cinder/rootwrap.conf
sql_connection = mysql://cinderUser:xxxxxxxx@10.32.14.x/cinder
api_paste_config = /etc/cinder/api-paste.ini
verbose = True
auth_strategy = keystone
volume_driver=nexenta.volume.NexentaDriver
nexenta_host=192.168.1.x
nexenta_user=admin
nexenta_password=xxxx
nexenta_volume=Volume01
nexenta_iscsi_target_portal_port=3260
nexenta_rest_port=2000
nexenta_rest_protocol="auto"
nexenta_sparse=false
nexenta_target_prefix="iqn.1986-03.com.sun:02:nova-"
nexenta_target_group_prefix="nova/"
iscsi_helper=tgtadm

Error in /var/log/cinder/cinder-volume.log

    service_name=service_name)
  File "/usr/lib/python2.7/dist-packages/cinder/service.py", line 330, in __init__
    *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/cinder/volume/manager.py", line 129, in __init__
    configuration=self.configuration)
  File "/usr/lib/python2.7/dist-packages/cinder/openstack/common/importutils.py", line 40, in import_object
    return import_class(import_str)(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/cinder/openstack/common/importutils.py", line 30, in import_class
    __import__(mod_str)
ImportError: No module named nexenta.volume

How to load nexenta volume module ?

Small update i modified files according to : https://github.com/openstack/cinder/commit/f4f75ca9c0833475cfdb547bdad6a4d618e9e842

But still the same error:

2013-04-27 01:35:11 CRITICAL [cinder] No module named nexenta.volume
Traceback (most recent call last):
  File "/usr/bin/cinder-volume", line 57, in <module>
    server = service.Service.create(binary='cinder-volume')
  File "/usr/lib/python2.7/dist-packages/cinder/service.py", line 435, in create
    service_name=service_name)
  File "/usr/lib/python2.7/dist-packages/cinder/service.py", line 330, in __init__
    *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/cinder/volume/manager.py", line 129, in __init__
    configuration=self.configuration)
  File "/usr/lib/python2.7/dist-packages/cinder/openstack/common/importutils.py", line 40, in import_object
    return import_class(import_str)(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/cinder/openstack/common/importutils.py", line 30, in import_class
    __import__(mod_str)
ImportError: No module named nexenta.volume
2014-01-20 04:39:46 -0500 answered a question How to set up neutron vpn service (VPNaaS)?

Hello,

I have the same error and can't find any good documentation. Any help ?

Thanks

2013-12-19 02:12:48 -0500 received badge  Notable Question (source)
2013-12-18 11:33:23 -0500 received badge  Famous Question (source)
2013-12-05 10:25:55 -0500 received badge  Notable Question (source)
2013-12-05 10:25:55 -0500 received badge  Popular Question (source)
2013-10-23 19:53:44 -0500 received badge  Notable Question (source)
2013-10-23 19:53:44 -0500 received badge  Famous Question (source)
2013-10-23 19:53:44 -0500 received badge  Popular Question (source)
2013-10-23 02:46:09 -0500 received badge  Enthusiast
2013-10-22 10:55:34 -0500 asked a question Template creation Cloud-init error: Did not find data source

I'm trying to configure my Ubuntu image. I followed everystep of this doc http://docs.openstack.org/image-guide/content/ubuntu-image.html . Then when i deploy the instance it has no name, no ssh key and so on.

When i deploy the CloudUbuntu image (downloaded from the website) it works well, so I'm assuming the metadata server is ok.

I guess i'm missing something un the template image I'm building but I don't understand what. The error is :

image description

Any suggestions in what may be missing in my image?

2013-10-22 04:00:59 -0500 received badge  Popular Question (source)
2013-10-18 11:34:56 -0500 commented question Openstack in enterprise

And where could we discuss about it ?

2013-10-18 03:41:38 -0500 asked a question Openstack in enterprise

I guys,

I'm testing / playing with Openstack for a couple of month now. As a technical guy i really like it, the large community, the support , the web dashboard, open standard, APIs and so on are good points compared to Microsoft or VMware solutions. However as a traditional infrastructure consultant i'm trying to see how openstack could replace existing solutions. And there Openstack miss some basic and important features for company's infrastructure such as :

  • Link iso to instance
  • Extend disk
  • Change cpu ram
  • Make templates
  • Shutdown instance
  • etc

Of course there are some alternative like virt-manager to do that but if we want Openstack to be widely deployed we maybe need to feet traditional customers habits.

I was also thinking that i am maybe missing the point and Openstack would be dedicated to program launching and terminating on demand instance but in that case (i think) we are missing a great opportunity.

Thank you for sharing your opinion,

Regards,

2013-09-20 08:06:28 -0500 received badge  Famous Question (source)
2013-09-03 00:51:34 -0500 received badge  Notable Question (source)
2013-08-30 14:54:48 -0500 commented answer Live migration : InvalidCPUInfo: Unacceptable CPU info: CPU doesn't have compatibility.

Yes, i ll try to test the fix proposed :)

2013-08-30 05:54:57 -0500 marked best answer OVS plugin Error Failed to create OVS patch port

I just installed a three nodes configuration

  • 1 Controller (mysql, Rabbit, NTP, keystone, glance, quantum, Openvswitch, nova and horizon) 172.17.1.1
  • 2 compute (nova, Quantum, OpenVswitch) 172.17.2.1

Here is my quantum.conf

[DEFAULT]
debug = True
verbose = True
state_path = /var/lib/quantum
bind_host = 0.0.0.0
bind_port = 9696
core_plugin = quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2
api_paste_config = /etc/quantum/api-paste.ini
control_exchange = quantum
rabbit_host = 172.17.1.1
rabbit_password = XXXXXXXX
rabbit_port = 5672
rabbit_userid = guest
notification_driver = quantum.openstack.common.notifier.rpc_notifier
default_notification_level = INFO
notification_topics = notifications
[QUOTAS]
[DEFAULT_SERVICETYPE]
[SECURITYGROUP]
[AGENT]
root_helper = sudo quantum-rootwrap /etc/quantum/rootwrap.conf
[keystone_authtoken]
auth_host = 172.17.1.1
auth_port = 35357
auth_protocol = http
admin_tenant_name = service
admin_user = quantum
admin_password = XXXXXXXX
signing_dir = /var/lib/quantum/keystone-signing

Here is ovs_quantum_plugin.ini

   [DATABASE]
sql_connection = mysql://quantumUser:XXXXXXX@172.17.1.1/quantum
reconnect_interval = 2
[OVS]
enable_tunneling = True
tenant_network_type = gre
tunnel_id_ranges = 1:1000
local_ip = 172.18.2.1
integration_bridge = br-int
tunnel_bridge = br-tun
[AGENT]
polling_interval = 2
[SECURITYGROUP]

When i try to run the OVS plugin i have the following error in /var/log/quantum/openvswitch-agent.log

ERROR [quantum.plugins.openvswitch.agent.ovs_quantum_agent] Failed to create OVS patch port. Cannot have tunneling enabled on this agent, since this version of OVS does not support tunnels or patch ports. Agent terminated!

Here is what syslog shows

Aug 30 18:51:29 SSCloud-08 ovs-vsctl: 00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl --timeout=2 -- --if-exists del-port br-int patch-tun
Aug 30 18:51:29 SSCloud-08 ovs-vsctl: 00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl --timeout=2 -- --if-exists del-br br-tun
Aug 30 18:51:29 SSCloud-08 kernel: [  949.133083] device br-tun left promiscuous mode
Aug 30 18:51:29 SSCloud-08 ovs-vsctl: 00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl --timeout=2 add-br br-tun
Aug 30 18:51:29 SSCloud-08 kernel: [  949.321265] device br-tun entered promiscuous mode
Aug 30 18:51:30 SSCloud-08 ovs-vsctl: 00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl --timeout=2 add-port br-int patch-tun
Aug 30 18:51:30 SSCloud-08 ovs-vsctl: 00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl --timeout=2 set Interface patch-tun type=patch
Aug 30 18:51:30 SSCloud-08 ovs-vswitchd: 00223|netdev_vport|ERR|patch-tun: patch type requires valid 'peer' argument
Aug 30 18:51:30 SSCloud-08 ovs-vsctl: 00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl --timeout=2 set Interface patch-tun options:peer=patch-int
Aug 30 18:51:30 SSCloud-08 ovs-vsctl: 00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl --timeout=2 add-port br-tun patch-int
Aug 30 18:51:30 SSCloud-08 ovs-vsctl: 00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl --timeout=2 set Interface patch-int type=patch
Aug 30 18:51:30 SSCloud-08 ovs-vswitchd: 00249|netdev_vport|ERR|patch-int: patch type requires valid 'peer' argument
Aug 30 18:51:30 SSCloud-08 ovs-vsctl: 00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl --timeout=2 set Interface patch-int options:peer=patch-tun

Openvswitch do loaded

# lsmod | grep openvswich
openvswitch            43533  3

dpkg -l openvswitch* says

# dpkg -l openvswitch\*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status ...
(more)
2013-08-29 03:45:31 -0500 commented answer Live migration : InvalidCPUInfo: Unacceptable CPU info: CPU doesn't have compatibility.

Ok I understand. But then what is the purpose of specyfing a cpu-mode and cpu_model if the check don't care ? Moreover here in my case I have the same CPU the only thing that change is the Stepping which is like a minor version change during CPU production process. What happen when you have two complete different model generations ? In my opinion it could be nice to be able to manually set the minimum CPU model/features to be able to live migrate VM accross all nodes. Therefor the CPU check should take the cpu model and mode into consideration. Do you think it's something possible ? in progress ? none of them ? Thanks !

2013-08-29 03:39:02 -0500 received badge  Popular Question (source)
2013-08-28 15:30:57 -0500 answered a question Live migration : InvalidCPUInfo: Unacceptable CPU info: CPU doesn't have compatibility.

I check again and even with: libvirt_cpu_mode=none it does not work.

I'm not a big fan of directly modifying virt/driver.py.

I'm sure there should be a configuration to adapte VM configuration to the lowest CPU. any help ?

Thanks guys !

2013-08-27 15:43:37 -0500 received badge  Enlightened (source)
2013-08-27 15:42:04 -0500 asked a question Live migration : InvalidCPUInfo: Unacceptable CPU info: CPU doesn't have compatibility.

Hi guys,

I'm trying to set up live migration between my two hosts. I have set up a NFS share volume and configure nova.conf to use it to store the VM (It works).

Then when i try to do live migration fron CLI here is what happen : Host1 to Host2 : ok Host2 to Host1 : error

Here is the error in the nova-api.log of the controller node :

2013-08-26 23:25:50.012 ERROR nova.api.openstack.compute.contrib.admin_actions [req-5f28e5de-1312-4e07-81e7-893f439d7ccb f235975a22d64ca3a28f4b5dc1cbceb8 00eb7054314244fca82cf79f2caa8ff7] Live migration of instance 32e94646-2a3a-4c53-b169-becd433880eb to host Host01 failed
2013-08-26 23:25:50.012 9958 TRACE nova.api.openstack.compute.contrib.admin_actions Traceback (most recent call last):
2013-08-26 23:25:50.012 9958 TRACE nova.api.openstack.compute.contrib.admin_actions   File "/usr/lib/python2.7/dist-packages/nova/api/openstack/compute/contrib/admin_actions.py", line 284, in _migrate_live
2013-08-26 23:25:50.012 9958 TRACE nova.api.openstack.compute.contrib.admin_actions     disk_over_commit, host)
2013-08-26 23:25:50.012 9958 TRACE nova.api.openstack.compute.contrib.admin_actions   File "/usr/lib/python2.7/dist-packages/nova/compute/api.py", line 134, in inner
2013-08-26 23:25:50.012 9958 TRACE nova.api.openstack.compute.contrib.admin_actions     return f(self, context, instance, *args, **kw)
2013-08-26 23:25:50.012 9958 TRACE nova.api.openstack.compute.contrib.admin_actions   File "/usr/lib/python2.7/dist-packages/nova/compute/api.py", line 2454, in live_migrate
2013-08-26 23:25:50.012 9958 TRACE nova.api.openstack.compute.contrib.admin_actions     disk_over_commit, instance, host_name)
2013-08-26 23:25:50.012 9958 TRACE nova.api.openstack.compute.contrib.admin_actions   File "/usr/lib/python2.7/dist-packages/nova/scheduler/rpcapi.py", line 110, in live_migration
2013-08-26 23:25:50.012 9958 TRACE nova.api.openstack.compute.contrib.admin_actions     dest=dest))
2013-08-26 23:25:50.012 9958 TRACE nova.api.openstack.compute.contrib.admin_actions   File "/usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/proxy.py", line 80, in call
2013-08-26 23:25:50.012 9958 TRACE nova.api.openstack.compute.contrib.admin_actions     return rpc.call(context, self._get_topic(topic), msg, timeout)
2013-08-26 23:25:50.012 9958 TRACE nova.api.openstack.compute.contrib.admin_actions   File "/usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/__init__.py", line 140, in call
2013-08-26 23:25:50.012 9958 TRACE nova.api.openstack.compute.contrib.admin_actions     return _get_impl().call(CONF, context, topic, msg, timeout)
2013-08-26 23:25:50.012 9958 TRACE nova.api.openstack.compute.contrib.admin_actions   File "/usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/impl_kombu.py", line 798, in call
2013-08-26 23:25:50.012 9958 TRACE nova.api.openstack.compute.contrib.admin_actions     rpc_amqp.get_connection_pool(conf, Connection))
2013-08-26 23:25:50.012 9958 TRACE nova.api.openstack.compute.contrib.admin_actions   File "/usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/amqp.py", line 612, in call
2013-08-26 23:25:50.012 9958 TRACE nova.api.openstack.compute.contrib.admin_actions     rv = list(rv)
2013-08-26 23:25:50.012 9958 TRACE nova.api.openstack.compute.contrib.admin_actions   File "/usr/lib/python2.7/dist-packages/nova ...
(more)
2013-08-19 17:20:18 -0500 received badge  Scholar (source)
2013-08-19 17:12:31 -0500 received badge  Notable Question
2013-08-12 03:34:36 -0500 received badge  Popular Question
2013-07-23 13:06:29 -0500 received badge  Student (source)
2013-07-23 05:47:12 -0500 received badge  Famous Question (source)
2013-07-16 17:44:12 -0500 received badge  Good Answer (source)
2013-07-02 08:27:28 -0500 received badge  Nice Answer (source)
2013-06-26 03:57:33 -0500 received badge  Famous Question (source)
2013-06-12 09:52:04 -0500 received badge  Notable Question (source)
2013-05-31 07:39:22 -0500 received badge  Notable Question (source)
2013-05-29 04:04:36 -0500 answered a question Cinder provider location address

It works ! Thanks !

2013-05-29 04:04:08 -0500 received badge  Supporter (source)
2013-05-29 03:23:48 -0500 asked a question Cinder provider location address

Hi all,

I am not able to mount volume to any instance.

The volume creation is ok but if i look in the cinder database the provider_location IP address is wrong. The IP is my public interface and so VM cannot mount volume using it !

mysql> select provider_location from volumes;
+-------------------------------------------------------------------------+
| provider_location                                                                            |
+-------------------------------------------------------------------------+                                                                                    |
| PublicInterfaceAddress:3260,2 iqn.2010-10.org.openstack:volume-4ce92bae-4f33-4114-a669-fc0fa296718c 1 |

Everytime i create a new volume i got this Public Interface Address.

I look around and can't see any configuration files where we should specify the address.

Any advice ?

2013-05-28 05:05:59 -0500 received badge  Famous Question (source)
2013-05-28 04:37:06 -0500 received badge  Popular Question (source)
2013-05-27 10:17:05 -0500 asked a question Ephemeral storage decision

Hi everyone,

I am evaluating the several method to store ephemeral disks.

What i want to achieve is :

  • Host ephemeral disk on compute node to have good I/O

  • Use low cost disks (using Direct Attached Storage)

  • Minimize network traffic
  • Be able to run live migration

Taking an example my idea would be to have :

  • The VM disk locally hosted on node 1 and replicated on node 2 and 3.
  • If node 1 fail I would be able to run the VM on node 2 or 3 but if I loose node 2 or 3 there is no impact on VM hosted on node 1.

Live migration should be aware of where my VM disk is replicated.

Is there a solution to achieve this ?

Thanks