Difference between revisions of "Ubuntu Enterprise Cloud"
Jump to navigation
Jump to search
Onnowpurbo (talk | contribs) |
Onnowpurbo (talk | contribs) |
||
Line 1: | Line 1: | ||
− | |||
==Objective== | ==Objective== | ||
Line 12: | Line 11: | ||
==STEP 1: Prerequisites== | ==STEP 1: Prerequisites== | ||
+ | To deploy a minimal cloud infrastructure, you’ll need at least two dedicated systems: | ||
+ | |||
+ | * a front end | ||
+ | * one or more node(s) | ||
+ | |||
+ | The following are recommendations, rather than fixed requirements. However, our experience in developing this documentation indicated the following suggestions. | ||
+ | |||
+ | ===Front End=== | ||
+ | |||
+ | |||
+ | Use the following table for a system that will run one or more of: | ||
+ | |||
+ | * the cloud controller (clc) | ||
+ | * the cluster controller (cc) | ||
+ | * walrus (the S3-like storage service) | ||
+ | * the storage controller (sc) | ||
+ | {| border="1" cellpadding=2 style="border-collapse: collapse" | ||
+ | ! Hardware | ||
+ | ! Minimum | ||
+ | ! Suggested | ||
+ | ! Notes | ||
+ | |- | ||
+ | | CPU | ||
+ | | 1GHz | ||
+ | | 2 x 2GHz | ||
+ | | for an all-in-one front end, it helps to have at least a dual core processor | ||
+ | |- | ||
+ | | Memory | ||
+ | | 2GB | ||
+ | | 4GB | ||
+ | | the Java web front end benefits from lots of available memory | ||
+ | |- | ||
+ | | Disk | ||
+ | | 5400rpm IDE | ||
+ | | 7200rpm SATA | ||
+ | | slower disks will work, but will yield much longer instance startup times | ||
+ | |- | ||
+ | | Disk Space | ||
+ | | 40GB | ||
+ | | 200GB | ||
+ | | 40GB is only enough space for only a single image, cache, etc., Eucalyptus does not like to run out of disk space | ||
+ | |- | ||
+ | | Networking | ||
+ | | 100Mbps | ||
+ | | 1000Mbps | ||
+ | | machine images are hundreds of MB, and need to be copied over the network to nodes | ||
+ | |} | ||
Revision as of 16:47, 1 October 2010
Objective
From this Tutorial you will learn how to install, configure, register and perform several operations on a basic UEC setup that results in a cloud with a one controller "front-end" and one or several node(s) for running Virtual Machine (VM) instances. You will also use examples to help get you started using your own private compute cloud.
Download
- Download iso Ubuntu Server dari
http://www.ubuntu.com/server/get-ubuntu/download
STEP 1: Prerequisites
To deploy a minimal cloud infrastructure, you’ll need at least two dedicated systems:
- a front end
- one or more node(s)
The following are recommendations, rather than fixed requirements. However, our experience in developing this documentation indicated the following suggestions.
Front End
Use the following table for a system that will run one or more of:
- the cloud controller (clc)
- the cluster controller (cc)
- walrus (the S3-like storage service)
- the storage controller (sc)
Hardware | Minimum | Suggested | Notes |
---|---|---|---|
CPU | 1GHz | 2 x 2GHz | for an all-in-one front end, it helps to have at least a dual core processor |
Memory | 2GB | 4GB | the Java web front end benefits from lots of available memory |
Disk | 5400rpm IDE | 7200rpm SATA | slower disks will work, but will yield much longer instance startup times |
Disk Space | 40GB | 200GB | 40GB is only enough space for only a single image, cache, etc., Eucalyptus does not like to run out of disk space |
Networking | 100Mbps | 1000Mbps | machine images are hundreds of MB, and need to be copied over the network to nodes |
Referensi
- http://www.ubuntu.com/cloud/private
- http://www.ubuntu.com/cloud/private/deploy
- https://help.ubuntu.com/community/UEC
- https://help.ubuntu.com/community/UEC/CDInstall