Jump to: navigation, search

Difference between revisions of "Graffiti/Dictionary"

(Capability Types)
Line 27: Line 27:
=== Namespaces ===
Namespaces contain metadata definitions. RBAC is done on the namespace.

Revision as of 23:39, 21 April 2014

Capability Types

Graffiti embraces the idea that cloud resources may be described using capabilities and requirements, a concept influenced by some parts of OpenStack today as well as by industry specifications like OASIS TOSCA (Please note, Graffiti is NOT an orchestration engine, it only assists in describing and locating existing resources in the cloud.).

A Capability Type is the following:

  • A metadata schema that describes a type of capability a cloud resource may provide
    • e.g. “Centos” may be a type of capability
  • Defines the structure of observable properties in a subset of the JSON Schema draft 04 format
    • The names, data types and allowed values of properties.
      • e.g. Centos has a version and architecture
  • Hierarchical
    • Can inherit properties from parent Capability Types
    • e.g. Centos is software and all software has a version
  • Referenced by requirements
    • e.g. My application requires Centos
  • Scoped by a namespace
    • Uniquely named within a namespace
      • Your definition of "Classified" is not the same as mine, so we'll agree to disagree
    • RBAC is done on the namespace, not on individual types
    • Capability Types may derive from Types in other namespaces


Namespaces contain metadata definitions. RBAC is done on the namespace.