BMC (Bare-Metal Container) offers an environment to run a container (Docker) image with a suitable Linux kernel on a remote physical machine. BMC allows to change the kernel and its settings for the container (Docker) image. As a result, the application extracts the full performance of the physical machine.
The following figure shows the difference in application invocation between traditional style and BMC. The traditional style is a system-centric architecture as it assumes the system software is fixed, running all the time, and unalterable by users. In contrast, BMC allows users to change the kernel and the machine for each application, which we describe as an application-centric architecture.
A pre-built BMC image using DIND (Docker in Docker) technique is offered. Users can avoid burdensome setting up (ex. Apache CGI, etc). We recommend new users to try this pre-built version.
https://hub.docker.com/r/baremetalcontainer/bmc/
- [1] K.Suzaki, H.Koie, and R.Takano, "Bare-Metal Container --- Direct Execution of a Container Image on a Remote Machine with an Optimized Kernel ---", the 18th IEEE High Performance Computing and Communications (HPCC) Dec.2016. / Ppaer PDF / Slide PDF
- [2] K.Suzaki, "Bare-Metal Container", Open Source Summit Japan 2017, July.2017.
- [3] K.Suzaki, H.Koie, and R.Takano, "Profile Guided Kernel Optimization for Individual Container Execution on Bare-Metal Container" SC17 poster
- [1] SuperComuting16 (SC16) [AIST booth 1709] Nov.2016 http://sc16.supercomputing.org/
- [2] SuperComuting17 (SC17) [AIST booth 1211] Nov.2016 http://sc17.supercomputing.org/