Github user aledsage commented on the pull request:
https://github.com/apache/incubator-brooklyn/pull/353#issuecomment-64885639
Note that the purpose of making PortForwardManager a singleton location is
two fold:
1. The instance needs to be shared by all applications (particularly
multiple apps that are being deployed to the same cloud account, such as to
vcloud's vCHS so are updating the same set of NAT rules).
2. This simplifies peristence - we just persist that location
automatically. Previously it was a config/attribute of an entity. We tried to
have exactly one entity having the authoritative object, and all the others
just being proxies that would talk to that shared instance. Another option was
to add `managementContext.getPortForwardManager`, but having spoken it over
with @ahgittin we were reluctant to more on `managementContext` (which would
have made persisting it more complicated as well).
---
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.
---
