openstack/magnum
Code Issues Proposed changes

Fix command line in document example

Browse Source 
Example in document for Kubernetes Load Balancer.

In the example, the commands to manually associate a floating IP
to the LB VIP uses grep on "TCP" to find the VIP from the neutron
list.  Recently the etcd pool protocol changes to TCP, so the
grep now returns 2 entries instead of just the entry for the LB.
This in turn gives an error in the next command.

Add another grep to filter out the etcd VIP.

Change-Id: I619fa09fb4a5db7bacbc5d73e38016b8cd6404c6
Closes-Bug:  1505780
This commit is contained in:
Ton Ngo
2015-10-13 21:59:24 +00:00
parent 288a9cd5ba
commit e37276fc15
1 changed files with 7 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
doc/source/dev/dev-kubernetes-load-balancer.rst
View File

@@ -155,9 +155,12 @@ on Horizon by navigating to::
Click on "Allocate IP To Project" and then on "Associate" for the new floating
IP.
Alternatively, associating a floating IP can be done on the command line as
follows. The commands shown below are for illustration purpose and assume
that there is only service with load balancer running in the bay.
Alternatively, associating a floating IP can be done on the command line by
allocating a floating IP, finding the port of the VIP, and associating the
floating IP to the port.
The commands shown below are for illustration purpose and assume
that there is only one service with load balancer running in the bay and
no other load balancers exist except for those created for the cluster.
First create a floating IP on the public network::
@@ -185,7 +188,7 @@ floating IP is shown above, but it can also be queried by::
Next find the VIP for the load balancer::
VIP_ID=$(neutron lb-vip-list | grep TCP | awk '{print $2}')
VIP_ID=$(neutron lb-vip-list | grep TCP | grep -v pool | awk '{print $2}')
Find the port for this VIP::