diff --git a/centos_pkg_dirs b/centos_pkg_dirs index e6e633552..6d86ffae2 100644 --- a/centos_pkg_dirs +++ b/centos_pkg_dirs @@ -109,3 +109,4 @@ kubernetes/docker-distribution kubernetes/helm logging/logmgmt filesystem/filesystem-scripts +utilities/branding diff --git a/utilities/branding/LICENSE b/utilities/branding/LICENSE new file mode 100644 index 000000000..d64569567 --- /dev/null +++ b/utilities/branding/LICENSE @@ -0,0 +1,202 @@ + + Apache License + Version 2.0, January 2004 + http://www.apache.org/licenses/ + + TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + + 1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix below). + + "Derivative Works" shall mean any work, whether in Source or Object + form, that is based on (or derived from) the Work and for which the + editorial revisions, annotations, elaborations, or other modifications + represent, as a whole, an original work of authorship. For the purposes + of this License, Derivative Works shall not include works that remain + separable from, or merely link (or bind by name) to the interfaces of, + the Work and Derivative Works thereof. + + "Contribution" shall mean any work of authorship, including + the original version of the Work and any modifications or additions + to that Work or Derivative Works thereof, that is intentionally + submitted to Licensor for inclusion in the Work by the copyright owner + or by an individual or Legal Entity authorized to submit on behalf of + the copyright owner. For the purposes of this definition, "submitted" + means any form of electronic, verbal, or written communication sent + to the Licensor or its representatives, including but not limited to + communication on electronic mailing lists, source code control systems, + and issue tracking systems that are managed by, or on behalf of, the + Licensor for the purpose of discussing and improving the Work, but + excluding communication that is conspicuously marked or otherwise + designated in writing by the copyright owner as "Not a Contribution." + + "Contributor" shall mean Licensor and any individual or Legal Entity + on behalf of whom a Contribution has been received by Licensor and + subsequently incorporated within the Work. + + 2. Grant of Copyright License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + copyright license to reproduce, prepare Derivative Works of, + publicly display, publicly perform, sublicense, and distribute the + Work and such Derivative Works in Source or Object form. + + 3. Grant of Patent License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + (except as stated in this section) patent license to make, have made, + use, offer to sell, sell, import, and otherwise transfer the Work, + where such license applies only to those patent claims licensable + by such Contributor that are necessarily infringed by their + Contribution(s) alone or by combination of their Contribution(s) + with the Work to which such Contribution(s) was submitted. If You + institute patent litigation against any entity (including a + cross-claim or counterclaim in a lawsuit) alleging that the Work + or a Contribution incorporated within the Work constitutes direct + or contributory patent infringement, then any patent licenses + granted to You under this License for that Work shall terminate + as of the date such litigation is filed. + + 4. Redistribution. You may reproduce and distribute copies of the + Work or Derivative Works thereof in any medium, with or without + modifications, and in Source or Object form, provided that You + meet the following conditions: + + (a) You must give any other recipients of the Work or + Derivative Works a copy of this License; and + + (b) You must cause any modified files to carry prominent notices + stating that You changed the files; and + + (c) You must retain, in the Source form of any Derivative Works + that You distribute, all copyright, patent, trademark, and + attribution notices from the Source form of the Work, + excluding those notices that do not pertain to any part of + the Derivative Works; and + + (d) If the Work includes a "NOTICE" text file as part of its + distribution, then any Derivative Works that You distribute must + include a readable copy of the attribution notices contained + within such NOTICE file, excluding those notices that do not + pertain to any part of the Derivative Works, in at least one + of the following places: within a NOTICE text file distributed + as part of the Derivative Works; within the Source form or + documentation, if provided along with the Derivative Works; or, + within a display generated by the Derivative Works, if and + wherever such third-party notices normally appear. The contents + of the NOTICE file are for informational purposes only and + do not modify the License. You may add Your own attribution + notices within Derivative Works that You distribute, alongside + or as an addendum to the NOTICE text from the Work, provided + that such additional attribution notices cannot be construed + as modifying the License. + + You may add Your own copyright statement to Your modifications and + may provide additional or different license terms and conditions + for use, reproduction, or distribution of Your modifications, or + for any such Derivative Works as a whole, provided Your use, + reproduction, and distribution of the Work otherwise complies with + the conditions stated in this License. + + 5. Submission of Contributions. Unless You explicitly state otherwise, + any Contribution intentionally submitted for inclusion in the Work + by You to the Licensor shall be under the terms and conditions of + this License, without any additional terms or conditions. + Notwithstanding the above, nothing herein shall supersede or modify + the terms of any separate license agreement you may have executed + with Licensor regarding such Contributions. + + 6. Trademarks. This License does not grant permission to use the trade + names, trademarks, service marks, or product names of the Licensor, + except as required for reasonable and customary use in describing the + origin of the Work and reproducing the content of the NOTICE file. + + 7. Disclaimer of Warranty. Unless required by applicable law or + agreed to in writing, Licensor provides the Work (and each + Contributor provides its Contributions) on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + implied, including, without limitation, any warranties or conditions + of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A + PARTICULAR PURPOSE. You are solely responsible for determining the + appropriateness of using or redistributing the Work and assume any + risks associated with Your exercise of permissions under this License. + + 8. Limitation of Liability. In no event and under no legal theory, + whether in tort (including negligence), contract, or otherwise, + unless required by applicable law (such as deliberate and grossly + negligent acts) or agreed to in writing, shall any Contributor be + liable to You for damages, including any direct, indirect, special, + incidental, or consequential damages of any character arising as a + result of this License or out of the use or inability to use the + Work (including but not limited to damages for loss of goodwill, + work stoppage, computer failure or malfunction, or any and all + other commercial damages or losses), even if such Contributor + has been advised of the possibility of such damages. + + 9. Accepting Warranty or Additional Liability. While redistributing + the Work or Derivative Works thereof, You may choose to offer, + and charge a fee for, acceptance of support, warranty, indemnity, + or other liability obligations and/or rights consistent with this + License. However, in accepting such obligations, You may act only + on Your own behalf and on Your sole responsibility, not on behalf + of any other Contributor, and only if You agree to indemnify, + defend, and hold each Contributor harmless for any liability + incurred by, or claims asserted against, such Contributor by reason + of your accepting any such warranty or additional liability. + + END OF TERMS AND CONDITIONS + + APPENDIX: How to apply the Apache License to your work. + + To apply the Apache License to your work, attach the following + boilerplate notice, with the fields enclosed by brackets "[]" + replaced with your own identifying information. (Don't include + the brackets!) The text should be enclosed in the appropriate + comment syntax for the file format. We also recommend that a + file or class name and description of purpose be included on the + same "printed page" as the copyright notice for easier + identification within third-party archives. + + Copyright [yyyy] [name of copyright owner] + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. diff --git a/utilities/branding/centos/build_srpm.data b/utilities/branding/centos/build_srpm.data new file mode 100755 index 000000000..188f58ba0 --- /dev/null +++ b/utilities/branding/centos/build_srpm.data @@ -0,0 +1,2 @@ +SRC_DIR="sources" +TIS_PATCH_VER=6 diff --git a/utilities/branding/centos/wrs-branding.spec b/utilities/branding/centos/wrs-branding.spec new file mode 100755 index 000000000..5ce029832 --- /dev/null +++ b/utilities/branding/centos/wrs-branding.spec @@ -0,0 +1,28 @@ +Summary: Titanium Cloud Branding Information +Name: wrs-branding +Version: 4.0.0 +Release: %{tis_patch_ver}%{?_tis_dist} +License: Apache-2.0 +Group: base +Packager: Wind River +URL: unknown + +Source0: %{name}-%{version}.tar.gz + +%define cgcs_sdk_deploy_dir /opt/deploy/cgcs_sdk + +%description +Titanium Cloud Branding allows alternate branding to be used for Horizon +in place of the default included with Titanium Cloud. + +%install +rm -rf $RPM_BUILD_ROOT +mkdir -p $RPM_BUILD_ROOT/%{cgcs_sdk_deploy_dir} +install -m 644 %{SOURCE0} $RPM_BUILD_ROOT/%{cgcs_sdk_deploy_dir}/%{name}-%{version}.tgz + +%clean +rm -rf $RPM_BUILD_ROOT + +%files +%defattr(-,root,root,-) +%{cgcs_sdk_deploy_dir} diff --git a/utilities/branding/sources/LICENSE b/utilities/branding/sources/LICENSE new file mode 100644 index 000000000..d64569567 --- /dev/null +++ b/utilities/branding/sources/LICENSE @@ -0,0 +1,202 @@ + + Apache License + Version 2.0, January 2004 + http://www.apache.org/licenses/ + + TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + + 1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix below). + + "Derivative Works" shall mean any work, whether in Source or Object + form, that is based on (or derived from) the Work and for which the + editorial revisions, annotations, elaborations, or other modifications + represent, as a whole, an original work of authorship. For the purposes + of this License, Derivative Works shall not include works that remain + separable from, or merely link (or bind by name) to the interfaces of, + the Work and Derivative Works thereof. + + "Contribution" shall mean any work of authorship, including + the original version of the Work and any modifications or additions + to that Work or Derivative Works thereof, that is intentionally + submitted to Licensor for inclusion in the Work by the copyright owner + or by an individual or Legal Entity authorized to submit on behalf of + the copyright owner. For the purposes of this definition, "submitted" + means any form of electronic, verbal, or written communication sent + to the Licensor or its representatives, including but not limited to + communication on electronic mailing lists, source code control systems, + and issue tracking systems that are managed by, or on behalf of, the + Licensor for the purpose of discussing and improving the Work, but + excluding communication that is conspicuously marked or otherwise + designated in writing by the copyright owner as "Not a Contribution." + + "Contributor" shall mean Licensor and any individual or Legal Entity + on behalf of whom a Contribution has been received by Licensor and + subsequently incorporated within the Work. + + 2. Grant of Copyright License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + copyright license to reproduce, prepare Derivative Works of, + publicly display, publicly perform, sublicense, and distribute the + Work and such Derivative Works in Source or Object form. + + 3. Grant of Patent License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + (except as stated in this section) patent license to make, have made, + use, offer to sell, sell, import, and otherwise transfer the Work, + where such license applies only to those patent claims licensable + by such Contributor that are necessarily infringed by their + Contribution(s) alone or by combination of their Contribution(s) + with the Work to which such Contribution(s) was submitted. If You + institute patent litigation against any entity (including a + cross-claim or counterclaim in a lawsuit) alleging that the Work + or a Contribution incorporated within the Work constitutes direct + or contributory patent infringement, then any patent licenses + granted to You under this License for that Work shall terminate + as of the date such litigation is filed. + + 4. Redistribution. You may reproduce and distribute copies of the + Work or Derivative Works thereof in any medium, with or without + modifications, and in Source or Object form, provided that You + meet the following conditions: + + (a) You must give any other recipients of the Work or + Derivative Works a copy of this License; and + + (b) You must cause any modified files to carry prominent notices + stating that You changed the files; and + + (c) You must retain, in the Source form of any Derivative Works + that You distribute, all copyright, patent, trademark, and + attribution notices from the Source form of the Work, + excluding those notices that do not pertain to any part of + the Derivative Works; and + + (d) If the Work includes a "NOTICE" text file as part of its + distribution, then any Derivative Works that You distribute must + include a readable copy of the attribution notices contained + within such NOTICE file, excluding those notices that do not + pertain to any part of the Derivative Works, in at least one + of the following places: within a NOTICE text file distributed + as part of the Derivative Works; within the Source form or + documentation, if provided along with the Derivative Works; or, + within a display generated by the Derivative Works, if and + wherever such third-party notices normally appear. The contents + of the NOTICE file are for informational purposes only and + do not modify the License. You may add Your own attribution + notices within Derivative Works that You distribute, alongside + or as an addendum to the NOTICE text from the Work, provided + that such additional attribution notices cannot be construed + as modifying the License. + + You may add Your own copyright statement to Your modifications and + may provide additional or different license terms and conditions + for use, reproduction, or distribution of Your modifications, or + for any such Derivative Works as a whole, provided Your use, + reproduction, and distribution of the Work otherwise complies with + the conditions stated in this License. + + 5. Submission of Contributions. Unless You explicitly state otherwise, + any Contribution intentionally submitted for inclusion in the Work + by You to the Licensor shall be under the terms and conditions of + this License, without any additional terms or conditions. + Notwithstanding the above, nothing herein shall supersede or modify + the terms of any separate license agreement you may have executed + with Licensor regarding such Contributions. + + 6. Trademarks. This License does not grant permission to use the trade + names, trademarks, service marks, or product names of the Licensor, + except as required for reasonable and customary use in describing the + origin of the Work and reproducing the content of the NOTICE file. + + 7. Disclaimer of Warranty. Unless required by applicable law or + agreed to in writing, Licensor provides the Work (and each + Contributor provides its Contributions) on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + implied, including, without limitation, any warranties or conditions + of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A + PARTICULAR PURPOSE. You are solely responsible for determining the + appropriateness of using or redistributing the Work and assume any + risks associated with Your exercise of permissions under this License. + + 8. Limitation of Liability. In no event and under no legal theory, + whether in tort (including negligence), contract, or otherwise, + unless required by applicable law (such as deliberate and grossly + negligent acts) or agreed to in writing, shall any Contributor be + liable to You for damages, including any direct, indirect, special, + incidental, or consequential damages of any character arising as a + result of this License or out of the use or inability to use the + Work (including but not limited to damages for loss of goodwill, + work stoppage, computer failure or malfunction, or any and all + other commercial damages or losses), even if such Contributor + has been advised of the possibility of such damages. + + 9. Accepting Warranty or Additional Liability. While redistributing + the Work or Derivative Works thereof, You may choose to offer, + and charge a fee for, acceptance of support, warranty, indemnity, + or other liability obligations and/or rights consistent with this + License. However, in accepting such obligations, You may act only + on Your own behalf and on Your sole responsibility, not on behalf + of any other Contributor, and only if You agree to indemnify, + defend, and hold each Contributor harmless for any liability + incurred by, or claims asserted against, such Contributor by reason + of your accepting any such warranty or additional liability. + + END OF TERMS AND CONDITIONS + + APPENDIX: How to apply the Apache License to your work. + + To apply the Apache License to your work, attach the following + boilerplate notice, with the fields enclosed by brackets "[]" + replaced with your own identifying information. (Don't include + the brackets!) The text should be enclosed in the appropriate + comment syntax for the file format. We also recommend that a + file or class name and description of purpose be included on the + same "printed page" as the copyright notice for easier + identification within third-party archives. + + Copyright [yyyy] [name of copyright owner] + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. diff --git a/utilities/branding/sources/horizon/README b/utilities/branding/sources/horizon/README new file mode 100755 index 000000000..fda4d4983 --- /dev/null +++ b/utilities/branding/sources/horizon/README @@ -0,0 +1,74 @@ +Copyright © 2014-2017 Wind River Systems, Inc. + +SPDX-License-Identifier: Apache-2.0 +----------------------------------------------------------------------- + + +Titanium Cloud Custom Branding +------------------------------- + +Custom branding for the Titanium Cloud is achieved through the creation and application +of a tarball containing a customized horizon theme and associated branding files + + +Creating a Custom Branding Tarball +---------------------------------- + +The tarball containing the customized branding files must be of the extension .tgz; its +file name has no constraints. 'sample_branding.tgz' has been included as an example of +the end result. Please note that branding tarballs created for previous releases of +Titanium Cloud are not forward-compatible, and must be recreated to accommodate the +latest branding styles present in Horizon. An example of how to compress an existing +theme would be to do the following from inside the branding's root directory: + tar czf new_branding.tgz * + +Two types of items are required in the branding tarball: + 1) The contents of a valid horizon theme directory as documented here: + docs.openstack.org/developer/horizon/topics/customizing.html + i.e. in the top level of the tarball are the theme folders 'static' and 'templates' (if used). + Both the default and material themes included with horizon are available to be + inherited from if desired. Note that when referencing assets included in the custom theme, + the theme name will be 'custom'. + + To base the new theme off of the standard titanium cloud theme, or to view an example + of how the tarball should be formatted, refer to the example tarball named + sample_branding.tgz included with this SDK. + + 2) Also in the top level of the tarball, a file named manifest.py which is used to overwrite the default + horizon settings used by Titanium Cloud. A description of its contents are as follows: + + SITE_BRANDING is the name that will be used in the site title, note that there are + other occurrences of the branding name that must be changed directly in the templates, + + HORIZON_CONFIG["help_url"] is the link that the help button will redirect + users to, note that the knowledge library url must also be changed directly in + the template, + + Sample entries for these variables are shown below: + + SITE_BRANDING = "Sample System Name" + HORIZON_CONFIG["help_url"] = "http://www.windriver.com/support/" + + +Applying a Custom Branding Tarball +---------------------------------- + +This branding tarball can be applied at various stages, the steps for each stage are +described below: + + 1) Before running config_controller + i) Copy the branding tarball to the /opt/branding directory, once config_controller + is run this branding will be automatically used by horizon + + 2) After running config_controller + i) If a previous branding tarball was already in use, + delete it from /opt/branding, + ii) Copy the new branding tarball to the /opt/branding directory on the + active controller, + iii) Execute the command + sudo service horizon restart + this will process the new branding files on the active controller, + iv) Lock the inactive controller, + v) Unlock the inactive controller. + lock and unlock can coincide with login banner customization, see + also README.banner diff --git a/utilities/branding/sources/horizon/sample_branding.tgz b/utilities/branding/sources/horizon/sample_branding.tgz new file mode 100755 index 000000000..59aba8614 Binary files /dev/null and b/utilities/branding/sources/horizon/sample_branding.tgz differ diff --git a/utilities/branding/sources/login-banner/README b/utilities/branding/sources/login-banner/README new file mode 100755 index 000000000..52ae11fd5 --- /dev/null +++ b/utilities/branding/sources/login-banner/README @@ -0,0 +1,132 @@ +Copyright (c) 2016 Wind River Systems, Inc. + +SPDX-License-Identifier: Apache-2.0 +-------------------------------------------------------------------- + +Titanium Cloud Customization of Login Banner Files +--------------------------------------------------- + +This feature permits the customization of prelogin message (issue) and +postlogin message of the day (motd) across the entire Titanium Cloud +cluster. It is a convenience feature that simplifies propagation of +the customized files. + +Introduction +------------ + +See also 'man issue' and 'man motd'. + +The following files can be customized, and are treated by this feature: + /etc/issue (login banner, console) + /etc/issue.net (login banner, ssh) + /etc/motd.head (message of the day, header) + /etc/motd.tail (message of the day, footer) + +The following files are not customizable, because each is generated by +software: + /etc/motd + /etc/sysinv/motd.system + /etc/platform/motd.license + +issue and issue.net are free standing files, while /etc/motd is +generated from the following sources, in the following order: + /etc/motd.head + /etc/sysinv/motd.system + /etc/platform/motd.license + /etc/motd.tail + +The customization procedure during Titanium Cloud Installation and +Commissioning is summarized as follows: + 1) provide customization files + 2) run 'config_controller' + +The customization procedure after config_controller is summarized +as follows: + 3) provide customization files + 4) run 'apply_banner_customization' + 5) lock/unlock each node + +Example tarball +--------------- + +sample_banner.tgz has been provided (adjacent to this README). +Extract the tarball on the active controller to the directory +/opt/banner, or as indicated in the following sections. + +The tarball contains examples of the four customizable login banner files. + +Procedure prior to config_controller +------------------------------------ + +When setting up a new cluster, immediately after the first controller +boots and before running config_controller: + +1) Provide customization files + +To customize any of the four customizable banner files listed above, +provide the new files in the following location: + /opt/banner/issue + /opt/banner/issue.net + /opt/banner/motd.head + /opt/banner/motd.tail + +I.e., + sudo mkdir -p /opt/banner + sudo tar xf sample_banner.tgz -C /opt/banner + +Each file is customized individually; Edit or remove these files in +/opt/banner according to requirements. + +2) Run config_controller + +When config_controller 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, +customization can be repeated after config_controller using the +following 'Procedure after deployment'; errors for customization do not +impact config_controller. + +Procedure after deployment +-------------------------- +Customization can be performed any time after deployment: + +1) Login to the active controller +2) Switch to root user, i.e., 'sudo bash' +3) Provide any of the customized banner files in /opt/banner, or another + directory: + /opt/banner/issue + /opt/banner/issue.net + /opt/banner/motd.head + /opt/banner/motd.tail +4) Apply the customization, execute: + 'apply_banner_customization /opt/banner', or + 'apply_banner_customization ' + + The default path, if no parameter is specified, is the current + working directory, i.e., + 'apply_banner_customization $(pwd)' + + The banners are applied to configuration and installed on the + current node, active controller. + +5) Lock and unlock other nodes in the cluster, either from the CLI or + the GUI, to install the customization on each node. Lock and unlock + can coincide with horizon branding procedure; see also adjacent + ../horizon/README for horizon branding. + + All subsequent newly added nodes will automatically get the banner + customization. + +Manual Restoration +------------------ + +Replaced versions of banner files can be retrieved at the user's +discretion from each node in the cluster, from the directory: + /opt/banner.bk + +A maximum of 10 versions of each file are maintained, with the oldest +versions replaced only when the count reaches 10. diff --git a/utilities/branding/sources/login-banner/sample_banner.tgz b/utilities/branding/sources/login-banner/sample_banner.tgz new file mode 100644 index 000000000..c6bfad919 Binary files /dev/null and b/utilities/branding/sources/login-banner/sample_banner.tgz differ