[jboss-jira] [JBoss JIRA] (AS7-713) Persist named rollout plans for reuse by clients

[Brian Stansberry (Updated) (JIRA)]

     [ https://issues.jboss.org/browse/AS7-713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry updated AS7-713:
---------------------------------

    Attachment: AS7-713.txt


Attached file is a quasi example.

It shows the description of the API and then some examples of using it to store/retrieve/modify/remove a rollout plan (which is just a chunk of DMR.)

It's a quasi-example because the rollout plan example I was using isn't valid; the in-series=>[] bit needs content between the []. As of today using that example will fail as Alexey added validation of the plan.

See bottom of http://community.jboss.org/docs/DOC-16336 for details on the proper structure for a rollout plan.

This JIRA is for the server-side work to be able to take the rollout plan DMR and persist it and retrieve it for future use.

Alexey is working on:

1) Easier CLI syntax for creating a rollout plan and associating it with any low level operation.

2) Ability to associate the *name* of a previously persisted rollout plan with an operation, rather than the full plan DMR. Saves the client having to read the plan using the :read-resource or :read-attribute like I did in the attached. Instead they just add a header to the operation referencing the rollout plan by name.
                
> Persist named rollout plans for reuse by clients
> ------------------------------------------------
>
>                 Key: AS7-713
>                 URL: https://issues.jboss.org/browse/AS7-713
>             Project: Application Server 7
>          Issue Type: Feature Request
>          Components: Domain Management
>            Reporter: Max Rydahl Andersen
>            Assignee: Brian Stansberry
>             Fix For: 7.1.0.CR1
>
>         Attachments: AS7-713.txt
>
>
> It seems to me that we will have multiple clients using the management api to deploy to domain and they all today need to somehow define at every deployment the rollout plan to use if not just the hardwired default.
> To avoid having to redefine that everytime it means clients such as IDE's, management console, command line tools will all have to somehow be able to persist this information in their own local setup and these will probably all be a little bit different and thus not shareable.
> Thus I suggest that it should be possible to define named rollout plan settings that all the clients can query and provide as named arguments in the managed deployments instead of it being up to every client to define it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira