Ask Your Question

upendras's profile - activity

2012-05-22 00:58:42 -0500 answered a question trying Qpid on Ubuntu 12.04 -- ClassNotFound exception

Managed to find the solution.

I had not installed the necessary libraries for Qpid on 192.168.1.4 and thus that error. The error message was misleading but did give a hint of the main problem.

so just ran the following on 192.168.1.4 also apt-get install qpidd qpid-tools qpid-doc qpid-client python-qpid-extras-qmf python-qpid python-cqpid

-u

2012-05-21 13:36:07 -0500 asked a question trying Qpid on Ubuntu 12.04 -- ClassNotFound exception

Hi,

I have nova Essex over Ubuntu-12.04 installed on my cluster. I am trying to experiment with the Qpid instead of RabbitMQ. I have installed Qpid and its other utilities using the following command: apt-get install qpidd qpid-tools qpid-doc qpid-client python-qpid-extras-qmf python-qpid python-cqpid

and have enabled the quid backend using the following flags in nova.conf --rpc_backend=nova.rpc.impl_qpid --qpid_hostname=192.168.1.7

But when I start nova-compute and other nova services, they are unable to find impl_qpid; the exact error from nova-compute.log is: 2012-05-21 08:58:13 TRACE nova ClassNotFound: Class impl_qpid could not be found: 'module' object has no attribute 'impl_qpid'

However, I can see impl_qpid.py and impl_qpid.pyc in /usr/lib/python2.7/dist-packages/nova/rpc. Please let me know where am I going wrong.

I have am pasting the relevant portions of nova-compute.log and nova.conf below

thanks in advance -upendra

===== nova.conf ==== --dhcpbridge_flagfile=/etc/nova/nova.conf --dhcpbridge=/usr/bin/nova-dhcpbridge --logdir=/var/log/nova --state_path=/var/lib/nova --lock_path=/var/lock/nova --force_dhcp_release --iscsi_helper=tgtadm --libvirt_use_virtio_for_bridges --connection_type=libvirt --root_helper=sudo nova-rootwrap --verbose --debug --ec2_private_dns_show_ip --auth_strategy=keystone

GLANCE

--image_service=nova.image.glance.GlanceImageService --glance_api_servers=192.168.1.4:9292

RPC backend

rabbit

#--rabbit_host=192.168.1.4 --rabbit_host=192.168.1.6

Qpid

--rpc_backend=nova.rpc.impl_qpid --qpid_hostname=192.168.1.7

NETWORK

--network_manager=nova.network.manager.FlatDHCPManager --flat_injected=False --fixed_range=192.168.100.0/24 --public_interface=eth0 --flat_interface=eth2 --flat_network_bridge=br100 --multi_host=True

DATABASE

--sql_connection=mysql://nova:nova@192.168.1.4/nova

========== nova-compute.log ============== 2012-05-21 08:58:09 DEBUG nova.service [-] network_driver : nova.network.linux_net from (pid=5173) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-05-21 08:58:09 DEBUG nova.service [-] quota_instances : 10 from (pid=5173) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-05-21 08:58:09 DEBUG nova.service [-] vnc_keymap : FLAG SET from (pid=5173) wait /usr/lib/python2.7/dist-packages/nova/service.py:409 2012-05-21 08:58:09 DEBUG nova.service [-] image_service : nova.image.glance.GlanceImageService from (pid=5173) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-05-21 08:58:09 DEBUG nova.service [-] libvirt_inject_password : FLAG SET from (pid=5173) wait /usr/lib/python2.7/dist-packages/nova/service.py:409 2012-05-21 08:58:09 DEBUG nova.service [-] control_exchange : nova from (pid=5173) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-05-21 08:58:09 DEBUG nova.service [-] volume_group : nova-volumes from (pid=5173) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-05-21 08:58:09 DEBUG nova.service [-] log_file : None from (pid=5173) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-05-21 08:58:09 DEBUG nova.service [-] compute_manager : nova.compute.manager.ComputeManager from (pid=5173) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-05-21 08:58:09 DEBUG nova.service [-] compute_driver : nova.virt.connection.get_connection from (pid=5173) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-05-21 08:58:09 DEBUG nova.service [-] network_topic : network from ... (more)

2011-10-04 16:10:13 -0500 answered a question nova-compute service hangs up

Thanks Sharif,

I removed all the packages (with the --purge flag) and re-installed the system from scratch and now things are working.

thanks -upendra

2011-10-04 08:43:18 -0500 asked a question nova-compute service hangs up

Hi

