2d49eb8e4f
This imports the "launch instance" end user guide docs from
the openstack-manuals repo. As part of the docs migration
in Pike, these were forgotten. The copied contents come from
the stable/ocata branch of openstack-manuals, and therefore
likely need some updating, but that could be done in follow up
changes. This is an initial import to (1) publish the content
again somewhere and (2) fix broken links in the cinder docs
for booting from volume.
Conflicts:
doc/source/index.rst
NOTE(mriedem): The conflict is due to not having change
Ia57c93ef1e72ccf134ba6fc7fcb85ab228d68a47 in pike.
Change-Id: Ie039322660fd0e2e0403843448379b78114c425b
Partial-Bug: #1714017
Related-Bug: #1711267
(cherry picked from commit 4ed5e81ee0)
7.0 KiB
Launch an instance using ISO image
Boot an instance from an ISO image
OpenStack supports booting instances using ISO images. But before you
make such instances functional, use the openstack server create command with the following
parameters to boot an instance:
$ openstack server create --image ubuntu-14.04.2-server-amd64.iso \
--nic net-id = NETWORK_UUID \
--flavor 2 INSTANCE_NAME
+--------------------------------------+--------------------------------------------+
| Field | 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-00000004 |
| 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 | ZaiYeC8iucgU |
| config_drive | |
| created | 2015-06-01T16:34:50Z |
| flavor | m1.small (2) |
| hostId | |
| id | 1e1797f3-1662-49ff-ae8c-a77e82ee1571 |
| image | ubuntu-14.04.2-server-amd64.iso |
| key_name | - |
| metadata | {} |
| name | INSTANCE_NAME |
| os-extended-volumes:volumes_attached | [] |
| progress | 0 |
| security_groups | default |
| status | BUILD |
| tenant_id | ccef9e62b1e645df98728fb2b3076f27 |
| updated | 2014-05-09T16:34:51Z |
| user_id | fef060ae7bfd4024b3edb97dff59017a |
+--------------------------------------+--------------------------------------------+In this command, ubuntu-14.04.2-server-amd64.iso is the
ISO image, and INSTANCE_NAME is the name of the new
instance. NETWORK_UUID is a valid network id in your
system.
Create a bootable volume for the instance to reside on after shutdown.
Create the volume:
$ openstack volume create \ --size <SIZE_IN_GB> \ --bootable VOLUME_NAMEAttach the instance to the volume:
$ openstack server add volume INSTANCE_NAME \ VOLUME_NAME \ --device /dev/vda
Note
You need the Block Storage service to preserve the instance after
shutdown. The --block-device argument, used with the legacy
nova boot, will not
work with the OpenStack openstack server create command. Instead, the
openstack volume create and openstack server add volume commands create
persistent storage.
After the instance is successfully launched, connect to the instance using a remote console and follow the instructions to install the system as using ISO images on regular computers. When the installation is finished and system is rebooted, the instance asks you again to install the operating system, which means your instance is not usable. If you have problems with image creation, please check the Virtual Machine Image Guide for reference.
Make the instances booted from ISO image functional
Now complete the following steps to make your instances created using ISO image actually functional.
Delete the instance using the following command.
$ openstack server delete INSTANCE_NAMEAfter you delete the instance, the system you have just installed using your ISO image remains, because the parameter
shutdown=preservewas set, so run the following command.$ openstack volume list +--------------------------+-------------------------+-----------+------+-------------+ | ID | Display Name | Status | Size | Attached to | +--------------------------+-------------------------+-----------+------+-------------+ | 8edd7c97-1276-47a5-9563- |dc01d873-d0f1-40b6-bfcc- | available | 10 | | | 1025f4264e4f | 26a8d955a1d9-blank-vol | | | | +--------------------------+-------------------------+-----------+------+-------------+You get a list with all the volumes in your system. In this list, you can find the volume that is attached to your ISO created instance, with the false bootable property.
Upload the volume to glance.
$ openstack image create --volume SOURCE_VOLUME IMAGE_NAME $ openstack image list +-------------------+------------+--------+ | ID | Name | Status | +-------------------+------------+--------+ | 74303284-f802-... | IMAGE_NAME | active | +-------------------+------------+--------+The
SOURCE_VOLUMEis the UUID or a name of the volume that is attached to your ISO created instance, and theIMAGE_NAMEis the name that you give to your new image.After the image is successfully uploaded, you can use the new image to boot instances.
The instances launched using this image contain the system that you have just installed using the ISO image.