Request #2020

Replacing oZones by an onezoned API proxy

Added by Simon Boulet about 8 years ago. Updated over 7 years ago.

Status:ClosedStart date:05/10/2013
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-
Pull request:

Description

Have a proxy between the oned API (ex. onezoned service). Replace VM / Host IDs by 64-bits long IDs with the first bits used to identify the OpenNebula instances. Ex. VM 1234 on the first instance could become VM 1000001234 , the same VM on the second instance 20000001234 etc. Hook Sunstone directly through the proxy for transparent management of multiple OpenNebula installation. Perhaps have Sunstone detect you're running on top of onezoned (instead of oned directly, perhaps by checking one.system.config or adding a one.system.ozones call to list zones) and add a dropdown to filter results / switch between instances.

History

#1 Updated by Ruben S. Montero about 8 years ago

  • Tracker changed from Feature to Request
  • Category set to 18

#2 Updated by Daniel Dehennin over 7 years ago

+1 if I understand correctly this request.

I did not test zones, I just read the documentation and I do not like the “modify apache configuration for each zone”.

Making a service, with the zones descriptions in the database ease the failover/load-balancing.

  • run 3 onezoned service on 3 machines
  • run 5 nginx with their upstreams to the 3 onezoned

Regards.

#3 Updated by Ruben S. Montero over 7 years ago

We are to completely redesign ozones, to accommodate this and other requests. I'll close this once we have an issue for the new ozones, so it can be linked to this request.

#4 Updated by Ruben S. Montero over 7 years ago

  • Status changed from Pending to Closed

This is going to be implemented for 4.6 as part of the redesign of ozones. We'll keep some IDs local to each oned (zone) while others global and shared across oneds (zones).

We are also adding a zone selector to target the proxy to the desired oned, as suggested in the description.

Closing this, probably #2665 is a good link for this issue, although the functionality described here has been split in several issues.

Also available in: Atom PDF