mkdevops-se / mkdevops-se/resultatfiler
En Elasticsearch-setup att testa mot?
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Vi skulle ha en Elasticsearch-setup med Kibana att testa mot. Exempel från ett gammalt projekt:
---
version: '3.3'
services:
elasticsearch_master:
image: docker.elastic.co/elasticsearch/elasticsearch:5.6.3
container_name: elasticsearch_master
environment:
- cluster.name=resultatfiler
- bootstrap.memory_lock=true
- xpack.security.enabled=false
- "ES_JAVA_OPTS=-Xms1g -Xmx1g" # Change to 4g in production.
ulimits:
memlock:
soft: -1
hard: -1
volumes:
- elasticsearch_master:/usr/share/elasticsearch/data
ports:
- 9200:9200
networks:
- elastic
restart: unless-stopped
elasticsearch_slave:
image: docker.elastic.co/elasticsearch/elasticsearch:5.6.3
container_name: elasticsearch_slave
environment:
- cluster.name=resultatfiler
- bootstrap.memory_lock=true
- xpack.security.enabled=false
- "ES_JAVA_OPTS=-Xms1g -Xmx1g" # Change to 4g in production.
- "discovery.zen.ping.unicast.hosts=elasticsearch_master"
ulimits:
memlock:
soft: -1
hard: -1
volumes:
- elasticsearch_slave:/usr/share/elasticsearch/data
networks:
- elastic
restart: unless-stopped
kibana:
image: docker.elastic.co/kibana/kibana:5.6.3
container_name: kibana
environment:
- ELASTICSEARCH_REQUESTTIMEOUT=90000
- ELASTICSEARCH_URL=http://elasticsearch_master:9200
- XPACK_SECURITY_ENABLED=false
- XPACK_GRAPH_ENABLED=false
- XPACK_ML_ENABLED=false
- XPACK_REPORTING_ENABLED=false
ports:
- 5601:5601
networks:
- elastic
restart: unless-stopped
depends_on:
- elasticsearch_master
volumes:
elasticsearch_master:
driver: local
elasticsearch_slave:
driver: local
networks:
elastic:
...
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Docker Compose YAML included in the issue and determine how it should fit the repository's testing workflow. The work is done when a repeatable Elasticsearch setup with Kibana is available for the project's tests, but the issue does not name any repository files or test entry points.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, elasticsearch
- Domain
- devops, infrastructure, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100