Difference between revisions of "Deploy Procedure in Kadeploy 3 and OAR"
(Added reference to public images and edited the initial warning) |
|||
| (9 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| + | __NOTOC__ | ||
| + | |||
| + | <div class="thumbnail img-thumbnail">http://wiki.sc3.uis.edu.co/images/a/a8/Logo_sc33.png</div> | ||
| + | <p><div class="btn btn-primary"><i class="fa fa-long-arrow-left"></i> [[Kadeploy]]</div></p> | ||
| + | |||
| + | <div class="col-md-14"> | ||
| + | <div class="panel panel-darker-white-border"> | ||
| + | <div class="panel-heading"> | ||
| + | <h3 class="panel-title">Deploy Procedure in Kadeploy 3 and OAR</h3> | ||
| + | </div> | ||
| + | <div class="panel-body"> | ||
| + | <p> | ||
| + | |||
{{Note|<nowiki> | {{Note|<nowiki> | ||
There are two kinds of environments, private and public. Private environments are only usable for the user that created them. Public environments are available for all users but they can only be created by root. It's important to note that difference and check whether an enviroment should be public or private when creating new ones. Files for public environments should be created in public directories, even if those aren't available via permissions to all users. This is a style norm. It's also important to note that the user that performs the operations related to deployments affects the visibility of said deployments. At the end of this page this will be clarified. | There are two kinds of environments, private and public. Private environments are only usable for the user that created them. Public environments are available for all users but they can only be created by root. It's important to note that difference and check whether an enviroment should be public or private when creating new ones. Files for public environments should be created in public directories, even if those aren't available via permissions to all users. This is a style norm. It's also important to note that the user that performs the operations related to deployments affects the visibility of said deployments. At the end of this page this will be clarified. | ||
| Line 51: | Line 64: | ||
environment_kind : linux | environment_kind : linux | ||
</nowiki></pre>}} | </nowiki></pre>}} | ||
| − | |||
{{Note|<nowiki> | {{Note|<nowiki> | ||
It is important to check the kernel and initrd. Usually the same ones from the base image will work but if you upgrade the distro (or just the kernel) you have to be careful. | It is important to check the kernel and initrd. Usually the same ones from the base image will work but if you upgrade the distro (or just the kernel) you have to be careful. | ||
</nowiki>}} | </nowiki>}} | ||
| + | After the dsc file is ready you must run the following command to add the environment: | ||
| + | {{Command|<nowiki>kaenv3 -a ambiente.dsc</nowiki>}} | ||
| + | Remember checking the dsc file name and path. Now can check with: | ||
| + | {{Command|<nowiki>kaenv3 -l</nowiki>}} | ||
| + | And the new environment must appear in the list. It will be ready to use. | ||
| + | |||
| + | </p> | ||
| + | </div> | ||
| + | </div> | ||
| + | </div> | ||
Latest revision as of 21:01, 9 April 2015
Deploy Procedure in Kadeploy 3 and OAR
Deploying a base image
It's necessary to check the exact name of the environment to deploy. The command kaenv3 -l allows to see all the environments available for the current user.
In this example, the base image selected for deployment is 'squeeze-x32-base'.
Then you can access the deployed node via ssh:
Saving the modified image
In the machine execute these commands
After exiting the machine, on the front-end execute the following commands, where xx is a numeric string between 01 and 16 (nodes availables at the moment) and archivoImagen.tgz is the filename of the image file:
Create the following file (in this case ambiente.dsc) in an accessible location, taking into account the filename used and other similar parameters:
name : ambiente version : 1 author : usuario tarball : /home/usuario/archivoImagen.tgz|tgz kernel : /boot/vmlinuz-2.6.26-2-amd64 initrd : /boot/initrd.img-2.6.26-2-amd64 fdisktype : 83 filesystem : ext3 visibility : private demolishing_env : 0 environment_kind : linux
In this case the image is going to be private, which means it can only be accessed and deployed by the user that created it. If you want it to be public, root must do it, and must set the visibility parameter to public in the dsc file; also, it is advisable to copy the image file to /home/images, lest you want to set a complicated permissions scheme, then you have to change the path in the dsc file accordingly:
name : ambiente version : 1 author : usuario tarball : /home/images/archivoImagen.tgz|tgz kernel : /boot/vmlinuz-2.6.26-2-amd64 initrd : /boot/initrd.img-2.6.26-2-amd64 fdisktype : 83 filesystem : ext3 visibility : public demolishing_env : 0 environment_kind : linux
After the dsc file is ready you must run the following command to add the environment:
Remember checking the dsc file name and path. Now can check with:
And the new environment must appear in the list. It will be ready to use.
