[jbosstools-issues] [JBoss JIRA] (ERT-248) Improve UI for Docker reconnection use case [EBZ#495600]

[Friendly Jira Robot (JIRA)]

Friendly Jira Robot created ERT-248:
---------------------------------------

             Summary: Improve UI for Docker reconnection use case [EBZ#495600]
                 Key: ERT-248
                 URL: https://issues.jboss.org/browse/ERT-248
             Project: Eclipse Release Train
          Issue Type: Task
          Components: Linux Tools
            Reporter: Friendly Jira Robot


When a docker connection has been disabled, it's hard to make it work again. You need to click the Enable Connection button. This is not very user friendly.
Until today, I thought the connection was either active or inactive. But today I learnt it can also be disabled. In my opinion it's not practical to have a disabled state at all.

Let me describe the scenario I went through. I was using Container Development Kit which is a server adapter and once you start it, it will create a docker connection and connect to it - docker daemon is running inside CDK. But it would work the same way with a Docker Machine that you start, then stop, then start again.

1. Start CDK (once started, it will create a docker connection)
2. Docker connection is grey, but you can expand it.
3. Expand docker connection in docker explorer - it works - you can see images
4. Stop CDK
5. Now the refresher job will timeout, so the docker connection will be disabled
6. Start CDK again
Now I would expect to be able to work with the docker connection again like after the first start of CDK, but I can't, because now the connection has been disabled. So now I need to know that it's disabled and I need to enable it. I think it can be confusing for a lot of people - why do you need an additional step now?

The above steps could be reproduced with docker-machine. But instead of starting CDK, you would simply do "docker-machine start/stop default" from CLI.

I don't have an exact recipe on how this should be done. But I wonder if we need the disabled state at all. Because once a connection becomes inactive, it is no longer expanded, so it won't produce errors all the time. One issue is that if you had the Docker Images view opened at the same time, that one would probably keep trying to connect (if there was no such thing as a disabled docker connection). So I'm not sure how to solve this.

But the most important thing for me would be to make this use case (the steps above) more user friendly - i.e. make reconnection to a docker daemon a smoother experience.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)