Monthly Archives: April 2012

Ethical Components Regarding Eucalyptus

Eucalyptus has a lot of vulnerability when it comes to ethical assessment.  Eucalyptus puts the power of a cloud at the keyboard of its users.  It is open-source and the community could potentially use it with malicious intent.  Who can be held accountable if the software is used for destructive purposes?

Eucalyptus has a very broad terms of use policy.  It simply states that contributors and users are responsible for the contributions they make toward the project and the implementation of the software. Users agree that it will only be used for lawful purposes.  Though, in the technology world, there is a lot of grey area. Laws often vary from state-to-state and even more so on the international level.  What if a cloud is hosted in one state, where the laws are loose, and is utilized in another state where they are very tight?  What legislature applies?  This area is still very undefined, and proposes great risk to contributors, users, and Eucalyptus’ responsibility.

On the other hand, the more detailed the terms of use becomes, the less versatility and flexibility you have with the software.  You begin to remove the open-source aspect that the project is based on.  The more you tell users what the software can and can’t be used for, the less likely they are to use it.  It becomes more of a burden to follow all of the terms of use than is worth it.  It’s essentially a catch-22.

I think the most obscene part of the whole project is the business structure.  When I buy something, I prefer to be told up-front how much it’s going to cost.  Eucalyptus gives a trial of there software, then you face a fee for continued use.  If you can’t quite figure out the incredibly dense and technical documentation, you’ll be charged a service fee for any help.  If you want to further specialize the software with add-ons, you’ll probably pay for those too.  Welcome to the Americanized version of marketing, where we nickel-and-dime you to death before you even have a working product.

I still think Eucalyptus has a lot of potential, but it requires a great deal of attention to business structure and project management.  Implement release dates, and stop nickel-and-diming to reach profitability.

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

4/30

I figured that since we are nearing the end of the semester I would post an updated list of current bugs/issues located on the EuTester github page. There are currently quite a bit more issues since the last time I posted the list and I think that some of them have come from our class’s extensive use of EuTester.

  • Update eutester/__init__.py
  • Feature Request: Allow for NC to be an optional value in config_file
  • Need way for machine access when keys have been previously synced
  • Restructure Eucaops into multiple modules
  • Create a Test Directory WikiAdmin
  • Need to investigate a tool that represents test results visually
  • Define licensing
  • Create a standard set of debug tools available when tests fail
  • Goals, purpose, and guidelines for contribution

My group is going to continue trying to run test scripts and familiarize ourselves with EuTester and hopefully try and look into one of these issues. We have posted all the information regarding issues/bugs for EuTester on our departmental wiki.

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

Wrapping Up Eutester Documentation

This week I’ve finished commenting on the webtestcase.py script and pushed the changes through. It was interesting running into my first conflict errors and having to pull changes from the origin master before being able to make any further pushes. So right now our group is almost done documenting the eucaweb directory with the init.py file being the only one left which I’ll try to finish documenting next week. At this point we’ve done a good amount of work on eutester documentation in general, although it’s looking like we won’t be able to complete the project entirely with the semester coming to an end. I’m also disappointed I wasn’t even able to develop any actual code to fix the issues on the Github issues tracker which I was planning on doing after the documentation project was finished. However, I feel good that we were able to help the creators of eucalyptus and I hope what we’ve done will assist anyone who works on the project in the future.

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

Wrapping Up Eutester Documentation

This week I’ve finished commenting on the webtestcase.py script and pushed the changes through. It was interesting running into my first conflict errors and having to pull changes from the origin master before being able to make any further pushes. So right now our group is almost done documenting the eucaweb directory with the init.py file being the only one left which I’ll try to finish documenting next week. At this point we’ve done a good amount of work on eutester documentation in general, although it’s looking like we won’t be able to complete the project entirely with the semester coming to an end. I’m also disappointed I wasn’t even able to develop any actual code to fix the issues on the Github issues tracker which I was planning on doing after the documentation project was finished. However, I feel good that we were able to help the creators of eucalyptus and I hope what we’ve done will assist anyone who works on the project in the future.

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

Wrapping Up Eutester Documentation

This week I’ve finished commenting on the webtestcase.py script and pushed the changes through. It was interesting running into my first conflict errors and having to pull changes from the origin master before being able to make any further pushes. So right now our group is almost done documenting the eucaweb directory with the init.py file being the only one left which I’ll try to finish documenting next week. At this point we’ve done a good amount of work on eutester documentation in general, although it’s looking like we won’t be able to complete the project entirely with the semester coming to an end. I’m also disappointed I wasn’t even able to develop any actual code to fix the issues on the Github issues tracker which I was planning on doing after the documentation project was finished. However, I feel good that we were able to help the creators of eucalyptus and I hope what we’ve done will assist anyone who works on the project in the future.

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

Wrapping Up Eutester Documentation

This week I’ve finished commenting on the webtestcase.py script and pushed the changes through. It was interesting running into my first conflict errors and having to pull changes from the origin master before being able to make any further pushes. So right now our group is almost done documenting the eucaweb directory with the init.py file being the only one left which I’ll try to finish documenting next week. At this point we’ve done a good amount of work on eutester documentation in general, although it’s looking like we won’t be able to complete the project entirely with the semester coming to an end. I’m also disappointed I wasn’t even able to develop any actual code to fix the issues on the Github issues tracker which I was planning on doing after the documentation project was finished. However, I feel good that we were able to help the creators of eucalyptus and I hope what we’ve done will assist anyone who works on the project in the future.

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

Wrapping Up Eutester Documentation

This week I’ve finished commenting on the webtestcase.py script and pushed the changes through. It was interesting running into my first conflict errors and having to pull changes from the origin master before being able to make any further pushes. So right now our group is almost done documenting the eucaweb directory with the init.py file being the only one left which I’ll try to finish documenting next week. At this point we’ve done a good amount of work on eutester documentation in general, although it’s looking like we won’t be able to complete the project entirely with the semester coming to an end. I’m also disappointed I wasn’t even able to develop any actual code to fix the issues on the Github issues tracker which I was planning on doing after the documentation project was finished. However, I feel good that we were able to help the creators of eucalyptus and I hope what we’ve done will assist anyone who works on the project in the future.

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

Wrapping Up Eutester Documentation

This week I’ve finished commenting on the webtestcase.py script and pushed the changes through. It was interesting running into my first conflict errors and having to pull changes from the origin master before being able to make any further pushes. So right now our group is almost done documenting the eucaweb directory with the init.py file being the only one left which I’ll try to finish documenting next week. At this point we’ve done a good amount of work on eutester documentation in general, although it’s looking like we won’t be able to complete the project entirely with the semester coming to an end. I’m also disappointed I wasn’t even able to develop any actual code to fix the issues on the Github issues tracker which I was planning on doing after the documentation project was finished. However, I feel good that we were able to help the creators of eucalyptus and I hope what we’ve done will assist anyone who works on the project in the future.

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

Wrapping Up Eutester Documentation

This week I’ve finished commenting on the webtestcase.py script and pushed the changes through. It was interesting running into my first conflict errors and having to pull changes from the origin master before being able to make any further pushes. So right now our group is almost done documenting the eucaweb directory with the init.py file being the only one left which I’ll try to finish documenting next week. At this point we’ve done a good amount of work on eutester documentation in general, although it’s looking like we won’t be able to complete the project entirely with the semester coming to an end. I’m also disappointed I wasn’t even able to develop any actual code to fix the issues on the Github issues tracker which I was planning on doing after the documentation project was finished. However, I feel good that we were able to help the creators of eucalyptus and I hope what we’ve done will assist anyone who works on the project in the future.

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

Wrapping Up Eutester Documentation

This week I’ve finished commenting on the webtestcase.py script and pushed the changes through. It was interesting running into my first conflict errors and having to pull changes from the origin master before being able to make any further pushes. So right now our group is almost done documenting the eucaweb directory with the init.py file being the only one left which I’ll try to finish documenting next week. At this point we’ve done a good amount of work on eutester documentation in general, although it’s looking like we won’t be able to complete the project entirely with the semester coming to an end. I’m also disappointed I wasn’t even able to develop any actual code to fix the issues on the Github issues tracker which I was planning on doing after the documentation project was finished. However, I feel good that we were able to help the creators of eucalyptus and I hope what we’ve done will assist anyone who works on the project in the future.

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