The region table is relatively new, and no one has stepped up to link the two together. A couple considerations:
A) a data migration will need to be performed to sync up the regions in the endpoint table with regions in the region table (populate those foreign keys, creating corresponding regions where necessary) B) endpoints are created today without requiring a region to be created; this workflow will have to continue for v2 and v3 (regions need to be created dynamically) On Thu, Jun 19, 2014 at 12:38 PM, Manickam, Kanagaraj < kanagaraj.manic...@hp.com> wrote: > Hi, > > > > In keystone, though “region” table is provided, it is not consumed in the > “endpoint” table. I have filed bug > https://bugs.launchpad.net/keystone/+bug/1332196 to address the same. > > > > Can anyone please provide details on, why this disconnect between endpoint > and region table. > > > > Thanks > > Kanagaraj M > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
