opendev/system-config
Code Issues Proposed changes

Make small tweaks to launch node README

Browse Source 
First of all, we're using RST syntax, so rename it to README.rst.

More importantly, remove menitons of puppetmaster - and puppet in
general, as they are distracting. When reading the file, my eyes
scanned and hit puppetmaster and I almost skipped the section with the
assumption it was out of date.

Change-Id: I294bf17084be7dad46e075ad2a3ef2674276c018
This commit is contained in:
Monty Taylor 2020-02-04 07:22:49 -06:00
parent 6f32fbebe5
commit 99a52a9c52
1 changed files with 9 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
launch/README → launch/README.rst
View File

@ -19,26 +19,24 @@ automatically, but it prints the commands to run). Note that for
records via the printed commands. Forward A and AAAA records should records via the printed commands. Forward A and AAAA records should
be added to opendev/zone-opendev.org/zones/opendev.org/zone.db. be added to opendev/zone-opendev.org/zones/opendev.org/zone.db.
In order for Ansible to be able to send out the Puppet updates, We need to add the host to our static inventory file so that
you also need the puppetmaster to accept the root SSH key for the the ansible runs see the new host. The launch script prints out
new server. So as root on bridge.openstack.org: the appropriate lines to add to
opendev/system-config:inventory/openstack.yaml.
In order for Ansible to work, you also need to accept the root SSH
key for the new server. Once the new DNS entries have propagated,
as root on bridge.openstack.org:
ssh root@$FQDN ssh root@$FQDN
Verify the fingerprint of the new server and type "yes" to accept. Verify the fingerprint of the new server and type "yes" to accept.
Then you can log out. Then you can log out.
Finally we need to add the host to our static inventory file so that
the periodic ansible runs (which can run puppet) see the new host.
Update opendev/system-config/inventory/openstack.yaml to
include the appropriate hostname and IP address details.
Add DNS Records Add DNS Records
=============== ===============
There are no scripts to automatically handle DNS at the moment due to The launch-node script will print the commands needed to be
a lack of library support for the new Rackspace Cloud DNS (with IPv6).
However, the launch-node script will print the commands needed to be
run to configure DNS for a newly launched server. To see the commands run to configure DNS for a newly launched server. To see the commands
for an existing server, run: for an existing server, run: