Skip to content

v0.3.0 Post install checklist

AnkshitJain edited this page Mar 18, 2018 · 2 revisions
  1. Do you have an active demo lab setup on mainserver and on gitlab?

  2. Are your students able to register and sign-in to gitlab?
    https://autolab.bits-goa.ac.in

  3. Is your demo lab evaluation setup working for you and your students?

  4. When an evaluation of an active lab is submitted, do you see scoreboard being updated?

  5. Are all the containers running and none have exited?
    $sudo docker ps -a

  6. Is the status page reflecting the running status of the AutolabJS containers?
    https://autolab.bits-goa.ac.in:9000/status

  7. Are there enough execution nodes?
    Required number of execution nodes = (4/3)*no. of evaluation requests per second * evaluation time per request.

  8. Is the AutolabJS performing well when given the expected number of evaluation requests?
    Please ask your instruction team to manually submit the expected number of evaluation requests and check the system response time.

** Post Install Checklist included in Deployment Tests **

The post install checklist is taken as a list of actions that should be successful after a new installation of AutolabJS.

The mapping for post install checklist

  1. DemoLabCheck:

    1. Create a lab author account on Gitlab.
    2. Create few student accounts on Gitlab. The student code used will be the ones from unit tests and io tests.
    3. The necessary files are committed to the respective repositories using gitlab.js.
    4. The evaluations are run using the submit.js script.

    Checks Completed:

    • Active demo lab setup on mainserver and on gitlab
    • Demo lab evaluation setup working for you and your students
  2. GitLabChecks:

    1. Unit tests for gitlab.js

    Checks completed:

    • Students able to register, sign-in, and commit to gitlab
  3. ScoreboardChecks:

    1. Scoreboard tests similar to functional tests

    Checks completed:

    • Scoreboard updated accordingly, when submission requests are made
  4. ContainerCheck:

    1. Check working status of all the docker containers using $sudo docker ps -a and existence of autolab-restart.sh at the right location.

    Checks completed:

    • Healthy status of all the separate components
  5. WebsiteCheck:

    1. Running of website load tests

    Checks completed:

    • Website up and running as expected
    • Execution nodes status verified
  6. GitLab_EN_CloningCheck:

    1. Cloning a test repo from all the execution nodes

    Checks completed:

    • All execution nodes are configured with Gitlab
  7. ContainerLocaleCheck:

    1. Run an evaluation with special characters in the submission

    Checks completed:

    • Docker containers are up with utf-8 locale and do not fail for the submission
  8. ConcurrentEvaluationsCheck:

    1. Submit concurrent evaluation requests to verify concurrency of execution.
    2. This would be done with the execution_node.bats test module.

    Checks completed:

    • Concurrent submission requests are handled by different execution nodes and evaluations are parallel.
  9. LoadCheck:

    1. Submit concurrent evaluation requests to verify concurrency of execution.
    2. This would be done with the execution_node.bats test module.

    Checks completed:

    • Concurrent submission requests are handled by different execution nodes and evaluations are parallel.
Clone this wiki locally
You can’t perform that action at this time.