Jump to: navigation, search

Difference between revisions of "Graffiti"

(Overview)
Line 1: Line 1:
  
 
== Overview ==
 
== Overview ==
Many OpenStack services are great at providing various mechanisms 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 source code. This makes things hard on everybody from administrators to end users.
+
We love OpenStack and we want to make it more approachable for end users.
  
We believe that OpenStack users should be able to declare the capabilities and service level objectives they require without needing a technical understand of OpenStack or being affected by the technical feature changes from version to version of OpenStack.
+
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.
  
At its most simple Graffiti is a metadata collaboration tool. We're starting small with the idea that we can demonstrate how having a metadata collaboration tool will allow even "simple" tasks like launching a VM became even simpler for non-technical users.
+
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.  
  
We believe in the OpenStack building block approach to services and we believe that Graffiti will enable other services to
+
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 and we invite anybody who want to join in to help out.
  
 
== Architecture ==
 
== Architecture ==
  
 +
Coming soon...
  
 
== API ==
 
== API ==

Revision as of 00:07, 8 March 2014

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 and we invite anybody who want to join in to help out.

Architecture

Coming soon...

API

Capability Type Management API

Resource Search API

Development