<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>Hi, Andrew</div><div><br></div><div>Agreed with your opinion. Initially Savanna’s templates approach is the option 1 you are talking about. </div><div>This was designed at the start of Savanna 0.2 release cycle. It was also documented here: <a href="https://wiki.openstack.org/wiki/Savanna/Templates">https://wiki.openstack.org/wiki/Savanna/Templates</a> . </div><div>Maybe some points are outdated but the idea is the same as the option 1: user can create cluster template and don’t need to specify all fields, for example ’node_groups’ field. And these fields, both required and optional, can be overwritten in the cluster object even if it contains ‘cluster_template_id’.</div><div><br></div><div>I see you raised this question because of patch <a href="https://review.openstack.org/#/c/56060/">https://review.openstack.org/#/c/56060/</a>. I think it’s just a bug in the validation level not in api.</div><div><br></div><div>I also agree that we should change UI part accordingly, at least add an ability for users to override fields set in cluster and node group templates during the cluster creation.</div><br><div>
<div>Regards,</div><div>Alexander Ignatov</div><div><br></div><br class="Apple-interchange-newline">
</div>
<br><div><div>On 12 Nov 2013, at 23:20, Andrey Lazarev <<a href="mailto:alazarev@mirantis.com">alazarev@mirantis.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Hi all,<div><br></div><div>I want to raise the question "What template is". Answer to this question could influence UI, validation and user experience significantly. I see two possible answers:</div>
<div><span style="font-family: 'Arial Unicode MS', Arial, sans-serif;">1. Template is a simplification for object creation. It allows to keep common params in one place and not specify them each time. </span></div>
<div><span style="font-family: 'Arial Unicode MS', Arial, sans-serif;">2. Template is a full description of object. User should be able to create object from template without specifying any params.</span></div>
<div><span style="font-family: 'Arial Unicode MS', Arial, sans-serif;"><br></span></div><div><span style="font-family: 'Arial Unicode MS', Arial, sans-serif;">As I see the current approach is the option 1, but UI is done mostly for option 2. This leads to situations when user creates incomplete template (backend allows it because of option 1), but can't use it later (UI doesn't allow to work with incomplete templates).</span></div>
<div><span style="font-family: 'Arial Unicode MS', Arial, sans-serif;"><br></span></div><div><font face="Arial Unicode MS, Arial, sans-serif">Let's define common vision on how will we treat templates and document this somehow.</font></div>
<div><font face="Arial Unicode MS, Arial, sans-serif"><br></font></div><div><font face="Arial Unicode MS, Arial, sans-serif">My opinion is that we should proceed with the option 1 and change UI accordingly. </font></div>
<div><br></div><div>Thanks,</div><div>Andrew</div></div>
_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></blockquote></div><br></body></html>