airship/airshipctl
Code Issues Proposed changes
A CLI for managing declarative infrastructure.
547 Commits 3 Branches 0 Tags 380 MiB
Go 85.6%
Shell 9.8%
Dockerfile 1.4%
Jinja 1.3%
Makefile 1.2%
Other 0.7%
cb59c859cb
Go to file
Drew Walters cb59c859cb Add Dell Redfish client 
The Dell Redfish implementation slightly deviates from the DMTF Redfish
specification. One variation is the Dell specification's classification
of virtual media, in which the Dell variation adds support for virtual
CDs and virtual floppy drives [0]. In order to perform some actions on Dell
hardware, airshipctl needs support for vendor specific clients.

This change introduces a vendor-specific Dell client to handle some
Redfish operations.

[0] https://www.dell.com/support/manuals/us/en/04/idrac9-lifecycle-controller-v3.2-series/idrac_3.21.21.21_redfishapiguide/virtualmedia?guid=guid-d9e76cf6-627d-4cb9-a3de-3f2b88b74cfb&lang=en-us

Relates-To: #139

Change-Id: Icc4500177e859d5a4607b98ec2bd2737521d00b1
Signed-off-by: Drew Walters <andrew.walters@att.com>
2020-04-17 19:51:24 +00:00
.github Add SECURITY.md 2020-02-20 16:57:57 -06:00
cmd Merge "Uplift go-git" 2020-04-15 13:08:33 +00:00
docs Create documentation for new developers 2020-04-08 19:22:27 +05:00
manifests Add CAPI bootstrap provider kubeadm 2020-04-17 18:20:27 +00:00
pkg Add Dell Redfish client 2020-04-17 19:51:24 +00:00
playbooks Add copyright for missing files 2020-04-09 08:35:59 -05:00
roles Add env variables for necessary roles. 2020-04-16 20:42:31 +00:00
testdata/k8s [AIR-97] Adding initinfra subcommand 2020-02-27 08:38:51 -06:00
tests/ansible Add copyright for missing files 2020-04-09 08:35:59 -05:00
testutil Aligned the function definiton to its signature 2020-04-16 11:07:23 -05:00
tools Switching local gating scripts to Python3 to comply with Zuul 2020-04-11 06:53:40 +00:00
zuul.d Merge "Use 16GB flavor for gate job and let it vote" 2020-04-03 17:09:27 +00:00
.gitignore [#6] Add config init subcommand 2020-02-17 16:22:10 -06:00
.gitreview Gerrit: Add .gitreview file 2019-06-25 08:11:57 -05:00
.golangci.yaml Add copyright for missing files 2020-04-09 08:35:59 -05:00
CONTRIBUTING.md [#39] Add Zuul job for GitHub Issues integration 2020-03-02 09:49:27 -06:00
Dockerfile [#81] makefile to check for unused test data 2020-03-08 00:05:48 +00:00
go.mod Uplift go-git 2020-04-14 09:07:28 -05:00
go.sum Uplift go-git 2020-04-14 09:07:28 -05:00
LICENSE Add LICENSE 2019-10-19 14:16:05 -05:00
main.go Add copyright for missing files 2020-04-09 08:35:59 -05:00
Makefile [#81] makefile to check for unused test data 2020-03-08 00:05:48 +00:00
README.md [#37] Change issue tracker info to GitHub Issues 2020-02-12 11:13:14 -06:00
Vagrantfile [#32]: scripts for local run playbooks 2020-02-28 17:24:32 -08:00

README.md

airshipctl

What is airshipctl

The airshipctl project is a CLI tool and Golang library for declarative management of infrastructure and software.

The goal for the project is to provide a seamless experience to operators wishing to leverage the best of breed open source options such as the Cluster API, Metal3-io, Kustomize, Kubeadm, and Argo -- into a straight forward and easily approachable tool.

This project is the heart of the effort to produce Airship 2.0, which has three main evolutions from 1.0:

  • Expand our use of entrenched upstream projects.
  • Embrace Kubernetes Custom Resource Definitions (CRD) – Everything becomes an Object in Kubernetes.
  • Make the Airship control plane ephemeral.

To learn more about the Airship 2.0 evolution, please check out the Airship Blog Series.

Contributing

This project is under heavy active development to reach an alpha state.

New developers should read the contributing guide as well as the developer guide in order to get started.

Architecture

The airshipctl tool is designed to work against declarative infrastructure housed in source control and manage the lifecycle of a site.

architecture diagram

Example Usage

In a nutshell, users of airshipctl should be able to do the following:

  1. Create an airshipctl Airship Configuration for their site - sort of like a kubeconfig file.
  2. Create a set of declarative documents representing the infrastructure (baremetal, cloud) and software.
  3. Run airshipctl document pull to clone the document repositories in your Airship Configuration.
  4. When deploying against baremetal infrastructure, run airshipctl bootstrap isogen to generate a self-contained ISO that can be used to boot the first host in the cluster into an ephemeral Kubernetes node.
  5. When deploying against baremetal infrastructure, run airshipctl bootstrap remotedirect to remotely provision the first machine in the cluster using the generated ISO, providing an ephemeral Kubernetes instance that airshipctl can communicate with for subsequent steps. This ephemeral host provides a foothold in the target environment so we can follow the standard cluster-api bootstrap flow.
  6. Run airshipctl cluster initinfra --clustertype=ephemeral to bootstrap the new ephemeral cluster with enough of the chosen cluster-api provider components to provision the target cluster.
  7. Run airshipctl clusterctl to use the ephemeral Kubernetes host to provision at least one node of the target cluster using the cluster-api bootstrap flow.
  8. Run airshipctl cluster initinfra --clustertype=target to bootstrap the new target cluster with any remaining infrastructure necessary to begin running more complex workflows such as Argo.
  9. Run airshipctl workflow submit sitemanage to run the out of the box sitemanage workflow, which will leverage Argo to handle bootstrapping the remaining infrastructure as well as deploying and/or updating software.

As users evolve their sites declaration, whether adding additional infrastructure, or software declarations, they can re-run airshipctl workflow submit sitemanage to introduce those changes to the site.

Project Resources