Changes

To allow customers to familiarize themselves with improved containers technology of Virtuozzo 6 OpenVZ 7 and to maximize AWS Azure instance utilization along with security and isolation we introduce Virtuozzo 6 OpenVZ 7 image for Amazon EC2. Virtuozzo 6 supports only container technology then deployed on Amazon EC2Microsoft Azure.Virtuozzo 6 OpenVZ 7 image is shipped in two editionsone edition:#Virtuozzo 6 - Amazon Billable#Virtuozzo 6 BYOL - Bring Your Own License versionOpenVZ 7.

Log into the AWS Azure Virtual Machine Marketplacehttp://azure.microsoft.com/en-us/marketplace/virtual-machines/, search for the AMI image from Odin as the publisher, then click the selected product. Check the product description to verify it suits your needs. Then click the "ContinueCreate the Virtual Machine" button. You can choose the Manual Launch with EC2 console by the pressing corresponding tab, or continue with the 1-Click Launch using predefined settings (the 1-Click Launch option does not allow you to modify the default storage size and type when creating the instance: 30 GB magnetic storage. To change disk storage after deployment, see the Amazon AWS documentation: [http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-expand-volume.html Expanding the Storage Space of a Volume])Create button again. 1-Click Launch (predefined settings):#Select the "Region" to deploy the instance and the EC2 Instance Type depending on your needs (Note: the price is different for different regions).#In VPC settings, select where your instance will be deployed: EC2 classic (recommended) or your personal Virtual Private Cloud. If the VPC network is selected, please make sure that your virtual network is configured to provide internet access to the instance is being deployed. The main differences between EC2-classic and VPC are described in [http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-vpc.html Amazon EC2 and Amazon Virtual Private Cloud (VPC)]. Find more information about VPC in the [http://aws.amazon.com/documentation/vpc/ Amazon VPC documentation].#Select the default options or create a new Security Group based on seller settings. Pay special attention to the ports that are required for Plesk - see Knowledgebase article [http://kb.odin.com/en/391 KB391: Which ports need to be opened for Enter all Plesk services to work with a firewall?]#Select the Key Pair to be used for connection to the instance (an existing Key Pair is required for connection to the Virtuozzo instance). A Key Pair can be generated in the [https://console.aws.amazon.com/ec AWS Management Console].#Click the Launch with 1-Click button.By defaultinformation like hostname, instances are deployed with small root storage (30 GB). It allows you deploy around 10 containers depends on container OS user and installed packages. To deploy instances with bigger storagepassword, use Manual Launch with EC2 console.To change the disk storage after deploymentchoose authentication type, check the Amazon AWS documentation: [http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-expand-volume.html Expanding the Storage Space of a Volume]pricing tier and other properties. Manual Launch with EC2 console (adjust additional settings such as disk space before launch):#Click on the Manual Launch tab.#Click the Launch with EC2 Console Create button in the Region the instance is to be deployed.#In the opened EC2 Console, choose an Instance Type depending on your requirements. Then, click the Next: Configure Instance Details button.#Set instance details. Here, you can select how many instances Login to deploy and select a Network (EC2-classic or VPC).If the VPC network is selected, please make sure that your virtual network is configured to provide internet access to the instance is being deployed. The main differences between EC2-classic and VPC are described in [http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-vpc.html Amazon EC2 and Amazon Virtual Private Cloud (VPC)]. Find more information about VPC in the [httpAzure Management Portal https://awsmanage.amazonwindowsazure.com/documentation/vpc/ Amazon VPC documentation].#Change other options if required, then click Next: Add Storage#Add storage Login to your instance. It is recommended that you increase your disk storage from the default values - your disk will be automatically resized when the instance is deployed. To change disk storage after deployment, check the Amazon AWS documentationjust created VM: [http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-expand-volume.html Expanding the Storage Space of a Volume]. You can also add more storages to your instance and change the storage volume types to increase performance. Find more information about the storage type and pricing in the Amazon AWS documentaion: [http://aws.amazon.com/ebs/details/ Amazon EBS Product Details]. Click Next: Tag Instance#Add Tags for the instance. For example, you can define a tag with key = Name and value = virtuozzo. Learn more about tagging your Amazon EC2 resources. Click Next: Configure Security Group#Configure the security group. A security group is a set of firewall rules that control the traffic for your instance. It is recommended that you configure the security group depending on services you are going to serve. You can find the basic recommendations here https://openvz.org/Setting_up_an_iptables_firewall. Click Next: Review Instance Launch#Review your instance launch details. You can go back to edit changes for each section. Click Launch to assign a key pair to your instance and complete the launch process. When the instance is deployed, click the Visit Your Software link. The page with your subscription will be opened. Select [https://console.aws.amazon.com/ec2/v2/ Manage in the AWS console]. In the opened AWS Management Console, open your instances list (using the Instances link Virtual Machines in the left menu) and select the instance.;Click on your OpenVZ VM;(Recommended) After every stop/start, your instance changes Click the external Dashboard and internal IP pair. Thus we recommend to attach special Elastic see VM's PUBLIC VIRTUAL IP to the instance. In the left menu, select Elastic IPs and Allocate New Address or select any existing unassociated address to be allocated to your instance. After Elastic IP attachment, reboot the instance and perform additional actions to configure Plesk (see the Changing IP Address sectionVIP). Please find more information about Elastic IP on Amazon AWS documentation: [http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html Elastic IP Addresses].ADDRESS; To connect your instance please use connection Connect to the VM via SSH as ec2-user with the private key of the Keys Pair you deployed the instance with. For examplessh: # ssh -i <path to private keyusername> ec2user@<elastic or public IPPublic VIP Address> To operate with Virtuozzo OpenVZ you need to enter sudo mode: # sudo -i ==How to install a license to the Virtuozzo 6 BYOL instance== To use Virtuozzo 6 BYOL instance you need to install a license acquired from Odin.Connect to your Virtuozzo 6 instance via SSH. For example: # ssh -i <path to private key> ec2user@<elastic or public IP>Enter sudo mode:

==Configuring NAT on How access your container from the instanceInternet==

If Azure allows to have only two external IPs per VMs network adapter: Virtual IP (VIP) and instance-level public IP address (PIP). Please see more details regarding Azure IPs: http://blogs.msdn.com/b/cloud_solution_architect/archive/2014/11/08/vips-dips-and-pips-in-microsoft-azure.aspxSome Azure Tiers allow to have multiple NICs per VM. More details: https://azure.microsoft.com/en-us/blog/multiple-vm-nics-and-network-virtual-appliances-in-azure/. But you do can not want to attach multiple Elastic IPs to your instance these NICs. Thus in most cases you may also need to configure internal use NAT on to give your Virtuozzo instancecontainers access to external networks. Please follow instructions in this article: https://openvz.org/Using_NAT_for_container_with_private_IPs