[openstack-dev] [E] [TripleO] scripts to do post deployment analysis of an overcloud

Hugh Brock hbrock at redhat.com
Mon Aug 8 14:35:58 UTC 2016


On Mon, Aug 8, 2016 at 4:02 PM, Tomas Sedovic <tsedovic at redhat.com> wrote:
> On 08/08/2016 11:05 AM, Hugh Brock wrote:
>>
>> On Wed, Aug 3, 2016 at 4:49 PM, Joe Talerico <jtaleric at redhat.com> wrote:
>>>
>>> On Wed, Jul 27, 2016 at 2:04 AM, Hugh Brock <hbrock at redhat.com> wrote:
>>>>
>>>> On Jul 26, 2016 8:08 PM, "Gordon, Kent"
>>>> <Kent.Gordon at verizonwireless.com>
>>>> wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Gonéri Le Bouder [mailto:goneri at lebouder.net]
>>>>>> Sent: Tuesday, July 26, 2016 12:24 PM
>>>>>> To: openstack-dev at lists.openstack.org
>>>>>> Subject: [E] [openstack-dev] [TripleO] scripts to do post deployment
>>>>>> analysis
>>>>>> of an overcloud
>>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> For the Distributed-CI[0] project, we did two scripts[1] that we use
>>>>>> to
>>>>>> extract
>>>>>
>>>>>
>>>>> Links not included in message
>>>>>
>>>>>> information from an overcloud.
>>>>>> We use this information to improve the readability of the deployment
>>>>>> logs.
>>>>>> I attached an example to show how we use the extracted stack
>>>>>> information.
>>>>>>
>>>>>> Now my question, do you know some other tools that we can use to do
>>>>>> this
>>>>>> kind of anaylsis?
>>>>>> --
>>>>>> Gonéri Le Bouder
>>>>>
>>>>>
> <snip>
>>
>>
>> Tomaš, this seems like it might be useful for the deploy validations,
>> and also for improving the quality of error reporting -- would you
>> mind taking a look?
>
>
> Yeah we may end up using the heat stack dump tool for some validations since
> it puts all the Heat data in one place.
>
> However, this seems like a great thing to be included in the openstack
> overcloud deploy command and/or the mistral workflow.
>
> I.e. after each deployment, we could run list_nodes_status to verify that
> the overcloud nodes are indeed running and accessible (before tempest) and
> dump the o-c-c logs to a known directory.

Cool!

Also don't forget about sbaker's amazing new error reporting tool
"openstack stack failures list overcloud" -- might be useful...

--Hugh


-- 
  ,       ,    | Hugh Brock, hbrock at redhat.com
  )-_"""_-(    | Director of Engineering, OpenStack Management
 ./ o\ /o \.   | TripleO: Install, configure, and scale OpenStack.
. \__/ \__/ .  | http://rdoproject.org, http://tripleo.org
...   V   ...  |
... - - - ...  | "I know that you believe you understand what you
 .   - -   .   | think I said, but I'm not sure you realize that what
  `-.....-´    | you heard is not what I meant." --Robert McCloskey
 "TripleOwl"



More information about the OpenStack-dev mailing list