I have downloaded the Diablo release and installed it on Ubuntu 11.04 I have followed steps outlined in ( http://docs.openstack.org/diablo/openstack-compute/admin/content/installing-the-cloud-controller.html (http://docs.openstack.org/diablo/open...) )

when I reach the point of starting the services; the command "sudo service nova-network start" returns but nova-network does not start ... then after that if I start nova-compute, it hangs up.

I am attaching a long nova-compute.log and nova.conf.

thanks in advance -upendra

== nova.conf === --dhcpbridge_flagfile=/etc/nova/nova.conf --dhcpbridge=/usr/bin/nova-dhcpbridge --logdir=/var/log/nova --state_path=/var/lib/nova --lock_path=/var/lock/nova --flagfile=/etc/nova/nova-compute.conf --force_dhcp_release=True --use_deprecated_auth --verbose --s3_host=192.168.245.65 --rabbit_host=192.168.245.65 --cc_host=192.168.245.65 --ec2_url=http://192.168.245.65:8773/services/Cloud --ec2_api=192.168.245.65 --network_manager=nova.network.manager.FlatManager --fixed_range=192.168.246.112/28 --network_size=8 --routing_source_ip=192.168.245.65 --sql_connection=mysql://root:novadbpass@192.168.245.65/nova --glance_host=192.168.245.65 --image_service=nova.image.glance.GlanceImageService --iscsi_ip_prefix=192.168. == nova.conf ===

========= nova-compute.log ============= 2011-10-03 22:03:11,650 DEBUG nova [-] Full set of FLAGS: from (pid=4567) wait /usr/lib/python2.7/dist-packages/nova/service.py:352 2011-10-03 22:03:11,650 DEBUG nova [-] storage_availability_zone : nova from (pid=4567) wait /usr/lib/python2.7/dist-packages/nova/service.py:355 2011-10-03 22:03:11,651 DEBUG nova [-] vc_image_name : vc_image from (pid=4567) wait /usr/lib/python2.7/dist-packages/nova/service.py:355 2011-10-03 22:03:11,651 DEBUG nova [-] ec2_dmz_host : 192.168.245.65 from (pid=4567) wait /usr/lib/python2.7/dist-packages/nova/service.py:355 2011-10-03 22:03:11,651 DEBUG nova [-] fixed_range : 192.168.246.112/28 from (pid=4567) wait /usr/lib/python2.7/dist-packages/nova/service.py:355 2011-10-03 22:03:11,651 DEBUG nova [-] compute_topic : compute from (pid=4567) wait /usr/lib/python2.7/dist-packages/nova/service.py:355 2011-10-03 22:03:11,651 DEBUG nova [-] vsa_topic : vsa from (pid=4567) wait /usr/lib/python2.7/dist-packages/nova/service.py:355 2011-10-03 22:03:11,651 DEBUG nova [-] fixed_range_v6 : fd00::/48 from (pid=4567) wait /usr/lib/python2.7/dist-packages/nova/service.py:355 2011-10-03 22:03:11,651 DEBUG nova [-] glance_api_servers : ['192.168.245.65:9292'] from (pid=4567) wait /usr/lib/python2.7/dist-packages/nova/service.py:355 2011-10-03 22:03:11,652 DEBUG nova [-] rabbit_password : guest from (pid=4567) wait /usr/lib/python2.7/dist-packages/nova/service.py:355 2011-10-03 22:03:11,652 DEBUG nova [-] user_cert_subject : /C=US/ST=California/L=MountainView/O=AnsoLabs/OU=NovaDev/CN=%s-%s-%s from (pid=4567) wait /usr/lib/python2.7/dist-packages/nova/service.py:355 2011-10-03 22:03:11,652 DEBUG nova [-] s3_dmz : 192.168.245.65 from (pid=4567) wait /usr/lib/python2.7/dist-packages/nova/service.py:355 2011-10-03 22:03:11,652 DEBUG nova [-] dhcp_lease_time : 120 from (pid=4567) wait /usr/lib/python2.7/dist-packages/nova/service ... (more)

2011-08-18 16:07:35 -0500 answered a question unable to delete VMs using nova delete command

Thanks Brian for a prompt response.

I re-started all the services on ibc6hb05 (which I was calling C2) ... everything stated to behave normally and I could also delete it those instances ...

$ sudo libvirtd restart; sudo service nova-network restart;sudo service nova-compute restart;sudo service nova-api restart; sudo service nova-scheduler restart;

I do not know why it was not working earlier ... but, looks like, restarting was a quick-fix.

thanks again, -upendra

2011-08-18 15:06:29 -0500 asked a question unable to delete VMs using nova delete command

Hi, I have a setup where there are two compute nodes, say (C1 and C2). C1 is also the cloud-controller node and object-store node.

I have a few VMs which show up using nova list command (as shown below):

$ nova list +----+-----------+---------+-----------+--------------+ | ID | Name | Status | Public IP | Private IP | +----+-----------+---------+-----------+--------------+ | 87 | Server 87 | SHUTOFF | | 9.59.231.196 | | 88 | Server 88 | SHUTOFF | | | | 89 | Server 89 | SHUTOFF | | |

+----+-----------+---------+-----------+--------------+

I want to delete all the three VMs; so use "nova delete" command and nothing really happens. I am pasting my nova-api.log. Nothing shows up in nova-compute.log. I am fine with manually removing the entries from mysql-table if there is a way (without breaking the installation) ... Any help will be appreciated.

thanks, -upendra

======== C1:/var/log/nova/nova-api.log ========= 2011-08-18 11:02:01,612 DEBUG nova.api.openstack [-] Successfully authenticated 'upendra' from (pid=1783) authenticate /usr/lib/pymodules/python2.6/nova/api/openstack/auth.py:111 2011-08-18 11:02:01,631 DEBUG routes.middleware [-] Matched GET /servers/87 from (pid=1783) __call__ /usr/lib/pymodules/python2.6/routes/middleware.py:100 2011-08-18 11:02:01,631 DEBUG routes.middleware [-] Route path: '/servers/:(id)', defaults: {'action': u'show', 'controller': } from (pid=1783) __call__ /usr/lib/pymodules/python2.6/routes/middleware.py:102 2011-08-18 11:02:01,632 DEBUG routes.middleware [-] Match dict: {'action': u'show', 'controller': , 'id': u'87'} from (pid=1783) __call__ /usr/lib/pymodules/python2.6/routes/middleware.py:103 2011-08-18 11:02:01,632 INFO nova.api.openstack.wsgi [-] GET http://19.69.230.129:8774/v1.0/servers/87?fresh=1313679721.61 (http://19.69.230.129:8774/v1.0/server...) 2011-08-18 11:02:01,799 INFO nova.api.openstack.wsgi [-] http://19.69.230.129:8774/v1.0/servers/87?fresh=1313679721.61 (http://19.69.230.129:8774/v1.0/server...) returned with HTTP 200 2011-08-18 11:02:01,817 DEBUG routes.middleware [-] Matched DELETE /servers/87 from (pid=1783) __call__ /usr/lib/pymodules/python2.6/routes/middleware.py:100 2011-08-18 11:02:01,818 DEBUG routes.middleware [-] Route path: '/servers/:(id)', defaults: {'action': u'delete', 'controller': } from (pid=1783) __call__ /usr/lib/pymodules/python2.6/routes/middleware.py:102 2011-08-18 11:02:01,818 DEBUG routes.middleware [-] Match dict: {'action': u'delete', 'controller': , 'id': u'87'} from (pid=1783) __call__ /usr/lib/pymodules/python2.6/routes/middleware.py:103 2011-08-18 11:02:01,818 INFO nova.api.openstack.wsgi [-] DELETE http://19.69.230.129:8774/v1.0/servers/87 (http://19.69.230.129:8774/v1.0/server...) 2011-08-18 11:02:01,818 DEBUG nova.compute.api [-] Going to try to terminate 87 from (pid=1783) delete /usr/lib/pymodules/python2.6/nova/compute/api.py:544 2011-08-18 11:02:01,980 DEBUG nova.rpc [-] Making asynchronous cast on compute.ibc6hb05... from (pid=1783) cast /usr/lib/pymodules/python2.6/nova/rpc.py:554

2011-08-18 11:02:02,021 INFO nova.api.openstack.wsgi [-] http://19.69.230.129:8774/v1.0/servers/87 (http://19.69 ...

(more)
2011-07-19 20:45:00 -0500 answered a question failed to create VM on 2nd compute node

Thanks Vish Ishaya, that solved my question.

2011-07-19 15:49:17 -0500 asked a question failed to create VM on 2nd compute node

Hi,

I have two compute nodes; first one (say CN_01) is on the same node which is also the cloud-controller node, while the 2nd node (say CN_02) is a dedicated compute node.

CN_01 has following processes; 1.) nova_apir 2.) nova-network 3.) nova-compute 4.) nova-scheduler 5.) nova-objectstore 6.) glance-registry 7.) glance-api

I have not made any setting changes to "/etc/glance/glance-api.conf" ... so everything is running on defaults.

I have registered an image (the standard ttylinux image); output of euca-describe-images is: $ euca-describe-images IMAGE ami-00000003 mybucket/ttylinux-uec-amd64-12.1_2.6.35-22_1.img.manifest.xml available public x86_64 machine aki-00000001 ari-00000002 IMAGE ari-00000002 mybucket/ttylinux-uec-amd64-12.1_2.6.35-22_1-initrd.manifest.xml available public x86_64 ramdisk IMAGE aki-00000001 mybucket/ttylinux-uec-amd64-12.1_2.6.35-22_1-vmlinuz.manifest.xml available public x86_64 kernel

When I create an instance of this image on CN_01, everything works fine. However, when I create an instance of the same image on CN_02 it fails. I am not sure if it is a bug or wrong configuration; I am attaching the nova-compute.log.

Please let me know if the cause of problem is obvious.

Thanks, -upendra

========== CN_02:/var/log/nova/nova-compute.log =========== 2011-07-19 10:45:25,342 DEBUG nova.rpc [-] received {u'_context_request_id': u'4Z2Z7NMZR4-Z37V1ZLOB', u'_context_read_deleted': False, u'args': {u'instance_id': 68, u'request_spec': {u'instance_properties': {u'state_description': u'scheduling', u'availability_zone': None, u'ramdisk_id': u'2', u'instance_type_id': 2, u'user_data': u'', u'vm_mode': None, u'reservation_id': u'r-7rmxukz7', u'user_id': u'upendra', u'display_description': None, u'key_data': u'ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAAAgQCfGYTuj0dtVgjSp5mMAHv/dPHUjBppmitimKEwroOy5HbWPsEWeWxvwXjz/q76X8kmdtoD43+IlZx1PG35xdVGgJ938tnmWubR4LtTxcbtM0f/dNdLjQRwkFmvJ4MmePbjLfTRTPIWfSayJKOFIiQM0A7f5uK2UYdfSo7wVNIdOw== nova@ibc6hb13\n', u'state': 0, u'project_id': u'myproj', u'metadata': {}, u'kernel_id': u'1', u'key_name': u'upen', u'display_name': None, u'local_gb': 0, u'locked': False, u'launch_time': u'2011-07-19T14:44:53Z', u'memory_mb': 512, u'vcpus': 1, u'image_ref': 3, u'architecture': None, u'os_type': None}, u'instance_type': {u'rxtx_quota': 0, u'deleted_at': None, u'name': u'm1.tiny', u'deleted': False, u'created_at': None, u'updated_at': None, u'memory_mb': 512, u'vcpus': 1, u'rxtx_cap': 0, u'extra_specs': {}, u'swap': 0, u'flavorid': 1, u'id': 2, u'local_gb': 0}, u'num_instances': 1, u'filter': u'nova.scheduler.host_filter.InstanceTypeFilter', u'blob': None}, u'admin_password': None, u'injected_files': None, u'availability_zone': None}, u'_context_is_admin': True, u'_context_timestamp': u'2011-07-19T14:44:53Z', u'_context_user': u'upendra', u'method': u'run_instance', u'_context_project': u'myproj', u'_context_remote_address': u'9.59.230.122'} from (pid=21444) process_data /usr/lib/pymodules/python2.7/nova/rpc.py:202 2011-07-19 10:45:25,342 DEBUG nova.rpc [-] unpacked context: {'timestamp': u'2011-07-19T14:44:53Z', 'msg_id': None, 'remote_address': u'9.59.230.122', 'project': u'myproj', 'is_admin': True, 'user': u'upendra', 'request_id': u'4Z2Z7NMZR4-Z37V1ZLOB', 'read_deleted': False} from (pid=21444) _unpack_context /usr/lib/pymodules/python2.7/nova/rpc.py:451 2011-07-19 10:45:25,400 AUDIT nova.compute.manager [4Z2Z7NMZR4-Z37V1ZLOB upendra myproj] instance 68: starting... 2011-07-19 10:45:25,564 DEBUG nova.rpc [-] Making asynchronous call on network ... from (pid=21444) multicall /usr/lib/pymodules/python2.7/nova/rpc.py ... (more)

2011-07-01 08:57:53 -0500 answered a question euca-describe-images does not work

I managed to fix it.

the document does not mention anything about glance; apparently it is important as image image manipulation commands eventually call the glance service.

so the fix is simple

$> sudo apt-get install -y glance $> sudo glance-control glance-api start

this fixes the problem.

thanks, -upendra

2011-06-30 16:41:33 -0500 asked a question euca-describe-images does not work

Hi,

I carried out the scripted install

$> wget --no-check-certificate https://github.com/dubsquared/OpenStack-NOVA-Installer-Script/raw/master/nova-CC-install-v1.1.sh (https://github.com/dubsquared/OpenSta...) $> sudo chmod 755 nova-CC-install-v1.1.sh

and it successfully complete (without finding dnsmasq ... )

then euca-describe-instances silently returns, however, euca-describe-images gives an error shown below:

$> euca-describe-images UnknownError: An unknown error has occurred. Please try your request again. $>

the /var/log/nova/nova-api.log for this entry query and nova.conf have been copy-pasted over here.

Please let me know ff someone is able to locate the mistake/problem

thanks, -upendra

========== nova-api.log =========== 2011-06-30 12:35:50,273 DEBUG nova.auth.manager [-] Looking up user: u'413e67ee-8ad4-4b41-a786-e6aace156613' from (pid=30810) authenticate /usr/lib/pymodules/python2.6/nova/auth/manager.py:277 2011-06-30 12:35:50,279 DEBUG nova.auth.manager [-] user: User('upendra', 'upendra', '413e67ee-8ad4-4b41-a786-e6aace156613', '26b84301-7015-4004-9b56-dd9b7a5b83d4', True) from (pid=30810) authenticate /usr/lib/pymodules/python2.6/nova/auth/manager.py:279 2011-06-30 12:35:50,288 DEBUG nova.signer [-] using _calc_signature_2 from (pid=30810) _calc_signature_2 /usr/lib/pymodules/python2.6/nova/auth/signer.py:126 2011-06-30 12:35:50,288 DEBUG nova.signer [-] query string: AWSAccessKeyId=413e67ee-8ad4-4b41-a786-e6aace156613%3Amyproject&Action=DescribeImages&Owner.1=self&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2011-06-30T16%3A35%3A50&Version=2009-11-30 from (pid=30810) _calc_signature_2 /usr/lib/pymodules/python2.6/nova/auth/signer.py:142 2011-06-30 12:35:50,289 DEBUG nova.signer [-] string_to_sign: GET 9.59.230.122:8773 /services/Cloud/ AWSAccessKeyId=413e67ee-8ad4-4b41-a786-e6aace156613%3Amyproject&Action=DescribeImages&Owner.1=self&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2011-06-30T16%3A35%3A50&Version=2009-11-30 from (pid=30810) _calc_signature_2 /usr/lib/pymodules/python2.6/nova/auth/signer.py:144 2011-06-30 12:35:50,289 DEBUG nova.signer [-] len(b64)=44 from (pid=30810) _calc_signature_2 /usr/lib/pymodules/python2.6/nova/auth/signer.py:147 2011-06-30 12:35:50,289 DEBUG nova.signer [-] base64 encoded digest: nigBCZgwtzbVK7T08ksP5Sr5bh14jBoNMaqcMe7aCoA= from (pid=30810) _calc_signature_2 /usr/lib/pymodules/python2.6/nova/auth/signer.py:148 2011-06-30 12:35:50,289 DEBUG nova.auth.manager [-] user.secret: 26b84301-7015-4004-9b56-dd9b7a5b83d4 from (pid=30810) authenticate /usr/lib/pymodules/python2.6/nova/auth/manager.py:322 2011-06-30 12:35:50,290 DEBUG nova.auth.manager [-] expected_signature: nigBCZgwtzbVK7T08ksP5Sr5bh14jBoNMaqcMe7aCoA= from (pid=30810) authenticate /usr/lib/pymodules/python2.6/nova/auth/manager.py:323 2011-06-30 12:35:50,290 DEBUG nova.auth.manager [-] signature: nigBCZgwtzbVK7T08ksP5Sr5bh14jBoNMaqcMe7aCoA= from (pid=30810) authenticate /usr/lib/pymodules/python2.6/nova/auth/manager.py:324 2011-06-30 12:35:50,290 AUDIT nova.api [I3BJRIEJQ2J5-PREFWKM upendra myproject] Authenticated Request For upendra:myproject) 2011-06-30 12:35:50,291 DEBUG nova.api [-] action: DescribeImages from (pid=30810) __call__ /usr/lib/pymodules/python2.6/nova/api/ec2/__init__.py:214 2011-06-30 12:35:50,291 DEBUG nova.api [-] arg: Owner.1 val: self from (pid=30810) __call__ /usr/lib/pymodules/python2.6/nova/api/ec2/__init__.py:216 2011-06-30 12:35:50,292 ERROR nova.api [I3BJRIEJQ2J5-PREFWKM upendra myproject] Unexpected error raised: Unable to connect to server. Got error: [Errno 111] ECONNREFUSED (nova.api): TRACE: Traceback (most recent call last): (nova.api): TRACE: File ... (more)