You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oodt.apache.org by "Chris A. Mattmann (JIRA)" <ji...@apache.org> on 2011/03/14 04:09:30 UTC
[jira] Created: (OODT-157) PCS Operator User Interface web
application
PCS Operator User Interface web application
-------------------------------------------
Key: OODT-157
URL: https://issues.apache.org/jira/browse/OODT-157
Project: OODT
Issue Type: Improvement
Components: crawler, file manager, pge wrapper framework, push pull framework, resource manager, workflow manager
Reporter: Chris A. Mattmann
Assignee: Chris A. Mattmann
Fix For: 0.3
We've got quite a nifty Operator User Interface web application at JPL that we'd like to contribute to the Apache OODT framework. We baked it up on OCO and used it on some other projects, including NPP Sounder PEATE (and SMAP, in progress). I'll attach some screenshots, but basically what it consists of is:
# A File Manager Browser webapp, with PCS trace enabled
# A Workflow Monitor webapp
# A PCS status monitor
# A PGE configuration/CAS configuration webapp
The existing version of this app is written is Struts and unfortunately is pretty messy at the moment. During this porting process, it's my proposal to:
# Port pcs/opsui to use Apache Wicket, a la OODT-155 and OODT-156
# depend on pcs/services to implement a Wicket-ized version of the PCS status monitor and the PCS trace functionality
# Overlay OODT-155 and OODT-156 on top of the webapp
# Port the PGE configuration/CAS configuration parts of the webapp to Wicket
Yes, this is another monster issue.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OODT-157) PCS Operator User Interface web
application
Posted by "Chris A. Mattmann (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13146453#comment-13146453 ]
Chris A. Mattmann commented on OODT-157:
----------------------------------------
In r1199374, I:
- added in the ganglia.url parameter as specified and flowed it through the [GANGLIA_URL] env var.
> PCS Operator User Interface web application
> -------------------------------------------
>
> Key: OODT-157
> URL: https://issues.apache.org/jira/browse/OODT-157
> Project: OODT
> Issue Type: Improvement
> Components: crawler, file manager, pge wrapper framework, push pull framework, resource manager, workflow manager
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Labels: interface, operator, pcs
> Fix For: 0.4
>
>
> We've got quite a nifty Operator User Interface web application at JPL that we'd like to contribute to the Apache OODT framework. We baked it up on OCO and used it on some other projects, including NPP Sounder PEATE (and SMAP, in progress). I'll attach some screenshots, but basically what it consists of is:
> # A File Manager Browser webapp, with PCS trace enabled
> # A Workflow Monitor webapp
> # A PCS status monitor
> # A PGE configuration/CAS configuration webapp
> The existing version of this app is written is Struts and unfortunately is pretty messy at the moment. During this porting process, it's my proposal to:
> # Port pcs/opsui to use Apache Wicket, a la OODT-155 and OODT-156
> # depend on pcs/services to implement a Wicket-ized version of the PCS status monitor and the PCS trace functionality
> # Overlay OODT-155 and OODT-156 on top of the webapp
> # Port the PGE configuration/CAS configuration parts of the webapp to Wicket
> Yes, this is another monster issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OODT-157) PCS Operator User Interface web
application
Posted by "Chris A. Mattmann (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13145856#comment-13145856 ]
Chris A. Mattmann commented on OODT-157:
----------------------------------------
In r1198964, I:
- finished the status page (show/hide, and sort/unsort all work now)
- cleaned up and refactored the status module
Up next:
- Resource monitor - pointer to Ganglia for now (will flow through via app context)
- Framing (skeletal stuff from OCO)
- PGE configuration pages (yes I'm nuts).
> PCS Operator User Interface web application
> -------------------------------------------
>
> Key: OODT-157
> URL: https://issues.apache.org/jira/browse/OODT-157
> Project: OODT
> Issue Type: Improvement
> Components: crawler, file manager, pge wrapper framework, push pull framework, resource manager, workflow manager
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Labels: interface, operator, pcs
> Fix For: 0.4
>
>
> We've got quite a nifty Operator User Interface web application at JPL that we'd like to contribute to the Apache OODT framework. We baked it up on OCO and used it on some other projects, including NPP Sounder PEATE (and SMAP, in progress). I'll attach some screenshots, but basically what it consists of is:
> # A File Manager Browser webapp, with PCS trace enabled
> # A Workflow Monitor webapp
> # A PCS status monitor
> # A PGE configuration/CAS configuration webapp
> The existing version of this app is written is Struts and unfortunately is pretty messy at the moment. During this porting process, it's my proposal to:
> # Port pcs/opsui to use Apache Wicket, a la OODT-155 and OODT-156
> # depend on pcs/services to implement a Wicket-ized version of the PCS status monitor and the PCS trace functionality
> # Overlay OODT-155 and OODT-156 on top of the webapp
> # Port the PGE configuration/CAS configuration parts of the webapp to Wicket
> Yes, this is another monster issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OODT-157) PCS Operator User Interface web
application
Posted by "Chris A. Mattmann (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13146790#comment-13146790 ]
Chris A. Mattmann commented on OODT-157:
----------------------------------------
In r1199621, I:
made the OPSUI totally skinnable, controlled by 2 parameters:
opsui.skin, currently can be "" blank, the default skin, or "classic", a throwback to the OCO OPSUI skin
opsui.homepage, should be set to a fully qualified class name of the Wicket Page class to use as the Home page link. In classic mode,
this should be set to org.apache.oodt.pcs.opsui.StatusPage
> PCS Operator User Interface web application
> -------------------------------------------
>
> Key: OODT-157
> URL: https://issues.apache.org/jira/browse/OODT-157
> Project: OODT
> Issue Type: Improvement
> Components: crawler, file manager, pge wrapper framework, push pull framework, resource manager, workflow manager
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Labels: interface, operator, pcs
> Fix For: 0.4
>
>
> We've got quite a nifty Operator User Interface web application at JPL that we'd like to contribute to the Apache OODT framework. We baked it up on OCO and used it on some other projects, including NPP Sounder PEATE (and SMAP, in progress). I'll attach some screenshots, but basically what it consists of is:
> # A File Manager Browser webapp, with PCS trace enabled
> # A Workflow Monitor webapp
> # A PCS status monitor
> # A PGE configuration/CAS configuration webapp
> The existing version of this app is written is Struts and unfortunately is pretty messy at the moment. During this porting process, it's my proposal to:
> # Port pcs/opsui to use Apache Wicket, a la OODT-155 and OODT-156
> # depend on pcs/services to implement a Wicket-ized version of the PCS status monitor and the PCS trace functionality
> # Overlay OODT-155 and OODT-156 on top of the webapp
> # Port the PGE configuration/CAS configuration parts of the webapp to Wicket
> Yes, this is another monster issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OODT-157) PCS Operator User Interface web
application
Posted by "Chris A. Mattmann (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13135182#comment-13135182 ]
Chris A. Mattmann commented on OODT-157:
----------------------------------------
In r1188753 and r1188755, I checked in a stub skeleton for the webapp. More work to come!
> PCS Operator User Interface web application
> -------------------------------------------
>
> Key: OODT-157
> URL: https://issues.apache.org/jira/browse/OODT-157
> Project: OODT
> Issue Type: Improvement
> Components: crawler, file manager, pge wrapper framework, push pull framework, resource manager, workflow manager
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Labels: interface, operator, pcs
> Fix For: 0.4
>
>
> We've got quite a nifty Operator User Interface web application at JPL that we'd like to contribute to the Apache OODT framework. We baked it up on OCO and used it on some other projects, including NPP Sounder PEATE (and SMAP, in progress). I'll attach some screenshots, but basically what it consists of is:
> # A File Manager Browser webapp, with PCS trace enabled
> # A Workflow Monitor webapp
> # A PCS status monitor
> # A PGE configuration/CAS configuration webapp
> The existing version of this app is written is Struts and unfortunately is pretty messy at the moment. During this porting process, it's my proposal to:
> # Port pcs/opsui to use Apache Wicket, a la OODT-155 and OODT-156
> # depend on pcs/services to implement a Wicket-ized version of the PCS status monitor and the PCS trace functionality
> # Overlay OODT-155 and OODT-156 on top of the webapp
> # Port the PGE configuration/CAS configuration parts of the webapp to Wicket
> Yes, this is another monster issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OODT-157) PCS Operator User Interface web
application
Posted by "Chris A. Mattmann (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13145207#comment-13145207 ]
Chris A. Mattmann commented on OODT-157:
----------------------------------------
In r1198618 and r1198619 I:
- integrated the wmonitor component into the app
- refactored and clean up app passing and bread crumbs
- mostly finished the status page
> PCS Operator User Interface web application
> -------------------------------------------
>
> Key: OODT-157
> URL: https://issues.apache.org/jira/browse/OODT-157
> Project: OODT
> Issue Type: Improvement
> Components: crawler, file manager, pge wrapper framework, push pull framework, resource manager, workflow manager
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Labels: interface, operator, pcs
> Fix For: 0.4
>
>
> We've got quite a nifty Operator User Interface web application at JPL that we'd like to contribute to the Apache OODT framework. We baked it up on OCO and used it on some other projects, including NPP Sounder PEATE (and SMAP, in progress). I'll attach some screenshots, but basically what it consists of is:
> # A File Manager Browser webapp, with PCS trace enabled
> # A Workflow Monitor webapp
> # A PCS status monitor
> # A PGE configuration/CAS configuration webapp
> The existing version of this app is written is Struts and unfortunately is pretty messy at the moment. During this porting process, it's my proposal to:
> # Port pcs/opsui to use Apache Wicket, a la OODT-155 and OODT-156
> # depend on pcs/services to implement a Wicket-ized version of the PCS status monitor and the PCS trace functionality
> # Overlay OODT-155 and OODT-156 on top of the webapp
> # Port the PGE configuration/CAS configuration parts of the webapp to Wicket
> Yes, this is another monster issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OODT-157) PCS Operator User Interface web
application
Posted by "Chris A. Mattmann (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147529#comment-13147529 ]
Chris A. Mattmann commented on OODT-157:
----------------------------------------
In r1200194 and in r1200195, I:
- refactored the Health Monitor into a webapp/components widget for reuse
- cleaned up some of the style/skin for classic
> PCS Operator User Interface web application
> -------------------------------------------
>
> Key: OODT-157
> URL: https://issues.apache.org/jira/browse/OODT-157
> Project: OODT
> Issue Type: Improvement
> Components: crawler, file manager, pge wrapper framework, push pull framework, resource manager, workflow manager
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Labels: interface, operator, pcs
> Fix For: 0.4
>
>
> We've got quite a nifty Operator User Interface web application at JPL that we'd like to contribute to the Apache OODT framework. We baked it up on OCO and used it on some other projects, including NPP Sounder PEATE (and SMAP, in progress). I'll attach some screenshots, but basically what it consists of is:
> # A File Manager Browser webapp, with PCS trace enabled
> # A Workflow Monitor webapp
> # A PCS status monitor
> # A PGE configuration/CAS configuration webapp
> The existing version of this app is written is Struts and unfortunately is pretty messy at the moment. During this porting process, it's my proposal to:
> # Port pcs/opsui to use Apache Wicket, a la OODT-155 and OODT-156
> # depend on pcs/services to implement a Wicket-ized version of the PCS status monitor and the PCS trace functionality
> # Overlay OODT-155 and OODT-156 on top of the webapp
> # Port the PGE configuration/CAS configuration parts of the webapp to Wicket
> Yes, this is another monster issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OODT-157) PCS Operator User Interface web
application
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann updated OODT-157:
-----------------------------------
Fix Version/s: (was: 0.5)
0.4
> PCS Operator User Interface web application
> -------------------------------------------
>
> Key: OODT-157
> URL: https://issues.apache.org/jira/browse/OODT-157
> Project: OODT
> Issue Type: Improvement
> Components: crawler, file manager, pge wrapper framework, push pull framework, resource manager, workflow manager
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Labels: interface, operator, pcs
> Fix For: 0.4
>
>
> We've got quite a nifty Operator User Interface web application at JPL that we'd like to contribute to the Apache OODT framework. We baked it up on OCO and used it on some other projects, including NPP Sounder PEATE (and SMAP, in progress). I'll attach some screenshots, but basically what it consists of is:
> # A File Manager Browser webapp, with PCS trace enabled
> # A Workflow Monitor webapp
> # A PCS status monitor
> # A PGE configuration/CAS configuration webapp
> The existing version of this app is written is Struts and unfortunately is pretty messy at the moment. During this porting process, it's my proposal to:
> # Port pcs/opsui to use Apache Wicket, a la OODT-155 and OODT-156
> # depend on pcs/services to implement a Wicket-ized version of the PCS status monitor and the PCS trace functionality
> # Overlay OODT-155 and OODT-156 on top of the webapp
> # Port the PGE configuration/CAS configuration parts of the webapp to Wicket
> Yes, this is another monster issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (OODT-157) PCS Operator User Interface web
application
Posted by "Chris A. Mattmann (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann resolved OODT-157.
------------------------------------
Resolution: Fixed
OK, I'm calling this done for 0.4! Thanks to everyone ([~ahart], [~cgoodale], and [~pramirez]) for helping make it awesome!
I'll open up a new issue for 0.5 to finish the config pages.
> PCS Operator User Interface web application
> -------------------------------------------
>
> Key: OODT-157
> URL: https://issues.apache.org/jira/browse/OODT-157
> Project: OODT
> Issue Type: Improvement
> Components: crawler, file manager, pge wrapper framework, push pull framework, resource manager, workflow manager
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Labels: interface, operator, pcs
> Fix For: 0.4
>
>
> We've got quite a nifty Operator User Interface web application at JPL that we'd like to contribute to the Apache OODT framework. We baked it up on OCO and used it on some other projects, including NPP Sounder PEATE (and SMAP, in progress). I'll attach some screenshots, but basically what it consists of is:
> # A File Manager Browser webapp, with PCS trace enabled
> # A Workflow Monitor webapp
> # A PCS status monitor
> # A PGE configuration/CAS configuration webapp
> The existing version of this app is written is Struts and unfortunately is pretty messy at the moment. During this porting process, it's my proposal to:
> # Port pcs/opsui to use Apache Wicket, a la OODT-155 and OODT-156
> # depend on pcs/services to implement a Wicket-ized version of the PCS status monitor and the PCS trace functionality
> # Overlay OODT-155 and OODT-156 on top of the webapp
> # Port the PGE configuration/CAS configuration parts of the webapp to Wicket
> Yes, this is another monster issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OODT-157) PCS Operator User Interface web
application
Posted by "Chris A. Mattmann (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153980#comment-13153980 ]
Chris A. Mattmann commented on OODT-157:
----------------------------------------
In r1204348 and r1204352 I started to add in the config pages for FM, WM, RM and PGE config.
> PCS Operator User Interface web application
> -------------------------------------------
>
> Key: OODT-157
> URL: https://issues.apache.org/jira/browse/OODT-157
> Project: OODT
> Issue Type: Improvement
> Components: crawler, file manager, pge wrapper framework, push pull framework, resource manager, workflow manager
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Labels: interface, operator, pcs
> Fix For: 0.4
>
>
> We've got quite a nifty Operator User Interface web application at JPL that we'd like to contribute to the Apache OODT framework. We baked it up on OCO and used it on some other projects, including NPP Sounder PEATE (and SMAP, in progress). I'll attach some screenshots, but basically what it consists of is:
> # A File Manager Browser webapp, with PCS trace enabled
> # A Workflow Monitor webapp
> # A PCS status monitor
> # A PGE configuration/CAS configuration webapp
> The existing version of this app is written is Struts and unfortunately is pretty messy at the moment. During this porting process, it's my proposal to:
> # Port pcs/opsui to use Apache Wicket, a la OODT-155 and OODT-156
> # depend on pcs/services to implement a Wicket-ized version of the PCS status monitor and the PCS trace functionality
> # Overlay OODT-155 and OODT-156 on top of the webapp
> # Port the PGE configuration/CAS configuration parts of the webapp to Wicket
> Yes, this is another monster issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OODT-157) PCS Operator User Interface web
application
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann updated OODT-157:
-----------------------------------
Fix Version/s: (was: 0.3)
0.4
- coming at you in 0.4
> PCS Operator User Interface web application
> -------------------------------------------
>
> Key: OODT-157
> URL: https://issues.apache.org/jira/browse/OODT-157
> Project: OODT
> Issue Type: Improvement
> Components: crawler, file manager, pge wrapper framework, push pull framework, resource manager, workflow manager
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Labels: interface, operator, pcs
> Fix For: 0.4
>
>
> We've got quite a nifty Operator User Interface web application at JPL that we'd like to contribute to the Apache OODT framework. We baked it up on OCO and used it on some other projects, including NPP Sounder PEATE (and SMAP, in progress). I'll attach some screenshots, but basically what it consists of is:
> # A File Manager Browser webapp, with PCS trace enabled
> # A Workflow Monitor webapp
> # A PCS status monitor
> # A PGE configuration/CAS configuration webapp
> The existing version of this app is written is Struts and unfortunately is pretty messy at the moment. During this porting process, it's my proposal to:
> # Port pcs/opsui to use Apache Wicket, a la OODT-155 and OODT-156
> # depend on pcs/services to implement a Wicket-ized version of the PCS status monitor and the PCS trace functionality
> # Overlay OODT-155 and OODT-156 on top of the webapp
> # Port the PGE configuration/CAS configuration parts of the webapp to Wicket
> Yes, this is another monster issue.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OODT-157) PCS Operator User Interface web
application
Posted by "Chris A. Mattmann (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152631#comment-13152631 ]
Chris A. Mattmann commented on OODT-157:
----------------------------------------
In r1203482, I:
* overlayed cas-product web services into app
* exposed /data and /dataset web services (RDF and RSS don't work b/c they require confs that I'm not baking in or assuming existence of as of yet).
* updated TraceableProductBrowser to link to ctxRoot/data?productID=<productId>
> PCS Operator User Interface web application
> -------------------------------------------
>
> Key: OODT-157
> URL: https://issues.apache.org/jira/browse/OODT-157
> Project: OODT
> Issue Type: Improvement
> Components: crawler, file manager, pge wrapper framework, push pull framework, resource manager, workflow manager
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Labels: interface, operator, pcs
> Fix For: 0.4
>
>
> We've got quite a nifty Operator User Interface web application at JPL that we'd like to contribute to the Apache OODT framework. We baked it up on OCO and used it on some other projects, including NPP Sounder PEATE (and SMAP, in progress). I'll attach some screenshots, but basically what it consists of is:
> # A File Manager Browser webapp, with PCS trace enabled
> # A Workflow Monitor webapp
> # A PCS status monitor
> # A PGE configuration/CAS configuration webapp
> The existing version of this app is written is Struts and unfortunately is pretty messy at the moment. During this porting process, it's my proposal to:
> # Port pcs/opsui to use Apache Wicket, a la OODT-155 and OODT-156
> # depend on pcs/services to implement a Wicket-ized version of the PCS status monitor and the PCS trace functionality
> # Overlay OODT-155 and OODT-156 on top of the webapp
> # Port the PGE configuration/CAS configuration parts of the webapp to Wicket
> Yes, this is another monster issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OODT-157) PCS Operator User Interface web
application
Posted by "Chris A. Mattmann (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152620#comment-13152620 ]
Chris A. Mattmann commented on OODT-157:
----------------------------------------
In r1203476 I:
- added 2 properties to the context.xml config:
{noformat}
org.apache.oodt.pcs.trace.excludeList
org.apache.oodt.pcs.trace.enableNotCat
{noformat}
* org.apache.oodt.pcs.trace.excludeList - A comma separated list of product type *name*s to exclude from the Trace. This has been useful in situations where there are products that have TONs of recursive dependencies to search through and you just want to speed up your traces.
* org.apache.oodt.pcs.trace.enableNotCat - This enables products that aren't cataloged in the FM to be included in a PCS trace tree. This is useful in the situation where you have e.g., a met extractor config file that's been included in either the InputFiles or OutputFiles met key, but that hasn't been cataloged in FM.
> PCS Operator User Interface web application
> -------------------------------------------
>
> Key: OODT-157
> URL: https://issues.apache.org/jira/browse/OODT-157
> Project: OODT
> Issue Type: Improvement
> Components: crawler, file manager, pge wrapper framework, push pull framework, resource manager, workflow manager
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Labels: interface, operator, pcs
> Fix For: 0.4
>
>
> We've got quite a nifty Operator User Interface web application at JPL that we'd like to contribute to the Apache OODT framework. We baked it up on OCO and used it on some other projects, including NPP Sounder PEATE (and SMAP, in progress). I'll attach some screenshots, but basically what it consists of is:
> # A File Manager Browser webapp, with PCS trace enabled
> # A Workflow Monitor webapp
> # A PCS status monitor
> # A PGE configuration/CAS configuration webapp
> The existing version of this app is written is Struts and unfortunately is pretty messy at the moment. During this porting process, it's my proposal to:
> # Port pcs/opsui to use Apache Wicket, a la OODT-155 and OODT-156
> # depend on pcs/services to implement a Wicket-ized version of the PCS status monitor and the PCS trace functionality
> # Overlay OODT-155 and OODT-156 on top of the webapp
> # Port the PGE configuration/CAS configuration parts of the webapp to Wicket
> Yes, this is another monster issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OODT-157) PCS Operator User Interface web
application
Posted by "Chris A. Mattmann (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144090#comment-13144090 ]
Chris A. Mattmann commented on OODT-157:
----------------------------------------
More progress in r1197617.
- PCS status page skinned and controller almost done
- refactored and flow through props via application object.
> PCS Operator User Interface web application
> -------------------------------------------
>
> Key: OODT-157
> URL: https://issues.apache.org/jira/browse/OODT-157
> Project: OODT
> Issue Type: Improvement
> Components: crawler, file manager, pge wrapper framework, push pull framework, resource manager, workflow manager
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Labels: interface, operator, pcs
> Fix For: 0.4
>
>
> We've got quite a nifty Operator User Interface web application at JPL that we'd like to contribute to the Apache OODT framework. We baked it up on OCO and used it on some other projects, including NPP Sounder PEATE (and SMAP, in progress). I'll attach some screenshots, but basically what it consists of is:
> # A File Manager Browser webapp, with PCS trace enabled
> # A Workflow Monitor webapp
> # A PCS status monitor
> # A PGE configuration/CAS configuration webapp
> The existing version of this app is written is Struts and unfortunately is pretty messy at the moment. During this porting process, it's my proposal to:
> # Port pcs/opsui to use Apache Wicket, a la OODT-155 and OODT-156
> # depend on pcs/services to implement a Wicket-ized version of the PCS status monitor and the PCS trace functionality
> # Overlay OODT-155 and OODT-156 on top of the webapp
> # Port the PGE configuration/CAS configuration parts of the webapp to Wicket
> Yes, this is another monster issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OODT-157) PCS Operator User Interface web
application
Posted by "Chris A. Mattmann (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13141691#comment-13141691 ]
Chris A. Mattmann commented on OODT-157:
----------------------------------------
Made some progress towards this in r1196327.
Now have:
* a file manager browser widget dropped in
* working on wwmonitor
* have started ported the opsui header template
TODO:
* rest of the OPSUI template
* pcs_status page
* pcs_trace functionality tied in to product view
* product download tied into product view
* login tied to CAS-SSO
> PCS Operator User Interface web application
> -------------------------------------------
>
> Key: OODT-157
> URL: https://issues.apache.org/jira/browse/OODT-157
> Project: OODT
> Issue Type: Improvement
> Components: crawler, file manager, pge wrapper framework, push pull framework, resource manager, workflow manager
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Labels: interface, operator, pcs
> Fix For: 0.4
>
>
> We've got quite a nifty Operator User Interface web application at JPL that we'd like to contribute to the Apache OODT framework. We baked it up on OCO and used it on some other projects, including NPP Sounder PEATE (and SMAP, in progress). I'll attach some screenshots, but basically what it consists of is:
> # A File Manager Browser webapp, with PCS trace enabled
> # A Workflow Monitor webapp
> # A PCS status monitor
> # A PGE configuration/CAS configuration webapp
> The existing version of this app is written is Struts and unfortunately is pretty messy at the moment. During this porting process, it's my proposal to:
> # Port pcs/opsui to use Apache Wicket, a la OODT-155 and OODT-156
> # depend on pcs/services to implement a Wicket-ized version of the PCS status monitor and the PCS trace functionality
> # Overlay OODT-155 and OODT-156 on top of the webapp
> # Port the PGE configuration/CAS configuration parts of the webapp to Wicket
> Yes, this is another monster issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OODT-157) PCS Operator User Interface web
application
Posted by "Chris A. Mattmann (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152632#comment-13152632 ]
Chris A. Mattmann commented on OODT-157:
----------------------------------------
OK, all checklist items are done *except for*
- Configuration tab.
I'll work on this next. Hopefully will have the whole app done in the next week so I can move back to finishing OODT-215.
> PCS Operator User Interface web application
> -------------------------------------------
>
> Key: OODT-157
> URL: https://issues.apache.org/jira/browse/OODT-157
> Project: OODT
> Issue Type: Improvement
> Components: crawler, file manager, pge wrapper framework, push pull framework, resource manager, workflow manager
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Labels: interface, operator, pcs
> Fix For: 0.4
>
>
> We've got quite a nifty Operator User Interface web application at JPL that we'd like to contribute to the Apache OODT framework. We baked it up on OCO and used it on some other projects, including NPP Sounder PEATE (and SMAP, in progress). I'll attach some screenshots, but basically what it consists of is:
> # A File Manager Browser webapp, with PCS trace enabled
> # A Workflow Monitor webapp
> # A PCS status monitor
> # A PGE configuration/CAS configuration webapp
> The existing version of this app is written is Struts and unfortunately is pretty messy at the moment. During this porting process, it's my proposal to:
> # Port pcs/opsui to use Apache Wicket, a la OODT-155 and OODT-156
> # depend on pcs/services to implement a Wicket-ized version of the PCS status monitor and the PCS trace functionality
> # Overlay OODT-155 and OODT-156 on top of the webapp
> # Port the PGE configuration/CAS configuration parts of the webapp to Wicket
> Yes, this is another monster issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OODT-157) PCS Operator User Interface web
application
Posted by "Chris A. Mattmann (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13146368#comment-13146368 ]
Chris A. Mattmann commented on OODT-157:
----------------------------------------
In r1199296 and r1199300, I:
- made the OPSUI skinnable
- provided a _classic skin that resembles the 2007 OCO original Operator Interface
In my next revisions I'll:
- include a ganglia.url parameter to link to ganglia via the resource monitor link. I'll map this to the ENV VAR [GANGLIA_URL]
- add a new component for PCS trace functionality and attach it to the File Manager product browser
- overlay the fmprod app and provide a download link for products
- create the Configuration views and modules and link them to the Configuration tab link
> PCS Operator User Interface web application
> -------------------------------------------
>
> Key: OODT-157
> URL: https://issues.apache.org/jira/browse/OODT-157
> Project: OODT
> Issue Type: Improvement
> Components: crawler, file manager, pge wrapper framework, push pull framework, resource manager, workflow manager
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Labels: interface, operator, pcs
> Fix For: 0.4
>
>
> We've got quite a nifty Operator User Interface web application at JPL that we'd like to contribute to the Apache OODT framework. We baked it up on OCO and used it on some other projects, including NPP Sounder PEATE (and SMAP, in progress). I'll attach some screenshots, but basically what it consists of is:
> # A File Manager Browser webapp, with PCS trace enabled
> # A Workflow Monitor webapp
> # A PCS status monitor
> # A PGE configuration/CAS configuration webapp
> The existing version of this app is written is Struts and unfortunately is pretty messy at the moment. During this porting process, it's my proposal to:
> # Port pcs/opsui to use Apache Wicket, a la OODT-155 and OODT-156
> # depend on pcs/services to implement a Wicket-ized version of the PCS status monitor and the PCS trace functionality
> # Overlay OODT-155 and OODT-156 on top of the webapp
> # Port the PGE configuration/CAS configuration parts of the webapp to Wicket
> Yes, this is another monster issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OODT-157) PCS Operator User Interface web
application
Posted by "Chris A. Mattmann (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13151874#comment-13151874 ]
Chris A. Mattmann commented on OODT-157:
----------------------------------------
In r1203082, I:
- exposed the PCS trace component
- added a Trace component in webapp/components
- exposed the Trace component as an upstream and downstream pedigree tree
- extended the ProductBrowser component into a TraceableProductBrowser, exposing the Trace button to generate the tree.
> PCS Operator User Interface web application
> -------------------------------------------
>
> Key: OODT-157
> URL: https://issues.apache.org/jira/browse/OODT-157
> Project: OODT
> Issue Type: Improvement
> Components: crawler, file manager, pge wrapper framework, push pull framework, resource manager, workflow manager
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Labels: interface, operator, pcs
> Fix For: 0.4
>
>
> We've got quite a nifty Operator User Interface web application at JPL that we'd like to contribute to the Apache OODT framework. We baked it up on OCO and used it on some other projects, including NPP Sounder PEATE (and SMAP, in progress). I'll attach some screenshots, but basically what it consists of is:
> # A File Manager Browser webapp, with PCS trace enabled
> # A Workflow Monitor webapp
> # A PCS status monitor
> # A PGE configuration/CAS configuration webapp
> The existing version of this app is written is Struts and unfortunately is pretty messy at the moment. During this porting process, it's my proposal to:
> # Port pcs/opsui to use Apache Wicket, a la OODT-155 and OODT-156
> # depend on pcs/services to implement a Wicket-ized version of the PCS status monitor and the PCS trace functionality
> # Overlay OODT-155 and OODT-156 on top of the webapp
> # Port the PGE configuration/CAS configuration parts of the webapp to Wicket
> Yes, this is another monster issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira