openstack team mailing list archive

Thread
Date
Re: Question: how to make floating ip pools?

To: Ahmed Al-Mehdi <ahmed@xxxxxxxxxx>
From: "Choe, Cheng-Dae" <whitekid@xxxxxxxxx>
Date: Wed, 28 Nov 2012 11:17:04 +0900
Cc: Bilel Msekni <bilel.msekni@xxxxxxxxxxxxxxxxxxx>, "openstack@xxxxxxxxxxxxxxxxxxx" <openstack@xxxxxxxxxxxxxxxxxxx>
In-reply-to: <CCDA1AF1.52E4%ahmed@coraid.com>
Hi..~
--
Choe, Cheng-Dae
http://blog.woosum.net
twitter: kiddtm

2012. 11. 28., 오전 12:28, Ahmed Al-Mehdi <ahmed@xxxxxxxxxx> 작성:

> Thank you for sending the link to your script, much appreciated.
> 
> Can you please shed some light when to use the "—tenant_id=admin" and "--tenant_id=proj_one" (a tenant other than admin tenant) when issuing the quantum command, e.g. creating external/internl network, sub-net, launching VM, etc.

when first run it require to create external network. so we require admin tenant, admin user
$ . openrc admin
$ vm_create.sh     # without argument then it create external/internal networks only
$ vm_create.sh admin_vm  # then create admin user's instance named "admin_vm"
$ . openrc demo                # switch to demo tenant
$ vm_create.sh demo_vm  # create demo tenant's internal networks and create instance named "demo_vm"

in summary
- when create external network, it requires admin tenant, admin user
- the other things are run by and tenant, user

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

Re: Question: how to make floating ip pools?
From: Ahmed Al-Mehdi, 2012-11-27