Technical Manual. Software Quality Analysis as a Service (SQUAAD) Team No.1. Implementers: Aleksandr Chernousov Chris Harman Supicha Phadungslip

Transcription

1 Technical Manual Software Quality Analysis as a Service (SQUAAD) Team No.1 Implementers: Aleksandr Chernousov Chris Harman Supicha Phadungslip Testers: Kavneet Kaur Reza Khazali George Llames Sahar Pure 04/25/2018

2 Version History Date Author Version Changes made Rationale 04/27/2018 CH 1.0 Add technical documentation for application build/deployment Delivery for as-built package 2

3 Table of Contents Technical Manual 1 Version History 2 Table of Contents 3 Build Dependencies 4 System Requirements 4 Additional Recommended 4 Build steps 4 Docker Toolbox - Windows 4 Linux & Mac Build 6 Auto Reload 6 Generating Docs 6 Deploying on AWS 7 Check Application Server Logs 8 Clearing Out Docker Images to Regain Space (Optionally Run This After Deploy) 8 HTTPS Cert Generation 8 Clear Your Database and Rebuild 10 Populating the DB with New Records 10 3

4 Build Dependencies or Docker Toolbox - for Windows or Mac (ships with everything you will need) Install Virtualbox: brew cask install virtualbox - for Mac Only Docker Docker Compose System Requirements 2GB of RAM 8GB Available Disk Space Additional Recommended Git Bash - for Windows If you receive the following error on Windows: No such file or directory bash, it means that your local git pull is converting line endings to Windows formatting CRLF, rather than respecting the line endings in the repo. You can resolve the issue by following the 4 commands here. Install the above dependencies before proceeding onto the build steps Build steps Docker Toolbox - Windows (using Git Bash terminal) Note: Steps 1-2 are required for only the first build - start with step 3 after you have created a Docker Machine successfully. 1. Confirm Docker toolbox installation was successful by confirming versions of required software. Add your local Docker installation directory to the PATH if the following commands do not work as expected. 4

5 $ docker-machine -v docker-machine.exe version , build $ docker -v Docker version ce, build 02c1d87 $ docker-compose -v docker-compose version , build c7bdf9e3 2. Create a Docker Machine to hold Docker containers for the application. The below command specifies the following configuration (note that your desired configuration may vary depending on your local machine): o use the virtualbox driver o o o o allow the virtual disk to grow to up to 100GB allocate 8GB RAM allocate 2 CPU cores name the machine squaad $ docker-machine create -d virtualbox --virtualbox-disk-size "100000" -- virtualbox-memory "8000" --virtualbox-cpu-count "2" squaad 3. After creating the Docker Machine, check that it is there as expected. $ docker-machine ls NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS squaad * virtualbox Running tcp:// :2376 v ce 4. Set your Docker Machine environment to squaad (or whatever you named your machine above - the Docker Toolbox default name is default). The setting only affects the current shell session - you must run it every time you open a new shell you wish to interact with the squaad Docker Machine in. $ eval $(docker-machine env squaad) 5. Navigate to the top-level directory for the repo locally. chris@desktop-93ieiib MINGW64 ~ $ cd ~/Documents/repos/SQUAAD/ chris@desktop-93ieiib MINGW64 ~/Documents/repos/SQUAAD (create-build) $ 6. Run the command to bring up the containers and build the application. $ docker-compose up --build 7. Verify that the containers are up and running. 5

6 MINGW64 ~/Documents/repos/SQUAAD (create-build) $ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES d03e3c643c86 squaad_proxy "nginx -g 'daemon..." 6 minutes ago Up 6 minutes :80->80/tcp, :443->443/tcp squaad_proxy_1 1bc8a85128e9 squaad_client "npm start" 6 minutes ago Up 6 minutes 3000/tcp squaad_client_ a98b squaad_server "/usr/entrypoint.s..." 4 hours ago Up 4 hours 8000/tcp squaad_server_1 ae38192dc02d postgres:9.6 "docker-entrypoint..." 22 hours ago Up 16 hours 5432/tcp squaad_postgres_1 8. Navigate to the URL from step 3, in my case it is The 'https' is important here, and you can expect to see a warning about the self-signed cert locally (you will need to bypass it). Linux & Mac Build (tested on Xubuntu and Docker for Mac) 1. Follow steps 5, 6, and 7 from 'Docker Toolbox - Windows' Instructions above. 2. Navigate to localhost. Auto Reload Auto reload has been tested on the configurations above - code changes to the /src directory in the server directory will trigger a reload of the API code. Similarly, code changes to the /src directory in the client directory will reload the React. Things that will not auto reload - these will require a rebuild: changes to package.json adding/deleting entire files changes to the.sql files in /db - these require the postgres-data volume to be removed to be recognized changes to proxy configuration Dockerfile and docker-compose.yml changes Generating Docs Run the docs generation script (uses ESDoc): Client chris@desktop-93ieiib MINGW64 ~/Documents/repos/squaad (code-docs) 6

