[JBoss JIRA] (JBIDE-11419) Openshift event model
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11419?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-11419:
-------------------------------------
Priority: Minor (was: Major)
> Openshift event model
> ---------------------
>
> Key: JBIDE-11419
> URL: https://issues.jboss.org/browse/JBIDE-11419
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 3.3.0.Beta3
> Reporter: Rob Stryker
> Assignee: Xavier Coulon
> Priority: Minor
> Fix For: LATER
>
>
> An event model is needed so that interested listeners can know when applications are created / deleted, domains are changed, etc. This event model must be robust enough to survive workspace restarts in some fashion (not necessarily persissted...) It must provide listeners an opportunity to subscribe in some fashion without forcing a long-running remote load of the model.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (JBIDE-11419) Openshift event model
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11419?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-11419:
------------------------------------------
set to *LATER* since there are very little requirements that would justify that we go for this big change. Furthermore there's very little time and plenty of new features/existing bugs. In other words: low prio to me.
> Openshift event model
> ---------------------
>
> Key: JBIDE-11419
> URL: https://issues.jboss.org/browse/JBIDE-11419
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 3.3.0.Beta3
> Reporter: Rob Stryker
> Assignee: Xavier Coulon
> Fix For: LATER
>
>
> An event model is needed so that interested listeners can know when applications are created / deleted, domains are changed, etc. This event model must be robust enough to survive workspace restarts in some fashion (not necessarily persissted...) It must provide listeners an opportunity to subscribe in some fashion without forcing a long-running remote load of the model.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (JBIDE-11447) OpenShift java client: validate optional values when requesting
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11447?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-11447:
-------------------------------------
Fix Version/s: LATER
(was: 4.0.x)
> OpenShift java client: validate optional values when requesting
> ---------------------------------------------------------------
>
> Key: JBIDE-11447
> URL: https://issues.jboss.org/browse/JBIDE-11447
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 3.3.0.Beta3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: LATER
>
>
> The RestRequest class currently validates required parameters when it is told to request to the PaaS. It's still missing to validate optional values. We should add this validation.
> RestRequest#ensureRequiredParameters (currently marked with //TODO)
> RestRequest#validateOptionalParameters (currently marked with //TODO)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (JBIDE-11419) Openshift event model
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11419?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-11419:
-------------------------------------
Fix Version/s: LATER
(was: 4.0.x)
> Openshift event model
> ---------------------
>
> Key: JBIDE-11419
> URL: https://issues.jboss.org/browse/JBIDE-11419
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 3.3.0.Beta3
> Reporter: Rob Stryker
> Assignee: Xavier Coulon
> Fix For: LATER
>
>
> An event model is needed so that interested listeners can know when applications are created / deleted, domains are changed, etc. This event model must be robust enough to survive workspace restarts in some fashion (not necessarily persissted...) It must provide listeners an opportunity to subscribe in some fashion without forcing a long-running remote load of the model.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (JBIDE-11903) OpenShift Explorer: add Application start/stop/restart
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11903?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-11903:
-------------------------------------
Fix Version/s: 4.1.0.Alpha1
(was: 4.0.x)
> OpenShift Explorer: add Application start/stop/restart
> -------------------------------------------------------
>
> Key: JBIDE-11903
> URL: https://issues.jboss.org/browse/JBIDE-11903
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 3.3.0.Beta2
> Environment: Eclipse plugin
> Reporter: Nam Duong
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Alpha1
>
>
> The OpenShift Console view should contain controls for application start|stop|restart to match the functionality of the CLI. Currently, if you select Window->Show View->Others->OpenShift Express Console, then login in and select an application. The right-click menu doesn't have start|stop|restart so users have to either install the rhc client tools or ssh onto the OpenShift host gear.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (JBIDE-11881) Display application state in OpenShift Explorer and Properties view
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11881?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-11881:
-------------------------------------
Fix Version/s: 4.1.0.Alpha1
(was: 4.0.x)
> Display application state in OpenShift Explorer and Properties view
> -------------------------------------------------------------------
>
> Key: JBIDE-11881
> URL: https://issues.jboss.org/browse/JBIDE-11881
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 3.3.0.Beta3
> Reporter: Xavier Coulon
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Alpha1
>
>
> From Bugzilla#805989
> The state of the application on each gear can be checked using the gear_groups
> rest api.
> /broker/rest/domains/<domain-name>/applications/<app-name>/gear_groups
> This rest call reflects the state of the application on each gear based on the
> contents of the file $OPENSHIFT_GEAR_DIR/runtime/.state
> The following states should be tracked in ~/runtime/.state
> stopped
> building
> deploying
> started
> idle
> unknown
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months