51d0cb7e04
With the introduction of Multus CNI, the portmap chained plugin was no longer configured. This commit simply adds the portmap plugin to the Multus configuration template. The portmap plugin allows a user to create a pod/deployment with a host->container port mapping by including the hostPort, containerPort in the container specification. ie: spec: containers: ports: - containerPort: 80 hostPort: 8089 In this example, one could access the service in the pod via container_ip:80 or node_ip:8089 Closes-Bug: 1832892 Change-Id: I0549bff242df881e652b742abdf4fb342b5d7a5e Signed-off-by: Steven Webster <steven.webster@windriver.com> |
||
---|---|---|
examples/remote | ||
playbookconfig | ||
.gitignore | ||
.gitreview | ||
.yamllint | ||
.zuul.yaml | ||
CONTRIBUTORS.wrs | ||
LICENSE | ||
README.rst | ||
centos_iso_image.inc | ||
centos_pkg_dirs | ||
test-requirements.txt | ||
tox.ini |
README.rst
stx-ansible-playbooks
StarlingX Bootstrap and Deployment Playbooks
Execution environment
- Unix like OS (recent Linux based distributions, MacOS, Cygwin)
- Python 2.7
Additional Required Packages
The playbooks in this repo have been verified with the following versions of Ansible and StarlingX playbooks dependencies:
- sshpass 1.06
- python2-ptyprocess 0.5
- python2-pexpect 4.6
- python2-netaddr 0.7
ansible
2.7.5
Supported StarlingX Releases
The playbooks in this repo are compatible with the following StarlingX releases:
- 19.09
Executing StarlingX Playbooks
Executing Bootstrap Playbook
Please refer to StarlingX Deployment Guides
, section
Configuration controller-0 of the respective system
configuration for instructions on how to set up and execute the
bootstrap playbook from another host.