[JBoss JIRA] (JBIDE-23660) CDK Server adapter should have an option to configure stop command
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23660?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-23660:
-------------------------------------
According to the code, shutdown uses "vagrant halt", not vagrant destroy.
In fact, there's only 2 mentions of the term "destroy" anywhere in the CDK plugins, and that's just to destroy the "vagrant halt" process if the process takes too long to complete.
As far as I can tell, we never run vagrant destroy.
> CDK Server adapter should have an option to configure stop command
> ------------------------------------------------------------------
>
> Key: JBIDE-23660
> URL: https://issues.jboss.org/browse/JBIDE-23660
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: cdk
> Affects Versions: 4.4.2.Final
> Reporter: Ricardo Martinelli Oliveira
> Assignee: Rob Stryker
>
> CDK Server adapter lets configure the vagrant startup options. There should have an option to do the same in the stop.
> Why?
> It seems that CDK Server adapter uses _vagrant destroy_ to stop CDK, but using that option has its drawbacks, like for example:
> * If I'm stopping it to save resources, then I'm loosing all my job in it.
> * All images already pulled will be lost, so I cannot work offline
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23660) CDK Server adapter should have an option to configure stop command
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23660?page=com.atlassian.jira.plugi... ]
Rob Stryker reassigned JBIDE-23660:
-----------------------------------
Assignee: Rob Stryker
> CDK Server adapter should have an option to configure stop command
> ------------------------------------------------------------------
>
> Key: JBIDE-23660
> URL: https://issues.jboss.org/browse/JBIDE-23660
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: cdk
> Affects Versions: 4.4.2.Final
> Reporter: Ricardo Martinelli Oliveira
> Assignee: Rob Stryker
>
> CDK Server adapter lets configure the vagrant startup options. There should have an option to do the same in the stop.
> Why?
> It seems that CDK Server adapter uses _vagrant destroy_ to stop CDK, but using that option has its drawbacks, like for example:
> * If I'm stopping it to save resources, then I'm loosing all my job in it.
> * All images already pulled will be lost, so I cannot work offline
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23765) Scale To: deployment that is being scaled is not show in the scaling dialog
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23765?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-23765:
----------------------------------------
Assignee: Andre Dietisheim
> Scale To: deployment that is being scaled is not show in the scaling dialog
> ---------------------------------------------------------------------------
>
> Key: JBIDE-23765
> URL: https://issues.jboss.org/browse/JBIDE-23765
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.3.AM1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, scaling_pods_wizard
> Fix For: 4.4.3.AM2
>
> Attachments: scaling-deployment-dialog.png, scaling-deployment-eap.png
>
>
> The "Scale To" dialog, that you get when you pick "Scale > To" in the context menu of a service in the OpenShift Explorer (and also in the Properties) wont tell you what deployment you are about to scale.
> !scaling-deployment-dialog.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23765) Scale To: deployment that is being scaled is not show in the scaling dialog
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23765?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23765:
-------------------------------------
Labels: openshift_v3 scaling_pods_wizard (was: )
> Scale To: deployment that is being scaled is not show in the scaling dialog
> ---------------------------------------------------------------------------
>
> Key: JBIDE-23765
> URL: https://issues.jboss.org/browse/JBIDE-23765
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.3.AM1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, scaling_pods_wizard
> Fix For: 4.4.3.AM2
>
> Attachments: scaling-deployment-dialog.png, scaling-deployment-eap.png
>
>
> The "Scale To" dialog, that you get when you pick "Scale > To" in the context menu of a service in the OpenShift Explorer (and also in the Properties) wont tell you what deployment you are about to scale.
> !scaling-deployment-dialog.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23764) Scaling To: wong number of current replicas shown at times
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23764?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23764:
-------------------------------------
Labels: openshift_v3 scaling_pods_wizard (was: scaling_pods_wizard)
> Scaling To: wong number of current replicas shown at times
> ----------------------------------------------------------
>
> Key: JBIDE-23764
> URL: https://issues.jboss.org/browse/JBIDE-23764
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.AM1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, scaling_pods_wizard
> Fix For: 4.4.3.AM2
>
> Attachments: scale-to-dialog.png
>
>
> Even though I tried very hard I unfortunately cannot provide steps to replicate this erroneous behaviour. But it happened to me here and there.
> The tooling provides a way to have a specified number of pods for a service. This is available via the context menu of a service (and other items in the tree and in the properties).
> !scale-to-dialog.png!
> The dialog that allows you to scale the number of replicas to a specific number initially shows the current number of replicas. You can then provide a specific number of replicas that you want to have, enabling the "OK" button.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months