more cleanup

fleeting/open-stack-bm.org

@@ -1,13 +0,0 @@
-#+TITLE: Openstack: Bare Metal service overview
-#+AUTHOR:
-
-Openstack's BM service "ironic" works by having basic operations
-add/edit/delete nodes
-power on/off
-provision/deploy/clean
-
-The "conductor" calls out to driver for vendor specific
-implementations of the above functions. A python ramdisk is used to
-provide control on the target machine.
-
-ref: https://docs.openstack.org/ironic/2023.1/install/get_started.html

literature-notes/OpenStackBareMetal.org

@@ -1,10 +0,0 @@
-#+TITLE: OpenStack: BareMetal
-
-Openstack has a collection of services named "ironic" that helps
-manage baremetal servers. The architecture is broken down by levels of
-abstraction. The highest abstraction is the API, which makes
-controlling different hardware seem the same. Below the API is a basic
-driver layer, which calls out to plugins to perform actions specific
-to a vendor/hardware type.
-
-ref: https://docs.openstack.org/ironic/2023.1/install/get_started.html

nautilus/sprint-planning.org

@@ -1,23 +0,0 @@
-* People
-- Emi
-- Hogle
-- Lucas
-- Laurence
-- Ian
-- Thiago
-- Sahil
-- Abhishek
-- Navaneeth
-- Surbhit
-- Nikita
-- Shelby
-
-
-** Remaining work:
-*** Integration testing with server service - Laurence
-*** Review nanometal doc with provisioning team - Ian
-*** Update automation of oapi-codegen and sqlboiler - Abhishek
-*** Serialized Scheduler Garbage collection - hogle
-
-
-** Sprint 19

slipbox/A.org

@@ -1,8 +0,0 @@
-#+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.

slipbox/B.org

@@ -1,11 +0,0 @@
-#+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]]

slipbox/C.org

@@ -1,10 +0,0 @@
-#+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