Using Virtuozzo in the Amazon EC2 - Revision history

Vporokhov at 13:40, 25 May 2016

2016-05-25T13:40:52Z

Sergey Bronnikov: Marked this version for translation

2015-12-26T08:37:26Z

Marked this version for translation

Sergey Bronnikov: add 'translate' tags

2015-12-25T22:48:24Z

add 'translate' tags

Sergey Bronnikov: add link to guide provided by Kentaro

2015-11-02T12:19:32Z

add link to guide provided by Kentaro

Sergey Bronnikov: Sergey Bronnikov moved page How to deploy OpenVZ on the Amazon EC2 to Using Virtuozzo in the Amazon EC2

2015-09-22T16:04:22Z

Sergey Bronnikov moved page How to deploy OpenVZ on the Amazon EC2 to Using Virtuozzo in the Amazon EC2

Sergey Bronnikov: Sergey Bronnikov moved page Using Virtuozzo in the Amazon EC2 to How to deploy OpenVZ on the Amazon EC2 without leaving a redirect

2015-09-22T16:04:05Z

Sergey Bronnikov moved page Using Virtuozzo in the Amazon EC2 to How to deploy OpenVZ on the Amazon EC2 without leaving a redirect

Kir: minor rewording and formatting nitpicks

2015-09-13T22:31:17Z

minor rewording and formatting nitpicks

Sergey Bronnikov: mark article as for virtuozzo only

2015-09-11T12:04:40Z

mark article as for virtuozzo only

Sergey Bronnikov: added categories

2015-09-11T11:56:55Z

added categories

Sergey Bronnikov: embed links to text and improve markup

2015-09-11T11:52:44Z

embed links to text and improve markup

Show changes

@@ Line 46: / Line 46: @@
 * 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 in the left menu) and select the instance.
 * (Recommended) After every stop/start, your instance changes the external and internal IP pair. Thus we recommend to attach special Elastic 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 section). 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].
-* To connect your instance please use connection via SSH as ec2-user with the private key of the Keys Pair you deployed the instance with. For example:
+* To connect your instance please use connection via SSH as ec2user with the private key of the Keys Pair you deployed the instance with. For example:
   # ssh -i <path to private key> ec2user@<elastic or public IP>

@@ Line 2: / Line 2: @@
 <translate>
 To allow customers to familiarize themselves with improved containers technology of Virtuozzo and to maximize AWS instance utilization along with security and isolation we introduce Virtuozzo image for Amazon EC2.
 Please note that:
 * Virtuozzo only supports containers then deployed on Amazon EC2.
 * Virtuozzo 7 image is shipped for only one version: Virtuozzo 7.
-== Steps to provisioning ==
+== Steps to provisioning == <!--T:3-->
 * Log into the [https://aws.amazon.com/marketplace AWS Marketplace], search for the AMI from Odin as the publisher, then click the selected product.
 * Check the product description to verify it suits your needs. Then click the "Continue" 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].
-=== 1-Click Launch (predefined settings) ===
+=== 1-Click Launch (predefined settings) === <!--T:5-->
 * 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].
@@ Line 24: / Line 28: @@
 To change the disk storage after deployment, check the Amazon AWS documentation: [http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-expand-volume.html Expanding the Storage Space of a Volume].
-=== Manual Launch with EC2 console ===
+=== Manual Launch with EC2 console === <!--T:7-->
 Adjust additional settings such as disk space before launch.
 * Click on the Manual Launch tab.
 * Click the Launch with EC2 Console button in the Region the instance is to be deployed.
@@ Line 44: / Line 50: @@
   # ssh -i <path to private key> ec2user@<elastic or public IP>
 * To operate with OpenVZ you need to enter sudo mode:
-  # sudo -i
+  <!--T:11-->
-== Configure the external IP address for the container ==
+== Configure the external IP address for the container == <!--T:12-->
 To access to your container through the Internet you can attach additional Private IPs and Elastic IPs to the instance and then attach every Private IP to the specific container.
 Please review this article to learn how to assign additional Elastic IPs to the instance http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/MultipleIP.html. If you need additional information on IP addressing in Amazon EC2 please see this article http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-instance-addressing.html
 Login to the Amazon EC2 Management Console.
 Assign new Private IP to your Instance:
 * Choose your instance;
 * Click Actions > Networking > Manage Private IP Addresses;
@@ Line 63: / Line 76: @@
 * Click Yes, Update.
 Assign new Elastic IP to corresponding Private IP of your instance:
 * Choose Elastic IP section in the menu;
 * Click Allocate New Addresses;
@@ Line 72: / Line 87: @@
 * Click Associate.
 Connect to your OpenVZ instance via SSH.
 Create example container:
-  # prlctl create 100700 --vmtype ct
+  <!--T:22-->
 Assign Private IP and DNS server to the container:
-  # prlctl set 100700 --ipadd <Private IP address>/24
+  <!--T:24-->
   # prlctl set 100700 --nameserver 8.8.8.8
 Start the container:
-  # prlctl start 100700
+  <!--T:26-->
 Enter the container and set root password:
-  # prlctl enter 100700
+  <!--T:28-->
   # passwd
 Connect to the container via SSH:
-  # ssh root@<Elastic IP Address>
+  <!--T:30-->
-== Configure NAT on the instance ==
+== Configure NAT on the instance == <!--T:31-->
 If you do not want to attach multiple Elastic IPs to your instance you may also to [[Using_NAT_for_container_with_private_IPs|configure internal NAT]] on your OpenVZ instance.
-== See also ==
+== See also == <!--T:33-->
 * [http://www.slideshare.net/kentaroebisawa/quick-start-guide-using-virtuozzo-7-on-aws-ec2 Quick Start Guide using Virtuozzo 7 (β) on AWS EC2]
 </translate>

@@ Line 1: / Line 1: @@
 {{Virtuozzo}}
 To allow customers to familiarize themselves with improved containers technology of Virtuozzo and to maximize AWS instance utilization along with security and isolation we introduce Virtuozzo image for Amazon EC2.
@@ Line 102: / Line 103: @@
 * [http://www.slideshare.net/kentaroebisawa/quick-start-guide-using-virtuozzo-7-on-aws-ec2 Quick Start Guide using Virtuozzo 7 (β) on AWS EC2]
 [[Category: Installation]]
 [[Category: HOWTO]]

@@ Line 98: / Line 98: @@
 If you do not want to attach multiple Elastic IPs to your instance you may also to [[Using_NAT_for_container_with_private_IPs|configure internal NAT]] on your OpenVZ instance.
 [[Category: Installation]]
 [[Category: HOWTO]]

@@ Line 1: / Line 1: @@
 {{Virtuozzo}}
 To allow customers to familiarize themselves with improved containers technology of Virtuozzo and to maximize AWS instance utilization along with security and isolation we introduce Virtuozzo image for Amazon EC2.
-* Virtuozzo supports only container technology then deployed on Amazon EC2.
+Please note that:
 * Virtuozzo 7 image is shipped for only one version: Virtuozzo 7.
@@ Line 13: / Line 12: @@
 * Check the product description to verify it suits your needs. Then click the "Continue" 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].
 === 1-Click Launch (predefined settings) ===

← Older revision	Revision as of 16:04, 22 September 2015
(No difference)

← 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 98:		Line 98:

	If you do not want to attach multiple Elastic IPs to your instance you may also to [[Using_NAT_for_container_with_private_IPs\|configure internal NAT]] on your OpenVZ instance.		If you do not want to attach multiple Elastic IPs to your instance you may also to [[Using_NAT_for_container_with_private_IPs\|configure internal NAT]] on your OpenVZ instance.
		+
		+	[[Category: Installation]]
		+	[[Category: HOWTO]]