1 / 15

System Design and Deployment Status

System Design and Deployment Status. PDS Management Council Face-to-Face UCLA, Los Angeles, California November 28-29, 2012 Sean Hardman. Topics. Status Overall Build 3a Deployment Search Service Status Report Service Status Build 3b and Beyond Next Steps. Overall Status.

afia
Télécharger la présentation

System Design and Deployment Status

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. System Design and Deployment Status PDS Management Council Face-to-Face UCLA, Los Angeles, California November 28-29, 2012 Sean Hardman

  2. Topics • Status • Overall • Build 3a • Deployment • Search Service Status • Report Service Status • Build 3b and Beyond • Next Steps System Design and Deployment Update

  3. Overall Status • Validate software in place supporting validation of PDS4 labels using XML Schema and Schematron files. • Initial data access and transform software in place for working with PDS4 data. • Harvest and Registry software in place to support EN and Node registration of PDS3 and PDS4 data. • Search software in place supporting catalog-level search. • Report software in place waiting to be populated with web logs. System Design and Deployment Update

  4. Build 3a Status • Upgraded the Data Search interface to remove the dependence on the PDS3 catalog database. • Refactored the Search Service to better support PDS4. • Kept up with Information Model changes. • Added support for PDAP search protocol. • Initial support for PDS4 data transformation. • Correct issues discovered during Build 2c testing. System Design and Deployment Update

  5. Build 3a StatusDeployment • Engineering Node • Deployment of the core components replacing the central catalog. • Runningside-by-side with PDS3 system for six months. • Existing search interfaces reworked to utilize the PDS4 infrastructure. • Discipline Nodes • Phased deployment of the core components at the Nodes is in process. • Once deployment is complete, Nodes may begin local registration of their PDS4 test bundles. • PDS3 data sets/products may be registered as well. System Design and Deployment Update

  6. Build 3a DeploymentEngineering Node System Design and Deployment Update

  7. Build 3a DeploymentDiscipline Node System Design and Deployment Update

  8. Node Deployment Status • A couple of early adopters have tackled the installation. • Have received procedure/documentation suggestions and some RFAs. • Actively working with Atmospheres to install the software at their Node. • The other Nodes have been contacted to arrange installation. • Most were waiting for an updated RDD. • The RDD now includes the Node installation procedure. • http://pds-engineering.jpl.nasa.gov/pds2010/development/3.0.0/release/index-3.0.0.html System Design and Deployment Update

  9. Build 3a DeploymentPDS3/PDS4 Product Registration System Design and Deployment Update

  10. Search Service Status • PDS4 core infrastructure running at the PDS Engineering Node. • Working with the IPDA to register ESA data sets in search via PDAP protocol. • Working on some metadata quality issues before integration with operational search. • Worked with Atmospheres to register archive information web sites for Cassini and Phoenix data access. • Use demonstration process to affirm the architecture and then expand. System Design and Deployment Update

  11. Search Deployment Linkable Results Page Archive Pages Facet-Based Search System Design and Deployment Update

  12. Report Service Status • Sawmill software installed at the EN. • Upgraded to the latest version from the vendor. • Ready to pull log files from the Nodes and setting up a mechanism for push capability. • Planned operational phases: • Initiate population of the service and initial report configuration (December 2012). • Generate PDS-wide web log reports. (March 2013) • Generate registry-based reports. (October 2013) System Design and Deployment Update

  13. Build 3b and Beyond • Continue to support Information Model changes. • Add support for content validation. • Tune the Search Service index. • Add support for product-level search. • Develop initial Transport Service. • Add support for additional transformations. • Add support for package generation. • Integrate distribution and transformation capabilities. • Upgrade PDS web presence. System Design and Deployment Update

  14. Next Steps • Work with the Nodes on Report Service population. • Continue working with the Nodes to deploy Build 3a software locally. • Continue Build 3b development. • Align tool development with the tool plan System Design and Deployment Update

  15. Questions/Comments

More Related