diff options
author | 2017-09-16 03:22:38 +0200 | |
---|---|---|
committer | 2017-10-03 18:41:20 +0200 | |
commit | 8ec927497b7ee0fd3b7346e957878173b080ef6a (patch) | |
tree | 2f2daf184b59ba934e95986e1dddbc27932eb96d /README.rst | |
parent | 0c00f813d709fd1b65e5dd52abcf16fd81b3d0e1 (diff) |
Identify jump host bridges based on IDF / PDF nets
- minor refactor of runtime templates parsing to allow var expansion;
- parse <pod_config.yml> into shell vars, match dynamically networks
from PDF to IP addresses on bridges of current jumphost;
- keep old '-B' parameter in <ci/deploy.sh>, use it for providing
fallback values in case there's no bridge name specified via IDF
and no IP on the jumphost for one or more of the PDF networks;
- re-enable dry-run to ease testing of the above;
- add sample 'idf-pod1.yaml' to <mcp/config/labs/local>;
The new behavior will try to determine the jump host bridge names:
1. Based on IDF mapping, if available
2. Based on PDF network matching with IP addrs on jumphost;
3. Fallback to values passed via '-B';
4. Fallback to default values hardcoded in the deploy script;
Later, we will drop MaaS network env vars in favor of PDF vars,
once the PDF template is generating them.
Change-Id: If9cd65d310c02965b2e2bfa06a0d7e0f97f1dd48
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
Diffstat (limited to 'README.rst')
0 files changed, 0 insertions, 0 deletions