+1, It will be very helpful to warn user. Not all configurations (which can be set via UI/CLI w/o yaml editing) are supported by network checker. It should be taken into account.
And we could recommend to run the check when user-defined configuration is uploaded but warn that given configuration might be not supported by network checker. Agree, this should be done on backend. Aleksey Kasatkin On Thu, Jan 15, 2015 at 10:54 PM, Lukasz Oles <lo...@mirantis.com> wrote: > Big +1, it would save me a lot of debugging time :) > > On Thu, Jan 15, 2015 at 5:20 PM, Vitaly Kramskikh > <vkramsk...@mirantis.com> wrote: > > Folks, > > > > I want to discuss possibility to add network verification status field > for > > environments. There are 2 reasons for this: > > > > 1) One of the most frequent reasons of deployment failure is wrong > network > > configuration. In the current UI network verification is completely > optional > > and sometimes users are even unaware that this feature exists. We can > warn > > the user before the start of deployment if network check failed of wasn't > > performed. > > > > 2) Currently network verification status is partially tracked by status > of > > the last network verification task. Sometimes its results become stale, > and > > the UI removes the task. There are a few cases when the UI does this, > like > > changing network settings, adding a new node, etc (you can grep > > "removeFinishedNetworkTasks" to see all the cases). This definitely > should > > be done on backend. > > > > What is your opinion on this? > > > > -- > > Vitaly Kramskikh, > > Software Engineer, > > 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 > > > > > > -- > Łukasz Oleś > > __________________________________________________________________________ > 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