Add Linux/ARM64 support to Stratos

[odidev]

Hi Team,

I am trying to add ARM64 jobs in travis for stratos but it seems it has several issues and does not contain ARM64 support. Please go through below issues in travis for arm64:

1. Stage ‘LINT’: For ARM64, I installed ‘xvfb’ and ‘golint’ via .travis.yml, and installed go v1.15.x for ARM64 platform. This stage is passing now for ARM64.
2. Stage ‘BUILD’: Build was failing to install ‘mc’ for ARM64. ‘mc’ is available for ARM64 platform, so after applying architecture check for arm64 here https://github.com/cloudfoundry/stratos/blob/master/deploy/ci/travis/e2e-mc-helper.sh#L10, build has moved further, and is now failing for the swaggo/swag binary. I had raised a PR in swaggo/swag to release binary for AArch64, which is merged and swag is available for AArch64 in version 1.7.0. I tried updating the version in /build/bk-build.sh, but encountered a checksum mismatch error. This is because the checksum for swag version v1.7.0 is missing in go.sum file.
3. STAGE ‘TEST’:

• Test index 1 is failing to install chrome browser binary for arm64. I installed it via apt-get and deb package, but the issue is not resolved.
• Test index 2 is again failing for the swaggo/swag binary.
• Test index 3 is failing for helm-unittest binary, which is not available for arm64. I have raised a PR for the same, which is not yet merged.
• Test index 4-10 are all failing to execute this command here https://github.com/cloudfoundry/stratos/blob/master/deploy/ci/travis/run-e2e-tests.sh#L16, and shows below error :

  HTTP request sent, awaiting response... 401 Unauthorized

Do you have any plans in adding arm64 support?

If interested in the same, then I am happy to contribute. If you can provide me with pointers on above issues, I can progress further and raise a PR for the same.

[richard-cox]

I cannot talk through the arm issues, but in terms of running the e2e tests independently from our travis workloads, you should check out the guide here. That's mainly for running them locally, however the 401 unauthorised you're seeing is due to the test attempting to fetch our ci secrets.yaml file. You'll need to run the tests with your own secrets.yaml which contains details of the CF instance the tests will run against. The link should give you enough info to set those up.