Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-16939

OpenShift application creation should not lock the UI while waiting for DNS to propagate

    • Icon: Feature Request Feature Request
    • Resolution: Duplicate
    • Icon: Major Major
    • 4.2.0.Beta2
    • None
    • openshift
    • None

      After completing the OpenShift -> New Application wizard, the UI locks while Eclipse waits for the OpenShift operation to complete. Many OpenShift operations (including application creation) can take quite a while, and it should be able to be moved to the background, allowing the user to continue working while waiting.

            [JBIDE-16939] OpenShift application creation should not lock the UI while waiting for DNS to propagate

            Closed as duplicate.

            Marián Labuda (Inactive) added a comment - Closed as duplicate.

            Sorry for the confusion.

            Lincoln Baxter III (Inactive) added a comment - Sorry for the confusion.

            Right Blocking != Freezing

            Lincoln Baxter III (Inactive) added a comment - Right Blocking != Freezing

            André Dietisheim added a comment - - edited

            oh, gotcha, by "freezing" you mean that the wizard is blocking you from doing anything else. The UI thread by itself is NOT frozen, the UI is still responsive but the user is blocked. I fully agree, this is suboptimal and tends to get more annoying the more OpenShift takes time to create applications (which got worse overtime, it started with 30+ seconds in the early days). We already planned to close the wizard once we triggered the creation: JBIDE-11367. Unfortunately lacking manpower there was still no time to implement it.

            André Dietisheim added a comment - - edited oh, gotcha, by "freezing" you mean that the wizard is blocking you from doing anything else. The UI thread by itself is NOT frozen, the UI is still responsive but the user is blocked. I fully agree, this is suboptimal and tends to get more annoying the more OpenShift takes time to create applications (which got worse overtime, it started with 30+ seconds in the early days). We already planned to close the wizard once we triggered the creation: JBIDE-11367 . Unfortunately lacking manpower there was still no time to implement it.

            As I mentioned in the original description, this occurs simply by completing the OpenShift New Application wizard.

            1. In the "OpenShift" view, right click on your account.
            2. Select "New" -> "Application"
            3. Enter an application name and select the gear type (I used EAP6 and a small gear)
            4. Click "Finish"

            OpenShift will now create the application and propagate the new DNS entry out to "the internet" - This can take quite some time, anywhere from 5 seconds to 5 minutes.

            The dialog remains open until this operation is finished. It is not possible to put this into the background.

            Additionally. As I just discovered while attempting to give exact steps. If you take too long to accept the RSA Fingerprint Dialog Box, the Git streaming operation times out and the application fails to import entirely.

            I highly doubt this is environment specific, but I use OSX 10.9.2 with Oracle Java 1.7_51 on a 64bit quad core intel i7 with hyper-threading and 16mb of memory.

            Lincoln Baxter III (Inactive) added a comment - As I mentioned in the original description, this occurs simply by completing the OpenShift New Application wizard. 1. In the "OpenShift" view, right click on your account. 2. Select "New" -> "Application" 3. Enter an application name and select the gear type (I used EAP6 and a small gear) 4. Click "Finish" OpenShift will now create the application and propagate the new DNS entry out to "the internet" - This can take quite some time, anywhere from 5 seconds to 5 minutes. The dialog remains open until this operation is finished. It is not possible to put this into the background. Additionally. As I just discovered while attempting to give exact steps. If you take too long to accept the RSA Fingerprint Dialog Box, the Git streaming operation times out and the application fails to import entirely. I highly doubt this is environment specific, but I use OSX 10.9.2 with Oracle Java 1.7_51 on a 64bit quad core intel i7 with hyper-threading and 16mb of memory.

            lincolnthree Could you be please more descriptive? Steps to reproduce, environment...? Thanks

            Marián Labuda (Inactive) added a comment - lincolnthree Could you be please more descriptive? Steps to reproduce, environment...? Thanks

            lincolnthree Still puzzled where you experience this and what tells you that it is DNS related. All tasks are afaik done in background jobs.
            Any chance you screencast what you exactly mean?

            André Dietisheim added a comment - lincolnthree Still puzzled where you experience this and what tells you that it is DNS related. All tasks are afaik done in background jobs. Any chance you screencast what you exactly mean?

            This is with the current JBDS 7.2 (or whatever the latest product release is)

            The OpenShift -> New Application wizard is where I specifically noticed this blocking. It may be the only place. I don't know if others block, I just know that OpenShift takes some time, so other should be checked to make sure they can be put into the background.

            Lincoln Baxter III (Inactive) added a comment - This is with the current JBDS 7.2 (or whatever the latest product release is) The OpenShift -> New Application wizard is where I specifically noticed this blocking. It may be the only place. I don't know if others block, I just know that OpenShift takes some time, so other should be checked to make sure they can be put into the background.

            André Dietisheim added a comment - - edited

            Hard to know what you really mean here. All (beside maybe forgotten parts?) operations are executed in the background. Can you please be more precise when exactly you experience freezing in the OpenShift tooling and what tells you that the freeze you see is DNS related?. I dont see any freezing after completion of the application wizard.
            What version of the tooling are you using ("Affects Version")?

            André Dietisheim added a comment - - edited Hard to know what you really mean here. All (beside maybe forgotten parts?) operations are executed in the background. Can you please be more precise when exactly you experience freezing in the OpenShift tooling and what tells you that the freeze you see is DNS related?. I dont see any freezing after completion of the application wizard. What version of the tooling are you using ("Affects Version")?

              adietish@redhat.com André Dietisheim
              lincolnthree Lincoln Baxter III (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: