Uploaded image for project: 'Acumos'
  1. Acumos
  2. ACUMOS-2639

acumos AIO sudo/non-sudo install fails

    XMLWordPrintable

    Details

    • Sprint:
      Boreas Dev Sprint 4

      Description

      Attempted to follow the notes for AIO sudo/non-sudo acumos install process see below, but failed as listed

      root@acumos-onclick-dev1:~/acumos# echo $ACUMOS_DOMAIN

      acumos-oneclick-dev1.eastus.cloudapp.azure.com

      root@acumos-onclick-dev1:~/acumos# git clone https://gerrit.acumos.org/r/system-integration

      Cloning into 'system-integration'...

      remote: Total 844 (delta 0), reused 844 (delta 0)

      Receiving objects: 100% (844/844), 861.37 KiB | 0 bytes/s, done.

      Resolving deltas: 100% (371/371), done.

      Checking connectivity... done.

      root@acumos-onclick-dev1:~/acumos# git fetch https://gerrit.acumos.org/r/system-integration refs/changes/97/3897/2 && git checkout FETCH_HEAD

      fatal: Not a git repository (or any of the parent directories): .git

      Here is the process that has been implemented to address this issue. This is from the updated user guide in patch https://gerrit.acumos.org/r/#/c/3897/ 

      For the Impatient (TL;DR)

      NOTICE:

      • this process will remove/install software on your host, and configure it e.g. firewall and security rules. Only execute this process if you understand the implications or are executing the process in a VM/host that you can easily re-create.
      • by default, the Acumos platform is deployed with service exposure options typical for development environments. Production environments and especially public environments will need additional planning and restrictions on exposed services, that otherwise could expose your host to security risks. FOR TEST PURPOSES ONLY; USE AT YOUR OWN RISK.

      Deploying as a Privileged (sudo) User

      This process is for a user that wants to execute all steps in the deployment process using their host account. To deploy the Acumos platform with the default options, as a user on a linux host with at least 16GB RAM and admin (sudo) permission, follow the process below.

      • clone the system-integration repo

      $ git clone https://gerrit.acumos.org/r/system-integration

      • using bash, check if the user is part of the docker group, and add if not

      $ if [[ "$(id -nG "$USER" | grep docker)" == "" ]]; then sudo usermod -G docker $USER; fi

      • if you see "usermod: group 'docker' does not exist", install docker (e.g. using setup-docker.sh in the system-integration/tools folder) and run the command above again. Once you do not see the message above, logout and re-login.
      • execute the following command to install/configure prerequisites, including k8s, MariaDB, and the ELK stack, using your user account, and hostname as the domain name you will use to access the deployed platform.

      $ bash system-integration/AIO/acumos_k8s_prep.sh $USER $HOSTNAME

      • When you see "Prerequisites setup is complete." as the result of the command above, execute the following commands to complete platform setup

      $ cd system-integration/AIO$ bash acumos_k8s_deploy.sh

      • when that command completes successfully, you should see a set of URLs to access the various platform services. You can also view the file "acumos.url" which will be in the system-integration/AIO folder
      • By default, the platform is not configured to require email confirmation of new accounts, so you can create a new account directly on the Portal home. To create an account with the Admin role (needed for various platform admin functions), use the create-user.sh script in the system-integration/AIO folder

      Preparation by Host Admin with Platform Deployment by Normal (non-sudo) User

      This process is for a host Admin (sudo user) to prepare the host for a normal (non-sudo) user that will complete the platform deployment, under their account.

      • Admin clones the system-integration repo

      $ git clone https://gerrit.acumos.org/r/system-integration

      • Admin ensures the user is part of the docker group
      • Admin executes the following command to install/configure prerequisites, including k8s, MariaDB, and the ELK stack, using their account. <user> in this case is the username of the normal user that will complete the deployment.

      $ bash system-integration/AIO/acumos_k8s_prep.sh <user> $HOSTNAME

      • When prerequisites setup is complete, the Admin copies the resulting environment files and system-integration clone to the user account, e.g.

      sudo cp -r acumos /home/<user>/.

      sudo chown <user>:<user> /home/<user>/acumos

      sudo cp -r system-integration /home/<user>/.

      sudo chown <user>:<user> /home/<user>/system-integration

      • The user executes the following commands to complete platform setup

      $ cd system-integration/AIO$ bash acumos_k8s_deploy.sh

       

        Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

            Assignee:
            blsaws Bryan Sullivan
            Reporter:
            bbhooper Bobbie Hooper
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: