b3c6dad3e0
This patch adds documentation for using a proxy when running magnum behind a firewall. Currently this feature only works with Swarm bays. Co-Authored By: Adrian Otto <adrian.otto@rackspace.com> Change-Id: If3f53978b11b6558b304a5c369b85fd9aa1e4a52 Partially-Implements: blueprint add-proxy
1.8 KiB
Using Proxies in magnum if running under firewall
If you are running magnum behind a firewall then you may need a proxy for using services like docker, kubernetes and mesos. Use these steps when your firewall will not allow you to use those services without a proxy.
NOTE: This feature only works with Swarm bays.
Proxy Parameters to define before use
- http-proxy
Address of a proxy that will receive all HTTP requests and relay them. The format is a URL including a port number. For example: http://10.11.12.13:8000 or http://abcproxy.com:8000
- https-proxy
Address of a proxy that will receive all HTTPS requests and relay them. The format is a URL including a port number. For example: https://10.11.12.13:8000 or https://abcproxy.com:8000
- no-proxy
A comma separated list of IP addresses or hostnames that should bypass your proxy, and make conenctions directly.
NOTE: You may not express networks/subnets. It only accepts names and ip addresses. Bad example: 192.168.0.0/28.
Steps to to configure proxies.
You can specify all three proxy parameteres while creating baymodel of any coe type. All of proxy parameters are optional.
magnum baymodel-create --name swarmbaymodel --image-id fedora-21-atomic-5 --keypair-id testkey --external-network-id public --dns-nameserver 8.8.8.8 --flavor-id m1.small --coe swarm --http-proxy <http://abc-proxy.com:8080> --https-proxy <https://abc-proxy.com:8080> --no-proxy <172.24.4.4,172.24.4.9,172.24.4.8>