Difference between revisions of "Deploy Procedure in Kadeploy 3 and OAR"
From Supercomputación y Cálculo Científico UIS
| Line 1: | Line 1: | ||
{{Note|<nowiki> | {{Note|<nowiki> | ||
| − | There are two kinds of environments, private and public. Private environments are only usable for the user | + | 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 important to note that the user that performs the operations related to deployments affects the | It's important to note that the user that performs the operations related to deployments affects the | ||
</nowiki>}} | </nowiki>}} | ||
Revision as of 20:57, 8 September 2014
NOTE:
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 important to note that the user that performs the operations related to deployments affects the
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.
kaenv3 -l
oarsub -I -t deploy
kadeploy3 -e squeeze-x32-base -f $OAR_NODEFILE
ssh root@nodo09
Saving the modified image
In the machine execute these commands
rm /etc/udev/rules.d/70-persistent-net.rules
mount -o bind / /mnt
After exiting the machine, on the front-end execute the following commands:
ssh root@guanexx "cd /mnt; tar --posix --numeric-owner --one-file-system -zcf - *" > archivoImagen.tgz
Create the following file in an accessible location:
File: ambiente.dsc
name : ambiente version : 1 author : usuario tarball : /home/usuario/ambiente.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
