Brand the Login Banner During Commissioning

You can customize the pre-login message (issue) and post-login MOTD across the entire StarlingX cluster during system commissioning and installation.

The following files can be customized to use this feature:

/etc/issue	console login banner
/etc/issue.net	ssh login banner
/etc/motd.head	message of the day header
/etc/motd.tail	message of the day footer This file is not present by default. You must first create it to apply your customizations.

issue and issue.net are free standing files. /etc/motd is generated from the following sources in the order presented:

1. /etc/motd.head

2. /etc/sysinv/motd.system

3. /etc/platform/motd.license

4. /etc/motd.tail

Complete the following procedure to customize the login banner during installation and commissioning:

Procedure

1. Provide customization files.

   To customize any of the four customizable banner files listed above, provide the new files in the following locations:

   • /opt/banner/issue

   • /opt/banner/issue.net

   • /opt/banner/motd.head

   • /opt/banner/motd.tail

   See the issue and motd man pages for details on file syntax.

2. Run Ansible Bootstrap playbook.

   When Ansible Bootstrap playbook is run, these files are moved from /opt/banner to configuration storage and are applied to the controller node as it is initialized. All nodes in the cluster which are subsequently configured will retrieve these custom banners as well.

   Note

   In the event that an error is reported for the banner customization, it can be repeated after running Ansible Bootstrap playbook and system deployment. Customization errors do not impact Ansible Bootstrap playbook. See Brand the Login Banner on a Commissioned System for more information.