Ask Your Question

hyunsun-moon's profile - activity

2018-06-25 03:54:09 -0600 received badge  Notable Question (source)
2018-06-25 03:54:09 -0600 received badge  Popular Question (source)
2017-06-21 14:29:24 -0600 received badge  Famous Question (source)
2016-06-09 23:49:49 -0600 received badge  Popular Question (source)
2016-06-09 23:49:49 -0600 received badge  Notable Question (source)
2015-08-27 07:09:02 -0600 received badge  Notable Question (source)
2015-05-28 14:17:03 -0600 received badge  Popular Question (source)
2013-07-29 01:24:23 -0600 received badge  Supporter (source)
2012-12-27 09:43:49 -0600 answered a question No access between provider and tenant networks

Thanks Ricardo. I solved the same issue with your comments.

FYI. I tested openstack and quantum on VMs runs on ESXi and got the exactly the same problem with Ricardo. Ping to the qg-xx interface, which resides in a different namespace from the root, failed from external. It only worked inside the same host. Gateway IP and floating IPs were set successfully and I set routing rules properly. By changing vswitch settings on vsphere client, it just worked well.

Refer to this link(http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004099) to set your VM's network interfaces to promiscuous mode, in case of you're using ESXi.

2012-05-22 01:35:22 -0600 answered a question Instances don't get an IP from DHCP (Quantum, OVS, multi-node computes)

askask,

in your '/var/log/message' log above, the actual VLAN ID assigned to your tap device is 4 I guess. "May 18 15:49:27 core01 ovs-vsctl: 00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl --timeout=2 set Port tap926d429e-53 tag=4" If VLAN 4 is not defined on your physical switch, as far as I know, any packets from the tap device could be discared. Check what VLAN ID is actually assigned to your tap device using 'ovs-vsctl show', tag number is VLAN ID.

Following page might help. http://openvswitch.org/support/config-cookbooks/vlan-configuration-cookbook/ (http://openvswitch.org/support/config...)

VLAN_MIN / VLAN_MAX is hard coded in quantum/plugins/openvswitch/ovs_quantum_plugin.py So I modified the source code. When I change the values to random numbers which I haven't defined on my physical switch, VM network failed. Don't forget to restart quantum service once you change the code.

Have you tried VLAN mode first? I guess VLAN_MIN is the same value with the --vlan_start flag on your nova.conf

Hope this helps.

2012-05-21 08:19:04 -0600 answered a question Instances don't get an IP from DHCP (Quantum, OVS, multi-node computes)

Hello,

Have you guys set trunk mode on your physical switch? If not, try it. I also had to change VLAN_MIN / VLAN_MAX values on quantum/plugins/openvswitch/ovs_quantum_plugin.py to the values defined on my switch. It defaults to VLAN_MIN=1 / VLAN_MAX=4094. Guess these values would be set as a flag.

Hope this helps.

2011-05-17 06:24:25 -0600 answered a question Vlan mode switch setting

It works, finally..!

2011-05-17 06:12:45 -0600 answered a question Vlan mode switch setting

Thanks Vish Ishaya, that solved my question.

2011-05-16 10:16:56 -0600 asked a question Vlan mode switch setting

Hi, I need some help to setup vlan mode deploy. For now, I could run instances from compute nodes but the instances fail to get an IP address from network node. I suspect vlan settings on the physical switch because there was no Rx packets passing vlan, only Tx packets. Here's my question.

  1. Should I create vlans used on Nova manually on the switch? Like vlan 100, every time?
  2. I read that vlan trunking must be enabled on the switch. What does it mean? Does it mean making new trunking port? Which did not work. Or should I make all used ports to trunk mode?

Please shed some lights..

2011-04-22 06:01:49 -0600 answered a question Instance on the pure compute node cannot reach the meta data server

Solved.

2011-04-22 05:52:17 -0600 answered a question Instance on the pure compute node cannot reach the meta data server

Hi, this was not a bug but missing a flag, --flat_interface=eth0. Thanks!

2011-04-20 07:06:48 -0600 answered a question Instance on the pure compute node cannot reach the meta data server

I found that DHCPDISCOVERY of VM is passed to br100, but failed to be forwarded to eth0 and further network hosts in LAN. FlatDHCP has the same problem.

2011-04-20 00:43:48 -0600 answered a question Instance on the pure compute node cannot reach the meta data server

It's odd because compute node can get the meta data.

GET http://169.254.169.254/

1.0 2007-01-19 2007-03-01 2007-08-29 2007-10-10 2007-12-15 2008-02-01 2008-09-01 2009-04-04


I wonder, how instance can get the IP address from DHCP server on network node, with the private IP like 10.0.0.1?

2011-04-20 00:29:53 -0600 answered a question Instance on the pure compute node cannot reach the meta data server

Here's iptables-save result of the compute node.

Generated by iptables-save v1.4.4 on Tue Apr 19 20:27:13 2011

