This guide shows you how to launch an instance of Fedora 22 image that we added in OpenStack Kilo on Ubuntu 14.04.2 – Glance. Here we will be using command line interface on the controller node to create an instance, this tutorial launches an instance using OpenStack Networking (neutron).
Load the admin credentials on the controller node.
# source demo-openrc.sh
Almost all cloud images uses public keys for authentication instead of user/password authentication. Before launching an instance, we must create a public/private key pair.
Generate and add a key pair.
# nova keypair-add my-key
Copy the output of above command and save it into any file, this key should be used with ssh command to login to instance.
List the available key pair’s.
# nova keypair-list +--------+-------------------------------------------------+ | Name | Fingerprint | +--------+-------------------------------------------------+ | my-key | 0a:b2:30:cb:54:fc:c4:69:29:00:19:ef:38:8d:2e:2d | +--------+-------------------------------------------------+
Launch an instance:
To launch an instance, we must need to know flavors, available images, networks, and security groups.
List the available flavors, this is nothing but a predefined allocation of cpu, memory and disk.
# nova flavor-list +----+-----------+-----------+------+-----------+------+-------+-------------+-----------+ | ID | Name | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor | Is_Public | +----+-----------+-----------+------+-----------+------+-------+-------------+-----------+ | 1 | m1.tiny | 512 | 1 | 0 | | 1 | 1.0 | True | | 2 | m1.small | 2048 | 20 | 0 | | 1 | 1.0 | True | | 3 | m1.medium | 4096 | 40 | 0 | | 2 | 1.0 | True | | 4 | m1.large | 8192 | 80 | 0 | | 4 | 1.0 | True | | 5 | m1.xlarge | 16384 | 160 | 0 | | 8 | 1.0 | True | +----+-----------+-----------+------+-----------+------+-------+-------------+-----------+
List available images.
# nova image-list +--------------------------------------+--------------------------------------+--------+--------+ | ID | Name | Status | Server | +--------------------------------------+--------------------------------------+--------+--------+ | a1533d87-d6fa-4d9d-bf85-6b2ab8400712 | Fedora-Cloud-Base-22-20150521.x86_64 | ACTIVE | | +--------------------------------------+--------------------------------------+--------+--------+
List available networks. Our instance will use int-net (Internal network), while creating the instance we must specify network using the ID instead of name.
# neutron net-list +--------------------------------------+---------+-------------------------------------------------------+ | id | name | subnets | +--------------------------------------+---------+-------------------------------------------------------+ | 187a7b6c-7d14-4d8f-8673-57fa9bab1bba | int-net | 7f75b54f-7b87-42e4-a7e1-f452c8adcb3a 192.168.100.0/24 | | db407537-7951-411c-ab8e-ef59d204f110 | ext-net | a517e200-38eb-4b4b-b82f-d486e07756ca 192.168.0.0/24 | +--------------------------------------+---------+-------------------------------------------------------+
List available security groups.
# nova secgroup-list +--------------------------------------+---------+------------------------+ | Id | Name | Description | +--------------------------------------+---------+------------------------+ | c88f4002-611e-41dd-af7c-2f7c348dea27 | default | Default security group | +--------------------------------------+---------+------------------------+
Default security group implements a firewall that blocks remote access to instance, to allow remote access to instance, we need to configure remote access.
The following commands adds rule to default security group, to allow ping and SSH access.
# nova secgroup-add-rule default icmp -1 -1 0.0.0.0/0 +-------------+-----------+---------+-----------+--------------+ | IP Protocol | From Port | To Port | IP Range | Source Group | +-------------+-----------+---------+-----------+--------------+ | icmp | -1 | -1 | 0.0.0.0/0 | | +-------------+-----------+---------+-----------+--------------+ # nova secgroup-add-rule default tcp 22 22 0.0.0.0/0 +-------------+-----------+---------+-----------+--------------+ | IP Protocol | From Port | To Port | IP Range | Source Group | +-------------+-----------+---------+-----------+--------------+ | tcp | 22 | 22 | 0.0.0.0/0 | | +-------------+-----------+---------+-----------+--------------+
Launch the first instance using the below command, load a variable for network ID.
# INT_NET_ID=`neutron net-list | grep int-net | awk '{ print $2 }'
Replace $INT_NET_ID with ID of internal network.
# nova boot --flavor m1.small --image Fedora-Cloud-Base-22-20150521.x86_64 --nic net-id=$INT_NET_ID --security-group default --key-name my-key MY-Fedora
+--------------------------------------+-----------------------------------------------------------------------------+
| Property | Value |
+--------------------------------------+-----------------------------------------------------------------------------+
| OS-DCF:diskConfig | MANUAL |
| OS-EXT-AZ:availability_zone | nova |
| OS-EXT-SRV-ATTR:host | - |
| OS-EXT-SRV-ATTR:hypervisor_hostname | - |
| OS-EXT-SRV-ATTR:instance_name | instance-0000000b |
| OS-EXT-STS:power_state | 0 |
| OS-EXT-STS:task_state | scheduling |
| OS-EXT-STS:vm_state | building |
| OS-SRV-USG:launched_at | - |
| OS-SRV-USG:terminated_at | - |
| accessIPv4 | |
| accessIPv6 | |
| adminPass | 7PGDvZaxnxR5 |
| config_drive | |
| created | 2015-07-02T17:45:15Z |
| flavor | m1.small (2) |
| hostId | |
| id | 7432030a-3cbe-49c6-956a-3e725e22196d |
| image | Fedora-Cloud-Base-22-20150521.x86_64 (a1533d87-d6fa-4d9d-bf85-6b2ab8400712) |
| key_name | my-key |
| metadata | {} |
| name | MY-Fedora |
| os-extended-volumes:volumes_attached | [] |
| progress | 0 |
| security_groups | default |
| status | BUILD |
| tenant_id | 9b05e6bffdb94c8081d665561d05e31e |
| updated | 2015-07-02T17:45:15Z |
| user_id | 127a9a6b822a4e3eba69fa54128873cd |
+--------------------------------------+-----------------------------------------------------------------------------+
We will check the status of our instance.
# nova list +--------------------------------------+-----------+--------+------------+-------------+-----------------------+ | ID | Name | Status | Task State | Power State | Networks | +--------------------------------------+-----------+--------+------------+-------------+-----------------------+ | 7432030a-3cbe-49c6-956a-3e725e22196d | MY-Fedora | ACTIVE | - | Running | int-net=192.168.100.8 | +--------------------------------------+-----------+--------+------------+-------------+-----------------------+
Create a floating IP address on the external network (ext-net).
# neutron floatingip-create ext-net Created a new floatingip: +---------------------+--------------------------------------+ | Field | Value | +---------------------+--------------------------------------+ | fixed_ip_address | | | floating_ip_address | 192.168.0.201 | | floating_network_id | db407537-7951-411c-ab8e-ef59d204f110 | | id | 0be060c7-d84f-4691-8205-34ad9bb6a296 | | port_id | | | router_id | | | status | DOWN | | tenant_id | 9b05e6bffdb94c8081d665561d05e31e | +---------------------+--------------------------------------+
We will associate the floating IP address to our instance (MY-Fedora).
# nova floating-ip-associate MY-Fedora 192.168.0.201
Check the status of the floating IP address.
# nova list +--------------------------------------+-----------+--------+------------+-------------+--------------------------------------+ | ID | Name | Status | Task State | Power State | Networks | +--------------------------------------+-----------+--------+------------+-------------+--------------------------------------+ | 7432030a-3cbe-49c6-956a-3e725e22196d | MY-Fedora | ACTIVE | - | Running | int-net=192.168.100.8, 192.168.0.201 | +--------------------------------------+-----------+--------+------------+-------------+--------------------------------------+
Verify the network connectivity using ping from any host on the external physical network.
C:\>ping 192.168.0.201 Pinging 192.168.0.201 with 32 bytes of data: Reply from 192.168.0.201: bytes=32 time=1ms TTL=63 Reply from 192.168.0.201: bytes=32 time=2ms TTL=63 Reply from 192.168.0.201: bytes=32 time=1ms TTL=63 Reply from 192.168.0.201: bytes=32 time=1ms TTL=63 Ping statistics for 192.168.0.201: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 2ms, Average = 1ms
Once you get a ping response, wait atleast a minute, allow the instance to get fully booted; then try to SSH from controller or external system. Use the key pair for authentication.
# ssh -i mykey [email protected] The authenticity of host '192.168.0.201 (192.168.0.201)' can't be established. ECDSA key fingerprint is 0e:c2:58:9b:7f:28:10:a9:e1:cf:6d:00:51:6b:1f:f5. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '192.168.0.201' (ECDSA) to the list of known hosts. [fedora@my-fedora ~]$
Now you have successfully logged into fedora instance.