GitHub user aledsage opened a pull request:
https://github.com/apache/brooklyn-server/pull/132
Fix JcloudsByonLocationResolver
- Previously, it created locations every time the resolver was called
(even if that was just to query about what it would produce), which
caused us to leak locations.
- Now it defers creating the locations (though doing this with
LocationSpec is not practical because of the relationship between
the JcloudsLocation and the machines)!
- Adds FixedListMachineProvisioningLocation.initialMachinesFactory,
for deferring the machine-lookup until the byon location is really
being created.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/aledsage/brooklyn-server
fix/JcloudsByonLocationResolver
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/brooklyn-server/pull/132.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 #132
----
commit bae0726d3a2ed984fa4a657168daf570b041625e
Author: Aled Sage <[email protected]>
Date: 2016-05-03T15:58:32Z
Fix JcloudsByonLocationResolver
- Previously, it created locations every time the resolver was called
(even if that was just to query about what it would produce), which
caused us to leak locations.
- Now it defers creating the locations (though doing this with
LocationSpec is not practical because of the relationship between
the JcloudsLocation and the machines)!
- Adds FixedListMachineProvisioningLocation.initialMachinesFactory,
for deferring the machine-lookup until the byon location is really
being created.
----
---
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.
---
