Store validations in Swift

Registered by Ana Krivokapić on 2018-02-09

(Converting from bug https://bugs.launchpad.net/tripleo/+bug/1625545)

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).

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.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Medium
Drafter:
Ana Krivokapić
Direction:
Needs approval
Assignee:
Ana Krivokapić
Definition:
Approved
Series goal:
Accepted for rocky
Implementation:
Implemented
Milestone target:
milestone icon rocky-3
Started by
Ana Krivokapić on 2018-04-25
Completed by
Ana Krivokapić on 2018-07-11

Related branches

Sprints

Whiteboard

[2018-07-11] All reviews merged

[2018-04-09] No update for Rocky. Moving to future. Please update and move back to Rocky if this will be worked on.

Gerrit topic: https://review.openstack.org/#q,topic:bp/store-validations-in-swift,n,z

Addressed by: https://review.openstack.org/564160
    Add an action to upload validations to Swift

Addressed by: https://review.openstack.org/564233
    Upload validations to swift on undercloud install

Addressed by: https://review.openstack.org/564254
    Upload validations to swift on undercloud install

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.