<p dir="ltr">Maybe cinder can emit more notification events, then a dashboard can be build separately with the appropriate access control and filtering? The same dash can then be used for many projects - all they need to add are the events with enough metadata</p>
<div class="gmail_quote">On 10 Apr 2015 18:53, "Ben Swartzlander" <<a href="mailto:ben@swartzlander.org">ben@swartzlander.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
On 04/10/2015 08:11 AM, John Griffith wrote:<br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_default" style="font-family:monospace,monospace"><br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Apr 10, 2015 at 6:16 AM,
liuxinguo <span dir="ltr"><<a href="mailto:liuxinguo@huawei.com" target="_blank">liuxinguo@huawei.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div link="blue" vlink="purple" lang="ZH-CN">
<div>
<p class="MsoNormal"><span lang="EN-US">Hi,</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">When we create
a volume in the horizon, there may occurrs some
errors at the driver</span></p>
<p class="MsoNormal"><span lang="EN-US">backend, and
the in horizon we just see a “error” in the volume
status.</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">So is there
any way to put the error information to the
horizon so users can know what happened exactly
just from the horizon?</span></p>
<p class="MsoNormal"><span lang="EN-US"></span></p>
<p class="MsoNormal"><span lang="EN-US">Thanks,</span></p>
<p class="MsoNormal"><span lang="EN-US">Liu</span></p>
</div>
</div>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage
questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
</blockquote>
</div>
<div class="gmail_default" style="font-family:monospace,monospace">The challenge here
is that the calls to the driver are async, so we don't
actually have any direct feedback/messages regarding the
result. One thing that's been talked about in the past is
adding additional information to the status which could be
presented so that end users and tools like Horizon would
have a little more information.</div>
<div class="gmail_default" style="font-family:monospace,monospace"><br>
</div>
<div class="gmail_default" style="font-family:monospace,monospace">The trick is however
we also do NOT want driver info going back to the end user,
the whole point of Cinder is to abstract all of that backend
specific type stuff. The idea kicked around in the past was
to introduce a sub-state with a bit more detail, but still
wouldn't be anything specific from the driver.</div>
<div class="gmail_default" style="font-family:monospace,monospace"><br>
</div>
<div class="gmail_default" style="font-family:monospace,monospace">Sounds like a good
topic to revisit for the Liberty release.</div>
</div>
</div>
</blockquote>
<br>
<br>
Agreed that driver messages shouldn't reach the end user, but would
it be helpful at all to the administrator to have driver error
messages visible on the admin panel?<br>
<br>
-Ben<br>
<br>
<br>
<blockquote type="cite">
<br>
<fieldset></fieldset>
<br>
<pre>__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div>