Virtual Private Cloud on Azure. Deployment Manual

The PaaS offers platform for Java, JavaEE and PHP applications with advanced automation for certified containers.

The platform is available for automatic and seamless installation on top of Azure, providing a fast and easy method to get into the cloud. Using Azure Marketplace, any ISV or enterprise customer can create the PaaS Orchestrator in the Azure cloud.

Easy installation of dedicated Virtual Private Cloud takes just a few hours but not days or months. In such a way, any ISV or enterprise can get their own light-weight version of the platform with a full range of features and great performance due to premium storage instances with local SSD.

Pre-Requirements

1. Active Azure Subscription

2. Domain Name for Platform VPC Instance

3. Preconfigured Azure Storage for Platform VM

Go to the Azure portal and click on the New button, then select the Data+Storage > Storage item.

Azure Storage for platform VM

Customize it with the required data:

  • Storage - name of your storage account
  • Pricing Tier - storage redundancy and performance
  • Resource Group - create new or choose the existing one
  • Subscription - choose subscription the storage will be bound to
  • Location - select the appropriate Azure region for your storage
  • Diagnostics - define if you want Azure to monitor your storage health

Click Create when the required data is filled in.

4. Created Virtual Network for Platform VM

Click on the New button and select the Networking > Virtual Network item:

Virtual Network for platform VM

Fill in the required data:

  • Name of your virtual network
  • Address space, Subnet name and Subnet CIDR block - select the appropriate address space and network size
    At the moment you should stick the Subnet CIDR block to 10.0.0.0/24 subnet. This limitation will be removed in the future PaaS for Azure releases.
  • Resource Group - create a new group or choose the existing one
  • Subscription - choose the required subscription
  • Location - select Azure region for your network (the same as you’ve selected for the storage account)

Click Create when the required data is filled in.

5. Odin Virtuozzo Containers (PCS) License

Send an email to the PaaS team requesting a product license:

  • Use the following address: <azure.marketplace@jelastic.com> and message subject: “Request for the platform License on Azure”
  • Describe how many Azure VMs you are going to create
  • The platform will send you back the list of license keys

Platform Installation via Azure Marketplace

Navigate to Azure Marketplace and find Jelastic Standard Edition.

Choose it and click Create Virtual Machine.

create Virtual Machine

After that, you will be redirected to Azure portal (where you need to sign up with your active Azure account) in order to provide the required data for the platform VM creation.

create VM for the platform Standard Edition

Create Platform VM

In the appeared tile, fill in the required data:

configure Azure VM

  • Host Name - name for your Platform VM
  • User Name, SSH Public Key or Password - credentials for VM administrator
  • Pricing Tier - the required VM specs (D12 or better is recommended for the platform infrastructure VM)
  • Optional Configurations required for setup:
    • In the Network setup panel, select the local virtual network you’ve created earlier. Specify the Domain Name for your platform - choose the existing domain or create a new one. In the IP Addresses configuration panel, turn the Instance IP address switcher to On, set the Private IP address switcher to Static and specify the IP Address which will be used for the platform VM instance.
      At the moment you should stick the Subnet CIDR block to 10.0.0.0/24 subnet. This limitation will be removed in the future PaaS for Azure releases.
    • Configure the Storage account to point to the storage you’ve created earlier.
  • Resource Group - create a new group or choose the existing one
  • Location - select the Azure region for your Platform VM (the same as you’ve selected for the storage account and local network previously)

Click Create. The pricing information will be loaded. Click Buy.

Follow the same steps to create more Platform VMs required for your cluster.

create more VMs for cluster

Add Storage to Platform VM

The platform VPC requires two storage disks:

  • the first should be 350 Gb size or larger for infrastructure and end-user containers
  • the second should be 100 Gb size or larger for Docker cache and end-user uploads storage (this disk is required only for the first VM in your VPC, the next VMs in the cluster need just one storage disk for infrastructure and end-user containers)

So, follow the next steps to attach the additional storage disk to your Platform VM.

Select the Browse button, choose Virtual Machines and select the Platform VM you’ve provisioned earlier. Then click on the Settings, select Disks and select Attach New.

add storage to VM

Here you need to fill in the required data:

  • Storage Container - select the Storage account and Container where the data disk space will be allocated
  • Disk File Name - specify a disk name or leave it auto-generated by Azure
  • Size - the desired disk size in gigabytes
  • Host Caching - disk accesses caching policy. Select Read/Write for infrastructure and containers' data disk and Read Only for the disk with Docker cache and end-user uploads

Repeat the same steps to attach the second storage disk if you created the first VPC.

Platform Domain Name Configuration (for the First VPC Node)

Delegate a domain name of your PaaS instance to the Public IP address of your first Azure VM with the PaaS cluster deployed using the hints below:

  • Use your primary domain to delegate a subdomain for the platform name server. Recommended subdomain name:
    jelastic.primarydomain.com
  • DNS server names and addresses:
    ns1.jelastic.primarydomain.com
    1 IP address allocated for this DNS server
  • Zone records example (make sure this is a part of the file for the parent zone primarydomain.com) - note the last one is a glue record:
    jelastic.primarydomain.com IN NS ns1.jelastic.primarydomain.com
    ns1.jelastic.primarydomain.com IN A 1.1.1.1
Make sure you DON’T have the SOA record for the jelastic.primarydomain.com zone on your DNS servers - otherwise the delegation will not work.

Configure Platform Installation

1. Navigate to the provision portal at http://azure-master.jelastic.com.

2. Enter the IP address of your Platform VM, created earlier at the Enter your PaaS at Azure deployment IP address input box and select the Continue button. The provision portal will check this VM for prerequisites and prepare it for the platform configuration process.

enter your account at Azure deployment IP

3. At the next page, fill in the following data:

  • Choose the Virtual Private Cloud > Deploy new VPC type of installation to provision VM as infrastructure
  • Specify a dedicated Cluster domain name for a new VPC
  • State the Cluster admin credentials that will be used for your VPC
  • State the Cluster admin credentials for your existent VPC
  • Generate a new SSH private key for the inter-cluster communication (download and save the key if you plan to deploy more nodes to this VPC)
  • Paste the Odin Virtuozzo containers (PCS) license received from our platform
  • Confirm Terms of Use and click Install

configure installation

If you attach the second (or further) VPC to your cluster, you need to:

  • choose Add new user node to the existing Azure VPC item
  • specify a cluster domain and admin credentials of the initial VPC machine
  • upload SSH key previously generated for the initial VPC
  • state a new Odin Virtuozzo containers license received from the platform

The installation will take an hour or two depending on your VM CPU and storage speed, so please be patient.

installation on Azure in progress

After that, you’ll be redirected to the admin panel and can start managing your VPC.

cluster admin panel

User’s dashboard will be available via the corresponding cluster domain name with the app.* prefix (i.e. app.jelastic.primarydomain.com in our case).

What’s next?