[JBoss JIRA] (JBIDE-21652) We should make OS 3 application status more visible for users
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21652?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21652:
------------------------------------------
[~fbricon] do we have a CR2 in our planing? I want to postpone this to CR2 or if there's none to 4.4.0.Alpha1.
> We should make OS 3 application status more visible for users
> -------------------------------------------------------------
>
> Key: JBIDE-21652
> URL: https://issues.jboss.org/browse/JBIDE-21652
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Alexey Kazakov
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> Currently it can be confusing for users when an application is not available because it's building.
> We should think about our options, how we could improve visibility of the application status in both OS Explorer and Servers view (for OS server adapters).
> For example we could add a status line for an "application" node (or even for a project?) and show "Building..." or something if any of its services is building. We also could use a red font for such statuses. An gif icon would be ideal but I'm not sure it's technically possible.
> OS Server adapter is a separate story but we need to add status for it too. Maybe it's worth a separate issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21082) Application wizard opens when not logged to Openshift
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21082?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21082:
------------------------------------------
[~scabanovich] is this something you could tackle?
> Application wizard opens when not logged to Openshift
> -----------------------------------------------------
>
> Key: JBIDE-21082
> URL: https://issues.jboss.org/browse/JBIDE-21082
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Jan Richter
> Assignee: Andre Dietisheim
> Labels: application_wizard, openshift_v3
> Fix For: 4.3.1.CR1
>
>
> Creating new application on a connection where I'm not logged in results in the following:
> First it opens an error dialog (which looks fine):
> {noformat}
> An internal error occurred during: "Loading projects, templates...".
> Could not list Project resources in namespace : javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
> {noformat}
> And then it opens the application wizard anyway.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-20513) tricky to login to openshift when token expires
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20513?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-20513:
------------------------------------------
a) I have to renew my token in oc every 24h as I have to in Eclipse. [~jcantrill] can you confirm?
b) I agree, the dialog should tell the user that the token expired and he has to get a new one
Refreshing pops up the login dialog for me. But yes, I agree, the user should be able to get the auth dialog in a more obvious way than with a refresh: context-menu? [~fbricon]?
> tricky to login to openshift when token expires
> -----------------------------------------------
>
> Key: JBIDE-20513
> URL: https://issues.jboss.org/browse/JBIDE-20513
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Max Rydahl Andersen
> Priority: Critical
> Fix For: 4.3.1.CR1
>
>
> I logged in with token.
> 24hrs later I start eclipse and expand the connection in explorer
> expecting to just login.
> Here is what happens instead:
> a) info message (not error) is logged to error log hiding the explorer view
> b) after some seconds (seems there is a timeout) a login dialog comes up saying I need to sign in (no clear info that auth failed or token missing etc.).
> cancel the dialog since I'm trying to figure out what happened.
> c) Now the explorer just shows "You must obtain API token by visiting ..." as child and I cannot see straightforward way to log in again.
> Turns out Refresh does trigger login again.
> meanwhile command line 'oc' seem to be fine at logging in with token older than 24 hrs...can't verify that though, but in any case:
> a) do a user really need to re-login every 24 hours ?
> b) the error handling/dialogs shown are not very informative
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21634) Explorer, Properties: Allow a user to scale their deployment
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21634?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21634:
------------------------------------------
[~jcantrill][~fbricon] this seems like a quite important issue we should tackle for CR1? Scaling matters for debugging.
> Explorer, Properties: Allow a user to scale their deployment
> ------------------------------------------------------------
>
> Key: JBIDE-21634
> URL: https://issues.jboss.org/browse/JBIDE-21634
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Jeff Cantrill
> Labels: explorer, openshift_v3, properties
> Fix For: 4.3.1.CR1
>
>
> The web and cli allows a user to scale their deployments, which is only possible now in Eclipse by editing the replicationcontroller. Add UI to facilitate scaling. Scaling should be allowed in some sort of context menu when selecting any of:
> 1. deployment (replication controller)
> 2. eclipse view of a deployment (server) -> walk back to the currrent deployment
> 3. pod -> walk back to the current deployment
> updating 'spec.replicas' causes a new pods to spin up
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21490) Enforce non empty git source parameter in templates
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21490?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21490:
------------------------------------------
[~scabanovich] is this small issue something you could tackle?
> Enforce non empty git source parameter in templates
> ---------------------------------------------------
>
> Key: JBIDE-21490
> URL: https://issues.jboss.org/browse/JBIDE-21490
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Fix For: 4.3.1.CR1
>
>
> Following JBIDE-21340, we need to add validation of required git source parameter property in ParameterListPage.
> To find out what parameter is the git repository url you'd do:
> {code}
> public String getGitRepoParameterKey() {
> ITemplate template = model.getSelectedTemplate();
> if (template != null) {
> for(String key : new String[]{"SOURCE_REPOSITORY_URL", "GIT_URI"}) {
> if (template.getParameters().containsKey(key)) {
> return key;
> }
> }
> }
> return null;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month