Google Git
Sign in
apache / ambari / aaffed79bdfe2adc7f5e46fd428c20c5ac9d6971 / . / ambari-logsearch
tree: 4032caa1787600d3f53a3edd7f6d9f693d602848 [path history] [tgz]
  1. ambari-logsearch-appender/
  2. ambari-logsearch-assembly/
  3. ambari-logsearch-config-api/
  4. ambari-logsearch-config-zookeeper/
  5. ambari-logsearch-it/
  6. ambari-logsearch-logfeeder/
  7. ambari-logsearch-logfeeder-plugin-api/
  8. ambari-logsearch-server/
  9. ambari-logsearch-web/
  10. docker/
  11. .gitignore
  12. pom.xml
  13. README.md
ambari-logsearch/README.md

Log Search

Setup local environment with docker

Prerequisites

Build and start Log Search in docker container

# to see available commands: run start-logsearch without arguments
cd docker
./logsearch-docker build-and-run # build mvn project locally, build docker image, start containers

If you run the script at first time, it will generate you a new Profile file or an .env file inside docker directory (run twice if both missing and you want to generate Profile and .env as well), in .env file you should set MAVEN_REPOSITORY_LOCATION (point to local maven repository location, it uses ~/.m2 by default). These will be used as volumes for the docker container. Profile file holds the environment variables that are used inside the containers, the .env file is used outside of the containers

Then you can use the logsearch-docker script to start the containers (start command). Also you can use docker-compose manually to start/manage the containers.

docker-compose up -d
# or start all services in one container:
docker-compose -f all.yml up -d

After the logsearch container is started you can enter to it with following commands:

docker exec -it docker_logsearch_1 bash
# or if you used all.yml for starting the logsearch docker container:
docker exec -it logsearch bash

In case if you started the containers separately and if you would like to access Solr locally with through your external ZooKeeper container, then point solr to localhost in your /etc/hosts file.

Run applications from IDE / maven

Package build process

  1. Check out the code from GIT repository

  2. On the logsearch root folder (ambari/ambari-logsearch), please execute the following Maven command to build RPM/DPKG:

mvn -Dbuild-rpm clean package

or

mvn -Dbuild-deb clean package
  1. Generated RPM/DPKG files will be found in ambari-logsearch-assembly/target folder

Running Integration Tests

By default integration tests are not a part of the build process, you need to set -Dbackend-tests or -Dselenium-tests (or you can use -Dall-tests to run both). To running the tests you will need docker here as well (right now docker-for-mac and unix are supported by default, for boot2docker you need to pass -Ddocker.host parameter to the build).

# from ambari-logsearch folder
mvn clean integration-test -Dbackend-tests failsafe:verify
# or run selenium tests with docker for mac, but before that you nedd to start xquartz
xquartz
# then in an another window you can start ui tests
mvn clean integration-test -Dselenium-tests failsafe:verify
# you can specify story file folde location with -Dbackend.stories.location and -Dui.stories.location (absolute file path) in the commands

Also you can run from the IDE, but make sure all of the ambari logsearch modules are built.