From 640ff61422bc0ee3966941b93d9889ddbbd38d77 Mon Sep 17 00:00:00 2001 From: ckonstanski Date: Thu, 30 Jul 2026 18:17:14 -0600 Subject: more files --- doc/tex/break-fix/.gitignore | 9 +++++ doc/tex/break-fix/compile.sh | 6 ++++ doc/tex/break-fix/slides.tex | 82 ++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 97 insertions(+) create mode 100644 doc/tex/break-fix/.gitignore create mode 100755 doc/tex/break-fix/compile.sh create mode 100644 doc/tex/break-fix/slides.tex (limited to 'doc/tex') diff --git a/doc/tex/break-fix/.gitignore b/doc/tex/break-fix/.gitignore new file mode 100644 index 0000000..99eff73 --- /dev/null +++ b/doc/tex/break-fix/.gitignore @@ -0,0 +1,9 @@ +*.aux +*.bbl +*.blg +*.log +*.nav +*.out +*.pdf +*.snm +*.toc diff --git a/doc/tex/break-fix/compile.sh b/doc/tex/break-fix/compile.sh new file mode 100755 index 0000000..6e2d731 --- /dev/null +++ b/doc/tex/break-fix/compile.sh @@ -0,0 +1,6 @@ +#!/bin/bash + +rm *-blx.bib *.aux *.bbl *.bcf *.blg *.log *.nav *.out *.run.xml *.snm *.toc +file="$(ls *.tex | awk -F. '{print $1}')" +pdflatex ${file} +exit 0 diff --git a/doc/tex/break-fix/slides.tex b/doc/tex/break-fix/slides.tex new file mode 100644 index 0000000..a3a0215 --- /dev/null +++ b/doc/tex/break-fix/slides.tex @@ -0,0 +1,82 @@ +% To make a PDF from this source, use the pdflatex command. +\documentclass[helvetica,english,utf8,notitle,nologo,8pt]{beamer} +\usetheme{boxes} +\usecolortheme{seahorse} +\usepackage[american]{babel} +\usepackage[babel]{csquotes} + +\begin{document} + +\title{Wind River Subcloud Break-Fix Procedure} +\author{Carlos Konstanski\\ +Far-Edge Engineering/Operations} + +\frame{\titlepage} + +\begin{frame} + \frametitle{Introduction} + + This document will describe the steps required to replace a Wind + River subcloud server, specifically the portion of the process that + is handled by Far-Edge Engineering/Operations. This group is + concerned with the installation of Wind River CaaS and the vDU + workloads. It is assumed that the prerequisite steps have already + been completed. These include but are not necessarily limited to: + + \begin{itemize} + \item Physical server racking + \item Network cabling + \item Capturing the serial number and iLO password from the sticker + on the bottom of the blade + \item Capturing the iLO IPv6 address + \end{itemize} +\end{frame} + +\begin{frame} + \frametitle{What Eng/Ops Needs in the Handoff} + + Once a new server has been racked and cabled, Far-Edge Eng/Ops needs + to be notified so that we can provision the new host. We require + three pieces of information in order to do this: + + \begin{enumerate} + \item The iLO IPv6 address. This is the key for looking up the + remainder of the server information in our system. + \item The iLO password. It is printed on a sticker on the bottom of + the blade. + \item The blade serial number. It is printed on the same sticker. + \end{enumerate} + + Workbench 360 has been proposed as the notification channel. +\end{frame} + +\begin{frame} + \frametitle{How to Procure the Subcloud Information} + + An interim web UI page has been set up to query server information + based on the FUZE ID: + + https://middleware.vcpfe.vzwops.com/caas/subcloud/ +\end{frame} + +\begin{frame} + \frametitle{What Eng/Ops Does Next} + + We will watch the automation pipeline to ensure that the server + completes the zero-touch provisioning process successfully. + + \begin{itemize} + \item On the central controller: dcmanager subcloud unmanage cluster\_name + \item On the central controller: dcmanager subcloud delete cluster\_name + \item Disassociate the server record from the old blade record in + the middleware database. + \item Ingest the new blade info (serial number and password). + \item Update icinga to pick up the new model\_check service which + will relink the server to the new blade. + \end{itemize} + + At this point the server will enter the automation pipeline and + proceed just like a normal installation. +\end{frame} + +\end{document} -- cgit v1.3