Monthly Archives: April 2012

Wrapping up the Semester

The last week or so I have spent all of my time outside of class and work finishing up classes for the semester, and cs401 was no different. Between getting slides together for our presentations and finishing up my ethical analysis of the Eucalyptus project, combined with all of my other classes, it has been a busy week.

Today during class Dave, Mike, and myself took a trip over to the server room to flatten the network. Once we had that accomplished, we sat down and and configured two more nodes and edited the Eucalyptus Installation documentation accordingly. To be honest, it was very easy to do following the documentation that Dave had on the Wiki, even if most of it wasn’t necessary anymore due to there being packages we could install instead of having to compile from source. Hopefully some other people can go through the guide and get the rest of the nodes up and running.

Overall I think I learned a lot in this class over the course of the semester. I learned about version control and coding in a team environment, cloud infrastructure and how it all comes together, and a lot of python. All of which I can safely assume will make great additions to my resume. That being said, I’m looking forward to seeing everyone’s presentations next week and seeing how much we have accomplished as a class.

 

From the blog clacroix12 by clacroix12 and used with permission of the author. All other rights reserved by the author.

Meeting 12 – Cloud is finally working right

At last, with a visit from Andy Grimm last week, looked like our Dave was enlightened by him and figured out what he went wrong with our cloud’s configuration and he got it fixed. Now our images on the cloud can be started. The downfall is that all the accounts are wiped, so we had to re-register and update the credentials. But anyway, it was a great news we got in a while. I can play around with eutester now.

From the blog longnguyen16 » wsu-cs by watever10 and used with permission of the author. All other rights reserved by the author.

Meeting 9 – Review what have been done so far!!

Today is like a day that we go over to see what the group has been able to accomplish so far. Each group will report what they have done. It looks like we got the cloud running to the point that images can be added but failed to be ran. I also found out that a new version of euca2ools on github will fix the small bug about uploading image in the previous version (the one stated as the latest stable version on the open.eucalyptus.com). And all kinds of documentations are looking great.

From the blog longnguyen16 » wsu-cs by watever10 and used with permission of the author. All other rights reserved by the author.

Class Week 12

In this week’s class we focused on making sure everyone is familiar with the things that are due for the end of class. We got together with our group to discuss what we are going to put together for the presentation on the last day of class. We need to figure out the information that we are going to discuss in our presentation and what materials needs to go on the slideshow. Each student is responsible for speaking for a few minutes about the things that we did on the group project, so I am coordinating with my group so we don’t all speak about the same thing. We worked on the bug tracker and putting together documentation about the current issues that people are having. I am going to be working this weekend on updating our section on the page with the new issues and getting rid of the old issues or the ones that have been closed. 

From the blog jgaval by jgaval1 and used with permission of the author. All other rights reserved by the author.

Class Week 11

In this week’s class we focused on everyone doing their part in the project to make sure everyone is contributing. We met with our groups and discussed all the things that need to be done for the remainder of the weeks and put it all together for everyone else to leave. I myself was working with Git hub to find all the issues that are being tracked, going through both the open and closed ones. It is important to look at the closed issues as well to see how the software has progressed from the beginning of the semester. Our group has been responsible for adding the documentation for the issues that have come up since everyday there are new updates.

From the blog jgaval by jgaval1 and used with permission of the author. All other rights reserved by the author.

CS401 – Creating the Wiki Articles

I am now actually consolidating the information our group researched and putting it into wiki articles. Right now I have the main page, the cloud controller, cluster controller, walrus and storage controller. I still need to do node controller and I need to go over everything and fix it up a bit.

Our group has also been working on the presentation that we will give during the final exam, and that is coming along well. Link to the wiki below.

 

http://cs.worcester.edu/wiki/index.php?n=Main.ArchitectureOverview

From the blog blabbecs401 » CS401 by blabbecs401 and used with permission of the author. All other rights reserved by the author.

Final Presentation

This week I spent most of my time figuring out what was left to finish in our eutester repository. I also used a lot of screenshots from github for my powerpoint presentation. I worked with Nate, Coady, and Marcos to put together our final project. We all put together screenshots and code samples from the changes we added to the repo to show everything we accomplished this semester.

Also, I wrote my paper on the Eucalyptus Ethical Analysis this week. It was interesting to look at the software and find out where it was good and where it was not so good. As it turns out, Eucalyptus is not 100% free and open source. It is better described as “open-core” because it only allows certain aspects of the product to be used for free. To add on more powerful features, users must pay a fee, which goes against the entire open source mindset. Users are only given a free trial of the software and all of the products that can be used with Eucalyptus are proprietary. There are other options that are similar to Eucalyptus, that are actually free and open source, but it appears that Eucalyptus is more mainstream and user friendly. 

From the blog trevorhodde by Trevor and used with permission of the author. All other rights reserved by the author.

Last week of class

This final week – before the last class – I have been working on my part of our groups presentation on GitHub/EUTester Documentation and the ethical analysis of the Eucalyptus project Dr. Wurst gave us. Our group has made significant progress in documenting EUTester, and the majority of the python scripts now have headers that document what that script does! Having to go through the code has been a good way to force me to learn python, which I have had on my to-do list for a while now, and has shown me the usefulness of the language.

From the blog nathandoe » WSU CS by nathandoe and used with permission of the author. All other rights reserved by the author.

Test Run of the Wiki

This week I am going to start from scratch and try to install Eutester+euca2ools from our wiki only, keeping notes along the way to see if we need to update anything to make it more clear.  I imagine from what I’ve been reading that we’ve made quite a large amount of progress over this course and when I had to restart last month it took me maybe an hour? (would be been less if I realized >>> meant that you type python ) but that’s besides the point.  This blog post will serve as a note pad for anything our wiki should make clearer.

 

 

Updated this:

I decided that I would find someone I could use that doesn’t really know much about Eucalyptus and at least knows how to work Linux.  It turned out pretty well, I have some notes jotted down that I can finalize the wiki with to make it as fast as possible.  Everything was pretty well laid out, aside form small things like the note “don’t forget to use sudo” after they entered all the commands.  One thing I need to add is that we never directly say to install boto.

 

Overall this test went pretty well.

From the blog jamescelona » WSU CS by jamescelona and used with permission of the author. All other rights reserved by the author.

Week of April 23 2012

This week we got together in class and decided on how we would go about presenting our portion of the Eucalyptus project. Our group, because it discusses the Architecture Overview, will be the first group to present on May 9th, 2012. We decided it is probably a good idea to do a couple of run-throughs of our oral presentation so that we are prepared on the day of so we met up on campus on Saturday to get started.

After meeting on Saturday, we came up with the details regarding what our presentation will consist of.

I added some finishing touches to what I already have written on the storage controller and machine images.

We also received the requirements/credentials for the Ethical Analysis of Eucalyptus so I began working on that as well. The topic I chose to discuss was security and cloud computing/Eucalyptus. There are security issues with cloud computing in general so I thought that would be an interesting topic to tackle.

From the blog nzahid » WSU CS by nzahid and used with permission of the author. All other rights reserved by the author.