You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by "Aled Sage (JIRA)" <ji...@apache.org> on 2017/11/14 20:46:05 UTC
[jira] [Updated] (BROOKLYN-529) Windows location keyPair issue
[ https://issues.apache.org/jira/browse/BROOKLYN-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aled Sage updated BROOKLYN-529:
-------------------------------
Description:
I can't deploy the following blueprint
{noformat}
name: bad
location:
'jclouds:aws-ec2':
region: eu-west-1
identity: xxx
credential: xxx
imageOwner: 801119661308
imageNameRegex: Windows_Server-2012-R2_RTM-English-64Bit-Base-.*
useJcloudsSshInit: false
keyPair: myKeypair
services:
- type: org.apache.brooklyn.entity.software.base.VanillaWindowsProcess
brooklyn.config:
install.command: echo installing
checkRunning.command: echo running
{noformat}
while the slightly modified version
{noformat}
name: bad
location:
'jclouds:aws-ec2':
region: eu-west-1
identity: xxx
credential: xxx
imageOwner: 801119661308
imageNameRegex: Windows_Server-2012-R2_RTM-English-64Bit-Base-.*
useJcloudsSshInit: false
services:
- type: org.apache.brooklyn.entity.software.base.VanillaWindowsProcess
brooklyn.config:
install.command: echo installing
checkRunning.command: echo running
{noformat}
works fine.
if you specify a keyPair, jclouds won’t wait for the admin password to be ready and will return the node without password; while if the blueprint doesn’t specify a keyPair name, jclouds will generate one and will use the private key to decrypt the admin password and pass back to brooklyn a node with a valid `LoginCredentials.password`
was:
I can't deploy the following blueprint
{{name: bad
location:
'jclouds:aws-ec2':
region: eu-west-1
identity: xxx
credential: xxx
imageOwner: 801119661308
imageNameRegex: Windows_Server-2012-R2_RTM-English-64Bit-Base-.*
useJcloudsSshInit: false
keyPair: myKeypair
services:
- type: org.apache.brooklyn.entity.software.base.VanillaWindowsProcess
brooklyn.config:
install.command: echo installing
checkRunning.command: echo running}}
while the slightly modified version
{{name: bad
location:
'jclouds:aws-ec2':
region: eu-west-1
identity: xxx
credential: xxx
imageOwner: 801119661308
imageNameRegex: Windows_Server-2012-R2_RTM-English-64Bit-Base-.*
useJcloudsSshInit: false
services:
- type: org.apache.brooklyn.entity.software.base.VanillaWindowsProcess
brooklyn.config:
install.command: echo installing
checkRunning.command: echo running}}
works fine.
if you specify a keyPair, jclouds won’t wait for the admin password to be ready and will return the node without password; while if the blueprint doesn’t specify a keyPair name, jclouds will generate one and will use the private key to decrypt the admin password and pass back to brooklyn a node with a valid `LoginCredentials.password`
> Windows location keyPair issue
> ------------------------------
>
> Key: BROOKLYN-529
> URL: https://issues.apache.org/jira/browse/BROOKLYN-529
> Project: Brooklyn
> Issue Type: Bug
> Reporter: Graeme Miller
>
> I can't deploy the following blueprint
> {noformat}
> name: bad
> location:
> 'jclouds:aws-ec2':
> region: eu-west-1
> identity: xxx
> credential: xxx
> imageOwner: 801119661308
> imageNameRegex: Windows_Server-2012-R2_RTM-English-64Bit-Base-.*
> useJcloudsSshInit: false
> keyPair: myKeypair
> services:
> - type: org.apache.brooklyn.entity.software.base.VanillaWindowsProcess
> brooklyn.config:
> install.command: echo installing
> checkRunning.command: echo running
> {noformat}
> while the slightly modified version
> {noformat}
> name: bad
> location:
> 'jclouds:aws-ec2':
> region: eu-west-1
> identity: xxx
> credential: xxx
> imageOwner: 801119661308
> imageNameRegex: Windows_Server-2012-R2_RTM-English-64Bit-Base-.*
> useJcloudsSshInit: false
> services:
> - type: org.apache.brooklyn.entity.software.base.VanillaWindowsProcess
> brooklyn.config:
> install.command: echo installing
> checkRunning.command: echo running
> {noformat}
> works fine.
> if you specify a keyPair, jclouds won’t wait for the admin password to be ready and will return the node without password; while if the blueprint doesn’t specify a keyPair name, jclouds will generate one and will use the private key to decrypt the admin password and pass back to brooklyn a node with a valid `LoginCredentials.password`
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)