From e29d3f6b14853497607a083fdd905edc56328bc3 Mon Sep 17 00:00:00 2001 From: jeewan rana Date: Tue, 22 Aug 2017 12:37:59 -0700 Subject: [PATCH 1/2] update service loadbalancer feature document --- .../source/documents/networking/services.md | 85 ++++++++++++++++++- 1 file changed, 82 insertions(+), 3 deletions(-) diff --git a/websrc/source/documents/networking/services.md b/websrc/source/documents/networking/services.md index 3882371..d1683f8 100644 --- a/websrc/source/documents/networking/services.md +++ b/websrc/source/documents/networking/services.md @@ -17,16 +17,95 @@ Services offer: - Minimal downtime. A provider is one or more containers that match the label selector associated with the services. + **Note**: This feature would be deprecated since docker 1.12 onword service load balancer feature is supported natively by docker swarm. ## Defining Services After you create your network, you can define services using the UI, the `netctl` command line interface (CLI), or the Contiv Network REST APIs, but it is recommended to use the UI or API to take advantage of the authentication and authorization options in those interfaces. -Note: Service requirements are defined by *selectors*. Selectors are key-value pairs +**Note**: Service requirements are defined by *selectors*. Selectors are key-value pairs that group providers with matching labels. -To create a Service Load Balancer using the UI: +###To create a Service Load Balancer using netctl: + +1\. Create newtwork as net0-2 in tenant default + + netctl network create net0-2 -s 10.0.0.0/24 -g 10.0.0.254 -encap vxlan -t default +2\. Create service network as svc-net-2-0 in tenant default + + netctl network create svc-net-2-0 -s 30.2.0.0/24 -g 30.2.0.254 -encap vxlan -t default + +3\. Create service on service network as svc-0-default in tenant default + + netctl service create svc-0-default --network svc-net-2-0 -t default --selector=key0=value1 --selector=key1=value2 --selector=key2=value3 --selector=key3=value4 --port=80:8080:TCP --port=643:7070:UDP + + +After above operation, check service IPs , using _netctl service inspect _. In this example, service Ips is 30.2.0.1 + +```` + [vagrant@netplugin-node1 ~]$ netctl service ls + ServiceName Tenant Network Selectors + --------- -------- ------- ------- + svc-0-default default svc-net-1-0 [key0=value1 key1=value2 key2=value3 key3=value4] + + [vagrant@netplugin-node1 ~]$ netctl service inspect svc-0-default + ---- + ---- + "labels": "map[key0:value1 key1:value2 key2:value3 key3:value4]", + "macAddress": "02:02:0a:00:00:08", + "network": "net0-1.default", + "serviceName": "svc-0-default" + } + ], + "serviceVip": "30.1.0.1" + } +```` + +4\. Create four service containers in network net0-2 + + docker run -itd --name=net0-2-srv0-0-0 --net=net0-2 contiv/alpine sleep 600m + docker run -itd --name=net0-2-srv1-1-1 --net=net0-2 contiv/alpine sleep 600m + docker run -itd --name=net0-2-srv2-2-2 --net=net0-2 contiv/alpine sleep 600m + docker run -itd --name=net0-2-srv3-0-3 --net=net0-2 contiv/alpine sleep 600m + +5\. Similarly create provider containers as service backend containers + + docker run -itd --name=srv-default-net0-2-20-3 --net=net0-2 --label=key0=value1 --label=key1=value2 --label=key2=value3 --label=key3=value4 contiv/alpine sleep 600m + docker run -itd --name=srv-default-net0-2-21-1 --net=net0-2 --label=key0=value1 --label=key1=value2 --label=key2=value3 --label=key3=value4 contiv/alpine sleep 600m + docker run -itd --name=srv-default-net0-2-22-2 --net=net0-2 --label=key0=value1 --label=key1=value2 --label=key2=value3 --label=key3=value4 contiv/alpine sleep 600m + docker run -itd --name=srv-default-net0-2-23-0 --net=net0-2 --label=key0=value1 --label=key1=value2 --label=key2=value3 --label=key3=value4 contiv/alpine sleep 600m + +6\. Run Service instances on provider containers(TCP server at ports 8080 and 7070) i.e Use netcat utility to run server + + docker exec -it srv-default-net0-2-20-3 nc -lk -p 7070 -e /bin/true & + docker exec -it srv-default-net0-2-21-1 nc -lk -p 7070 -e /bin/true & + docker exec -it srv-default-net0-2-22-2 nc -lk -p 7070 -e /bin/true & + docker exec -it srv-default-net0-2-23-0 nc -lk -p 7070 -e /bin/true & + docker exec -it srv-default-net0-2-20-3 nc -lk -p 8080 -e /bin/true & + docker exec -it srv-default-net0-2-21-1 nc -lk -p 8080 -e /bin/true & + docker exec -it srv-default-net0-2-22-2 nc -lk -p 8080 -e /bin/true & + docker exec -it srv-default-net0-2-23-0 nc -lk -p 8080 -e /bin/true & + +7\. login into service conatiner and connect to service i.e Use netcat utility to run client to connect server + + docker exec -it net0-2-srv1-1-1 nc -z -n -v -w 1 30.2.0.1 80 + docker exec -it net0-2-srv3-0-3 nc -z -n -v -w 1 30.2.0.1 80 + docker exec -it net0-2-srv2-2-2 nc -z -n -v -w 1 30.2.0.1 80 + docker exec -it net0-2-srv0-0-0 nc -z -n -v -w 1 30.2.0.1 80 + +8.\ As above operation result, client utiltiy must be connected to the service + + + + + + + + + + +###To create a Service Load Balancer using the UI: 1\. From *Service Load Balancer*, click *Create Service Load Balanacer*. ![service](CreateServiceLoadBalancer.png)
@@ -93,4 +172,4 @@ docker exec -it 9e6842a59369ba67d6224c1502ab0e68360fe7aaa0949a04462a9ae0bdbc6830 ``` *Note*: The service IP can also be a preferred IP address. This can be enforced while creating the service configuration with the `-ip` option. ---> \ No newline at end of file +--> From 2676efd6591487a2aa3c2bd96c4f25e4ca9c99e1 Mon Sep 17 00:00:00 2001 From: Jeewan Rana Date: Fri, 25 Aug 2017 14:35:24 -0700 Subject: [PATCH 2/2] incorporate review comments --- documents/networking/services.html | 65 +++++++++++- sitemap.xml | 100 +++++++++--------- .../source/documents/networking/services.md | 80 +++++++++++++- 3 files changed, 189 insertions(+), 56 deletions(-) diff --git a/documents/networking/services.html b/documents/networking/services.html index 5fb73d8..8358f1e 100644 --- a/documents/networking/services.html +++ b/documents/networking/services.html @@ -240,14 +240,73 @@

Service Load Balancing

  • Minimal downtime.
    • -

    A provider is one or more containers that match the label selector associated with the services.

    +

    A provider is one or more containers that match the label selector associated with the services. + Note: This feature would be deprecated since docker 1.12 onward service load balancer feature is supported natively by docker swarm.

    Defining Services

    After you create your network, you can define services using the UI, the netctl command line interface (CLI), or the Contiv Network REST APIs, but it is recommended to use the UI or API to take advantage of the authentication and authorization options in those interfaces.

    -

    Note: Service requirements are defined by selectors. Selectors are key-value pairs +

    Note: Service requirements are defined by selectors. Selectors are key-value pairs that group providers with matching labels.

    -

    To create a Service Load Balancer using the UI:

    + +

    To create a Service Load Balancer using netctl:

    +

    1. Create network as net0-2 in default tenant

    +
    netctl network create net0-2 -s 10.0.0.0/24 -g 10.0.0.254 -encap vxlan -t default
+
    +

    2. Create service network as svc-net-2-0 in default tenant

    +
    netctl network create svc-net-2-0 -s 30.2.0.0/24 -g 30.2.0.254 -encap vxlan -t default
+
    +

    3. Create service on service network as svc-0-default in default tenant

    +
    netctl service create svc-0-default --network svc-net-2-0 -t default --selector=key0=value1 --selector=key1=value2 --selector=key2=value3 --selector=key3=value4 --port=80:8080:TCP --port=643:7070:UDP
+
    +

    4. Verify service name and its IPs.

    +
    [vagrant@netplugin-node1 ~]$ netctl service ls
+ServiceName    Tenant    Network      Selectors
+---------      --------  -------      -------
+svc-0-default  default   svc-net-1-0  [key0=value1 key1=value2 key2=value3 key3=value4]
+
+[vagrant@netplugin-node1 ~]$ netctl service inspect svc-0-default
+----
+----
+       "labels": "map[key0:value1 key1:value2 key2:value3 key3:value4]",
+       "macAddress": "02:02:0a:00:00:08",
+       "network": "net0-1.default",
+       "serviceName": "svc-0-default"
+      }
+    ],
+    "serviceVip": "30.1.0.1" 
+  }
+
    +

    4. Create four service containers in network net0-2

    +
    docker run -itd --name=net0-2-srv0-0-0 --net=net0-2  contiv/alpine  sleep 600m
+docker run -itd --name=net0-2-srv1-1-1 --net=net0-2  contiv/alpine  sleep 600m
+docker run -itd --name=net0-2-srv2-2-2 --net=net0-2  contiv/alpine  sleep 600m
+docker run -itd --name=net0-2-srv3-0-3 --net=net0-2  contiv/alpine  sleep 600m
+
    +

    5. Similarly create provider containers as service backend containers

    +
    docker run -itd --name=srv-default-net0-2-20-3 --net=net0-2  --label=key0=value1 --label=key1=value2 --label=key2=value3 --label=key3=value4  contiv/alpine sleep 600m
+docker run -itd --name=srv-default-net0-2-21-1 --net=net0-2  --label=key0=value1 --label=key1=value2 --label=key2=value3 --label=key3=value4  contiv/alpine sleep 600m
+docker run -itd --name=srv-default-net0-2-22-2 --net=net0-2  --label=key0=value1 --label=key1=value2 --label=key2=value3 --label=key3=value4  contiv/alpine sleep 600m
+docker run -itd --name=srv-default-net0-2-23-0 --net=net0-2  --label=key0=value1 --label=key1=value2 --label=key2=value3 --label=key3=value4  contiv/alpine sleep 600m
+
    +

    6. Run Service instances on provider containers(TCP server at ports 8080 and 7070) i.e Use netcat utility to run server

    +
    docker exec -it srv-default-net0-2-20-3  nc -lk -p 7070 -e /bin/true &
+docker exec -it srv-default-net0-2-21-1  nc -lk -p 7070 -e /bin/true &
+docker exec -it srv-default-net0-2-22-2  nc -lk -p 7070 -e /bin/true &
+docker exec -it srv-default-net0-2-23-0  nc -lk -p 7070 -e /bin/true &
+docker exec -it srv-default-net0-2-20-3  nc -lk -p 8080 -e /bin/true &
+docker exec -it srv-default-net0-2-21-1  nc -lk -p 8080 -e /bin/true &
+docker exec -it srv-default-net0-2-22-2  nc -lk -p 8080 -e /bin/true &
+docker exec -it srv-default-net0-2-23-0  nc -lk -p 8080 -e /bin/true & 
+
    +

    7. login into service conatiners and connect to service i.e Use netcat utility to run client to connect service

    +
    docker exec -it net0-2-srv1-1-1  nc -z -n -v -w 1  30.2.0.1 80
+docker exec -it net0-2-srv3-0-3  nc -z -n -v -w 1  30.2.0.1 80
+docker exec -it net0-2-srv2-2-2  nc -z -n -v -w 1  30.2.0.1 80
+docker exec -it net0-2-srv0-0-0  nc -z -n -v -w 1  30.2.0.1 80
+
    + +

    To create a Service Load Balancer using the UI:

    1. From Service Load Balancer, click Create Service Load Balanacer. service
    The Create Service Load Balancer page displays.
    diff --git a/sitemap.xml b/sitemap.xml index 209e67f..078ffec 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -2,301 +2,301 @@ http://contiv.io/articles/2016/03/06/scaling-microservices.html - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/articles/2016/05/17/onug-contiv-award.html - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/articles/2016/07/13/dockercon-talk.html - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/articles/ - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/admin/createNodes.html - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/admin/createTenant.html - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/admin/ - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/admin/manageAuthorizations.html - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/admin/manageLDAP.html - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/admin/manageNetworks.html - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/admin/manageUsers.html - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/api/contiv.html - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/api/wip.html - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/community/ - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/demos/ - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/gettingStarted/ - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/ - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/networking/aci_setup.html - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/networking/aci_ug.html - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/networking/bgp.html - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/networking/concepts.html - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/networking/features.html - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/networking/ - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/networking/ipam.html - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/networking/ipv6.html - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/networking/l2-vlan.html - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/networking/physical-networks.html - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/networking/policies.html - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/networking/portinfo.html - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/networking/services.html - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/openshift/ - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/reference/netctlcli.html - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/releasenotes/beta.html - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/releasenotes/v10x.html - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/releasenotes/v11x.html - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/samples/ - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/samples/mcast.html - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/support/supportmatrix/ - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/support/supportmatrix/v10x.html - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/support/supportmatrix/v11x.html - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/talks/ - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/tutorials/container-101.html - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/tutorials/contiv-compose.html - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/tutorials/contiv-policy-kubernetes-16.html - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/tutorials/contiv-policy.html - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/tutorials/ - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/tutorials/networking-kubernetes-16.html - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/tutorials/prometheus-tutorial.html - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/ - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 http://contiv.io/documents/support/ - 2017-08-16T00:00:00+00:00 + 2017-08-23T00:00:00+00:00 monthly 0.5 diff --git a/websrc/source/documents/networking/services.md b/websrc/source/documents/networking/services.md index 3882371..c927ebc 100644 --- a/websrc/source/documents/networking/services.md +++ b/websrc/source/documents/networking/services.md @@ -17,16 +17,90 @@ Services offer: - Minimal downtime. A provider is one or more containers that match the label selector associated with the services. + **Note**: This feature would be deprecated since docker 1.12 onward service load balancer feature is supported natively by docker swarm. ## Defining Services After you create your network, you can define services using the UI, the `netctl` command line interface (CLI), or the Contiv Network REST APIs, but it is recommended to use the UI or API to take advantage of the authentication and authorization options in those interfaces. -Note: Service requirements are defined by *selectors*. Selectors are key-value pairs +**Note**: Service requirements are defined by *selectors*. Selectors are key-value pairs that group providers with matching labels. -To create a Service Load Balancer using the UI: +### To create a Service Load Balancer using netctl: + +1\. Create network as net0-2 in default tenant + + netctl network create net0-2 -s 10.0.0.0/24 -g 10.0.0.254 -encap vxlan -t default + +2\. Create service network as svc-net-2-0 in default tenant + + netctl network create svc-net-2-0 -s 30.2.0.0/24 -g 30.2.0.254 -encap vxlan -t default + +3\. Create service on service network as svc-0-default in default tenant + + netctl service create svc-0-default --network svc-net-2-0 -t default --selector=key0=value1 --selector=key1=value2 --selector=key2=value3 --selector=key3=value4 --port=80:8080:TCP --port=643:7070:UDP + + +4\. Verify service name and its IPs. + +``` +[vagrant@netplugin-node1 ~]$ netctl service ls +ServiceName Tenant Network Selectors +--------- -------- ------- ------- +svc-0-default default svc-net-1-0 [key0=value1 key1=value2 key2=value3 key3=value4] + +[vagrant@netplugin-node1 ~]$ netctl service inspect svc-0-default +---- +---- + "labels": "map[key0:value1 key1:value2 key2:value3 key3:value4]", + "macAddress": "02:02:0a:00:00:08", + "network": "net0-1.default", + "serviceName": "svc-0-default" + } + ], + "serviceVip": "30.1.0.1" + } +``` + +4\. Create four service containers in network net0-2 + + docker run -itd --name=net0-2-srv0-0-0 --net=net0-2 contiv/alpine sleep 600m + docker run -itd --name=net0-2-srv1-1-1 --net=net0-2 contiv/alpine sleep 600m + docker run -itd --name=net0-2-srv2-2-2 --net=net0-2 contiv/alpine sleep 600m + docker run -itd --name=net0-2-srv3-0-3 --net=net0-2 contiv/alpine sleep 600m + +5\. Similarly create provider containers as service backend containers + + docker run -itd --name=srv-default-net0-2-20-3 --net=net0-2 --label=key0=value1 --label=key1=value2 --label=key2=value3 --label=key3=value4 contiv/alpine sleep 600m + docker run -itd --name=srv-default-net0-2-21-1 --net=net0-2 --label=key0=value1 --label=key1=value2 --label=key2=value3 --label=key3=value4 contiv/alpine sleep 600m + docker run -itd --name=srv-default-net0-2-22-2 --net=net0-2 --label=key0=value1 --label=key1=value2 --label=key2=value3 --label=key3=value4 contiv/alpine sleep 600m + docker run -itd --name=srv-default-net0-2-23-0 --net=net0-2 --label=key0=value1 --label=key1=value2 --label=key2=value3 --label=key3=value4 contiv/alpine sleep 600m + +6\. Run Service instances on provider containers(TCP server at ports 8080 and 7070) i.e Use netcat utility to run server + + docker exec -it srv-default-net0-2-20-3 nc -lk -p 7070 -e /bin/true & + docker exec -it srv-default-net0-2-21-1 nc -lk -p 7070 -e /bin/true & + docker exec -it srv-default-net0-2-22-2 nc -lk -p 7070 -e /bin/true & + docker exec -it srv-default-net0-2-23-0 nc -lk -p 7070 -e /bin/true & + docker exec -it srv-default-net0-2-20-3 nc -lk -p 8080 -e /bin/true & + docker exec -it srv-default-net0-2-21-1 nc -lk -p 8080 -e /bin/true & + docker exec -it srv-default-net0-2-22-2 nc -lk -p 8080 -e /bin/true & + docker exec -it srv-default-net0-2-23-0 nc -lk -p 8080 -e /bin/true & + +7\. login into service conatiners and connect to service i.e Use netcat utility to run client to connect service + + docker exec -it net0-2-srv1-1-1 nc -z -n -v -w 1 30.2.0.1 80 + docker exec -it net0-2-srv3-0-3 nc -z -n -v -w 1 30.2.0.1 80 + docker exec -it net0-2-srv2-2-2 nc -z -n -v -w 1 30.2.0.1 80 + docker exec -it net0-2-srv0-0-0 nc -z -n -v -w 1 30.2.0.1 80 + + + + + + +### To create a Service Load Balancer using the UI: 1\. From *Service Load Balancer*, click *Create Service Load Balanacer*. ![service](CreateServiceLoadBalancer.png)
    @@ -93,4 +167,4 @@ docker exec -it 9e6842a59369ba67d6224c1502ab0e68360fe7aaa0949a04462a9ae0bdbc6830 ``` *Note*: The service IP can also be a preferred IP address. This can be enforced while creating the service configuration with the `-ip` option. ---> \ No newline at end of file +-->