diff options
author | Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com> | 2018-06-27 10:32:45 +0000 |
---|---|---|
committer | Gerrit Code Review <gerrit@opnfv.org> | 2018-06-27 10:32:45 +0000 |
commit | 064e5f23d85cc3964a53dba63dbad31228526cd8 (patch) | |
tree | ff64cb9b9dfc09952983ccf6541b3db012042326 | |
parent | 5c211990a4264ed414dd6f107e47341aaeea1b4d (diff) |
Update git submodules
* Update docs/submodules/yardstick from branch 'master'
- Merge "Define several containers per pod in a replication controller"
- 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>
m--------- | docs/submodules/yardstick | 0 |
1 files changed, 0 insertions, 0 deletions
diff --git a/docs/submodules/yardstick b/docs/submodules/yardstick -Subproject c16201daef25b211a9b65e557f83b2d5eb05ffa +Subproject 8d3eedf007d338a032d106842cb66baa3a8eb8b |