Skip to content

Latest commit

 

History

History
93 lines (84 loc) · 4.33 KB

DEVELOPER.md

File metadata and controls

93 lines (84 loc) · 4.33 KB
Raw

How are make targets generated

Every sub-projects must provide with a Makefile that contains any targets. Currently we have;

  • ansible/build-fb-suse/Makefile
  • ansible/provision-and-execute-tests/Makefile
  • ansible/upload-win-packages/Makefile
  • terraform/ec2-suse-builders/Makefile
  • terraform/ec2-test-executors/Makefile
  • versions/Makefile
  • schemas/Makefile

When make is invoked in the root directory, it will look for all Makefiles present in the sub-projects, scan their targets and populate them in the root Makefile. As an example, all targets from ansible/build-fb-suse/Makefile will be available in the root Makefile as;

  • ansible/build-fb-suse/run
  • ansible/build-fb-suse/clean

CAUTION
Targets included in Ansible.common.mk or Terraform.common.mk are not included in the root Makefile. This happens because the root Makefile can only identify targets that are present in the sub-projects Makefiles , and not in any referenced files (like Ansible.common.mk or Terraform.common.mk).

How to test make targets locally

The "local" make target allows you to test any make target like you were executing it remotely in a Fargate task. Instead, though, it will execute it in a local Docker container using the same image used by the Fargate task and by mounting this repository (in its current status, locally) as a volume instead of pulling it from GitHub.

The target will read some of the required credentials from Vault. So, you need to log in to Vault before using this make target.

This target accepts a single argument, named "target", which specifies what target needs to be executed inside the container, as well as its arguments. Note that the PRE_RELEASE_NAME environment variable does NOT need to be provided. Instead, the "local" make target will set it up for you to the value local-<YOUR_USERNAME>.

Terraform targets

EC2 SUSE builders

The following command would create the SUSE builder VMs, and the corresponding Terraform state would be stored in the backend S3 bucket under the key "suse-builders-local-<YOUR_USERNAME>.

make local target="terraform/ec2-suse-builders/provision"

To destroy the created resources, you'd need to then run:

make local target="terraform/ec2-suse-builders/clean "

EC2 Test executors

Spin up an ec2 instances for only the packages for which the used fb version does not exist in either staging nor production:

make local target="terraform/ec2-test-executors/prerelease"

Spin up an ec2 instance for each supported package (every yml file in versions/):

make local target="terraform/ec2-test-executors/all"

Note that there is only one target to destroy the resources, since the clean target will destroy all the resources created by either prerelease or all targets.

make local target="ansible/provision-and-execute-tests/clean"

Ansible targets

Each ansible playbook is contained within a project folder with it's own Makefile. This makes it easier to execute, since we just need to provide the path to that project folder and the target we'd like to execute. Once ec2 instances are up, tagged and running, we can run ansible playbooks on them.

Build fluent-bit SLES

 make local target="ansible/build-fb-suse/run"

Provision and execute tests

Prerelease

If we spun up instances to test only prerelease packages, we can then run tests on them. Here we select the prerelease target since this will run the playbook to install NRIA from production bucket AND install fluent-bit from the pre_release.

 make local target="ansible/provision-and-execute-tests/prerelease"

Production and Staging

Now, when packages are available in either production or staging, we can then run tests on NRIA installed from either of this repositories(buckets). This means the NRIA will pull the latest fluent-bit package from the selected bucket. This way we can, after testing the package from the pre_release, publish it to staging and run again the test suite to make sure everything is working as expected.

Production
 make local target="ansible/provision-and-execute-tests/production"
Staging
 make local target="ansible/provision-and-execute-tests/staging"

Upload windows packages to bucket

 make local target="ansible/upload-win-packages"