Difference between revisions of "Nimble"
Yuntongjin (talk | contribs) (→Use Cases) |
Yuntongjin (talk | contribs) (→Use Cases) |
||
Line 17: | Line 17: | ||
== Use Cases == | == 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== | == RSD Integration== |
Revision as of 09:15, 12 October 2016
Contents
OpenStack Bare Metal Computing
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.
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. 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
Source code | https://github.com/openstack/nimble |
Bug tracker | https://bugs.launchpad.net/nimble |
Feature tracker | https://blueprints.launchpad.net/nimble |
python-nimbleclient
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? What's the relationship with Nimble and Ironic? What's the relationship with Nimble and Valence?
References
[1] https://www.dmtf.org/standards/redfish