Difference between revisions of "Valence Threat Model"
(Created page with "== Valence == Valence is a collection of functionality to ease consuming disaggregated rack resources, compute, storage, and network that are accessible via the DMTF Redfish...") |
(→Valence assets) |
||
| Line 12: | Line 12: | ||
* '''An API Server and Controller''' component that is comprised of: | * '''An API Server and Controller''' component that is comprised of: | ||
API server that provides a RESTful interface to compose and decompose nodes and list them | API server that provides a RESTful interface to compose and decompose nodes and list them | ||
| − | + | # A Controller component that makes the appropriate backend calls to the Rack Controller implementation using Redfish REST API calls, authenticates users, manages user quotas, and more | |
| − | + | #A database to track registered users, user quotas, allocation of resources, hardware flavors and more. | |
| − | + | #Connection credentials and address to the Rack Controller,, which controls the rack scale resource pool. Connection details could be provided in a config file or obtained and stored from form input data. | |
| − | + | *'''OpenStack Plugins ''' that essentially shall enable an existing cloud, if configured to do so, to acquire and release resources from a disaggregated pool of resources. In particular these plugins will allow OpenStack/nova to add/release compute hosts, OpenStack/ironic to add/release bare metal nodes, and OpenStack/horizon. This aspect as it evolves will be covered by a separate security review. | |
| − | *'''OpenStack Plugins '''that essentially shall enable an existing cloud, if configured to do so, to acquire and release resources from a disaggregated pool of resources. In particular these plugins will allow OpenStack/nova to add/release compute hosts, OpenStack/ironic to add/release bare metal nodes, and OpenStack/horizon. This aspect as it evolves will be covered by a separate security review. | ||
Revision as of 10:50, 10 January 2017
Valence
Valence is a collection of functionality to ease consuming disaggregated rack resources, compute, storage, and network that are accessible via the DMTF Redfish RESTful API, to launch a cloud and dynamically grow/shrink an OpenStack cloud. The Redfish API is implemented, in our case, by Intel Rack Scale Design PodManager. The functionality is exposed to registered users.
Valence is composed of 3 components, a Web-UI, An API + Controller component, and a collection of plugins for OpenStack that shall allow dynamic grow/shrink of an OpenStack cloud. In the above figure, these are to the extreme left, colored in green and boxed with “Valence” label.
Valence assets
- Web UI -- application that provides the graphical user interface
HTML, javascript, style sheets associated with the Web application
- An API Server and Controller component that is comprised of:
API server that provides a RESTful interface to compose and decompose nodes and list them
- A Controller component that makes the appropriate backend calls to the Rack Controller implementation using Redfish REST API calls, authenticates users, manages user quotas, and more
- A database to track registered users, user quotas, allocation of resources, hardware flavors and more.
- Connection credentials and address to the Rack Controller,, which controls the rack scale resource pool. Connection details could be provided in a config file or obtained and stored from form input data.
- OpenStack Plugins that essentially shall enable an existing cloud, if configured to do so, to acquire and release resources from a disaggregated pool of resources. In particular these plugins will allow OpenStack/nova to add/release compute hosts, OpenStack/ironic to add/release bare metal nodes, and OpenStack/horizon. This aspect as it evolves will be covered by a separate security review.
