[openstack-dev] [all][Kingbird]Multi-Region Orchestrator
pratapagoutham at gmail.com
Wed Jan 31 18:17:19 UTC 2018
Thanks for the questions.. :)
What precisely do you mean by "resources" above ??
Resources as-in resources required to boot-up a vm (Keypair, Image, Flavors
Also, by "syncing", do you mean "replicating"? The reason I ask is because
in the case of, say, VM "resources", you can't "sync" a VM across regions.
You can replicate its bootable image, but you can't "sync" a VM's state
across multiple OpenStack deployments.
Yes as you said syncing as-in replicating only.
and yes we cannot sync vm's across regions but our idea is to
sync/replicate all the parameters required to boot a vm
(viz. *image, keypair, flavor*) which are originally there in the source
region to the target regions in a single-go.
I'm curious what you mean by "resource management". Could you elaborate a
bit on this?
Resource management as-in managing the resources i.e say a user has a
glance image(*qcow2 or ami format*) or
say flavor(*works only if admin*) with some properties or keypair present
in one source region and he wants the same image or
same flavor with same properties or the same keypair in another set of
regions user may have to recreate them in all target regions.
But with the help of kingbird you can do all the operations in a single go.
--> If user wants to sync a resource of type keypair he can replicate the
keypair into multiple target regions in single go (similarly glance images
and flavors )
--> If user wants different type of resource( keypair,image and flavor) in
a single go then user can give a yaml file as input and kingbird
replicates all resources in all target regions
On Wed, Jan 31, 2018 at 9:25 PM, Jay Pipes <jaypipes at gmail.com> wrote:
> On 01/31/2018 01:49 AM, Goutham Pratapa wrote:
>> *Kingbird (The Multi Region orchestrator):*
>> We are proud to announce kingbird is not only a centralized quota and
>> resource-manager but also a Multi-region Orchestrator.
>> *Use-cases covered:
>> *- Admin can synchronize and periodically balance quotas across regions
>> and can have a global view of quotas of all the tenants across regions.
>> - A user can sync a resource or a group of resources from one region to
>> other in a single go
> What precisely do you mean by "resources" above?
> Also, by "syncing", do you mean "replicating"? The reason I ask is because
> in the case of, say, VM "resources", you can't "sync" a VM across regions.
> You can replicate its bootable image, but you can't "sync" a VM's state
> across multiple OpenStack deployments.
> A user can sync multiple key-pairs, images, and flavors from one region
>> to other, ( Flavor can be synced only by admin)
>> - A user must have complete tempest test-coverage for all the
>> scenarios/services rendered by kingbird.
>> - Horizon plugin so that user can access/view global limits.
>> * Our Road-map:*
>> -- Automation scripts for kingbird in
>> -- Add SSL support to kingbird
>> -- Resource management in Kingbird-dashboard.
> I'm curious what you mean by "resource management". Could you elaborate a
> bit on this?
> -- Kingbird in a docker
>> -- Add Kingbird into Kolla.
>> We are looking out for*_contributors and ideas_* which can enhance
>> Kingbird and make kingbird a one-stop solution for all multi-region problems
>> *_Stable Branches :_
>> Kingbird-server: https://github.com/openstack/kingbird/tree/stable/queens
>> *Python-Kingbird-client (0.2.1): https://github.com/openstack/p
>> ython-kingbirdclient/tree/0.2.1 <https://github.com/openstack/
>> I would like to Thank all the people who have helped us in achieving this
>> milestone and guided us all throughout this Journey :)
>> Goutham Pratapa
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscrib
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev