So what you need is the ability to create more users on all the
cluster nodes? There is no easy way to accomplish this right now.

There is an experimental solution you can try. You need to build Whirr
from trunk + WHIRR-255 [1]. You should get a build that has basic
support for Puppet for cluster configuration. Check
recipes/puppet-ec2.properties to get an idea how to configure roles.

The Puppet master has a git repository you can clone in order to work
with the manifest files. site.pp should contain a list of all the
Puppet enabled hosts.

The basic workflow looks like this:

$ whirr launch-cluster hadoop_with_puppet.properties
( puppet master on namenode and puppet agent on data nodes)

$ git clone ssh://puppet-master-ip/etc/puppet/manifests
(edit manifests files as needed to create new accounts)

$ git commit & push to origin

$ whirr run-puppet
(this will apply the manifest files as needed check the output for errors)

Also keep in mind that you should probably edit the security group
using the AWS console to allow access on ssh from multiple IPs.

WHIRR-255 is work in progress and probably will change a lot before
entering the trunk.

Let me know if you face any problems, I'm the one working on this feature.

[1] https://issues.apache.org/jira/browse/WHIRR-255

Cheers,

-- Andrei Savu / andreisavu.ro

On Wed, Jun 8, 2011 at 7:10 AM, John Conwell <j...@iamjohn.me> wrote:
> Thats not that feasible in a team environment, where multiple people share
> multiple resources.
>
> On Tue, Jun 7, 2011 at 4:39 PM, Khanh Nguyen <nguyen.h.kh...@gmail.com>
> wrote:
>>
>> Can you copy your .ssh/id_rsa and use it at the other machines?
>>
>> -k
>>
>> On Tue, Jun 7, 2011 at 6:52 PM, John Conwell <j...@iamjohn.me> wrote:
>> > Is there anyway I can configure whirr to allow me to ssh into any node
>> > in my
>> > cluster from a different machine than the one that launched the cluster?
>> >  My
>> > clusters can be fairly long lived, and I might need to access one of the
>> > nodes via ssh from home, or customer's office, or someone else on my
>> > team,
>> > or some such.  Is there any way I can configure whirr to allow this?
>
>
>
> --
>
> Thanks,
> John C
>

Reply via email to