Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Feb 16 2019 19:04
    codecov[bot] commented #328
  • Feb 16 2019 19:04
    hrishikesh-dahiya synchronize #328
  • Feb 07 2019 12:14
    prasadtalasila closed #330
  • Feb 07 2019 12:14
    prasadtalasila commented #330
  • Feb 07 2019 08:15
    prasadtalasila commented #268
  • Feb 07 2019 08:12
    prasadtalasila labeled #330
  • Feb 07 2019 08:12
    prasadtalasila labeled #330
  • Feb 07 2019 08:12
    prasadtalasila opened #330
  • Jan 30 2019 11:25
    prasadtalasila labeled #329
  • Jan 30 2019 11:25
    prasadtalasila opened #329
  • Jan 29 2019 12:40
    prasadtalasila commented #328
  • Jan 29 2019 10:55
    hrishikesh-dahiya edited #328
  • Jan 29 2019 10:54
    codecov[bot] commented #328
  • Jan 29 2019 10:54
    hrishikesh-dahiya synchronize #328
  • Jan 23 2019 16:03
    prasadtalasila commented #306
  • Jan 21 2019 21:36
    prasadtalasila commented #306
  • Jan 20 2019 07:51
    hrishikesh-dahiya edited #328
  • Jan 20 2019 07:51
    hrishikesh-dahiya edited #328
  • Jan 20 2019 07:51
    hrishikesh-dahiya edited #328
  • Jan 20 2019 07:51
    hrishikesh-dahiya edited #328
Prasad Talasila
@prasadtalasila
The docker commands that are useful for this purpose are: docker commit, docker login, docker tag, docker push and docker pull.
The requirement is to take the verified images and push them to docker hib with correct names (see
for names) and a tag of 0.4.0
Prasad Talasila
@prasadtalasila
A new github repository https://github.com/autolabjs/containers has been setup and the containers for main server, load balancer and execution nodes have been successfully built. We need to push the docker images (or aliases to known versions of container images for gitlab and mysql). Helpful information is available on the wiki page: https://github.com/autolabjs/containers/wiki.
@jineetd you only need to procure MySQL and Gitlab containers from others. You can probably push an alias for both mysql and gitlab containers.
Once you have the working versions of these containers, you can try the installation again to make sure that everything goes through successfully.
jineetd
@jineetd
@prasadtalasila sir docker userid is jineetd
Prasad Talasila
@prasadtalasila
@jineetd You have been added to AutolabJS organization on Docker Hub. I have downgraded MySQL to v5.7.4 and made some minor improvements to install configuration. The code is available on mysql-fix branch (https://github.com/AutolabJS/AutolabJS/tree/mysql-fix). This branch should install seamlessly. Please try and let me know.
I have also pushed all the required containers to AutolabJS docker hub. Please see https://hub.docker.com/u/autolabjs/. If everything works for you on mysql-fix branch, you can try to replace the containers with the containers of autolabjs organization. Think about the problem and then I will provide an outline of the solution to implement. Let me know when you are ready for this step.
jineetd
@jineetd
Alright sir
jineetd
@jineetd
jineetd
@jineetd
Sir,these are the logs of deployment test
Should I update the containers to 18.04?
Prasad Talasila
@prasadtalasila
Good that you have a successful install.
The first step before upgrading to Ubuntu 18.04 is to modify the existing Dockerfiles of main server, load balancer and execution nodes to use the images pushed to autolabjs organization on the docker hub.
Please try that first.
jineetd
@jineetd
Ok I'll try
Prasad Talasila
@prasadtalasila
A sample Dockerfile for main server is as follows.
FROM autolabjs/nodejs:latest

COPY docker-entrypoint.sh /usr/local/bin/docker-entrypoint.sh

ENTRYPOINT ["docker-entrypoint.sh"]
Similarly, you can change for the load balancer and execution node also.
You can change the docker files, redo the installation to verify that it works as expected.
Thanks for trying.
Prasad Talasila
@prasadtalasila
@jineetd I have updated the container labels to 0.4.0. Please use 0.4.0 label instead of latest.
jineetd
@jineetd
jineet@jineet-Inspiron-5567:~/AutolabJS$ sudo docker pull autolabjs/gitlab-ce
Using default tag: latest
Error response from daemon: manifest for autolabjs/gitlab-ce:latest not found
How do I counter this?
Prasad Talasila
@prasadtalasila
The valid tags are available under tags of four repositories available at: https://hub.docker.com/u/autolabjs/
At the moment, the valid pull commands are:
docker pull autolabjs/gitlab-ce:10.1.4-ce.0
docker pull autolabjs/mysql:5.7.4
docker pull autolabjs/executionnode:0.4.0
docker pull autolabjs/nodejs:0.4.0
jineetd
@jineetd
Logs after reinstallation...
Prasad Talasila
@prasadtalasila
@jineetd the logs look good. Please send the PR to dev branch of AutolabJS
jineetd
@jineetd
Sir, the dockerfiles we have do not mention anything about the NODE version, they are taken directly from the dockerhub. In this case how do I upgrade them from 8.x to 10.x?
Prasad Talasila
@prasadtalasila
The dockerfiles are in https://github.com/AutolabJS/containers repository. Please update them and send a PR to that repository. Two changes are needed: Ubuntu 18.04 and Node 10.x.
Once the containers are updated in the repository, new containers are automatically get built on docker hub.
jineetd
@jineetd
@prasadtalasila Sir, what will the travis.yml file do?
What will be its functionality?
Chaitanya Mukka
@mukkachaitanya
The travis.yml file governs the working of Travis CI (Continuous integration).
before_script:
 - bash tests/install.sh
 - bash tests/compile.sh

script:
 - bash tests/test_runner.sh

after_script:
- ./main_server/node_modules/.bin/codecov -F ${TEST_TYPE:0:-6}
For the above example you instruct Travis to run those bash scripts accordingly.
Chaitanya Mukka
@mukkachaitanya
Its basically automation of testing, what the above example illustrates. Whenever you give a PR or a push code to the repository, the above script, called the travis build is spawned. Again in the above case, it runs the various tests and updates the test coverage of the same on codecov
Prasad Talasila
@prasadtalasila
@jineetd Please see the Travis tutorial (https://docs.travis-ci.com/user/tutorial/) and extensive docs (https://docs.travis-ci.com/). The Getting Started section of docs is particularly useful.
jineetd
@jineetd
Sir the installation of 0.5.0v went successful. Don't we have post install checklist for this? Or are they the same as for previous versions
Prasad Talasila
@prasadtalasila
@jineetd Thanks for checking out the installation setup. The post install checklist is same as that of AutolabJS v0.4.0. However, the deployment tests that run after the installation are failing even for a successful installation of AutolabJS v0.5.0. I created an issue AutolabJS/AutolabJS#317 to track the problem.
Chaitanya Mukka
@mukkachaitanya
Chaitanya Mukka
@mukkachaitanya
This looks good https://github.com/FiloSottile/mkcert but not sure if helpful.
Prasad Talasila
@prasadtalasila
@mukkachaitanya Thanks for the recommendations. The Node.js best practices sheet is good and has been added to the coding stanards page of AutolabJS.
The mkcert in principle is good, but can't be used in our project for two reasons.
  1. We need to install the certificate on client machines for which mkcert is of no use.
  2. We need to be able to configure the cryptographic settings of the certificates. mkcert hardcodes these choices.
    So, we need to give this project a pass.
Prasad Talasila
@prasadtalasila
Prasad Talasila
@prasadtalasila

Good news to all.
I have managed to separate the installation of execution nodes into a new repository: https://github.com/AutolabJS/executionnodes/
It's still a work in progress, but using this code base, you can install the execution nodes on as many servers as you want.
Please try the latest commit on dev branch: https://github.com/AutolabJS/executionnodes/tree/dev. The relevant install instructions are available at: https://github.com/AutolabJS/executionnodes/wiki/Install

I am truly excited about this result. Ideally this repo and AutolabJS v0.5.0 together should solve the installation difficulties to a large extent.
Do take it for a test drive and let me know. Your feedback is highly welcome.

Chaitanya Mukka
@mukkachaitanya
That's great news sir! This should also help us to have elasticity and auto-scaling. I'll go ahead and try it out.
Prasad Talasila
@prasadtalasila
A heads up to everyone. GSoC 2019 organization application has been pushed. The corresponding GSoC project site resides at: https://autolabjs.github.io/gsoc/.