...

On the other hand, light weight development environments can be created through Docker. That setup comes handy when you need to edit files and perform compilation from command line. Docker containers are great to run your TAT tests. Your development cycle can be speed up through the use of containers.

How it works?

Often, when it is time to develop code for ACS, you end up trying to mixed up these elements:

• The ACS Distribution (acs_binary) with all the base system already compiled. You want to develop code on top of that release.
• Your git local repository  (acs_repo)
• A working repository with patches (INTROOT) to be shared between nodes. (acs_working)

All these elements are not suitable to be stored inside the VM or Docker container, because of the space they use (Several GB) and that we want to recreate the environment several times during the development cycle. For that reason, that elements are kept inside the local host and they are shared with the environment through:

• NFS (network File Sharing)  between the VM (guest) and the host
• Docker Volumes (between container and host)

• Development Workflow

• Install Guide

• VirtualBox 6.1

• Vagrant 

• Docker (not need for Virtual Machines only setup)

• pyenv (recommended)

• Python required packages

Install python requirement with pip

pip install -r requirements.txt

• Setting up a Development Environment

Create .acsenv in your home folder

...

Warning: acs needs at least 4GB (4096MB) of memory.

• Setting up your development environment

Once the

• VPN Install on Centos 7 VM