To allow customers users to familiarize themselves with improved containers technology of OpenVZ Virtuozzo 7 and to maximize Azure instance utilization along with security and isolation we introduce OpenVZ Virtuozzo 7 image for Microsoft Azure.

OpenVZ Note that:* Virtuozzo 7 image is shipped in one edition: OpenVZ only for version 7.

==Steps to Deployprovisioning Virtuozzo in Azure ==

* Log into the Azure Virtual Machine Marketplace [http://azure.microsoft.com/en-us/marketplace/virtual-machines/Azure Virtual Machine Marketplace], search for the image from Odin, then click the selected product.* Check the product description to verify it suits your needs. Then click the "Create the Virtual Machine" button.* Click Create button again.* Enter all required information like hostname, user and password, choose authentication type, pricing tier and other properties.* Click Create button.* Login to [https://manage.windowsazure.com Azure Management Portal].

Check the product description Login to verify it suits just created VM:* Click Virtual Machines in left menu;* Click on your needs. Then click OpenVZ VM;* Click the "Create Dashboard and see VM's PUBLIC VIRTUAL IP (VIP) ADDRESS;* Connect to the Virtual Machine" button.VM via ssh:

Login == How to Azure Management Portal https://manage.windowsazure.com.access to your container from the Internet ==

Login Azure allows to just created VMhave only two external IPs per VMs network adapter:#Click Virtual Machines in left menu;#Click on your OpenVZ VM;#Click the Dashboard IP (VIP) and see VM's PUBLIC VIRTUAL instance-level public IP address (VIPPIP) ADDRESS;#Connect . More details about IP addresses assignment see in [http://blogs.msdn.com/b/cloud_solution_architect/archive/2014/11/08/vips-dips-and-pips-in-microsoft-azure.aspx Azure documentation]. Some Azure Tiers allow to the have [https://azure.microsoft.com/en-us/blog/multiple-vm-nics-and-network-virtual-appliances-in-azure/ multiple NICs per VM via ssh: # ssh <username>@<Public VIP Address> To operate with OpenVZ ]. But you can not attach multiple IPs to these NICs. Thus in most cases you need to enter sudo mode: # sudo -i[[Using_NAT_for_container_with_private_IPs|use NAT]] to give your containers access to external networks.

Azure allows to have only two external IPs per VMs network adapter[[Category: 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 can not attach multiple IPs to these NICs. Installation]]Thus in most cases you need to use NAT to give your containers access to external networks. Please follow instructions in this article: https[[Category://openvz.org/Using_NAT_for_container_with_private_IPsHOWTO]]