Entries in 'grid deployment'

Next Page »

rPath Enables Cloud Computing for DoE, CERN

From http://www.gridtoday.com/grid/2370981.html

rPath Enables Cloud Computing for DoE, CERN

RALEIGH, N.C., June 4 — rPath, whose unique technology simplifies application distribution and management through virtual appliances, today announced that the U.S. Department of Energy (DOE) and the European Organization for Nuclear Research (CERN) have been using rBuilder to deliver virtual appliances to both scientists’ desktops and computational clouds. The use of rBuilder in these environments reduces the effort required to support users and allows researchers to take advantage of underutilized computational resources.

rBuilder is the first and only product that simplifies and automates the creation of virtual appliances. A virtual appliance is an application with a streamlined operating system, offered in a format that runs in virtualized environments.

CERN turned to virtual appliances to facilitate the analysis of data created by the Large Hadron Collider (LHC) experiments. The complete software environment needed by the LHC applications is assembled by rBuilder and distributed to run as a virtual machine on physicists’ desktops. Virtual appliances provide a consistent application environment for the LHC applications while, at the same time, allowing scientists to use their desktops for analysis, regardless of operating system.

“The coupling between the LHC applications and the operating system is very strong,” stated Predrag Buncic, virtualization R&D project leader. “By distributing these applications as virtual appliances, we are able to isolate the application from the underlying desktop or laptop operating system, allowing the researchers to run the applications on systems that normally would not be supported.”

