more
This commit is contained in:
8
slipbox/A.org
Normal file
8
slipbox/A.org
Normal file
@@ -0,0 +1,8 @@
|
||||
#+TITLE: NanoMetal
|
||||
#+AUTHOR: Adam Mohammed
|
||||
|
||||
Nanometal intends to be a easily deployable suite of services which
|
||||
help you manage your hardware as if it were in a datacenter controlled
|
||||
by equinixmetal. This means that you can use the existing APIs to
|
||||
manage your machines, provisioning and deprovisioning on the fly, and
|
||||
having easy out-of-band access for when things go wrong.
|
||||
11
slipbox/B.org
Normal file
11
slipbox/B.org
Normal file
@@ -0,0 +1,11 @@
|
||||
#+TITLE: Levels of abstraction to manage hardware differences
|
||||
|
||||
OpenStack and Equinix metal both use multiple layers of abstraction to
|
||||
make managing bare metal servers look simple. On the surface you get
|
||||
access to basic operations: provision/deprovision, rescue, power,
|
||||
boot. Each of which ends up having to do specific things depending on
|
||||
the hardware vendor or OS.
|
||||
|
||||
|
||||
TAGS: BareMetal Management
|
||||
REF: [[file:~/org-notes/literature-notes/OpenStackBareMetal.org][OpenStack_Ironic]]
|
||||
10
slipbox/C.org
Normal file
10
slipbox/C.org
Normal file
@@ -0,0 +1,10 @@
|
||||
#+TITLE: RAMDisk to provide initial machine control
|
||||
|
||||
OpenStack's ironic-conductor is the basic gRPC API that performs
|
||||
actions on bare metal. In order for it to provide this functionality
|
||||
the conductor relies on drivers, which handle the hardware specific
|
||||
implementation issues, and an on-machine agent. The on-machine agent
|
||||
is loaded as a ramdisk and gives the conductor the ability to perform
|
||||
some sets of actions on the machine.
|
||||
|
||||
TAGS: BareMetal Provisioning
|
||||
Reference in New Issue
Block a user