Difference between revisions of "Graffiti"
(Many OpenStack services are great at providing somewhere to use metadata in terms of key-value pairs, but collaborating on the actual metadata is largely a disconnected and difficult process that often involves searching outdated wiki and opening the code) |
|||
| Line 1: | Line 1: | ||
Graffiti | Graffiti | ||
| + | |||
| + | == Overview == | ||
| + | Many OpenStack services are great at providing somewhere to use metadata in terms of key-value pairs, but collaborating on the actual metadata is largely a disconnected and difficult process that often involves searching outdated wikis and opening the source code. | ||
| + | |||
| + | At its most simple Graffiti is a metadata collaboration tool. We're starting small with the idea that we can demonstrate how having a common collaboration tool will allow even "simple" tasks like launching a VM became more oriented to the capabilities an end user desires and less about the technology implementation. | ||
Revision as of 21:52, 6 March 2014
Graffiti
Overview
Many OpenStack services are great at providing somewhere to use metadata in terms of key-value pairs, but collaborating on the actual metadata is largely a disconnected and difficult process that often involves searching outdated wikis and opening the source code.
At its most simple Graffiti is a metadata collaboration tool. We're starting small with the idea that we can demonstrate how having a common collaboration tool will allow even "simple" tasks like launching a VM became more oriented to the capabilities an end user desires and less about the technology implementation.
