On Boarding OS Image

1. Login to the Marketplace using your administrator credentials.

   

2. Navigate to tab VM Image On-boarding > Images page.
3. Click Add Image and provide values as mentioned in the table below:

   

   Field	Value you must enter
   Name	This is the name of the image shown to user when they launch a VM. Usually this is the full name of an OS for e.g.: CentOS 6.5
   Code	Uniquely identifiable word used to identify this image within JSDN. You can type any word and does not have to match the code/id in the IaaS vendor platform. You will use this code in the next step.
   Platform	Select the OS category that matches the image you are creating.
   Version	Leave this field blank. This is not shown to the user that launches VMs.
   Description	You may type anything here. This is not shown to the user that launches VMs.
   Architecture	Select the appropriate value.
   Type	Select OS.
   Properties	Leave this field blank.

4. Click Save. Once you have your image ready, create Components, Resource Components and Provider Image.
5. To create Component, navigate to tab VM Image On-boarding > Components. Click Add Component and provide value as instructed below:

   Field	Value you must enter
   Name	Relevant component name.
   Code	Type a word that uniquely identifies this.
   Description	Leave Blank
   Type	Select Operating System.
   Platform	Select the same OS category that you selected for the image you create in the above step.
   Image	Select the image you create in the step above.
   Properties	Leave blank
   Secure Properties	Leave blank

6. Click Save.
7. Navigate to tab VM Image On-boarding > Resource Component. Click Add Resource Component and provide values as instructed below:

   Field	Value you must enter
   Resource Type	Select Operating System
   Resource Name	Select OS type
   Component Name	Select the component that you created in the step above.

8. Click Save.
9. Navigate to tab VM Image On-boarding > Provider Images. Click Add Provider Images and provide values as instructed below:
   Note: The "Add Provider Images" step must be repeated for every vendor that the OS option is going to be made available for. For example: if Cent OS 6.5 should be available for both AWS and Azure, you must acquire the appropriate image ID from the vendor for that OS version and repeat the "Add Provider Image" step for each vendor to allow JSDN to provision that image when the user selects it.

   Field	Value you must enter
   Service Provider	Select the appropriate IaaS provider or platform.
   Region	Select the region or select the provider region that you have created.
   JC Image	Select Image code created under images tab.
   Service Provider Image Code	This is the image ID or code in the IaaS provider platform for example in AWS this will be referred as AMI ID. The following Windows 2012 AWS images have been certified and could be used in JSDN. You may use them in case you wish to add a Windows 2012 image: Region AMI ID us-east-1 ami-507b0647 us-west-1 ami-69febd09 For AWS: Click hereto know how to obtain Image ID from AWS EC2 Console. For vCenter: To obtain the Image ID from vCenter, navigate to Home > Inventory > VMs and Templates. Select the appropriate datacenter from the left pane then, select the Virtual Machine tab from the right pane. Select the appropriate template and copy the template UUID, which will be your Image Code to be used in JSDN. Note: If you are using vCenter version 6.5 and above, click here to know how to obtain UUID.
   Type	Leave blank
   Size	Leave blank
   Properties	Leave blank
   Secure Properties	Choose from one of values below based on the vendor & OS based on the instructions below.

   Secure Properties for AWS:

   {"CREDENTIALS ":{"adminUserId":"<<USER_NAME>>","adminPassword":"<<PASSWORD>>"}}
   <<USER_NAME>>: this differs with the image. For example, for AWS Linux this is ‘ec2-user’. For AWS CentOS, it is ‘centos’.
   <<PASSWORD>>: If the image has a default password, then type the value here. If the system uses PEM file based SSH login, then leave this blank.
   Example value for an AWS-CentOS image that uses PEM file based authentication:
   {"CREDENTIALS ":{"adminUserId":"root", "adminPassword":""}}

   Secure Properties for Azure: Leave the field blank

   Secure Properties for Google Cloud: Leave the field blank

   Secure Properties for VMWare:

   {"CREDENTIALS ":{"adminUserId":"<< USER_NAME>>","adminPassword":"<<PASSWORD>>"}}
   <<USER_NAME>>: this differs with the image.
   <<PASSWORD>>: If the image has a default password, then type the value here.
   Example value for an Ubuntu image that uses PEM file based authentication:
   {"CREDENTIALS ":{"adminUserId":"root", "adminPassword":"UNIXroot"}}

   Secure Properties for OpenStack:

   {"CREDENTIALS ":{"adminUserId":"<<USER_NAME>>","adminPassword":"<<PASSWORD>>"}}
   <<USER_NAME>>: Image username used to launch the instance.
   <<PASSWORD>>: The default password for image.
   Example: {"CREDENTIALS ":{"adminUserId":"centos", "adminPassword":"UnixRoot"}}

   Secure Properties for IBM Bluemix (Softlayer)

   {"CREDENTIALS ":{"adminUserId":"<<USER_NAME>>","adminPassword":"<<PASSWORD>>"}}
   <<USER_NAME>>: Image username used to launch the instance.
   <<PASSWORD>>: The default password for image.

   Example: {"CREDENTIALS ":{"adminUserId":"centos", "adminPassword":"UnixRoot"}}

10. Click Save.
11. Repeat this step to configure the image for all regions that the image should be will be available in.
12. Upload SLAs for each image created in JSDN:

    Once images are created, upload an HTML file version of the vendor SLA for that image into the following location where JSDN is installed (ensure <<provider_code>> & <<component_code>> are replaced):

    /d01/jboss-as-7.1.1.Final/pp_config/jsdn/LicenseAgreement/<<provider_code>>/<<component code>>/sla.html

13. Here are the provider codes for each vendor:

Component code is the code added in Step 5.

Example path for the SLA html for a CentOS 6.5 image for AWS:

/d01/jboss-as-7.1.1.Final/pp_config/jsdn/LicenseAgreement/aws/CENTOS65/sla.html