v1.9.1-criteo4: Criteo: travis build

Change-Id: I6f6913b3f07ede35c40bb92294ee506b0dd9dc4c

v1.9.1-criteo3

[Streaming][Bugfix] Fix error(s) on services not being modified befor…

v1.9.1-criteo2

[Streaming][bugfix] handle TLS signalisation when TLS is disabled on …

v1.9.1-criteo1: Criteo: travis build

Change-Id: I6f6913b3f07ede35c40bb92294ee506b0dd9dc4c

v1.8.6-criteo1: Criteo: travis build

Change-Id: I6f6913b3f07ede35c40bb92294ee506b0dd9dc4c

v1.8.5-criteo1: Criteo: travis build

Change-Id: I6f6913b3f07ede35c40bb92294ee506b0dd9dc4c

v1.8.4-criteo3: Criteo: travis build

Change-Id: I6f6913b3f07ede35c40bb92294ee506b0dd9dc4c

v1.8.4-criteo2: [BUGFIX] Avoid GetDatacenter* methods to flood Consul servers logs

When calling `GetDatacentersByDistance()` or `GetDatacentersMap()`, an
incorrect condition was used to diplay log message, thus flooding
Consul's logs.

Example of message:

```
  [WARN] agent.router: Non-server in server-only area: non_server=myClientNode area=lan
```

This message is only valid for WAN areas, filter to avoid creating
hundreds of logs/s on our clusters, each time someone is calling this
method.

Our logs were flooded by such messages when migrating our Consul servers
from 1.7.7 to 1.8.4.

This will issue fix #8663

v1.8.4-criteo1: Criteo: travis build

Change-Id: I6f6913b3f07ede35c40bb92294ee506b0dd9dc4c

v1.8.3-criteo1: Criteo: travis build

Change-Id: I6f6913b3f07ede35c40bb92294ee506b0dd9dc4c