UEC Сравнение версий

Различия

Здесь показаны различия между двумя версиями данной страницы.

Ссылка на это сравнение

Предыдущая версия справа и слева Предыдущая версия
Следующая версия
Предыдущая версия
wiki:руководство_по_ubuntu_server:виртуализация:uec [2012/09/24 18:14]
[Запуск образа]
wiki:руководство_по_ubuntu_server:виртуализация:uec [2012/09/28 20:29] (текущий)
[Обзор]
Строка 7: Строка 7:
  
 =====UEC===== =====UEC=====
- 
-    Overview 
-    Prerequisites 
-    Installing the Cloud/​Cluster/​Storage/​Walrus Front End Server 
-    Installing the Node Controller(s) 
-    Register the Node(s) 
-    Obtain Credentials 
-    Install an Image from the Store 
-    Run an Image 
-    More Information 
-    References 
  
 ====Обзор==== ====Обзор====
  
-UEC (Ubuntu Enterprise Cloud) ​is now depracated in favour of UC (Ubuntu Cloud). ​The former is based on Eucalyptus ​and the latter is based on Openstack. ​This section of the guide will be removed in future iterations.+<note important>​**UEC** (Ubuntu Enterprise Cloud - корпоративное облако Ubuntuна данный момент считается устаревшим в пользу ​UC (Ubuntu Cloud - Облако Ubuntu). Первое основано на Eucalyptus, а второе - на Openstack. ​Эта секция руководства будет удалена в дальнейшем.</​note>​ 
  
 This tutorial covers UEC installation from the Ubuntu 12.04 LTS Server Edition CD, and assumes a basic network topology, with a single system serving as the "​all-in-one controller",​ and one or more nodes attached. This tutorial covers UEC installation from the Ubuntu 12.04 LTS Server Edition CD, and assumes a basic network topology, with a single system serving as the "​all-in-one controller",​ and one or more nodes attached.
Строка 51: Строка 41:
 ==Требования к внешнему интерфейсу UEC== ==Требования к внешнему интерфейсу UEC==
  
-Hardware +Hardware ​ ​^ ​Minimum ​ ​^ ​Suggested ​ ​^ ​Notes  ^ 
-  +CPU  ​| ​1 GHz  ​| ​2 x 2 GHz  ​| ​For an all-in-one front end, it helps to have at least a dual core processor. ​ | 
- +Memory ​ ​| ​2 GB  ​| ​4 GB  ​| ​The Java web front end benefits from lots of available memory. ​ | 
-Minimum +Disk  ​| ​5400 RPM IDE  ​| ​7200 RPM SATA  ​| ​Slower disks will work, but will yield much longer instance startup times. ​ | 
-  +Disk Space  ​| ​40 GB  ​| ​200 GB  ​| ​40GB is only enough space for only a single image, cache, etc., Eucalyptus does not like to run out of disk space. ​ | 
- +Networking ​ ​| ​100 Mbps  ​| ​1000 Mbps  ​| ​Machine images are hundreds of MB, and need to be copied over the network to nodes. ​ |
-Suggested +
-  +
- +
-Notes +
- +
-CPU +
-  +
- +
-1 GHz +
-  +
- +
-2 x 2 GHz +
-  +
- +
-For an all-in-one front end, it helps to have at least a dual core processor. +
- +
-Memory +
-  +
- +
-2 GB +
-  +
- +
-4 GB +
-  +
- +
-The Java web front end benefits from lots of available memory. +
- +
-Disk +
-  +
- +
-5400 RPM IDE +
-  +
- +
-7200 RPM SATA +
-  +
- +
-Slower disks will work, but will yield much longer instance startup times. +
- +
-Disk Space +
-  +
- +
-40 GB +
-  +
- +
-200 GB +
-  +
- +
-40GB is only enough space for only a single image, cache, etc., Eucalyptus does not like to run out of disk space. +
- +
-Networking +
-  +
- +
-100 Mbps +
-  +
- +
-1000 Mbps +
-  +
- +
-Machine images are hundreds of MB, and need to be copied over the network to nodes.+
  
 ===Требования к узлу=== ===Требования к узлу===
Строка 125: Строка 56:
 ==Требования к узлу UEC== ==Требования к узлу UEC==
  
-Hardware +Hardware ​ ​^ ​Minimum ​ ​^ ​Suggested ​ ​^ ​Notes  ^ 
-  +CPU  ​| ​VT Extensions ​ ​| ​VT, 64-bit, Multicore ​ ​| ​64-bit can run both i386, and amd64 instances; by default, Eucalyptus will only run 1 VM per CPU core on a Node.  | 
- +Memory ​ ​| ​1 GB  ​| ​4 GB  ​| ​Additional memory means more, and larger guests. ​ | 
-Minimum +Disk  ​| ​5400 RPM IDE  ​| ​7200 RPM SATA or SCSI  ​| ​Eucalyptus nodes are disk-intensive;​ I/O wait will likely be the performance bottleneck. ​ | 
-  +Disk Space  ​| ​40 GB  ​| ​100 GB  ​| ​Images will be cached locally, Eucalyptus does not like to run out of disk space. ​ | 
- +Networking ​ ​| ​100 Mbps  ​| ​1000 Mbps  ​| ​Machine images are hundreds of MB, and need to be copied over the network to nodes. ​ |
-Suggested +
-  +
- +
-Notes +
- +
-CPU +
-  +
- +
-VT Extensions +
-  +
- +
-VT, 64-bit, Multicore +
-  +
- +
-64-bit can run both i386, and amd64 instances; by default, Eucalyptus will only run 1 VM per CPU core on a Node. +
- +
-Memory +
-  +
- +
-1 GB +
-  +
- +
-4 GB +
-  +
- +
-Additional memory means more, and larger guests. +
- +
-Disk +
-  +
- +
-5400 RPM IDE +
-  +
- +
-7200 RPM SATA or SCSI +
-  +
- +
-Eucalyptus nodes are disk-intensive;​ I/O wait will likely be the performance bottleneck. +
- +
-Disk Space +
-  +
- +
-40 GB +
-  +
- +
-100 GB +
-  +
- +
-Images will be cached locally, Eucalyptus does not like to run out of disk space. +
- +
-Networking +
-  +
- +
-100 Mbps +
-  +
- +
-1000 Mbps +
-  +
- +
-Machine images are hundreds of MB, and need to be copied over the network to nodes.+
  
 ====Установка сервера внешнего интерфейса для облака/​кластера/​хранилища/​Walrus==== ====Установка сервера внешнего интерфейса для облака/​кластера/​хранилища/​Walrus====
Строка 481: Строка 353:
 <​code>​ <​code>​
 #!/bin/sh #!/bin/sh
-ech +echo ========== Hello World: $(date) ==========
-+
- ========== Hello World: $(date) ==========+
 echo "I have been up for $(cut -d\  -f 1 < /​proc/​uptime) sec" echo "I have been up for $(cut -d\  -f 1 < /​proc/​uptime) sec"
 </​code>​ </​code>​
Строка 497: Строка 367:
 ========== Hello World: Mon Mar 29 18:05:05 UTC 2010 ========== ========== Hello World: Mon Mar 29 18:05:05 UTC 2010 ==========
 I have been up for 28.26 sec I have been up for 28.26 sec
 +</​code>​
 Your output may vary. Your output may vary.
  
Строка 505: Строка 375:
  
 For example, create a text file named cloud-config.txt containing: For example, create a text file named cloud-config.txt containing:
 +<​code>​
 #​cloud-config #​cloud-config
 apt_upgrade:​ true apt_upgrade:​ true
Строка 518: Строка 388:
 - echo ======= Hello World ===== - echo ======= Hello World =====
 - echo "I have been up for $(cut -d\  -f 1 < /​proc/​uptime) sec" - echo "I have been up for $(cut -d\  -f 1 < /​proc/​uptime) sec"
 +</​code>​
  
 Create a new instance: Create a new instance: