Traffic Management Configuration

A10 Lightning ADC offers comprehensive load balancing functionalities such as elastic, secure, and centralized management of cloud applications. However, its main advantage comes from its use of cloud infrastructure to dramatically improve application deliveries in the cloud and data center environments. The figure below shows the deployment of the Application Delivery System (ADS) on a full scale.

_images/image_ADS_Deployment.png

A10 Lightning ADC uniquely enables the following load balancing capabilities of cloud application:

  • Layer 4 to Layer 7 advanced load balancing with autoscale

Extends the traditional load balancing services with content switching and session persistence.

  • Policy-based traffic management

Specifies policies to optimally fulfill user requests.

  • Close-loop application delivery

Offers real-time application analytics, also provides adjustments for loading balancing policies.

In the case, where your organization is migrating it’s legacy applications from the data center, or building a new container based micro service applications in the cloud. The A10 Lightning ADC load balancer deploys in minutes through an application-intimate proxy in your availability zone.

The A10 Lightning ADC Elastic Load Balancing(ELB) service enhances the cloud application capacity, flexibility, and visibility without any changes to application code.

Application Domain

A10 Lightning ADC accepts the client requests for the domain names configured as application domains. When you onboard A10 Lightning ADC, it creates an application domain by default (based on your application endpoint).

Adding and Removing a Domain

Adding a Domain

Follow the steps below for configuring an application domain in A10 Lightning ADC:

  1. In A10 Lightning ADC goto Configuration > Application Configuration > Settings screen.
_images/image1.0.png
  1. Select Add a Domain, enter the domain name (For example, www.example.com), and then click Save to add an application domain.
_images/image1.1.png
_images/image1.2.png

Adding Multiple Application Domains

You can add as many Fully Qualified Domain Names (FQDNs) as application domains, using the Add a Domain option. Wildcard (*) may be used for specifying all the subdomains of a domain.

Deleting a Domain

If you have multiple doamins, you can delete a domain by simply clicking Delete button, and then clicking the Delete Domain button.

_images/image1.3.png
_images/image1.4.png

Application DNS

Application DNS refers to the DNS name of Lightning ADC(LADC). If you are using a third-party DNS provider, then when you choose the option Other while adding your application, you need to change the DNS record of your Application Domain in the DNS Provider such that it points to Application DNS. And then, manually replace the CNAME record in your DNS provider with the Application DNS URL in this field. If you choose Route 53 as your DNS provider, this step is automated.

_images/image1.5.png

Note

You need a public DNS entry (For example, www.example.com or app.example.com) with DNS service provider of your choice for enabling users to access your application. Typically, the DNS entry is a ‘CNAME’ record or an ‘A’ record in your application domain’s hosted zone file.

Changing DNS Entry for Enabling Traffic Flow

Once you have completed required configurations, select Change DNS on the Settings Page. A message pop-up is displayed asking if you want to update the DNS information.

When Change DNS button is selected, the traffic from the application domain is routed through the Lightning ADC (LADC). The LADCs deployed, are your application Front End at this step. Note, that until you enable A10 Lightning ADC, traffic does not pass through the LADC.

_images/image1.6.png

The above steps complete the onboarding process in A10 Lightning ADC.

Ports

Adding a Port

A10 Lightning ADC listens for application traffic on the listening ports. To add a port(s)in the settings screen click on ADD PORT/LISTNER option. You can even add multiple listening ports if required.

_images/image1.7.png

Note

Before adding any HTTP2 or SSL ports make sure SSL is enabled.

Removing a Port

If you have multiple ports, you can delete a port by simply clicking Delete button, and then clicking the Delete option.

Note

Disabling SSL will also disable HTTP2

_images/image1.8.png
_images/image1.9.png

SSL Termination

Configuring SSL for a Domain

Each Application Domain with Fully Qualified Domain Names (FQDNs) requires its SSL settings if SSL is enabled on A10 Lightning ADC. When you add a new application domain and want to copy the SSL settings of an existing domain to the new one, use the Copy SSL Settings option.

SSL Certificates (also called digital certificates) is enabled to establish a secure encrypted connection between A10 Lightning ADC and Application Servers. The SSL connection protects sensitive data exchanged during each session.

To enable SSL, you need to have a valid SSL Certificate that identifies you and install it on the application server. A padlock icon is used to indicate the usage of SSL certificate in a web browser. However, it can also be shown by a green address bar. Once SSL installation is complete, you can access A10 Lightning ADC securely by changing the URL from Http:// to Https://. When an SSL certificate is installed on the application server, you can be sure that the information you enter is secure.

_images/image1.10.png

When you enable SSL in A10 Lightning ADC, the below options are displayed. Click on the relevant help buttons to get more information on these options.

  • Validate Certificate using server certificate chain/server key
  • Option to choose SSL Versions
  • Option to choose Ciphers
  • Option to choose Client Authentication

Copying SSL Properties to Multiple Domains

If SSL is already configured in a domain, we can copy the same config to newly added domains. Click on the Copy SSL settings and select the domain to copy SSL settings from in the left section. Select the domain to copy SSL settings to in the right section and click on Copy as shown in the figure below.

_images/image1.29.png

Http2

HTTP/2 is the next-generation protocol for transferring information on the web, improving upon HTTP/1.1 with more features leading to better performance. It manipulates HTTP traffic, with particular goals of reducing web page load latency and improves the web security. This policy can only be enabled with SSL as shown in the figure below.

_images/image1.30.png

Services

A service is identified by a traffic condition and a set of servers that serve traffic for client requests that match the traffic condition.

Default Service

When we configure an application a default service is created with the servers discovered/specified while onboarding an application.

Creating a Service

A new service is created under the following conditions:

  • When the traffic is served from a different set of servers.
  • When the traffic is served from various ports of the same set of servers.

Ordering of Services

If there are multiple services, they can be reordered using the up/down arrow icons based on which service the traffic should pass through.

_images/image1.31.png

Service Condition

When you add a service, you can configure traffic conditions within the service, and when there are client requests that match these service conditions they are served by the application servers.

_images/image_ServiceCondition.png

You can configure logical conditions for a service, using the following options:

  • URL Path: Enter the URL path value.
  • Header: Enter the header parameter name and value.
  • Cookie: Enter the header parameter name and value.
  • Query Parameter: Enter the query parameter name and value to present in the query string in a GET request.
  • Scheme: Select the scheme as Http or Https.
  • Method: The Http method on which this request is made. There are 4 Http methods; they are GET, POST, PUT, and DELETE.
  • Port: Enter the port value.
  • POST Body Parameter: Enter the POST Body Parameter value in the POST Request.
  • Country: The country code for the client network. This code is a two letter or three letter code or full name of the country.
  • Network: Network IP Address of the client network.

Use the logical operators AND and OR to combine multiple conditions and form a single final service condition. Once you have created a service, you can edit the service configurations later if required, using the pencil icon.

Servers

The Application Servers configured within the service are displayed in the Servers section. These servers provide/serve traffic that matches the conditions specified in the service. You can edit the application server configuration using the adjacent pencil icon (View/Edit Server Group).

_images/image1.11.png

The Edit Servers window is displayed where you can modify the application server information.

_images/image1.12.png
./images/image1.38ServiceDownCondition.png
_images/image1.32.png

Load Balancing

Load balancing distributes client requests across multiple servers to optimize resource utilization. In a scenario where a limited number of servers provide service to a large number of clients, a server can become overloaded degrading server performance. Load balancing is used to prevent bottlenecks by forwarding the client requests to the servers best suited to handle them, thus balancing the load.

Load balancing uses algorithms called load balancing methods, to determine how the load is distributed among the servers.

In A10 Lightning ADC, you can select any of these load balancing methods:

  • Least Connections
  • Round Robin
  • IP Hash
  • IP Port Hashing
  • Least Connections

When a load balancer is configured to use the least connection method, it selects the service with the least number of active connections to ensure that the load of the active requests is balanced on the services. This method is the default load balancing method because it provides the best performance.

This method is used when you do not want to overload a busy server and distribute the load to other servers which are relatively less loaded.

Round-Robin

Round-robin load balancing is one of the simplest methods for distributing client requests across a group of servers. In this mode of load balancing, the load balancer passes each new connection request to the next server in line, eventually distributing connections evenly across the array of machines being load balanced. When it reaches the end of the list, the load balancer loops back and goes down the list again (sends the next request to the first listed server, the one after that to the second server, and so on).

When configuring a service in A10 Lightning ADC, choose the round-robin load balancing method if there are enough number of client requests and when they need to be processed almost equally and fast enough among the available servers. Also, note that round-robin method should be used when application servers are stateless and sessions are managed centrally at the back-end.

IP Hash

