dashboard to make it much dumber and go through the
>> murano API for everything (which ultimately is probably a good thing).
>>
>>
>>
>> *From:* Stan Lagun [mailto:sla...@mirantis.com]
>> *Sent:* Sunday, July 20, 2014 5:42 AM
>> *To:* OpenStack Development Mailing
> murano API for everything (which ultimately is probably a good thing).
>
>
>
> *From:* Stan Lagun [mailto:sla...@mirantis.com]
> *Sent:* Sunday, July 20, 2014 5:42 AM
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [Mur
...@mirantis.com]
Sent: Sunday, July 20, 2014 5:42 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Murano] Image tagging
Hi!
I think it would be usefull to share the original vision on tagging that we had
back in 0.4 era when it was introduced
Hi!
I think it would be usefull to share the original vision on tagging that we
had back in 0.4 era when it was introduced.
Tagging was supposed to be JSON image metadata with extendable scheme.
Workflow should be able to both utilize that metadata and impose some
constraints on it. That feature w
Hi,
Images that can be used for package deployment have to be tagged in glance in
order to enable the UI to filter the list of images to present to a user (and
potentially preselect). Currently the tags are defined in the dashboard code
(images/forms.py) which makes things very inflexible; if I