Background: Use this procedure to deploy a supervisory box in AWS.
With internal virtualization environment
Creating the Virtual Machine
Retrieve the master from the FTP site depending on the virtualization technology used:
FTP site : ftp://software.servicenav.io (contact support to get credentials)
Directory: VSM-VSB: Images Available for VMware and HyperV
Creating the Virtual Machine in its virtualization environment
Migrating your Virtual Machine to Amazon EC2 using AWS Connector for vCenter:
http://docs.aws.amazon.com/fr_fr/amp/latest/userguide/migrate-vms.html
Import your Virtual Machine using AWS Systems Manager for Microsoft SCVMM:
http://docs.aws.amazon.com/fr_fr/AWSEC2/latest/WindowsGuide/scvmm-import-vm.html
Without internal virtualization environment
Prerequisite
Retrieve the OVA image and vmdk available on our FTP site:
FTP site : ftp://software.servicenav.io (contact support to get credentials)
Directory: SNB-SNM - ServiceNav Box
Fil : take the last available OVF master
Import your Virtual Machine as an image:
You can import it to Amazon EC2. The import process is the same regardless of the origin of the virtual machine.
Uploading the image to Amazon S3
Upload your virtual machine image file to your Amazon S3 compartment using the upload tool of your choice. For more information about loading files via the S3 Console, see Loading items into Amazon S3. For more information about the Java Enhanced Uploader applet, see Using Enhanced Uploader.
After loading your virtual machine image file into Amazon S3, you can use AWS CLI to import image. The tools accept the Amazon S3 compartment and the file path or URL for a public Amazon S3 file. Private Amazon S3 files require a Signed GET URL.
Creating your VM from OVA or VMDK
The following examples use the AWS CLI command import-image to create import tasks.
Example 1: Importing an OVA
aws ec2 import-image --description "Windows 2008 OVA
" --license-type <"Value." "Value." "Span.
--disk-containers file://containers.json
Here is an example file containers.json
.
[
{
"Description": "Windows 2008 OVA
", "Format": "ova", "UserBucket": { "S3Bucket": "my-import-bucket
", "S3Key": "vms/my-windows-2008-vm.ova
" } } ]
Example 2: Importing multiple disks from vmdk
$
C:>
aws ec2 import-image --description "Windows 2008 VMDKs
" --license-type <"Value." "Value." "Span.
--disk-containers file://containers.json
Here is an example file containers.json
.
[
{
"Description": "First disk
", "Format": "vmdk
", "UserBucket": { "S3Bucket": "my-import-bucket
", "S3Key": "disks/my-windows-2008-vm-disk1.vmdk
" } }, { "Description": "
", "Format": "vmdk
", "UserBucket": { "S3Bucket": "my-import-bucket
", "S3Key": "disks/my-windows-2008-vm-disk2.vmdk
" } } ]
Checking the status of the import task
The command describe-import-image-tasks is used to display the status of an import task.
Status values include the following:
active
- The import task is in progress.deleting
- The import task is being cancelled.deleted
- The import task is cancelled.updating
- The import status is being updated.validating
- The imported image is being validated.validated
- The imported image has been validated.converting
- The imported image is converted into an AMI.completed
- The import task is complete and the AMI is ready for use.
aws ec2 describe-import-image-tasks --import-task-ids import-ami-abcd1234
You can also use the old command from the command line interface (CLI) EC2 ec2 describe-conversion-tasks to achieve the same goal:
Useful links:
http://docs.aws.amazon.com/vm-import/latest/userguide/vmimport-image-import.html#import-vm-image
Importing a VM as an Image Using VM Import/Export
Commissioning of a ServiceNav Box
Follow the following procedure from section 2 onwards:
SaaS mode: https://coservit.com/servicenav/fr/documentation/mise-en-service-dune-box-servicenav/
License Mode : https://servicenav.coservit.com/en/documentations/commissioning-of-a-servicenav-box-in-saas-mode/