> I really don't like setting the error message as the default one in > the DB schema and consider it as a last resort solution. If > possible update the message to error one just before you start > to build the image.
+1. > What about add some check or some message > "Fuel-master Deployment in progress, please wait %s" ? I don't like this idea, since I believe it's something that user shouldn't care at all. I see two possible *right* appraoch to handle this: 1. We keep it As Is, and say "user should not use Fuel until Fuel Master deployment is finished". 2. We make API / Web UI unaccessible externally until Fuel Master is deployed (e.g. iptables rules or nginx ones). What do you say? - Igor On Wed, Dec 16, 2015 at 12:00 PM, Aleksey Zvyagintsev <azvyagint...@mirantis.com> wrote: > Actually, its gloval problem : > UI accessible for user earlier then deployment has been done. I think we > should also handle this somehow - otherwise user can start doing "some > things" like spawning HW - and fail . > What about add some check or some message "Fuel-master Deployment in > progress, please wait %s" ? > > > > > On Tue, Dec 15, 2015 at 6:56 PM, Vitaly Kramskikh <vkramsk...@mirantis.com> > wrote: >> >> Hi, >> >> I really don't like setting the error message as the default one in the DB >> schema and consider it as a last resort solution. If possible update the >> message to error one just before you start to build the image. >> >> 2015-12-15 18:48 GMT+03:00 Artur Svechnikov <asvechni...@mirantis.com>: >>> >>> Hi folks, >>> Recently was introduced special notification about absented bootstrap >>> image. >>> >>> Currently this notification is sent from fuel-bootstrap-cli. It means >>> that error message will not be sent when failure occurs before first >>> building (like in [1]). I think it will be better to set error message on >>> WebUI by default through fixtures and then remove it if first build is >>> successful. >>> >>> Please share your opinions about this issue. >>> >>> [1] https://bugs.launchpad.net/fuel/+bug/1526351 >>> >>> Best regards, >>> Svechnikov Artur >>> >>> >>> __________________________________________________________________________ >>> 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 >>> >> >> >> >> -- >> Vitaly Kramskikh, >> Fuel UI Tech Lead, >> Mirantis, Inc. >> >> __________________________________________________________________________ >> 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 >> > > > > -- > --- > Best regards, > Aleksey Zvyagintsev > > __________________________________________________________________________ > 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
