You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by "Mike Zaccardo (JIRA)" <ji...@apache.org> on 2017/02/15 22:47:41 UTC
[jira] [Updated] (BROOKLYN-439) Existing `userMetadata` cannot be
used with WinRM deployments on certain clouds
[ https://issues.apache.org/jira/browse/BROOKLYN-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Zaccardo updated BROOKLYN-439:
-----------------------------------
Environment:
AWS
Vcloud Director
Description:
*Applies to AWS and Vcloud Director based clouds*
When deploying a WinRM-based blueprint, the `userMetadata` of the deployment location's configuration must be empty. See: http://docs.cloudsoft.io/blueprints/base-blueprints/winrm/index.html#user-metadata-service-requirement
This prevents the user from deploying with any other potentially useful `userMetadata` values, like their email or a "keep" tag. It will also cause the WinRM deployment to fail if the user does not realize that s/he has existing `userMetadata` in place, and there is no relevant error message to make this clear.
Ideally the existing `userMetadata` could be merged with the necessary WinRM script so the user does not have to abandon their desired `userMetadata`.
The relevant code is here: https://github.com/apache/brooklyn-server/blob/master/locations/jclouds/src/main/java/org/apache/brooklyn/location/jclouds/JcloudsLocation.java#L1470
was:
When deploying a WinRM-based blueprint, the `userMetadata` of the deployment location's configuration must be empty. See: http://docs.cloudsoft.io/blueprints/base-blueprints/winrm/index.html#user-metadata-service-requirement
This prevents the user from deploying with any other potentially useful `userMetadata` values, like their email or a "keep" tag. It will also cause the WinRM deployment to fail if the user does not realize that s/he has existing `userMetadata` in place, and there is no relevant error message to make this clear.
Ideally the existing `userMetadata` could be merged with the necessary WinRM script so the user does not have to abandon their desired `userMetadata`.
The relevant code is here: https://github.com/apache/brooklyn-server/blob/master/locations/jclouds/src/main/java/org/apache/brooklyn/location/jclouds/JcloudsLocation.java#L1470
Summary: Existing `userMetadata` cannot be used with WinRM deployments on certain clouds (was: Existing `userMetadata` cannot be used with WinRM deployments)
> Existing `userMetadata` cannot be used with WinRM deployments on certain clouds
> -------------------------------------------------------------------------------
>
> Key: BROOKLYN-439
> URL: https://issues.apache.org/jira/browse/BROOKLYN-439
> Project: Brooklyn
> Issue Type: Improvement
> Affects Versions: 0.11.0
> Environment: AWS
> Vcloud Director
> Reporter: Mike Zaccardo
> Priority: Minor
> Labels: windows
>
> *Applies to AWS and Vcloud Director based clouds*
> When deploying a WinRM-based blueprint, the `userMetadata` of the deployment location's configuration must be empty. See: http://docs.cloudsoft.io/blueprints/base-blueprints/winrm/index.html#user-metadata-service-requirement
> This prevents the user from deploying with any other potentially useful `userMetadata` values, like their email or a "keep" tag. It will also cause the WinRM deployment to fail if the user does not realize that s/he has existing `userMetadata` in place, and there is no relevant error message to make this clear.
> Ideally the existing `userMetadata` could be merged with the necessary WinRM script so the user does not have to abandon their desired `userMetadata`.
> The relevant code is here: https://github.com/apache/brooklyn-server/blob/master/locations/jclouds/src/main/java/org/apache/brooklyn/location/jclouds/JcloudsLocation.java#L1470
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)