About tm_mad_system


(alfiechan) #1

I am confuse about tm_mad_system=“ssh”. I read the official doc

when say “Combining the shared & SSH Transfer Modes”,

Blockquote
To select the (alternate) deployment mode, add the following attribute to the Virtual Machine template:
TM_MAD_SYSTEM=“ssh”

but there is no tm_mad_system option for vm template. and the image datastore does have one. so is it typo or am I missing something?


#2

I’d like to know that as well.


(Geclaff) #3

You can simply add this (Advanced mode):
DISK = [
DEV_PREFIX = “sd”,
DRIVER = “qcow2”,
IMAGE = “”,
IMAGE_UNAME = “”,
TM_MAD_SYSTEM = "SSH" ]


(alfiechan) #4

well, could you elaborate more detail about tm_mad_system options?


(Geclaff) #5

link to explain:
Combining the shared & SSH Transfer Modes


(alfiechan) #6

hmm,I just don’t understand when will utilize tm_mad_system, and when will utilize tm_mad.
the official doc does explanation well on this


(Juan Jose Montiel Cano) #7

I’ll try to explain this option.

If we have 3 datastores: ( 2 Systems datastores and 1 Image Datastore), with these configurations:

  • System datastore (ssh):

TM_MAD=“ssh”
LN_TARGET=“SYSTEM”
CLONE_TARGET=“SYSTEM”

  • System datastore ( shared ):

TM_MAD=“shared”
LN_TARGET=“NONE”
CLONE_TARGET=“SYSTEM”

  • Image Datastore (shared):

TM_MAD = “shared”
LN_TARGET = “NONE”
CLONE_TARGET = “SYSTEM”
TM_MAD_SYSTEM =" ssh"
LN_TARGET_SSH = “SYSTEM”
CLONE_TARGET_SSH =" SYSTEM"
DISK_TYPE_SSH = “FILE”

We can have an image saved into image datastore and use this image in a system datastore with the option TM_MAD_SYSTEM, only you need to define this option into your disk definition:

DISK = [
DEV_PREFIX = “sd”,
DRIVER = “shared”,
IMAGE = “”,
IMAGE_UNAME = “”,
TM_MAD_SYSTEM = "SSH " ]

From this time, OpenNebula will use the ssh optons saved into the image datastore to clone the images ( CLONE_TARGET_SSH and LN_TARGET_SSH) , also you need to define a DISK_TYPE_SSH to say to OpenNebula that the new image will be in this format.

All of these configuration need to be defined into oned.conf file.