<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 05/08/2017 01:45 PM, Marios Andreou
wrote:<br>
</div>
<blockquote
cite="mid:CAM51kHUEzV00OPQ70=sX35ZtWOdKw9qS4OrCmJLuh4aYYHYvJQ@mail.gmail.com"
type="cite">
<div dir="ltr">Hi folks, after some discussion locally with
colleagues about improving the upgrades experience, one of the
items that came up was pre-upgrade and update validations. I
took an AI to look at the current status of tripleo-validations
[0] and posted a simple WIP [1] intended to be run before an
undercloud update/upgrade and which just checks service status.
It was pointed out by shardy that for such checks it is better
to instead continue to use the per-service manifests where
possible like [2] <span style="font-size:12.8px">for example
where we check status before N..O major upgrade. There may
still be some undercloud specific validations that we can land
into the tripleo-validations repo (thinking about things like
the neutron networks/ports, validating the current nova nodes
state etc?).</span></div>
</blockquote>
Yes, I think a bunch of validation: db states, services states,
network connectivity (external, internal)<br>
<blockquote
cite="mid:CAM51kHUEzV00OPQ70=sX35ZtWOdKw9qS4OrCmJLuh4aYYHYvJQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div><span style="font-size:12.8px"><br>
</span></div>
<div><span style="font-size:12.8px">So do folks have any
thoughts about this subject - for example the kinds of
things we should be checking - Steve said he had some
reviews in progress for collecting the overcloud ansible
puppet/docker config into an ansible playbook that the
operator can invoke for upgrade of the 'manual' nodes (for
example compute in the N..O workflow) - the point being that
we can add more per-service ansible validation tasks into
the service manifests for execution when the play is run by
the operator - but I'll let Steve point at and talk about
those. </span></div>
<div><br>
</div>
</div>
</blockquote>
I have a WIP review about that [1], but i need to revisit it a bit,
to add a part into the mistral workflow (Im also writing a POC to
create a mistral workbook for major upgrade and validate minor/major
upgrade before starting [2], I have a third one in progress, not
pushed yet, to implement the major upgrade option in the cli):<br>
<pre wrap=""><a class="moz-txt-link-freetext" href="https://review.openstack.org/444224">[1] https://review.openstack.org/444224</a>
[2] <a class="moz-txt-link-freetext" href="https://review.openstack.org/#/c/462961">https://review.openstack.org/#/c/462961</a>
</pre>
<br>
<blockquote
cite="mid:CAM51kHUEzV00OPQ70=sX35ZtWOdKw9qS4OrCmJLuh4aYYHYvJQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>cheers, marios</div>
<div><br>
</div>
<div>
<div>
<div>
<div>[0] <a moz-do-not-send="true"
href="https://github.com/openstack/tripleo-validations">https://github.com/openstack/tripleo-validations</a> </div>
<div>[1] <a moz-do-not-send="true"
href="https://review.openstack.org/#/c/462918/">https://review.openstack.org/#/c/462918/</a></div>
</div>
<div>[2] <span style="font-size:12.8px"> </span><a
moz-do-not-send="true"
href="https://github.com/openstack/"><a class="moz-txt-link-freetext" href="https://github.com/openstack/">https://github.com/openstack/</a></a><wbr>tripleo-heat-templates/blob/<wbr>stable/ocata/puppet/services/<wbr>neutron-api.yaml#L197 </div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
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>
<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>
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>