airship/treasuremap
Code Issues Proposed changes

MAAS improvements for DNS & NodePort

Browse Source 
Using MAAS IP for DNS allows installation by not requiring
direct internet connectivity for PXE/bootstrap interface.

NodePort usage for genesis bootstrap helps troubleshooting
during bare-metal deployment. The NodePort is unset once the
full-site (maas-scaled) is deployed.

Change-Id: I6cab0b3cfc541d43d738f3dc144bb29d848ab718
This commit is contained in:
Kaspars Skels 2019-08-26 15:28:55 -05:00
parent f3b851a69e
commit 44d6f90a2d
2 changed files with 14 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
site/seaworthy/networks/physical/networks.yaml
View File

@ -139,10 +139,11 @@ data:
# Choose FQDN according to the node FQDN naming conventions at the top of # Choose FQDN according to the node FQDN naming conventions at the top of
# this document. # this document.
domain: atlantafoundry.com domain: atlantafoundry.com
# List of upstream DNS forwards. Verify you can reach them from your # NEWSITE-CHANGEME: Use MAAS VIP as the DNS server.
# environment. If so, you should not need to change them. # MAAS has inbuilt DNS server and Debian mirror that allows nodes to be
# TODO: This should be populated via substitution from common-addresses # deployed without requiring routed/internet access for the PXE interface.
servers: '8.8.8.8,8.8.4.4,208.67.222.222' # See data.vip.maas_vip in networks/common-addresses.yaml
servers: '10.23.20.9'
... ...
--- ---
schema: 'drydock/NetworkLink/v1' schema: 'drydock/NetworkLink/v1'

10
type/foundry/charts/ucp/comps/maas.yaml
View File

@ -20,5 +20,13 @@ metadata:
path: .vip.maas_vip path: .vip.maas_vip
dest: dest:
path: .values.network.maas_ingress.addr path: .values.network.maas_ingress.addr
data: {} data:
values:
network:
region_api:
# Enable NodePort for initial genesis deployment.
# This helps with early deployment of bare-metal servers
# and is later removed by maas-scaled overrides
node_port:
enabled: true
... ...