Editing Using Virtuozzo in the Microsoft Azure
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
| − | + | ==Release Notes== | |
| − | To allow | + | 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. | |
| − | |||
| − | == Steps to | + | ==Steps to Deploy== |
| − | + | 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 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> | # ssh <username>@<Public VIP Address> | ||
| − | + | To operate with OpenVZ you need to enter sudo mode: | |
| − | |||
# sudo -i | # sudo -i | ||
| − | == How | + | ==How access 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). | + | 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 |
| + | 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 | |
| − | |||