7 $ docker-compose run client npm run esdoc $ docker cp $(docker ps -aq head -n 1):/tmp/esdoc/./client/docs $ docker stop $(docker ps -aq head -n 1) $ docker rm $(docker ps -aq head -n 1) Server chris@desktop-93ieiib MINGW64 ~/Documents/repos/squaad (code-docs) $ docker-compose run server npm run esdoc $ docker cp $(docker ps -aq head -n 1):/tmp/esdoc/./server/docs $ docker stop $(docker ps -aq head -n 1) $ docker rm $(docker ps -aq head -n 1) Docs are now available at./client/docs/esdoc and./server/docs/esdoc. Deploying on AWS 1. SSH onto the server ssh -i "squaad.pem" ubuntu@ec us-east-2.compute.amazonaws.com 2. Elevate your shell privileges sudo su 3. Change directory to the SQUAAD repo cd /home/ubuntu/squaad/squaad 4. Stash changes (only changes should be the real HTTP cert/key) git stash 5. Ensure you are on the master branch git checkout master 6. Pull the most recent changes git pull 7. Pop the stashed crt/key for HTTPS back (that way we don't commit this to the repo) git stash pop 8. Rebuild/redeploy the app with the newest code from master HOST=squaadweb.com docker-compose up --build -d 7

8 Check Application Server Logs 1. SSH onto the server ssh -i "squaad.pem" 2. Elevate your shell privileges sudo su 3. Change directory to the SQUAAD repo cd /home/ubuntu/squaad/squaad 4. View logs docker-compose logs -f 5. Ctrl+c to exit Clearing Out Docker Images to Regain Space (Optionally Run This After Deploy) 1. SSH onto the server ssh -i "squaad.pem" 2. Elevate your shell privileges sudo su 3. Remove unused images docker rmi $(docker images -a grep "^<none>" awk '{print $3}') HTTPS Cert Generation Overall Strategy We use the Let's Encrypt certbot utility to generate a free and totally secure HTTPS cert. Certbot uses a series of tests, the easiest and most common being a placement of a specific file on an NGINX server via HTTP. Since our deployment redirects all HTTP requests to HTTPS by default, we take the following approach: 8

9 - Ensure that squaadweb.com and are both pointing to the AWS server - Spin down the application - Spin up a generic NGINX Docker container, exposing port 80 to receive HTTP requests - Install certbot within the NGINX container - Run the cert generation utility - Copy the certs out from the container onto the AWS server - Put the certs into the proper placement for the application deployment - Deploy the application as per usual Requirements - Root SSH access to the AWS server - Familiarity with Docker (specifically docker cp) Steps ssh -i 'squaad.pem' ubuntu@ec us-east-2.compute.amazonaws.com (on AWS server) sudo su docker stop $(docker ps -aq) docker run -p 80:80 --name certbot_nginx -it nginx:1.13 bash (in Docker container) echo 'deb stretch-backports main' >> etc/apt/sources.list apt-get update apt-get install python-certbot-nginx -t stretch-backports -y certbot certonly --standalone -d squaadweb.com -d (prompts for and agreement to terms of service - answer as appropriate) cp /etc/letsencrypt/live/squaadweb.com/fullchain.pem. cp /etc/letsencrypt/live/squaadweb.com/privkey.pem. <Ctrl+d> (on AWS server) docker cp certbot_nginx:fullchain.pem. docker cp certbot_nginx:privkey.pem. mkdir -p /etc/letsencrypt/live/squaadweb.com/ mv fullchain.pem /etc/letsencrypt/live/squaadweb.com mv privkey.pem /etc/letsencrypt/live/squaadweb.com cp /etc/letsencrypt/live/squaadweb.com/fullchain.pem /home/ubuntu/squaad/squaad/proxy/ssl.crt cp /etc/letsencrypt/live/squaadweb.com/privkey.pem /home/ubuntu/squaad/squaad/proxy/ssl.key cd /home/ubuntu/squaad/squaad HOST=squaadweb.com docker-compose up --build -d docker rm certbot_nginx (verify that both squaadweb.com and are shown as secure) 9

10 Clear Your Database and Rebuild docker stop $(docker ps -aq) docker rm -v squaad_postgres_1 docker volume rm squaad_postgres-data docker-compose up --build Note: You will lose your current local database changes and will be set back to the base structure with only the data in the migrations e.g. only login and other default logins will be available. The.sql scripts in this directory will only run on the very first time the database builds. Removing the data volume simulates the initial build and triggers the data load, which means our database version control is essentially a flush-and-fill currently. Populating the DB with New Records 1. SCP the file onto the server, then SSH onto the server (for a server update) scp -i "squaad.pem" huawei-request-insert ubuntu@ec us-east- 2.compute.amazonaws.com:/home/ubuntu ssh -i "squaad.pem" ubuntu@ec us-east-2.compute.amazonaws.com 2. From a directory containing the dump file with only inserts (using huaweirequest-insert as an example file) 3. Determine the new projects to be inserted cat huawei-request-insert grep "INSERT INTO applications"; example result: INSERT INTO applications (repo_url, application) VALUES (' 'apache-carbondata'); INSERT INTO applications (repo_url, application) VALUES (' 'Huawei-openstack4j'); INSERT INTO applications (repo_url, application) VALUES (' 'hyperledger-fabric-sdkjava'); 4. Copy the new dump into the database container docker cp huawei-request-insert squaad_postgres_1:/ 10

11 5. Drop pkey constraint on cpairs docker exec squaad_postgres_1 psql -U postgres -c " ALTER TABLE public.cpairs DROP CONSTRAINT cpairs_pkey; " 6. Drop pkey constraint on impact_pairs docker exec squaad_postgres_1 psql -U postgres -c " ALTER TABLE public.impact_pairs DROP CONSTRAINT impact_pairs_pkey; " 7. Run the new dump's SQL code to populate the tables docker exec squaad_postgres_1 psql -U postgres -f huawei-request-insert 8. Drop the impact_pairs and cpairs sequence index docker exec squaad_postgres_1 psql -U postgres -c " DROP SEQUENCE public.cpairs_id_seq CASCADE; DROP SEQUENCE public.impact_pairs_id_seq CASCADE; " 9. Drop/add pkey constraint back on cpairs docker exec squaad_postgres_1 psql -U postgres -c " ALTER TABLE public.cpairs DROP COLUMN id; ALTER TABLE public.cpairs ADD COLUMN id SERIAL PRIMARY KEY; " 10. Drop/add pkey constraint back on impact_pairs docker exec squaad_postgres_1 psql -U postgres -c " ALTER TABLE public.impact_pairs DROP COLUMN id; ALTER TABLE public.impact_pairs ADD COLUMN id SERIAL PRIMARY KEY; " 11. Insert rows into the project table for each of the application datasets docker exec squaad_postgres_1 psql -U postgres -c " INSERT INTO project (name, repo_url, ispublic, prefix, compile_command, build_folder, source_folder, status) VALUES ('apache-carbondata', ' 1, '', '', '', '', 'ACTIVE'); INSERT INTO project (name, repo_url, ispublic, prefix, compile_command, build_folder, source_folder, status) VALUES ('Huawei-openstack4j', ' 1, '', '', '', '', 'ACTIVE'); INSERT INTO project (name, repo_url, ispublic, prefix, compile_command, build_folder, source_folder, status) VALUES 11

12 ('hyperledger-fabric-sdk-java', ' 1, '', '', '', '', 'ACTIVE'); " 12