Project

General

Profile

Bug #52914

mgr/dashboard: follow-up tasks cephadm/box

Added by Pere Díaz Bou about 2 months ago. Updated about 1 month ago.

Status:
Pending Backport
Priority:
Normal
Category:
Build, CI, Dependencies & Tools
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
pacific
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Description of problem

Work to be done on cephadm's Docker in Docker box
  1. rootless unprivileged docker (cgroups v2?)
  2. Use [letsencrypt SSL certificates](https://letsencrypt.org/) to avoid self-signed certificate issues
  3. Replace var-lib-docker volume with side-car registry caching service.
  4. Expose cephadm.log to stdout for `dc/docker logs` (might be almost impossible due to systemd PID 1)
  5. Create and use separate cluster network
  6. Add vstart-runner-like teuthology integration (for running tests)dd time sync
  7. Modify ceph-volume to accept loopback devices and it can be used to create more osds.
  8. Replace docker with podman and podman-compose https://www.redhat.com/sysadmin/podman-inside-container .
  9. Improve flow of scripts. Add more options to skip parts or something like that.
  10. If you start a cluster more than one time with the same number of osds it should be easier to call `cephadm ceph-volume lvm zap /dev/vg1/lv{i}` than removing the whole loopback device and recreating it again. This will also improve the start time.
  11. Update dependencies of ceph-ci/ceph in order to not have to create a wrapper for the image and trick cephadm. (`./get_ceph_image.sh` creates the wrapper with the same image name but with more deps).
  12. Rewrite scripts to python.

Environment

  • ceph version string:
  • Platform (OS/distro/release):
  • Cluster details (nodes, monitors, OSDs):
  • Did it happen on a stable environment or after a migration/upgrade?:
  • Browser used (e.g.: Version 86.0.4240.198 (Official Build) (64-bit)):

How reproducible

Steps:

  1. ...

Actual results

Please add logs and/or screenshots

Expected results

here

Additional info

here


Related issues

Copied to Dashboard - Backport #53080: pacific: mgr/dashboard: follow-up tasks cephadm/box New

History

#1 Updated by Pere Díaz Bou about 1 month ago

13. Change network to work with subnets or another thing. Test whether current public network conflicts with ceph-dev or kcli.

#2 Updated by Ernesto Puerta about 1 month ago

  • Status changed from New to Pending Backport
  • Backport set to pacific
  • Pull request ID set to 41325

#3 Updated by Backport Bot about 1 month ago

  • Copied to Backport #53080: pacific: mgr/dashboard: follow-up tasks cephadm/box added

Also available in: Atom PDF