Add subcluster image

Closes Issue #20

Change-Id: I571aab3fa7ac147a0afacd6467b46fb45e7b9ad6
This commit is contained in:
Anderson, Craig (ca846m) 2021-06-09 08:59:43 -07:00
parent e9c6cb0419
commit 736b199980
7 changed files with 38 additions and 0 deletions

View File

@ -0,0 +1,3 @@
This folder represents a "QCOW bundle", i.e. a container image that will
contain all of the target QCOW images needed for a particular subcluster
deployment.

View File

@ -0,0 +1,3 @@
By default, the QCOW produced from this set of configs will be
deployed to subcluster control-plane nodes in airshipctl
deployment.

View File

@ -0,0 +1,4 @@
# Custom user-defined overrides to the `osconfig` playbook can be placed here.
#
# You would only use this if you needed to apply some settings uniques to
# control-plane image. Ex: kernel boot params specific to non-worker nodes.

View File

@ -0,0 +1,3 @@
# Custom user-defined overrides to the `qcow` playbook can be placed here.
# Example, Changing disk size:
#qcow_capacity: 200G

View File

@ -0,0 +1,6 @@
By default, the QCOW produced from this set of configs will be
deployed to data-plane nodes in airshipctl subcluster
deployment.
Currently these are symlinks since there is no difference, but
this can be changed if/when worker nodes use a different config.

View File

@ -0,0 +1,18 @@
# Custom user-defined overrides to the `osconfig` playbook can be placed here.
#
# You would only use this if you needed to apply some settings uniques to
# data-plane image. Ex: hugepages and cpu pinning configuration
# grub_cmdline_linux_default_append:
# - name: hugepagesz
# value: "1G"
# - name: hugepages
# value: "100"
# - name: default_hugepagesz
# value: "1G"
# - name: isolcpus
# value: "4-43,48-87"
# - name: rcu_nocbs
# value: "4-43,48-87"
# - name: transparent_hugepage
# value: "never"

View File

@ -0,0 +1 @@
../control-plane/qcow-vars.yaml