<div dir="ltr">Matt,<div><br></div><div>For <span style="font-family:arial,sans-serif;font-size:13px">swift-internal</span> we are using the same keystone (and identity protocol version) as for savanna. Also savanna admin tenant is used.    <br>
<div><br></div><div>Thanks,</div><div>Andrew.</div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jan 23, 2014 at 6:17 PM, Matthew Farrellee <span dir="ltr"><<a href="mailto:matt@redhat.com" target="_blank">matt@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">what makes it internal vs external?<br>
<br>
swift-internal needs user & pass<br>
<br>
swift-external needs user & pass & ?auth url?<br>
<br>
best,<br>
<br>
<br>
matt<br>
<br>
On 01/23/2014 08:43 PM, Andrew Lazarev wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Matt,<br>
<br>
I can easily imagine situation when job binaries are stored in external<br>
HDFS or external SWIFT (like data sources). Internal and external swifts<br>
are different since we need additional credentials.<br>
<br>
Thanks,<br>
Andrew.<br>
<br>
<br>
On Thu, Jan 23, 2014 at 5:30 PM, Matthew Farrellee <<a href="mailto:matt@redhat.com" target="_blank">matt@redhat.com</a><br>
<mailto:<a href="mailto:matt@redhat.com" target="_blank">matt@redhat.com</a>>> wrote:<br>
<br>
    trevor,<br>
<br>
    job binaries are stored in swift or an internal savanna db,<br>
    represented by swift-internal:// and savanna-db:// respectively.<br>
<br>
    why swift-internal:// and not just swift://?<br>
<br>
    fyi, i see mention of a potential future version of savanna w/<br>
    swift-external://<br>
<br>
    best,<br>
<br>
<br>
    matt<br>
<br>
    ______________________________<u></u>___________________<br>
    OpenStack-dev mailing list<br>
    OpenStack-dev@lists.openstack.<u></u>__org<br>
    <mailto:<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.<u></u>openstack.org</a>><br>
    <a href="http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack-dev" target="_blank">http://lists.openstack.org/__<u></u>cgi-bin/mailman/listinfo/__<u></u>openstack-dev</a> <<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a>><br>

<br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
<br>
</blockquote>
<br>
<br>
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
</blockquote></div><br></div>