You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Larry McCay (JIRA)" <ji...@apache.org> on 2014/09/26 01:23:34 UTC

[jira] [Commented] (KNOX-348) Deployment Time Topology Smoke Test

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

Larry McCay commented on KNOX-348:
----------------------------------

This could be driven from the ServiceRegistryService or the TopologyService - the topology service is the basis for the admin API - so probably make the most sense. This would be an interesting addition to the API.

> Deployment Time Topology Smoke Test
> -----------------------------------
>
>                 Key: KNOX-348
>                 URL: https://issues.apache.org/jira/browse/KNOX-348
>             Project: Apache Knox
>          Issue Type: Improvement
>          Components: Server
>            Reporter: Larry McCay
>             Fix For: 0.6.0
>
>
> At deployment time the accessibility of the services defined in the topology descriptor should be able to be verified.
> Based on some new config of the topology, the deployment machinery should enumerate the defined services and invoke some sanity check on the services directly. The results should be captured in a JSON file and persisted along side the topology or in a separate directory for these results.
> The results should be able to be accessed via browser as a dashboard and through an API that we expose for it.
> The tests should also be able to be run periodically and on demand in order to assess the health of the cluster's access through knox.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)