[openstack-dev] [TripleO] Consolidating TripleO validations with Browbeat validations

Tomas Sedovic tsedovic at redhat.com
Tue Jun 21 08:59:51 UTC 2016


On 06/20/2016 08:58 PM, Assaf Muller wrote:
> On Mon, Jun 20, 2016 at 12:43 PM, Joe Talerico <jtaleric at redhat.com> wrote:
>> On Mon, Jun 20, 2016 at 12:41 PM, Ihar Hrachyshka <ihrachys at redhat.com> wrote:
>>>
>>>> On 20 Jun 2016, at 18:37, Joe Talerico <jtaleric at redhat.com> wrote:
>>>>
>>>> Hello - It would seem there is a little bit of overlap with TripleO
>>>> validations ( clapper validations ) and Browbeat *Checks*. I would
>>>> like to see these two come together, and I wanted to get some feedback
>>>> on this.
>>>>
>>>> For reference here are the Browbeat checks :
>>>> https://github.com/openstack/browbeat/tree/master/ansible/check
>>>>
>>>> We check for common deployment mistakes, possible deployment
>>>> performance issues and some bugs that could impact the scale and
>>>> performance of your cloud... At the end we build a report of found
>>>> issues with the cloud, like :
>>>> https://github.com/openstack/browbeat/blob/master/ansible/check/browbeat-example-bug_report.log
>>>>
>>>> We eventually wanted to take these findings and push them to
>>>> ElasticSearch as metadata for our result data (just so we would be
>>>> aware of any BZs or possibly missed tuning).
>>>>
>>>> Anyhoo, I just would like to get feedback on consolidating these
>>>> checks into TripleO Validations if that makes sense. If this does make
>>>> sense, who could I work with to see that this happens?
>>>
>>> Sorry for hijacking the thread somewhat, but it seems that neutron-sanity-check would cover for some common deployment issues, if utilized by projects like browbeat. Has anyone considered the tool?
>>>
>>> http://docs.openstack.org/cli-reference/neutron-sanity-check.html
>>>
>>> If there are projects that are interested in integrating checks that are implemented by neutron community, we would be glad to give some guidance.
>>>
>>> Ihar
>>
>> Hey Ihar - the TripleO validations are using this :
>> https://github.com/rthallisey/clapper/blob/0881300a815f8b801a38d117b8d01b42a00c7f7b/ansible-tests/validations/neutron-sanity-check.yaml
>
> Oops, that's missing a bunch of configuration files. Here's the
> configuration values it expects:
> https://github.com/openstack/neutron/blob/master/neutron/cmd/sanity_check.py#L32
>
> And here's how the tool uses them:
> https://github.com/openstack/neutron/blob/master/neutron/cmd/sanity_check.py#L272
>
> It runs specific checks according to configuration file values. Is
> ipset enabled in the OVS agent configuration file? Great, let's check
> we can use it and report back if there's any errors.

Aah, thanks for letting us know! I'll update the validation.

Tomas

>
>>
>>> __________________________________________________________________________
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>




More information about the OpenStack-dev mailing list