Reference Airship manifests, CICD, and reference architecture.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

66 lines
2.5KB

  1. ---
  2. # Drydock BaremetalNode resources for a specific rack are stored in this file.
  3. #
  4. # NOTE: For new sites, you should complete the networks/physical/networks.yaml
  5. # file before working on this file.
  6. #
  7. # In this file, you should make the number of `drydock/BaremetalNode/v1`
  8. # resources equal the number of bare metal nodes you have, either by deleting
  9. # excess BaremetalNode definitions (if there are too many), or by copying and
  10. # pasting the last BaremetalNode in the file until you have the correct number
  11. # of baremetal nodes (if there are too few).
  12. #
  13. # Then in each file, address all additional NEWSITE-CHANGEME markers to update
  14. # the data in these files with the right values for your new site.
  15. #
  16. # *NOTE: The Genesis node is counted as one of the control plane nodes. Note
  17. # that the Genesis node does not appear on this bare metal list, because the
  18. # procedure to reprovision the Genesis host with MaaS has not yet been
  19. # implemented. Therefore there will be only three bare metal nodes in this file
  20. # with the 'masters' tag, as the genesis roles are assigned in a difference
  21. # place (profiles/genesis.yaml).
  22. # NOTE: The host profiles for the control plane are further divided into two
  23. # variants: primary and secondary. The only significance this has is that the
  24. # "primary" nodes are active Ceph nodes, whereas the "secondary" nodes are Ceph
  25. # standby nodes. For Ceph quorum, this means that the control plane split will
  26. # be 3 primary + 1 standby host profile, and the Genesis node counts toward one
  27. # of the 3 primary profiles. Other control plane services are not affected by
  28. # primary vs secondary designation.
  29. #
  30. # TODO: Include the hostname naming convention
  31. #
  32. schema: 'drydock/BaremetalNode/v1'
  33. metadata:
  34. schema: 'metadata/Document/v1'
  35. # NEWSITE-CHANGEME: The next node's hostname
  36. name: airsloop-compute-1
  37. layeringDefinition:
  38. abstract: false
  39. layer: site
  40. storagePolicy: cleartext
  41. data:
  42. # NEWSITE-CHANGEME: The next node's IPv4 addressing
  43. addressing:
  44. - network: oob
  45. address: 10.22.104.22
  46. - network: pxe
  47. address: 10.22.70.22
  48. - network: oam
  49. address: 10.22.71.22
  50. - network: calico
  51. address: 10.22.72.22
  52. - network: storage
  53. address: 10.22.73.22
  54. - network: overlay
  55. address: 10.22.74.22
  56. # NEWSITE-CHANGEME: The next node's host profile
  57. # This is the third "primary" control plane profile after genesis
  58. host_profile: compute_r720xd
  59. metadata:
  60. # NEWSITE-CHANGEME: The next node's rack designation
  61. rack: cab22
  62. # NEWSITE-CHANGEME: The next node's role desigatnion
  63. tags:
  64. - 'workers'
  65. ...