Launch an Instance from OpenStack (Liberty) Dashboard

You may also like...

10 Responses

  1. Dhanapal says:

    Dear Pradeep,
    Thanks for providing such a wonderful step by step guide for bringing up instance. Have tried to bring up the same fedora image provided here with virtual box. My virtual box has interface with ip 192.168.56.103 and dashboard is being accessed using this ip inside virtual box.

    Now, I brought up the instance by following the steps mentioned and my instance associated floating ip which is allocated from the external pool as 192.168.56.51.

    When I tried to ssh 192.168.56.51, getting no route to host error.

    [email protected]:~$ ssh -i myssh-keys.pem 192.168.56.51 -l fedora
    ssh: connect to host 192.168.56.51 port 22: No route to host
    [email protected]:~$

    List of interface in the system:
    ——————————–
    [email protected]:~$ ifconfig
    br-ex Link encap:Ethernet HWaddr 26:69:31:53:f7:4b
    inet addr:192.168.56.1 Bcast:0.0.0.0 Mask:255.255.255.0
    inet6 addr: 2001:db8::2/64 Scope:Global
    inet6 addr: fe80::2469:31ff:fe53:f74b/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:36 errors:0 dropped:2 overruns:0 frame:0
    TX packets:157 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:2900 (2.9 KB) TX bytes:7374 (7.3 KB)

    enp0s3 Link encap:Ethernet HWaddr 08:00:27:1f:15:b0
    inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0
    inet6 addr: fe80::a00:27ff:fe1f:15b0/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:1817138 errors:0 dropped:0 overruns:0 frame:0
    TX packets:444940 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:2011689572 (2.0 GB) TX bytes:32372620 (32.3 MB)

    enp0s8 Link encap:Ethernet HWaddr 08:00:27:60:0c:84
    inet addr:192.168.56.103 Bcast:192.168.56.255 Mask:255.255.255.0
    inet6 addr: fe80::a00:27ff:fe60:c84/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:4575 errors:0 dropped:0 overruns:0 frame:0
    TX packets:123 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:430030 (430.0 KB) TX bytes:15096 (15.0 KB)

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:65536 Metric:1
    RX packets:1522434 errors:0 dropped:0 overruns:0 frame:0
    TX packets:1522434 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:1841120824 (1.8 GB) TX bytes:1841120824 (1.8 GB)

    qbre4cc1c39-a6 Link encap:Ethernet HWaddr a6:b3:d5:dd:c4:bb
    UP BROADCAST RUNNING MULTICAST MTU:1450 Metric:1
    RX packets:49 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:13056 (13.0 KB) TX bytes:0 (0.0 B)

    qvbe4cc1c39-a6 Link encap:Ethernet HWaddr a6:b3:d5:dd:c4:bb
    inet6 addr: fe80::a4b3:d5ff:fedd:c4bb/64 Scope:Link
    UP BROADCAST RUNNING PROMISC MULTICAST MTU:1450 Metric:1
    RX packets:7 errors:0 dropped:0 overruns:0 frame:0
    TX packets:52 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:738 (738.0 B) TX bytes:14040 (14.0 KB)

    qvoe4cc1c39-a6 Link encap:Ethernet HWaddr 02:25:f0:17:cd:58
    inet6 addr: fe80::25:f0ff:fe17:cd58/64 Scope:Link
    UP BROADCAST RUNNING PROMISC MULTICAST MTU:1450 Metric:1
    RX packets:52 errors:0 dropped:0 overruns:0 frame:0
    TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:14040 (14.0 KB) TX bytes:738 (738.0 B)

    tape4cc1c39-a6 Link encap:Ethernet HWaddr fe:16:3e:5f:71:5c
    inet6 addr: fe80::fc16:3eff:fe5f:715c/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1450 Metric:1
    RX packets:45 errors:0 dropped:0 overruns:0 frame:0
    TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:500
    RX bytes:13302 (13.3 KB) TX bytes:738 (738.0 B)

    virbr0 Link encap:Ethernet HWaddr 52:54:00:cc:a6:ba
    inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
    UP BROADCAST MULTICAST MTU:1500 Metric:1
    RX packets:0 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:0 (0.0 B) TX bytes:0 (0.0 B)

    [email protected]:~$

    Route table entries are:
    ————————-
    [email protected]:~$ route -n
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface
    0.0.0.0 10.0.2.2 0.0.0.0 UG 0 0 0 enp0s3
    10.0.0.0 192.168.56.10 255.255.255.0 UG 0 0 0 enp0s8
    10.0.2.0 0.0.0.0 255.255.255.0 U 0 0 0 enp0s3
    192.168.56.0 0.0.0.0 255.255.255.0 U 0 0 0 enp0s8
    192.168.56.0 0.0.0.0 255.255.255.0 U 0 0 0 br-ex
    192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0
    [email protected]:~$

    It would be great help if you provide any input on this.

    Thanks in Advance.

  2. Hello Dhanapal ,

    Have you configured Security firewall rules for the VM ?, by default SSH port is blocked.

    • Dhanapal says:

      Dear Pradeep,
      Thanks for your reply. I have not configured it, could you please give me a pointer on how to do it?
      I am using windows as host machine and guest as ubuntu wily server (Installed devstack on ubuntu server).

      Thanks for your help

  3. Vaibhav Sharma says:

    Hello Pradeep,

    I have installed Openstack Mitaka using three nodes: Controller (IP Address: 192.168.100.62), Compute (IP Address: 192.168.100.63) and Networking Node (192.168.100.64).
    I have followed your website to do the installation and then network bridging. After successful installation I have followed above steps to create project, user, image, network and router. At last I have created an instance successfully.

    Internal network is configured as 10.10.10.0/24
    External network is configured as 192.168.100.0/34, Gateway IP is 192.168.100.1 and Allocation pool IP is 192.168.100.120, 192.168.100.125

    After creating instance, I am able to access the instance from the console on OpenStack Dashboard.

    Router External IP is listed as 192.168.100.120
    Instance External IP is listed as 192.168.100.121

    I have created security rules for SSH and ICMP but still I am not able to do SSH and ping the instance using the External IP (192.168.100.121)

    Please let me know if you need any other information.

    It would be great help if you provide any input on this. Please provide you email address if possible.

    Thanks in Advance.

    Regards,
    Vaibhav

  4. jribeauv says:

    Hi,

    Great post !!
    Congratulations.

    I follow this post for installing all-in-one Liberty on CentOs7.

    All is fine , except I got following error in Horizon dashboard :

    Error: Unable to retrieve volume limit information.

    I checked with Liberty2 and Liberty-3 , I got error in both cases.

    Did you encounter this error ?

    Thx for help.

    Regards,

    J.P.

  5. arpit says:

    great work i am trying on flat network where ip address of cloud can ping outside computer without public ip address i am frusted please help me

  6. vishal rai says:

    if you are getting error Unable to retrieve volume limit information . then you have to increase the number of virtual cpu(vcp if you are installing inside vmwrae workstation or vmware ESXi). The openstack requires a lot of CPU resources. Definitely your error will remove if assign a more cpu to compute node.

  7. Vikas says:

    Thanks for sharing the instructions.
    I followed the document and installed openstack.
    I am able to ping and ssh to the openstack instance but from openstack I am not able to ping the external default gateway and cannot access internet. Can you please help with this issue.

  8. Sampath says:

    Hi,
    I am not able to ping external network its showing router port is down.

Leave a Reply

Your email address will not be published. Required fields are marked *