brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bostko <>
Subject [GitHub] brooklyn-server issue #150: Ability to perform installation on a Windows Blu...
Date Sat, 04 Jun 2016 14:31:03 GMT
Github user bostko commented on the issue:
    @nakomis I amended the PR.
    To summarize, the special think for the Blueprint I tested was that:
    1. By default the install command restarts the VM on its own. A restart command executed
through winrm may report non-zero code status or connection exception.
    2. It changes the domain settings of the Windows Machine. By default Apache Brooklyn uses
username and password to authenticate via NTLM against the Windows VM. When such operation
is performed the winrm connection hangs and you cannot continue execute commands.
    So to resolve the issues above I made changes to my blueprint to not restart automatically
and restart by setting the `install.reboot.required` config.
    To make sure that the install command won't hang and the reboot command can be triggered,
    for these two commands when `install.reboot.required` is used I added the computer name
when authenticating.
    Basically adding a Computer name to the authentication should be safe and tends to be
the better way for authentication, but because it is tricky to get this name and it is not
still tested I made the change only for when `install.reboot.required` is used.
    I tested my changes against different clouds with Basic and NTLM authentication and all
    The clouds which I tested against were:
    - AWS EC2
    - Azure
    - Vcloud Director

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 or file a JIRA ticket
with INFRA.

View raw message