*nat :PREROUTING ACCEPT [229:43562] :POSTROUTING ACCEPT [10:622] :OUTPUT ACCEPT [11:693] :nova-compute-OUTPUT - [0:0] :nova-compute-POSTROUTING - [0:0] :nova-compute-PREROUTING - [0:0] :nova-compute-floating-snat - [0:0] :nova-compute-snat - [0:0] :nova-postrouting-bottom - [0:0] -A PREROUTING -j nova-compute-PREROUTING -A PREROUTING -d 169.254.169.254/32 -p tcp -m tcp --dport 80 -j DNAT --to-destination 121.166.195.54:8773 -A POSTROUTING -j nova-compute-POSTROUTING -A POSTROUTING -j nova-postrouting-bottom -A POSTROUTING -s 192.168.122.0/24 ! -d 192.168.122.0/24 -p tcp -j MASQUERADE --to-ports 1024-65535 -A POSTROUTING -s 192.168.122.0/24 ! -d 192.168.122.0/24 -p udp -j MASQUERADE --to-ports 1024-65535 -A POSTROUTING -s 192.168.122.0/24 ! -d 192.168.122.0/24 -j MASQUERADE -A OUTPUT -j nova-compute-OUTPUT -A nova-compute-snat -j nova-compute-floating-snat -A nova-postrouting-bottom -j nova-compute-snat COMMIT

Completed on Tue Apr 19 20:27:13 2011

Generated by iptables-save v1.4.4 on Tue Apr 19 20:27:13 2011

*filter :INPUT ACCEPT [475311:42792648] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [928238:74704384] :nova-compute-FORWARD - [0:0] :nova-compute-INPUT - [0:0] :nova-compute-OUTPUT - [0:0] :nova-compute-inst-18 - [0:0] :nova-compute-local - [0:0] :nova-compute-sg-fallback - [0:0] :nova-filter-top - [0:0] -A INPUT -j nova-compute-INPUT -A INPUT -i virbr0 -p udp -m udp --dport 53 -j ACCEPT -A INPUT -i virbr0 -p tcp -m tcp --dport 53 -j ACCEPT -A INPUT -i virbr0 -p udp -m udp --dport 67 -j ACCEPT -A INPUT -i virbr0 -p tcp -m tcp --dport 67 -j ACCEPT -A FORWARD -j nova-filter-top -A FORWARD -j nova-compute-FORWARD -A FORWARD -d 192.168.122.0/24 -o virbr0 -m state --state RELATED,ESTABLISHED -j ACCEPT -A FORWARD -s 192.168.122.0/24 -i virbr0 -j ACCEPT -A FORWARD -i virbr0 -o virbr0 -j ACCEPT -A FORWARD -o virbr0 -j REJECT --reject-with icmp-port-unreachable -A FORWARD -i virbr0 -j REJECT --reject-with icmp-port-unreachable -A OUTPUT -j nova-filter-top -A OUTPUT -j nova-compute-OUTPUT -A nova-compute-FORWARD -i br100 -j ACCEPT -A nova-compute-FORWARD -o br100 -j ACCEPT -A nova-compute-inst-18 -m state --state INVALID -j DROP -A nova-compute-inst-18 -m state --state RELATED,ESTABLISHED -j ACCEPT -A nova-compute-inst-18 -s 10.0.0.1/32 -p udp -m udp --sport 67 --dport 68 -j ACCEPT -A nova-compute-inst-18 -s 10.0.0.0/26 -j ACCEPT -A nova-compute-inst-18 -j nova-compute-sg-fallback -A nova-compute-local -d 10.0.0.3/32 -j nova-compute-inst-18 -A nova-compute-sg-fallback -j DROP -A nova-filter-top -j nova-compute-local COMMIT

Completed on Tue Apr 19 20:27:13 2011

2011-04-20 00:25:29 -0600 answered a question Instance on the pure compute node cannot reach the meta data server

I was using VLAN mode and did iptables -t nat -A PREROUTING for the 169.254.169.254 to the API node.

2011-04-20 00:24:31 -0600 asked a question Instance on the pure compute node cannot reach the meta data server

I deployed nova to the two servers, one runs api, network, scheduler, objectstore, and the other runs compute only. Instance has been proceed to the running state successfully, however, console output shows that the instance failed to start up unable to reach metadata server. See the console output below.


