<div dir="ltr">Hi guys!<div><br></div><div>I agreed with Stan suggestion. We also need to track somewhere in the documentation for mapping between the Murano version and <span id="4bff78d9-a1b5-49a4-b10e-0e54389784f0" class="GINGER_SOFTWARE_mark">Dynamic UI</span> version.</div>
<div><br></div><div>BTW, what about to keep version values in integer, so the next one would be 3?</div><div><br></div><div>Regards, Kate.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Jul 6, 2014 at 4:21 PM, Stan Lagun <span dir="ltr"><<a href="mailto:slagun@mirantis.com" target="_blank">slagun@mirantis.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I we increment version to say 2.1 we could add code to dashboard to check for markup version and if it encounters version 2.0 to print verbose error telling how to migrate markup to 2.1.<div>
I don't see how both version can be supported simulteniously but at lease Version attribute must be checked and forms older version must fail with descriptive message rather than causing unpredictable behavior.</div>
</div><div class="gmail_extra"><br clear="all"><div><div dir="ltr"><span style="border-collapse:separate;color:rgb(0,0,0);font-family:'Times New Roman';font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium"><span style="font-family:arial;font-size:small">Sincerely yours,<br>
Stan Lagun<br>Principal Software Engineer @ Mirantis</span></span><br><span style="border-collapse:separate;color:rgb(0,0,0);font-family:'Times New Roman';font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium"><span style="font-family:arial;font-size:small"><br>
<a href="mailto:slagun@mirantis.com" target="_blank"></a></span></span></div></div><div><div class="h5">
<br><br><div class="gmail_quote">On Fri, Jul 4, 2014 at 8:24 PM, Timur Sufiev <span dir="ltr"><<a href="mailto:tsufiev@mirantis.com" target="_blank">tsufiev@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi, folks!<br>
<br>
Recently we had decided to change a bit how Murano's dynamic UI works,<br>
namely do not explicitly specify 'name' field in first 'Add<br>
Application' form, but add it here automatically, since every<br>
component in Murano has a name. To avoid confusion with the 'name'<br>
field added by hand to the first form's markup, 'name' field on the<br>
first step will be forbidden and processing of an old UI markup which<br>
has such field will cause an exception. All these changes are<br>
described in the blueprint [1] in a greater detail.<br>
<br>
What is not entirely clear to me is whether should we increase<br>
'Version' attribute of UI markup or not? On one hand, the format of UI<br>
markup is definitely changing - and old UI definitions won't work with<br>
the UI processor after [1] is implemented. It is quite reasonable to<br>
bump a format's version to reflect that fact. On the other hand, we<br>
will hardly support both format versions, instead we'll rewrite UI<br>
markup in all existing Murano Apps (there are not so many of them yet)<br>
and eventually forget that once upon a time the user needed to specify<br>
'name' field explicitly.<br>
<br>
What do you think?<br>
<br>
[1] <a href="https://blueprints.launchpad.net/murano/+spec/dynamic-ui-specify-no-explicit-name-field" target="_blank">https://blueprints.launchpad.net/murano/+spec/dynamic-ui-specify-no-explicit-name-field</a><br>
<span><font color="#888888"><br>
--<br>
Timur Sufiev<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</font></span></blockquote></div><br></div></div></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>