[
https://issues.apache.org/jira/browse/WHIRR-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13963734#comment-13963734
]
ASF GitHub Bot commented on WHIRR-760:
--------------------------------------
GitHub user ashley-taylor opened a pull request:
https://github.com/apache/whirr/pull/7
WHIRR-760
allow other sudoers access
allow password ssh access
configure all systems against the private ip address
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ashley-taylor/whirr branch-0.9
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/whirr/pull/7.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 #7
----
commit 67234d51a129e0b2acc60d965780815067700b59
Author: ashley-taylor <[email protected]>
Date: 2014-04-09T02:50:59Z
WHIRR-760
allow other sudoers access
allow password ssh access
configure all systems against the private ip address
----
> Changes required to work with rackspace and rackconnect
> -------------------------------------------------------
>
> Key: WHIRR-760
> URL: https://issues.apache.org/jira/browse/WHIRR-760
> Project: Whirr
> Issue Type: Improvement
> Components: core
> Reporter: Ashley Taylor
>
> When trying to create a cluster we encountered so issues with working with
> rackconnect (rackspaces network configuration tool)
> We needed to allow password ssh access
> needed the sudoers file to be modified not replace
> needed the machine to configure against the private ip
> have a patch that
> makes the disabling of password access optional
> changes the sudoers change to make use of sudoers.d folder this will only
> work on linux flavors that have this feature.
> and one to make it specify the private ip as both the public and private so
> the machine configures correctly.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
