Open Stack

Hi,

1) +1 for warning

2) I don't think that we should delete tasks, it's a history which can be
useful,
for example for stats feature, also it's useful for debugging, but each task
should have created_at and updated_at fields, and from api you will be able
to get the latest tasks for specific env.

Thanks,

On Thu, Jan 15, 2015 at 7:20 PM, Vitaly Kramskikh <vkramskikh at 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-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150116/02bdd8cf/attachment.html>