summaryrefslogtreecommitdiffstats
path: root/dashboard/Prox_BM_vpe-4Port-1529345833067.json
diff options
context:
space:
mode:
authorRodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>2018-05-05 11:13:28 +0100
committerRodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>2018-06-14 07:15:23 +0000
commit34292694f596561de9c78f0feb663ffa5de0dc2d (patch)
tree2460af044a7f541cc7e103ee542f59379a2d6c25 /dashboard/Prox_BM_vpe-4Port-1529345833067.json
parent01edaefa20775921200a6a1b17fbfd67f7aca77e (diff)
Define several containers per pod in a replication controller
Add the ability to define not only one but many containers per pod in a replication controller descriptor. This feature must be backwards compatible; all current test cases using the "single container" server definition must be accepted. Example of single container pod definition: context: type: Kubernetes servers: host: image: ... commands: ... volumes: - name: volume1 # mandatory <volume type definition> # mandatory Example of several container pod definition: context: type: Kubernetes servers: host: containers: # if this key is present, all container specific parameters (image, commands, args, volumeMounts, etc.) must be defined per container - image: ... commands: ... - image: ... commands: ... volumes: - name: volume1 # mandatory <volume type definition> # mandatory NOTE: other parameters, like "volumes" or "nodeSelector", are common to all containers in the pod. JIRA: YARDSTICK-1155 Change-Id: Ib95668c68e9c09e6de3f1aa41c903cc52e6809ad Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
Diffstat (limited to 'dashboard/Prox_BM_vpe-4Port-1529345833067.json')
0 files changed, 0 insertions, 0 deletions