Please refer my vm creation script<span></span><div><span style="font-family:Helvetica;font-size:15px;white-space:nowrap"><a href="http://blog.woosum.net/archives/990">http://blog.woosum.net/archives/990</a></span><br dir="ltr">
<br>2012년 11월 27일 화요일에 Ahmed Al-Mehdi님이 작성:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
<br>
If you don't mind me asking, how did you create/launch the VM instance<br>
using the Cirros image? Did you use Horizon or command line? If command<br>
line, can you please share the commands you used?<br>
<br>
Thank you,<br>
Ahmed.<br>
<br>
<br>
On 11/27/12 1:31 AM, "이창만" <<a>cm224.lee@samsung.com</a>> wrote:<br>
<br>
>Thanks a lot guys.<br>
><br>
>I've solved my issue for your advice. :)<br>
>It was caused by Port_id and Nova.conf of compute node.<br>
>Now I have to deploy swift and lunch vm instance using iso.<br>
>I'm appreciate if you answer my foolish question.<br>
><br>
>Best Regard.<br>
><br>
><br>
>> -----Original Message-----<br>
>> From: Choe, Cheng-Dae [mailto:<a>whitekid@gmail.com</a>]<br>
>> Sent: Tuesday, November 27, 2012 4:46 PM<br>
>> To: 이창만<br>
>> Cc: <a>openstack@lists.launchpad.net</a><br>
>> Subject: Re: [Openstack] Question: how to make floating ip pools?<br>
>><br>
>> Hi...<br>
>> --<br>
>> Choe, Cheng-Dae<br>
>> <a href="http://blog.woosum.net" target="_blank">http://blog.woosum.net</a><br>
>> twitter: kiddtm<br>
>><br>
>> 2012. 11. 27., 오후 2:59, 이창만 <<a>cm224.lee@samsung.com</a>> 작성:<br>
>><br>
>> ><br>
>> > Hello,<br>
>> ><br>
>> > I am doing below guide.<br>
>> > <a href="https://github.com/mseknibilel/OpenStack-Folsom-Install-" target="_blank">https://github.com/mseknibilel/OpenStack-Folsom-Install-</a><br>
>> guide/blob/VLAN/2NICs/OpenStack_Folsom_Install_Guide_WebVersion.rst<br>
>> ><br>
>> > At Ch.11 Your First VM, I've encountered a error.<br>
>> > My question is:<br>
>> > 1) What is the $put_id_floating_ip and $put_id_vm_port?<br>
>> > e.g.) $ quantum floatingip-associate $put_id_floating_ip<br>
>>$put_id_vm_port<br>
>> put_id_floating_ip is your floating id. below command show your<br>
>>floatingip.<br>
>> # quantum floatingip-list<br>
>><br>
>>+--------------------------------------+------------------+--------------<br>
>>--<br>
>> -----+--------------------------------------+<br>
>> | id | fixed_ip_address |<br>
>> floating_ip_address | port_id |<br>
>><br>
>>+--------------------------------------+------------------+--------------<br>
>>--<br>
>> -----+--------------------------------------+<br>
>> | abfb3889-32f4-4854-bd61-6fb37e406faa | 172.16.1.3 | 10.100.1.131<br>
>> | 3be818d4-b4e9-4e9f-b42f-66701bd57b47 |<br>
>><br>
>>+--------------------------------------+------------------+--------------<br>
>>--<br>
>> -----+--------------------------------------+<br>
>><br>
>> $put_id_vm_port is that your vm's port that attached your network. when<br>
>> your instance and floatingip is like below<br>
>> root@control:~# nova list<br>
>><br>
>>+--------------------------------------+-------+--------+----------------<br>
>>--<br>
>> +<br>
>> | ID | Name | Status | Networks<br>
>> |<br>
>><br>
>>+--------------------------------------+-------+--------+----------------<br>
>>--<br>
>> +<br>
>> | a7b32a1d-25b7-4efe-97ba-1dafd478ef2b | test0 | ACTIVE |<br>
>>admin=172.16.1.3<br>
>> |<br>
>><br>
>>+--------------------------------------+-------+--------+----------------<br>
>>--<br>
>> +<br>
>> root@control:~# quantum port-list --<br>
>>--device_id=a7b32a1d-25b7-4efe-97ba-<br>
>> 1dafd478ef2b<br>
>><br>
>>+--------------------------------------+------+-------------------+------<br>
>>--<br>
>><br>
>>-------------------------------------------------------------------------<br>
>>--<br>
>> +<br>
>> | id | name | mac_address |<br>
>> fixed_ips<br>
>> |<br>
>><br>
>>+--------------------------------------+------+-------------------+------<br>
>>--<br>
>><br>
>>-------->> -----+--------------------------------------+<br>
>><br>
>> you can associate floatingip to instance like this.<br>
>> # quantum floatingip-associate abfb3889-32f4-4854-bd61-6fb37e406faa<br>
>> 3be818d4-b4e9-4e9f-b42f-66701bd57b47<br>
>><br>
>><br>
>> ><br>
>> > 2) How can I know whether controller node and compute is connected?<br>
>><br>
>> $ nova-manage service list<br>
>> command show that what nova services is running.<br>
>><br>
>> ><br>
>> > The status of Controller node - I can't see any resources.<br>
>> > a.Overview of Project on horizon<br>
>> > i.Quota Summary is empty<br>
>> > 1.Used of Available Instances : NULL<br>
>> > 2.Used of Available vCPUs : NULL<br>
>> > 3.Used MB of MB Available RAM : NULL<br>
>> ><br>
>> > == Error Log ==<br>
>> ><br>
>> > root@node1:/home/zeus# quantum floatingip-create --tenant-id<br>
>> 7230c184c85141b59f6a0df0843ea0d2 ext_net<br>
>> > Created a new floatingip:<br>
>> > +---------------------+--------------------------------------+<br>
>> > | Field | Value |<br>
>> > +---------------------+--------------------------------------+<br>
>> > | fixed_ip_address | |<br>
>> > | floating_ip_address | 192.168.2.3 |<br>
>> > | floating_network_id | 1d6b740f-3f19-482b-a0b8-b4bcd83d5b3b |<br>
>> > | id | fd6429bd-cf71-45c0-bf0b-3c80e1fe527b |<br>
>> > | port_id | |<br>
>> > | router_id | |<br>
>> > | tenant_id | 7230c184c85141b59f6a0df0843ea0d2 |<br>
>> > +---------------------+--------------------------------------+<br>
>> > root@node1:/home/zeus# quantum port-list<br>
>> ><br>
>>+--------------------------------------+------+-------------------+------<br>
>><br>
>>-------------------------------------------------------------------------<br>
>>--<br>
>> ---+<br>
>> > | id | name | mac_address |<br>
>> fixed_ips<br>
>> |<br>
>> ><br>
>>+--------------------------------------+------+-------------------+------<br>
>><br>
>>-------------------------------------------------------------------------<br>
>>--<br>
>> ---+<br>
>> > | 1a284c3e-bacf-4281-a1a2-b8d3f485dab1 | | fa:16:3e:0d:4e:c0 |<br>
>> {"subnet_id": "994af63f-d5f2-492d-9229-aa878651b95d", "ip_address":<br>
>> "192.168.2.2"} |<br>
>> > | 1a93a78e-cb59-4647-bf13-49e3553bb2aa | | fa:16:3e:b1:9c:10 |<br>
>> {"subnet_id": "b9a8c9b4-7ebf-43c6-b8d5-afb44c13ba54", "ip_address":<br>
>> "10.10.10.1"} |<br>
>> > | d9b3496d-89e6-4ae7-b117-e22048acb6ef | | fa:16:3e:50:e9:91 |<br>
>> {"subnet_id": "994af63f-d5f2-492d-9229-aa878651b95d", "ip_address":<br>
>> "192.168.2.3"} |<br>
>> > | ed32a365-48ce-4f94-8b7f-6e02c8d876d3 | | fa:16:3e:2d:bc:93 |<br>
>> {"subnet_id": "b9a8c9b4-7ebf-43c6-b8d5-afb44c13ba54", "ip_address":<br>
>> "10.10.10.2"} |<br>
>> ><br>
>>+--------------------------------------+------+-------------------+------<br>
>><br>
>>-------------------------------------------------------------------------<br>
>>--<br>>> ---+<br>
>> > root@node1:/home/zeus# quantum floatingip-associate<br>
>>fd6429bd-cf71-45c0-<br>
>> bf0b-3c80e1fe527b 1a284c3e-bacf-4281-a1a2-b8d3f485dab1<br>
>> > Bad floatingip request: Port 1a284c3e-bacf-4281-a1a2-b8d3f485dab1 is<br>
>> associated with a different tenant than Floating IP fd6429bd-cf71-45c0-<br>
>> bf0b-3c80e1fe527b and therefore cannot be bound.<br>
>> > root@node1:/home/zeus# quantum floatingip-associate<br>
>>fd6429bd-cf71-45c0-<br>
>> bf0b-3c80e1fe527b d9b3496d-89e6-4ae7-b117-e22048acb6ef<br>
>> > Bad floatingip request: Port d9b3496d-89e6-4ae7-b117-e22048acb6ef is<br>
>> associated with a different tenant than Floating IP fd6429bd-cf71-45c0-<br>
>> bf0b-3c80e1fe527b and therefore cannot be bound.<br>
>> ><br>
>> ><br>
>> ><br>
>> ><br>
>> ><br>
>> ><br>
>> ><br>
>> ><br>
>> ><br>
>> ><br>
>> > == Network configuration ==<br>
>> ><br>
>> ><br>
>> > root@node1:/home/zeus# ifconfig -a<br>
>> > br-eth1 Link encap:Ethernet HWaddr 00:02:2a:d7:fd:fe<br>
>> > BROADCAST MULTICAST MTU:1500 Metric:1<br>
>> > RX packets:126 errors:0 dropped:0 overruns:0 frame:0<br>
>> > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0<br>
>> > collisions:0 txqueuelen:0<br>
>> > RX bytes:14123 (14.1 KB) TX bytes:0 (0.0 B)<br>
>> ><br>
>> > br-ex Link encap:Ethernet HWaddr 1c:6f:65:40:2b:c0<br>
>> > inet addr:192.168.2.10 Bcast:192.168.2.255<br>
>>Mask:255.255.255.0<br>
>> > inet6 addr: fe80::1e6f:65ff:fe40:2bc0/64 Scope:Link<br>
>> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br>
>> > RX packets:18802 errors:0 dropped:0 overruns:0 frame:0<br>
>> > TX packets:19881 errors:0 dropped:0 overruns:0 carrier:0<br>
>> > collisions:0 txqueuelen:0<br>
>> > RX bytes:8561104 (8.5 MB) TX bytes:9941901 (9.9 MB)<br>
>> ><br>
>> > br-int Link encap:Ethernet HWaddr 06:3c:48:84:1f:46<br>
>> > BROADCAST MULTICAST MTU:1500 Metric:1<br>
>> > RX packets:12 errors:0 dropped:0 overruns:0 frame:0<br>
>> > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0<br>
>> > collisions:0 txqueuelen:0<br>
>> > RX bytes:936 (936.0 B) TX bytes:0 (0.0 B)<br>
>> ><br>
>> > eth0 Link encap:Ethernet HWaddr 1c:6f:65:40:2b:c0<br>
>> > inet6 addr: fe80::1e6f:65ff:fe40:2bc0/64 Scope:Link<br>
>> > UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1<br>
>> > RX packets:21627 errors:0 dropped:0 overruns:0 frame:0<br>
>> > TX packets:22537 errors:0 dropped:0 overruns:0 carrier:0<br>
>> > collisions:0 txqueuelen:1000<br>
>> > RX bytes:8747289 (8.7 MB) TX bytes:10117341 (10.1 MB)<br>
>> ><br>
>> > eth1 Link encap:Ethernet HWaddr 00:02:2a:d7:fd:fe<br>
>> > inet addr:100.10.10.51 Bcast:100.10.10.255<br>
>>Mask:255.255.255.0<br>
>> > inet6 addr: fe80::202:2aff:fed7:fdfe/64 Scope:Link<br>
>> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br>
>> > RX packets:117 errors:0 dropped:0 overruns:0 frame:0<br>
>> > TX packets:21 errors:0 dropped:0 overruns:0 carrier:0<br>
>> > collisions:0 txqueuelen:1000<br>
>> > RX bytes:13425 (13.4 KB) TX bytes:1562 (1.5 KB)<br>
>> ><br>
>> > int-br-eth1 Link encap:Ethernet HWaddr 22:42:20:65:f6:d4<br>
>> > inet6 addr: fe80::2042:20ff:</blockquote></div><br><br>-- <br>Choe, Cheng-Dae<br>Blog: <a href="http://www.woosum.net" target="_blank">http://blog.woosum.net</a><br>