The DOE is exploring the concept of using virtual appliances to provide customized environments for scientific applications. Scientific applications are turned into virtual appliances using rPath’s rBuilder. The “Science Clouds” project (http://workspace.globus.org/clouds) provides resources capable of hosting multiple scientific appliances using the Globus Virtual Workspaces software. Scientists submit their virtual appliances to any available resource, knowing that the application environment is controlled and isolated from the underlying system. By relying on portable appliances, the scientists can leverage the resources of science clouds, and seamlessly move to commercial providers, such as Amazon’s EC2, when additional resources are needed.

“For a proof-of-concept, anybody can just configure a virtual machine image by hand,” said Kate Keahey, a scientist at Argonne National Laboratory. “But providing appliance management and maintenance that will scale to many thousands of appliances and that will be truly interoperable between different resource providers requires a new approach.”

About rPath

For application providers that want to accelerate license growth, expand into new markets, and reduce support and development costs, rPath’s platform transforms applications into virtual appliances. A virtual appliance is an application combined with just enough operating system (JeOS) for it to run optimally in any virtualized environment. Virtual appliances eliminate the hassles of installing, configuring and maintaining complex application environments. Only rPath’s technology simplifies application distribution, lowers the customer service costs of maintenance and management, and produces multiple virtual machine formats. The company is headquartered in Raleigh, N.C. For more information, visit www.rpath.com.

—–

Source: rPath

Stratus Cloud at the University of Florida

From workspace-announce:

I am happy to announce the availability of a science cloud (codenamed “Stratus” ;-) at the University of Florida. This cloud introduces a new feature: the use of virtual networks with virtual machines for cloud computing.

The cloud is available for members of the scientific community: to obtain access you will need to provide a justification (a few sentences explaining your science project) to cloud administrators at UFL. To find out more go to:

http://workspace.globus.org/clouds/

The cloud is currently deployed on a modest allocation of resources as a beta project. We welcome comments, feedback, and bug reports.

Cloud lock-in is not such a big deal

There’s been a lot of talk about the dangers of getting locked in to cloud platforms, developing an application that is only suited to one platform.

Here’s a, let’s say… “embellished” example: Gangsta cloud wars could pivot on the traffic-driving power of Google and Microsoft/Yahoo.

When you’re using VMs like Xen (e.g. on EC2), if you design things for it you “should be able to” move without a ton of hassle (research. plan.). The workspace project has been working on portability and usability (see The first one-click STAR production cluster) and one of the things we can do now is use the same VM image on a regular cluster (such as on the Teraport cloud) and EC2. The contextualization software can be configured to sense if it is on EC2 or not (and will bootstrap accordingly). It “would be nice” if such things were standardized but this is not a real problem right now (IMHO).

About something more “strongly typed” like Google’s AppEngine. Application migration might be a bit harder, but not if the APIs are well known and repeatable. Google’s SDK is even Apache 2 licensed.

To that point, have a look at Announcing AppDrop.com (host Google App Engine projects on EC2). It’s not there yet (database is a flat file) but, hey, it was developed in a few days. Cool. Read more at http://appdrop.com.

The long term idea is not that this would solve all your problems magically but that such things are possible, and if there’s a real market for choices, it seems like more work on things of this nature are also inevitable.

I’m no datacenter business expert, but the biggest problem right now seems to be that few people will be able to compete on costs/efficiencies of scale with Google/Amazon/Microsoft/eBay. (<predictions…>) It feels like it would naturally approach the straight web hosting business, though. Let’s say a standard, open source cloud computing infrastructure emerges (such as Apache httpd in the analogy). There will be various levels of players as far as the capital they have and certainly better and worse companies to choose from (including those that differentiate on service etc). But if you’re really sweating the savings an enormous company could provide with such efficiencies vs. a normal size company/datacenter, you’re probably at the point where you could save a whole lot more by buying your own computers.(</predictions…>)

Miscellaneous point about lock-in: something user-facing that ties you to a provider does not seem like a wise idea (e.g. Google’s Users API).

Amazon EC2 persistent storage

EC2 announced future support for adding raw, persistent block devices to VMs, a few non-Amazon people are even testing it already.

See Werner Vogels and this RightScale post.

TeraGrid planning site

Old news, but here’s an interesting website: Online Home for the TeraGrid Planning Process. In particular, the Position Papers section.

Google launches application hosting

They’ve taken the application level approach (Python currently).

And unlike Sun’s attempt (which also needed porting of app to a platform instead of the looser requirements of EC2 style), there is an interesting entry incentive:

“It’s free to get started. Every Google App Engine application can use up to 500MB of persistent storage and enough bandwidth and CPU for 5 million monthly page views.”

http://code.google.com/appengine/

http://code.google.com/appengine/docs/whatisgoogleappengine.html

http://googleappengine.blogspot.com/2008/04/introducing-google-app-engine-our-new.html

http://appgallery.appspot.com/

http://groups.google.com/group/google-appengine

Nimbus: The University of Chicago Science Cloud

If you’re on the workspace-announce list, you will have already seen the “Science Cloud Available at the University of Chicago” email.

Built with the workspace service, we’ve made some nice client enhancements to get to “cloud simplicity” and it’s up and running on 16 nodes and already serving guests. See the the documentation for command samples, the idea is to make it as simple as possible. On the service side, Nimbus uses TP1.3.1 with some very small additions (mostly this differs because of a new authorization plugin). Building cloud computing solutions is the main business of the workspace service.

Have a look!

GridShib SAML Tools v0.3.0

We are pleased to announce GridShib SAML Tools v0.3.0, the final release in the v0.3.0 development cycle:

http://gridshib.globus.org/docs/gridshib-saml-tools-0.3.0/readme.html

http://gridshib.globus.org/download.html#saml-tools

The GridShib SAML Tools are a suite of standalone client tools that issue SAML assertions and optionally bind these assertions to X.509 proxy certificates. To try out the software before downloading, visit our online demo:

https://computer.ncsa.uiuc.edu/gst-demo/

The GridShib SAML Tools require only Java 1.4 (or later) and Ant 1.6 (or later). Proxy certificates issued by the SAML Tools are compatible with GridShib for Globus Toolkit v0.6.0 Alpha (or later).

There have been significant changes in this version of the GridShib SAML Tools since the previous release:

http://gridshib.globus.org/docs/gridshib-saml-tools-0.3.0/CHANGES.txt

Important new features of GridShib SAML Tools v0.3.0 include:

  • enhanced command-line interface
  • new command-line options for the SAML Assertion Issuer Tool, including the option to output a DER-encoded ASN.1 structure
  • new X.509 Binding Tool, to bind arbitrary content to a non-critical extension of an X.509 proxy certificate
  • new SAML Security Info Tool, for examining the contents of X.509-bound SAML tokens
  • expanded Java API, for producing and consuming SAML assertions and X.509 proxy certificates
  • support for the TeraGrid Science Gateway Use Case

This development cycle was largely driven by the TeraGrid Science Gateway Use Case:

http://gridshib.globus.org/docs/gridshib-saml-tools-0.3.0/teragrid/readme.html

Science Gateways use the SAML Tools to enable auditing, incident response, and access control in Globus-based grids.

To learn more about this and other use cases, visit the “About GridShib” page:

http://gridshib.globus.org/about.html

While the GridShib SAML Tools produce X.509-bound SAML tokens, the complementary software component GridShib for Globus Toolkit consumes them. The latter is scheduled for release later this month or early next. See the roadmap on the GridShib home page for the latest updates.

Tom Scavo
For the GridShib Team


Next Page »