<div dir="ltr">I've added my blog to the OpenStack blog feed and I've published a post about switching/upgrading to Fernet [0].<div><br></div><div>I'm not sure when it will propagate to the OpenStack blog, but I published it yesterday. Hopefully this helps!</div><div><div><br></div><div><br></div><div>[0] <a href="http://lbragstad.com/what-you-need-to-know-about-keystones-new-default-token-format/">http://lbragstad.com/what-you-need-to-know-about-keystones-new-default-token-format/</a></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 7, 2016 at 9:46 AM, Matt Fischer <span dir="ltr"><<a href="mailto:matt@mattfischer.com" target="_blank">matt@mattfischer.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">How to add yourself to Planet OpenStack: <a href="https://wiki.openstack.org/wiki/AddingYourBlog" target="_blank">https://wiki.<wbr>openstack.org/wiki/<wbr>AddingYourBlog</a><div><br></div><div>As for SuperUser you could reach out to them if you think it's interesting for users/operators. Generally they'll want to publish it there first then you follow-up with your blog post a few days later.</div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Mon, Nov 7, 2016 at 8:17 AM, Lance Bragstad <span dir="ltr"><<a href="mailto:lbragstad@gmail.com" target="_blank">lbragstad@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr">That's a good idea. Is there a page detailing the process for contributing to the OpenStack Blog? I did some checking but haven't found any resources yet. I also asked in #openstack and #openstack-doc.</div><div class="m_7393856730609134935HOEnZb"><div class="m_7393856730609134935h5"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Nov 3, 2016 at 11:04 AM, Rochelle Grober <span dir="ltr"><<a href="mailto:rochelle.grober@huawei.com" target="_blank">rochelle.grober@huawei.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div>a blog post on the OpenStack sore might be good. superuser? there are folks reading this who can help<br>
<br>
Sent from HUAWEI AnyOffice<br>
</div>
<div name="AnyOffice-Background-Image" style="border-top:1px solid #b5c4df;font-size:14px;line-height:20px;padding:8px">
<div style="word-break:break-all"><b>From:</b>Lance Bragstad</div>
<div style="word-break:break-all"><b>To:</b>OpenStack Development Mailing List (not for usage questions),<a href="mailto:openstack-operators@lists.openstack.org" target="_blank">openstack-operators<wbr>@lists.openstack.org</a>,</div>
<div style="word-break:break-all"><b>Date:</b>2016-11-03 08:11:20</div>
<div style="word-break:break-all"><b>Subject:</b>Re: [openstack-dev] [keystone][tripleo][ansible][p<wbr>uppet][all] changing default token format</div>
<div><br>
</div>
</div><div><div class="m_7393856730609134935m_346324029907425257h5">
<div>
<div dir="ltr">I totally agree with communicating this the best we can. I'm adding the operator list to this thread to increase visibility.
<div><br>
</div>
<div>If there are any other methods folks think of for getting the word out, outside of what we've already done (release notes, email threads, etc.), please let me know. I'd be happy to drive those communications.</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Nov 3, 2016 at 9:45 AM, Alex Schultz <span dir="ltr">
<<a href="mailto:aschultz@redhat.com" target="_blank">aschultz@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hey Steve,<br>
<span><br>
On Thu, Nov 3, 2016 at 8:29 AM, Steve Martinelli <<a href="mailto:s.martinelli@gmail.com" target="_blank">s.martinelli@gmail.com</a>> wrote:<br>
> Thanks Alex and Emilien for the quick answer. This was brought up at the<br>
> summit by Adam, but I don't think we have to prevent keystone from changing<br>
> the default. TripleO and Puppet can still specify UUID as their desired<br>
> token format; it is not deprecated or slated for removal. Agreed?<br>
><br>
<br>
</span>My email was not to tell you to stop.I was just letting you know that<br>
your change does not affect the puppet modules because we define our<br>
default as UUID. It was just as a heads up to others on this email<br>
that this change should not affect anyone consuming the puppet modules<br>
because our default is still UUID and will be even after keystone's<br>
default changes.<br>
<br>
Thanks,<br>
-Alex<br>
<div class="m_7393856730609134935m_346324029907425257m_1377278771804089471HOEnZb">
<div class="m_7393856730609134935m_346324029907425257m_1377278771804089471h5"><br>
> On Thu, Nov 3, 2016 at 10:23 AM, Alex Schultz <<a href="mailto:aschultz@redhat.com" target="_blank">aschultz@redhat.com</a>> wrote:<br>
>><br>
>> Hey Steve,<br>
>><br>
>> On Thu, Nov 3, 2016 at 8:11 AM, Steve Martinelli <<a href="mailto:s.martinelli@gmail.com" target="_blank">s.martinelli@gmail.com</a>><br>
>> wrote:<br>
>> > As a heads up to some of keystone's consuming projects, we will be<br>
>> > changing<br>
>> > the default token format from UUID to Fernet. Many patches have merged<br>
>> > to<br>
>> > make this possible [1]. The last 2 that you probably want to look at are<br>
>> > [2]<br>
>> > and [3]. The first flips a switch in devstack to make fernet the<br>
>> > selected<br>
>> > token format, the second makes it default in Keystone itself.<br>
>> ><br>
>> > [1] <a href="https://review.openstack.org/#/q/topic:make-fernet-default" rel="noreferrer" target="_blank">
https://review.openstack.org/#<wbr>/q/topic:make-fernet-default</a><br>
>> > [2] DevStack patch: <a href="https://review.openstack.org/#/c/367052/" rel="noreferrer" target="_blank">
https://review.openstack.org/#<wbr>/c/367052/</a><br>
>> > [3] Keystone patch: <a href="https://review.openstack.org/#/c/345688/" rel="noreferrer" target="_blank">
https://review.openstack.org/#<wbr>/c/345688/</a><br>
>> ><br>
>><br>
>> Thanks for the heads up. In puppet openstack we had already<br>
>> anticipated this and attempted to do the same for the<br>
>> puppet-keystone[0] module as well. Unfortunately after merging it, we<br>
>> found that tripleo wasn't yet prepared to handle the HA implementation<br>
>> of fernet tokens so we had to revert it[1]. This shouldn't impact<br>
>> anyone currently consuming puppet-keystone as we define uuid as the<br>
>> default for now. Our goal is to do something similar this cycle but<br>
>> there needs to be some further work in the downstream consumers to<br>
>> either define their expected default (of uuid) or support fernet key<br>
>> generation correctly.<br>
>><br>
>> Thanks,<br>
>> -Alex<br>
>><br>
>> [0] <a href="https://review.openstack.org/#/c/389322/" rel="noreferrer" target="_blank">
https://review.openstack.org/#<wbr>/c/389322/</a><br>
>> [1] <a href="https://review.openstack.org/#/c/392332/" rel="noreferrer" target="_blank">
https://review.openstack.org/#<wbr>/c/392332/</a><br>
>><br>
>> ><br>
>> > ______________________________<wbr>______________________________<wbr>______________<br>
>> > OpenStack Development Mailing List (not for usage questions)<br>
>> > Unsubscribe:<br>
>> > <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">
OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
>> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">
http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
>> ><br>
>><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.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">
http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
><br>
><br>
><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.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">
http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
><br>
<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.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div></div></div>
</blockquote></div><br></div>
</div></div><br></div></div>______________________________<wbr>_________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.open<wbr>stack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-operators</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br></div>