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>
 +
It's important to note that the type of user affects the ...
 +
</nowiki>}}
 +
 
'''Deploying a base image'''
 
'''Deploying a base image'''
  
To be filled soon
+
It's necessary to check the exact name of the environment to deploy.  The command kaenv3 -l allows to see all the available
 +
{{Command|<nowiki>kaenv3 -l</nowiki>}}
 +
 
 +
{{Command|<nowiki>oarsub -I -t deploy</nowiki>}}
 +
 
 +
{{Command|<nowiki>kadeploy3 -e squeeze-x32-base -f $OAR_NODEFILE</nowiki>}}
 +
 
 +
{{Command|<nowiki>ssh root@nodo09</nowiki>}}
  
 
'''Saving the modified image'''
 
'''Saving the modified image'''

Revision as of 20:13, 8 September 2014

NOTE: It's important to note that the type of user 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 available

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