Files
pezkuwi-subxt/substrate/.maintain/chaostest/src/config/README.md
T
HarryHong 36e312088e [CI]Chaostest suite initiation (#5793)
* Initiate chaostest cli test suite: singlenodeheight on one dev node
    Added chaostest stages in CI
    Added new docker/k8s resources and environments to CI
    Added new chaos-only tag to gitlab-ci.yml

* Update .maintain/chaostest/src/commands/singlenodeheight/index.js

Co-authored-by: Max Inden <mail@max-inden.de>

* change nameSpace to namespace(one word)

* update chaos ci job to match template

* rename build-pr ci stage to docker [chaos:basic]

* test gitlab-ci [chaos:basic]

* Update .gitlab-ci.yml

* add new build-chaos-only condition

* add *default-vars to singlenodeheight [chaos:basic]

* change build-only to build-rules on substrate jobs [chaos:basic]

* test and change when:on_success to when:always [chaos:basic]

* resolve conflicts and test [chaos:basic]

Co-authored-by: Max Inden <mail@max-inden.de>
Co-authored-by: Denis Pisarev <denis.pisarev@parity.io>
2020-07-23 12:53:55 +02:00

589 B

chaostest CONFIG

Since deployment can behave differently, we want to keep a state between phases including different test subjects.

Content

The state could include informations such as:

{
    namespace,
    image,
    bootnode: {
        podname,
        ip,
        port,
        peerId,
        privateKey,
        publicKey
    },
    nodes: [{
        podname,
        ip,
        port,
        nodeType: 'validator' | 'bootnode' | ,
        privateKey (validator only),
        publicKey (validator only)
    }]
}

TODO

k8s configuration chainspec chaos-agent