BIGTOP-2848: Add provisioner for CentOS 7 AArch64

[nareshgbhat]

Add provisioner yaml config file for centOS 7 AArch64

Signed-off-by: Naresh Bhat [email protected]

[ghost]

Are you intentionally pointing this to repo: "http://bigtop-repos.s3.amazonaws.com/releases/1.2.0/centos/7/x86_64" I was under the impression this is for AArch64, no?

[nareshgbhat]

@c0s it is my mistake, you are right the change should be as below repo: "http://bigtop-repos.s3.amazonaws.com/releases/1.2.0/centos/7/aarch64" Should I make this change and verify, re-post it ?

[ghost]

Well, the change still reads " +repo: "http://bigtop-repos.s3.amazonaws.com/releases/1.2.0/centos/7/x86_64" "

[nareshgbhat]

@c0s now the repo is pointing to aarch64. Sorry for delay, Thanks.

[evans-ye]

Patch looks good except you should set enable_local_repo to false.

[nareshgbhat]

@evans-ye Thanks for pointing. Done.

[evans-ye]

LGTM, thanks for the patch. Will commit shortly.

[docularxu]

When I run [bigtop]/provisioner/docker$ ./docker-hadoop.sh -C config_centos-7-aarch64.yaml --create 5 --smoke-tests --destroy on an aarch64 machine, I always get this failure:

ERROR: for 20180508_023622_r14423_bigtop_3 manifest for bigtop/puppet:trunk-centos-7-aarch64 not found ERROR: for 20180508_023622_r14423_bigtop_2 manifest for bigtop/puppet:trunk-centos-7-aarch64 not found ERROR: for 20180508_023622_r14423_bigtop_1 manifest for bigtop/puppet:trunk-centos-7-aarch64 not found ERROR: for 20180508_023622_r14423_bigtop_5 manifest for bigtop/puppet:trunk-centos-7-aarch64 not found ERROR: for 20180508_023622_r14423_bigtop_4 manifest for bigtop/puppet:trunk-centos-7-aarch64 not found ERROR: manifest for bigtop/puppet:trunk-centos-7-aarch64 not found

Anybody has any idea? Does this mean the URL isn't valid any more? "http://bigtop-repos.s3.amazonaws.com/releases/1.2.0/centos/7/aarch64"

@nareshgbhat

[JunHe77]

The image (bigtop/puppet:trunk-centos-7-aarch64) is not provided on dockhub. You need to build it locally. For all valid images at present, pls check here: https://hub.docker.com/r/bigtop/puppet/tags To build a bigtop-* docker image, pls check by issuing: ./gradlew tasks

[docularxu]

I see. Just found the same by having a closer look of docker-compose.yml. And clearly, if run with -c config_debian-8-aarch64.yaml, it has this problem too.

But should a user be warned if an image doesn't exist and requires local build?

Another solution possibly, should we change the images to something existing in hub.docker.com, for example, trunk-debian-9-aarch64 exists in docker registery, we can create a yaml named "config_debian-9-aarch64.yaml". Do you think this is a good solution?

[nareshgbhat]

My apologies for late reply. I was on vacation. The patch is conflicting. We usually follow the official docker image registry. Jun is right there is no "The image (bigtop/puppet:trunk-centos-7-aarch64) is not provided on dockhub. You need to build it locally."

For Debian 9 changes you need to create a new jira issue and re-post the patch. This jira issue is used to follow up and post the changes for CentOS 7.

Yes, if the trunk debian 9 aarch64 image exists it makes sense to change it.