The semester is over and this is basically my last blog post for now, but im actually thinking of keeping this blog and beginning to use it for things that i find interesting.
Basically the euca2ools group presentation seemed to have gone pretty well and everything worked while giving it(which is awesome). Considering the amount of problems that we have been running into coming up to this day we were very excited that everything worked.
John in our group was actually able to upload a CentOS image and get it running on our cloud the previous day of the presentations, and then on the day of the presentations we were able to get a third image up and running with no Walrus errors and SSH into that instance. Dhimitri and I were kind of surprised to say the least cause the day before Walrus was giving us the 403 Forbidden error, so it seemed to have fixed itself….
Walrus may have just had a hiccup and that restarting it that day may have solved the issue we were having. Dhimitri also managed to get up a new node running which you could see with the euca-describe-availabilityzones command. All in all, it seemed that the Euca2ools wiki worked out for the best and seemed that a lot of people were able to follow a lot of the steps to use for themselves. This was a really fun and interesting project to work on despite a lot of the issues that kept happening on our way but i think it was for the best cause many of us gained a lot of experience and a lot of understanding of the whole Cloud computing and what it is.
Leading down to the couple of weeks of the semester and beginning to finish up/wrap everything that we have done up to present, we ran into a couple of issues.
Dhimitri and I were in the same Euca2ools group for the presentations so we were working together through the weekend on what we were going to present and go through as a demo during the presentation. As he was working on a script, i was going through and testing our cloud by uploading a different image and kernel and trying to get more instances up and running, and also deleting images from the cloud.
The first issue that we ran into was a problem with getting a new instance up and running. At first i thought it was cause i did not bundle the kernel and image together correctly, so i tried it over and over again until i though it was perfect. The image that i used was the same image as the one that was currently running, so when it was not working we knew we had a bit of a problem. From what the NC log told us we were getting some type of 403 forbidden error and seemed to be stopping us from running instances.
A second issue that occurred, was after uploading quite a few images, kernels, and ram-disks the amount of images on the cloud was kind of cluttered so i wanted to delete some of them. When running the command to delete these images however they were not being removed. We would de-register them and delete but they were not being removed. They stayed on the cloud and listed as de-registered so we restarted the services and still nothing the images appeared back on the cloud as normal.
Towards the final weeks of the semester we actually managed to put together a cloud that was basically running. I say basically running because there still seems to be a few bugs here and there that causes some issues every once in a while.
In the week that we managed to finally get an image up and running Dave actually had decided to reinstall eucalyptus on our cloud with the packages that Eucalyptus team had end up putting together halfway through the semester. During class he actually managed to quickly install all of the packages and set everything up, while long and I managed to package and image with a kernel that was working on the ECC cloud, and we actually managed to get it running.
This was a success at running an image and all seemed well but there was still some work to be done, we could run one image but when we tried to run more it was not allowing us to due to not enough resources and seemed not to be assigning IP’s correctly. So there must have been a problem with the network configuration, Mike was tasked with flattening the network and after some tweeks that Dave did to the networking configuration on the cloud all seemed much better.
We were able to get multiple instances up in the long run and the troubleshooting that Dhimitri and I have been doing seemed to help locating where some potential problems were by going through the nclog file.
One of the issues that we had while setting up our cloud was incompatible BIOS revision on the machines we were using. They were out of date and did not allow the use of virtualization, so we had to update the BIOS a certain way with the DELL Executable that was the only way to update the BIOS was using an EXE.
The first step to creating the bootable disk was downloading FreeDOS so that we can boot up into FreeDOS and run the executable.
In order to do this you do: wget http://www.fdos.org/bootdisks/autogen/FDOEM.144.gz
Then, gunzip FDOEM.144.gz to unzip the file.
The second step is to copy the BIOS flash utility and the BIOS image that needs to be used to upgrade, and mount it to a floppy disk image. Here is what you do in order to complete this step:
mount -t vfat -o loop FDOEM.144 /tmp/floppy
After mounting the Floppy you want to copy the EXE. that you downloaded for the BIOS:
cp DELLBIOSVERSION.exe /tmp/floppy (not actual name of the bios)
then unmount the floppy: umount /tmp/floppy
Step 3 is to burn the bootable CD which emulates a floppy device.
mkisofs -o bootcd.iso -b FDOEM.144 FDOEM.144
cdrecord -v bootcd.iso
After you have created this bootable disk, all you have to do is boot the CD in the machine and basically type in the EXE. and it will autoflash to the new bios.
Last week their was a class discussion on which projects the class most wanted to work on. Two projects that i had researched a bit that i though would have been interesting included Mumble or PuTTY, but i figured that these projects might not have been substantial enough for the whole class.
Some of the bigger projects that seemed to be top picks included Eucalyptus, Irrchlicht, Mozilla, Chromium, and OpenOffice. There wasn’t a real certainty of what each person wanted to work on, so we did a class vote to see what the front runners were going to be. The projects that came out ahead included Eucalyptus, Irrchlicht, and Mozilla. After the final shuffling of the votes however the project that had the majority of votes was Eucalyptus.
There was also a class discussion going on at the same time in the IRC Channel, however i was not able to get into the chat because of certain hardware issues i was having with my laptop that day.
During class we were all introduced into the world of IRC Chat. The exercise that we were given to complete was for you and a partner to edit each other’s profile pages on the Learning Open Source site, but with certain rules attached. In order to complete the assignment we had to only communicate using the IRC channel, talking back and forth in chat.
The whole process was very intriguing because the whole class was silent with chuckles filling the room every once in a while. Although this is wasnt my first time in an IRC Chat environment, it was my first time partaking in an IRC that contained class mates of mine during a class, and talking about the various subject matters going on, such as possible projects to work on.
Over the course of the semester i am sure that the IRC chat will become a very useful tool in communicating with others on the current project we will be working on, and also be a tool that we could use when we have questions, such that we can go on the IRC channel and ask the question we seek an answer to. Continue Reading
This is my first post, some of the things that I am looking forward to the work that we are going to get to be doing in this course. Some of the things that i wish to accomplish is to just gain overall experience in working in a larger project, as compared to the smaller programs we have done previously; Another thing is being able to contribute something to the project that we get to work on, that could possibly benefit hundreds or even thousands of people that use that open source software.