Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use OpenEBS Director with OpenEBS CI for log collection and troubleshooting #229

Open
kmova opened this issue Mar 30, 2020 · 0 comments
Open
Assignees

Comments

@kmova
Copy link
Contributor

kmova commented Mar 30, 2020

OpenEBS CI runs on GitLab and uses on-premise Kubernetes clusters setup with:

  • Native Kubernetes
  • OpenShift 4.2
  • Konvoy

All the above clusters are running over Vitrual Machines hosted by MayaData.

The logs from the pipelines are currently being pushed to ECK cluster setup using OpenEBS Local PV. The E2e team maintainers manage the ECK cluster and will have to manage access to the logs to developers, as well as perform day 2 operations on ECK cluster - to manage the capacity.

The proposed solution is to make use of "Director On-prem" setup for managing the OpenEBS CI Kubernetes clusters and also grant access to OpenEBS developers to access the logs.

  • The Director on Prem should be accessible to remote workers.
  • The Director on Prem should allow to add new team members to the existing clusters
  • Ability to connect native, openshift and konvoy clusters
  • The OpenEBS CI K8s clusters launch many stateful workloads with different OpenEBS volumes, the Director On-prem should be able to capture the logs from all the openebs pods and Kubernetes nodes.
  • OpenEBS director should be non-intrusive to the running of pipelines.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants