Store the validations in Swift

[Tomas Sedovic]

This has been suggested as a followup to the initial validation implementation. Instead of having the validations called from a known disk location like we do now, we would keep them in Swift (similar to the way TripleO Heat templates are used).

[vikrant (ervikrant06)]

Can you please help me to understand the advantage of keeping the validations in swift instead of default location and running it from swift object ?

AFAIK THT are kept in default location /usr/share/openstack-tripleo-heat-templates/and overcloud swift object is getting created during the installation of overcloud.

[Tomas Sedovic (tsedovic)]

Sorry for taking so long to respond.

You are correct that the initial THT are seeded from disk during the undercloud installation, but after that everything happens in Swift. When you do a deployment, it's the Swift templates that are used. If you want to add/change a template, you need to do it in Swift.

This proposes doing the same for the validations.

Here's a few reasons:

1. The UI can't access the disk but it can talk to Swift so if we want to manipulate the validations (e.g. adding new ones, showing their contents, etc.) it's easier this way

2. At some point we want to have a highly available undercloud and at that point, we don't want the disks to be the primary locations of data, because we'd have to sync everything and it would lead to problems. Having Swift be the single source of truth lets us avoid this.

3. We can have additional tools that read/process the data without having to be running on the undercloud

These are basically the same reasons that led to Swift being the primary storage for THT and this just follows suit.

I know this will add another layer of indirection and will make things more complex which is not making me happy either. But it makes sense here.

[Ana Krivokapić (akrivoka)]

Moved to bp https://blueprints.launchpad.net/tripleo/+spec/store-validations-in-swift