On 7/16/18 6:32 PM, Dan Prince wrote:
On Mon, Jul 16, 2018 at 11:27 AM Cédric Jeanneret wrote:
Dear Stackers,
In order to let operators properly validate their undercloud node, I
propose to create a new subcommand in the "openstack undercloud" "tree":
`openstack undercloud validate'
This
Dear Stackers,
Seeing the answers on and off-list, we're moving forward!
So, here are the first steps:
A blueprint has been created:
https://blueprints.launchpad.net/tripleo/+spec/validation-framework
I've started a draft of the spec, based on the feedbacks and discussions
I could have:
I opened this RFE: https://bugzilla.redhat.com/show_bug.cgi?id=1601739
Regards,
Udi Kalifon; Senior QE; RHOS-UI Automation
On Tue, Jul 17, 2018 at 8:42 AM, Cédric Jeanneret
wrote:
>
>
> On 07/17/2018 06:57 AM, Udi Kalifon wrote:
> > We should also add support for the openstack client to
On 07/17/2018 06:57 AM, Udi Kalifon wrote:
> We should also add support for the openstack client to launch the other
> validators that are used in the GUI. There are validators for the
> overcloud as well, and new validators are added all the time.
>
> These validators are installed under
>
Hi
Dear Stackers,
In order to let operators properly validate their undercloud node, I
propose to create a new subcommand in the "openstack undercloud" "tree":
`openstack undercloud validate'
This should only run the different validations we have in the
undercloud_preflight.py
That way, an
We should also add support for the openstack client to launch the other
validators that are used in the GUI. There are validators for the overcloud
as well, and new validators are added all the time.
These validators are installed under
/usr/share/openstack-tripleo-validations/validations/ and
On Mon, Jul 16, 2018 at 11:27 AM Cédric Jeanneret wrote:
>
> Dear Stackers,
>
> In order to let operators properly validate their undercloud node, I
> propose to create a new subcommand in the "openstack undercloud" "tree":
> `openstack undercloud validate'
>
> This should only run the different
Dear Stackers,
In order to let operators properly validate their undercloud node, I
propose to create a new subcommand in the "openstack undercloud" "tree":
`openstack undercloud validate'
This should only run the different validations we have in the
undercloud_preflight.py¹
That way, an