[JBoss JIRA] (JBIDE-22239) Allow a user to choose to permanently update their desired replicas for their deployment
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22239?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-22239:
---------------------------------------
Based on the original impl of how we support scaling I would expect:
* scale deployment config - updates DC and RC
* scale deployment/replication controller - updates only the rc
This would imply further changes to the DC will over-write any changes to the RC. But, this PR/issue may no longer be valid since the rework I added for #JBIDE-23030 which changes our scaling workflow to utilize the 'scale' endpoint over direct edit of a DC.
> Allow a user to choose to permanently update their desired replicas for their deployment
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-22239
> URL: https://issues.jboss.org/browse/JBIDE-22239
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Jeff Cantrill
> Assignee: Viacheslav Kabanovich
> Labels: openshift_v3
> Fix For: 4.4.1.Final
>
>
> When scaling, we should provide an option to a user who is scaling their deployment to update the deploymentconfig desired replias setting. Currently, if you scale the deployment in the explorer view or the replicationcontroller in the tabs view, image or config change triggers from a DC will set the replica count to whats defined their. Suggest:
> * Adding a custom dialog in the "..to.." option
> * Update to use a spinner
> * Add a checkbox to 'make the change perminent'
> * If checkbox=true, you should only need to update the dc if it has a configchange trigger.
> * Optionally show checkbox if unable to determine the dc associated with the deployment.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (JBIDE-23005) Server Adapter: Stuck on creating/publishing
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23005?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23005:
-------------------------------------
Fix Version/s: 4.4.2.AM1
(was: 4.4.1.Final)
> Server Adapter: Stuck on creating/publishing
> --------------------------------------------
>
> Key: JBIDE-23005
> URL: https://issues.jboss.org/browse/JBIDE-23005
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.2.AM1
>
> Attachments: stucked_server_adapter
>
>
> When I am trying to create a new OpenShift 3 server adapter, many times creation does not work. Server get stucked at publishing and there is a hanging job Check module status for server eap-app at OpenShift... I am using CDK OpenShift and build an application on eap 6.4 template with kitchensink context_dir. Connection is not established. While this is happening (job is hanging) there is no error in error log.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (JBIDE-22860) Application Wizard: Improve layout for templates
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22860?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22860:
-------------------------------------
Fix Version/s: 4.4.2.AM1
(was: 4.4.1.Final)
> Application Wizard: Improve layout for templates
> ------------------------------------------------
>
> Key: JBIDE-22860
> URL: https://issues.jboss.org/browse/JBIDE-22860
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Marián Labuda
> Assignee: Fred Bricon
> Priority: Minor
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.2.AM1
>
>
> In the New OpenShift Application wizard we have 2 tabs for a decision on what should a new application be based. One for server-template-based application (either from templates or builder images) and one for "Local template". Problem with local template is that it supports usage of URL templates - I can provide an URL of a template. This is not really local template. I think we should rename "Local template" tab to "Custom template" or something what would suggest usage of URLs as well as templates from local file system.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (JBIDE-22860) Application Wizard: Improve layout for templates
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22860?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22860:
-------------------------------------
Sprint: devex #120 September 2016 (was: devex #119 August 2016)
> Application Wizard: Improve layout for templates
> ------------------------------------------------
>
> Key: JBIDE-22860
> URL: https://issues.jboss.org/browse/JBIDE-22860
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Marián Labuda
> Assignee: Fred Bricon
> Priority: Minor
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.2.AM1
>
>
> In the New OpenShift Application wizard we have 2 tabs for a decision on what should a new application be based. One for server-template-based application (either from templates or builder images) and one for "Local template". Problem with local template is that it supports usage of URL templates - I can provide an URL of a template. This is not really local template. I think we should rename "Local template" tab to "Custom template" or something what would suggest usage of URLs as well as templates from local file system.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months
[JBoss JIRA] (JBIDE-22914) OpenShift Deployment: Deploy latest does not work correctly
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22914?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22914:
-------------------------------------
Fix Version/s: 4.4.2.AM1
(was: 4.4.1.Final)
> OpenShift Deployment: Deploy latest does not work correctly
> -----------------------------------------------------------
>
> Key: JBIDE-22914
> URL: https://issues.jboss.org/browse/JBIDE-22914
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Marián Labuda
> Labels: openshift_v3
> Fix For: 4.4.2.AM1
>
>
> When I have an application where no replication controller is yet and I want to deploy latest, I get following error:
> {code}
> Unable to perform a deployment for config hello-openshift
> com.openshift.restclient.NotFoundException: replicationcontrollers "hello-openshift-0" not found
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:105)
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:59)
> at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190)
> at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163)
> at okhttp3.RealCall.execute(RealCall.java:57)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:200)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:181)
> at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:269)
> at com.openshift.internal.restclient.capability.resources.DeployCapability.deploy(DeployCapability.java:59)
> at org.jboss.tools.openshift.internal.ui.handler.TriggerDeploymentHandler$1$1.visit(TriggerDeploymentHandler.java:90)
> at org.jboss.tools.openshift.internal.ui.handler.TriggerDeploymentHandler$1$1.visit(TriggerDeploymentHandler.java:1)
> at com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:91)
> at org.jboss.tools.openshift.internal.ui.handler.TriggerDeploymentHandler$1.doRun(TriggerDeploymentHandler.java:85)
> at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
> This is wrong, because it is trying to "deploy latest replication controller" instead of deploying latest deployment configuration (as it works e.g. from oc binary - deployment uses latest deployment configuration not replication controller which could be understood as instance of deployment configuration). Therefore if there is no replication controller and I click Deploy Latest in context menu of a service in OpenShift Explorer view or in context menu of a deployment configuration in properties view, I get the error.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
7 years, 10 months