Quick, Solid, and Automatic - OpenStack Bare-metal Orchestration

Bare-metal on OpenStack is the trend, and if we can add orchestration around bare-metal will bring you automatic management around the town. But how we orchestrate over bare-metal servers? Is it just the same as orchestrating over VMs? Which services do we need to have a full running bare-metal orchestration service? And how about the performance and what workflow changing when you adding automatic functionality (like self-healing or autoscaling)? In this presentation will introduce bare-metal on OpenStack, and go through detail on how can you use Ironic and Heat to manage your baremetal servers in automatic way.

With Baremetal become one common use case OpenStack have. Does OpenStack innovate fast enough for the needs? What's the community' plan/works? And I think what's important question for you, is baremetal on OpenStack a good choice? we will introduce how can we keep it quick, solid and automatic to support baremetal application infrastructure.

[bhaskaruid]

Thanks for this Video ! I am a beginner of OpenStack. I have recently built a test environment (4 CentOS physical servers, Controller, Compute, BlockStotage and Object Storage Node) of core components of OpenStack and able to create VMs, Allocate Volumes and associating Floating IPs. Now I am configuring Ironic on that environment. All components of Ironic are configured in Controller Node. I am going to launch a baremetal instance. Is any dependency on Compute Node is there? Or can we provision a baremetal instance without Compute Node? Please help.