UEC: Manajemen Image - Revision history

Onnowpurbo: /* Pranala Menarik */

2011-01-06T12:31:26Z

Pranala Menarik

Onnowpurbo at 02:18, 20 December 2010

2010-12-20T02:18:26Z

Onnowpurbo at 02:05, 20 December 2010

2010-12-20T02:05:32Z

Onnowpurbo at 01:59, 20 December 2010

2010-12-20T01:59:54Z

Onnowpurbo at 01:32, 20 December 2010

2010-12-20T01:32:37Z

Onnowpurbo at 01:29, 20 December 2010

2010-12-20T01:29:44Z

Onnowpurbo at 01:11, 20 December 2010

2010-12-20T01:11:19Z

Show changes

Onnowpurbo at 03:43, 19 December 2010

2010-12-19T03:43:48Z

Onnowpurbo at 03:24, 19 December 2010

2010-12-19T03:24:09Z

Onnowpurbo at 12:08, 16 December 2010

2010-12-16T12:08:55Z

@@ Line 166: / Line 166: @@
 ==Pranala Menarik==
-* [[Ubuntu Enterprise Cloud: Eucalyptus Beginner’s Guide]] '''RECOMMENDED'''
+* [[Ubuntu Enterprise Cloud: Panduan Untuk Pemula]] '''RECOMMENDED'''
 * [[Ubuntu Enterprise Cloud: Instalasi UEC]]
 * [[Cloud Computing]]

@@ Line 127: / Line 127: @@
 ==Mendaftarkan ramdisk image==
-Execute the following commands to bundle and register the ramdisk image (initrd.img-2.6.28-11-server)
+Jalankan perintah berikut untuk mem-bundel dan mendaftarkan ramdisk image (initrd.img-2.6.28-11-server)
   uecadmin@client1:~$ euca-bundle-image -i  initrd.img-2.6.28-11-server
@@ Line 133: / Line 133: @@
   uecadmin@client1:~$ euca-register mybucket/initrd.img-2.6.28-11-server.manifest.xml
-Save the output produced by the last command above (eri-XXXXXXXX), which will be needed while registering the disk image.
+Simpan output yagn dihasilkan oleh perintah terakhir di atas (eri-XXXXXXXX), yang akan dibutuhkan pada saat mendaftarkan disk image.
-Execute the following commands to bundle and register the ramdisk image (image.img)
   uecadmin@client1:~$ euca-bundle-image -i image.img --kernel eki-XXXXXXXX --ramdisk eri-XXXXXXXX
@@ Line 142: / Line 144: @@
   uecadmin@client1:~$ euca-register mybucket/image.img.manifest.xml
-Replace eki-XXXXXXXX and eri-XXXXXXXX with the exact values you have saved earlier.
+Ganti eki-XXXXXXXX dan eri-XXXXXXXX dengan nilai yang kita peroleh sebelumnya
-Image Listing
-The new images that have been uploaded can be seen by using euca-describe-images command.
+Image baru yang sudah di upload dapat dilihat menggunakan perintah euca-describe-images
@@ Line 153: / Line 157: @@
   IMAGE   eki-685F1306    mybucket/vmlinuz-2.6.28-11-server.manifest.xml      admin    available       public  x86_64  kernel
-More details on managing the instances in later chapters.
+Tentang bagaimana managing instances akan di terangkan di bagian selanjutnya.

@@ Line 112: / Line 112: @@
 Sebelum menjalankan upload shutdown VM.
 ==Mendaftarkan kernel image==
-Execute the following commands to bundle and register the kernel image (vmlinuz-2.6.28-11-server)
+Jalankan perintah berikut untuk mem-bundel dan mendaftarkan kernel image (vmlinuz-2.6.28-11-server)
-Save the output produced by the last command above (eki-XXXXXXXX), which will be needed while registering the disk image.
+==Mendaftarkan ramdisk image==
 Execute the following commands to bundle and register the ramdisk image (initrd.img-2.6.28-11-server)
