[one-users] OpenNebula multi-site --- question
Carlos Martín Sánchez
cmartin at opennebula.org
Fri Jan 18 03:02:50 PST 2013
Hi,
The oZones component [1] offers a centralized way to manage different
OpenNebula instances, a single entry point for users of the different
zones, and a mechanism to divide each zone in small administrative domains
(Virtual Data Centers).
But each zone is not aware of the other ones, and you cannot move resources
between them.
The kind of high availability that you describe can be enabled within each
OpenNebula instance though, using the fault tolerance hooks [2] you can
redeploy the VMs that were running on a crashed Host.
Best regards.
[1] http://opennebula.org/documentation:rel3.8:ozones
[2] http://opennebula.org/documentation:rel3.8:ftguide
--
Carlos Martín, MSc
Project Engineer
OpenNebula - The Open-source Solution for Data Center Virtualization
www.OpenNebula.org | cmartin at opennebula.org |
@OpenNebula<http://twitter.com/opennebula><cmartin at opennebula.org>
On Thu, Jan 17, 2013 at 6:23 PM, Giovanni Ponti <giovanni.ponti at enea.it>wrote:
> Il 17/01/2013 17:15, Ignacio M. Llorente ha scritto:
>
> Dear Giovanni,
>>
>> This is a very good question, which answer depends on the type and level
>> of collaboration that you expect across the different sites. I envision
>> three different architectures:
>>
>> - Loosely Coupled Federation: Each site has its own OpenNebula instance
>> managed by its Admin team that exposes cloud APIs (OCCI/EC2) and GUIs.
>> In this scenario you could share a single authentication mechanism so a
>> user can have access to any of the clouds, or you could define a user
>> space for each site. You could also install your own appliance
>> marketplace to allow users to easily share appliances across sites.
>>
>> - Tightly Coupled Federation: Each site has its own OpenNebula instance,
>> all of them are managed by the same Admin team, and you use the oZones
>> component for federation. In this case you will provide your users with
>> a single access point for all the zones and can allocate resources
>> through Virtual Data Centers to different Departments/Projects, etc.
>>
>> - Hybrid Cloud Federation: Each site has its own OpenNebula instance
>> managed by its Admin team that exposes cloud APIs (OCCI/EC2) and GUIs. A
>> user can only access its primary site, and the access to remote clouds
>> is performed by the cloudbursting functionality of OpenNebula which is
>> managed by the administrator of the site, and in principle fully
>> transparent to the user. This would require the adaptation of the cloud
>> connector to support remote OpenNebula instances.
>>
>> I hope this helps,
>>
>> Thanks!
>>
>>
> Thanks for your reply! Many aspects are clear now.
>
> Nevertheless, I've a futher question regardering the vm
> migration/live-migration mechanism in a Tightly Coupled Federation, that
> seems to be the most suitable for our purposes.
> In particular, what happens to the VMs deployed on physical nodes in a
> oZones if such resources go down? Is the system able to migrate VMs to
> another oZone that shares the same repository area?
>
> Thanks again,
> Giovanni
>
>
>
> On Thu, Jan 17, 2013 at 12:00 PM, Giovanni Ponti <giovanni.ponti at enea.it
>> <mailto:giovanni.ponti at enea.it**>> wrote:
>>
>> I'm Giovanni Ponti, an ENEA researcher based in Portici Research
>> Center.
>> One of my research interest is Cloud Computing, and I'm following
>> and organizing cloud experiences in ENEA-GRID.
>>
>> We are planning to have a multi-site cloud envorinment among ENEA
>> computational centers (that are six). At the moment, we have
>> installed OpenNebula only in one site (i.e., Portici one), and we
>> are evaluating a further installation on another ENEA site.
>>
>> My question regards the ways in which two (or more) OpenNebula
>> installation may communicate and/or interact to export a whole
>> integrated cloud enviroment. In particular, as I know that
>> OpenNebula provides several interfaces to export cloud facilities
>> and to perform remote action (e.g., OCCI), it is not particularly
>> clear how aspect ragardering virtual machines are handled, such as
>> vm migration among sites or other.
>>
>> Thanks in advance for your reply(s)
>>
>> Giovanni
>>
>>
>> --
>> Ing. Giovanni Ponti, PhD
>> UTICT-HPC
>> ENEA - C.R. Portici
>> P.le E. Fermi, 1 (Loc. Granatello)
>> 80055 Portici (NA), Italy
>> phone : (+39) 081-7723564 <tel:%28%2B39%29%20081-**7723564> | int.:
>> [89] 2564
>> fax : (+39) 081-7723344 <tel:%28%2B39%29%20081-**7723344>
>> email : giovanni.ponti at enea.it <mailto:giovanni.ponti at enea.it**>
>> web : http://www.afs.enea.it/gponti
>> ______________________________**___________________
>> Users mailing list
>> Users at lists.opennebula.org <mailto:Users at lists.**opennebula.org<Users at lists.opennebula.org>
>> >
>> http://lists.opennebula.org/__**listinfo.cgi/users-opennebula.**__org<http://lists.opennebula.org/__listinfo.cgi/users-opennebula.__org>
>>
>> <http://lists.opennebula.org/**listinfo.cgi/users-opennebula.**org<http://lists.opennebula.org/listinfo.cgi/users-opennebula.org>
>> >
>>
>>
>>
>>
>> --
>> Ignacio M. Llorente, PhD, MBA
>> Project Director
>> OpenNebula - The Open Source Solution for Data Center Virtualization
>> www.OpenNebula.org <http://www.OpenNebula.org> |
>> imllorente at opennebula.org <mailto:imllorente at opennebula.**org<imllorente at opennebula.org>>
>> | @OpenNebula
>>
>
> --
> Ing. Giovanni Ponti, PhD
> UTICT-HPC
> ENEA - C.R. Portici
> P.le E. Fermi, 1 (Loc. Granatello)
> 80055 Portici (NA), Italy
> phone : (+39) 081-7723564 | int.: [89] 2564
> fax : (+39) 081-7723344
> email : giovanni.ponti at enea.it
> web : http://www.afs.enea.it/gponti
> ______________________________**_________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/**listinfo.cgi/users-opennebula.**org<http://lists.opennebula.org/listinfo.cgi/users-opennebula.org>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20130118/c5b53239/attachment-0002.htm>
More information about the Users
mailing list