In the IP Hash load balancing, the client’s IP address is used as a hashing key to select the server (from the server group) to which the client’s requests are directed. This load balancing method ensures that the requests from the same client are always directed to this server, except when the server is unavailable.

This mode is particularly useful when you want to direct requests from the same client to the same server always. The IP hash method is useful when your application servers are stateful.

IP Port Hashing

In the IP Port Hash load balancing, the client’s IP address and Port number are used to calculate the hashing key to select the application server (from the server group) to which the client’s request are directed. As long as the IP address and the port number remain the same, the client’s requests are directed to the same server. But if the port number changes (but the IP address remains the same), the client’s requests are directed to a different server. Also, when the port number varies on the same client machine, the client’s requests are redirected to a different server.

In A10 Lightning ADC, load balancing is always enabled and defaults to ‘Least Connections’ even if the checkbox is unchecked. You can choose ‘Round Robin’ or ‘IP Hash’ by selecting the corresponding radio button.

Session Persistence

Session persistence refers to directing a client’s requests to the same back-end web or application server for the duration of a “session” or the time it takes to complete a task or transaction. Also, we can redirect the same client to the same server, using the session persistence.

Note

A session is defined as a series of transactions between a client and a server, over some finite period of time– ranging from several minutes to hours.

When you enable Session Persistence in a service in A10 Lightning ADC, the following options are displayed:

Query Parameter

The query parameter in the HTTP GET request. For example, in the HTTP request http:// www.abc.com/w/index.php?title=Main_page&action=raw, the query parameter name is the title.

Location Affinity

Location Affinity provides the capabilities to load balance the inter-zone traffic, distributing the traffic evenly across the application servers with location aware load balancing.

Location Affinity supports Affinity Only and Affinity Weight options which give the user the flexibility to load balance the traffic more precisely within the Zone.

Note

The Location Affinity is supported only in AWS.

Note

When Location Affinity is enabled, it is recommended to disable the Session Persistence to avoid any interoperability issues.

Affinity Only: When this option is enabled Lightning ADC will only use Application Servers with the same zone as itself. Other Application Servers will only be used in case all local Application Servers are out of service.

Note

When Affinity Only is enabled, Affinity Weight option is ignored.

Affinity Weight: When this option has been enabled the weight of the zone local server is multiplied by the Affinity Weight specified in the filed.

For example, Assume these are the servers configured along with their weights.

  • 190.168.128.31 - Weight 1
  • 190.168.128.32 - Weight 1

When Affinity Weight is set to 2 and assuming 190.168.128.31 is the zone local server, configuration will be written out as

  • 190.168.128.31 - Weight 2 (1 * 2)
  • 190.168.128.32 - Weight 1

For every 3 requests, LADC will push 2 requests to 190.168.128.31 and 1 request to 190.168.128.32. By adjusting Affinity Weight, the user can keep more requests within the same zone as Lightning ADC.

Configuring Location Affinity

The Location Affinity is configurable both in the existing default service and also in the new service after onboarding.

To configure Location Affinity in the default service, click View/Edit Server Group and enable the Location Affinity as shown. Note, by default the Location Affinity feature is disabled.

_images/image1.43.png
_images/image1.44.png

To configure Location Affinity for a New service in A10 Lightning ADC goto Services > Add New Service > Server Information > Location Affinity as shown below:

_images/image1.39.png

Select the AWS in the server field.

_images/image1.40.png

When Affinity Only is enabled the Affinity Weight is disabled.

_images/image1.41.png

The Affinity Weight is enabled since Affinity Only is disabled.

_images/image1.42.png

Server Monitoring

When adding a new service in A10 Lightning ADC, you can configure out-of-band monitoring of application servers where A10 Lightning ADC probes actively whether the application servers are active or not. You need to specify the monitoring protocol (TCP/HTTP, or secure TCP/HTTP connections), monitoring interval, and timeout.

Note

You can monitor the Application Server Health from the Dashboard.

Description of Fields

  • Monitor Protocol: You can set the protocol over which A10 Lightning ADC provides application server monitoring. The protocol can be TCP or Http. For secure monitoring, use SSL over TCP or Http options.
  • Monitor URL: When you select the monitor protocol such as Http or Https, you must also specify the Monitor URL. In this case, A10 Lightning ADC probes the monitor URL specified. Note that this field is visible only when you select Http or Https.
  • Monitor Interval: The time (in seconds) for which the application server is probed and monitored.
  • Monitor Timeout: The time (in seconds) after which the monitoring probe should timeout, within the monitoring interval.

Server Limits

When you configure a new service in A10 Lightning ADC, you can specify the required timeouts when requesting information from the application server or when getting a response from the application server.

Description of Fields

  • Close connection to server if cannot read for(seconds):

Here you can specify the time within which you want to close the connection to the application server if you cannot read the required information from the server within this specified time.

For example, suppose you have set this timeout value to 300 seconds. If you want to download information from the server, and if the task takes more than 300 seconds (say 500 seconds), your connection to the server closes in 300 seconds as the timeout value is 300 seconds. So you may increase this timeout value to 500 seconds so that your download is complete.

  • Close connection to server if cannot write for(seconds):

Here you can specify the time within which you want to close the connection to the application server if you cannot write the required information on the server within this specified time.

For example, suppose you have set this timeout value to 300 seconds. If you want to upload information to the server, and if the task takes more than 300 seconds (say 500 seconds), your connection to the server closes in 300 seconds as the timeout value is 300 seconds. So you may increase this timeout value to 500 seconds so that your upload is complete.

SSL between Proxy and Server

Secure Sockets Layer (SSL) Certificates (also called digital certificates) can be enabled to establish a secure encrypted connection between A10 Lightning ADC and Application Servers. The SSL connection protects sensitive data exchanged during each session.

To enable SSL, you need to get an SSL Certificate that identifies you and install it on the application server. The use of an SSL certificate is usually indicated by a padlock icon in web browsers, but it can also be shown by a green address bar. Once you have done the SSL installation, you can access A10 Lightning ADC securely by changing the URL from http:// to https://. When an SSL certificate is installed on the application server, you can be sure that the information you enter is secure.

When you enable SSL in A10 Lightning ADC, following options are displayed. Click on the relevant help buttons to get more information on these options.

  • Validate Certificate
  • Option to choose SSL Versions
  • Option to choose Ciphers

Service Down Condition

When all the servers configured in a service are down (not functioning), the service is said to be down. A10 Lightning ADC provides you three different options to account for this downtime:

Select the option to configure fallback if all servers go down. To enable the options, do the following.

  • Use this service

Choose an existing service to which you can redirect the traffic when your service is down.

  • Send static content

Provide the response code and URL to which you can re-direct the traffic when your service is down.

  • Redirect to

Provide the redirect URL to which you can redirect the traffic when your service is down.

Backend Server Surge Protection

The Backend Server Surge Protection policy prevents the backend server from getting overloaded with indefinite traffic, which may cause the server to perform inefficiently. With this policy, the user can limit the traffic flow to the server and limit the keep alive time for a connection based on the values set. The two fields which are Connection Keepalive Timeout and Maximum Number of Request Per Connection allows the user to set the connection keepalive time and maximum request allowed in a connection. It is recommended to set the connection keepalive timeout value as “4”, which means if the connection is ideal with no requests coming in for 4 seconds the connection is closed. Similarly, the user can set the maximum number of requests allowed per connection.

Activating and Deactivating a Service

Once you create a service, you need to activate the service so that A10 Lightning ADC passes traffic through the application servers configured within the service.

Default service is activated once the cluster association is completed. New services, when created, has to be activated for the traffic to pass through. A service can be deactivated using the disable icon

Activating a New Service

Follow the steps below to Add a New Service and Activate the Service:

  1. Form the Services Screen click on ADD NEW SERVICE and in the next screen configure a new service.
_images/image1.13.png
  1. Click on Activate button to enable the Service.
_images/image1.14.png

Deactivating a Service

To deactivate a service, click on De-activate button and then select De-activate option.

_images/image1.15.png
_images/image1.16.png

Smart Flow

Default SmartFlow

When you create a new service, a default SmartFlow is created with the traffic condition(s) defined in the service.

Adding a SmartFlow

New smart flow is created when policy configuration is required for a different smart flow condition. In this case, a request from the client will hit the smart flow if the condition matches. When multiple smart flows are created, it can be reordered as required.

SmartFlow Configuration

Follow the below steps to configure a SmartFlow:

  1. Click Application > Services
_images/image1.36.png
  1. Click Add a SmartFlow and provide the Smartflow Service details as below.
_images/image1.37.png
  1. Set the Smartflow conditions in the respective fileds.

SmartFlow Conditions

List below describes the SmartFlow conditions:

  • URL Path: Enter the URL path value.
  • Header: Enter the header parameter name and value.
  • Cookie: Enter the header parameter name and value.
  • Query Parameter: Enter the query parameter name and value to present in the query string in a GET request.
  • Scheme: Select the scheme as Http or Https.
  • Method: The Http method on which this request is made. There are 4 Http methods; they are GET, POST, PUT, and DELETE.
  • Port: Enter the port value.
  • POST Body Parameter: Enter the POST Body Parameter value in the POST Request.
  • Country: The country code for the client network. This code is a two letter or three letter code or full name of the country.
  • Network: Network IP Address of the client network.
  • Allow Traffic - If the smart flow condition matches, the policies configured will be applied if this is enabled
  • Redirect Traffic to - If the smart flow condition matches, the traffic will be redirected [temporarily or permanently] to the URL specified
  • Deny all Traffic - If the smart flow condition matches, all the requests will be denied with no response or the desired message entered by the user

SmartFlow Actions

Configuring Action Policy Rules

In the action policy rules, you can do these tasks:

You can specify rules or action policies that return custom content to the user (For example, an alias response code), for the response codes coming from the application server. This enhances the user experience, For example, if you want to hide a particular response code from the user, you can specify an alias code in the action policy configured in the Lightning ADC (LADC), so that the user sees the alias code instead of the response code that you want to hide. In the action policy rules, you can do these tasks:

  • Set up alias response codes or alias response URLs that the Lightning Application Delivery Controller (LADC) should provide the user, for the response codes coming from the Application server.
  • Redirect the user to a redirect URL

Activating and Deactivating a SmartFlow

Whenever a new smart flow is created, it needs to be activated [using the enable/disable button]. In the case of multiple smart flows, if one is deactivated the traffic will hit the one which is below in order.

_images/image1.33.png
_images/image1.34.png

Traffic Manipulation Policies

URL Rewrite

The URL Rewrite policy helps you to rewrite complex URLs into user-friendly and search-friendly URLs without changing the page structure.

Configuring URL Rewrite Policy

After rewriting the URL, do the following; Choose an option from After Rewrite drop-down box. These options are used to apply specific rules to re-written URLs. Enable the policy using the Enable button. Finally, enable the Case Insensitive button, this allows the server to ignore cases in rewritten URLs.

_images/image1.17.png

Response Body Rewrite

You can control the display of text, headers and error code to web page visitors by using Body Rewrites function.

Configuring Body Rewrites Policy

Enter the Regex or String value in the field named Match. Enter a new string value or Regex in the Replace With field, and click Enable button. Enable Case Insensitive button, this is optional.

_images/image1.18.png

Header Rewrite

HTTP rewriting is the technic which allows the proxy to change content on the fly while .We can Add/Delete/rewrite request and response headers. The following header requests are configured by default in the smart flows-

  • X-Forwarded-For adds the server IP
  • X-Forwarded-Proto adds the scheme
  • X-Forwarded-Port adds the server port
_images/image1.19.png

Cross-Origin Resource Sharing(CORS)

In A10 Lightning ADC, you can specify a Cross-Origin Resource Sharing (CORS) policy which includes Http headers to allow communication between pages from different origins. You may want to enable CORS policy only if you have such a use case.

_images/image1.20.png

Specifying Allowed Domains

Here, you need to define the domains allowed to share resources with your servers. You should specify this using base URL where wildcard (*) denotes all subdomains. Only GET and POST methods are allowed. For example, specifying https://.example.com in the policy allows any page from any sub­domain of example.com to share a resource with your server over Https. You can specify more than one base URL by pressing the **+* Add More option.

Returning custom response

You can specify rules or action policies that return custom content to the user (For example, an alias response code), for the response codes coming from the application server. For instance, if you want to hide a particular response code from the user, you can specify an alias code in the action policy configured in the Lightning ADC (LADC), so that the user sees the alias code instead of the response code that you want to hide. However, when Allow merging of Rules option is enabled then the Return custom content security policies set at the Application level is merged with the Action policies settings, if Allow merging of Rules option is disabled then policies set under Action policies holds good for Smartflow traffic. And, if Action policies are disabled, then by default Return custom content settings holds good for application traffic.

_images/image1.21.png

Traffic Optimisation Policies

Compression

The compression policy is used to deliver content or data faster by reducing the amount of data that is transferred. The speed of data transfer increases with data compression. While defining the compression policy, you just need to provide the minimum size you want to compress and the type of content to be compressed. The minimum compression size is an integer value measured in bytes, and the type of content that to be compressed can be plain text/HTML or just plain text.

