-
Notifications
You must be signed in to change notification settings - Fork 294
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
DNM: Initial work on docker task for teuthology #558
Conversation
Can one of the admins OK this pull request so I can run a build? |
ok to test |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
Task that allows to execute orchestrate docker containers from teuthology. Supported maestro-ng commands are 'start', 'stop' and 'pull'. Tests for this task are also present. A new dependency is added to setup.py (maestro-ng). Besides the 'command' option, the docker task has two options that specify what services are being operated on: 'services' and 'roles'. The first one is used to specify services in maestro-ng's format. The latter signals the creation of services for the entries in teuthology's 'roles' configuration.
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
This PR went stale, so I'll close it. Reopen if it's still relevant? |
Introduces a 'docker' task that leverages maestro-ng to deploy a docker-based ceph cluster. In a nutshell, it maps the teuthology configuration (roles and targets) to a maestro-ng configuration and passes that to maestro-ng to execute commands.
Supported maestro-ng commands are start, stop and pull. It also adds tests for this task. A new dependency is added to setup.py (maestro-ng).
Follow-up items:
execute
command. This allows other tasks (e.g. radosbench) that rely on Remote's SSH connection to be able to execute inside a container.test_begin
doesn't execute.