Hadoop cluster security: hadoop keys

Bug #1179821 reported by Sergey Lukjanov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Sahara
Fix Released
High
Alexander Kuznetsov

Bug Description

Savanna should generate unique keypairs for each Hadoop cluster and provision it to all vms to provide the following abilities:

* hadoop user of each vm can access any other Hadoop cluster vm using this key
* Savanna can access any Hadoop cluster vm using this key

So, Savanna should store keypair in db.

Tags: 0.2
Changed in savanna:
assignee: Dmitry Mescheryakov (dmitrymex) → Alexander Kuznetsov (akuznetsov)
tags: added: 0.2
removed: 0.1-backport
Changed in savanna:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to savanna (master)

Reviewed: https://review.openstack.org/31490
Committed: http://github.com/stackforge/savanna/commit/01c3e9943a2de691455783f6af663216fb6915f9
Submitter: Jenkins
Branch: master

commit 01c3e9943a2de691455783f6af663216fb6915f9
Author: Alexander Kuznetsov <email address hidden>
Date: Mon Jun 3 16:26:52 2013 +0400

    Cluster security and node placement control

    Adding user key to the cluster

    Each cluster will have a it own private key for passwordless login

    It is possible to schedule a data nodes on diffirent hosts

    implements: blueprint node-placement-control and blueprint cluster-security

    fixed: bug #1179815 and bug #1179821

    Change-Id: I27183b9fcf1652b8f65a7018fe9cb880d5bed3b3

Changed in savanna:
status: In Progress → Fix Committed
Changed in savanna:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.