Follow the steps below to configure a compression policy in A10 Lightning ADC:

  1. In A10 Lightning ADC window click Configuration > Services > Add a Smart Flow.
_images/image1.22.png
  1. Select Performance under Policies and then select Compression. Enter a number in the Min Compressible Size (bytes) box. This number specifies the minimum file size for compression. Compress any text or application content by choosing any one of the options as listed in Content types.
  • text/html
  • text/plain
  • text/css
  • application/json
  • application/xml
  • application/javascript
_images/image1.23.png

Viewing the Compression Policy Metrics

You can use Analytics > Metrics menu to see the compression policy metrics for a selected service. Browse through the charts to see the Compression policy-related metrics.

./images/.png

Caching

Caching reuses information stored earlier to respond to a client request, to reduce data traversing on a network and decreases response times.

Note

HTML pages are cached automatically, hence, activating this function will not impact transmission of such pages.

Viewing the Caching Policy Metrics

You can use Analytics > Metrics menu to see the Caching policy metrics for a selected service. Browse through the charts to see the Caching policy-related metrics.

./images/.png

PageSpeed

Page Speed policy accelerates delivery of both HMTL and non-HTML pages.

Note

HTML pages are delivered faster even without Page Speed because of Caching.

The surge queue trend graph is viewed from Analytics > Metrics menu.

_images/image63.png

This chart shows the pending requests from clients (queued within the surge queue) plotted against the number of claims or request count.

Blue/Green Deployments

A popular DevOps use case for A10 Lightning ADC is automating Blue/Green deployments to enable continuous delivery with zero downtime. Use A10 Lightning ADC to set traffic steering policies for inbound traffic across old (blue) and new (green) deployments while both environments remain online. Monitor blue and green server behavior and health metrics to adjust traffic steering rules in real-time. A10 Lightning ADC improves productivity by providing a unified view of the entire Blue/Green deployment process.

_images/image_Blue-GreenDeploymentDiagram_NEW.png

A10 Lightning ADC supports Blue/Green deployments and precise traffic steering between the different releases. Blue/Green deployment is a powerful technique for directing traffic between old (blue) and new (green)deployments while both environments remain online.

A10 Lightning ADC allows its customers to define and manage a split traffic rule for their Blue/Green deployments. That is, customers can specify the IP addresses for their blue and green versions and control what portion of the live production traffic should be directed to which deployment. You can choose a simple percentage split or create a split rule based on anything in HTTP request object, such as a geographic region.

Another advantage is that the A10 Lightning ADC customers gain precisely targeted phased rollouts without any effort on the development side, using Blue/Green deployment. Set and change the traffic split rule from the A10 Lightning ADC user interface, where you can also monitor health and success metrics for both deployments. Drive more traffic to the green implementation when the confidence in the green release increases. If problems arise, direct all the traffic back to the blue release.

Here is the workflow for a typical Blue/Green deployment:

_images/image52.png

Configuring Blue-Green deployment in A10 Lightning ADC

Follow the below steps to configure Blue/Green deployment in A10 Lightning ADC:

  1. From A10 Lightning ADC screen Select Configuration > Blue/Green. The following settings screen is displayed, select Configure a Blue/Green Deployment.
_images/image1.24.png
  1. Choose an existing service; this is marked as Blue service. At the same time, a clone is created which is characterized as Green service.
_images/image1.25.png
  1. Select Next configure Green Service. The screen to configure Green service deployment is displayed.

Enter the following details in the screen below:

  • Service name: Enter the blue-green service name with a maximum of 30 characters.
  • Description: Enter a description for the service.
  • Direct a set percentage traffic to Green Service: Enter the integer value of the percentage of traffic that you want to direct to Blue Service and Green Service.
  • Mirror Traffic (Only GET requests): All the requests that hit green will be mirrored to blue service.
  • Direct traffic to Green service based on condition: Enter a service condition, and based on this condition the traffic will be redirected to the Green service.
_images/image1.26.png
  1. Select Next select servers for Green. The Add Servers for Green Service screen is displayed.

You can add the servers manually by entering the IP Address and Port number.

_images/image1.27.png

(Or) choose the servers from Blue service.

_images/image1.28.png

Select Save Blue/Green deployment, this saves the deployment. The blue-green service is visible from the Configuration>Services tab. You can also edit the service from this tab.

_images/image1.35.png