{"id":265,"date":"2011-02-17T04:57:38","date_gmt":"2011-02-17T04:57:38","guid":{"rendered":"http:\/\/gigihfordanama.wordpress.com\/?p=265"},"modified":"2012-08-08T00:13:16","modified_gmt":"2012-08-08T00:13:16","slug":"develop-your-own-cloud-computing-infrastucture-with-ubuntu-enterprise-cloud-uec","status":"publish","type":"post","link":"https:\/\/dosen.unila.ac.id\/gigih\/2011\/02\/17\/develop-your-own-cloud-computing-infrastucture-with-ubuntu-enterprise-cloud-uec\/","title":{"rendered":"Develop your Own Cloud Computing Infrastructure with Ubuntu Enterprise Cloud (UEC) ,Eucalyptus,Walrus"},"content":{"rendered":"<p style=\"text-align:center\">Diiiceritaken bahwasanya hari ini\u00a0 mencoba implementasi Cloud Computing menggunakan software terbaru varian ubuntu yakni <strong>Ubuntu Enterprise Cloud (UEC). <\/strong>dari referensi yang sudah saya baca konsep dasar si Cloud Computing ini adalah berbagi resource Hardware dalam jaringan sehingga pemanfaatan infrastruktur jaringan akan semakin maksimal, Topology <strong>UEC<\/strong> biasanya seperti gambar dibawah. <a href=\"http:\/\/www.ibm.com\/developerworks\/opensource\/library\/os-cloud-virtual1\/fig4.gif\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone\" src=\"http:\/\/www.ibm.com\/developerworks\/opensource\/library\/os-cloud-virtual1\/fig4.gif\" alt=\"\" width=\"580\" height=\"350\" \/><\/a><\/p>\n<p style=\"text-align:left\">rencananya akan saya gunakan beberapa PC\u00a0 iddle untuk diinstall sebagai Node, sedangkan untuk Cloud Controllernya akan saya gunakan Server Acer Altos ex server Proxy. Saat ini sudah terinstall Cloud Controller menggunakan Ubuntu 10.10 release dialamat <a href=\"https:\/\/mirror.unila.ac.id:8443\">https:\/\/mirror.unila.ac.id:8443<\/a> ,\u00a0 on progress lagi menyiapkan Pc untuk digunakan sebagai Node.\u00a0 Detail instalasi bisa dibaca selengkap<\/p>\n<p><strong><!--more--><\/strong><\/p>\n<p><a href=\"https:\/\/help.ubuntu.com\/community\/UEC\/CDInstall\">Link detail dari alamat berikut : https:\/\/help.ubuntu.com\/community\/UEC\/CDInstall<\/a><\/p>\n<h2>Overview<\/h2>\n<p><span class=\"anchor\"> <\/span><span class=\"anchor\"> <\/span><\/p>\n<p class=\"line874\">This tutorial covers UEC installation from the Ubuntu 10.10 Server Edition CD, and assumes a basic network topology, with a single system serving as the &#8220;all-in-one controller&#8221;, and one or more nodes attached. <span class=\"anchor\"> <\/span><span class=\"anchor\"> <\/span><\/p>\n<h2 id=\"Objective\">Objective<\/h2>\n<p><span class=\"anchor\"> <\/span><span class=\"anchor\"> <\/span><\/p>\n<p class=\"line874\">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 &#8220;front-end&#8221; 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. <span class=\"anchor\"> <\/span><span class=\"anchor\"> <\/span><\/p>\n<h2 id=\"Tutorial\">Tutorial<\/h2>\n<p><span class=\"anchor\"> <\/span><\/p>\n<h3 id=\"STEP 1: Prerequisites\">STEP 1: Prerequisites<\/h3>\n<p><span class=\"anchor\"> <\/span><span class=\"anchor\"> <\/span><\/p>\n<p class=\"line874\">To deploy a minimal cloud infrastructure, you\u2019ll need at least two dedicated systems: <span class=\"anchor\"> <\/span><\/p>\n<ul>\n<li>a front end <span class=\"anchor\"> <\/span><\/li>\n<li>one or more node(s)<span class=\"anchor\"> <\/span><span class=\"anchor\"> <\/span><\/li>\n<\/ul>\n<div dir=\"ltr\" lang=\"en\">\n<p><span class=\"anchor\"> <\/span><\/p>\n<p><span class=\"anchor\"> <\/span><\/p>\n<p class=\"line874\">The following are recommendations, rather than fixed requirements.  However, our experience in developing this documentation indicated the following suggestions.<span class=\"anchor\"> <\/span><span class=\"anchor\"> <\/span><\/p>\n<h4 id=\"Front End\">Front End<\/h4>\n<p><span class=\"anchor\"> <\/span><span class=\"anchor\"> <\/span><\/p>\n<p class=\"line874\">Use the following table for a system that will run one or more of: <span class=\"anchor\"> <\/span><\/p>\n<ul>\n<li>the cloud controller (clc) <span class=\"anchor\"> <\/span><\/li>\n<li>the cluster controller (cc) <span class=\"anchor\"> <\/span><\/li>\n<li>walrus (the S3-like storage service) <span class=\"anchor\"> <\/span><\/li>\n<li>the storage controller (sc) <span class=\"anchor\"> <\/span><span class=\"anchor\"> <\/span><\/li>\n<\/ul>\n<div>\n<table>\n<tbody>\n<tr>\n<td>\n<p class=\"line862\"><strong>Hardware<\/strong><\/p>\n<\/td>\n<td>\n<p class=\"line862\"><strong>Minimum<\/strong><\/p>\n<\/td>\n<td>\n<p class=\"line862\"><strong>Suggested<\/strong><\/p>\n<\/td>\n<td>\n<p class=\"line862\"><strong>Notes<\/strong><\/p>\n<\/td>\n<\/tr>\n<tr>\n<td><span class=\"anchor\"> <\/span>&nbsp;<\/p>\n<p class=\"line862\">CPU<\/p>\n<\/td>\n<td>\n<p class=\"line862\">1GHz<\/p>\n<\/td>\n<td>\n<p class=\"line862\">2 x 2GHz<\/p>\n<\/td>\n<td>\n<p class=\"line862\">for an all-in-one front end, it helps to have at least a dual core processor<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td><span class=\"anchor\"> <\/span>&nbsp;<\/p>\n<p class=\"line862\">Memory<\/p>\n<\/td>\n<td>\n<p class=\"line862\">2GB<\/p>\n<\/td>\n<td>\n<p class=\"line862\">4GB<\/p>\n<\/td>\n<td>\n<p class=\"line862\">the Java web front end benefits from lots of available memory<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td><span class=\"anchor\"> <\/span>&nbsp;<\/p>\n<p class=\"line862\">Disk<\/p>\n<\/td>\n<td>\n<p class=\"line862\">5400rpm IDE<\/p>\n<\/td>\n<td>\n<p class=\"line862\">7200rpm SATA<\/p>\n<\/td>\n<td>\n<p class=\"line862\">slower disks will work, but will yield much longer instance startup times<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td><span class=\"anchor\"> <\/span>&nbsp;<\/p>\n<p class=\"line862\">Disk Space<\/p>\n<\/td>\n<td>\n<p class=\"line862\">40GB<\/p>\n<\/td>\n<td>\n<p class=\"line862\">200GB<\/p>\n<\/td>\n<td>\n<p class=\"line862\">40GB is only enough space for only a single image, cache, etc., Eucalyptus does <em>not<\/em> like to run out of disk space<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td><span class=\"anchor\"> <\/span>&nbsp;<\/p>\n<p class=\"line862\">Networking<\/p>\n<\/td>\n<td>\n<p class=\"line862\">100Mbps<\/p>\n<\/td>\n<td>\n<p class=\"line862\">1000Mbps<\/p>\n<\/td>\n<td>\n<p class=\"line862\">machine images are hundreds of MB, and need to be copied over the network to nodes<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p><span class=\"anchor\"> <\/span><span class=\"anchor\"> <\/span><\/p>\n<h4 id=\"Node(s)\">Node(s)<\/h4>\n<p><span class=\"anchor\"> <\/span><span class=\"anchor\"> <\/span><\/p>\n<p class=\"line874\">The other system(s) are nodes, which will run: <span class=\"anchor\"> <\/span><\/p>\n<ul>\n<li>the node controller (nc) <span class=\"anchor\"> <\/span><span class=\"anchor\"> <\/span><\/li>\n<\/ul>\n<p class=\"line874\">These systems will actually run the instances.  You will need one or more systems with: <span class=\"anchor\"> <\/span><\/p>\n<div>\n<table>\n<tbody>\n<tr>\n<td>\n<p class=\"line862\"><strong>Hardware<\/strong><\/p>\n<\/td>\n<td>\n<p class=\"line862\"><strong>Minimum<\/strong><\/p>\n<\/td>\n<td>\n<p class=\"line862\"><strong>Suggested<\/strong><\/p>\n<\/td>\n<td>\n<p class=\"line862\"><strong>Notes<\/strong><\/p>\n<\/td>\n<\/tr>\n<tr>\n<td><span class=\"anchor\"> <\/span>&nbsp;<\/p>\n<p class=\"line862\">CPU<\/p>\n<\/td>\n<td>\n<p class=\"line862\">VT extensions<\/p>\n<\/td>\n<td>\n<p class=\"line862\">VT, 64-bit, Multicore<\/p>\n<\/td>\n<td>\n<p class=\"line862\">64-bit can run both i386, and amd64 instances; by default, Eucalyptus will only run 1 VM per CPU core on a Node<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td><span class=\"anchor\"> <\/span>&nbsp;<\/p>\n<p class=\"line862\">Memory<\/p>\n<\/td>\n<td>\n<p class=\"line862\">1GB<\/p>\n<\/td>\n<td>\n<p class=\"line862\">4GB<\/p>\n<\/td>\n<td>\n<p class=\"line862\">additional memory means more, and larger guests<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td><span class=\"anchor\"> <\/span>&nbsp;<\/p>\n<p class=\"line862\">Disk<\/p>\n<\/td>\n<td>\n<p class=\"line862\">5400rpm IDE<\/p>\n<\/td>\n<td>\n<p class=\"line862\">7200rpm SATA or SCSI<\/p>\n<\/td>\n<td>\n<p class=\"line862\">Eucalyptus nodes are disk-intensive; I\/O wait will likely be the performance bottleneck<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td><span class=\"anchor\"> <\/span>&nbsp;<\/p>\n<p class=\"line862\">Disk Space<\/p>\n<\/td>\n<td>\n<p class=\"line862\">40GB<\/p>\n<\/td>\n<td>\n<p class=\"line862\">100GB<\/p>\n<\/td>\n<td>\n<p class=\"line862\">images will be cached locally, Eucalyptus does <em>not<\/em> like to run out of disk space<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td><span class=\"anchor\"> <\/span>&nbsp;<\/p>\n<p class=\"line862\">Networking<\/p>\n<\/td>\n<td>\n<p class=\"line862\">100Mbps<\/p>\n<\/td>\n<td>\n<p class=\"line862\">1000Mbps<\/p>\n<\/td>\n<td>\n<p class=\"line862\">machine images are hundreds of MB, and need to be copied over the network to nodes<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p><span class=\"anchor\"> <\/span><span class=\"anchor\"> <\/span><\/p>\n<\/div>\n<p><span class=\"anchor\"> <\/span><span class=\"anchor\"> <\/span><\/p>\n<p class=\"line867\">&nbsp;<\/p>\n<h3 id=\"STEP 2: Install the Cloud\/Cluster\/Storage\/Walrus Front End Server\">STEP 2: Install the Cloud\/Cluster\/Storage\/Walrus Front End Server<\/h3>\n<p><span class=\"anchor\"> <\/span><span class=\"anchor\"> <\/span><\/p>\n<ol type=\"1\">\n<li>Download the 10.04 Server ISO <span class=\"anchor\"> <\/span><\/li>\n<li>\n<p class=\"line862\">When you boot, select \u201cInstall Ubuntu Enterprise Cloud\u201d.<\/p>\n<p><img decoding=\"async\" class=\"attachment\" src=\"https:\/\/help.ubuntu.com\/community\/UEC\/CDInstall?action=AttachFile&amp;do=get&amp;target=bootscreen.png\" alt=\"bootscreen.png\" \/> <span class=\"anchor\"> <\/span><\/li>\n<li>\n<p class=\"line862\">The installer will detect if any other Eucalyptus components are present.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"attachment\" src=\"https:\/\/help.ubuntu.com\/community\/UEC\/CDInstall?action=AttachFile&amp;do=get&amp;target=uec1.png\" alt=\"uec1.png\" width=\"640\" height=\"480\" \/> <span class=\"anchor\"> <\/span><\/li>\n<li>\n<p class=\"line862\">You can then choose which components to install, based on your chosen <a href=\"\/community\/UEC\/Topologies\">topology<\/a>.<\/p>\n<p><img decoding=\"async\" class=\"attachment\" src=\"https:\/\/help.ubuntu.com\/community\/UEC\/CDInstall?action=AttachFile&amp;do=get&amp;target=uec2.png\" alt=\"uec2.png\" \/> <span class=\"anchor\"> <\/span><\/li>\n<li>It will ask two other cloud-specific questions during the course of the install: <span class=\"anchor\"> <\/span>\n<ol type=\"1\">\n<li>\n<p class=\"line862\">Name of your cluster, e.g. <em>cluster1<\/em>.<\/p>\n<p><img decoding=\"async\" class=\"attachment\" src=\"https:\/\/help.ubuntu.com\/community\/UEC\/CDInstall?action=AttachFile&amp;do=get&amp;target=uec3.png\" alt=\"uec3.png\" \/> <span class=\"anchor\"> <\/span><\/li>\n<li>\n<p class=\"line862\">A range of public IP addresses on the LAN that the cloud can allocate to instances, e.g. <em>192.168.1.200-192.168.1.249<\/em>.<\/p>\n<p><img decoding=\"async\" class=\"attachment\" src=\"https:\/\/help.ubuntu.com\/community\/UEC\/CDInstall?action=AttachFile&amp;do=get&amp;target=uec4.png\" alt=\"uec4.png\" \/> <span class=\"anchor\"> <\/span><span class=\"anchor\"> <\/span><\/li>\n<\/ol>\n<\/li>\n<\/ol>\n<p class=\"line867\">&nbsp;<\/p>\n<h3 id=\"STEP 3: Install the Node Controller(s)\">STEP 3: Install the Node Controller(s)<\/h3>\n<p><span class=\"anchor\"> <\/span><span class=\"anchor\"> <\/span><\/p>\n<p class=\"line874\">The node controller install is even simpler. Just make sure that you are connected to the network on which the cloud\/cluster controller is already running.  <span class=\"anchor\"> <\/span><span class=\"anchor\"> <\/span><\/p>\n<ol type=\"1\">\n<li>Boot from the same ISO on the node(s) <span class=\"anchor\"> <\/span><\/li>\n<li>Select \u201cInstall Ubuntu Enterprise Cloud\u201d <span class=\"anchor\"> <\/span><\/li>\n<li>It should detect the Cluster and preselect \u201cNode\u201d install for you <span class=\"anchor\"> <\/span><\/li>\n<li>Confirm the partitioning scheme <span class=\"anchor\"> <\/span><\/li>\n<li>The rest of the installation should proceed uninterrupted; complete the installation and reboot the node<span class=\"anchor\"> <\/span><span class=\"anchor\"> <\/span><\/li>\n<\/ol>\n<h3 id=\"STEP 4: Register the Node(s)\">STEP 4: Register the Node(s)<\/h3>\n<div dir=\"ltr\" lang=\"en\">\n<div dir=\"ltr\" lang=\"en\">\n<p>As of Ubuntu 10.04 LTS, all component registration should be automatic, assuming:<\/p>\n<div dir=\"ltr\" lang=\"en\">\n<p><span class=\"anchor\"> <\/span><\/p>\n<ol type=\"a\">\n<li>Public SSH keys have been exchanged properly <span class=\"anchor\"> <\/span><\/li>\n<li>The services are configured properly <span class=\"anchor\"> <\/span><\/li>\n<li>The services are publishing their existence <span class=\"anchor\"> <\/span><\/li>\n<li>The appropriate uec-component-listener is running <span class=\"anchor\"> <\/span><\/li>\n<li>Verify Registration. <span class=\"anchor\"> <\/span><span class=\"anchor\"> <\/span><\/li>\n<\/ol>\n<p class=\"line862\">Steps a to e should only be required if you&#8217;re using the <a href=\"\/community\/UEC\/PackageInstall\">UEC\/PackageInstall<\/a> method.  Otherwise, if you are following the <a href=\"\/community\/UEC\/CDInstall\">UEC\/CDInstall<\/a> method, these steps should already be completed automatically for you, and therefore you can skip a to e. <span class=\"anchor\"> <\/span><span class=\"anchor\"> <\/span><\/p>\n<p class=\"line874\"><strong>a.<span class=\"anchor\"> <\/span>Exchange Public SSH Keys<\/strong><\/p>\n<p>The Cloud Controller&#8217;s <em>eucalyptus<\/em> user needs to have SSH access to the Walrus Controller, Cluster Controller, and Storage Controller as the <em>eucalyptus<\/em> user.<\/p>\n<div dir=\"ltr\" lang=\"en\">\n<p><span class=\"anchor\"> <\/span><\/p>\n<p class=\"line862\">Install the Cloud Controller&#8217;s <em>eucalyptus<\/em> user&#8217;s public ssh key by:<\/p>\n<ul>\n<li>\n<p class=\"line862\">On the target controller, temporarily set a password for the <em>eucalyptus<\/em> user:<\/p>\n<pre>sudo passwd eucalyptus<\/pre>\n<p>Then, on the Cloud Controller:<\/p>\n<pre>sudo -u eucalyptus ssh-copy-id -i \/var\/lib\/eucalyptus\/.ssh\/id_rsa.pub eucalyptus@&lt;IP_OF_NODE&gt;<\/pre>\n<\/li>\n<li>\n<p class=\"line862\">You can now remove the password of the <em>eucalyptus<\/em> account on the target controller, if you wish:<\/p>\n<\/li>\n<\/ul>\n<ul>\n<li>\n<pre>sudo passwd -d eucalyptus<\/pre>\n<p>&nbsp;<\/li>\n<\/ul>\n<\/div>\n<p class=\"line874\"><strong>b. Configure the Services<\/strong><\/p>\n<p class=\"line862\">On the <strong>Cloud Controller<\/strong>:<\/p>\n<ul>\n<li>\n<p class=\"line862\">For the <strong>Cluster Controller<\/strong> Registration:<\/p>\n<ul>\n<li>\n<p class=\"line862\">Define the shell variable <strong>CC_NAME<\/strong> in <tt>\/etc\/eucalyptus\/eucalyptus-cc.conf<\/tt><\/p>\n<\/li>\n<li>\n<p class=\"line862\">Define the shell variable <strong>CC_IP_ADDR<\/strong> in <tt>\/etc\/eucalyptus\/eucalyptus-ipaddr.conf<\/tt>, as a space separated list of one or more IP addresses.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n<li>\n<p class=\"line862\">For the <strong>Walrus Controller<\/strong> Registration:<\/p>\n<ul>\n<li>\n<p class=\"line862\">Define the shell variable <strong>WALRUS_IP_ADDR<\/strong> in <tt>\/etc\/eucalyptus\/eucalyptus-ipaddr.conf<\/tt>, as a single IP address.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p class=\"line862\">On the <strong>Cluster Controller<\/strong>:<\/p>\n<ul>\n<li>\n<p class=\"line862\">For <strong>Storage Controller<\/strong> Registration:<\/p>\n<ul>\n<li>\n<p class=\"line862\">Define the cluster name in the shell variable <strong>CC_NAME<\/strong> in <tt>\/etc\/eucalyptus\/eucalyptus-cc.conf<\/tt><\/p>\n<\/li>\n<li>\n<p class=\"line862\">Define the shell variable <strong>SC_IP_ADDR<\/strong> in <tt>\/etc\/eucalyptus\/eucalyptus-ipaddr.conf<\/tt>, as a space separated list of one or more IP addresses.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p class=\"line874\"><strong>c. Publish<\/strong><\/p>\n<p class=\"line874\">Now start the publication services.<\/p>\n<ul>\n<li>\n<p class=\"line891\"><strong>Walrus Controller<\/strong>:<\/p>\n<pre>sudo start eucalyptus-walrus-publication<\/pre>\n<\/li>\n<li>\n<p class=\"line891\"><strong>Cluster Controller<\/strong>:<\/p>\n<pre>sudo start eucalyptus-cc-publication<\/pre>\n<\/li>\n<li>\n<p class=\"line891\"><strong>Storage Controller<\/strong>:<\/p>\n<pre>sudo start eucalyptus-sc-publication<\/pre>\n<\/li>\n<li>\n<p class=\"line891\"><strong>Node Controller<\/strong><\/p>\n<pre>sudo start eucalyptus-nc-publication<\/pre>\n<\/li>\n<\/ul>\n<p class=\"line874\"><strong>d. Start the Listener<\/strong><\/p>\n<p class=\"line862\">On the <strong>Cloud Controller<\/strong> and the <strong>Cluster Controller(s)<\/strong>, run:<\/p>\n<pre>sudo start uec-component-listener<\/pre>\n<p class=\"line874\">&nbsp;<\/p>\n<h4 id=\"Verify Registration\">e. Verify Registration<\/h4>\n<pre>cat \/var\/log\/eucalyptus\/registration.log\n2010-04-08 15:46:36-05:00 | 24243 -&gt; Calling node cluster1 node 10.1.1.75\n2010-04-08 15:46:36-05:00 | 24243 -&gt; euca_conf --register-nodes returned 0\n2010-04-08 15:48:47-05:00 | 25858 -&gt; Calling walrus Walrus 10.1.1.71\n2010-04-08 15:48:51-05:00 | 25858 -&gt; euca_conf --register-walrus returned 0\n2010-04-08 15:49:04-05:00 | 26237 -&gt; Calling cluster cluster1 10.1.1.71\n2010-04-08 15:49:08-05:00 | 26237 -&gt; euca_conf --register-cluster returned 0\n2010-04-08 15:49:17-05:00 | 26644 -&gt; Calling storage cluster1 storage 10.1.1.71\n2010-04-08 15:49:18-05:00 | 26644 -&gt; euca_conf --register-sc returned 0<\/pre>\n<\/div>\n<\/div>\n<\/div>\n<h3 id=\"STEP 5: Obtain Credentials\">STEP 5: Obtain Credentials<\/h3>\n<div dir=\"ltr\" lang=\"en\">\n<p class=\"line862\">After installing and booting the Cloud Controller, users of the cloud will need to retrieve their <em>credentials<\/em>.  This can be done either through a web browser, or at the command line.<\/p>\n<h4 id=\"From a Web Browser\">From a Web Browser<\/h4>\n<ol type=\"1\">\n<li>From your web browser (either remotely or on your Ubuntu server) access the following URL:\n<pre>https:\/\/&lt;cloud-controller-ip-address&gt;:8443\/<\/pre>\n<div>\n<table>\n<tbody>\n<tr>\n<td style=\"background-color:#91f49f\">\n<p class=\"line862\"><strong>Important!<\/strong> You must use a secure connection, so make sure you use &#8220;https&#8221; not &#8220;http&#8221; in your URL.  You will get a security certificate warning.  You will have to add an exception to view the page. If you do not accept it you will not be able to view the Eucalyptus configuration page.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/li>\n<li>Use username &#8216;admin&#8217; and password &#8216;admin&#8217; for the first time login (you will be prompted to change your password).<\/li>\n<li>Then follow the on-screen instructions to update the admin password and email address.<\/li>\n<li>\n<p class=\"line862\">Once the first time configuration process is completed, click the &#8216;credentials&#8217; tab located in the top-left portion of the screen.<\/p>\n<p><a class=\"nonexistent\" title=\"Upload new attachment &quot;UECcredentials-2.png&quot;\" href=\"\/community\/UEC\/Credentials?action=AttachFile&amp;rename=UECcredentials-2.png\"><img decoding=\"async\" src=\"https:\/\/help.ubuntu.com\/community\/UEC\/GetAnImageFromStore?action=AttachFile&amp;do=get&amp;target=Private-store-cr.png\" alt=\"\" \/><\/a><\/li>\n<li>Click the &#8216;Download Credentials&#8217; button to get your certificates<\/li>\n<li>\n<p class=\"line862\">Save them to <tt>~\/.euca<\/tt><\/p>\n<\/li>\n<li>Unzip the downloaded zipfile into a safe location (~\/.euca)\n<pre>unzip -d ~\/.euca mycreds.zip<\/pre>\n<p>&nbsp;<\/li>\n<\/ol>\n<p><strong>From a Command Line<\/strong><\/p>\n<ol type=\"1\">\n<li>Alternatively, if you are on the command line of the Cloud Controller, you can run:\n<pre>mkdir -p ~\/.euca\nchmod 700 ~\/.euca\ncd ~\/.euca\nsudo euca_conf --get-credentials mycreds.zip\nunzip mycreds.zip\nln -s ~\/.euca\/eucarc ~\/.eucarc\ncd -<\/pre>\n<\/li>\n<\/ol>\n<p><strong>Extracting and Using Your Credentials<\/strong><\/p>\n<p class=\"line874\">Now you will need to setup EC2 API and AMI tools on your server using X.509 certificates.<\/p>\n<ol type=\"1\">\n<li>Install the required cloud user tools:\n<pre>sudo apt-get install euca2ools<\/pre>\n<\/li>\n<li>To validate that everything is working correctly, get the local cluster availability details:\n<pre>. ~\/.euca\/eucarc\neuca-describe-availability-zones verbose\nAVAILABILITYZONE   myowncloud                 192.168.1.1\nAVAILABILITYZONE   |- vm types                free \/ max   cpu   ram  disk\nAVAILABILITYZONE   |- m1.small                0004 \/ 0004   1    192     2\nAVAILABILITYZONE   |- c1.medium               0004 \/ 0004   1    256     5\nAVAILABILITYZONE   |- m1.large                0002 \/ 0002   2    512    10\nAVAILABILITYZONE   |- m1.xlarge               0002 \/ 0002   2   1024    20\nAVAILABILITYZONE   |- c1.xlarge               0001 \/ 0001   4   2048    20<\/pre>\n<\/li>\n<\/ol>\n<\/div>\n<h3 id=\"STEP 6: Install an image from the store\">STEP 6: Install an image from the store<\/h3>\n<div dir=\"ltr\" lang=\"en\">\n<p class=\"line862\">The following is by far the simplest way to install an image.  However, advanced users may be interested in learning how to <a href=\"\/community\/UEC\/BundlingImages\">Bundle their own image<\/a>.<\/p>\n<p class=\"line874\">The simplest way to add an image to UEC is to install it from the Image Store on the UEC web interface.<\/p>\n<ol type=\"1\">\n<li>Access the web interface at the following URL (Make sure you specify https):\n<pre>https:\/\/&lt;cloud-controller-ip-address&gt;:8443\/<\/pre>\n<\/li>\n<li>Enter your login and password (if requested, as you may still be logged in from earlier)<\/li>\n<li>Click on the Store tab\n<p class=\"line891\"><img decoding=\"async\" class=\"attachment\" src=\"https:\/\/help.ubuntu.com\/community\/UEC\/GetAnImageFromStore?action=AttachFile&amp;do=get&amp;target=Private-store-cr.png\" alt=\"Private-store-cr.png\" \/><\/p>\n<\/li>\n<li>Browse available images<\/li>\n<li>Click on install for the image you want<\/li>\n<\/ol>\n<p class=\"line874\">Once the image has been downloaded and installed, you can click on &#8220;How to run?&#8221; that will be displayed below the image button to view the command to execute to instantiate (start) this image.  The image will also appear on the list given on the Image tab.<\/p>\n<ul>\n<li>\n<p class=\"line891\"><img decoding=\"async\" class=\"attachment\" src=\"https:\/\/help.ubuntu.com\/community\/UEC\/GetAnImageFromStore?action=AttachFile&amp;do=get&amp;target=private-images-cr.png\" alt=\"private-images-cr.png\" \/><\/p>\n<\/li>\n<\/ul>\n<\/div>\n<h3 id=\"STEP 7: Run an Image\">STEP 7: Run an Image<\/h3>\n<div dir=\"ltr\" lang=\"en\">\n<p class=\"line874\">There are multiple ways to instantiate an image in UEC:<\/p>\n<ul>\n<li>Use the command line<\/li>\n<li>Use one of the UEC compatible management tools such as Landscape<\/li>\n<li>\n<p class=\"line862\">Use the <a href=\"\/community\/UEC\/ElasticFox\">ElasticFox<\/a> extension to Firefox<\/p>\n<\/li>\n<\/ul>\n<p class=\"line874\">Here we will describe the process from the command line:<\/p>\n<ol type=\"1\">\n<li>Before running an instance of your image, you should first create a keypair (ssh key) that you can use to log into your instance as root, once it boots. The key is stored, so you will only have to do this once.  Run the following command:\n<pre>if [ ! -e ~\/.euca\/mykey.priv ]; then\n    mkdir -p -m 700 ~\/.euca\n    touch ~\/.euca\/mykey.priv\n    chmod 0600 ~\/.euca\/mykey.priv\n    euca-add-keypair mykey &gt; ~\/.euca\/mykey.priv\nfi<\/pre>\n<div>\n<table>\n<tbody>\n<tr>\n<td style=\"background-color:#91f49f\">\n<p class=\"line891\"><strong>Note:<\/strong> You can call your key whatever you like (in this example, the key is called &#8216;mykey&#8217;), but remember what it is called. If you forget, you can always run <tt>euca-describe-keypairs<\/tt> to get a list of created keys stored in the system.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/li>\n<li>You must make sure to source ~\/.euca\/eucarc before you run any of the eucatools. It is probably best to add this to the bottom of your .bashrc script.<\/li>\n<li>You must also allow access to port 22 in your instances:\n<pre>euca-authorize default -P tcp -p 22 -s 0.0.0.0\/0<\/pre>\n<\/li>\n<li>Next, you can create instances of your registered image:\n<pre>euca-run-instances $EMI -k mykey -t m1.small<\/pre>\n<div>\n<table>\n<tbody>\n<tr>\n<td style=\"background-color:#91f49f\">\n<p class=\"line891\"><strong>Note:<\/strong> If you receive an error regarding image_id, you may find it by viewing Images page or click &#8220;How to Run&#8221; on the Store page to see the sample command.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/li>\n<li class=\"gap\">The first time you run an instance, the system will be setting up caches for the image from which it will be created.  This can often take some time the first time an instance is run given that VM images are usually quite large.  To monitor the state of your instance, run:\n<pre>watch -n5 euca-describe-instances<\/pre>\n<p>In the output, you should see information about the instance, including its state.  While first-time caching is being performed, the instance&#8217;s state will be &#8216;pending&#8217;.<\/li>\n<li>When the instance is fully started, the above state will become &#8216;running&#8217;. Look at the IP address assigned to your instance in the output, then connect to it:\n<pre>IPADDR=$(euca-describe-instances | grep $EMI | grep running | tail -n1 | awk '{print $4}')\nssh -i ~\/.euca\/mykey.priv ubuntu@$IPADDR<\/pre>\n<\/li>\n<li>And when you are done with this instance, exit your SSH connection, then terminate your instance:\n<pre>INSTANCEID=$(euca-describe-instances | grep $EMI | grep running | tail -n1 | awk '{print $2}')\neuca-terminate-instances $INSTANCEID<\/pre>\n<\/li>\n<\/ol>\n<\/div>\n<h2 id=\"More Information\">More Information<\/h2>\n<div dir=\"ltr\" lang=\"en\">\n<p class=\"line862\">How to use the <a href=\"\/community\/UEC\/StorageController\">Storage Controller<\/a><\/p>\n<p class=\"line874\">Controlling eucalyptus services:<\/p>\n<ul>\n<li>sudo service eucalyptus [start|stop|restart] (on the CLC\/CC\/SC\/Walrus side)<\/li>\n<li>sudo service eucalyptus-nc [start|stop|restart] (on the Node side)<\/li>\n<\/ul>\n<p class=\"line874\">Locations of some important files:<\/p>\n<ul>\n<li>\n<p class=\"line891\"><strong>Log files:<\/strong><\/p>\n<ul>\n<li>\n<p class=\"line891\"><tt>\/var\/log\/eucalyptus<\/tt><\/p>\n<\/li>\n<\/ul>\n<\/li>\n<li>\n<p class=\"line891\"><strong>Configuration files:<\/strong><\/p>\n<ul>\n<li>\n<p class=\"line891\"><tt>\/etc\/eucalyptus<\/tt><\/p>\n<\/li>\n<\/ul>\n<\/li>\n<li>\n<p class=\"line891\"><strong>Database:<\/strong><\/p>\n<ul>\n<li>\n<p class=\"line891\"><tt>\/var\/lib\/eucalyptus\/db<\/tt><\/p>\n<\/li>\n<\/ul>\n<\/li>\n<li>\n<p class=\"line891\"><strong>Keys<\/strong><\/p>\n<ul>\n<li>\n<p class=\"line891\"><tt>\/var\/lib\/eucalyptus<\/tt><\/p>\n<\/li>\n<li>\n<p class=\"line891\"><tt>\/var\/lib\/eucalyptus\/.ssh<\/tt><\/p>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p class=\"line874\">Notes:<\/p>\n<ul>\n<li>Don&#8217;t forget to source your ~\/.euca\/eucarc before running the client tools.<\/li>\n<\/ul>\n<p class=\"line874\">Links:<\/p>\n<ul>\n<li>\n<p class=\"line891\"><a class=\"http\" href=\"http:\/\/www.eucalyptus.com\/open\/\">Eucalyptus Project Site (forums, documentation, downloads)<\/a><\/p>\n<\/li>\n<li>\n<p class=\"line891\"><a class=\"http\" href=\"http:\/\/www.launchpad.net\/eucalyptus\/\">Eucalyptus on Launchpad (bugs, code)<\/a><\/p>\n<\/li>\n<li>\n<p class=\"line891\"><a class=\"http\" href=\"http:\/\/eucalyptus.cs.ucsb.edu\/wiki\/EucalyptusTroubleshooting_v1.5\">Eucalyptus Troubleshooting (1.5)<\/a><\/p>\n<\/li>\n<li>\n<p class=\"line891\"><a class=\"http\" href=\"http:\/\/wiki.rightscale.com\/2._References\/02-Cloud_Infrastructures\/Eucalyptus\/03-Administration_Guide\/Register_with_RightScale?ls=Referral&amp;sd=%3EPartner_Ubuntu_Partnerpage&amp;campaign=70170000000KyOn\">Register your cloud with RightScale<\/a><\/p>\n<\/li>\n<\/ul>\n<\/div>\n<h2 id=\"Glossary\">Glossary<\/h2>\n<div dir=\"ltr\" lang=\"en\">\n<p class=\"line874\">The Ubuntu Enterprise Cloud documentation uses terminology that might be unfamiliar to some readers.  This page is intended to provide a glossary of such terms and acronyms.<\/p>\n<ul>\n<li>\n<p class=\"line891\"><strong>Cloud<\/strong> &#8211; A federated set of physical machines that offer computing resources through virtual machines, provisioned and recollected dynamically.<\/p>\n<\/li>\n<li>\n<p class=\"line891\"><strong>Cloud Controller (CLC)<\/strong> &#8211; Eucalyptus component that provides the web UI (an https server on port 8443), and implements the Amazon EC2 API.  There should be only one Cloud Controller in an installation of UEC.  This service is provided by the Ubuntu <em>eucalyptus-cloud<\/em> package.<\/p>\n<\/li>\n<li>\n<p class=\"line891\"><strong>Cluster<\/strong> &#8211; A collection of nodes, associated with a Cluster Controller.  There can be more than one Cluster in an installation of UEC.  Clusters are sometimes physically separate sets of nodes.  (e.g. floor1, floor2, floor2).<\/p>\n<\/li>\n<li>\n<p class=\"line891\"><strong>Cluster Controller (CC)<\/strong> &#8211; Eucalyptus component that manages collections of node resources.  This service is provided by the Ubuntu <em>eucalyptus-cc<\/em> package.<\/p>\n<\/li>\n<li>\n<p class=\"line891\"><strong>EBS<\/strong> &#8211; Elastic Block Storage. <a class=\"http\" href=\"http:\/\/aws.amazon.com\/ebs\/\">http:\/\/aws.amazon.com\/ebs\/<\/a><\/p>\n<\/li>\n<li>\n<p class=\"line891\"><strong>EC2<\/strong> &#8211; Elastic Compute Cloud.  Amazon&#8217;s pay-by-the-hour, pay-by-the-gigabyte public cloud computing offering.<\/p>\n<\/li>\n<li>\n<p class=\"line891\"><strong>EKI<\/strong> &#8211; Eucalyptus Kernel Image.<\/p>\n<\/li>\n<li>\n<p class=\"line891\"><strong>EMI<\/strong> &#8211; Eucalyptus Machine Image.<\/p>\n<\/li>\n<li>\n<p class=\"line891\"><strong>ERI<\/strong> &#8211; Eucalyptus Ramdisk Image.<\/p>\n<\/li>\n<li>\n<p class=\"line891\"><strong>Eucalyptus<\/strong> &#8211; Elastic Utility Computing Architecture for Linking Your Programs To Useful Systems.  An open source project originally from the University of California at Santa Barbara, now supported by Eucalyptus Systems, a Canonical Partner.<\/p>\n<\/li>\n<li>\n<p class=\"line891\"><strong>Front-end<\/strong> &#8211; Physical machine hosting one (or more) of the high level Eucalyptus components (cloud, walrus, storage controller, cluster controller).<\/p>\n<\/li>\n<li>\n<p class=\"line891\"><strong>Node<\/strong> &#8211; A node is a physical machine that&#8217;s capable of running virtual machines, running a node controller.  Within Ubuntu, this generally means that the CPU has VT extensions, and can run the KVM hypervisor.<\/p>\n<\/li>\n<li>\n<p class=\"line891\"><strong>Node Controller (NC)<\/strong> &#8211; Eucalyptus component that runs on nodes which host the virtual machines that comprise the cloud.  This service is provided by the Ubuntu package <em>eucalyptus-nc<\/em>.<\/p>\n<\/li>\n<li>\n<p class=\"line891\"><strong>S3<\/strong> &#8211; Simple Storage Service.  Amazon&#8217;s pay-by-the-gigabyte persistent storage solution for EC2. <a class=\"http\" href=\"http:\/\/aws.amazon.com\/s3\/\">http:\/\/aws.amazon.com\/s3\/<\/a><\/p>\n<\/li>\n<li>\n<p class=\"line891\"><strong>Storage Controller (SC)<\/strong> &#8211; Eucalyptus component that manages dynamic block storage services (EBS).  Each &#8216;cluster&#8217; in a Eucalyptus installation can have its own Storage Controller.  This component is provided by the &#8216;eucalyptus-sc&#8217; package.<\/p>\n<\/li>\n<li>\n<p class=\"line891\"><strong>UEC<\/strong> &#8211; Ubuntu Enterprise Cloud.  Ubuntu&#8217;s cloud computing solution, based on Eucalyptus.<\/p>\n<\/li>\n<li>\n<p class=\"line891\"><strong>VM<\/strong> &#8211; Virtual Machine.<\/p>\n<\/li>\n<li>\n<p class=\"line891\"><strong>VT<\/strong> &#8211; Virtualization Technology.  An optional feature of some modern CPUs, allowing for accelerated virtual machine hosting.<\/p>\n<\/li>\n<li>\n<p class=\"line891\"><strong>Walrus<\/strong> &#8211; Eucalyptus component that implements the Amazon S3 API, used for storing VM images and user storage using S3 bucket put\/get abstractions.<\/p>\n<\/li>\n<\/ul>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>Diiiceritaken bahwasanya hari ini\u00a0 mencoba implementasi Cloud Computing menggunakan software terbaru varian ubuntu yakni Ubuntu Enterprise Cloud (UEC). dari referensi yang sudah saya baca konsep dasar si Cloud Computing ini adalah berbagi resource Hardware dalam jaringan sehingga pemanfaatan infrastruktur jaringan akan semakin maksimal, Topology UEC biasanya seperti gambar dibawah. rencananya akan saya gunakan beberapa PC\u00a0 &hellip; <a href=\"https:\/\/dosen.unila.ac.id\/gigih\/2011\/02\/17\/develop-your-own-cloud-computing-infrastucture-with-ubuntu-enterprise-cloud-uec\/\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Develop your Own Cloud Computing Infrastructure with Ubuntu Enterprise Cloud (UEC) ,Eucalyptus,Walrus&#8221;<\/span><\/a><\/p>\n","protected":false},"author":25,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1348,9],"tags":[],"class_list":["post-265","post","type-post","status-publish","format-standard","hentry","category-kiat-sukses-menjadi-seorang-network-engineer-2","category-world-of-ict"],"_links":{"self":[{"href":"https:\/\/dosen.unila.ac.id\/gigih\/wp-json\/wp\/v2\/posts\/265"}],"collection":[{"href":"https:\/\/dosen.unila.ac.id\/gigih\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dosen.unila.ac.id\/gigih\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dosen.unila.ac.id\/gigih\/wp-json\/wp\/v2\/users\/25"}],"replies":[{"embeddable":true,"href":"https:\/\/dosen.unila.ac.id\/gigih\/wp-json\/wp\/v2\/comments?post=265"}],"version-history":[{"count":0,"href":"https:\/\/dosen.unila.ac.id\/gigih\/wp-json\/wp\/v2\/posts\/265\/revisions"}],"wp:attachment":[{"href":"https:\/\/dosen.unila.ac.id\/gigih\/wp-json\/wp\/v2\/media?parent=265"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dosen.unila.ac.id\/gigih\/wp-json\/wp\/v2\/categories?post=265"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dosen.unila.ac.id\/gigih\/wp-json\/wp\/v2\/tags?post=265"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}