-	uecadmin@client1:~$ euca-bundle-image -i  initrd.img-2.6.28-11-server
+ uecadmin@client1:~$ euca-bundle-image -i  initrd.img-2.6.28-11-server
-	uecadmin@client1:~$ euca-upload-bundle -b mybucket -m /tmp/initrd.img-2.6.28-11-server.manifest.xml
+ uecadmin@client1:~$ euca-upload-bundle -b mybucket -m /tmp/initrd.img-2.6.28-11-server.manifest.xml
-	uecadmin@client1:~$ euca-register mybucket/initrd.img-2.6.28-11-server.manifest.xml
+ uecadmin@client1:~$ euca-register mybucket/initrd.img-2.6.28-11-server.manifest.xml
 Save the output produced by the last command above (eri-XXXXXXXX), which will be needed while registering the disk image.
@@ Line 135: / Line 138: @@
 Execute the following commands to bundle and register the ramdisk image (image.img)
-	uecadmin@client1:~$ euca-bundle-image -i image.img --kernel eki-XXXXXXXX --ramdisk eri-XXXXXXXX
+ uecadmin@client1:~$ euca-bundle-image -i image.img --kernel eki-XXXXXXXX --ramdisk eri-XXXXXXXX
-	uecadmin@client1:~$ euca-upload-bundle -b mybucket -m /tmp/image.img.manifest.xml
+ uecadmin@client1:~$ euca-upload-bundle -b mybucket -m /tmp/image.img.manifest.xml
-	uecadmin@client1:~$ euca-register mybucket/image.img.manifest.xml
+ uecadmin@client1:~$ euca-register mybucket/image.img.manifest.xml
 Replace eki-XXXXXXXX and eri-XXXXXXXX with the exact values you have saved earlier.
@@ Line 145: / Line 148: @@
-	uecadmin@client1:~$ euca-describe-images
+ uecadmin@client1:~$ euca-describe-images
-	IMAGE   emi-70B70EC0    mybucket/image.img.manifest.xml                     admin   available        public  x86_64  machine
+ IMAGE   emi-70B70EC0    mybucket/image.img.manifest.xml                     admin   available        public  x86_64  machine
-	IMAGE   eri-A2BE13EC    mybucket/initrd.img-2.6.28-11-server.manifest.xml   admin    available       public  x86_64  ramdisk
+ IMAGE   eri-A2BE13EC    mybucket/initrd.img-2.6.28-11-server.manifest.xml   admin    available       public  x86_64  ramdisk
-	IMAGE   eki-685F1306    mybucket/vmlinuz-2.6.28-11-server.manifest.xml      admin    available       public  x86_64  kernel
+ IMAGE   eki-685F1306    mybucket/vmlinuz-2.6.28-11-server.manifest.xml      admin    available       public  x86_64  kernel
 More details on managing the instances in later chapters.

@@ Line 104: / Line 104: @@
 ==Pendaftaran ke Eucalyptus==
-The last step would be to upload the images to Eucalyptus. The files that need to be uploaded for the above sample setup are: vmlinuz-2.6.28-11-server, initrd.img-2.6.28-11-server, image.img.
+Langkah terakhir adalah mengupload image ke Eucalyptus. File yang perlu di upload untuk contoh di atas adalah vmlinuz-2.6.28-11-server, initrd.img-2.6.28-11-server, image.img.
-Copy the kernel and the initrd image from the VM image to some place outside. These will be used later for creating and uploading a complete virtual image to Eucalyptus.
+Copy kernel dan initrd image dari VM image ke sebuah lokasi di luar. Hal ini di perlukan untuk digunakan selanjutnya waktu membuat dan mengupload complete virtual image ke Eucalyptus.
-	$ scp /boot/initrd.img-2.6.28-11-server user@A.B.C.D:
+ $ scp /boot/initrd.img-2.6.28-11-server user@A.B.C.D:
-	$ scp /boot/vmlinuz-2.6.28-11-server user@A.B.C.D:
+ $ scp /boot/vmlinuz-2.6.28-11-server user@A.B.C.D:
-Before starting the upload process shut down the VM.
+Sebelum menjalankan upload shutdown VM.
-Registering kernel image
 Execute the following commands to bundle and register the kernel image (vmlinuz-2.6.28-11-server)
@@ Line 143: / Line 144: @@
 The new images that have been uploaded can be seen by using euca-describe-images command.
-For Ex:
 	uecadmin@client1:~$ euca-describe-images
 	IMAGE   emi-70B70EC0    mybucket/image.img.manifest.xml                     admin   available        public  x86_64  machine

@@ Line 99: / Line 99: @@
   $ sudo rm -rf /etc/udev/rules.d/70-persistent-net.rules
-Hal di atas This completes the process of customizing the OS installed as a reference image.
+Selesai sudah proses customisasi OS yang akan di instalasi sebagai reference image.
 ==Pendaftaran ke Eucalyptus==

@@ Line 70: / Line 70: @@
 ==Integrasi dengan Eucalyptus==
-An instance running under Eucalyptus needs to know what IP it has and also, it needs to have the public key of the user allowed to do a passwordless access through SSH. This is accomplished by using a restful interface provided by the cloud. The interface is available under this URL: http://169.254.169.254/latest/meta-data and accessible from within the Instance.
+Sebuah Instance jalan di Eucalyptus perlu mengetahui IP yang dia miliki, dia juga membutuhkan public key dari pengguna yang di ijinkan untuk mengakses secara passwordless melalui SSH. Hal ini dapat di akses menggunakan interface yang di sediakan oleh cloud. Interface tersebut tersedia melalui URL http://169.254.169.254/latest/meta-data yang dapat di akses dari dalam instance.
-Eucalyptus node controller is set up to prevent automatic key injection if the system is in MANAGED or MANAGED-NOVLAN mode. Instead, it is assumed that the instance will use the above meta-data service to retrieve the public keys when running in these modes. You will need to facilitate this by installing curl and adding a script that will run on each boot.
+Eucalyptus node controller di setup untuk menjaga tidak terjadinya automatic key injection jika system di operasikan menggunakan mode MANAGED atau MANAGED-NOVLAN. Akan tetapi, Eucalyptus akan berasumsi bahwa instance akan menggunakan layanan meta-data di atas untuk mengambil public key jika di jalankan pada mode di atas. Kita perlu memfasilitasi ini dengan menginstal crul dan menambahkan sedikit script setiap kali booting.
-Install curl on the VM.
+Instalasi crul di VM
-	$ sudo apt-get install curl
+ $ sudo apt-get install curl
-Now add the following lines to /etc/rc.local of the image.
+Tambahakan kalimat berikut di /etc/rc.local sebelum kata 'exit 0' dari image
-	depmod -a
+ depmod -a
-	modprobe acpiphp
+ modprobe acpiphp
-−
-	# simple attempt to get the user ssh key using the meta-data service
+  # simple attempt to get the user ssh key using the meta-data service
-	# assuming “user” is the username of an account that has been created
+ # assuming “user” is the username of an account that has been created
-−
-	mkdir -p /home/user/.ssh
+  mkdir -p /home/user/.ssh
-	echo &gt;&gt; /home/user/.ssh/authorized_keys
+ echo &gt;&gt; /home/user/.ssh/authorized_keys
-	curl -m 10 -s http://169.254.169.254/latest/meta-data/public-keys/0/openssh-key | grep 'ssh-rsa' &gt;&gt; \
+ curl -m 10 -s http://169.254.169.254/latest/meta-data/public-keys/0/openssh-key | grep 'ssh-rsa' &gt;&gt; \
-	                          /home/user/.ssh/authorized_keys
+                           /home/user/.ssh/authorized_keys
-	echo &quot;AUTHORIZED_KEYS:&quot;
+ echo &quot;AUTHORIZED_KEYS:&quot;
-	echo &quot;************************&quot;
+ echo &quot;************************&quot;
-	cat /home/user/.ssh/authorized_keys
+ cat /home/user/.ssh/authorized_keys
-	echo &quot;************************&quot;
+ echo &quot;************************&quot;
-Add the above lines before the “exit 0” in /etc/rc.local
+Juga buang network persistent rules dari /etc/udev/rules.d, sehingga instance selalu nyala dengan eth0 sebagai nama interface seperti yang di harapkan oleh Eucalyptus.
-Also remove the network persistent rules from /etc/udev/rules.d, so that the instance always comes up with eth0 as the interface name as expected by eucalyptus.
+ $ sudo rm -rf /etc/udev/rules.d/70-persistent-net.rules
-	$ sudo rm -rf /etc/udev/rules.d/70-persistent-net.rules
+Hal di atas This completes the process of customizing the OS installed as a reference image.
-This completes the process of customizing the OS installed as a reference image.
+==Pendaftaran ke Eucalyptus==
 The last step would be to upload the images to Eucalyptus. The files that need to be uploaded for the above sample setup are: vmlinuz-2.6.28-11-server, initrd.img-2.6.28-11-server, image.img.

@@ Line 33: / Line 33: @@
 ===Membuat Image disk===
-This will represent the main HDD of the virtual machine, so make sure to give it as much space as you will need. Since we are building a kvm image, we can use a qcow2 format for disk images. Qcow2 is an expandable image format, so it will only occupy as much storage space as is actually filled by the data within the image.
+Hal ini memrepresentasikan harddisk utama dari virtual machine, oleh karenanya kita perlu memastikan bahwa kita memberikan alokasi harddisk yang cukup. Karena kita akan membuat image kvm, kita menggunakan format qcow2 untuk image. Qcow2 adalah format image yang dapat di expand, oleh karenanya dia hanya akan menggunakan tempat penyimpanan yang berisi data aja dari image tersebut.
   uecadmin@client1:~$ kvm-img create -f qcow2 image.img 5G
@@ Line 52: / Line 49: @@
   -net nic -net user -nographic -vnc :0
-If your installation process requires more than 256MB of RAM change the -m option, and if you need more processors available, you can use the ‘-c’ option.
+Jika proses instalasi membutuhkan RAM lebih dari 256MB ubah opsi -m, dan jika kita membutuhkan lebih banyak prosesor yang tersedia, kita dapat menggunakan opsi '-c'.
 The command above will boot a new KVM instance, with the disk image you’ve created as the primary HDD and the iso as the first bootable device. Also the ‘-nographic’ option will not display any graphical output. You can connect to the instance through VNC (use display number :0) and finish the installation.
-view source
 	For Ex: vncviewer A.B.C.D :0, where A.B.C.D is the IP address of Client1.
@@ Line 163: / Line 160: @@
 Create an ISO image of the relevant Windows installation CD. And start the installation process.
-view source
 	uecadmin@client1:~$ sudo kvm -m 1024 -cdrom Win2003ServerR2x86_cd1.iso -drive file=win-2k3.img,if=scsi,boot=on -nographic -vnc :0
@@ Line 184: / Line 180: @@
 . Finish the installation of Windows XP.
 . Now create another disk image using kemu-img
-view source
 	$ kvm-img create -f qcow2 newdisk.img 5G
@@ Line 229: / Line 224: @@
 Execute the following command to create the boot disk.
-view source
 	uecadmin@client1:~$ dd bs=512 count=2880 if=/dev/zero of=win-boot.img

@@ Line 10: / Line 10: @@
 Dari interface [[web]] Eucalyptus, kita dapat melihat daftar dari EMI yang ada di tab “Store” di web. Daftar ini adalah EMI yang ada di Canonical atau partner. Kita dapat memilih untuk mendownload dan menginstall image ini langsung dari Canonical site.
 Since most enterprise/individual users of Eucalyptus have a need for bringing up instances based on custom images, image management plays a key role in Eucalyptus administration. Such images could be based on a preferred version/variant of a preferred OS distribution with a set of required applications pre-installed.
@@ Line 26: / Line 28: @@
 ==Membuat Linux Image==
-We will use Client1 for the purpose of working on creation of the image. Please note that we had installed KVM on Client1.
+Kita akan menggunakan Client1 untuk pembuatan image. Untuk itu, kita perlu menginstalasi KVM di Client1.
-Creating a new disk Image
 This will represent the main HDD of the virtual machine, so make sure to give it as much space as you will need. Since we are building a kvm image, we can use a qcow2 format for disk images. Qcow2 is an expandable image format, so it will only occupy as much storage space as is actually filled by the data within the image.