for shortrun i am transfering manually .. but for long run if we have
the possibility to register kernel and initrd as well like we do in euca
, that will be great.. may be something to be added in wish list.
Zeeshan
On 02/09/2011 05:36 PM, Javier Fontan wrote:
That is possible but that will
That is possible but that will lead to huge amount of hacks as you
have to do this (at least):
* Parse the deployment.0 file or call back to opennebula to ask for
the source kernel/initrd files. TM knows nothing about kernel/initrd
* Rewrite the deployment.0 file to point to the newly copied
kerne
what about extending tm driver for ssh which copy the needed kernel
alongwith images to node ?
Zeeshan
On 02/09/2011 01:30 PM, Ruben Diez wrote:
Hi Zeeshan
You MUST put the kernels in all the nodes. You can use the
parallel-scp stuff or export them to all the nodes by NFS... It is
your dec
Hi Zeeshan
You MUST put the kernels in all the nodes. You can use the parallel-scp
stuff or export them to all the nodes by NFS... It is your decision...
The concrete mechanism is not the matter... The important stuff is to
make kernels accessible by all the physical nodes
Regards
Zeesh
Hi Ruben ,
thanks for answer ,
But if i have 10 kernels and 10 nodes , is there any easy way to
transfer kernels beside NFS ..
in Eucalyptus we can upload kernel and initrd alongwith image in
repository , any way to do the same in opennebula ..?
BR
Zeeshan
On 02/08/2011 06:31 PM, Ruben
You must copy the kernel on the correct path to every physical nodes
You can use a tool like parallel-scp (
http://code.google.com/p/parallel-ssh/ ) for do this... (perhaps your
distro have a package for parallel-ssh)
Other possibility is use full virtualization and not paravirtualization
Hi, When creating vm i am getting this
Tue Feb 8 11:43:07 2011 [TM][I]: tm_clone.sh:
frontnebula:/srv/cloud/one/var//images/8625d68b699fd30e64360471eb2c38fed47fcfb6
nebula1:/srv/cloud/one/var//0/images/disk.0
Tue Feb 8 11:43:07 2011 [TM][I]: tm_clone.sh: DST:
/srv/cloud/one/var//0/images/disk
