GitHub user ahgittin opened a pull request:
https://github.com/apache/incubator-brooklyn/pull/83
Deploy across an entire web cluster
Adds deploy, undeploy, and redeployAll to webapp cluster entities (DWAC and
ControlledDWAC).
Also fixes some issues noticed in how tasks are tracked and displayed.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ahgittin/incubator-brooklyn web-cluster-deploy
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-brooklyn/pull/83.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #83
----
commit a070492a20505e2b2671e9a0b229ba6e47063f97
Author: bmwshop <[email protected]>
Date: 2014-06-23T18:01:00Z
deploy / undeploy / update on the ControlledDynamicWebAppCluster
commit 36423a546e07da32fb1e421731747afdc1600321
Author: Alex Heneveld <[email protected]>
Date: 2014-07-18T19:38:37Z
tidy initial pull request from @bmwshop, as per code review, plus some todo
comments
commit e58bdba72312de47c4cdbb7d8b925b1d4df711d8
Author: Alex Heneveld <[email protected]>
Date: 2014-07-18T19:58:16Z
move deploy and redeploy bodies to DynamicWebAppCluster, with
ControlledDWAC calling to that,
and with new interfaces for the shared items (deploy effectors etc) so that
ControlledDWAC is not a JavaWebAppSoftwareProcess
commit 6c2a3932e6fb9df4599a93c96f1f9c22a0bbf14b
Author: Alex Heneveld <[email protected]>
Date: 2014-07-18T21:32:59Z
better tasks logic for deploying wars when target entity is ready (ie
service up), failing gracefully if it's not, with some helpers in Tasks and
DynamicTasks
commit 2db8fd95031d0b9c6ba9e9c45b314ccc480e1f4a
Author: Alex Heneveld <[email protected]>
Date: 2014-07-18T22:14:12Z
squash code warnings, clarify user-facing messages, fix redeployAll bug
commit ab7e3d0ff42f3c5baae04fcfff31fdfa7d6dd155
Author: Alex Heneveld <[email protected]>
Date: 2014-07-22T00:33:51Z
have at-entity tasks show up as children (in dynamic queueing context,
though still submitted externally which means they will not be run as part of
queue), and allow them to have children: improves traceability in GUI when
effector methods call other effector methods, they show up as children rather
than background tasks (or worse, not even as background tasks); and support
setting flags in TaskBuilder
commit 2e124ca0c6ee89709dcf4f153c2e6f87ab3b5a66
Author: Alex Heneveld <[email protected]>
Date: 2014-07-22T00:36:53Z
parallel task should not fail if inessential child fails
commit 47488483167f9de09b014e3933b7c7b24ccc4895
Author: Alex Heneveld <[email protected]>
Date: 2014-07-22T00:37:23Z
improve display of task results, catch NPE when switching task contexts,
and ensure data is cleared (nulled) for old map entries due to backbone bug
(without this, sometimes blockingTask might show up as `TYPEOF undefined` when
you inspect its JSON)
commit a0584189808a78ded581dbf5b273d5987adb90e2
Author: Alex Heneveld <[email protected]>
Date: 2014-07-22T00:38:49Z
include blocking details when waiting for service up to invoke an effector
on a child
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
