<div dir="ltr">-1 for using kernel parameters for configuring the whole master node installation. User should be able to edit configuration and then re-deploy the master node. I have no idea what would UX look like if we used kernel paramenters.</div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div>Vladimir Kozhukalov</div></div></div>
<br><div class="gmail_quote">On Thu, Jul 23, 2015 at 7:49 PM, Vladimir Kozhukalov <span dir="ltr"><<a href="mailto:vkozhukalov@mirantis.com" target="_blank">vkozhukalov@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">The topic is NOT 'get rid of validation' but rather 'get rid of semi-graphical ncurses based interface'. It is not so hard to adopt every piece of validation we currently have in fuelmenu and implement even more including syntax validation using, for example, PLY and logic validation. My idea is to switch from ncurses to plain text file (thoroughly commented), because it so easy to add new parameters or remove those we don't need any more.<span class="HOEnZb"><font color="#888888"><div><br></div><div><br></div><div><br></div></font></span></div><div class="gmail_extra"><span class="HOEnZb"><font color="#888888"><br clear="all"><div><div><div>Vladimir Kozhukalov</div></div></div>
<br></font></span><div class="gmail_quote"><div><div class="h5">On Thu, Jul 23, 2015 at 6:17 PM, Nick Chase <span dir="ltr"><<a href="mailto:nchase@mirantis.com" target="_blank">nchase@mirantis.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
<div bgcolor="#FFFFFF" text="#000000"><span>
<br>
<br>
<blockquote type="cite">
<div class="gmail_extra">
<div class="gmail_quote">On Thu, Jul 23, 2015 at 4:05 PM,
Matthew Mosesohn <span dir="ltr"><<a href="mailto:mmosesohn@mirantis.com" target="_blank"></a><a href="mailto:mmosesohn@mirantis.com" target="_blank">mmosesohn@mirantis.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Here's a
relic of what users used to have to configure by<br>
hand:<br>
<a href="https://github.com/stackforge/fuel-library/blob/b015ed975b58dddff3b8da0ce34d9a638c22d032/deployment/puppet/openstack/examples/site_simple.pp" rel="noreferrer" target="_blank">https://github.com/stackforge/fuel-library/blob/b015ed975b58dddff3b8da0ce34d9a638c22d032/deployment/puppet/openstack/examples/site_simple.pp</a><br>
<br>
Am I alone in thinking it's not the best use of our
development<br>
resources to throw it away and replace it with a text file
that is<br>
edited by hand?<br>
</blockquote>
</div>
</div>
</blockquote>
<br></span>
Please, please, please, I'm having PTSD just remembering that
@#$%@#%$ file. I think I was able to successfully deploy without
major engineering help about 2% of the time. We absolutely,
positively, MUST maintain the validation.<br>
<br>
Just because the people installing OpenStack are generally not
afraid to edit config files doesn't mean that we should be making
them do it.<span><font color="#888888"><br>
<br>
---- Nick<br>
</font></span></div>
<br></div></div><span class="">__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></span></blockquote></div><br></div>
</blockquote></div><br></div>