guyuqi commented on pull request #657:
URL: https://github.com/apache/bigtop/pull/657#issuecomment-679872117


   >It seems that the Source3: kibana.default line in kibana.spec should be 
removed.
   
   Yes, I'll remove it and rebase this pr for conflicting file: 
`bigtop_toolchain/manifests/packages.pp`, thanks, @sekikn
   
   
   >I also tried to run the smoke test on Debian and Ubuntu, but on those 
distros, start-kibana in TestKibanaSmoke.groovy didn't seem to return and the 
test didn't finish. Is it the same for you, or it normally finishes on your 
environment?
   
   I re-verified this PR on Ubuntu16.04 and debian-9 and also succesfully run 
the smoke tests.
   Before running the kibana smoke tests, `elasticsearch `is required to be 
installed in advance.
   
   Could you please rebuild elasticsearch and kibana again:
   1.  `docker run --rm  -v `pwd`:/ws --workdir /ws 
bigtop/slaves:trunk-ubuntu-16.04 bash -c '. /etc/profile.d/bigtop.sh; ./gradlew 
allclean elasticsearch-pkg kibana-pkg apt'`
   
   
   2. Deploy elasticsearch and kibana in advance:
   
   BIGTOP_HOME/provisioner/docker/config_ubuntu-16.04.yaml: 
   ```
   docker:
           memory_limit: "4g"
           image:  "bigtop/puppet:trunk-ubuntu-16.04"
   
   repo: "http://repos.bigtop.apache.org/releases/1.4.0/ubuntu/16.04/$(ARCH)"
   distro: debian
   components: [elasticsearch, kibana]
   enable_local_repo: true
   smoke_test_components: [kibana]
   
   ```
   config_debian-9.yaml
   ```
   docker:
           memory_limit: "4g"
           image: "bigtop/puppet:trunk-debian-9"
   
   repo: "http://repos.bigtop.apache.org/releases/1.4.0/debian/9/$(ARCH)"
   distro: debian
   components: [elasticsearch, kibana]
   enable_local_repo: true
   smoke_test_components: [kibana]
   ```
   
   3. Run smoke tests:
   Unbuntu 16.04:
   `./docker-hadoop.sh -C config_ubuntu-16.04 -c 1 -s`
   Debian 9:
   `./docker-hadoop.sh -C config_debian-9.yaml -c 1 -s
   `
   
   
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to