Hello,

    I'm trying to   fully automate my vHMC instances  with the "Activation Engine" setup, However  Im unclear on how to put it all together or how it works . Can someone show me an example or how to set it up  or what to put in the Disk space. 

• If you are using the Activation Engine, replace AEDISK with the name of Activation Engine virtual disk image. Otherwise, remove the disk element.

i assume  example:

   <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='none'/>
      <source file='DISK_PATH'/>    <---------- Location  of the  disk1.img
      <target dev='vda' bus='virtio'/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw'/>
      <source file='AEDISK'/>            <------- replace  "AEDISK"  with  what ?? 
      <target dev='vdb' bus='virtio'/>
    </disk>  

Im running it on  x86 KVM

Hi Marvin.,

The "DISK_PATH" is the location of the virtual machine image that will be included in the vHMC bundle. After extracting the bundle, the user can access disk1.img; Please provide the full qualified path to the file.

The AEDISK is the location of the activation engine iso file, which must be provided by the user in order for network and other configurations to be enabled during automatic deployment. The Readme.pdf packaged with tar explains how to create an activation engine. The user_data is the sample example file to generate the activation engine. 

Hello Santhosh ,

 Perfect! this is very clear now.   

thanks for the help 

Original Message:
Sent: Wed October 16, 2024 06:58 AM
From: Santhosh S Samaka
Subject: Activation Engine -- how to setup

Hi Marvin.,

The "DISK_PATH" is the location of the virtual machine image that will be included in the vHMC bundle. After extracting the bundle, the user can access disk1.img; Please provide the full qualified path to the file.

The AEDISK is the location of the activation engine iso file, which must be provided by the user in order for network and other configurations to be enabled during automatic deployment. The Readme.pdf packaged with tar explains how to create an activation engine. The user_data is the sample example file to generate the activation engine. 

Sample ex:

 <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='none'/>
      <source file='/home/user/extracted_tar/disk1.img'/>   
      <target dev='vda' bus='virtio'/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw'/>
      <source file='/home/user/extracted_tar/AEdrive.iso'/>       
      <target dev='vdb' bus='virtio'/>
    </disk>  

Regard.,

Samaka

------------------------------
Santhosh S Samaka
------------------------------

Hello again  Santhosh,

   Do you know what reason would the info in the "user_data" would not apply  it self ?  like example adding a pre fill out the IPV4 address or  skip the keyboard and or wizard ? for some reason i still have to do all that. i would like that to be all automated ..  

Original Message:
Sent: Wed October 16, 2024 06:58 AM
From: Santhosh S Samaka
Subject: Activation Engine -- how to setup

Hi Marvin.,

The "DISK_PATH" is the location of the virtual machine image that will be included in the vHMC bundle. After extracting the bundle, the user can access disk1.img; Please provide the full qualified path to the file.

The AEDISK is the location of the activation engine iso file, which must be provided by the user in order for network and other configurations to be enabled during automatic deployment. The Readme.pdf packaged with tar explains how to create an activation engine. The user_data is the sample example file to generate the activation engine. 

Sample ex:

 <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='none'/>
      <source file='/home/user/extracted_tar/disk1.img'/>   
      <target dev='vda' bus='virtio'/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw'/>
      <source file='/home/user/extracted_tar/AEdrive.iso'/>       
      <target dev='vdb' bus='virtio'/>
    </disk>  

Regard.,

Samaka

------------------------------
Santhosh S Samaka
------------------------------

Hi Marvin.,

The user_data is a sample example included in the bundle. This must be filled out by the administrator based on the environment where the automation is required for deployment. Ex: ip, subnet details, disk paths. All of these details will change depending on the environment. 

Regards.,

Samaka

Original Message:
Sent: Wed October 30, 2024 01:08 PM
From: Marvin Jones
Subject: Activation Engine -- how to setup

Hello again  Santhosh,

   Do you know what reason would the info in the "user_data" would not apply  it self ?  like example adding a pre fill out the IPV4 address or  skip the keyboard and or wizard ? for some reason i still have to do all that. i would like that to be all automated ..  

------------------------------
Marvin Jones
------------------------------


Original Message:
Sent: Wed October 16, 2024 06:58 AM
From: Santhosh S Samaka
Subject: Activation Engine -- how to setup

Hi Marvin.,

The "DISK_PATH" is the location of the virtual machine image that will be included in the vHMC bundle. After extracting the bundle, the user can access disk1.img; Please provide the full qualified path to the file.

The AEDISK is the location of the activation engine iso file, which must be provided by the user in order for network and other configurations to be enabled during automatic deployment. The Readme.pdf packaged with tar explains how to create an activation engine. The user_data is the sample example file to generate the activation engine. 

Sample ex:

 <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='none'/>
      <source file='/home/user/extracted_tar/disk1.img'/>   
      <target dev='vda' bus='virtio'/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw'/>
      <source file='/home/user/extracted_tar/AEdrive.iso'/>       
      <target dev='vdb' bus='virtio'/>
    </disk>  

Regard.,

Samaka

------------------------------
Santhosh S Samaka

Hi Santhosh,

      I have filled out all the details i need in the  "user_data" file  and updated the  XML file with the paths to the  disk1.img and  AEdrive.iso. However when I issues the command virsh start XML the settings in my user_data dose not get applied to my new HMC VM.    do you know what i might be missing here ?

Original Message:
Sent: Wed November 06, 2024 01:25 AM
From: Santhosh S Samaka
Subject: Activation Engine -- how to setup

Hi Marvin.,

The user_data is a sample example included in the bundle. This must be filled out by the administrator based on the environment where the automation is required for deployment. Ex: ip, subnet details, disk paths. All of these details will change depending on the environment. 

Regards.,

Samaka

------------------------------
Santhosh S Samaka
------------------------------


Original Message:
Sent: Wed October 30, 2024 01:08 PM
From: Marvin Jones
Subject: Activation Engine -- how to setup

Hello again  Santhosh,

   Do you know what reason would the info in the "user_data" would not apply  it self ?  like example adding a pre fill out the IPV4 address or  skip the keyboard and or wizard ? for some reason i still have to do all that. i would like that to be all automated ..  

------------------------------
Marvin Jones


Original Message:
Sent: Wed October 16, 2024 06:58 AM
From: Santhosh S Samaka
Subject: Activation Engine -- how to setup

Hi Marvin.,

The "DISK_PATH" is the location of the virtual machine image that will be included in the vHMC bundle. After extracting the bundle, the user can access disk1.img; Please provide the full qualified path to the file.

The AEDISK is the location of the activation engine iso file, which must be provided by the user in order for network and other configurations to be enabled during automatic deployment. The Readme.pdf packaged with tar explains how to create an activation engine. The user_data is the sample example file to generate the activation engine. 

Sample ex:

 <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='none'/>
      <source file='/home/user/extracted_tar/disk1.img'/>   
      <target dev='vda' bus='virtio'/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw'/>
      <source file='/home/user/extracted_tar/AEdrive.iso'/>       
      <target dev='vdb' bus='virtio'/>
    </disk>  

Regard.,

Samaka

------------------------------
Santhosh S Samaka