You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/07/23 20:59:39 UTC
[jira] [Commented] (KNOX-349) Knox API for Topology Management
[ https://issues.apache.org/jira/browse/KNOX-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14072146#comment-14072146 ]
ASF subversion and git services commented on KNOX-349:
------------------------------------------------------
Commit 5169480b3e09d900e32ed0e429a84974209c466b in knox's branch refs/heads/master from [~kevin.minder]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=5169480 ]
KNOX-349: Knox API for Topology Management. Initial step only supports GETs for topologies collection and single topology.
> Knox API for Topology Management
> --------------------------------
>
> Key: KNOX-349
> URL: https://issues.apache.org/jira/browse/KNOX-349
> Project: Apache Knox
> Issue Type: Sub-task
> Components: ClientDSL, KnoxCLI, Server
> Reporter: Larry McCay
> Fix For: 0.5.0
>
> Attachments: KNOX-349.patch
>
>
> Cluster topology deployments must be manageable by a Knox API:
> GET all deployed topologies
> GET specifics about a single topology
> GET smoke test results for topology
> PUT new topology to deploy
> POST update topology
> POST update topology smoke test results
> DELETE topology - undeploy
> DELETE all topologies - undeploy all
--
This message was sent by Atlassian JIRA
(v6.2#6252)