[openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

Tomas Sedovic tsedovic at redhat.com
Tue Dec 22 17:17:03 UTC 2015

On 12/22/2015 04:36 PM, Dougal Matthews wrote:
> Hi all,
> This topic came up in the 2015-12-15 meeting[1], and again briefly today.
> After working with the code that came out of the deployment library
> spec[2] I
> had some concerns with how we are storing the templates.
> For alternatives, I see a can think of a couple of options:
> - Use a database, like we did for Tuskar and most OpenStack API's do.
> - Invest time in building something on Swift.
> - Glance was transitioning to be a Artifact store. I don't know the
> status of
>    this or if it would meet out needs.
> Any input, ideas or suggestions would be great!

This is probably worth mentioning:


If this extension to the API goes through, it may add some weight to the 
database option.

At minimum, we'd have to store the validation results somewhere and be 
able to query them per stage, validation and (optionally) plan. That 
could be done in Swift or filesystem/git as well, but we'd have to write 
code to handle indexing and querying and at that point using a DB seems 

Tomas Sedovic

> Thanks,
> Dougal
> [1]:
> http://eavesdrop.openstack.org/meetings/tripleo/2015/tripleo.2015-12-15-14.03.log.html#l-89
> [2]:
> https://specs.openstack.org/openstack/tripleo-specs/specs/mitaka/tripleo-overcloud-deployment-library.html
> [3]: https://review.openstack.org/#/c/257481/
> __________________________________________________________________________
> 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