Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Sign up like normal (email, pwd)
  • No activation email will be sent, you can find the activation link with the command
    root@rancher:~# kubectl logs dev-em-645d6bf559-h9tdq

    There will be a message with the activation link to navigate to in your web browser.

  • login to your new account and create an engagement
  • Add a public ssh key your profile

To login to the admin account

  • From the sign up page, click the 'reset password' button
  • use emailĀ admin@na.com
  • Perform the same exercise as signing up, by browsing the engagement manager pod logs for the password reset link
  • Paste the password reset link into your browser, and use the temp password from the logs
  • Create a new password


Once you create an engagement from the portal, a corresponding git repository will be created in the vvp-gitlab pod. To access the gitlab dashboard, you need to figure out what port is mapped for it. To do this, perform the same exercise as for the ext-haproxy pod, except instead now find the vvp-gitlab external port.

Navigate to http://10.66.35.69:<gitlab port> in your web browser. The root password is stored in the gitlab configmap and is base64 encoded. You should change the password as soon as possible.


Known Issues

If you are intending to only use VVP as an internal tool and not accessible publicly, you can mark the new git repo as "public" in the settings of the gitlab dashboard.

If VVP is available publicly but you wish to keep the heat templates stored in it private, you will need to modify the jenkins container file /usr/local/bin/ice-testengine to include the username/password for gitlab when cloning the heat templates from the gitlab instance.

To clone the git repo from gitlab, you will only be able to use http.