Jump to: navigation, search

Difference between revisions of "Graffiti"

Line 55: Line 55:
== Development ==
== Development ==
* Open source under Apache 2.0
* Open source under Apache 2.0
* [https://github.com/stackforge/graffiti Service Source Repository]
* [https://github.com/stackforge/graffiti Graffiti API Service Source Repository]
* [https://github.com/ttripp/horizon Temporary Horizon POC Fork Repository]
* [https://github.com/ttripp/horizon Temporary Horizon POC Fork Repository]
* [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]

Revision as of 19:28, 18 April 2014

Introduction and Project Goals

Graffiti is new project that HP and Intel have started working on and we invite your participation.

The high level goal of Graffiti is for OpenStack users to be able to declare the capabilities and service level objectives they require at a higher, more portable way than they do today. The system will then guide the selection of lower level cloud resources that match the desired capabilities.

Various OpenStack services have introduced techniques to abstract some of the low level resource selection to one level higher (such as flavors or volume types). While powerful, a challenge that we’ve experienced with OpenStack is that the way resource types and resource instances get exposed and discovered across services makes usage and remapping across deployments a manual and error prone process. Graffiti intends to provide a common methodology to describe resource capabilities in the cloud which we believe can then be leveraged by other projects such as Horizon, Nova, Heat, scheduling, reservation, and policy enforcement to enable better cross service collaboration and consistency.

How it works

  1. Load your capability vocabulary into the Graffiti dictionary
  2. "Tag" the resources in your cloud with your capabilities
  3. Let end users and admins find your resources


Graffiti provides cross service metadata tagging and search aggregation. It does this while also improving context and namespacing of the metadata.

Many OpenStack services are great at providing somewhere to use metadata in terms of key-value pairs. However, collaborating on metadata is largely a disconnected and difficult process. This often involves searching outdated wikis and opening the source code. It becomes more difficult as a cloud's scale grows. At its most basic concept Graffiti is a project to enable better metadata collaboration across services and projects.

The Graffiti project currently has two aspects:

  • Immediate improvements in Horizon with no required changes to existing services
    • * With limitations.
  • A central collaboration service without the limitations of a Horizon only solution
    • * With the intent of also enhancing existing services as needed

The full architecture may be found on the Architecture page.


We are working on a proof of concept with Horizon that crosses Nova, Glance, and Cinder. We are using the POC to help us better understand technical issues and will use that to start working on existing projects and to implement our project.

We will be at the summit with a demo of the POC (in whatever state it is) and have a scheduled design session where we'd love to discuss with the community where Graffiti can best fit in to the ecosystem and how it may relate to other projects and use cases.


We will be showing a proof of concept demo in Horizon that crosses Nova, Glance, and Cinder at Horizon. We will upload screen casts soon of the progress.

Get Involved

We encourage participation where Graffiti can best fit in to the ecosystem and how it may relate to other projects and use cases.

Graffiti is just getting underway and we are working on a POC. The POC is being done under open development.


The developers use IRC in #graffiti on Freenode for development discussion.

Frequently Asked Questions

Please see our Graffiti/FAQ for answers to common questions.