10:27 a.m.
Persist named deployment groups for reuse by clients
----------------------------------------------------
Key: AS7-713
URL: https://issues.jboss.org/browse/AS7-713
Project: Application Server 7
Issue Type: Feature Request
Reporter: Max Rydahl Andersen
Assignee: Jason Greene
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 deployment 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 deployment 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:41 a.m.
New subject: [JBoss JIRA] Updated: (AS7-713) Persist named rollout plans for reuse by clients
[
https://issues.jboss.org/browse/AS7-713?page=com.atlassian.jira.plugin.sy...
]
Brian Stansberry updated AS7-713:
---------------------------------
Summary: Persist named rollout plans for reuse by clients (was: Persist named
deployment groups for reuse by clients)
Description:
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.
was:
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 deployment 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 deployment 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.
Modified title and description to use "rollout plan" instead of
"deployment". These settings can apply to any update, not just deployments, so
I've been using "rollout plan" to avoid ambiguity.
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
Reporter: Max Rydahl Andersen
Assignee: Jason Greene
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:01 a.m.
New subject: [JBoss JIRA] Updated: (AS7-713) Persist named rollout plans for reuse by clients
[
https://issues.jboss.org/browse/AS7-713?page=com.atlassian.jira.plugin.sy...
]
Brian Stansberry updated AS7-713:
---------------------------------
Assignee: (was: Jason Greene)
Component/s: Domain Management
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
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:20 a.m.
New subject: [JBoss JIRA] Updated: (AS7-713) Persist named rollout plans for reuse by clients
[
https://issues.jboss.org/browse/AS7-713?page=com.atlassian.jira.plugin.sy...
]
Brian Stansberry updated AS7-713:
---------------------------------
Fix Version/s: 7.1.0.Beta1
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
Fix For: 7.1.0.Beta1
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:13 p.m.
New subject: [JBoss JIRA] Updated: (AS7-713) Persist named rollout plans for reuse by clients
[
https://issues.jboss.org/browse/AS7-713?page=com.atlassian.jira.plugin.sy...
]
Brian Stansberry updated AS7-713:
---------------------------------
Fix Version/s: Open To Community
(was: 7.1.0.Alpha1)
Moving to Open to Community as I can't commit they'll be resources to do this for
7.1.
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
Fix For: Open To Community
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:35 p.m.
New subject: [JBoss JIRA] (AS7-713) Persist named rollout plans for reuse by clients
[
https://issues.jboss.org/browse/AS7-713?page=com.atlassian.jira.plugin.sy...
]
Brian Stansberry updated AS7-713:
---------------------------------
Fix Version/s: 7.1.0.CR1
(was: Open To Community)
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
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
12:35 p.m.
New subject: [JBoss JIRA] (AS7-713) Persist named rollout plans for reuse by clients
[
https://issues.jboss.org/browse/AS7-713?page=com.atlassian.jira.plugin.sy...
]
Brian Stansberry reassigned AS7-713:
------------------------------------
Assignee: Brian Stansberry
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
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
2:04 p.m.
New subject: [JBoss JIRA] (AS7-713) Persist named rollout plans for reuse by clients
[
https://issues.jboss.org/browse/AS7-713?page=com.atlassian.jira.plugin.sy...
]
Brian Stansberry resolved AS7-713.
----------------------------------
Resolution: Done
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
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
4:42 a.m.
New subject: [JBoss JIRA] (AS7-713) Persist named rollout plans for reuse by clients
[
https://issues.jboss.org/browse/AS7-713?page=com.atlassian.jira.plugin.sy...
]
Max Rydahl Andersen commented on AS7-713:
-----------------------------------------
marked as resolved - any pointers to how to use this?
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
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
5:02 p.m.
New subject: [JBoss JIRA] (AS7-713) Persist named rollout plans for reuse by clients
[
https://issues.jboss.org/browse/AS7-713?page=com.atlassian.jira.plugin.sy...
]
Brian Stansberry commented on AS7-713:
--------------------------------------
The API description:
[domain@localhost:9999 /] cd management-client-content=rollout-plans
[domain@localhost:9999 management-client-content=rollout-plans]
:read-resource-description(recursive=true,inherited=false,operations=true)
{
"outcome" => "success",
"result" => {
"description" => "Storage information about a set of named
management update rollout plans useful to management clients that are stored in the domain
content repository. The child resources under this resource provide access to these plans
to management clients, allowing clients to use the plans by referencing them by name,
avoiding the need to recreate them for each use.",
"attributes" => {"hash" => {
"type" => BYTES,
"description" => "The hash of all stored rollout plans. Used
internally by host controllers to locate rollout plan content.",
"expressions-allowed" => false,
"nillable" => true,
"min" => 20L,
"max" => 20L,
"access-type" => "read-only",
"storage" => "configuration"
}},
"operations" => {"add" => {
"operation-name" => "add",
"description" => "Adds the capability to store named rollout
plans.",
"request-properties" => {"hash" => {
"type" => BYTES,
"description" => "The hash of all stored rollout plans.
Used internally by host controllers to locate rollout plan content.",
"expressions-allowed" => false,
"required" => false,
"nillable" => true,
"min" => 20L,
"max" => 20L
}},
"reply-properties" => {}
}},
"children" => {"rollout-plan" => {
"description" => "A stored rollout plan.",
"model-description" => {"*" => {
"description" => "A stored rollout plan.",
"attributes" => {
"content" => {
"type" => OBJECT,
"description" => "The rollout plan content, in
JBoss DMR form.",
"expressions-allowed" => false,
"nillable" => false,
"access-type" => "read-write",
"storage" => "runtime",
"restart-required" => "no-services"
},
"hash" => {
"type" => BYTES,
"description" => "The hash of the rollout plan
content.",
"expressions-allowed" => false,
"nillable" => false,
"min" => 20L,
"max" => 20L,
"access-type" => "read-only",
"storage" => "runtime"
}
},
"operations" => {
"store" => {
"operation-name" => "store",
"description" => "Updates the content of an
existing persisted rollout plan, after first checking that the provided 'hash'
parameter matches the current rollout plan hash. Fails if the hashes do not match. Using
this operation instead of the 'write-attribute' operation for the
'content' attribute provides a guarantee that the update will not conflict with a
previous update unknown to the caller.",
"request-properties" => {
"hash" => {
"type" => BYTES,
"description" => "The value the caller
believes to be the hash of the rollout plan content that is being replaced.",
"expressions-allowed" => false,
"required" => true,
"nillable" => false,
"min" => 20L,
"max" => 20L
},
"content" => {
"type" => OBJECT,
"description" => "The updated rollout
plan content, in JBoss DMR form.",
"expressions-allowed" => false,
"required" => true,
"nillable" => false
}
},
"reply-properties" => {}
},
"remove" => {
"operation-name" => "remove",
"description" => "Removes a rollout plan from
the persistent store.",
"request-properties" => {},
"reply-properties" => {}
},
"add" => {
"operation-name" => "add",
"description" => "Adds a rollout plan to the
persistent store.",
"request-properties" => {"content" => {
"type" => OBJECT,
"description" => "The rollout plan content,
in JBoss DMR form.",
"expressions-allowed" => false,
"required" => true,
"nillable" => false
}},
"reply-properties" => {}
}
},
"children" => {}
}}
}}
}
}
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
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
5:02 p.m.
New subject: [JBoss JIRA] (AS7-713) Persist named rollout plans for reuse by clients
[
https://issues.jboss.org/browse/AS7-713?page=com.atlassian.jira.plugin.sy...
]
Brian Stansberry updated AS7-713:
---------------------------------
Comment: was deleted
(was: The API description:
[domain@localhost:9999 /] cd management-client-content=rollout-plans
[domain@localhost:9999 management-client-content=rollout-plans]
:read-resource-description(recursive=true,inherited=false,operations=true)
{
"outcome" => "success",
"result" => {
"description" => "Storage information about a set of named
management update rollout plans useful to management clients that are stored in the domain
content repository. The child resources under this resource provide access to these plans
to management clients, allowing clients to use the plans by referencing them by name,
avoiding the need to recreate them for each use.",
"attributes" => {"hash" => {
"type" => BYTES,
"description" => "The hash of all stored rollout plans. Used
internally by host controllers to locate rollout plan content.",
"expressions-allowed" => false,
"nillable" => true,
"min" => 20L,
"max" => 20L,
"access-type" => "read-only",
"storage" => "configuration"
}},
"operations" => {"add" => {
"operation-name" => "add",
"description" => "Adds the capability to store named rollout
plans.",
"request-properties" => {"hash" => {
"type" => BYTES,
"description" => "The hash of all stored rollout plans.
Used internally by host controllers to locate rollout plan content.",
"expressions-allowed" => false,
"required" => false,
"nillable" => true,
"min" => 20L,
"max" => 20L
}},
"reply-properties" => {}
}},
"children" => {"rollout-plan" => {
"description" => "A stored rollout plan.",
"model-description" => {"*" => {
"description" => "A stored rollout plan.",
"attributes" => {
"content" => {
"type" => OBJECT,
"description" => "The rollout plan content, in
JBoss DMR form.",
"expressions-allowed" => false,
"nillable" => false,
"access-type" => "read-write",
"storage" => "runtime",
"restart-required" => "no-services"
},
"hash" => {
"type" => BYTES,
"description" => "The hash of the rollout plan
content.",
"expressions-allowed" => false,
"nillable" => false,
"min" => 20L,
"max" => 20L,
"access-type" => "read-only",
"storage" => "runtime"
}
},
"operations" => {
"store" => {
"operation-name" => "store",
"description" => "Updates the content of an
existing persisted rollout plan, after first checking that the provided 'hash'
parameter matches the current rollout plan hash. Fails if the hashes do not match. Using
this operation instead of the 'write-attribute' operation for the
'content' attribute provides a guarantee that the update will not conflict with a
previous update unknown to the caller.",
"request-properties" => {
"hash" => {
"type" => BYTES,
"description" => "The value the caller
believes to be the hash of the rollout plan content that is being replaced.",
"expressions-allowed" => false,
"required" => true,
"nillable" => false,
"min" => 20L,
"max" => 20L
},
"content" => {
"type" => OBJECT,
"description" => "The updated rollout
plan content, in JBoss DMR form.",
"expressions-allowed" => false,
"required" => true,
"nillable" => false
}
},
"reply-properties" => {}
},
"remove" => {
"operation-name" => "remove",
"description" => "Removes a rollout plan from
the persistent store.",
"request-properties" => {},
"reply-properties" => {}
},
"add" => {
"operation-name" => "add",
"description" => "Adds a rollout plan to the
persistent store.",
"request-properties" => {"content" => {
"type" => OBJECT,
"description" => "The rollout plan content,
in JBoss DMR form.",
"expressions-allowed" => false,
"required" => true,
"nillable" => false
}},
"reply-properties" => {}
}
},
"children" => {}
}}
}}
}
}
)
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
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
5:04 p.m.
New subject: [JBoss JIRA] (AS7-713) Persist named rollout plans for reuse by clients
[
https://issues.jboss.org/browse/AS7-713?page=com.atlassian.jira.plugin.sy...
]
Brian Stansberry reopened AS7-713:
----------------------------------
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
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
5:12 p.m.
New subject: [JBoss JIRA] (AS7-713) Persist named rollout plans for reuse by clients
[
https://issues.jboss.org/browse/AS7-713?page=com.atlassian.jira.plugin.sy...
]
Brian Stansberry resolved AS7-713.
----------------------------------
Resolution: Done
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
5:12 p.m.
New subject: [JBoss JIRA] (AS7-713) Persist named rollout plans for reuse by clients
[
https://issues.jboss.org/browse/AS7-713?page=com.atlassian.jira.plugin.sy...
]
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
4779
days inactive
5002
days old
13 comments
8 participants
participants (8)
-
Brian Stansberry (Assigned) (JIRA) -
Brian Stansberry (Commented) (JIRA)
-
Brian Stansberry (JIRA)
-
Brian Stansberry (Reopened) (JIRA)
-
Brian Stansberry (Resolved) (JIRA)
-
Brian Stansberry (Updated) (JIRA)
-
Max Rydahl Andersen (Commented) (JIRA)
-
Max Rydahl Andersen (JIRA)