Ask Your Question

maoliping455's profile - activity

2019-10-30 12:59:22 -0500 received badge  Famous Question (source)
2019-10-30 12:59:22 -0500 received badge  Notable Question (source)
2015-09-03 20:38:49 -0500 received badge  Popular Question (source)
2014-06-06 20:13:37 -0500 received badge  Popular Question (source)
2013-10-16 08:38:36 -0500 answered a question why dhcp_lease_time default value is 120s?

Thanks Aaron Rosen, that solved my question.

2013-10-16 01:07:59 -0500 asked a question why dhcp_lease_time default value is 120s?

In dhcp agent the default value of dhcp_lease_time is 120, this means the lease time is 120s, why we use such a short time? why do not we use 24 hours or some other longer time ? Thanks.

2013-07-18 19:39:18 -0500 answered a question Unable to SSH/Ping to an instance

In your VM, run ifconfig , does it have IP in eth0? If not, it is dhcp issue...

2013-07-18 19:36:40 -0500 answered a question *NOT SOLVED*Network fails on cirros image creation

dhcp is not work. Do you use install your all in one env with command "parkstack --allinone"?

2013-07-18 19:20:37 -0500 answered a question DHCP problem

Not sure I have unstood what you said... ^_^ So you mean you use nova-network? The log shows that your VM has send dhcp req, but it does not get response from dnsmasq. You can run dhcpc in your VM in VNC, and use tcpdump to see where the req packet be, then you can see what's the problem. BTW, after you kill dnsmasq and restart nova-network, do you mean your dnsmasq is not up? You can boot another VM, I think dnsmasq should be up. Otherwise, you need to check if there is any error message in log...

2013-07-17 11:45:43 -0500 answered a question DHCP problem

I think I have met the same issue before, you can check quantum dhcp log. If you find the log like following:

RuntimeError: Command: ['sudo', '/usr/bin/quantum-rootwrap', '/etc/quantum/rootwrap.conf', 'ip', 'link', 'set', 'qg-dd9483f7-7d', 'address', 'fa:16:3e:a9:07:58']Exit code: 2Stdout: ''Stderr: 'RTNETLINK answers: Device or resource busy\n'

You can solve this issue refer to the following URL: http://blog.csdn.net/maoliping455mlp455/article/details/9331375 (http://blog.csdn.net/maoliping455mlp4...)

2013-07-17 11:45:41 -0500 answered a question DHCP problem

I think I have met the same issue before, you can check quantum dhcp log. If you find the log like following:

RuntimeError: Command: ['sudo', '/usr/bin/quantum-rootwrap', '/etc/quantum/rootwrap.conf', 'ip', 'link', 'set', 'qg-dd9483f7-7d', 'address', 'fa:16:3e:a9:07:58']Exit code: 2Stdout: ''Stderr: 'RTNETLINK answers: Device or resource busy\n'

You can solve this issue refer to the following URL: http://blog.csdn.net/maoliping455mlp455/article/details/9331375 (http://blog.csdn.net/maoliping455mlp4...)

2013-07-17 11:45:39 -0500 answered a question DHCP problem

I think I have met the same issue before, you can check quantum dhcp log. If you find the log like following:

RuntimeError: Command: ['sudo', '/usr/bin/quantum-rootwrap', '/etc/quantum/rootwrap.conf', 'ip', 'link', 'set', 'qg-dd9483f7-7d', 'address', 'fa:16:3e:a9:07:58']Exit code: 2Stdout: ''Stderr: 'RTNETLINK answers: Device or resource busy\n'

You can solve this issue refer to the following URL: http://blog.csdn.net/maoliping455mlp455/article/details/9331375 (http://blog.csdn.net/maoliping455mlp4...)

2013-07-17 11:45:38 -0500 answered a question DHCP problem

I think I have met the same issue before, you can check quantum dhcp log. If you find the log like following:

RuntimeError: Command: ['sudo', '/usr/bin/quantum-rootwrap', '/etc/quantum/rootwrap.conf', 'ip', 'link', 'set', 'qg-dd9483f7-7d', 'address', 'fa:16:3e:a9:07:58']Exit code: 2Stdout: ''Stderr: 'RTNETLINK answers: Device or resource busy\n'

You can solve this issue refer to the following URL: http://blog.csdn.net/maoliping455mlp455/article/details/9331375 (http://blog.csdn.net/maoliping455mlp4...)

2013-07-15 18:33:27 -0500 answered a question OpenStack VMs are unable to communicate with Outer World

nova-network support floating ip, and floating ip will help you solve this issue.

2013-07-15 18:26:34 -0500 answered a question Folsom: novnc is not working, not able to access VNC of the instances. Error: Failed to connect to server (code: 1006)

Can find any error message in consoleauth.log?

2013-04-25 01:50:40 -0500 answered a question nova work with quantum

Thanks for your help.

I have installed Bridge-utils. I find the reason, openvswitch 1.10.90 do not support brctl. I use openvswitch 1.9.XX , then, it can support brctl.

Thanks a lot.

2013-04-08 08:52:55 -0500 asked a question nova work with quantum

Hi all,

I try to use quantum work with nova. I use openvswitch plugin. When I start up a instance, I have the following error log:

2013-04-08 08:39:44 2796 TRACE nova.compute.manager [instance: 06af7b16-cac7-4cdf-a294-58306a5cf536] Traceback (most recent call last): 2013-04-08 08:39:44 2796 TRACE nova.compute.manager [instance: 06af7b16-cac7-4cdf-a294-58306a5cf536] File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 747, in _spawn 2013-04-08 08:39:44 2796 TRACE nova.compute.manager [instance: 06af7b16-cac7-4cdf-a294-58306a5cf536] block_device_info) 2013-04-08 08:39:44 2796 TRACE nova.compute.manager [instance: 06af7b16-cac7-4cdf-a294-58306a5cf536] File "/usr/lib/python2.6/site-packages/nova/exception.py", line 117, in wrapped 2013-04-08 08:39:44 2796 TRACE nova.compute.manager [instance: 06af7b16-cac7-4cdf-a294-58306a5cf536] temp_level, payload) 2013-04-08 08:39:44 2796 TRACE nova.compute.manager [instance: 06af7b16-cac7-4cdf-a294-58306a5cf536] File "/usr/lib64/python2.6/contextlib.py", line 23, in __exit__ 2013-04-08 08:39:44 2796 TRACE nova.compute.manager [instance: 06af7b16-cac7-4cdf-a294-58306a5cf536] self.gen.next() 2013-04-08 08:39:44 2796 TRACE nova.compute.manager [instance: 06af7b16-cac7-4cdf-a294-58306a5cf536] File "/usr/lib/python2.6/site-packages/nova/exception.py", line 92, in wrapped 2013-04-08 08:39:44 2796 TRACE nova.compute.manager [instance: 06af7b16-cac7-4cdf-a294-58306a5cf536] return f(args, *kw) 2013-04-08 08:39:44 2796 TRACE nova.compute.manager [instance: 06af7b16-cac7-4cdf-a294-58306a5cf536] File "/usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py", line 1086, in spawn 2013-04-08 08:39:44 2796 TRACE nova.compute.manager [instance: 06af7b16-cac7-4cdf-a294-58306a5cf536] block_device_info=block_device_info) 2013-04-08 08:39:44 2796 TRACE nova.compute.manager [instance: 06af7b16-cac7-4cdf-a294-58306a5cf536] File "/usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py", line 1863, in to_xml 2013-04-08 08:39:44 2796 TRACE nova.compute.manager [instance: 06af7b16-cac7-4cdf-a294-58306a5cf536] rescue, block_device_info) 2013-04-08 08:39:44 2796 TRACE nova.compute.manager [instance: 06af7b16-cac7-4cdf-a294-58306a5cf536] File "/usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py", line 1821, in get_guest_config 2013-04-08 08:39:44 2796 TRACE nova.compute.manager [instance: 06af7b16-cac7-4cdf-a294-58306a5cf536] cfg = self.vif_driver.plug(instance, (network, mapping)) 2013-04-08 08:39:44 2796 TRACE nova.compute.manager [instance: 06af7b16-cac7-4cdf-a294-58306a5cf536] File "/usr/lib/python2.6/site-packages/nova/virt/libvirt/vif.py", line 216, in plug 2013-04-08 08:39:44 2796 TRACE nova.compute.manager [instance: 06af7b16-cac7-4cdf-a294-58306a5cf536] utils.execute('brctl', 'addbr', br_name, run_as_root=True) 2013-04-08 08:39:44 2796 TRACE nova.compute.manager [instance: 06af7b16-cac7-4cdf-a294-58306a5cf536] File "/usr/lib/python2.6/site-packages/nova/utils.py", line 206, in execute 2013-04-08 08:39:44 2796 TRACE nova.compute.manager [instance: 06af7b16-cac7-4cdf-a294-58306a5cf536] cmd=' '.join(cmd)) 2013-04-08 08:39:44 2796 TRACE nova.compute.manager [instance: 06af7b16-cac7-4cdf-a294-58306a5cf536] ProcessExecutionError: Unexpected error while running command. 2013-04-08 08:39:44 2796 TRACE nova.compute.manager [instance: 06af7b16-cac7-4cdf-a294-58306a5cf536] Command: sudo nova-rootwrap /etc/nova/rootwrap.conf brctl addbr qbr64c8f98c-5c 2013-04-08 08:39:44 2796 TRACE nova.compute.manager [instance: 06af7b16-cac7-4cdf-a294-58306a5cf536] Exit code: 1 2013-04-08 08:39:44 2796 TRACE nova.compute.manager [instance: 06af7b16-cac7-4cdf-a294-58306a5cf536] Stdout: '' 2013-04-08 08:39:44 2796 TRACE nova.compute.manager [instance: 06af7b16-cac7-4cdf-a294-58306a5cf536] Stderr: 'add bridge failed: Package not installed\n'

the log seems like "brctl" can't work. I find my openvswitch can't work with command "brctl". My OS is CentOS6 ... (more)

2013-02-28 13:34:56 -0500 answered a question ETag of manifest file

Thanks David Goetz, that solved my question.

2013-02-26 09:05:29 -0500 asked a question ETag of manifest file

I find the following description from http://docs.openstack.org/developer/swift/overview_large_objects.htm (http://docs.openstack.org/developer/s...) “The response’s ETag for a GET or HEAD on the manifest file will be the MD5 sum of the concatenated string of ETags for each of the segments in the / listing, dynamically.”

So I upload two segment files and a manifest file, then I want to use the ETag of segment file to calculate the ETag of manifest file. a) segment file1: ETag: c4ca4238a0b923820dcc509a6f75849b b) segment file2: ETag: c81e728d9d4c2f636f067f89cc14862c c) So I think the ETag of manifest file should be 02e26c67c011b6b0914cfd3f5cac506f: #cat manifestETag c4ca4238a0b923820dcc509a6f75849bc81e728d9d4c2f636f067f89cc14862c #md5sum manifestETag 02e26c67c011b6b0914cfd3f5cac506f manifestETag

But in face the ETag of manifest is 302cbafc0dfbc97f30d576a6f394dad3.

So I think the ETag of manifest should be “02e26c67c011b6b0914cfd3f5cac506f”, But in fact it is 302cbafc0dfbc97f30d576a6f394dad3.