|
|
| (58 intermediate revisions by 4 users not shown) |
| Line 1: |
Line 1: |
| − | = OpenStack Bare Metal Computing =
| + | #REDIRECT [[Mogan]] |
| − | | |
| − | Nimble aims to separate bare metal computing management from Nova, which is designed specifically for BMs, so we can provide a more lightweight and convenient platform with more advanced features by leveraging Ironic. Besides this, we also plan to support RSD(Rack Scale Design), so we can not only provide Pre-set Configuration Servers but also Custom Servers.
| |
| − | | |
| − | == Nimble Mission Statement ==
| |
| − | | |
| − | To implement a service which focuses on the management of bare metal computing resources.
| |
| − | | |
| − | == What is Nimble? ==
| |
| − | | |
| − | The figure below describes how Nimble interact with other OpenStack services to manage bare metal servers.
| |
| − | [[File:Nimble-workflow.png|250x250|nimble detailed workflow]]
| |
| − | | |
| − | == Why Nimble? ==
| |
| − | | |
| − | Ironic only provides the capability to provision bare metal servers, which lacks scheduling ability and multitenancy support. Currently it is highly depends on Nova
| |
| − | | |
| − | == Use Cases ==
| |
| − | # NFV uses wants to orchestration and provisioning bare metal , with multi tenancy support.
| |
| − | # An enterprise user would like to float a cloud sourcing hardware within a datacenter, nimble will orchestrate RSD hardware resource to meet this requirement.
| |
| − | # An enterprise operator want to inventory all the physic assets, model the physic datacenter arch, mapping into a object model to help him manage physic assets, scheduling and optimize within datacenter.
| |
| − | | |
| − | == RSD Integration==
| |
| − | Rack Scale Design (RSD) implementations represent the next generation of Software Defined Infrastructure that can be dynamically provisioned across compute, network and storage resources.The fundamental premise for an RSA-based solution is the customers’ ability to “right-size” their endto-end infrastructure needs according to anticipated workload performance and capacity requirements, across pooled resources.
| |
| − | [[File:RSD.png|150x150|Rack Scale Design]]
| |
| − | VALENCE is a controller for Pooled and composable resources which adhere to DMTF[1] Redfish[2] with hardware management requests. That includes provisioning and management of RSD components and underlay features.
| |
| − | | |
| − | = Projects =
| |
| − | | |
| − | == nimble ==
| |
| − | | |
| − | {| border="1" cellpadding="2"
| |
| − | | Source code
| |
| − | | https://github.com/openstack/nimble
| |
| − | |-
| |
| − | | Bug tracker
| |
| − | | https://bugs.launchpad.net/nimble
| |
| − | |-
| |
| − | | Feature tracker
| |
| − | | https://blueprints.launchpad.net/nimble
| |
| − | |}
| |
| − | | |
| − | == python-nimbleclient ==
| |
| − | | |
| − | {| border="1" cellpadding="2"
| |
| − | | Source code
| |
| − | | https://github.com/openstack/python-nimbleclient
| |
| − | |-
| |
| − | | Bug tracker
| |
| − | | https://bugs.launchpad.net/python-nimbleclient
| |
| − | |-
| |
| − | | Feature tracker
| |
| − | | https://blueprints.launchpad.net/python-nimbleclient
| |
| − | |}
| |
| − | | |
| − | = People =
| |
| − | Zhenguo Niu (zhenguo)
| |
| − | | |
| − | Rui Chen (RuiChen)
| |
| − | | |
| − | YunTong Jin (yuntong.jin@intel.com)
| |
| − | | |
| − | Shaohe Feng (shaohe_feng)
| |
| − | | |
| − | = IRC =
| |
| − | | |
| − | Discussion of the project also takes place in '''#openstack-nimble''' on irc.freenode.net. This is a great place to jump in and start your nimble adventure.
| |
| − | | |
| − | = FAQ =
| |
| − | # What's the relationship with Nimble and Nova？ Nimble is aim to provide bare metal orchestration.
| |
| − | # What's the relationship with Nimble and Ironic？ Ironic is integrated into Nimble as a engine, which will be use to deploy(part of provisioning) baremetal node. And also Nimble leverage Ironic API to manage node’s lifecycle.
| |
| − | # What's the relationship with Nimble and Valence？ VALENCE is a RSD controller for Pooled and composable resources, | |
| − | it provide compose API for pooled resource, and also Redfish endpoint to control composed node that used by nimble.
| |
| − | For example if a particular flavor system is requested which maps to a RSD system, such a call should go to nimble which subsequently VALENCE to provide that node.
| |
| − | and nimble will enroll that node to ironic and provisioning the node with ironic.
| |
| − | == References ==
| |
| − | | |
| − | [1] https://www.dmtf.org/standards/redfish
| |
| − | | |
| − | [2] https://www.dmtf.org/
| |
| − | ----
| |
| − | [[Category:Baremetal Compute]]
| |
| − | [[Category:Nimble]] | |
