Difference between revisions of "Graffiti"
Travis Tripp (talk | contribs) |
|||
| Line 26: | Line 26: | ||
* [https://bugs.launchpad.net/graffiti Bug tracker] | * [https://bugs.launchpad.net/graffiti Bug tracker] | ||
* [https://blueprints.launchpad.net/graffiti Feature Tracker] | * [https://blueprints.launchpad.net/graffiti Feature Tracker] | ||
| + | * [https://github.com/stackforge/graffiti Code Repository] | ||
Revision as of 19:34, 10 March 2014
Contents
Overview
We love OpenStack and we want to make it more approachable for end users.
We want users to be able to declare the capabilities they want from the system without being technical experts on the nuances of OpenStack, whether this is to launch simple instances or to launch full application stacks with their desired level of service assurance.
We are starting small with the idea that we can demonstrate how we can make even "simple" tasks like launching a VM became even simpler for non-technical users.
At its most simple concept Graffiti is a metadata collaboration tool. Many OpenStack services are great at providing various mechanisms to use metadata in terms of key-value pairs, but collaborating on the actual metadata between developers, admins, services, UI, and end users is largely a disconnected and difficult process that often involves searching outdated wikis, opening source code, and in the best cases making a lot of command line calls. This makes things hard on everybody. We want to make things easier.
Architecture
Coming soon...
API
Capability Type Management API
Resource Search API
Get Involved
We are still in the very early stages, but we welcome involvement!
