mirror of
https://github.com/linuxkit/linuxkit.git
synced 2025-09-29 01:56:52 +00:00
f65a4e803d
This commit updates the support for pushing images into OpenStack by inheriting environment variables for endpoint and authentication information, when available. It also attempts to make the `openstack run` support more consistent with other providers (specifically GCP and AWS), i.e just take the name of the image as the argument and launch an instance using that. Finally, it also updates the relevant documentation for OpenStack support. Signed-off-by: Nick Jones <nick@dischord.org>
84 lines
2.7 KiB
Markdown
84 lines
2.7 KiB
Markdown
# LinuxKit with OpenStack
|
|
|
|
LinuxKit interacts with OpenStack through its native APIs and requires access and provides basic support for pushing images and launching virtual instances.
|
|
|
|
Supported (tested) versions of the relevant OpenStack APIs are:
|
|
|
|
- Keystone v3
|
|
- Glance v2
|
|
- Nova v2
|
|
- Neutron v2
|
|
|
|
## Authentication
|
|
|
|
LinuxKit's support for OpenStack handles two ways of providing the endpoint and authentication details. You can either set the standard set of environment variables and the commands detailed below will inherit those, or you can explicitly provide them on the command-line as options to `push` and `run`. The examples below use the latter, but if you prefer the former then you'll need to set the following:
|
|
|
|
```shell
|
|
OS_USERNAME="admin"
|
|
OS_PASSWORD="xxx"
|
|
OS_TENANT_NAME="linuxkit"
|
|
OS_AUTH_URL="https://keystone.com:5000/v3"
|
|
OS_USER_DOMAIN_NAME=default
|
|
```
|
|
|
|
## Push
|
|
|
|
### Image types supported:
|
|
- **ami** (Amazon Machine image)
|
|
- **vhd** (Hyper-V)
|
|
- **vhdx** (Hyper-V)
|
|
- **vmdk** (VMware Disk)
|
|
- **raw** (Raw disk image)
|
|
- **qcow2** (Qemu disk image)
|
|
- **iso** (ISO9660 compatible CD-ROM image)
|
|
|
|
A compatible image needs to have the correct extension (must match one from above) in order to be supported by the `linuxkit push openstack` command. The `openstack` backend will use the filename extension to determine the image type, and use the filename as a label for the new image.
|
|
|
|
Images generated with Moby can be uploaded into OpenStack's image service with `linuxkit push openstack`, plus a few options. For example:
|
|
|
|
```shell
|
|
./linuxkit push openstack \
|
|
-authurl=https://keystone.example.com:5000/v3 \
|
|
-username=admin \
|
|
-password=XXXXXXXXXXX \
|
|
-project=linuxkit \
|
|
-img-name=LinuxKitTest
|
|
./linuxkit.iso
|
|
```
|
|
|
|
If successful, this will return the image's UUID. If you've set your environment variables up as described above, this command can then be simplified:
|
|
|
|
```shell
|
|
./linuxkit push openstack \
|
|
-img-name "LinuxKitTest" \
|
|
~/Desktop/linuxkitmage.qcow2
|
|
```
|
|
|
|
## Run
|
|
|
|
Virtual machines can be launched using `linuxkit run openstack`. As an example:
|
|
|
|
```shell
|
|
linuxkit run openstack \
|
|
-authurl https://keystone.example.com:5000/v3 \
|
|
-username=admin \
|
|
-password=xxx \
|
|
-project=linuxkit \
|
|
-network c5d02c5f-c625-4539-8aed-1dab3aa85a0a \
|
|
LinuxKitTest
|
|
```
|
|
|
|
This will create a new instance with the same name as the image, and if successful will return the newly-created instance's UUID. You can then check the boot logs as follows, e.g:
|
|
|
|
```shell
|
|
$ openstack console log show 7cdd4d53-78b3-47c7-9a77-ba8a3f60548d
|
|
[..]
|
|
linuxkit-fa163ec840c9 login: root (automatic login)
|
|
|
|
Welcome to LinuxKit!
|
|
|
|
NOTE: This system is namespaced.
|
|
The namespace you are currently in may not be the root.
|
|
[..]
|
|
```
|