Centralized Cloud Management

The Appliance provides users with a centralized console to manage most commonly used IaaS Resources: VMs, Block Volumes & Network Interfaces.

Launching & Managing IaaS Resources

The appliance provides a Catalog which has stack templates that you can quickly launch into all various IaaS vendor platforms.

It also provides you with a Dashboard that lets you to view and monitor your real-time IaaS services usage and usage trends.

You can use the Resources option to manage all your IaaS resources. The AppStacks page gives you visibility into your application stacks, the Instances page lists all instances available to you and allows you to manage, launch, stop, terminate, reboot, attach volumes and administer all activities related to instances, the Image page displays all the images created and available and allows you to create instances from the image. The Volume Snapshot page lists the available volume snapshots, the Instance Monitoring page tracks the health of your IaaS resources, the Security Groups page that enables you to implement network level security rules on specified instances, and a SSO Console that gives you quick access to vendors’ cloud service management portals (control panels). Use the Import IaaS Resources page to bring in the IaaS resources purchased outside the store and manage them just like other resources.

Important Note when launching stacks into Google Cloud & IBM Bluemix (SoftLayer): Please note that Security Groups are not yet supported in the appliance and therefore you must remove them before you launch stack templates into Google Cloud and IBM Bluemix (SoftLayer).
Note: All stack launch requests require administrator approval from the Manage > Requests page.
Note: All the pre-defined roles will have complete access to IaaS services and the IaaS Console. In addition to the pre-defines roles, if you want to provide IaaS related access to any custom created role, you need to mark and enable all infrastructure management privileges using the Roles and Privileges feature.

Launch AppStack

You can order stand-alone virtual machines (instances) and application stacks from the store catalog. An application stack refers to a set of servers and user defined applications whose relationships and configurations can be managed collectively.

Pre-Conditions:
You must link your cloud account details to your organization.
Virtual Private Cloud should be configured for your account.

To place an order for an application stack or an instance, do the following:

  1. Navigate to the Catalog page.
  2. Click on the view offers for Stack service which you want to order. Click Launch.
  3. The Stack Interface page is displayed. It lists the associated instances and applications. Review the details and price. You can view the estimated cost per month of the stack.
  4. Enter the Stack Name and Description in the respective fields. If the Stack Name and Description are pre-populated, you can edit these fields according to your requirement. The Stack Details section displays pre-provided details such as the stack name, description and associated tags. The tags displayed are applicable to the entire stack.
  5. Type the Budget Code in the Budget Code field. If you do not know the budget code, click the Lookup link next to the Budget field and then select a budget code. This is applicable only while configuring Enterprise Store. Click here to know how to upload Budget Code.
  6. The Resources section displays the instance level details. It displays vendors, versions of the applications, operating system, flavor/instance type, region so that you can select the suitable option that meets your requirement. The Vendor section displays the vendors who support the selected stack. Review the details, and then select a suitable vendor from the list.

  7. Select the region from the Region drop-down list. Select the memory Size and Operating System. You also need to decide whether you need the monitoring agent to be installed in the system. Select Yes from the drop-down list if you want the instance to be monitored. Select No otherwise. Select the Instance Type from the instance type drop-down list. Select the Network from the network drop-down list.
  8. Select the Subnet from the subnet drop-down list.
    Note: If you are configuring for Private Cloud, you must obtain Public IP (Floating IP).
    Note: The selection parameters in the Resource section vary based on the supported vendor.
  9. The Security Groups section displays the security groups and associated port and rule. You can edit the existing security group rules, port range and IP address. You can also create a security group by clicking the Create Security Group link. In the Security Group window, provide the security rules and port range. Refer to Security Group section for more information.
  10. View the sequence in which each instance is to be launched in the Orchestration Sequence section.
  11. Click Launch.
    Note: Some of the applications in the stack might require additional user level information. Enter the required values in the appropriate fields.
    Note: While Launching an AppStack, please ensure that the Instance Name is unique for easy identification and based on the provider specific naming conventions. This field is case sensitive. Recommended that the length should be at least 2 chars less than the provider specified length (Example: VM length in AWS & OpenStack- upto 253 chars; Azure-upto 13 chars; IBM & Google- upto 61 chars). It is likely that provisioning of VMs may fail if the VM name does not meet the provider criteria. Azure: Instance name cannot be more than 13 characters long, be entirely numeric or with special characters and no space is allowed. Google: The first character must be a lowercase letter, and all following characters must be a dash, lowercase letter, or digit, except the last character, which cannot be a dash. IBM: The hostname and domain (VM Name) must be alphanumeric strings between 1-63 characters in length that may be separated by periods '.'. The only other allowable special character is the dash '-'. Check IBM portal for further details.
  12. The Service Level Agreement page is displayed. Click Agree to agree the conditions.

An order for the instance/stack is placed with the store. A message indicating that the order needs to be approved is displayed. Refer to the below screen shot.

To approve the same, navigate to Manage > Requests page and select the order. The order that you have created will be in Approval Pending state.

Click the View link from the Actions column. The system will redirect you to View Request Details page.

On the View Request Details page, click Approve. The Request Receipt is displayed.

Now, navigate back to Manage > Request page. You will find the order is in "In-Progress", once the stack is in running status then the order will be Fulfilled.

Now, navigate back to Manage > Instances page. You will find the instance is in Running status.

An e-mail will be sent to you with the stack provisioning status. Once the stack is successfully provisioned, you can start using your stack.

Computing and Application Stack Service

The store offers various computing services and application stacks from the top cloud infrastructure vendors. You can review the details of these services on the catalog and take an informed decision about which IaaS vendor and service is best suited for your requirements.

The pricing of IaaS services is entirely based on the usage. You need to pay only for the resources you consume. The store offers various standard instances and stacks. Each instance/stack has different hourly pricing for their utilization levels. The pricing is the cost of running a specified machine image and operating system with the selected resource configuration as a service. You can view the estimated price per hour for an instance and the estimated monthly bill which is based on 100% utilization for 30 days. Review the price before purchasing the service.
Note: The billing amount for IaaS services in the invoice might slightly vary from the estimated price on the Catalog page.
Instance types constitute varying combinations of CPU, memory, storage, and networking capacity and allow you to choose the right combination of resources. You can select the region where you want to setup your server, select a pre-configured machine image to setup your server, an operating system and the physical resource combination. Each instance type includes one or more instance sizes, allowing you to select the right size to meet your target workload requirements. The store provides pre-built images. Select a suitable image from the available images list. An image is a collection of files for a specific operating system (OS) that helps to create a server. Select the Flavor/Size Reference refers to the resource configuration for a server. Each flavor is a unique combination of disk space, memory capacity, vCPUs, and network bandwidth. It refers to the allocation of physical resources.
Note: The fields you need to select vary based on vendors. Some services might require you to select the required hard disk and CPU separately from the respective drop-down list. Please select the options as available and as per the requirement.
The Estimated Price field displays the estimated monthly price for the 100% utilization of resources for a month for the selected instance/stack. Review the price details.
Note: An existing security group automatically gets associated with the instance. If you want to change and want to define a new one. Click the Edit link.
  • If you want to create a new security group, click the Create New Security Group link. The newly created security group is automatically associated to the instance. Refer to Security Groups Concepts Overview for more information on creating a new security group and editing an existing security group and associating the same to an instance. You can implement network rules on an ordered instance to ensure security.

Security Groups

The concept of security group is to define a set of access permissions on an instance. Use the editable Tags drop-down list to select an existing Key/Value. Tags are just labels which you can use classify the instances you use. A tag consists of a key/value pair. You can add up to 10 unique tags to each instance. Tags enable you to manage the infrastructure services in a better way. For example, if you want to assign an instance to the Recruitment team in the HR department, you can create a tag as Recruitment with value HR. A tag consists of a key and value. You can add up to 10 unique keys for each instance. Either selects an existing Tag and Value from the drop-down list or Type a Tag and Value of your choice. The access rules define source based access based on the IP addresses and sub net. You can also specify the protocol and port range (or ICMP type and code). Across TCP & UDP, the protocol and range are specified. It does not allow traffic from any other IP addresses. These rules determine which network traffic should be delivered to the selected instance. You can view and modify the rules for a security group any time. If you do not associate a security group to the instance, the default security group will be automatically associated.
Note: Some services do not require security group association. The security group field will not be available for such services.

Manage AppStack

The AppStacks page enables you to manage all the stacks ordered by your organization. It lists all the stacks available to you, their status and the tags associated with them. It also displays the total number of application stacks and the percentage of the stacks which are in various status. You can search for a specific application stack by stack name or associated tag.

Once the application stack is provisioned, it will be in the running status. You can view the application stack details. Once you finish using the stack, you can terminate the stack. You can manage the instances within the stack as normal instances using the Instances tab.

Fields Description
Template Name Displays the template name
Stack Name Displays the name of the application stack.
Status Displays the status of the application stack.
Tags

Displays the tags which are associated with the application stack. You can define the tags for instance while placing order for the stack.

