Hi, Jay, >From exactly definition, it's not full "independent" concept.
The KeyStone services will be distributed into each data center, so if one data center failed, the identity management especially token validation can work still in other data centers. That's one case studied in OPNFV multisite project. There is difference between " An end user is able to import image from another Glance in another OpenStack cloud while sharing same identity management( KeyStone )" and other use cases. The difference is the image import need to reuse the token in the source Glance, other ones don't need this. Best Regards Chaoyi Huang ( Joe Huang ) -----Original Message----- From: Jay Pipes [mailto:jaypi...@gmail.com] Sent: Friday, February 19, 2016 10:43 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [glance]one more use case for Image Import Refactor from OPNFV On 02/18/2016 08:34 PM, joehuang wrote: > Hello, > > Glad to know that the "Image Import Refactor" is the essential BP in > Mitaka. One more use case from OPNFV as following: > > In OPNFV, one deployment scenario is each data center will be deployed > with independent OpenStack instance, but shared identity management. That's not independent OpenStack instances. > That means there will be one Glance with its backend in each datacenter. > This is to make each datacenter can work standalone as much as > possible, even others crashed. If the identity management is shared, it's not standalone. Best, -jay __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
