[wildfly-dev] Migration management operation - open questions
Stuart Douglas
stuart.w.douglas at gmail.com
Thu Aug 13 01:50:17 EDT 2015
I have added this to the Undertow op here:
https://github.com/wildfly/wildfly/pull/7926/files
The approach I took was to add the warnings to the describe-migration op,
and when running the migrate op make the describe-migration operation the
first step in the composite, so the output looks like this:
http://pastebin.com/B01KNAHX
I am not sure how much I like it, but it also has the advantage than it
displays what has been done when you are running the migrate op. I don't
know much about the internals of composite operations, so I am not sure how
hard it would be to somehow add this information directly.
Stuart
On Thu, 13 Aug 2015 at 15:27 Stuart Douglas <stuart.w.douglas at gmail.com>
wrote:
>
>> I propose the following format for the "result" field of the migrate
>> operation response:
>>
>> {
>> "migration-warnings"=>[
>> "WFXXX1234: the blah is blah",
>> "WFXXX2345: the foo is barred"
>> ]
>> }
>>
>>
> The current implementation use a composite operation, so the results look
> like:
>
> /subsystem=web:migrate
> {
> "outcome" => "success",
> "result" => {
> "step-1" => {"outcome" => "success"},
> "step-2" => {"outcome" => "success"},
> "step-3" => {"outcome" => "success"},
> ....
> }
> }
>
> Because this is using a composite op, I am not sure how the
> migration-warnings should be displayed? Possibly as the results of the
> first step?
>
> Stuart
>
>
>>
>> --
>> Brian Stansberry
>> Senior Principal Software Engineer
>> JBoss by Red Hat
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20150813/ea1499f4/attachment-0001.html
More information about the wildfly-dev
mailing list