<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">2018-01-17 0:29 GMT+08:00 Emilien Macchi <span dir="ltr"><<a target="_blank" href="mailto:emilien@redhat.com">emilien@redhat.com</a>></span>:<br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">Here's an update so we can hopefully, as a community, take a decision<br>
in the next days or so.<br>
<br>
<br>
* Migration to StoryBoard<br>
<br>
Champion: Kendall Nelson<br>
<a target="_blank" rel="noreferrer" href="https://review.openstack.org/#/c/513875/">https://review.openstack.org/#<wbr>/c/513875/</a><br>
Some projects already migrated, some projects will migrate soon but<br>
there is still a gap of things that prevents some projects to not<br>
migrate.<br>
See <a target="_blank" rel="noreferrer" href="https://storyboard.openstack.org/#%21/search?tags=blocking-storyboard-migration">https://storyboard.openstack.<wbr>org/#!/search?tags=blocking-<wbr>storyboard-migration</a><br>
For that reason, we are postponing this goal to later but work needs<br>
to keep going to make that happen one day.<br>
<br>
<br>
* Remove mox<br>
<span class="gmail-"><br>
Champion: Sean McGinnis (unless someone else steps up)<br>
</span><a target="_blank" rel="noreferrer" href="https://review.openstack.org/#/c/532361/">https://review.openstack.org/#<wbr>/c/532361/</a><br>
This goal is to clean some technical debt in the code.<br>
It remains a good candidate for Queens.<br>
<br>
<br>
* Ensure pagination links<br>
<br>
Champion: Monty Taylor<br>
<a target="_blank" rel="noreferrer" href="https://review.openstack.org/#/c/532627/">https://review.openstack.org/#<wbr>/c/532627/</a><br>
This one would improve API users experience.<br>
It remains a good candidate for Queens.<br>
<br>
<br>
* Enable mutable configuration<br>
Champion: ChangBo Guo<br>
Nothing was proposed in governance so far and we have enough proposals<br>
now, I guess it could be a candidate for a future cycle though. This<br>
one would make happy our operators.<br>
<br></blockquote><div> This is the review in governance <a href="https://review.openstack.org/534605">https://review.openstack.org/534605</a><br></div><div> This change really benefit users, hope this can be finished in Rocky.<br></div><div><br> </div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
<br>
* Cold upgrades capabilities<br>
Champion: Masayuki Igawa<br>
<a target="_blank" rel="noreferrer" href="https://review.openstack.org/#/c/533544/">https://review.openstack.org/#<wbr>/c/533544/</a><br>
This one would be appreciated by our operators who always need<br>
improvements on upgrades experience - I believe it would be a good<br>
candidate.<br>
<br>
<br>
Note: some projects requested about having less goals so they have<br>
more time to work on their backlogs. While I agree with that, I would<br>
like to know who asked exactly, and if they would be affected by the<br>
goals or not.<br>
It will help us to decide which ones we take.<br>
<br>
So now, it's really a good time to speak-up and say if:<br>
- your project could commit to 2 of these goals or not (and why? backlog? etc)<br>
- which ones you couldn't commit to<br>
- the ones you prefer<br>
<br>
We need to take a decision as a community, not just TC members, so<br>
please bring feedback.<br>
<br>
Thanks,<br>
<div class="gmail-HOEnZb"><div class="gmail-h5"><br>
<br>
On Fri, Jan 12, 2018 at 2:19 PM, Lance Bragstad <<a href="mailto:lbragstad@gmail.com">lbragstad@gmail.com</a>> wrote:<br>
><br>
><br>
> On 01/12/2018 11:09 AM, Tim Bell wrote:<br>
>> I was reading a tweet from Jean-Daniel and wondering if there would be an appropriate community goal regarding support of some of the later API versions or whether this would be more of a per-project goal.<br>
>><br>
>> <a target="_blank" rel="noreferrer" href="https://twitter.com/pilgrimstack/status/951860289141641217">https://twitter.com/<wbr>pilgrimstack/status/<wbr>951860289141641217</a><br>
>><br>
>> Interesting numbers about customers tools used to talk to our @OpenStack APIs and the Keystone v3 compatibility:<br>
>> - 10% are not KeystoneV3 compatible<br>
>> - 16% are compatible<br>
>> - for the rest, the tools documentation has no info<br>
>><br>
>> I think Keystone V3 and Glance V2 are the ones with APIs which have moved on significantly from the initial implementations and not all projects have been keeping up.<br>
> Yeah, I'm super interested in this, too. I'll be honest I'm not quite<br>
> sure where to start. If the tools are open source we can start<br>
> contributing to them directly.<br>
>><br>
>> Tim<br>
>><br>
>> -----Original Message-----<br>
>> From: Emilien Macchi <<a href="mailto:emilien@redhat.com">emilien@redhat.com</a>><br>
>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.<wbr>openstack.org</a>><br>
>> Date: Friday, 12 January 2018 at 16:51<br>
>> To: OpenStack Development Mailing List <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.<wbr>openstack.org</a>><br>
>> Subject: Re: [openstack-dev] [all] [tc] Community Goals for Rocky<br>
>><br>
>> Here's a quick update before the weekend:<br>
>><br>
>> 2 goals were proposed to governance:<br>
>><br>
>> Remove mox<br>
>> <a target="_blank" rel="noreferrer" href="https://review.openstack.org/#/c/532361/">https://review.openstack.org/#<wbr>/c/532361/</a><br>
>> Champion: Sean McGinnis (unless someone else steps up)<br>
>><br>
>> Ensure pagination links<br>
>> <a target="_blank" rel="noreferrer" href="https://review.openstack.org/#/c/532627/">https://review.openstack.org/#<wbr>/c/532627/</a><br>
>> Champion: Monty Taylor<br>
>><br>
>> 2 more goals are about to be proposed:<br>
>><br>
>> Enable mutable configuration<br>
>> Champion: ChangBo Guo<br>
>><br>
>> Cold upgrades capabilities<br>
>> Champion: Masayuki Igawa<br>
>><br>
>><br>
>> Thanks everyone for your participation,<br>
>> We hope to make a vote within the next 2 weeks so we can prepare the<br>
>> PTG accordingly.<br>
>><br>
>> On Tue, Jan 9, 2018 at 10:37 AM, Emilien Macchi <<a href="mailto:emilien@redhat.com">emilien@redhat.com</a>> wrote:<br>
>> > As promised, let's continue the discussion and move things forward.<br>
>> ><br>
>> > This morning Thierry brought the discussion during the TC office hour<br>
>> > (that I couldn't attend due to timezone):<br>
>> > <a target="_blank" rel="noreferrer" href="http://eavesdrop.openstack.org/irclogs/%23openstack-tc/latest.log.html#t2018-01-09T09:18:33">http://eavesdrop.openstack.<wbr>org/irclogs/%23openstack-tc/<wbr>latest.log.html#t2018-01-<wbr>09T09:18:33</a><br>
>> ><br>
>> > Some outputs:<br>
>> ><br>
>> > - One goal has been proposed so far.<br>
>> ><br>
>> > Right now, we only have one goal proposal: Storyboard Migration. There<br>
>> > are some concerns about the ability to achieve this goal in 6 months.<br>
>> > At that point, we think it would be great to postpone the goal to S<br>
>> > cycle, continue the progress (kudos to Kendall) and fine other goals<br>
>> > for Rocky.<br>
>> ><br>
>> ><br>
>> > - We still have a good backlog of goals, we're just missing champions.<br>
>> ><br>
>> > <a target="_blank" rel="noreferrer" href="https://etherpad.openstack.org/p/community-goals">https://etherpad.openstack.<wbr>org/p/community-goals</a><br>
>> ><br>
>> > Chris brought up "pagination links in collection resources" in api-wg<br>
>> > guidelines theme. He said in the past this goal was more a "should"<br>
>> > than a "must".<br>
>> > Thierry mentioned privsep migration (done in Nova and Zun). (action,<br>
>> > ping mikal about it).<br>
>> > Thierry also brought up the version discovery (proposed by Monty).<br>
>> > Flavio proposed mutable configuration, which might be very useful for operators.<br>
>> > He also mentioned that IPv6 support goal shouldn't be that far from<br>
>> > done, but we're currently lacking in CI jobs that test IPv6<br>
>> > deployments (question for infra/QA, can we maybe document the gap so<br>
>> > we can run some gate jobs on ipv6 ?)<br>
>> > (personal note on that one, since TripleO & Puppet OpenStack CI<br>
>> > already have IPv6 jobs, we can indeed be confident that it shouldn't<br>
>> > be that hard to complete this goal in 6 months, I guess the work needs<br>
>> > to happen in the projects layouts).<br>
>> > Another interesting goal proposed by Thierry, also useful for<br>
>> > operators, is to move more projects to assert:supports-upgrade tag.<br>
>> > Thierry said we are probably not that far from this goal, but the<br>
>> > major lack is in testing.<br>
>> > Finally, another "simple" goal is to remove mox/mox3 (Flavio said most<br>
>> > of projects don't use it anymore already).<br>
>> ><br>
>> > With that said, let's continue the discussion on these goals, see<br>
>> > which ones can be actionable and find champions.<br>
>> ><br>
>> > - Flavio asked how would it be perceived if one cycle wouldn't have at<br>
>> > least one community goal.<br>
>> ><br>
>> > Thierry said we could introduce multi-cycle goals (Storyboard might be<br>
>> > a good candidate).<br>
>> > Chris and Thierry thought that it would be a bad sign for our<br>
>> > community to not have community goals during a cycle, "loss of<br>
>> > momentum" eventually.<br>
>> ><br>
>> ><br>
>> > Thanks for reading so far,<br>
>> ><br>
>> > On Fri, Dec 15, 2017 at 9:07 AM, Emilien Macchi <<a href="mailto:emilien@redhat.com">emilien@redhat.com</a>> wrote:<br>
>> >> On Tue, Nov 28, 2017 at 2:22 PM, Emilien Macchi <<a href="mailto:emilien@redhat.com">emilien@redhat.com</a>> wrote:<br>
>> >> [...]<br>
>> >>> Suggestions are welcome:<br>
>> >>> - on the mailing-list, in a new thread per goal [all] [tc] Proposing<br>
>> >>> goal XYZ for Rocky<br>
>> >>> - on Gerrit in openstack/governance like Kendall did.<br>
>> >><br>
>> >> Just a fresh reminder about Rocky goals.<br>
>> >> A few questions that we can ask ourselves:<br>
>> >><br>
>> >> 1) What common challenges do we have?<br>
>> >><br>
>> >> e.g. Some projects don't have mutable configuration or some projects<br>
>> >> aren't tested against IPv6 clouds, etc.<br>
>> >><br>
>> >> 2) Who is willing to drive a community goal (a.k.a. Champion)?<br>
>> >><br>
>> >> note: a Champion is someone who volunteer to drive the goal, but<br>
>> >> doesn't commit to write the code necessarily. The Champion will<br>
>> >> communicate with projects PTLs about the goal, and make the liaison if<br>
>> >> needed.<br>
>> >><br>
>> >> The list of ideas for Community Goals is documented here:<br>
>> >> <a target="_blank" rel="noreferrer" href="https://etherpad.openstack.org/p/community-goals">https://etherpad.openstack.<wbr>org/p/community-goals</a><br>
>> >><br>
>> >> Please be involved and propose some ideas, I'm sure our community has<br>
>> >> some common goals, right ? :-)<br>
>> >> Thanks, and happy holidays. I'll follow-up in January of next year.<br>
>> >> --<br>
>> >> Emilien Macchi<br>
>> ><br>
>> ><br>
>> ><br>
>> > --<br>
>> > Emilien Macchi<br>
>><br>
>><br>
>><br>
>> --<br>
>> Emilien Macchi<br>
>><br>
>> ______________________________<wbr>______________________________<wbr>______________<br>
>> OpenStack Development Mailing List (not for usage questions)<br>
>> Unsubscribe: <a target="_blank" rel="noreferrer" href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
>> <a target="_blank" rel="noreferrer" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
>><br>
>><br>
>> ______________________________<wbr>______________________________<wbr>______________<br>
>> OpenStack Development Mailing List (not for usage questions)<br>
>> Unsubscribe: <a target="_blank" rel="noreferrer" href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
>> <a target="_blank" rel="noreferrer" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
><br>
><br>
><br>
> ______________________________<wbr>______________________________<wbr>______________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a target="_blank" rel="noreferrer" href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
> <a target="_blank" rel="noreferrer" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
><br>
<br>
<br>
<br>
--<br>
Emilien Macchi<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a target="_blank" rel="noreferrer" href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a target="_blank" rel="noreferrer" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>ChangBo Guo(gcb)<br></div><div>Community Director @EasyStack<br></div></div></div></div></div>
</div></div>