1 [ 0.000000] Initializing cgroup subsys cpuset^M 2 [ 0.000000] Initializing cgroup subsys cpu^M 3 [ 0.000000] Linux version 2.6.32-28-server (buildd@allspice) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #55-Ubuntu SMP Mon Jan 10 23: 57:16 UTC 2011 (Ubuntu 2.6.32-28.55-server 2.6.32.27+drm33.12)^M 4 [ 0.000000] Command line: root=/dev/vda console=ttyS0^M 5 [ 0.000000] KERNEL supported cpus:^M 6 [ 0.000000] Intel GenuineIntel^M 7 [ 0.000000] AMD AuthenticAMD^M 8 [ 0.000000] Centaur CentaurHauls^M 9 [ 0.000000] BIOS-provided physical RAM map:^M 10 [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f000 (usable)^M 11 [ 0.000000] BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved)^M 12 [ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)^M 13 [ 0.000000] BIOS-e820: 0000000000100000 - 000000001fffb000 (usable)^M 14 [ 0.000000] BIOS-e820: 000000001fffb000 - 0000000020000000 (reserved)^M 15 [ 0.000000] BIOS-e820: 00000000fffc0000 - 0000000100000000 (reserved)^M 16 [ 0.000000] DMI 2.4 present.^M 17 [ 0.000000] last_pfn = 0x1fffb max_arch_pfn = 0x400000000^M 18 [ 0.000000] x86 PAT enabled: cpu 0, old 0x0, new 0x7010600070106^M 19 [ 0.000000] Scanning 1 areas for low memory corruption^M 20 [ 0.000000] modified physical RAM map:^M 21 [ 0.000000] modified: 0000000000000000 - 0000000000001000 (usable)^M 22 [ 0.000000] modified: 0000000000001000 - 0000000000006000 (reserved)^M 23 [ 0.000000] modified: 0000000000006000 - 000000000009f000 (usable)^M 24 [ 0.000000] modified: 000000000009f000 - 00000000000a0000 (reserved)^M 25 [ 0.000000] modified: 00000000000f0000 - 0000000000100000 (reserved)^M 26 [ 0.000000] modified: 0000000000100000 - 000000001fffb000 (usable)^M 27 [ 0.000000] modified: 000000001fffb000 - 0000000020000000 (reserved)^M 28 [ 0.000000] modified: 00000000fffc0000 - 0000000100000000 (reserved)^M 29 [ 0.000000] init_memory_mapping: 0000000000000000-000000001fffb000^M 30 [ 0.000000] NX (Execute Disable) protection: active^M 31 [ 0.000000] ACPI: RSDP 00000000000f8940 00014 (v00 BOCHS )^M 32 [ 0.000000] ACPI: RSDT 000000001fffde30 00034 (v01 BOCHS BXPCRSDT 00000001 BXPC 00000001)^M 33 [ 0.000000] ACPI: FACP 000000001ffffe70 00074 (v01 BOCHS BXPCFACP 00000001 BXPC 00000001)^M 34 [ 0.000000] ACPI: DSDT 000000001fffdfd0 01E22 (v01 BXPC BXDSDT 00000001 INTL 20090123)^M 35 [ 0.000000] ACPI: FACS 000000001ffffe00 00040^M 36 [ 0.000000] ACPI: SSDT 000000001fffdf90 00037 (v01 BOCHS BXPCSSDT 00000001 BXPC 00000001)^M 37 [ 0.000000] ACPI: APIC 000000001fffdeb0 00072 (v01 BOCHS BXPCAPIC 00000001 BXPC 00000001)^M 38 [ 0.000000] ACPI: HPET 000000001fffde70 00038 (v01 BOCHS BXPCHPET 00000001 BXPC 00000001)^M 39 [ 0.000000] No NUMA configuration found^M 40 [ 0.000000] Faking a node at 0000000000000000-000000001fffb000^M 41 [ 0.000000] Bootmem setup node 0 0000000000000000-000000001fffb000^M 42 [ 0.000000] NODE_DATA [0000000000009000 - 000000000000dfff]^M

43 [ 0.000000] bootmap [000000000000e000 - 0000000000011fff] pages 4^M 44 [ 0.000000] (6 early reservations) ==> bootmem [0000000000 - 001fffb000]^M 45 [ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]^M 46 [ 0.000000] #1 [0000006000 - 0000008000] TRAMPOLINE ==> [0000006000 - 0000008000 ...

(more)
2011-04-13 01:31:00 -0600 answered a question Success SSH a tty image but failed SSH UEC image

I got the same error with 980. The instance running on the host where api service is running well booted (without above error), but others fails to boot with the "url error [timed out]".

2011-04-13 01:25:47 -0600 answered a question How can I make server.config.template?

Thanks Vish Ishaya, that solved my question.

2011-04-13 01:25:29 -0600 answered a question How can I make server.config.template?

Hi Vish, thanks! It helped me a lot.

2011-04-12 11:12:21 -0600 asked a question How can I make server.config.template?

Hello,

It's not that easy to be done vpn test without guidance.. Anyway,finally I can get user_data from the meta-data server with revision 980. I found that autorun.sh tries to 'sed ... server.config.template > server.conf' and got some errors without server.config.template.

I copied sample server.conf from openvpn source code to the cloudpipe image. It succeed to run openvpn server but I cannot access to the vpn.

Do I make a special template file for server.conf?

One more question, the instance running at the second compute node(running only compute service) seems fail to access metadata server displaying the following error log during boot.


cloud-init running: Tue, 12 Apr 2011 11:09:06 +0000. up 87.14 seconds waiting for metadata service at http://169.254.169.254/2009-04-04/meta-data/instance-id (http://169.254.169.254/2009-04-04/met...) 11:09:06 [ 1/100]: url error [[Errno 101] Network is unreachable] 11:09:07 [ 2/100]: url error [[Errno 101] Network is unreachable] 11:09:08 [ 3/100]: url error [[Errno 101] Network is unreachable] 11:09:09 [ 4/100]: url error [[Errno 101] Network is unreachable] 11:09:10 [ 5/100]: url error [[Errno 101] Network is unreachable] 11:09:11 [ 6/100]: url error [[Errno 101] Network is unreachable] 11:09:13 [ 7/100]: url error [[Errno 101] Network is unreachable] 11:09:15 [ 8/100]: url error [[Errno 101] Network is unreachable] 11:09:17 [ 9/100]: url error [[Errno 101] Network is unreachable] 11:09:19 [10/100]: url error [[Errno 101] Network is unreachable] 11:09:21 [11/100]: url error [[Errno 101] Network is unreachable] 11:09:24 [12/100]: url error [[Errno 101] Network is unreachable] 11:09:27 [13/100]: url error [[Errno 101] Network is unreachable] 11:09:30 [14/100]: url error [[Errno 101] Network is unreachable]

I did iptables -t nat -A PREROUTING -d 169.254.169.254/32 -p tcp -m tcp --dport 80 -j DNAT --to-destination $NOVA_API_IP:8773.

2011-04-11 16:49:56 -0600 answered a question cloudpipe instance fails to get payload.b64

oh, it was already in bug report, Bug #757293.

2011-04-11 16:41:47 -0600 answered a question cloudpipe instance fails to get payload.b64

Hi Barton, here are the results of curl http://169.254.169.254/latest/meta-data/ local-ipv4 reservation-id local-hostname placement/ ami-launch-index public-hostname mpi/ hostname ami-id public-keys/ instance-action public-ipv4 block-device-mapping/ ami-manifest-path security-groups instance-type instance-id

It's from the normal instance because I don't know how to log in to the cloudpipe server. Frequently the same command (curl http://169.254.169.254/latest/meta-data/ ) occurs the following error!!!


Traceback (most recent call last): File "/usr/lib/pymodules/python2.6/eventlet/wsgi.py", line 336, in handle_one_response result = self.application(self.environ, start_response) File "/usr/lib/pymodules/python2.6/paste/urlmap.py", line 203, in __call__ return app(environ, start_response) File "/usr/lib/pymodules/python2.6/webob/dec.py", line 147, in __call__ resp = self.call_func(req, args, *self.kwargs) File "/usr/lib/pymodules/python2.6/webob/dec.py", line 208, in call_func return self.func(req, args, *kwargs) File "/root/openstack/nova/nova/api/ec2/__init__.py", line 59, in __call__ rv = req.get_response(self.application) File "/usr/lib/pymodules/python2.6/webob/request.py", line 919, in get_response application, catch_exc_info=False) File "/usr/lib/pymodules/python2.6/webob/request.py", line 887, in call_application app_iter = application(self.environ, start_response) File "/usr/lib/pymodules/python2.6/webob/dec.py", line 147, in __call__ resp = self.call_func(req, args, *self.kwargs) File "/usr/lib/pymodules/python2.6/webob/dec.py", line 208, in call_func return self.func(req, args, *kwargs) File "/root/openstack/nova/nova/api/ec2/metadatarequesthandler.py", line 74, in __call__ meta_data = cc.get_metadata(remote_address) File "/root/openstack/nova/nova/api/ec2/cloud.py", line 173, in get_metadata 'instance-type': instance_ref['instance_type'], File "/root/openstack/nova/nova/db/sqlalchemy/models.py", line 74, in __getitem__ return getattr(self, key) File "/usr/lib/pymodules/python2.6/sqlalchemy/orm/attributes.py", line 163, in __get__ instance_dict(instance)) File "/usr/lib/pymodules/python2.6/sqlalchemy/orm/attributes.py", line 382, in get value = callable_(passive=passive) File "/usr/lib/pymodules/python2.6/sqlalchemy/orm/strategies.py", line 578, in __call__ (mapperutil.state_str(state), self.key) DetachedInstanceError: Parent instance <instance at="" 0x45dd810=""> is not bound to a Session; lazy load operation of attribute 'instance_type' cannot proceed

2011-04-11 16:41:40 -0600 answered a question cloudpipe instance fails to get payload.b64

Hi Barton, here are the results of curl http://169.254.169.254/latest/meta-data/ local-ipv4 reservation-id local-hostname placement/ ami-launch-index public-hostname mpi/ hostname ami-id public-keys/ instance-action public-ipv4 block-device-mapping/ ami-manifest-path security-groups instance-type instance-id

It's from the normal instance because I don't know how to log in to the cloudpipe server. Frequently the same command (curl http://169.254.169.254/latest/meta-data/ ) occurs the following error!!!


Traceback (most recent call last): File "/usr/lib/pymodules/python2.6/eventlet/wsgi.py", line 336, in handle_one_response result = self.application(self.environ, start_response) File "/usr/lib/pymodules/python2.6/paste/urlmap.py", line 203, in __call__ return app(environ, start_response) File "/usr/lib/pymodules/python2.6/webob/dec.py", line 147, in __call__ resp = self.call_func(req, args, *self.kwargs) File "/usr/lib/pymodules/python2.6/webob/dec.py", line 208, in call_func return self.func(req, args, *kwargs) File "/root/openstack/nova/nova/api/ec2/__init__.py", line 59, in __call__ rv = req.get_response(self.application) File "/usr/lib/pymodules/python2.6/webob/request.py", line 919, in get_response application, catch_exc_info=False) File "/usr/lib/pymodules/python2.6/webob/request.py", line 887, in call_application app_iter = application(self.environ, start_response) File "/usr/lib/pymodules/python2.6/webob/dec.py", line 147, in __call__ resp = self.call_func(req, args, *self.kwargs) File "/usr/lib/pymodules/python2.6/webob/dec.py", line 208, in call_func return self.func(req, args, *kwargs) File "/root/openstack/nova/nova/api/ec2/metadatarequesthandler.py", line 74, in __call__ meta_data = cc.get_metadata(remote_address) File "/root/openstack/nova/nova/api/ec2/cloud.py", line 173, in get_metadata 'instance-type': instance_ref['instance_type'], File "/root/openstack/nova/nova/db/sqlalchemy/models.py", line 74, in __getitem__ return getattr(self, key) File "/usr/lib/pymodules/python2.6/sqlalchemy/orm/attributes.py", line 163, in __get__ instance_dict(instance)) File "/usr/lib/pymodules/python2.6/sqlalchemy/orm/attributes.py", line 382, in get value = callable_(passive=passive) File "/usr/lib/pymodules/python2.6/sqlalchemy/orm/strategies.py", line 578, in __call__ (mapperutil.state_str(state), self.key) DetachedInstanceError: Parent instance <instance at="" 0x45dd810=""> is not bound to a Session; lazy load operation of attribute 'instance_type' cannot proceed

2011-04-11 16:41:05 -0600 answered a question cloudpipe instance fails to get payload.b64

Hi Barton, here are the results of curl http://169.254.169.254/latest/meta-data/ local-ipv4 reservation-id local-hostname placement/ ami-launch-index public-hostname mpi/ hostname ami-id public-keys/ instance-action public-ipv4 block-device-mapping/ ami-manifest-path security-groups instance-type instance-id

It's from the normal instance because I don't know how to log in to the cloudpipe server. Frequently the same command (curl http://169.254.169.254/latest/meta-data/ ) occurs the following error!!!


Traceback (most recent call last): File "/usr/lib/pymodules/python2.6/eventlet/wsgi.py", line 336, in handle_one_response result = self.application(self.environ, start_response) File "/usr/lib/pymodules/python2.6/paste/urlmap.py", line 203, in __call__ return app(environ, start_response) File "/usr/lib/pymodules/python2.6/webob/dec.py", line 147, in __call__ resp = self.call_func(req, args, *self.kwargs) File "/usr/lib/pymodules/python2.6/webob/dec.py", line 208, in call_func return self.func(req, args, *kwargs) File "/root/openstack/nova/nova/api/ec2/__init__.py", line 59, in __call__ rv = req.get_response(self.application) File "/usr/lib/pymodules/python2.6/webob/request.py", line 919, in get_response application, catch_exc_info=False) File "/usr/lib/pymodules/python2.6/webob/request.py", line 887, in call_application app_iter = application(self.environ, start_response) File "/usr/lib/pymodules/python2.6/webob/dec.py", line 147, in __call__ resp = self.call_func(req, args, *self.kwargs) File "/usr/lib/pymodules/python2.6/webob/dec.py", line 208, in call_func return self.func(req, args, *kwargs) File "/root/openstack/nova/nova/api/ec2/metadatarequesthandler.py", line 74, in __call__ meta_data = cc.get_metadata(remote_address) File "/root/openstack/nova/nova/api/ec2/cloud.py", line 173, in get_metadata 'instance-type': instance_ref['instance_type'], File "/root/openstack/nova/nova/db/sqlalchemy/models.py", line 74, in __getitem__ return getattr(self, key) File "/usr/lib/pymodules/python2.6/sqlalchemy/orm/attributes.py", line 163, in __get__ instance_dict(instance)) File "/usr/lib/pymodules/python2.6/sqlalchemy/orm/attributes.py", line 382, in get value = callable_(passive=passive) File "/usr/lib/pymodules/python2.6/sqlalchemy/orm/strategies.py", line 578, in __call__ (mapperutil.state_str(state), self.key) DetachedInstanceError: Parent instance <instance at="" 0x45dd810=""> is not bound to a Session; lazy load operation of attribute 'instance_type' cannot proceed

2011-04-11 10:15:17 -0600 asked a question cloudpipe instance fails to get payload.b64

Hello, I'm trying to test VPN. I added some scripts to the cloudpipe image's rc.local for fetching user-data from metadata server.(I found the useful scripts from this board).

Here's the script.


echo Downloading payload from userdata wget http://169.254.169.254/latest/user-data -O /tmp/payload.b64 echo Decrypting base64 payload openssl enc -d -base64 -in /tmp/payload.b64 -out /tmp/payload.zip

mkdir -p /tmp/payload echo Unzipping payload file unzip -o /tmp/payload.zip -d /tmp/payload/

if the autorun.sh script exists, run it

if [ -e /tmp/payload/autorun.sh ]; then echo Running autorun.sh cd /tmp/payload sh /tmp/payload/autorun.sh

else echo rc.local : No autorun script to run fi

exit 0


I was able to run vpn instance successfully but during the boot processing, I got the following errors so that the OpenVPN server fails to launch. No more debug messages...

Did I miss something?


Downloading payload from userdata --2011-04-11 09:49:43-- http://169.254.169.254/latest/user-data Connecting to 169.254.169.254:80... connected. HTTP request sent, awaiting response... 500 Internal Server Error 2011-04-11 09:49:43 ERROR 500: Internal Server Error.

2011-04-11 05:08:49 -0600 answered a question nova-manage vpn run is not working!

FYI. genvpn_sh_path refers to 'geninter.sh' instead of 'genvpn.sh' in nova/crypto.py. Changing it to 'genvpn.sh', It is now working....

2011-04-11 02:40:39 -0600 answered a question nova-manage vpn run is not working!

I made some work around with the bug, but still get the following errors!

=================================================

2011-04-11 11:36:28,305 DEBUG nova.cloudpipe [-] Launching VPN for NOVAADMPRJ from (pid=31141) launch_vpn_instance /root/openstack/nova/nova/cloudpipe/pipelib.py:97 2011-04-11 11:36:28,414 DEBUG nova.utils [-] backend <module 'nova.db.sqlalchemy.api'="" from="" '="" root="" openstack="" nova="" nova="" db="" sqlalchemy="" api.pyc'=""> from (pid=31141) __get_backend /root/openstack/nova/nova/utils.py:427 2011-04-11 11:36:28,499 DEBUG nova.utils [-] Running cmd (subprocess): sh /root/openstack/state/CA/geninter.sh NOVAADMPRJ /C=US/ST=California/L=MountainView/O=AnsoLabs/OU=NovaDev/CN=project-ca-NOVAADMPRJ-2011-04-11T02:36:28Z from (pid=31141) execute /root/openstack/nova/nova/utils.py:150 2011-04-11 11:36:28,576 DEBUG nova.utils [-] Result was 1 from (pid=31141) execute /root/openstack/nova/nova/utils.py:166 2011-04-11 11:36:28,577 CRITICAL nova [-] Unexpected error while running command. Command: sh /root/openstack/state/CA/geninter.sh NOVAADMPRJ /C=US/ST=California/L=MountainView/O=AnsoLabs/OU=NovaDev/CN=project-ca-NOVAADMPRJ-2011-04-11T02:36:28Z Exit code: 1 Stdout: '' Stderr: "Generating a 1024 bit RSA private key\n...........................++++++\n...........++++++\nwriting new private key to 'private/cakey.pem'\n-----\nUsing configuration from ./openssl.cnf\nchown: invalid user: nova:nogroup'\n" (nova): TRACE: Traceback (most recent call last): (nova): TRACE: File "/root/openstack/nova/bin/nova-manage", line 1122, in <module> (nova): TRACE: main() (nova): TRACE: File "/root/openstack/nova/bin/nova-manage", line 1111, in main (nova): TRACE: fn(*argv) (nova): TRACE: File "/root/openstack/nova/bin/nova-manage", line 170, in run (nova): TRACE: self.pipe.launch_vpn_instance(project_id) (nova): TRACE: File "/root/openstack/nova/nova/cloudpipe/pipelib.py", line 105, in launch_vpn_instance (nova): TRACE: user_data=self.get_encoded_zip(project_id), (nova): TRACE: File "/root/openstack/nova/nova/cloudpipe/pipelib.py", line 77, in get_encoded_zip (nova): TRACE: crypto.generate_vpn_files(project_id) (nova): TRACE: File "/root/openstack/nova/nova/crypto.py", line 236, in generate_vpn_files (nova): TRACE: _ensure_project_folder(project_id) (nova): TRACE: File "/root/openstack/nova/nova/crypto.py", line 223, in _ensure_project_folder (nova): TRACE: _project_cert_subject(project_id)) (nova): TRACE: File "/root/openstack/nova/nova/utils.py", line 173, in execute (nova): TRACE: cmd=' '.join(cmd)) (nova): TRACE: ProcessExecutionError: Unexpected error while running command. (nova): TRACE: Command: sh /root/openstack/state/CA/geninter.sh NOVAADMPRJ /C=US/ST=California/L=MountainView/O=AnsoLabs/OU=NovaDev/CN=project-ca-NOVAADMPRJ-2011-04-11T02:36:28Z (nova): TRACE: Exit code: 1 (nova): TRACE: Stdout: '' (nova): TRACE: Stderr: "Generating a 1024 bit RSA private key\n...........................++++++\n...........++++++\nwriting new private key to 'private/cakey.pem'\n-----\nUsing configuration from ./openssl.cnf\nchown: invalid user:nova:nogroup'\n" (nova): TRACE:

2011-04-11 02:18:38 -0600 answered a question nova-manage vpn run is not working!

Hi Vish, I was almost in sleep as writing the confusing question :)

Anyway, I was mean that the vpn instance didn't success to run with 'nova-manage run vpn PROJECTID', but with 'euca-run-instance' for confirming there's no problem with the image itself. The flags did not work for me. However, I found some bug in nova/crypto.py regarding ca_path reference reported Bug #757033.

2011-04-07 20:00:46 -0600 asked a question nova-manage vpn run is not working!

Hi,

I'm trying to run VPN. I made a cloudpipe image and add the image id to nova.conf with --vpn_image_id=xxx. Compute knows it is a cloudpipe image, because it assigns 10.0.0.2 address to the instance when I run the image with euca-run-instance command. But it will fail to run openvpn server without autorun.sh.

Don't know why 'nova-manage vpn run'. It does not show any error messages or log. It just do nothing. Any idea?

2011-04-07 00:33:00 -0600 answered a question Multi node deploy: instance spawning failure

Great! I will try Glance, too.

2011-04-06 07:34:37 -0600 answered a question network interfaces confusion

Hi, check network_manager in nova.conf file. It's on $NOVA_DIR/bin/ or /etc if you installed with deploy tool. I guess it's VlanManager if you haven't changed it.

In that case, nova-network fetches IP address for VM from dnsmasq at instance creation. You shouldn't assign IP address for network interface of VM on your host OS.

Just run instance and check the IP address displayed as a result of euca-describe-instance. You can ping or ssh to the VM with that IP address. No additional settings are required.

If you're Korean, visit http://www.openstack.or.kr :)

2011-04-06 07:19:42 -0600 answered a question Multi node deploy: instance spawning failure

Thanks Vish, Everett. Solved this problem by mounting controller's images directory on the compute host using nfs. Unfortunately, I have no Swift running on my system so that I cannot use Glance.

2011-04-05 08:56:53 -0600 asked a question Multi node deploy: instance spawning failure

Hello,

I have deployed latest nova on 2 host machines, one for controller(nova-api, nova-scheduler, nova-network, nova-objectstore) and the other for compute(nova-compute, nova-scheduler).

Problem is, as I hit run instance from the controller node, following compute error occurs on the compute node. nova-compute, nova-scheduler service was successfully added on the service table and euca-describe-instance show the state of instance spawning fail.

root@cloud02:~/openstack# nova-manage service list cloud02 nova-scheduler enabled :-) 2011-04-05 09:01:01 cloud02 nova-network enabled :-) 2011-04-05 09:01:01 cloud01 nova-scheduler enabled :-) 2011-04-05 08:59:23 cloud01 nova-compute enabled :-) 2011-04-05 08:59:17

root@cloud02:~/openstack# euca-describe-instances RESERVATION r-etss4atr NOVAADMPRJ default INSTANCE i-00000002 ami-0640184b 10.0.0.3 10.0.0.3 failed to spawn novaadm (NOVAADMPRJ, cloud01) 0 m1.small 2011-04-05T08:27:10Z nova

=============================================================================

2011-04-05 17:48:41,923 AUDIT nova.compute.manager [M39CSSE2RGAXIFEYZ6HY novaadm NOVAADMPRJ] instance 2: starting... 2011-04-05 17:48:42,018 DEBUG nova.rpc [-] Making asynchronous call on network.cloud02 ... from (pid=4290) call /root/openstack/nova/nova/rpc.py:345 2011-04-05 17:48:42,019 DEBUG nova.rpc [-] MSG_ID is 1d0b70e00fc94c14a7ed0bc91a17dd60 from (pid=4290) call /root/openstack/nova/nova/rpc.py:348 2011-04-05 17:48:42,458 DEBUG nova.virt.libvirt_conn [-] instance instance-00000002: starting toXML method from (pid=4290) to_xml /root/openstack/nova/nova/virt/libvirt_conn.py:899 2011-04-05 17:48:42,531 DEBUG nova.virt.libvirt_conn [-] instance instance-00000002: finished toXML method from (pid=4290) to_xml /root/openstack/nova/nova/virt/libvirt_conn.py:941 2011-04-05 17:48:42,582 INFO nova [-] called setup_basic_filtering in nwfilter 2011-04-05 17:48:42,582 INFO nova [-] ensuring static filters 2011-04-05 17:48:42,648 DEBUG nova.utils [-] Attempting to grab semaphore "iptables" for method "apply"... from (pid=4290) inner /root/openstack/nova/nova/utils.py:594 2011-04-05 17:48:42,648 DEBUG nova.utils [-] Attempting to grab file lock "iptables" for method "apply"... from (pid=4290) inner /root/openstack/nova/nova/utils.py:599 2011-04-05 17:48:42,653 DEBUG nova.utils [-] Running cmd (subprocess): sudo iptables-save -t filter from (pid=4290) execute /root/openstack/nova/nova/utils.py:150 2011-04-05 17:48:42,665 DEBUG nova.utils [-] Running cmd (subprocess): sudo iptables-restore from (pid=4290) execute /root/openstack/nova/nova/utils.py:150 2011-04-05 17:48:42,677 DEBUG nova.utils [-] Running cmd (subprocess): sudo iptables-save -t nat from (pid=4290) execute /root/openstack/nova/nova/utils.py:150 2011-04-05 17:48:42,689 DEBUG nova.utils [-] Running cmd (subprocess): sudo iptables-restore from (pid=4290) execute /root/openstack/nova/nova/utils.py:150 2011-04-05 17:48:42,718 DEBUG nova.utils [-] Running cmd (subprocess): mkdir -p /root/openstack/state/instances/instance-00000002/ from (pid=4290) execute /root/openstack/nova/nova/utils.py:150 2011-04-05 17:48:42,726 INFO nova.virt.libvirt_conn [-] instance instance-00000002: Creating image 2011-04-05 17:48:42,776 DEBUG nova.utils [-] Attempting to grab semaphore "115ec19b" for method "call_if_not_exists"... from (pid=4290) inner /root/openstack/nova/nova/utils.py:594 2011-04-05 17:48:42,777 DEBUG nova.utils [-] Running cmd (subprocess): cp /root ... (more)

2011-02-15 02:09:02 -0600 answered a question Should I do something for meta-data server?

Thanks Everett, but it still not work. Actually it worked well before, I don't know why it has just stopped working. I tested the following command anyway.

GET http://$NOVA_API_IP:8773/latest/user-data

Traceback (most recent call last): File "/usr/lib/pymodules/python2.6/eventlet/wsgi.py", line 336, in handle_one_response result = self.application(self.environ, start_response) File "/usr/lib/pymodules/python2.6/paste/urlmap.py", line 203, in __call__ return app(environ, start_response) File "/usr/lib/pymodules/python2.6/webob/dec.py", line 147, in __call__ resp = self.call_func(req, args, *self.kwargs) File "/usr/lib/pymodules/python2.6/webob/dec.py", line 208, in call_func return self.func(req, args, *kwargs) File "/root/Work/openstack/nova/nova/api/ec2/__init__.py", line 60, in __call__ rv = req.get_response(self.application) File "/usr/lib/pymodules/python2.6/webob/request.py", line 918, in get_response application, catch_exc_info=False) File "/usr/lib/pymodules/python2.6/webob/request.py", line 886, in call_application app_iter = application(self.environ, start_response) File "/usr/lib/pymodules/python2.6/webob/dec.py", line 147, in __call__ resp = self.call_func(req, args, *self.kwargs) File "/usr/lib/pymodules/python2.6/webob/dec.py", line 208, in call_func return self.func(req, args, *kwargs) File "/root/Work/openstack/nova/nova/api/ec2/metadatarequesthandler.py", line 74, in __call__ meta_data = cc.get_metadata(remote_address) File "/root/Work/openstack/nova/nova/api/ec2/cloud.py", line 143, in get_metadata instance_ref = self.compute_api.get_all(ctxt, fixed_ip=address) File "/root/Work/openstack/nova/nova/compute/api.py", line 333, in get_all return self.db.fixed_ip_get_instance(context, fixed_ip) File "/root/Work/openstack/nova/nova/db/api.py", line 298, in fixed_ip_get_instance return IMPL.fixed_ip_get_instance(context, address) File "/root/Work/openstack/nova/nova/db/sqlalchemy/api.py", line 108, in wrapper return f(args, *kwargs) File "/root/Work/openstack/nova/nova/db/sqlalchemy/api.py", line 607, in fixed_ip_get_instance fixed_ip_ref = fixed_ip_get_by_address(context, address) File "/root/Work/openstack/nova/nova/db/sqlalchemy/api.py", line 108, in wrapper return f(args, *kwargs) File "/root/Work/openstack/nova/nova/db/sqlalchemy/api.py", line 597, in fixed_ip_get_by_address raise exception.NotFound(_('No floating ip for address %s') % address) NotFound: No floating ip for address $NOVA_API_IP

2011-02-14 10:14:42 -0600 asked a question Should I do something for meta-data server?

ami-tty image downloaded using 'nova.sh install' succeeds to run but instance console log reports some errors. As a result, i could ping the instance but could not access with ssh to the instance.

...

Lease of 10.0.0.5 obtained, lease time 120^M starting DHCP forEthernet interface eth0 [ ^[[1;32mOK^[[0;39m ]^M cloud-setup: checking http://169.254.169.254/2009-04-04/meta-data/instance-id%5EM (http://169.254.169.254/2009-04-04/met...) cloud-setup: failed 1/30: up 7.97. iid had 1.0^M cloud-setup: failed 2/30: up 9.18. iid had 1.0^M cloud-setup: failed 3/30: up 10.35. iid had 1.0^M cloud-setup: failed 4/30: up 11.52. iid had 1.0^M cloud-setup: failed 5/30: up 12.70. iid had 1.0^M cloud-setup: failed 6/30: up 13.88. iid had 1.0^M cloud-setup: failed 7/30: up 15.06. iid had 1.0^M cloud-setup: failed 8/30: up 16.24. iid had 1.0^M cloud-setup: failed 9/30: up 17.43. iid had 1.0^M cloud-setup: failed 10/30: up 18.62. iid had 1.0^M cloud-setup: failed 11/30: up 19.81. iid had 1.0^M cloud-setup: failed 12/30: up 21.00. iid had 1.0^M cloud-setup: failed 13/30: up 22.20. iid had 1.0^M cloud-setup: failed 14/30: up 23.40. iid had 1.0^M cloud-setup: failed 15/30: up 24.60. iid had 1.0^M cloud-setup: failed 16/30: up 25.80. iid had 1.0^M cloud-setup: failed 17/30: up 27.01. iid had 1.0^M cloud-setup: failed 18/30: up 28.22. iid had 1.0^M cloud-setup: failed 19/30: up 29.43. iid had 1.0^M cloud-setup: failed 20/30: up 30.65. iid had 1.0^M cloud-setup: failed 21/30: up 31.86. iid had 1.0^M cloud-setup: failed 22/30: up 33.08. iid had 1.0^M cloud-setup: failed 23/30: up 34.30. iid had 1.0^M cloud-setup: failed 24/30: up 35.60. iid had 1.0^M cloud-setup: failed 25/30: up 36.89. iid had 1.0^M cloud-setup: failed 26/30: up 38.11. iid had 1.0^M cloud-setup: failed 27/30: up 39.34. iid had 1.0^M cloud-setup: failed 28/30: up 40.56. iid had 1.0^M cloud-setup: failed 29/30: up 41.82. iid had 1.0^M cloud-setup: failed 30/30: up 43.05. iid had 1.0^M cloud-setup: after 30 fails, debugging^M cloud-setup: running debug (30 tries reached)^M ############ debug start ##############^M

/etc/rc.d/init.d/sshd start^M

stty: /dev/console^M generating DSS host key [^[[1;33mWATING^[[0;39m]^[[-11G^[[1;34m..^[[0;39m [ ^[[1;32mOK^[[0;39m ]^M generating RSA host key [^[[1;33mWATING^[[0;39m]^[[-11G^[[1;34m..^[[0;39m [ ^[[1;32mOK^[[0;39m ]^M startup dropbear [ ^[[1 ... (more)

2011-01-21 03:29:20 -0600 answered a question Couldn't start nova-compute service due to sql error

You should create DB for nova first.

mysql -p$MYSQL_PASS -e 'CREATE DATABASE nova'

and then create tables for nova. I guess this might have been updated in rev.581.

nova-manage db sync

2011-01-21 01:13:51 -0600 answered a question Couldn't run instance due to dnsmasq error.

Check if dnsmasq is running already.

ps -aef | grep dnsmasq

If you have running dnsmasq, kill it and retry.