oodt-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management
Date Fri, 14 Jul 2017 04:58:00 GMT

    [ https://issues.apache.org/jira/browse/OODT-945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16086866#comment-16086866
] 

ASF GitHub Bot commented on OODT-945:
-------------------------------------

Github user chrismattmann commented on the issue:

    https://github.com/apache/oodt/pull/44
  
    hi @IMS94 got further, but failing on unit tests, thoughts?
    
    ```
    -------------------------------------------------------
     T E S T S
    -------------------------------------------------------
    Running org.apache.oodt.config.distributed.DistributedConfigurationManagerTest
    log4j:WARN No appenders could be found for logger (org.apache.zookeeper.server.quorum.QuorumPeerConfig).
    log4j:WARN Please initialize the log4j system properly.
    Starting configuration publishing
    
    Processing commands for component : FILE_MANAGER
    Publishing configuration for : FILE_MANAGER
    Published configuration for : FILE_MANAGER
    
    
    Processing commands for component : RESOURCE_MANAGER
    Publishing configuration for : RESOURCE_MANAGER
    Published configuration for : RESOURCE_MANAGER
    
    Starting configuration publishing
    
    Processing commands for component : FILE_MANAGER
    Clearing configuration for : FILE_MANAGER
    Cleared configuration for : FILE_MANAGER
    
    
    Processing commands for component : RESOURCE_MANAGER
    Clearing configuration for : RESOURCE_MANAGER
    Cleared configuration for : RESOURCE_MANAGER
    
    Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.209 sec <<<
FAILURE! - in org.apache.oodt.config.distributed.DistributedConfigurationManagerTest
    loadConfigurationTest(org.apache.oodt.config.distributed.DistributedConfigurationManagerTest)
 Time elapsed: 0.049 sec  <<< FAILURE!
    java.lang.AssertionError: null
    	at org.junit.Assert.fail(Assert.java:86)
    	at org.junit.Assert.assertTrue(Assert.java:41)
    	at org.junit.Assert.assertTrue(Assert.java:52)
    	at org.apache.oodt.config.distributed.DistributedConfigurationManagerTest.loadConfigurationTest(DistributedConfigurationManagerTest.java:91)
    
    Running org.apache.oodt.config.distributed.DistributedConfigurationPublisherTest
    Starting configuration publishing
    
    Processing commands for component : FILE_MANAGER
    Publishing configuration for : FILE_MANAGER
    Published configuration for : FILE_MANAGER
    
    Verifying configuration for : FILE_MANAGER
    OK... Configuration verified
    Verified configuration for : FILE_MANAGER
    
    
    Processing commands for component : RESOURCE_MANAGER
    Publishing configuration for : RESOURCE_MANAGER
    Published configuration for : RESOURCE_MANAGER
    
    Verifying configuration for : RESOURCE_MANAGER
    OK... Configuration verified
    Verified configuration for : RESOURCE_MANAGER
    
    Starting configuration publishing
    
    Processing commands for component : FILE_MANAGER
    Clearing configuration for : FILE_MANAGER
    Cleared configuration for : FILE_MANAGER
    
    
    Processing commands for component : RESOURCE_MANAGER
    Clearing configuration for : RESOURCE_MANAGER
    Cleared configuration for : RESOURCE_MANAGER
    
    Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.512 sec - in org.apache.oodt.config.distributed.DistributedConfigurationPublisherTest
    
    Results :
    
    Failed tests: 
      DistributedConfigurationManagerTest.loadConfigurationTest:91 null
    
    Tests run: 2, Failures: 1, Errors: 0, Skipped: 0
    
    [INFO] ------------------------------------------------------------------------
    [INFO] Reactor Summary:
    [INFO] 
    [INFO] OODT Core .......................................... SUCCESS [  1.820 s]
    [INFO] Common Utilities ................................... SUCCESS [ 17.797 s]
    [INFO] CAS Command Line Interface ......................... SUCCESS [  6.046 s]
    [INFO] OODT - Configuration Management .................... FAILURE [  5.426 s]
    [INFO] Process Control System Input Data Package .......... SKIPPED
    [INFO] Catalog and Archive Service Generic Multi-valued Metadata Container SKIPPED
    [INFO] CAS Protocol ....................................... SKIPPED
    [INFO] CAS Protocol FTP Implementation .................... SKIPPED
    [INFO] CAS Protocol HTTP Implementation ................... SKIPPED
    [INFO] CAS Protocol IMAPS Implementation .................. SKIPPED
    [INFO] CAS Protocol SFTP Implementation ................... SKIPPED
    [INFO] Query Expression ................................... SKIPPED
    [INFO] OODT Single Sign On Security Package ............... SKIPPED
    [INFO] Catalog and Archive File Management Component ...... SKIPPED
    [INFO] OODT CAS Virtual Catalog and Integration Service. .. SKIPPED
    [INFO] Catalog and Archive Resource Management Component .. SKIPPED
    [INFO] Catalog and Archive Workflow Management Component .. SKIPPED
    [INFO] Catalog and Archive Crawling Framework ............. SKIPPED
    [INFO] CAS Curation Web Services .......................... SKIPPED
    [INFO] Process Control System Core Package ................ SKIPPED
    [INFO] OODT Wicket Web Components ......................... SKIPPED
    [INFO] CAS Curation Interface ............................. SKIPPED
    [INFO] CAS PGE Adaptor Framework .......................... SKIPPED
    [INFO] CAS Installer Maven Mojo ........................... SKIPPED
    [INFO] OODT :: Archetypes :: OpsUI ........................ SKIPPED
    [INFO] OODT :: Archetypes :: RADiX ........................ SKIPPED
    [INFO] OODT :: Archetypes ................................. SKIPPED
    [INFO] CAS Push-Pull-Framework ............................ SKIPPED
    [INFO] Product Service .................................... SKIPPED
    [INFO] Profile Service .................................... SKIPPED
    [INFO] OODT Web Grid ...................................... SKIPPED
    [INFO] XML-configured, DBMS-based Product and Profile Server SKIPPED
    [INFO] Apache OODT Configurable OPeNDAP Profile Server .... SKIPPED
    [INFO] CAS File Manager Browser Web App ................... SKIPPED
    [INFO] CAS Product Server Web Application ................. SKIPPED
    [INFO] CAS Workflow Manager Monitor Web App ............... SKIPPED
    [INFO] Catalog and Archive File Management Browser ........ SKIPPED
    [INFO] Catalog and Archive Workflow Management GUI Editor . SKIPPED
    [INFO] Process Control System Operator Interface Webapp ... SKIPPED
    [INFO] OODT Process Control System JAX-RS service layer ... SKIPPED
    [INFO] Apache OODT ........................................ SKIPPED
    [INFO] ------------------------------------------------------------------------
    [INFO] BUILD FAILURE
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 31.600 s
    [INFO] Finished at: 2017-07-13T15:38:14-07:00
    [INFO] Final Memory: 53M/480M
    [INFO] ------------------------------------------------------------------------
    [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.17:test
(default-test) on project oodt-conf: There are test failures.
    [ERROR] 
    [ERROR] Please refer to /Users/mattmann/git/oodt/config/target/surefire-reports for the
individual test results.
    [ERROR] -> [Help 1]
    [ERROR] 
    [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
    [ERROR] Re-run Maven using the -X switch to enable full debug logging.
    [ERROR] 
    [ERROR] For more information about the errors and possible solutions, please read the
following articles:
    [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
    [ERROR] 
    [ERROR] After correcting the problems, you can resume the build with the command
    [ERROR]   mvn <goals> -rf :oodt-conf
    LMC-053601:oodt mattmann$ 
    ```


> Rework OODT configuration to make use of  Zookeeper for distributed configuration management
> --------------------------------------------------------------------------------------------
>
>                 Key: OODT-945
>                 URL: https://issues.apache.org/jira/browse/OODT-945
>             Project: OODT
>          Issue Type: Bug
>            Reporter: Tom Barber
>            Assignee: Tom Barber
>              Labels: gsoc2017, mentor
>
> OODT is made up of a number of different components, each of which have their own set
of configuration files and locations. This is complex to manage and causes additional problems
when the platform requires distribution across servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an opional
Zookeeper module that would allow users to commission a zookeeper cluster and register the
various OODT components against it, which will allow the zookeeper cluster to maintain the
state of the various OODT components regardless of scale.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message