<html><head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head><body bgcolor="#FFFFFF" text="#000000"><br>
<span>
</span><br>
<blockquote style="border: 0px none;"
cite="mid:db9d76d5-7fd0-b2fd-ceb4-d46f075bc374@gmail.com" type="cite">
<div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="width:100%;border-top:2px solid #EDF1F4;padding-top:10px;"> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:49%;">
<a moz-do-not-send="true" href="mailto:mriedemos@gmail.com"
style="color:#485664
!important;padding-right:6px;font-weight:500;text-decoration:none
!important;">Matt Riedemann</a></div> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:48%;text-align:
right;"> <font color="#909AA4"><span style="padding-left:6px">October
4, 2017 at 10:51 AM</span></font></div> </div></div>
<div style="color: rgb(144, 154, 164); margin-left: 24px;
margin-right: 24px;" __pbrmquotes="true" class="__pbConvBody"><br>
<br>What's the difference between this tag and the zero-impact-upgrades
tag?
I guess the accessible one is, can a user still ssh into their VM while
the nova compute service is being upgraded. The zero-impact-upgrade one
is more to do with performance degradation during an upgrade. I'm not
entirely sure what that might look like, probably need operator input.
For example, while upgrading, you're live migrating VMs all over the
place which is putting extra strain on the network.
<br>
<br>I think all of the tags could benefit from some examples for real
use
cases so people have context when reading them.
<br></div>
</blockquote>
We do provide tag definitions. They're linked from the Project Navigator
(e.g.
<a class="moz-txt-link-freetext" href="https://docs.openstack.org/project-team-guide/stable-branches.html">https://docs.openstack.org/project-team-guide/stable-branches.html</a>).
These provide pretty thorough definitions, and in some cases examples. I
like the idea of having additional examples per project and that's
something we could easily put into the Project Navigator.<br>
<blockquote style="border: 0px none;"
cite="mid:db9d76d5-7fd0-b2fd-ceb4-d46f075bc374@gmail.com" type="cite">
<div style="color: rgb(144, 154, 164); margin-left: 24px;
margin-right: 24px;" __pbrmquotes="true" class="__pbConvBody">
<br>Also, does the Foundation have any data on how much tags are used as
input to weigh decisions about choosing to adopt an OpenStack project in
a deployment or not?</div>
</blockquote>
One could probably make this inference based around user survey data +
which tags are used in the more vs. less popular projects. Right now,
it's not something we track, but it's an interesting point. I'll spend
some time looking at it :)
<blockquote style="border: 0px none;"
cite="mid:db9d76d5-7fd0-b2fd-ceb4-d46f075bc374@gmail.com" type="cite">
<div style="color: rgb(144, 154, 164); margin-left: 24px;
margin-right: 24px;" __pbrmquotes="true" class="__pbConvBody"> I'm not
entirely sure what the carrot and stick is
with tags or if/how people are consuming them. I don't ever think about
tags personally, probably because there is no bi-annual audit process on
them to see if we need to add/remove tags from nova.
<br></div>
</blockquote>
It's a good point. So far the biggest carrot is to make sure your
project stats look as up to date as other mature and well adopted
projects. To date, it seems to have had a positive impact in getting
projects to keep their tags updated and/or figure out what they need to
do to get the tag.
<blockquote style="border: 0px none;"
cite="mid:db9d76d5-7fd0-b2fd-ceb4-d46f075bc374@gmail.com" type="cite">
<div style="color:#909AA4;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody">
<br></div>
<div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="width:100%;border-top:2px solid #EDF1F4;padding-top:10px;"> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:49%;">
<a moz-do-not-send="true" href="mailto:sean.mcginnis@gmx.com"
style="color:#485664
!important;padding-right:6px;font-weight:500;text-decoration:none
!important;">Sean McGinnis</a></div> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:48%;text-align:
right;"> <font color="#909AA4"><span style="padding-left:6px">October
3, 2017 at 1:52 PM</span></font></div> </div></div>
<div style="color:#909AA4;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody"><div>I'm hoping this will get a
little more attention.<br><br>We recently started discussing removing
governance tags that did not have any<br>projects asserting them. I
think this makes a lot of sense. Some tags were<br>defined apparently in
the hope that it would get projects thinking about them<br>and wanting
to either apply for the tag, or do the work to be able to meet the<br>requirements
for that tag.<br><br>While this may have worked in some cases, we do
have a few that are a little<br>unclear and not really getting much
attention. We will likely clean up that<br>tag list a little, but there
was some push back on at least one tag.<br><br>The
supports-accessible-upgrade tag basically states that a service can be<br>upgraded
without affecting access to the resources that the service manages<br>[1].
This actually fits with how at least Nova and Cinder work, so a patch
is<br>now out there to assert this for those two projects [2].<br><br>I
would bet there are several other projects out there that work in this
same<br>way. Since we are looking between removing tags or using them
(use it or lose<br>it), I would actually love to see more projects
asserting this tag. If your<br>project manages a set of resources that
are available even when your service<br>is down and/or being upgraded,
please consider submitting a patch like [2] to<br>add your project to
the list.<br><br>And just a general call out to raise awareness - please
take a look through<br>the other defined tags and see if there are any
others that are applicable to<br>your projects [3].<br><br>Thanks!<br><br>Sean
(smcginnis)<br><br><br>[1]
<a class="moz-txt-link-freetext" href="https://governance.openstack.org/tc/reference/tags/assert_supports-accessible-upgrade.html">https://governance.openstack.org/tc/reference/tags/assert_supports-accessible-upgrade.html</a><br>[2]
<a class="moz-txt-link-freetext" href="https://review.openstack.org/#/c/509170/">https://review.openstack.org/#/c/509170/</a><br>[3]
<a class="moz-txt-link-freetext" href="https://governance.openstack.org/tc/reference/tags/index.html">https://governance.openstack.org/tc/reference/tags/index.html</a><br><br>__________________________________________________________________________<br>OpenStack
Development Mailing List (not for usage questions)<br>Unsubscribe:
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br><a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br></div></div>
</blockquote>
<br>
</body></html>