[openstack-dev] [Glare][Heat][Tacker][Murano][App-Catalog] [Glance] How to validate your binary data in OpenStack

Flavio Percoco flavio at redhat.com
Wed Jul 27 11:30:46 UTC 2016

On 25/07/16 20:03 -0400, Nikhil Komawar wrote:
>Thanks for your nice message Mikhail.
>I, however, wanted to address a small correction to avoid any further
>presumptions about Glare, Glance and Images API with the tags associated
>in the email subject herewith. (also adding Glance tag to the list to
>ensure we reach the appropriate Images related audience).

Allow me to further nitpick on the tags. It'd be better to just use Glance as
tag for these emails and make Glare just part of the rest of the subject. This
disctinction is important as these tags are used to filter emails and Glare is
not really an independent project but part of Glance.

(sorry for the nitpick but I thought I'd take this chance to share it)
Keep it up, folks.

>On 7/25/16 2:26 PM, Mikhail Fedosin wrote:
>> Hello! Today I want to discuss with community one good feature in
>> Glare - artifact validation. In short Glare allows to validate binary
>> data before it's uploaded to store. For example, for Tosca we're able
>> to check if uploaded yaml is a valid template [1], for vm images we
>> can test their integrity. For sure, Glare supports quite sophisticated
>> workflows, like sending murano packages to external CI
>While this feature looks nothing less than excellent, it is unfortunate
>that the Images API is built into Glance -- meaning Glance will remain
>the reference implementation of the OpenStack Images API for the near to
>long future. So, while it may be possible to test integrity of data
>assets, it won't be possible for any operator/user/API-consumer to use
>Glare for Images as Glance will remain the whole and sole API for Images
>and all future features need to be implemented therein.
>The reasons for this have been discussed briefly in the proposal
>(review) of the Glare spec and in related conversations. If anyone needs
>more info, please reach out.
>> or validate Heat templates with given environments.
>> So, I want to think out what validation is exactly required from Glare
>> and how we can help related projects to succeed, checking and reliably
>> storing their binary assets.
>> Best regards,
>> Mikhail Fedosin
>> [1]
>> https://review.openstack.org/#/c/337633/10/contrib/glare/openstack_app_catalog/artifacts.py@159
>> __________________________________________________________________________
>> 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
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe

Flavio Percoco
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 847 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160727/a739447b/attachment.pgp>

More information about the OpenStack-dev mailing list