Track scalability of Magnum
Magnum builds the infrastructure (bay) using OpenStack services to deliver container as a service. This blueprint provides a set of contexts and scenarios to test the scalability of Magnum as well as the bay hosting the containers. The scenarios will cover all bay types: Kubernetes, Swarm, Mesos.
Blueprint information
- Status:
- Not started
- Approver:
- Boris Pavlovic
- Priority:
- Undefined
- Drafter:
- Ton Ngo
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
strigazi on Fri Jun 16 08:11:04 UTC 2017:
We need to move from python-k8sclient to python-kubernetes
Scenarios to consider for each bay type: Kubernetes, Swarm, Mesos
-Create, delete baymodel (Winnie)
-Create, update, delete baymodel
-Create, delete bay
-Create, scale up n node, delete bay
-Create, scale down n node, delete bay
-Create, show cert for bay
-Create container/pod in bay, delete container/pod (Winnie)
Gerrit topic: https:/
Addressed by: https:/
[Magnum] Add Magnum client to Rally
Addressed by: https:/
[Magnum] Base context for Magnum baymodel
Addressed by: https:/
[Magnum] Scenario to list Magnum baymodels
Addressed by: https:/
[Magnum] Scenario to create a Magnum bay
Addressed by: https:/
[magnum] Change magnum service type
Addressed by: https:/
[Magnum] Context and scenario for Kubernetes
Addressed by: https:/
[magnum] Add rally job for magnum
Addressed by: https:/
Fix rally gate job for magnum
Addressed by: https:/
[Magnum] Context and scenario for Swarm
Addressed by: https:/
[Magnum] Scenario for Mesos
Addressed by: https:/
[magnum] Fix client
Gerrit topic: https:/
Addressed by: https:/
[magnum] Move list baymodels in a scenario class
Addressed by: https:/
[WIP] Remove list_bays scenario from jobs
Gerrit topic: https:/
Addressed by: https:/
[magnum] Rename to cluster and cluster_template
