From 4daae4e756947dec089ff2892044a10e8d138084 Mon Sep 17 00:00:00 2001 From: Adam Mohammed Date: Sat, 20 Apr 2024 10:23:31 -0400 Subject: [PATCH] more cleanup --- .../nanometal}/k8s-concept-review.org | 0 .../watch}/collector.yaml | 0 .../watch}/integration.org | 0 fleeting/open-stack-bm.org | 13 ----------- .../performance-aware-programming}/notes.org | 0 literature-notes/OpenStackBareMetal.org | 10 -------- nautilus/sprint-planning.org | 23 ------------------- slipbox/A.org | 8 ------- slipbox/B.org | 11 --------- slipbox/C.org | 10 -------- 10 files changed, 75 deletions(-) rename {nanometal => equinix/api-team/nanometal}/k8s-concept-review.org (100%) rename {equinix-watch => equinix/watch}/collector.yaml (100%) rename {equinix-watch => equinix/watch}/integration.org (100%) delete mode 100644 fleeting/open-stack-bm.org rename {performance-aware-programming => learning/performance-aware-programming}/notes.org (100%) delete mode 100644 literature-notes/OpenStackBareMetal.org delete mode 100644 nautilus/sprint-planning.org delete mode 100644 slipbox/A.org delete mode 100644 slipbox/B.org delete mode 100644 slipbox/C.org diff --git a/nanometal/k8s-concept-review.org b/equinix/api-team/nanometal/k8s-concept-review.org similarity index 100% rename from nanometal/k8s-concept-review.org rename to equinix/api-team/nanometal/k8s-concept-review.org diff --git a/equinix-watch/collector.yaml b/equinix/watch/collector.yaml similarity index 100% rename from equinix-watch/collector.yaml rename to equinix/watch/collector.yaml diff --git a/equinix-watch/integration.org b/equinix/watch/integration.org similarity index 100% rename from equinix-watch/integration.org rename to equinix/watch/integration.org diff --git a/fleeting/open-stack-bm.org b/fleeting/open-stack-bm.org deleted file mode 100644 index 6e55099..0000000 --- a/fleeting/open-stack-bm.org +++ /dev/null @@ -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 diff --git a/performance-aware-programming/notes.org b/learning/performance-aware-programming/notes.org similarity index 100% rename from performance-aware-programming/notes.org rename to learning/performance-aware-programming/notes.org diff --git a/literature-notes/OpenStackBareMetal.org b/literature-notes/OpenStackBareMetal.org deleted file mode 100644 index e61d341..0000000 --- a/literature-notes/OpenStackBareMetal.org +++ /dev/null @@ -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 diff --git a/nautilus/sprint-planning.org b/nautilus/sprint-planning.org deleted file mode 100644 index 9a8aa56..0000000 --- a/nautilus/sprint-planning.org +++ /dev/null @@ -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 diff --git a/slipbox/A.org b/slipbox/A.org deleted file mode 100644 index 4140c88..0000000 --- a/slipbox/A.org +++ /dev/null @@ -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. diff --git a/slipbox/B.org b/slipbox/B.org deleted file mode 100644 index 0c72843..0000000 --- a/slipbox/B.org +++ /dev/null @@ -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]] diff --git a/slipbox/C.org b/slipbox/C.org deleted file mode 100644 index 8b4df96..0000000 --- a/slipbox/C.org +++ /dev/null @@ -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