brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BROOKLYN-427) JcloudsLocation is not releasing its customizers
Date Wed, 25 Jan 2017 14:58:26 GMT


ASF GitHub Bot commented on BROOKLYN-427:

Github user geomacy commented on the issue:
    Addressed review [comment](
"Can you instead add the config for JCLOUDS_LOCATION_CUSTOMIZERS..."

> JcloudsLocation is not releasing its customizers
> ------------------------------------------------
>                 Key: BROOKLYN-427
>                 URL:
>             Project: Brooklyn
>          Issue Type: Bug
>            Reporter: Geoff Macartney
>            Priority: Minor
> preRelease and postRelease of JcloudsLocationCustomizers are not being 
> called as expected during the release of a Jclouds machine location.
> The problem is that the "setup" used in JcloudsLocation.obtainOnce includes a copy of
the flags passed from MachineLifecycleEffectorTasks#stopAnyProvisionedMachines,
> which includes the customizers. However, the "setup" used in the "release"
> method of JcloudsLocation is taken from the JcloudsLocation itself, which
> is the provisioning (i.e. parent) location, which doesn't have those 
> customizers in it. 
> It would actually make more sense to get the location customizers from
> the machine location, as a given parent could have mutiple machines
> with different customizers. 

This message was sent by Atlassian JIRA

View raw message