From 1ed2b6fce2c08867c55786fc4aeebe983f312b4c Mon Sep 17 00:00:00 2001 From: Tomáš Levora Date: Tue, 12 Nov 2019 14:28:27 +0000 Subject: Revert "Fix packaging offline-installer" This reverts commit 92477974b68c7638a43ffc869e3ea9fb854b3534. Reason for revert: Not solved handling of application_configuration.yml in package.py Change-Id: I814c01dc1f7334a961e991c42fd485d9af4675a1 Signed-off-by: Tomas Levora Issue-ID: OOM-2201 --- docs/InstallGuide.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/InstallGuide.rst') diff --git a/docs/InstallGuide.rst b/docs/InstallGuide.rst index 947cd727..9239cad9 100644 --- a/docs/InstallGuide.rst +++ b/docs/InstallGuide.rst @@ -233,7 +233,7 @@ After all the changes, the ``'hosts.yml'`` should look similar to this:: infrastructure: hosts: infrastructure-server: - ansible_host: 10.8.8.100 + ansible_host: 10.8.8.13 #IP used for communication between infra and kubernetes nodes, must be specified. cluster_ip: 10.8.8.100 @@ -326,7 +326,7 @@ Second one controls time zone setting on host. It's value should be time zone na Final configuration can resemble the following:: resources_dir: /data - resources_filename: resources_package.tar + resources_filename: resources-package.tar app_data_path: /opt/onap app_name: onap timesync: @@ -432,7 +432,7 @@ Part 4. Post-installation and troubleshooting After all of the playbooks are run successfully, it will still take a lot of time until all pods are up and running. You can monitor your newly created kubernetes cluster for example like this:: - $ ssh -i ~/.ssh/offline_ssh_key root@10.8.8.100 # tailor this command to connect to your infra-node + $ ssh -i ~/.ssh/offline_ssh_key root@10.8.8.4 # tailor this command to connect to your infra-node $ watch -d -n 5 'kubectl get pods --all-namespaces' Alternatively you can monitor progress with ``helm_deployment_status.py`` script located in offline-installer directory. Transfer it to infra-node and run:: -- cgit 1.2.3-korg