Joshua Harlow 09a369ae1b Attach log listeners to other engines
Attach the created task/flow/engine listener to
the other usages of taskflow that exist in cinder
so that those locations can also benefit from
the same logging of state and activity.

Part of blueprint task-logging

Change-Id: I4ba7fe625a88967607adaa18d329bec56825201c
2014-06-20 19:09:48 -07:00
2014-04-16 08:16:30 -03:00
2014-04-25 18:31:06 +03:00
2013-11-28 09:52:23 +00:00
2012-05-03 10:48:26 -07:00
2014-05-07 12:03:15 -07:00
2013-06-14 14:02:17 +00:00
2012-05-03 10:48:26 -07:00
2012-11-22 12:47:49 -07:00
2012-05-03 10:48:26 -07:00
2012-08-10 11:56:00 -04:00
2012-05-03 10:48:26 -07:00
2014-03-27 11:14:52 +01:00
2014-05-22 07:04:39 +00:00

The Choose Your Own Adventure README for Cinder

You have come across a storage service for an open cloud computing service. It has identified itself as "Cinder." It was abstracted from the Nova project.

To monitor it from a distance: follow @openstack on twitter.

To tame it for use in your own cloud: read http://docs.openstack.org

To study its anatomy: read http://cinder.openstack.org

To dissect it in detail: visit http://github.com/openstack/cinder

To taunt it with its weaknesses: use http://bugs.launchpad.net/cinder

To watch it: http://jenkins.openstack.org

To hack at it: read HACKING.rst

Description
OpenStack Block Storage (Cinder)
Readme 913 MiB
Languages
Python 99.7%
Smarty 0.3%