for provisioning instances. I don't think they propose compatibility with
their machine format (AMI). I believe the issue here is whether Amazon
copyrighted the interface, and even then I don't think that precludes
someone else from implementing the interface. An IP protection expert would
have to weigh in. But aside from the legalities, it's cool to see that they
made life easier for us all by implementing an already-existing API for
machine control rather than inventing a new one. Thanks guys!
It would be great if some standardization comes about for the cloud control
aspects (machine provisioning, machine location migration, etc) for those of
us that are trying to build things on top of clouds. Right now the segment
is very fractured with many vendors and products taking different approaches
and you can't even depend on the idea that people will have an instance
control system in place.
----- Original Message -----
From: "simone brunozzi" <simone.brunozzi@gmail.com>
To: <cloud-computing@googlegroups.com>
Sent: Tuesday, June 10, 2008 12:29 PM
Subject: Re: Eucaliptus
>
> Noah,
> i suppose you meant "AMI", not "API". AMI is short for Amazon Machine
> Image, and yes, Amazon uses Xen.
> From my personal, unofficial perspective, Eucalyptus is an interesting
> project, but it doesn't have much sense if you don't face lock-in
> policies. You could need Eucalyptus if, for example, the cloud
> provider was not using an open source hypervisor, such as Vmware. In
> those cases, migrating your IT infrastructure is more expensive,
> because you need to re-engineer most services. Data, instead, is
> always accessible from any cloud provider so far.
>
> Cheers,
>
> Simone
>
> Simone Brunozzi
> Amazon.com Technology Evangelist - Europe
>
> ---------------------------------------
> http://www.brunozzi.com - http://twitter.com/simone_brunozzi
> http://www.linkedin.com/in/simonebrunozzi
> ---------------------------------------
>
>
> On Tue, Jun 10, 2008 at 8:46 PM, Noah Campbell <noahcampbell@gmail.com>
> wrote:
>>
>> You need to be careful mixing open source and cloud infrastructure
>> because they don't necessarily accumulate goodness.
>>
>> For example, Amazon is rumored to run on Xen. This is an open source
>> product and could enable anyone to go forth and offer a similar
>> service like amazon without a large barrier of entry in software
>> license expenses.
>>
>> Cloud providers like Amazon are also providing an operational service
>> that goes beyond just the software. Being able to provision a virtual
>> machine, on demand, and provide SLA around QoS is a very difficult
>> problem that requires an organization that understands what they're
>> doing.
>>
>> Not to pick on RackSpace, but they represent the ISP model where they
>> provide network, HVAC, and even the hardware, but they really leave
>> the SLAs and fitness of the gear up to the customer to manage. A
>> problem comes up inside the box, it is up to the customer to detect it
>> and request its replacement.
>>
>> Cloud computing changes this demarkation of responsibility and pushes
>> into the server as well.
>>
>> Please do not take this as a poke at Eucalyptus, I think it's great to
>> start and see these cloud control systems come about. On a side note,
>> does any know if Eucalyptus can copy an API that Amazon created?
>> IANAL, but doesn't an API fall under copyright?
>>
>> -Noah
>>
>> On Jun 9, 11:29 pm, James Urquhart <jurquh...@yahoo.com> wrote:
>>> I got interested in Eucalyptus a few days ago, and know that both Don
>>> MacAskill and Dion Hinchcliffe share my excitement. Simon Wardley put
>>> up an interesting post about its possible effects on "cloud
>>> lock-in":http://blog.gardeviance.org/2008/06/open-sourced-ec2-not-by-amazon.html
>>>
>>> Eucalyptus has the opportunity to be VERY big, if they can get the
>>> community they need to drive further development. The need for an open
>>> source "alternative" cloud infrastructure platform (er, "fog computing"
>>> platform?) is huge, and one based on a widely accepted API has the best
>>> chance of success. I encourage everyone interested in seeing
>>> "portability" from Amazon to other infrastructures to check this out.
>>>
>>> Still in its infancy, to be sure, but in the right place at the right
>>> time.
>>>
>>> Has anyone downloaded it yet?
>>>
>>> James
>>>
>>> ----- Original Message ----
>>> From: Khazret Sapenov <sape...@gmail.com>
>>> To: cloud-computing@googlegroups.com
>>> Sent: Monday, June 9, 2008 2:39:58 PM
>>> Subject: Eucaliptus
>>>
>>> Interesting project, IMHO to start building your own EC2-like cloud
>>> environment
>>>
>>> http://eucalyptus.cs.ucsb.edu/wiki/EucalyptusOverview
>>> Elastic Computing, Utility Computing, and Cloud Computing are (possibly
>>> synonymous) terms referring to a popular SLA-based computing paradigm
>>> that allows users to "rent" Internet-accessible computing capacity on a
>>> for-fee basis. While a number of commercial enterprises currently offer
>>> Elastic/Utility/Cloud hosting services and several proprietary software
>>> systems exist for deploying and maintaining a computing Cloud,
>>> standards-based open-source systems have been few and far between.
>>> EUCALYPTUS -- Elastic Utility Computing Architecture for Linking Your
>>> Programs To Useful Systems -- is an open-source software infrastructure
>>> for implementing Elastic/Utility/Cloud computing using computing
>>> clusters and/or workstation farms. The current interface to EUCALYPTUS
>>> is interface-compatible with Amazon.com's EC2 (arguably the most
>>> commercially successful Cloud computing service), but the infrastructure
>>> is designed to be modified and extended so that multiple client-side
>>> interfaces can be supported. In addition, EUCALYPTUS is implemented
>>> using commonly-available Linux tools and basic web service technology
>>> making it easy to install and maintain.
>>> Overall, the goal of the EUCALYPTUS project is to foster community
>>> research and development of Elastic/Utility/Cloud service implementation
>>> technologies, resource allocation strategies, service level agreement
>>> (SLA) mechanisms and policies, and usage models. The current release is
>>> version 1.0 and it includes the following features:
>>> * Interface compatibility with EC2
>>> * Simple installation and deployment using Rocks
>>> cluster-management tools
>>> * Simple set of extensible cloud allocation policies
>>> * Overlay functionality requiring no modification to the target
>>> Linux environment
>>> * Basic "Cloud Administrator" tools for system management and
>>> user accounting
>>> * The ability to configure multiple clusters, each with private
>>> internal network addresses, into a single Cloud.
>>> The initial version of EUCALYPTUS requires Xen to be installed on all
>>> nodes that can be allocated, but no modifications to the "dom0"
>>> installation or to the hypervisor itself.
>>
>> >
>>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cloud Computing" group.
To post to this group, send email to cloud-computing@googlegroups.com
To unsubscribe from this group, send email to cloud-computing-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.ca/group/cloud-computing?hl=en
-~----------~----~----~----~------~----~------~--~---
Posts
No comments:
Post a Comment