containers-a8 / sampleapp Goto Github PK

1. Run the official image (from dockerhub) of consul
2. Expose the consul UI on the public IP so that we can see the UI

We need to manage de-registration of services.
Broadly there are two options

1. In Consul 0.7 and later, checks that are associated with a service may also contain an optional deregister_critical_service_after field, which is a timeout in the same Go time format as interval and ttl. If a check is in the critical state for more than this configured value, then its associated service (and all of its associated checks) will automatically be deregistered. [https://www.consul.io/docs/agent/checks.html]
2. Deregister when the container stops. I see two options here:
   1. Can we run a clean up script when the docker stop is executed?
   2. The SIGTERM signal is passed to processes in the container. If we can trap this signal, then we can deregister the service. For example a script looping with a trap which runs a cleanup function on SIGTERM and SIGINT

Option 1. is easier to implement, but has two significant problems. It will leave the registry in a stale state until the critical timeout is reached and it could cause http timeouts and slow response as the stopped service instances won't be detected until the consul runs the health check against that service instance.

Option 2. is better but requires more work to customise the container and is more intrusive on the DevOps. As we are already injecting a goreman procfile to register the service, this would be one extra modification.

1. Currently we are working independently as we are not able to join other's Org. We need to be able to use a single org and space.

This is used as a placeholder for the environment properties in the Pipeline