Some instances come with default tags. You can have a maximum of 10 tags for each instance.

Viewing Application Stack Details

To view the details for a particular instance, do the following:

  1. Navigate to Resources> AppStacks page. The AppStacks page is displayed.
  2. On the AppStacks page, click the View Details link from the Actions column next to the application stack which you want to view the details. The Application Stack page is displayed.

The Application Stack is displayed with all the applications and instances that are included in the application stack and their relationships with each other. The right pane of the page displays the status of the stack, the available actions. It also displays the resource information of each instance. The resources section displays the available details of the instances such as vendor, region, availability zone, size, Network ID, operating system and the associated security groups information. You can also view the port and the protocol associated with which the communication is established between instances.

You can also view the estimated cost for the selected stack at the top of the page. You can view instance level cost at each instance level

Resources and Details Panel

The fields available are the following:

  • Stack Template Details:
    • Stack template name and description: Displays the application stack name. You can edit the name if required. The stack template name should be unique.
    • Description: Displays the description for the instance. You can edit the description if required.
    • Tags: Tags are just labels which you can use to classify the stack you use. A tag consists of a key/value pair. You can add up to 10 unique tags to each Application Stack. Click Add New to add a new tag. The tags you define here are applicable to the Stack as a whole.
  • Resources: Select each resource from the stack to view the properties. Displays the properties for each instance that you have selected.
    • Instance Name: Displays name for the instance.
    • Instance Details: Displays the selected vendor, deployed region, Network ID, operating system and the associated security groups information.
    • Security Groups: If the security group connection between two instances is established, select the receiver instance to see the rules of the associated security group. The rule and the port values will be displayed for the receiver instance.
    • Scripts: This option is available only if you have selected scripts to install external applications. It displays the parameters related to the selected scripts.
  • Orchestration Sequence: An orchestration sequence defines the launch sequence in which the instances will be initiated. It is provided while creating a stack. It cannot be edited.
Terminating an Application Stack

To terminate an application stack, do the following:

  1. On the Resourcesmenu, click AppStacks. The AppStacks page is displayed.
  2. On the AppStacks page, click the Terminate link from the Actions column for the stack which you want to terminate. The Terminate window is displayed.
  3. In the Terminate window, click Terminate. The application stack will be terminated.

Cloud Migration - Bulk Upload

The Cloud Migration in JSDN helps you to get an insight of your private cloud usage and cost, side by side with your public cloud usage and cost. The Migration dashboard enables you to quickly track and analyze your Data Center migration status along with the resource utilization.

To compare the usage details post migration, upload a cloud migration template in the JSDN platform. In the template provide your virtual/physical machines details (such as Vendor Name, Region, Data Center, and others) and upload it. You can add multiple VMs details (if you have) in the template. Once the file is successfully uploaded, you can see the details in your Migration Dashboard page. To view your Migration Dashboard page, navigate to Dashboard > IaaS Dashboard and select Cloud Migration. For more information refer to Cloud Migration.

Download/Upload Template

To upload a cloud migration template, do the following:

  1. On the My Companymenu, click Bulk Upload. The Bulk Upload page is displayed.
  2. On the Bulk Upload page, select the Cloud Migration from the Template Type drop-down list.
  3. Click Download. The Cloud Migration template will be downloaded into your local machine.
  4. The downloaded template will be Comma Separated Values (CSV) file format. You will be able to edit this file using Microsoft Excel. You will need to fill in the VM details.
  5. Click Upload Template. A Upload Template pop-up window is displayed.
  6. Select the Template Type as Cloud Migration from the drop-down list and click Browse and select the file.
  7. Click Upload.
  8. Once you click Upload, you can see the upload status. The upload status changes from In-Progress to Successful. If there are any errors in the file, the system will display an error message.

View Data Load Details

Once the file is uploaded successfully, you can view the details in Data Load Report. To view the data load report, do the following:

  1. On the My Companymenu, click Bulk Upload. The Bulk Upload page is displayed.
  2. On the Bulk Upload page, click the View Details link from the Actions column of the respective successfully uploaded file.
  3. The Data Load Report pop-up window is displayed with the details. If the status is Successful/Partially Successful, it displays the percentage of completion, total number of records it is uploaded, number of records successfully uploaded and number of records failed.
    Note: You cannot view the details, if the status of the files in Failed state.

Delete File

Once the file is uploaded successfully or partially successful or even failed, you can delete file. To view the data load report, do the following:

  1. On the My Companymenu, click Bulk Upload. The Bulk Upload page is displayed.
  2. On the Bulk Upload page, click the Delete link from the Actions column of the respective uploaded file.
  3. A confirmation message is displayed. Click Ok to confirm.

Manage Instances

This section explains you about Life Cycle Management of an Instance. How you can launch your instance (SSH - secure shell), stop, terminate and reboot your instances using this tab. It displays the list of instances ordered for your organization, their status, and the tags associated with the instances. It also displays the number of instances which are running, stopped, terminated, and other status. You can search for instances based on the instance name.

Use the Instances option to manage your instances. You can launch your instance (SSH - secure shell), stop, terminate and reboot your instances using this tab. It displays the list of instances ordered for your organization, their status, and the tags associated with the instances. It also displays the number of instances which are running, stopped, terminated, and other status. You can search for instances based on the instance name.

The following table displays the options available on the Instances page:

Fields Descriptions
Instance Name Displays the instance name. You can view the Instance details, launch SSH and manage the instance (stop, terminate, reboot, attach new volume, attach existing volume, create VM image, resize image are the available actions). Click the link next to the instance name to do the required action.
Provider Displays the service provider name and logo.
Region Displays the region where the instance is located.
AppStack Displays name of the AppStack to which the instance is associated.
Attach Volume(s) Displays the volumes that are attached to the instance.
Imported Displays whether the resources are imported or not.
Status Displays the status of the instance. It displays whether the instance is initializing, running, stopped or terminated. The other status available are creating customer account, creating instance, script execution-in progress error, starting, stopping and terminating.
Actions A number of actions that you can perform.
Tags Displays the tags associated with the instance. You can add up to 10 tags for an instance. You can create a tag using the Customize Instance page while buying the service or using the Instance Details > Tag tab.

The following are the actions available for the IaaS services from various vendors:

Actions AWS Azure Public Azure Stack OpenStack Private Cloud Amazon EC2 VMWare Microsoft Azure IBM BlueMix Google Cloud
Windows Linux Windows Linux Windows Linux Windows Linux
Launch SSH Yes Yes Yes Yes Yes No No No Yes No Yes No Yes
Start Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Stop Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Terminate Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Reboot Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Attach New Volume Yes Yes Yes Yes Yes No No Yes Yes Yes Yes Yes Yes
Attach Existing Volume Yes NA NA Yes Yes No No No No Yes Yes Yes Yes
Create Image Yes No No Yes Yes No No No No No No No No
Resize Yes Yes Yes Yes Yes No No Yes Yes Yes Yes Yes Yes
Instance Credentials Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Enable/Disable Monitoring Yes Yes Yes Yes Yes No No Yes Yes Yes Yes Yes Yes

Instance LifeCycle

Search for Specific Instances

You can search for specific instances using the Search option. To search for instance, do the following:

  1. On the Resourcesmenu, click Instances. The Instances page is displayed.
  2. Type the search text in the Search Here field.
  3. Click Go. The search results will be displayed.
View Instance Details

To view details of an existing instance, do the following:

  1. On the Resourcesmenu, click Instances. The Instances page is displayed.
  2. On the Instances page, click the View Details link from the Actions column.
  3. The View Instance Details page is displayed, where you can view the details about the selected instance.
Connecting to VM

Once the order status of the IaaS subscription is fulfilled, you can connect to your virtual machine (instance) from the Manage > Instances option. Launch SSH allows you to connect securely to your virtual machine and execute commands. It is the equivalent of opening a terminal window on the virtual server.

To connect to your instance, do the following:

  1. On the Resourcesmenu, click Instances. The Instances page is displayed.
  2. On the Instances page, click Launch SSH link from the Actions column next to the instance which you want to launch.

This takes you to the login prompt of the virtual machine (with a specific IP address created for you). Refer to Instance Credentials section to set your username and password. Now, you can start working at the command line of your virtual machine.

Starting and Stopping an Instance
You can start and stop an instance. When you stop an instance, the instance performs a normal shutdown and stops running.
Note: The start and stop actions may not be applicable to instances from all vendors.
Note: While starting and stopping an instance, the instance status gets change. It is recommended that you should wait for a while unless the process is completed.

Starting an Instance

To start an Instance, do the following:

  1. On the Resourcesmenu, click Instances. The Instances page is displayed.
  2. On the Instances page, click the Start link from the Actions column next to the instance which you want to start.

The starting process might take few minutes; in the mean time you will not be able to perform any actions.

Stopping an Instance

To stop an Instance, do the following:

  1. On the Resourcesmenu, click Instances. The Instances page is displayed.
  2. On the Instances page, click the Stop link from the Actions column next to the instance which you want to stop.

The stopping process might take few minutes; in the mean time you will not be able to perform any actions. The status of the machine changes to stopping and then stopped.

Terminating an Instance

Terminate an instance stops the instance and releases all resources allocated to that instance. Once you are sure that you do not need the instance any more, just terminate the instance. Once you terminate the instance, you cannot connect to the instance and also the store will stop charging for the instance.

To terminate an instance, do the following:

  1. On the Resourcesmenu, click Instances. The Instances page is displayed.
  2. On the Instances page, click the Terminate link from the Actions column next to the instance which you want to terminate.
  3. A confirmation message is displayed, whether you would like to terminate the instance or you would like to terminate the AppStack to which your instance is associated with.
  4. If you want to terminate the instance, click Terminate Instance Only.
  5. If you want to terminate the entire AppStack, click Terminate Entire AppStack.
The terminate process might take few minutes; in this time you will not be able to perform any actions.
Note: Once an instance is terminated, you can only view the details of the instance. You cannot perform any actions on the terminated instance.
Note: When you terminate an instance, all associated volumes will be detached and deleted.
Rebooting an Instance

Rebooting an instance refers to restarting an instance and reloading the operating system. To reboot an Instance, do the following:

  1. On the Resourcesmenu, click Instances. The Instances page is displayed.
  2. On the Instances page, click the Reboot link from the Actions column next to the instance which you want to reboot.

The rebooting process might take few minutes; in this time you will not be able to perform any actions.

You can Single Sign-On to the vendor console, just clicking on the Vendor Console icon.

Attach Volume

Attach a New Volume

You can attach a volume to an instance in the same location and from the same provider. The volume can only be attached to an instance which is in the running status. To attach a volume to an instance, do the following,

  1. On the Resourcesmenu, click Instances. The Instances page is displayed.
  2. On the Instances page, click the Attach New Volume link from the Actions column. The Add New Volume window is displayed.

  3. Type a suitable volume name in the Volume Name field. This helps you to identify the volume.
  4. Select the Volume type from the Type drop-down list. The volume types vary based on vendors. You can decide whether you need standard or high performance volume types.
  5. In the Size field, type the size of the volume in GB or TB.
  6. Click Done.

A new volume with the selected specifications is created and attached to the instance.

Attach an Existing Volume

To attach an existing volume, do the following:

  1. On the Resourcesmenu, click Instances. The Instances page is displayed.
  2. On the Instances page, click the Attach Existing Volume link from the Actions column. The Add Existing Volume window is displayed.

  3. All the volumes which are available in the free pool for your consumption will be displayed.
  4. Mark and select the volumes which you want to attach to your instance.
  5. Click Done. All the selected volumes will be attached to the instance.
    Note: Before you attach any volume, refer to the Live Dashboard to verify the volume status. Because, the volumes that are deleted at ISV level are still displayed.

Create Image from an Instance

An image in JSDN is the exact replica of the contents of the default hard drive of an instance. You can create an image from an instance. Once you create an image, you can launch any number of instances from the same image. It helps you retain the basic characteristics of the base image so that any changes you make to the base image does not affect other images. You can create VM images for instances which are in running or stopped status. However, it would be ideal that you create an image from a stopped instance to avoid data loss.

To create the image of an instance, do the following,

  1. On the Resources menu, click Instances. The Instances page is displayed.
  2. On the Instances page, click the Create VM Image link from the Actions column. The Create VM Image window is displayed.
  3. Type a suitable image name in the Image Name field. This helps you to identify the image. Provide a unique name for the image. This field is case sensitive and it accepts only a maximum of 50 ASCII characters.
  4. Type description for the image you are creating in the Description field. The image will be listed on the Image listing page. You can spin off an instance from the image you created.
  5. Click Create.

The instance status changes to “In Progress” and users will not be able to take any action on these instances.

Resize an Instance

You can dynamically resize your instances as your infrastructure requirements change. You can reduce the size of the instance if your resources are under utilized. Similarly, you can increase the size of your instance if your resources are over utilized. You can initiate resizing only for a running or stopped instance. To resize the instance, perform the following steps:

  1. On the Resourcesmenu, click Instances. The Instances page is displayed.
  2. On the Instances page, click the Resize link from the Actions column. The Resize Instance window is displayed. It displays the current configuration of the instance. The configuration selection fields vary based on the vendor. Review the current configuration details (Flavor/and RAM and CPU).

  3. Select the new configuration from the configuration drop-down list.
  4. Click Resize.
The instance resizing process will be initiated and once resizing is completed, you can view the new configuration details on the Instance Details page. The instance status changes to “resizing “and user will not be able to perform any action on the instance during this state.
Note: When you downsize, please make sure that the new configuration supports your applications.

Instance Credentials

The instance credentials option helps you to set your username and password, or upload your .PEM file to login to your Virtual Machine.

You can contact your administrator to get your username and password, and .PEM file. If you have your username and password and or .PEM file, do the following:

  1. Navigate to Resources > Instances page.
  2. On the Instances page, click the Instance Credentials link from the Action column of the respective Instance.
  3. Enable the Credential radio button and enter your Username and Password.

    OR

  4. Enable the Upload PEM File radio button and enter your username and browse and select your .PEM file.
  5. Click Submit.

Instance Monitoring

The Jamcracker Appliance, comes with an option where-in you can integrate any third-party monitoring tool, using which you can monitor your CPU Utilization, Network In, Network Out, Disk Read, Disk Write, Memory Utilization, and Volume Utilization of an instance. However, before you integrate your tool the monitoring server should be configured. Read more on how to configure the monitoring server and JSDN server.

The Enable or Disabled Monitoring option is configured while launching an AppStack on the Designer Console (under Resource Configuration). If you later wish to change the monitoring configuration, you can:

  1. Navigate to Resources > Instances page.
  2. On the Instances page, click the Enable/Disable Monitoring link from the Action column of the respective Instance.
  3. If you click the Enable/Disable Monitoring link, a confirmation message is displayed. Click Confirm to enable/disable the option. Once the monitoring option is enabled, monitor the instances from the Monitoring IaaS Resources page.
    Note: If you have configured any third party monitoring tool, then you must ensure your monitoring agent is up and running when the VM is in Active state.

By default, this option is disabled for any Jamcracker appliance package. To enable Monitoring server on your appliance package, you will have to place a request with our support team (jc.appliance@jamcracker.com). Our support team will share a Monitoring Image with you (offline). You have to create an Instance out of the Image and map both the instances. These instances should be launched in same VPC network. Since, both these instances needs to communicate via a Private IP.

To communicate via a Private IP, you must enable the in-bound rules in the security groups. Click here to know how to enable in-bound rules.

JSDN Server Manual Setup

Build Information

  • Linux

Integration Environment

Environment Version
Application Server JBoss 7.1.1.Final
Database Postgresssql (9.3.6)
Operating System CentOS Linux 7.2.1511 64 bit
Processor Intel(R) Xeon(R) CPU X5680 @ 3.6GHz or above
Web Server Apache2.4.7
CPUs 2
RAM 8 GB
Disk Space 50 GB or above

Terminologies used

  1. <<JBOSS_HOME>> = /d01/jboss-as-7.1.1.Final.
  2. <<JBOSS_SERVER_PRIVATE_IP>> = Appliance jboss server private IP.
  3. <<DB_SERVER_PRIVATE_IP>> = Appliance Jboss server private IP.
  4. <<monitoring_server_private_ip_address>> = Monitoring server private IP.

Prerequisite

A new monitoring server needs to be set up for monitoring to work in conjunction with JSDN appliance.
Note: Associate the public ip address to monitoring server.

Enable below security groups for JSDN server in AWS.

Custom TCP 111 <<MONITORING_SERVER_PRIVATE_IP>>/32
Custom TCP 2049 <<MONITORING_SERVER_PRIVATE_IP>>/32
  1. pp_config mount: steps to be performed in jsdn server as root user..
    • yum install -y nfs*
    • service nfs start
    • vi/etc/exports

      add below entry with proper values.

      /d01/jboss-as-7.1.1.Final/pp_config<<monitoring-server-private-ip>>(rw,sync,no_root_squash)

      For saving the file please follow below command

      <<JBOSS-Server-Private-IP>>:/d01/jboss-as-7.1.1.Final/pp_config/d01/jboss-as-7.1.1.Final/pp_config nfs defaults 0 0
    • Esc
    • :wq!

      Execute below commands:

      • exportfs –avr
      • systemctl enable nfs-server
  2. Stop the postgres service using below command using root user.( Root user : sudo su)
    • systemctl stop postgresql-9.5.service
  3. Add below property in pg_hba.conf file under IPV4 local connections section.
    • vi/var/lib/pgsql/9.5/data/pg_hba.conf

      search for keyword “IPv4 local connections” add below entry.

      host all all <<Monitoring_server_private_IP>>/32 trust

    • Esc
    • :wq!
  4. Once added the above entry start the postgres service using root user (sudo su).
    • systemctl start postgresql-9.5.service

      Please enable below security group rules for jsdn app server in AWS.
      HTTP 80 0.0.0.0/0
      HTTPS 443 0.0.0.0/0
      PostgreSQL 5432

      <<Monitoring_server_private_IP>>/32

      SSH 22

      0.0.0.0/0

      SMTP 25

      0.0.0.0/0

      Custom TCP 1099 <<Monitoring_server_private_IP>>/32
      Custom TCP 8080 <<Monitoring_server_private_IP>>/32

Perform the following steps to update server time zone, service IP address, apache server details:

  1. Do this steps if your jboss server time zone is other than IST.

    For checking time zone use below command:

    • date

    Please check the jboss server time zone(GMT/PST etc..) and update same time zone id in

    • vi ~jboss/pp_config /monitor/monitor.properties

    search for keyword “monitor.server.timezone”

    Ex:- Set this property to GMT, if monitor server timezone in GMT.

    monitor.server.timezone=GMT

    • Esc
    • :wq!

    Please add below property in “dynamicproperty.properties && monitor.properties”. If it is already there ignore.

    • vi ~jboss/pp_config/dynamicproperty.properties

    convert.nagios.server.time.to.gmt=false

    • Esc
    • :wq!
    • vi ~jboss/pp_config /monitor/monitor.properties

    convert.nagios.server.time.to.gmt=false

    • Esc
    • :wq!

  2. Update proper monitoring_server_ipaddress for below property in.
    • vi ~jboss/pp_config/environment.properties

    search for “monitoring” and add/update below entry.

    monitoring=http://<<monitoring_server_private_ip_address>>:8080/monitoring/

    • Esc
    • :wq!

  3. Please collect monitoring server ip’s in AWS:

    PUBLIC_IP_WHERE_MONITORING_INSTALLED

    PRIVATE_IP_WHERE_MONITORING_INSTALLED

  4. Update (if not found add) the below properties in.

    vi ~jboss/pp_config/monitor/monitor.properties and

    vi ~jboss/pp_config/dynamicproperty.properties
    • PRIVATE_IP_FOR_MONITOR_SERVER=<<PRIVATE_IP_WHERE_MONITORING_INSTALLED>>

    • PUBLIC_IP_FOR_MONITOR_SERVER=<<PUBLIC_IP_WHERE_MONITORING_INSTALLED>>

    • PUBLIC_IP_FOR_AGENT_SCRIPT_SERVER=35.169.90.20

    • PRIVATE_IP_FOR_AGENT_SCRIPT_SERVER=172.31.49.102

  5. Update the below property in environment properties file.
    • vi ~jboss/pp_config/environment.properties

    app_server_ips=<<JBOSS_SERVER_PRIVATE_IP>>

    • Esc
    • :wq!
      Note: Perform the below steps in jsdn server.
  6. Apache changes: Only monitoring related call will be re-directed to monitoring server.

    Edit /usr/local/apache2/conf/extra/httpd-vhosts.conf file and update the 'jcmonitoringcluster'

    proxy tag with monitoring_server_private_ip_address, as shown below in apache server

    • vi /usr/local/apache2/conf/extra/httpd-vhosts.conf

    <Proxy "balancer://jcmonitoringcluster">

    BalancerMember http://<<monitoring_server_private_ip_address>>:8080 route=jboss1

    ProxySet stickysession=JSESSIONID|jsessionid scolonpathdelim=On

    </Proxy>

    • Esc
    • :wq!
  7. Reboot the jsdn server using below command:

    reboot

Monitoring Server Manual Setup

Build Information

  • Linux

Integration Environment

Environment Version
Application Server JBoss 7.1.1.Final
Database Postgresssql (9.3.6)
Operating System CentOS Linux 7.2.1511 64 bit
Processor Intel(R) Xeon(R) CPU X5680 @ 3.6GHz or above
Web Server Apache2.4.7
CPUs 2
RAM 8 GB
Disk Space 50 GB or above

Terminologies used

  1. <<JBOSS_HOME>> = /d01/jboss-as-7.1.1.Final.
  2. <<JBOSS_SERVER_PRIVATE_IP>> = Appliance jboss server private IP.
  3. <<DB_SERVER_PRIVATE_IP>> = Appliance Jboss server private IP.
  4. <<monitoring_server_private_ip_address>> = Monitoring server private IP.

Prerequisite

A new monitoring server needs to be set up for monitoring to work in conjunction with JSDN appliance.
Note: Associate the public ip address to monitoring server.

Enable below security groups for monitoring server in AWS.

Custom TCP 111 <<JBOSS_SERVER_PRIVATE_IP>>/32
Custom TCP 2049 <<JBOSS_SERVER_PRIVATE_IP>>/32
HTTP 80 0.0.0.0/0
HTTPs 443 0.0.0.0/0
SSH 22 0.0.0.0/0
Custom TCP 8080 0.0.0.0/0
Custom TCP 5667 <<JBOSS_SERVER_PRIVATE_IP>>/32
  1. pp_config mount: in monitoring server.
    • yum install -y nfs*
    • vi /etc/fstab
      <<JBOSS-Server-Private-IP>>:/d01/jboss-as-7.1.1.Final/pp_config/d01/jboss-as-7.1.1.Final/pp_config nfs defaults 0 0
    • Esc
    • :wq!
      Note: Please install NFS in JSDN server before proceeding further.
    • service nfs start
    • systemctl enable nfs-server
    • mount -a
  2. In monitoring server copy the backup monitor tar file from /d01 location to pp_config location and extract the tar file in same location.
    • cd /d01/jboss-as-7.1.1.Final/pp_config
    • mv monitor monitor_bak
    • cp /d01/jboss-as-7.1.1.Final/monitor.tar
    • tar -xvf monitor.tar

Enable Below Security Group rules for Monitoring Server in AWS:

Steps:
Note: Please perform below steps in monitoring server.
  1. vi /d01/jboss-as-7.1.1.Final/bin/sj and search for 'java.rmi.server.hostname' and replace
     <<JOBSERVER_IP>> with ipaddress.
     -Djava.rmi.server.hostname=<<JBOSS_SERVER_PRIVATE_IP>>
  2. For creating fresh monitor schema do the below sub-steps.
  3. Update the database server details in installation.properties file.
    • vi ~jboss/monitoring_install_home/installation.properties
  4. Once you open the above installation file, under postgres section replace below place holders with proper db details and run the ant target using jboss user.

    For finding JSDN DB name access the below location in JSDN Server and open the xml file. The highlighted is the JSDN DB name.

    -------------------------------------------------------------------------------------

    JSDN DB Name :

    cd /d01/jboss-as-7.1.1.Final/standalone/deployments/

    vi as-pivotpath-oracle-ds.xml

    localhost:5432/jcp7125?stringtype=unspecified</connection-url>

    Note: jcp7125 is the JSDN DB name

    -----------------------------------------------------------------------------------------

    monitor_username=<<MONITOR_DB_NAME>>
    monitor_password=<<MONITOR_DB_NAME>>
    monitor_url=jdbc\:postgresql\://<<JBOSS_SERVER_PRIVATE_IP>>\:5432/<<JSDN_DB_NAME>>?stringtype\=unspecified
    username=<<JSDN_DB_NAME>>
    password=<<JSDN_DB_NAME>>
    url=jdbc\:postgresql\://<<JBOSS_SERVER_PRIVATE_IP>>\:5432/<<JSDN_DB_NAME>>?stringtype\=unspecified
    postgres_database_name=<<JSDN_DB_NAME>>
    default_schema_name=<<JSDN_DB_NAME>>
    default_support_schema_name=<<JSDN_DB_NAME>>_support

    For saving property file.

    • Esc
    • :wq!
    Examples:
    <<JSDN_DB_NAME>> = jcp7123
    <<MONITOR_DB_NAME>> = jcp7123_mon
  5. Go to monitoring install home folder and run the below ant target using jboss user.
    • su – jboss
    • cd ~jboss/monitoring_install_home/
    • ant setupMonitorDB
    • ant updateDBInJSDN
  6. Update the proper monitor schema IP details in as-monitoring-oracle-ds.xml in.
    1. cd ~jboss /standalone/deployments
    2. vi as-monitoring-oracle-ds.xml
    Example:
    <connection-url>jdbc:postgresql://<<DB_SERVER_PRIVATE_IP>>:5432/<<JSDN_DB_NAME>>?
    stringtype=unspecified</connection-url>
    <security>
    <user-name>MONITOR_DB_NAME</user-name>
    <password> MONITOR_DB_NAME </password>
    • Esc
    • :wq!
  7. Update proper JSDN schema IP details in as-pivothpath-oracle-ds.xml in.
    <<JBOSS_HOME>>/standalone/deployments folder .
    • cd ~jboss /standalone/deployments
    • vi as-pivothpath-oracle-ds.xml
    Example:
    <connection-url>jdbc:postgresql://<<DB_SERVER_PRIVATE_IP>>:5432/<<JSDN_DB_NAME>>?
    stringtype=unspecified</connection-url>
    Note: To replace Multiple values please use below command.

    ESC

    :%S/<<Old_Value>>/<<New_Value>>/g

    • Esc
    • :wq!
      Note: Please verify below entries.
  8. Update (if not found add) the below properties in.
    vi ~jboss/pp_config/monitor/monitor.properties and 
    vi ~jboss/pp_config/dynamicproperty.properties
    PRIVATE_IP_FOR_MONITOR_SERVER=<<PRIVATE_IP_WHERE_MONITORING_INSTALLED>>
    PUBLIC_IP_FOR_MONITOR_SERVER=<<PUBLIC_IP_WHERE_MONITORING_INSTALLED>>
    PUBLIC_IP_FOR_AGENT_SCRIPT_SERVER=35.169.90.20
    PRIVATE_IP_FOR_AGENT_SCRIPT_SERVER=172.31.49.102
    • Esc
    • :wq!
  9. Update the below property in environment properties file.
    • vi/d01/jboss-as-7.1.1.Final/pp_config/environment.properties

    app_server_ips=<<JBOSS_SERVER_PRIVATE_IP>>

    • Esc
    • :wq!
  10. Reboot the monitoring server using below command:
    • exit (moving to root user)
    • reboot
  11. After reboot login to the monitoring server and switch to root user (sudo su) and then switch to jboss user (su - jboss) then start jboss service in monitoring server by using below commands.
    • cd ~jboss/bin/
    • ./sj
  12. Click RBAC Tab by login into super admin url:
  13. Click the “click here” link.

Manage Instance Details

Use the Instance Details page to view and edit the details of the instance you selected. You can view the instance name, the status of the instance, the security groups associated with the instance (if applicable) and the resource configuration for the instance. The following sections will guide you to understand the activities you can perform on this page.

View and Edit Instance Details

To view or edit an instance details, do the following:

  1. On the Resourcesmenu, click Instances. The Instances page is displayed.
  2. On the Instances page, click the View Details link from the Actions column. The Instance Details page is displayed.

The following table displays the fields and options available on the Instance Details page.

Fields Description
Instance Name Displays the name of the instance. You can edit the instance name as required.
Stack Name Displays the stack name to which the instance is associated to. Click the link to know more about the stack.
Network ID Displays the network Id where the instances belongs to.
Vendor Displays the provider name.
Region Displays the region in which the instance is running.
Image Displays the image which is used for creating the instance.
Availability Zone Displays region and availability zone (if available for the vendor) where the image is created.
Family Displays the category to which the family belongs to. These families are categorized into General Purpose, Compute Optimize, GPU Instance, Memory Optimize and Storage Optimize.
Type Displays the type of instance. Instance types comprise varying combinations of CPU, memory, storage, and networking capacity and give you the flexibility to choose the appropriate mix of resources for your applications. Each instance type includes one or more instance sizes, allowing you to scale your resources to the requirements of your target workload.
Size Displays the size of the Amazon instance. Applicable only to Amazon service.
Enable Monitoring Displays whether monitoring is enabled or not.
Status Displays the status of the instance. Displays whether the instance is running, stopped or terminated. Click the Action drop-down list to see the list of actions available. Select the action you want to do.
Termination Date Select the date by when you want to terminate the service. After selecting the date, click Apply. Applicable to only “running” and stopped” instances.
IP Displays the IP address of the server. Applicable to only “running” and “terminated” instances.
Provision Date Displays the provision date. This displays the date what it was last created on.
Imported Displays whether the resources are imported or not from the ISV portal.
If you make any changes to the instance details, click Save to save the changes.
Note: Some of the parameters vary based on the cloud providers.

Manage Network Interface

Use the Network Interface page to add and manage network interfaces for the selected VM. The page lists the available network interfaces and associated network, subnet, private IP, Public IP, Security Group, status and other details. You can also edit and delete the network interface details using this page. You can also add new network interface using the Add New Interface option. The following table displays the fields and options available on the Network Interface page.

Fields Description
Name/Description Displays the name/description of the Network Interface.
Network Displays the network where the instances belongs to. Displays the selected VPC/VNet
Subnet Displays the associated subnet.
Private IP Displays the selected private IP address of the machine.
Public IP Displays the selected public IP address of the machine.
Security Group Displays the security group associated with the network interface.
Status Displays the status of the network interface.
Actions Displays the actions available. You can edit and delete the network interface details.
Adding New Network Interface

In addition to the default network interface, if you want to add a new interface, you can do it using the Add New Interface option.

  1. On the Resourcesmenu, click Instances. The Instances page is displayed.
  2. On the Instance Details page, click the Network Interface tab. The Network Interface page is displayed.

  3. Click the Network Interface page, click Add Network Interface. The Add Network Interface window will be displayed.
  4. In the Add Network Interface window, enter the details required for creating the network interface.

  5. In the Name /Description field, enter the name/description for the network interface.
  6. Select the Subnet from the list of available subnets in the customer’s account that belong to the selected VPC/VNet. The subnets are specific to a VPC/VNet. Click here to know how to create VPC and Subnets.
  7. Private IP - Provide the Private IP address for the machine. If you leave the field blank, the VM will be auto assigned with a private IP (dynamic). If you want to provide a static private IP, please type a valid IP address which is in the range of selected Subnet.
  8. Public IP - Provide the Public IP address for the machine. If you leave the field blank, the VM will be auto assigned with a NAT’ed public IP. If you want to provide a static public IP, please type a valid IP address which is in the range of selected Subnet.
    Note: For Private Cloud select the Public IP (Floating IP) or select the option as "None" then no IP will be assigned to the network interface.
    Note: When you select a static public IP and launch the VM, the IP will be allotted to the user and will not be available to other users.
  9. If you select no public IP, the interface will not have the public IP.
  10. In the Security Groups section, click Create Security Group.
  11. Click Add.
Deleting the Additional Network Interface

You can use the Network Interface page to delete a non- default network interface. To delete a network interface, do the following:

  1. On the Resourcesmenu, click Instances. The Instances page is displayed.
  2. On the Instance Details page, click the Network Interface tab. The Network Interface page is displayed.
  3. Click the Network Interface page, click the Actions drop down and then click the Delete link next to the interface which you want to delete.
  4. You will be prompted to confirm the deletion.
  5. Click Confirm.
The Network Interface will be deleted.
Note: You cannot delete a default network interface.
Note: If the Network Interface is not removed, any associated Public Static IP addresses will remain associated with the Network Interface.
Managing Static Public IP Addresses

Use the Static Public IP Address page to manage all the static public IP addresses. It lists all the available static public IP and their details. You can obtain a new IP or release an existing IP.

The following table displays the fields and options available on the Static Public IP Address page.

Fields Description
Provider Displays the name of the provider from which the IP address was obtained.
IP Address Displays the actual IP address assigned to the virtual machine. For AWS, it is an elastic IP. In the case of Azure, it is a reserved IP.
Associated Network Interface It displays the network interface IP is currently associated with.
Associated VMs Displays the name of the virtual machine the IP is associated with.
Actions Click the Actions list and then click the Release IP to release the IP.
Obtaining Static Public IP Addresses
  1. On the Resourcesmenu, click Static Public IP Address. The Static Public IP Address page is displayed.
  2. On the Static Public IP Address page, click Obtain New IP. The Obtain New IP window is displayed.
  3. Select the provider from whom you want to obtain the public static IP address. The public IP addresses retrieved from the provider can only be used with the VMs of the same provider.
  4. Select the Region from the Region drop-down list. Here, you will be selecting the region the IP address will be available in.
  5. Click Confirm.
    Note: The public IP addresses retrieved from the provider can only be used with the VMs of the same provider.

Once IP is successfully obtained, you can assign it to VMs.

Releasing a Static Public IP Address
  1. On the Resourcesmenu, click Static Public IP Address. The Static Public IP Address page is displayed.
  2. On the Static Public IP Address page, click the Actions list next to the IP you want to release and then click the Release IP to release the IP.
  3. You will be prompted to confirm the release of the IP, click Confirm.
    Note: If the IP is currently associated with a network interface, the system disassociates it before releasing the IP.
What are Tags?

Tags are just labels which you can use to classify the instances you use. A tag consists of a key/value pair. You can add up to 10 unique tags to each instance. Tags enable you to manage the infrastructure services in a better way. For example, if you want to assign this instance to the Recruitment team in the HR department, you can create a tag as Recruitment with value HR. A tag consists of a key and value. Either select an existing Tag and Value from the drop-down list or Type a Tag and Value of your choice.

Adding Tags

You can add tags which you want to associate to an instance in the Additional Information window while ordering an IaaS service. You can select an existing tag and value from the drop-down list or Type a tag and value of your choice.

You can also add tags to a specific instance using the Instance Details page. To add tags to a specific instance, do the following:

  1. On the Resourcesmenu, click Instances. The Instances page is displayed.
  2. On the Instances page, click the View Details link from the Actions column. The Instance Details page is displayed.
  3. On the Instance Details page, click the Tags tab.
  4. On the Tags tab, click Add Another Tag link. Add tag and value as required.
  5. Click Save.
Editing Tags

You can edit tags that are associated with a specific instance. To edit tags associated with a specific instance, do the following:

  1. On the Resourcesmenu, click Instances. The Instances page is displayed.
  2. On the Instances page, click the View Details link from the Actions column. The Instance Details page is displayed.
  3. On the Instance Details page, click the Tags tab.
  4. On the Tags tab, edit the tag name and value as required. You can add tags as well.
  5. Click Save.
Viewing Tags Associated with the Instance

You can use tags to manage and identify your instances easily. Tags are just labels which you can use to classify the instances you use. A tag consists of a key/value pair. You can add up to 10 unique tags to each instance. To view the associated tags with a specific instance, do the following:

  1. On the Resourcesmenu, click Instances. The Instances page is displayed.
  2. On the Instances page, click the View Details link from the Actions column. The Instance Details page is displayed.
  3. On the Instance Details page, click the Tags tab. It displays the tags and the tag details (Key and Value). If required, you can also add tags to associate instances.
  4. If you make any changes to the Tags page, click Save to save the changes.
Deleting Tags

You can delete your tags from the Instance Details >Tags tab. To delete tags, do the following:

  1. On the Resourcesmenu, click Instances. The Instances page is displayed.
  2. On the Instances page, click the View Details link from the Actions column. The Instance Details page is displayed.
  3. On the Instance Details page, click the Tags tab.
  4. Click the (X) cross sign next to tag to delete the tag. The tag is deleted.

Manage Images

The Images page lists all the images created and available to you. It also displays all the images which are in the error and in progress state.

The following table displays the options available on the Images page:

Fields Description
Image Name

Displays the image name. It displays the image name up to 12 characters and then truncated by three dots.

You can create an instance from the image. Click Launch Instance next to the image name to create an instance out of it. A replica of the instance (the same state when the image was created) will be created from the image.The launch instance link is available only for active instances.

Description Displays the short description for the image. It displays upto 12 characters and then truncated by three dots.
Provider Displays the name of the image provider/vendor.
Region/Availability Zone Displays region and availability zone (if available for the vendor) where the image is created.
Created On Displays the date when image was created.
Created By Displays the name of the user who created the image.
Source Instance Displays the name of the source instance from which the image was created.
Status Displays the status of the image. It displays images which are in active, error and in-progress status. You can perform actions only on the images which are in active status.

Create an Instance from an Image

You can create an instance from an image. To create an instance from an image, perform the following steps:

  1. On the Resourcesmenu, click Images. The Images page is displayed.
  2. On the Images page, click the Create Instance link from the Actions column from which you want to create an instance. The Application Stack designer console is displayed.
  3. Type the name of the stack in the Stack Name field. Type a short description for the stack in the Description field.
  4. Select the instance/resource within the designer console. The Resources Properties section displays the instance level details. It displays vendor, operating system, flavor/instance type and region. You can review the details. Select the operating system and other required parameters which you can change.
  5. Click Launch. You can view the newly launched instance on the Instances page. You can start using the instance as any other instance.
    Note: The selection parameters in the Resource section vary based on the supported vendor.

Delete an Image

To delete an image, perform the following steps:

  1. On the Resourcesmenu, click Images. The Images page is displayed.
  2. On the Images page, click the Delete link from the Actions column which you want to delete. You will be prompted to confirm the deletion.
  3. Click Yes to confirm the deletion. The image will be deleted.

Manage Volumes

The store offers highly reliable and consistent block level storage volumes for use with the instances. You can add multiple volumes to scale up the storage and performance of the instance. The Instances/Instance Details page lets you add more block storage volume to your instances. Only volumes which are from the same vendor and which are compatible with the instance are displayed for your selection.

You can attach a new volume or an existing volume to an instance which is available in the same availability zone. You can choose the type of the storage, the performance type (standard or high performance), volume size, processing speed of the volume (IOPS- Input Output per second) etc. from the selection parameters. You cannot modify these parameters after the volume is provisioned to you. Once you attach a volume, you can mount these volumes as devices on your instances. You can use these volumes as how you use a hard drive.
Note: Block storage provided by some vendors are closely linked to the attached instance. When you terminate the instance, the associated volumes will be terminated along with instance. Some other vendors support block storage which persist independently from the life of the instance.

Attach Volume

Attach a New Volume

You can attach a volume to an instance in the same location and from the same provider. The volume can only be attached to an instance which is in the running status. To attach a volume to an instance, do the following,

  1. On the Resourcesmenu, click Instances. The Instances page is displayed.
  2. On the Instances page, click the Attach New Volume link from the Actions column. The Add New Volume window is displayed.

  3. Type a suitable volume name in the Volume Name field. This helps you to identify the volume.
  4. Select the Volume type from the Type drop-down list. The volume types vary based on vendors. You can decide whether you need standard or high performance volume types.
  5. In the Size field, type the size of the volume in GB or TB.
  6. Click Done.

A new volume with the selected specifications is created and attached to the instance.

Attach an Existing Volume

To attach an existing volume, do the following:

  1. On the Resourcesmenu, click Instances. The Instances page is displayed.
  2. On the Instances page, click the Attach Existing Volume link from the Actions column. The Add Existing Volume window is displayed.

  3. All the volumes which are available in the free pool for your consumption will be displayed.
  4. Mark and select the volumes which you want to attach to your instance.
  5. Click Done. All the selected volumes will be attached to the instance.
    Note: Before you attach any volume, refer to the Live Dashboard to verify the volume status. Because, the volumes that are deleted at ISV level are still displayed.

Detach Volume

You can detach a volume from an instance. Once you detach the instance, it will be moved to the free pool. Even after you detach the volume from an instance, you will be charged for the same. To stop paying for the unwanted volume, you need to terminate them.

  1. On the Resourcesmenu, click Instances. The Instances page is displayed.
  2. On the Instances page, click the View Details link from the Actions column. The Instance Details page is displayed.
  3. On the Instance Details page, click the Volume tab.
  4. Click the Detach link. An alert message will be displayed prompting you to confirm whether you want to detach the volume. The volume will be detached from the instance and will be moved to the available pool.

Create Volume Snapshot

You can take the backup or shadow copy of your volume using snapshots. A volume snapshot is a point-in-time copy of the volume. You can create another volume from the volume snapshots. To create a snapshot of the volume, do the following:

  1. On the Resourcesmenu, click Instances. The Instances page is displayed.
  2. On the Instances page, click the View Details link from the Actions column. The Instance Details page is displayed.
  3. On the Instance Details page, click the Volume(s) tab.
  4. Click the Create Volume Snapshot link from the Actions column. A Create Volume Snapshot window will be displayed.
  5. In the Create Volume Snapshot window, type the name and description for the volume in the respective fields. You need to provide a unique snapshot name, the name is case sensitive and should not exceed beyond 50 ASCII characters. In the Description field, provide a short description for the snap shot.The description field is case sensitive and should not exceed beyond 500 ASCII characters.
  6. Click Done.
    Note: You can create volume snapshots only for AWS and OpenStack volumes. The store does not support creating volume for VCD.
    Note: If your volume is mounted, it is recommended that you unmount the volume first and then take the snapshot.

Once the volume snapshot creation is done, you will be redirected to the Volume Snapshots page where the snapshot you just created is listed. (Click the Volume Snapshots link, it takes you to the Volume Snapshots page.)

Delete and Terminate Volume

You can delete the volume once you no longer need it. Once you delete the volume, the data within is lost. So, make sure you have a backup for your data.

  1. On the Resourcesmenu, click Instances. The Instances page is displayed.
  2. On the Instances page, click the View Details link from the Actions column. The Instance Details page is displayed.
  3. On the Instance Details page, click the Volume(s)
  4. Click the Detach and Terminate link. An alert message will be displayed prompting you to confirm whether you want to detach and terminate the volume. Once you confirm, the volume will be detached and terminated.

Manage Volume Snapshots

The Volume Snapshots page lists all the volume snapshots created and available to you. It also displays all the volume snapshots which are in the “error” and “in progress” state.

The following table displays the options available on the Volume Snapshots page:

Fields Description
Snapshot Name

Displays the name for the volume snapshot. It displays the image name up to 12 characters and then truncated by three dots.

You can create a volume from the snapshot. Click Create Volume next to the snapshot name to create a volume out of it. A replica of the volume (the same state when the snapshot was created) will be created from the snapshot.

Description Displays the short description for the image. It displays upcto 12 characters and then truncated by three dots.
Provider Displays the name of the volume snapshot vendor.
Region/Availability Zone Displays region and availability zone (if available for the vendor) where the volume snapshot is created.
Created On Displays the date when volume snapshot was created.
Created By Displays the name of the user who created the volume snapshot.
Source Volume Displays the name of the source volume from which the volume snapshot was created.
Status Displays the status of the volume snapshot. It displays volume snapshots which are in active, error and in-progress, deleting status. You can perform actions only on the images which are in active status.

Creating a Volume from a Volume Snapshot

