Open Stack

On Mon, May 15, 2017 at 7:27 PM, Steven Hardy <shardy at redhat.com> wrote:

> On Mon, May 08, 2017 at 02:45:08PM +0300, Marios Andreou wrote:
> >    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]Â 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?).
> >    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.Â
>
> Thanks for starting this thread Marios, sorry for the slow reply due to
> Summit etc.
>
> As we discussed, I think adding validations is great, but I'd prefer we
> kept any overcloud validations specific to services in t-h-t instead of
> trying to manage service specific things over multiple repos.
>
> This would also help with the idea of per-step validations I think, where
> e.g you could have a "is service active" test and run it after the step
> where we expect the service to start, a blueprint was raised a while back
> asking for exactly that:
>
> https://blueprints.launchpad.net/tripleo/+spec/step-by-step-validation
>
>
thanks for this we can use it one less to file :D

and ack on the overcloud vs undercloud - sounds like tripleo-validations is
the right place/folks agree in general to having some ansible tasks there
to validate _stuff_ (thanks very much @bnemec and @emilien for suggestions

thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170517/ad6dfd20/attachment.html>