<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000"><p>Just to clarify, the reason you want custom project IDs is so
that when you create a project in one region, you can create it
again with the same ID in another? Isn't that just manual
replication though?<br>
<br>
What happens when there are projects in only one region? Or if
that isn't meant to happen, how would you make sure that doesn't
happen?<br></p></div></blockquote><div>Not quite sure I understand the point...</div><div>Yes, this is exactly the reason why I need this feature. Project creation/replication is supposed to be done via external scripts. Currently I already have 2 slightly different use cases which definitely require this feature.</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000"><p>
</p><div><div class="h5">
<br>
<div class="m_413820465018961637moz-cite-prefix">On 06/12/16 07:20, Andrey Grebennikov
wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div class="h5">
<div dir="ltr"><span style="font-size:12.8000001907349px">Hi
keystoners,</span>
<div style="font-size:12.8000001907349px">I'd like to open the
discussion about the little feature which I'm trying to push
forward for a while but I need some
feedbacks/opinions/concerns regarding this.</div>
<div style="font-size:12.8000001907349px">Here is the review I'm
talking about <a href="https://review.openstack.org/#/c/403866/" target="_blank">https://review.openstack<wbr>.org/#/c/403866/</a></div>
<div style="font-size:12.8000001907349px"><br>
</div>
<div style="font-size:12.8000001907349px">What I'm trying to
cover is multi-region deployment, which includes
geo-distributed cloud with independent Keystone in every
region.</div>
<div style="font-size:12.8000001907349px"><br>
</div>
<div style="font-size:12.8000001907349px">There is a number of
use cases for the change:</div>
<div style="font-size:12.8000001907349px">1. Allow users to
re-use their tokens in all regions across the distributed
cloud. With global authentication (LDAP backed) and same roles
names this is only one missing piece which prevents the user
to switch between regions even withing single Horizon session.</div>
<div style="font-size:12.8000001907349px">2. Automated tools
responsible for statistics collection may access all regions
using one token (real customer's usecase)</div>
<div style="font-size:12.8000001907349px">3. Glance replication
may happen because the images' parameter "owner" (which is a
project) should be consistent across the regions.</div>
<div style="font-size:12.8000001907349px"><br>
</div>
<div style="font-size:12.8000001907349px">What I hear all time -
"you have to replicate your database" which from the
devops/deployment/operations perspective is totally wrong
approach.</div>
<div style="font-size:12.8000001907349px">If it is possible to
avoid Galera replication over geographically distributed
regions - then API calls should be used. Moreover, in case of
2 DCs there will be an issue to decide which region has to
take over when they are isolated from each other.</div>
<div style="font-size:12.8000001907349px"><br>
</div>
<div style="font-size:12.8000001907349px">There is a long
conversation in the comments of the review, mainly with
concerns from cores (purely developer's opinions).</div>
<div style="font-size:12.8000001907349px"><br>
</div>
<div style="font-size:12.8000001907349px">Please help me to
bring it to life ;)</div>
<div style="font-size:12.8000001907349px"><br>
</div>
<div style="font-size:12.8000001907349px">PS I'm so sorry,
forgot to create a topic in the original message</div>
<div><br>
</div>
-- <br>
<div class="m_413820465018961637gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">Andrey Grebennikov
<div>Principal Deployment Engineer</div>
<div>Mirantis Inc, Austin TX</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="m_413820465018961637mimeAttachmentHeader"></fieldset>
<br>
</div></div><span class=""><pre>______________________________<wbr>______________________________<wbr>______________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="m_413820465018961637moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a>
<a class="m_413820465018961637moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a>
</pre>
</span></blockquote>
<br>
</div>
<br>______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr">Andrey Grebennikov<div>Principal Deployment Engineer</div><div>Mirantis Inc, Austin TX</div></div></div></div></div>
</div></div>