You can create a volume from a snapshot. To create a volume from a snapshot, perform the following steps:

  1. On the Resourcesmenu, click Volume Snapshots. The Volume Snapshots page is displayed.

  2. On the Volume Snapshots page, click the Create Volume link next to the snapshot name from which you want to create a volume. The Create Volume window is displayed.
    Note: You can create volume only from active snapshots.
  3. Type a suitable volume name in the Volume Name field. This helps you to identify the volume. Provide a unique name for the volume. This field is case sensitive and it accepts only a maximum of 50 ASCII characters.
  4. Displays the Region where the volume is getting created.
  5. Select the Type of volume which you want to create. The volumes differ in performance characteristics. Select the type from the Type drop-down list. The volume type may vary based on vendors. You can decide whether you need standard or high performance volume types.
  6. In the Size field, type the size of the volume in GB or TB.
  7. Click Done.

Delete Volume Snapshots

To delete a snapshot, perform the following steps:

  1. On the Resourcesmenu, click Volume Snapshots. The Volume Snapshots page is displayed.
  2. On the Volume Snapshots page, click the Delete link next to the snapshot which you want to delete. You will be prompted to confirm the deletion.
  3. Click Confirm to confirm the deletion. The snapshot will be deleted.
Once you delete the snapshot, the data will be lost. So, please be careful when you delete a snapshot which is a part of the instance snapshot (image).
Note: Some vendors (OpenStack) do not allow termination of an instance or volume if they have active snapshots associated with them. In such cases, you need to delete the snapshot first before deleting the volume.

Manage Security Groups

The security group section explains how to create, view, edit, and delete security groups. When you buy an instance, you can associate one or more security groups with the instance. The security group rules determine which network traffic should be delivered to the selected instance. You can implement network rules for a security group and then associate the security groups to an instance to ensure that the instance is in compliance with the network policy of the organization.

Security Groups Concepts Overview

Regardless of the type of instance you order, the store makes sure that the network level security rules are implemented and addressed at an instance level. You can define rules based on the protocol and port range (or ICMP type and code); it does not allow traffic from any other IP addresses. You can view and modify the rules for a security group any time. The rules that you modify are automatically applied to all instances that are associated the security group.

You can associate a maximum of 500 security groups to an instance. When multiple security groups are applied to an instance, the rules from each security group are effectively aggregated to create one larger set of rules. The aggregated rules are then used to determine access to the instances. If you do not specifically associate a security group to an instance, the instance is automatically associated to the default security group and the rules associated with the security group.

Add New Security Group

To add a new security group, do the following:

  1. On the Resourcesmenu, click Security Groups. The Security Group page is displayed.
  2. On the left pane, you can find the list of existing security groups. On the right pane of the page, the Add New Security Group section is displayed. If you want to add a new security group while reviewing the details of another security group, click Add Security Group.
  3. In the Details section, enter the Group Name in the Group Name field.
  4. In the Description field, enter a suitable description for the security group.
  5. If you want to make this security group as the default security group for your organization, enable the Select the check box to set the security group as default for your organization check box. If you do not associate a security group with the instance, the default security group will be associated to the instance automatically.

Now, add the security group permissions as required and then click Save.

Add New Permissions

  1. Now, you can set the rules which decide the network rules for these security groups. To set the new permission level, click Add New Permission.
  2. Set the network rules by specifying the following details:

    The security group rules enables a specific source to reach the instances using a certain protocol (TCP, UDP, or ICMP) and destination port or ports (if the protocol is TCP or UDP). For example, a rule could allow IP address 205.2.132.5 (the source) to reach the instances on TCP port 22 (the protocol and destination port). If you specify ICMP as the protocol for the rule, you must also specify an ICMP type and code.

    First, select the Protocol Type, TCP, UDP or ICMP from the Create a New Rule drop-down list.

    Port Range

    In Port range, specify a port or port range.

    • TCP – You can enter the port ranges in the To and From fields. If a single port is required then the From and To value should be the same. The values accepted are 1 to 65535.
    • UDP – You can enter the port ranges in the To and From fields. If a single port is required then the From and To value should be the same. The values accepted are 1 to 65535.
    • ICMP – Instead of the From and To, the two text boxes will be replaced with Type and code. The values Accepted are 1 to 65535.

    Source

    In the source field, type the IP address or range of addresses in CIDR notation that is allowed access. For example, you can use 205.2.132.5 to limit access to one computer at that IP address; 205.2.132.5/24 to limit access to a network at that range of IP addresses. You can enter 0.0.0.0/0 to allow all IP addresses to access the specified port range.

    • In Port range, specify a port or port range.
    • IP Address: Values 000 to 255 at each offset. Format (xxx.xxx.xxx.xxx)
  3. Click Add New link to add new permission.
  4. Click Save. The new security group with a set of permissions is created.

View Permissions of a Sercurity Group

You can view the permissions configured of a security group. To view the details, do the following:

  1. On the Resources menu, click Security Groups option. The Security Groups page is displayed.
  2. On the Security Groups page, click the Security Group link whose details you want to view from the left pane of the page. The detail of the security group is displayed.

Edit Security Group

You can edit the description and the access type of a security group. To edit the security group details, do the following:

  1. On the Resources menu, click Security Groups option. The Security Groups page is displayed.
  2. On the Security Groups page, click the Security Group link whose details you want to view from the left pane of the page. The detail of the security group is displayed.
  3. You can edit the description by typing the description in the Description field.
  4. You can change the status of the security group - whether the security group is the default group for all the instances you order for your organization.
  5. You can modify the permissions or add new permissions if required.
  6. Once you complete your changes, click Save.
    Note: You cannot change the name of the security group.

Delete Security Group

To delete a security group, do the following:

  1. On the Resources menu, click Security Groups option. The Security Groups page is displayed.
  2. On the Security Groups page, click the Security Group link whose details you want to view from the left pane of the page. The detail of the security group is displayed.
  3. Click Delete Security Group.
    Note: You cannot delete security groups that are associated with running instances.
  4. You will be prompted to confirm the deletion.
  5. Click Confirm. The selected security group is deleted.

Life Cycle Management

This section explains you about Life Cycle Management of an Instance. How you can launch your instance (SSH - secure shell), stop, terminate and reboot your instances using this tab. It displays the list of instances ordered for your organization, their status, and the tags associated with the instances. It also displays the number of instances which are running, stopped, terminated, and other status. You can search for instances based on the instance name. Click here to know more about Instance Life Cycle Management.

Import IaaS Resources

Note: Pre-requisite is to configure images associated with the instances. Click here to know Onboarding OS Images for AppStacks.

It is difficult for organizations to manage multiple cloud services provisioned from various vendors outside the store. When you have existing IaaS resources from disparate IaaS vendors, the administration of these resources becomes difficult. It limits monitoring, managing and efficiently managing of these resources. It is important that you need a single pane of glass for managing all your IaaS resources.

The store allows you to easily bring in your existing resources with other vendors so that you can manage the life cycle activities of these resources. You can use the Import IaaS Resources feature to bring in the existing resources to the store. The platform provides two ways of importing your IaaS resources (a) Manual Import and (b) Auto Import Resources. For Manual way of import, you need to download the template provided by the store, follow the instructions in the template and specify the data accordingly. Once you enter the required information, upload the template file without making any change in the format.
Note: To import IaaS resource details directly from vendor portal, the store should have the customer’ account details with the vendor in the system. Another requirement is that there should be at-least one billing subscription generated/available for the customer in the system. Click here to know how to add customer account details.
Note: Before you start importing your resources, it is mandatory to associate your Image IDs in JSDN. Please contact your administrator to have your Image IDs associated in JSDN or refer to On Boarding OS Images.
Note: The usage record should be created for the instance that you want to import into the system.

Manual Import

Note: The Manual Import process is applicable only for importing Google Cloud resources. The current functionality allows you to import resources such as VMs, Storage Volumes and Network Interfaces only. However for importing resources of other providers use the "Auto Import Resources" process. If you still want to import resources for other providers manually, then please contact Jamcracker Support team.

To import existing IaaS resources manually, do the following:

  1. On the Resourcesmenu, click Import IaaS Resources. The Import IaaS Resources page will be displayed.

  2. To download the template, click the.xls or.xlsx link and then download the Resource Template. You can save the file on your local computer. Read through the instructions in the first worksheet, then fill up the required information carefully. Do not fill the SecurityGroups worksheet in the downloaded file, as it is not supported for Google Cloud Platform.
  3. To upload the template, click Choose File and then browse and select the template file, then click Upload.
    Note: Once you upload the file, it is recommended that you should not refresh the Manual Import page. As the browse might re-initiate the import process.
    Note: The budget code column in the Import Resource template is applicable to only organizations which use budget functionality.

The Import History section displays the import file history and the upload details. The following table displays the options available in the Import History section:

Fields Description
File Name Displays the name of the uploaded template file.
Uploaded By Displays the name of the user who uploaded the file.
Uploaded On Displays the date when the file is uploaded.
File Processing Status Displays the file processing status. If the process is successful, the file processing status is displayed as Completed. If the import process is still in progress, it displays the In Progress status. If an error occurred while importing, it displays the Error status. If the file processing is failed completely or partially, the status is displayed as Failed. Click the Failed link to view the details of the file processing and the failure reasons.
Note: For monitoring the imported resources, please install the monitoring agent manually in the instances which are to be monitored. Refer to the Installing Monitoring Agent in the Imported VMs for more information.

Auto Import Resources

Note: Pre-requisites: Before you start importing your resources, it is mandatory to associate your Image IDs in JSDN. Please contact your administrator to have your Image IDs associated in JSDN or refer to On Boarding OS Images.

To Automate the import resources process, do the following:

  1. On the Resourcesmenu, click Import IaaS Resources. The Import IaaS Resources page will be displayed.
  2. Click the Auto Import Resourcesicon. The Auto Import Resources/Schedule Automated Import page, displays list of providers added so far. Refer to the below table to see the list of supported providers along with the resource type.
    Resource Type AWS Azure (CSP) Azure (PAYG) IMB Bluemix OpenStack
    VMs Yes Yes Yes Yes Yes
    Storage Volumes Yes Yes Yes Yes No
    Network Interfaces Yes Yes Yes Yes Yes
    Security Groups Yes Yes Yes No Yes
  3. Select the provider from which you want to import your resources.

  4. Click Create. A scheduled import is created and set to run the job once in everyday. During this time, the system will update the log.
  5. Click View Log link from the Actions column, to view the logs of the respective provider account.

  6. The View Log page displays list of resources that are imported on a particular date/days. Click the View Details link to view the status of the resources that are imported.

  7. If you want to delete the Auto Import, click the Delete icon from the Action column. A Confirmation message is displayed.
  8. Click Confirm, to delete.
    Note: If it is a reseller store, while importing resources through the automated process, you cannot associate a budget code.

Once you complete the import process, you can launch and manage the life cycle of the imported resources just like any other IaaS resource which you provisioned in the store. To perform an SSO or SSH to the instance, you need to provide the valid credentials or up load the .PEM file.

You can identify your imported resources from the Instance page and Instance Details page; the imported resources will have Yes in the Imported Resources column.

Manage Resource Scripts

The Resource Scripts framework in JSDN Platform helps you to create various resources scripts.

The current version of JSDN Platform supports Ansible scripts to launch resources. It comes with some pre-seeded templates like Database, S3 Bucket, Elastic Load Balancing, Elastic Container Service, Route 53 and more to consume the resource. However, these resources can be managed only through provider console only.

The JSDN Platform helps you to execute your own custom script by selecting the Resource Type as "Custom" and providing a valid script.
Note: You should have valid permissions to perform the following actions. If you don’t see any of the options, we recommend you to contact your administrator.

Add New Script

  1. On the Resourcesmenu, click Resource Script. The Manage Resource Script page is displayed with list of existing scripts that are added so far in the platform.
  2. Click the Add Script icon. The Add Script page is displayed.
  3. Select the Provider from the drop-down list. Please note, the current release of JSDN is supported for Amazon Web Services only.
  4. Select the Resource Type from the drop-down list. You can select either Elastic Container Service, Identity and Access Management, RDS, Network, Route53, S3 Bucket or Elastic Load Balancing from the drop-down list.
  5. If you select Elastic Container Service (ECS) as your resource type, you will have an option to select "Launch ECS Instance" or "Delete ECS Instance".

    OR

  6. If you select Identity and Access Management (IAM) as your resource type, you will have an option to select "Create IAM Role" or "Delete IAM Role".

    OR

  7. If you select Relational Database Service (RDS) as your resource type, you will have an option to select either “Launch DB Instance” or “Delete DB Instance” or “Modify DB Instance” from the Template drop-down list. OR
  8. f you select Network as your resource type, you will have an option to select either “Create Subnet” or “Create VPC” from the Template drop-down list.

    OR

  9. If you select Route53 as your resource type, you will have an option to select "Create Zone" or "Create or Update a Record Set" or "Create or Update Multiple Record Sets" or "Delete a Record Set".

    OR

  10. If you select S3 Bucket as your resource type, you will have an option to select "Create S3 Bucket" or "Delete S3 Bucket".

    OR

  11. If you select Elastic Load Balancing (ELB) as your resource type, you will have an option to select "Create ELB" or "Delete ELB" or "Link Instance to ELB".

    OR

  12. If you select Custom as your resource type, you will have an option to select "Custom Template".

    OR

  13. If you select VPN as your resource type, you will have an option to select "Create VPN" or "Delete VPN".

    OR

  14. If you select DynamoDB as your resource type, you will have an option to select "Create Table" or "Delete Table".
  15. Enter a name for the script. Provide a unique Script Name to identify your template. It is case sensitive and should not exceed beyond 128 ASCII characters.
  16. If you want to modify the existing script, you can modify it. If you modify the script it is recommended that it should be in working condition before executing.
  17. Click Execute, to execute the script.
  18. Click Save, to save the script.

    Once the script is executed, you can refer to your Manage Resource Script page to see the status. If the script is successfully executed, you will see the status as Completed. If it fails, you will see the status as Failed.

Edit Script

  1. On the Resourcesmenu, click Resource Script. The Manage Resource Script page is displayed with list of existing scripts that are added so far in the platform.
  2. Please note, you can edit the scripts those are in Failed status.
  3. Click the Edit link from the Action column. The Edit Script page is displayed.
  4. On the Edit Script page, make the necessary changes and click Re-execute.

View Script Logs

  1. On the Resourcesmenu, click Resource Script. The Manage Resource Script page is displayed with list of existing scripts that are added so far in the platform.
  2. Click the View Log link from the Action column. The View Log pop-up window is displayed.
  3. The View Log pop-up window displays the log details.

View Script

  1. On the Resourcesmenu, click Resource Script. The Manage Resource Script page is displayed with list of existing scripts that are added so far in the platform.
  2. Click the View Script link from the Action column. The View Script pop-up window is displayed.
  3. The View Script pop-up window displays the script that was used while adding the script.

Re-execute Script

  1. On the Resourcesmenu, click Resource Script. The Manage Resource Script page is displayed with list of existing scripts that are added so far in the platform.
  2. Please note, you can re-execute the scripts those are in Failed status.
  3. Click the Re-execute link from the Action column. A confirmation message is displayed.
  4. Click Confirm, to delete the script.

Delete Script

  1. On the Resourcesmenu, click Resource Script. The Manage Resource Script page is displayed with list of existing scripts that are added so far in the platform.
  2. Please note, you can delete the scripts those are in Failed status.
  3. Click the Delete link from the Action column. A confirmation message is displayed.
  4. Click Confirm, to delete the script.

Security

Jamcracker Platform addresses cloud security issues in the following ways:

Centralized, subscription management and single sign on. When a user or employee leaves, the service subscriptions can be terminated from a single console, reducing risk of services being left on and accessible after the employee leaves.

When user management is integrated with LDAP based directories such as Active Directory or RedHat Directory services, or SAML 2.0 based federated identity services, then user management remains centralized in the directory and federated identity servers, allowing user management to continue with familiar systems.

For Infrastructure as a Service, the Recommendations Dashboard provides a view into security groups that have wide open ports on the internet for protocols other than HTTP (Port 80) and HTTPS (Port 443).

Further, Jamcracker Platform uses standard frameworks and tools to enforce security standards. The following are the key features of the platform security:

  • Robust authentication mechanism based on Java Authentication and Authorization Service (JAAS)
  • Completely Automated Public Turing test to tell Computers and Humans Apart (CAPTCHA)
  • Protection for sensitive pages
  • Role Based Access Control (RBAC) framework based on JAAS to validate every request
  • Protection based on the Open Web Application Security Project (OWASP) recommendations
  • Restrictions on GET and POST interchange operation
  • Sensitive Information is not submitted in GET Parameter
  • Auditing mechanism logs all the user activities in database
  • Hypertext Transfer Protocol (HTTP) header log for each request
  • All sensitive information (password, credit card numbers, and so on) are encrypted/hashed and stored in database
  • Support for Payment Card Industry (PCI) compliant hosting
  • Defined process for production server hardening
  • Protection against Web Directories List Vulnerability
  • Protection against Path-based Vulnerability
  • Protection against Directory Listing
  • Secured cookies
  • Protection against Layer 7 DoS/DDoS attack
  • Step-up authentication
  • Secured storage of sensitive configuration parameters
  • Protection against concurrent login (concurrent login restriction)

Compliance

Jamcracker Platform provides, in a single platform instance, centralized marketplace and administrative interface for all aspects of cloud service brokerage, governance and management, including services, orders, users, and organization or department specific portals.

Within the same platform instance, multiple portals can be utilized to deliver organization specific catalogs, AAA, roles, financial management and policies. All of these functionalities roll up at the marketplace level where instance wide operations and control can occur.

Delegated administration to each organization can be provided, or a single administrator/administrative group can be employed to manage all MACD requests.

Virtually all events in the system are logged and can be reported on when compliance reports are required.