Hello, Here's my 2 cents on it.
I think the effort we put to support fuelmenu doesn't worth it. I used to deploy fuel too often in previous release, and I never used features of fuelmenu? Why? Because I prefer to apply changes on already deployed node. Moreover, I don't like that users are prompted with fuelmenu by default. I want to deploy fuel automatically, without any manual actions (though it's another topic). I'm agree with Vladimir, vim + config files are enough, since Fuel is not a product for housewives. It's a product for those who do not hesitate to use Vim for soft configuration. Thanks, Igor On Thu, Jul 23, 2015 at 2:27 PM, Matthew Mosesohn <mmoses...@mirantis.com> wrote: > We had that before and had very poor validation. Removing fuelmenu > would make the experience quite manual and prone to errors. > > This topic comes up once a year only from Fuel Python developers > because they rarely use it and no dev cycles have been invested in > improving it. > > The actual Fuel deployers use it and appreciate its validation and > wish to extend it. > > I'd like to hear more feedback. > > On Thu, Jul 23, 2015 at 2:23 PM, Vladimir Kozhukalov > <vkozhuka...@mirantis.com> wrote: >> Dear colleagues, >> >> What do you think of getting rid of fuelmenu and substituting it with >> thoroughly commented text file + some validation + vim? The major pro of >> this is that text file is easier to extend and edit. Many people prefer vim >> UX instead of wandering through the semi-graphical interface. And it is not >> so hard to implement syntax and logic checking for the text file. >> >> Please give your opinions about this. >> >> Vladimir Kozhukalov >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: openstack-dev-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev