I've been inspired by a discussion with PatWendorf and some folks on the cloud interoperability forum about UCI project and its value and I have created the illustrated architecture diagram.
This is an eye-bird view about the vision of the UCI project. The main goal of this project as described by Pat is to have an abstraction layer which is agnostic to any cloud API, platform or infrastructure.
The main driver of this architecture is to abstract the usage of any cloud API and unify them in one layer with the help of the semantic web and OWL in which you have a pool of resources semantically understood and described to enable you to use these resources regardless these resources are allocated from Amazon EC2 as a provider or Enomaly platform etc.
Once you have a unified interface with common definitions to these resources, you can allocate, de-allocate, provision virtual machines or manage them through the UCI layer using the Agent component.
This architecture is a mix of layers and components along with a use case described at the UCI project requirement page http://code.google.com/p/unifiedcloud/wiki/UCI_Requirements
This UCI layer (web browser or UCI cloud client) should provide a kind of a dashboard (the component on the left of the diagram) to show the state of all allocated resources and running VMs.
2 comments:
Can I know how semantic web play a role in UCI?
thank you
Hello Jailan,
The main driver of UCI is to abstract the usage of any cloud API and unify them in one layer with the help of the semantic web and OWL in which you have a pool of resources semantically understood and described to enable you to use these resources regardless its provider.
in semantic web we can use resource description framework (RDF) to describe a semantic cloud data model (taxonomy & ontology). The benefit to an RDF based ontology languages is they act as general method for the conceptual description or modeling of information that is implemented by web resources.
Post a Comment