Using Virtuozzo in the Microsoft Azure - Revision history

Kir: rm /Release notes /

2015-09-13T22:33:09Z

rm ‎Release notes

Sergey Bronnikov: mark article as for virtuozzo only

2015-09-11T12:04:58Z

mark article as for virtuozzo only

Sergey Bronnikov: added categories

2015-09-11T11:56:40Z

added categories

Sergey Bronnikov at 11:42, 11 September 2015

2015-09-11T11:42:18Z

Sergey Bronnikov: Sergey Bronnikov moved page How to deploy OpenVZ 7 on the Microsoft Azure to Using Virtuozzo in the Microsoft Azure without leaving a redirect

2015-09-11T11:38:49Z

Sergey Bronnikov moved page How to deploy OpenVZ 7 on the Microsoft Azure to Using Virtuozzo in the Microsoft Azure without leaving a redirect

Sergey Bronnikov: Improve markup

2015-09-11T11:19:01Z

Improve markup

Vporokhov at 22:56, 10 September 2015

2015-09-10T22:56:39Z

Vporokhov at 22:55, 10 September 2015

2015-09-10T22:55:49Z

Vporokhov at 22:54, 10 September 2015

2015-09-10T22:54:52Z

Vporokhov at 22:54, 10 September 2015

2015-09-10T22:54:37Z

@@ Line 1: / Line 1: @@
 {{Virtuozzo}}
 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.
-Virtuozzo 7 image is shipped only for version 7.
+Note that:
 == Steps to provisioning Virtuozzo in Azure ==

← Older revision		Revision as of 12:04, 11 September 2015
Line 1:		Line 1:
		+	{{Virtuozzo}}
		+
	== Release Notes ==		== Release Notes ==

← Older revision		Revision as of 11:56, 11 September 2015
Line 29:		Line 29:

	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). 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.
		+
		+
		+	[[Category: Installation]]
		+	[[Category: HOWTO]]

@@ Line 7: / Line 7: @@
 == Steps to provisioning Virtuozzo in Azure ==
-* 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.
+* 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 Azure Management Portal https://manage.windowsazure.com.
+* Login to [https://manage.windowsazure.com Azure Management Portal].
 Login to just created VM:
@@ Line 28: / Line 28: @@
 == 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 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. 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
+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.

@@ Line 1: / Line 1: @@
-==Release Notes==
+== Release Notes ==
-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.
+Virtuozzo 7 image is shipped only for version 7.
-==Steps to Deploy==
+== Steps to provisioning Virtuozzo in Azure ==
-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.
+* 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.
+Login to just created VM:
-Click Create button again.
+ # ssh <username>@<Public VIP Address>
-Enter all required information like hostname, user and password, choose authentication type, pricing tier and other properties.
+* To operate with OpenVZ you need to enter sudo mode:
   # sudo -i
-==How access your container from the Internet==
+== How to access to your container from the Internet ==
-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
+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 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. 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

← Older revision	Revision as of 11:38, 11 September 2015
(No difference)

← Older revision		Revision as of 22:54, 10 September 2015
Line 2:		Line 2:

	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 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.
		+
	OpenVZ 7 image is shipped in one edition: OpenVZ 7.		OpenVZ 7 image is shipped in one edition: OpenVZ 7.

Using Virtuozzo in the Microsoft Azure - Revision history

Kir: rm /*Release notes */

Sergey Bronnikov: mark article as for virtuozzo only

Sergey Bronnikov: added categories

Sergey Bronnikov at 11:42, 11 September 2015

Sergey Bronnikov: Sergey Bronnikov moved page How to deploy OpenVZ 7 on the Microsoft Azure to Using Virtuozzo in the Microsoft Azure without leaving a redirect

Sergey Bronnikov: Improve markup

Vporokhov at 22:56, 10 September 2015

Vporokhov at 22:55, 10 September 2015

Vporokhov at 22:54, 10 September 2015

Vporokhov at 22:54, 10 September 2015

Kir: rm /Release notes /