Difference between revisions of "Using Virtuozzo in the Microsoft Azure"

From OpenVZ Virtuozzo Containers Wiki
Jump to: navigation, search
m (rm →‎Release notes)
 
(8 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
==Release Notes==
+
{{Virtuozzo}}
  
−
To allow customers to familiarize themselves with improved containers technology of OpenVZ 7 and to maximize Azure instance utilization along with security and isolation we introduce OpenVZ 7 image for Microsoft Azure.
+
To allow users to familiarize themselves with improved containers technology of Virtuozzo 7 and to maximize Azure instance utilization along with security and isolation we introduce Virtuozzo 7 image for Microsoft Azure.  
−
OpenVZ 7 image is shipped in one edition: OpenVZ 7.
 
  
−
==Steps to Deploy==
+
Note that:
 +
* Virtuozzo 7 image is shipped only for version 7.
 +
 
 +
== Steps to provisioning Virtuozzo in Azure ==
 +
 
 +
* Log into the [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].
  
−
Log into the Azure Virtual Machine Marketplace http://azure.microsoft.com/en-us/marketplace/virtual-machines/, 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 Azure Management Portal https://manage.windowsazure.com.
 
 
Login to just created VM:
 
Login to just created VM:
−
Click Virtual Machines in left menu;
+
* Click Virtual Machines in left menu;
−
Click on your OpenVZ VM;
+
* Click on your OpenVZ VM;
−
Click the Dashboard and see VM's PUBLIC VIRTUAL IP (VIP) ADDRESS;
+
* Click the Dashboard and see VM's PUBLIC VIRTUAL IP (VIP) ADDRESS;
−
Connect to the VM via ssh:
+
* Connect to the VM via ssh:
 +
 
 
  # ssh <username>@<Public VIP Address>
 
  # ssh <username>@<Public VIP Address>
−
To operate with OpenVZ you need to enter sudo mode:
+
 
 +
* To operate with OpenVZ you need to enter sudo mode:
 +
 
 
  # sudo -i
 
  # sudo -i
  
−
==How access your container from the Internet==
+
== How to access to your container from the Internet ==
 +
 
 +
Azure allows to have only two external IPs per VMs network adapter: Virtual IP (VIP) and instance-level public IP address (PIP). 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 have [https://azure.microsoft.com/en-us/blog/multiple-vm-nics-and-network-virtual-appliances-in-azure/ multiple NICs per VM]. But you can not attach multiple IPs to these NICs. Thus in most cases you need to [[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: 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.aspx
+
[[Category: Installation]]
−
Some 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.
+
[[Category: HOWTO]]
−
Thus in most cases you need to use NAT to give your containers access to external networks. Please follow instructions in this article: https://openvz.org/Using_NAT_for_container_with_private_IPs
 

Latest revision as of 22:33, 13 September 2015

Openvz-logo.png This article is for Virtuozzo 7 only.

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

Note that:

  • Virtuozzo 7 image is shipped only for version 7.

Steps to provisioning Virtuozzo in Azure[edit]

  • Log into the 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 Azure Management Portal.

Login to just created VM:

  • Click Virtual Machines in left menu;
  • Click on your OpenVZ VM;
  • Click the Dashboard and see VM's PUBLIC VIRTUAL IP (VIP) ADDRESS;
  • Connect to the VM via ssh:
# ssh <username>@<Public VIP Address>
  • To operate with OpenVZ you need to enter sudo mode:
# sudo -i

How to access to your container from the Internet[edit]

Azure allows to have only two external IPs per VMs network adapter: Virtual IP (VIP) and instance-level public IP address (PIP). More details about IP addresses assignment see in Azure documentation. Some Azure Tiers allow to have multiple NICs per VM. But you can not attach multiple IPs to these NICs. Thus in most cases you need to use NAT to give your containers access to external networks.

Retrieved from "https://wiki.openvz.org/index.php?title=Using_Virtuozzo_in_the_Microsoft_Azure&oldid=17666"