elastic / elastic/elastic-package

Need docker image for Ceph integration system test

Open
#1,126 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
72
Forks
141
Avg merge
19h 42m
Merged PRs (30d)
55

Description

Currently, we are trying to perform a system test with ceph/daemon image.

For the octopus version, we are facing this issue while performing Ceph operations in the docker image,
![image](https://user-images.githubusercontent.com/118714680/215976714-18078fb9-d0ce-486a-87aa-c85f2279879c.png)

We have referred to the [Ceph metricbeat module](https://github.com/elastic/beats/blob/master/metricbeat/module/ceph/docker-compose.yml) and how they are doing system tests. So we have used ceph/daemon:master-97985eb-nautilus-centos-7-x86_64 same image. we have performed similar steps with our system test. But we are facing an issue related to `API Secret Key`.

We must pass the API User and API Secret Key while configuring the Ceph integration. (We already mentioned how to get these details in our [README.md](https://github.com/elastic/integrations/pull/4930/files#diff-0103bb9ee6141c6f91f8fe0fc69fc8debc0469b3f4ad88534b457df7078da6ec))
For the API User, the environment is set as a static value for API User (i.e. demo).
But for the API Secret Key, the system has a dynamic value. (Generated by Ceph environment)
So we need to set the API Secret Key to the environment variable and pass it while doing the system test.
But somehow we are not able to do this while doing the system test.

We need a docker image for Ceph with API User and API Secret Key set in the environment variable while performing the system tests.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing README.md and the Ceph metricbeat docker-compose.yml referenced in the issue, then trace how the Ceph system test consumes the image and credentials. The work is done when a usable Ceph Docker image provides the API user and dynamically generated secret key through environment variables for the system test.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
devops, testing-qa
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.