CadolesKube
/
vms
7
0
Fork 0
Code Issues 2 Pull Requests 1 Projects Releases Wiki Activity

README: fix typo

This commit is contained in:
Laurent Gourvenec 2023-02-08 12:01:09 +01:00
parent 8ce318aa74
commit ecb857ff45
1 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
README.md
View File

@ -10,7 +10,7 @@ This is a simple wrapper to help you build and publish images with "packer" and
### The "publisher" tool called "tools/one-templates" ### The "publisher" tool called "tools/one-templates"
This is a simple script to create and manage OpenNebula "Templates", all kinds of templates : This is a simple script to create and manage OpenNebula "Templates", all kinds of templates:
* VMs * VMs
* Networks * Networks
* Images * Images
@ -23,13 +23,13 @@ With this tool you can publish all the images and the necessary templates to act
* Packer >= 1.6.0 * Packer >= 1.6.0
* virt-sparsify (optional) * virt-sparsify (optional)
* Ruby * Ruby
* These ruby gems : * These ruby gems:
* opennebula * opennebula
* opennebula-cli * opennebula-cli
* opennebula-oca * opennebula-oca
* webrick * webrick
* An OpenNebula server or cluster >= 5.6 (with OpenNebula Flow and OneGate enabled) * An OpenNebula server or cluster >= 5.6 (with OpenNebula Flow and OneGate enabled)
* An account with the proper ACL on the OpenNebula server/cluster to : * An account with the proper ACL on the OpenNebula server/cluster to:
* create/manage images * create/manage images
* create/manage vm templates * create/manage vm templates
* create/manage services templates * create/manage services templates
@ -39,13 +39,13 @@ With this tool you can publish all the images and the necessary templates to act
First you need to create the "publisher" "tools/one-templates" configuration. First you need to create the "publisher" "tools/one-templates" configuration.
This configuration is located in "./tools/.one-templates.conf". This configuration is located in "./tools/.one-templates.conf".
Note that you can use a diffrent configuration file setting the TEMPLATER_CONFIG environment file before starting the build script. Note that you can use a different configuration file setting the TEMPLATER_CONFIG environment file before starting the build script.
``` ```
$ cat ./tools/one-templates.conf $ cat ./tools/one-templates.conf
user: myOpenNebulaUser user: myOpenNebulaUser
token: myVerySecretOpenNebulaTemporaryToken token: myVerySecretOpenNebulaTemporaryToken
builder_addr: IP Address of the building machine (offen you own local IP address) builder_addr: IP Address of the building machine (often your own local IP address)
endpoint: http://myOpenNebulaServerAddress... endpoint: http://myOpenNebulaServerAddress...
flow_endpoint: http://myOpenNEbulaServerAddress/oneflow flow_endpoint: http://myOpenNEbulaServerAddress/oneflow
datastore_id: TheDataStoreIDForMyImages datastore_id: TheDataStoreIDForMyImages
@ -53,8 +53,8 @@ datastore_id: TheDataStoreIDForMyImages
When this configuration is done you can use the "build" tool. When this configuration is done you can use the "build" tool.
The recipes are organised by OS, version and flavor, one OS contains various versions and falvors. The recipes are organised by OS, version and flavor, one OS contains various versions and flavors.
You can list the availabled OS and versions whith this command : You can list the available OS and versions with this command:
``` ```
$ ./build list $ ./build list
@ -62,19 +62,19 @@ You can build :
* alpine : * alpine :
- 3.16 - 3.16
``` ```
To build all the flavors of a version you can run this command : To build all the flavors of a version you can run this command:
``` ```
$ ./build start alpine 3.16 $ ./build start alpine 3.16
``` ```
To build only one flavor for on version you can run this command : To build only one flavor for one version you can run this command:
``` ```
$ ./build run alpine 3.16 k3s $ ./build run alpine 3.16 k3s
``` ```
`!!! Make shure the "base" falvor is build before trying to build another falvor. !!!` `!!! Make sure the "base" flavor is build before trying to build another flavor. !!!`
``` ```
$ ./build run alpine 3.16 base $ ./build run alpine 3.16 base