[jbosstools-issues] [JBoss JIRA] (JBIDE-13934) implement application ready-wait using dns_resolvable

[Andre Dietisheim (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-13934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andre Dietisheim updated JBIDE-13934:
-------------------------------------

    Fix Version/s: 4.2.x
                       (was: 4.1.x)

    
> implement application ready-wait using dns_resolvable
> -----------------------------------------------------
>
>                 Key: JBIDE-13934
>                 URL: https://issues.jboss.org/browse/JBIDE-13934
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: openshift
>    Affects Versions: 4.1.0.Alpha2
>            Reporter: Andre Dietisheim
>            Assignee: Andre Dietisheim
>             Fix For: 4.2.x
>
>
> When waiting for an app to become ready, we simply try to resolve it's hostname and report it ready as soon as we can resolve it.
> Apparently there's a cache for DNS resolution that holds entries (successful/unsuccessful resolution) that prevents immediate feedback. The immediate feedback is provided by a RESTful resource on the broker:
> {code}
> GET  https://host/broker/rest/domains/<id>/applications/<id>/dns_resolvable
> {code}
> Quote from rally
> {quote}
> 1. Who is it for? (e.g. all users, serious developers, paid tier)
> All users
> 2. What product does it apply to? (Online, Enterprise, Origin)
> All
> 3. What is it? What does it do?
> A simple broker API check to see if DNS is created via an actual DNS nameserver lookup that is not subject to caching.
> 4. How do you use it? What is the user impact?
> Request:
> GET  https://host/broker/rest/domains/<id>/applications/<id>/dns_resolvable
> Response:
> ->If DNS is resolvable
> HTTP status:200
> Body:  {"supported_api_versions":[1.0,1.1,1.2],"data":true,"type":"boolean","status":"ok","messages":[],"version":"1.2"}
> ->If DNS is not resolvable
> HTTP status:404
> 5. Why is it important?
> The problem is when a client tool checks to see if DNS is available or not, that value gets cached for a solid 30 seconds. To avoid the cache, queries can be run directly against DYN's DNS servers.
> This broker API check to see if DNS is created by querying DNS servers directly.
> 6. What version number of software, package, client tools, etc?
> NA
> 7. When is it available for GA? (OSE 1.2, Online Sprint #)
> Spring 19
> 8. What tools / software does the docs team need to test it? (if applicable)
> NA - already been tested by QE
> 9. Are there any blog or wiki posts on the subject? (Provide links)
> No
> 10. Any other notes or details that users should know that will help the docs team?
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira