[JBoss JIRA] (JBIDE-14647) investigate safe replacement for org.eclipse.jgit.internal.storage.file.FileRepository
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14647?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-14647.
---------------------------------
> investigate safe replacement for org.eclipse.jgit.internal.storage.file.FileRepository
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-14647
> URL: https://issues.jboss.org/browse/JBIDE-14647
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Affects Versions: 4.1.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Beta2
>
>
> In org.jboss.tools.openshift.egit.test we have a class TestRepository that we use to test our EGit utils. This class is using *org.eclipse.jgit.internal.storage.file.FileRepository* which is marked as internal, not publicly exported. We should look into a replacement since using it is not safe.
> I mailed jgit-dev on the 27th of May:
> {quote}
> we heavily use egit/jgit in our OpenShift tooling. We have our own set of tests and in these we use org.eclipse.jgit.internal.storage.file.FileRepository to check our commit- and push-facilites work right.
> Unfortunately org.eclipse.jgit.internal.storage.file.FileRepository is marked as internal and using it is therefore not safe/recommended. Can you please export this class publicly or point us to a public replacement?
> {quote}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 1 month
[JBoss JIRA] (JBIDE-13934) implement application ready-wait using dns_resolvable
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13934?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-13934.
---------------------------------
Closing as rejected.
> 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: LATER
>
>
> 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 was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 1 month
[JBoss JIRA] (JBIDE-15158) if I create a scalable application I get a non-useful dialog about HAProxy (watcher)
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15158?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-15158.
---------------------------------
Verified in JBDS 8.0.0.Beta3c.
> if I create a scalable application I get a non-useful dialog about HAProxy (watcher)
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-15158
> URL: https://issues.jboss.org/browse/JBIDE-15158
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Affects Versions: 4.1.0.CR1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.2.0.Alpha1
>
> Attachments: ha-proxy-started.png
>
>
> How to reproduce:
> # ASSERT: make sure that you dont have any scalable application in your domain
> # EXEC: launch OpenShift application wizard and provide some name, type and check *enable Scaling*
> Result:
> You get a dialog which informs you that the HAProxy was started:
> !ha-proxy-started.png!
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 1 month