New Await strategy: Await ping service

[aslakknutsen]

In lights of 'ss' seemingly being removed from all over the place to align the content of base docker images, I think we can expect ss to be more and more un available in the future:
jboss-dockerfiles/base#5

A possible await strategy could be to deploy a minimal container that can ping the target containers from inside the machine/host.

• Create/Start a Arquillian Ping container
• Create/Start the configured N containers
• Communicate with the Ping container
  • http://ping/internal_container_ip/ports...

Of course, the question remains, when do we know the Ping container is up and running? I guess we could create a resilliant await client that can attempt a few times before failing. With a minimal sized image it shouldn't take long to start the service.

[lordofthejars]

how about trying other commands that runs pretty similar as ss? Do you think all of them are going to be removed? Also I am still see two options:

1. user need to create a dockerfile that installs ss.
2. we can install it by letting user set the command to execute to install it.

[smiklosovic]

maybe this is the right time to incorporate propper api for connection checks on application layer, afaik port binding done doesnt necessarilly mean the target app under test is fully running

[smiklosovic]

i have connection checks on tcp and udp layer based on spacelift reexecution feature of connection tasks, could not that just be called repeatedly until successful connection or timeout?

[lordofthejars]

This is the polling strategy right?
El 6/2/2016 10:10 a. m., "Štefan Miklošovič" [email protected]
escribió:

i have connection checks on tcp and udp layer based on spacelift
reexecution feature of connection tasks, could not that just be called
repeatedly until successful connection or timeout?

—
Reply to this email directly or view it on GitHub
#283 (comment)
.

[aslakknutsen]

A Health API Ping would be a common strategy.

[lordofthejars]

we can use https://github.com/vishnubob/wait-for-it but this implies copying that file into container and execute it. This change could be related with #333

[lordofthejars]

@aslakknutsen can I close this issue with won't fixed since now we can register custom await strategies?

[aslakknutsen]

@lordofthejars Sure, but maybe create a new one for e.g. 'HTTPAwaitStrategy' that can verify a HTTP response by content/status code ?