Difference between revisions of "Valence"
(→Introduction) |
(→What is in a name?) |
||
| Line 14: | Line 14: | ||
Our github is called '''RSC''' for Rack Scale Controller, and some of you may have heard us refer to this as '''Plasma'''. Do let us know if you have a strong aversion to '''Valence'''! | Our github is called '''RSC''' for Rack Scale Controller, and some of you may have heard us refer to this as '''Plasma'''. Do let us know if you have a strong aversion to '''Valence'''! | ||
If you are excited, curious, would like to participate, shoot us an email! | If you are excited, curious, would like to participate, shoot us an email! | ||
| + | |||
| + | == Valence, a Wannabe OpenStack Big Tent Project == | ||
| + | What is Valence? It really is a collection of all things Rack Scale Control, from an user interface to help compose and view nodes, to supporting launch of an OpenStack cloud using your favorite (one day in the future) deployment tool, a place to register blueprints, a banner under which to assemble a growing community interested in this functionality, a place to hold Nova and Ironic drivers and Horizon plugins to support growing/shrinking clouds dynamically, viewing Rack Scale flavors. | ||
| + | |||
| + | === Weekly Meetings === | ||
| + | |||
| + | === Meeting Minutes === | ||
| + | |||
| + | === Agenda for Next Meeting === | ||
| + | |||
| + | == References == | ||
Revision as of 08:00, 7 September 2016
Contents
Introduction
Rack Scale Design allows considering compute, storage, and networking as disaggregated resources that can be composed on the fly to meet various needs in a data center/cloud. Disaggregation, in addition to allowing hardware refresh at different rates for each of storage, compute, and networking, supports more efficient resource utilization. Imagine a cloud that grew and shrank to meet usage by virtue of being connected to a rack that allowed such dynamic composition and release, where you might compose a node with copious storage or another that provided pure compute horsepower.
To bring such a vision to light, the compute industry collaborated to standardize and define the RESTful RedFish API[1]. Intel PodManager implements the RedFish API. The API in addition to supporting composition and release of nodes supports managing them (power-on/off), discovering hardware capabilities, and even collecting advanced telemetry.
Using software that implements the RedFish API, one could construct nodes to deploy an OpenStack Cloud and with drivers for Nova and Ironic grow and shrink the cloud to meet utilization needs. Hardware flavors could be defined no different from VM flavors for the undercloud. This was take us closer to true Software Defined Infrastructure (SDI).
What is in a name?
Our github is called RSC for Rack Scale Controller, and some of you may have heard us refer to this as Plasma. Do let us know if you have a strong aversion to Valence! If you are excited, curious, would like to participate, shoot us an email!
Valence, a Wannabe OpenStack Big Tent Project
What is Valence? It really is a collection of all things Rack Scale Control, from an user interface to help compose and view nodes, to supporting launch of an OpenStack cloud using your favorite (one day in the future) deployment tool, a place to register blueprints, a banner under which to assemble a growing community interested in this functionality, a place to hold Nova and Ironic drivers and Horizon plugins to support growing/shrinking clouds dynamically, viewing Rack Scale flavors.
