sig_cloud/diskimage-builder
11
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Update README regarding Debian and OpenSUSE support

Browse source 
Change-Id: Ib66525f25cb138358f854492fbd665814d060cda
This commit is contained in:
Tim Potter 2014-05-08 09:55:13 +10:00
parent 1b71aafc08
commit 096b6c8e04
1 changed files with 10 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
README.md
View file

@ -57,7 +57,7 @@ Installation
* Clone the repository locally, then add bin to your path. * Clone the repository locally, then add bin to your path.
* Make sure you have qemu-img (qemu-utils package on Ubuntu/Debian, * Make sure you have qemu-img (qemu-utils package on Ubuntu/Debian,
qemu on Fedora/RHEL) and kpartx installed. qemu on Fedora/RHEL/OpenSUSE) and kpartx installed.
Invocation Invocation
========== ==========
@ -105,7 +105,8 @@ offline mode.
Base images Base images
----------- -----------
These are cached by the standard elements - fedora, redhat, ubuntu. These are cached by the standard elements - fedora, redhat, ubuntu,
debian and opensuse.
source-repositories source-repositories
------------------- -------------------
@ -188,12 +189,13 @@ element adds support for mellanox infiniband hardware to both the deploy
ramdisk and the built images. ramdisk and the built images.
Images must specify a base distribution image element. Currently base Images must specify a base distribution image element. Currently base
distribution elements exist for fedora, rhel, and ubuntu. Other distribution elements exist for fedora, rhel, ubuntu, debian and
distributions may be added in future, the infrastructure deliberately opensuse. Other distributions may be added in future, the
makes few assumptions about the exact operating system in use. infrastructure deliberately makes few assumptions about the exact
The base image has opensshd running (a new key generated on first boot) operating system in use. The base image has opensshd running (a new
and accepts keys via the cloud metadata service, loading them into the key generated on first boot) and accepts keys via the cloud metadata
distribution specific default user account. service, loading them into the distribution specific default user
account.
The goal of a built image is to have any global configuration ready to roll, The goal of a built image is to have any global configuration ready to roll,
but nothing that ties it to a specific cloud instance: images should be able to but nothing that ties it to a specific cloud instance: images should be able to