Hi Anamika,
I just tested the following blueprint (add your prefered location to it)
name: Riak-Cluster 1
services:
- type: org.apache.brooklyn.entity.nosql.riak.RiakCluster
initialSize: 1
brooklyn.config:
provisioning.properties:
extraSshPublicKeyUrls: http://mypublickey
Notice here I'm using
type: org.apache.brooklyn.entity.nosql.riak.RiakCluster
as I'm using the latest brooklyn 0.8.0-SNAPSHOT which rename the packages
inside `software` module. If you are using the released 0.7.0-incubating
you can stick with
- type: brooklyn.entity.nosql.riak.RiakCluster
To test that it actually worked you can copy the `host.sshAddress` sensor
value from `Sensors` tab for each riak node and run:
ssh <your-user>:<host.sshAddress>
and
ssh -i <Brooklyn_Stable-private-key> <your-user>:<host.sshAddress>
HTH,
Andrea
---
FYI, in general, you don't need to specify the ssh PublicKey to ssh into
the VMs provisioned by Brooklyn: it will try to use the ssh keys associated
to the user that launched Brooklyn.
On Mon, 24 Aug 2015 at 10:49 Anamika Roychowdhury <[email protected]>
wrote:
> Hi Andrea,
>
> I feel there is no problem with alignment.
> For a single Riak Node , I am able to ssh, but the problem comes when I am
> trying to ssh to the node which is under Riak Cluster.
>
> The YAML that I am using for a Riak Cluster is following:
>
> name: Riak-Cluster
> location:
> jclouds:aws-ec2:
> credential: zN7YwJ4hhH6d3lbr9koS7az1ZPOtK+hPaf8+EyTW
> identity: AKIAIVI6M354IOE3GU3Q
> region: us-west-2
> services:
> - type: brooklyn.entity.nosql.riak.RiakCluster
> initialSize: 2
> memberSpec:
> $brooklyn:entitySpec:
> type: brooklyn.entity.nosql.riak.RiakNode
> provisioning.properties:
> extraSshPublicKeyUrls:
> https://s3-us-west-2.amazonaws.com/gowribudal/Brooklyn_Stable.pub
>
> Is this the way I should provide ssh key for the cluster?
>
> On Mon, Aug 24, 2015 at 2:41 PM, Andrea Turli <
> [email protected]> wrote:
>
> > Hi Anamika,
> >
> > your blueprint looks correct to me but for a weird indentation in the
> > extraSshPublicKeyUrls
> >
> > could you please try something like
> >
> > name: Riak-Node
> > location:
> > jclouds:aws-ec2:
> > credential: My-Credential
> > identity: My-Identity
> > region: region
> > services:
> > - type: brooklyn.entity.nosql.riak.RiakNode
> > provisioning.properties:
> > extraSshPublicKeyUrls:
> > https://s3-us-west-2.amazonaws.com/MyLocation/My_Public_Key.pub
> >
> > Let us know if that helps,
> > Andrea
> >
> > On Mon, 24 Aug 2015 at 06:33 Anamika Roychowdhury <
> [email protected]
> > >
> > wrote:
> >
> > > Hi Team,
> > >
> > > I have deployed a Riak cluster using the following YAML:
> > >
> > > name: Riak-Cluster
> > > location:
> > > jclouds:aws-ec2:
> > > credential: My-Credential
> > > identity: My-Identity
> > > region: region
> > > services:
> > > - type: brooklyn.entity.nosql.riak.RiakCluster
> > > initialSize: 2
> > > memberSpec:
> > > $brooklyn:entitySpec:
> > > type: brooklyn.entity.nosql.riak.RiakNode
> > > provisioning.properties:
> > > extraSshPublicKeyUrls:
> > > - https://s3-us-west-2.amazonaws.com/MyLocation/My_Public_Key.pub
> > >
> > > I am not able to ssh to any of the node that has been created under the
> > > Riak cluster using the private key (PORT 22 is open)
> > >
> > > But , While I have deployed a single Riak node using the following
> > > blueprint, I am able to ssh to the instance:
> > >
> > > name: Riak-Node
> > > location:
> > > jclouds:aws-ec2:
> > > credential: My-Credential
> > > identity: My-Identity
> > > region: region
> > > services:
> > > - type: brooklyn.entity.nosql.riak.RiakNode
> > > provisioning.properties:
> > > extraSshPublicKeyUrls:
> > > https://s3-us-west-2.amazonaws.com/MyLocation/My_Public_Key.pub
> > >
> > > Can anybody please tell me on where I'm going wrong or how should I
> > > provide extraSshPublicKeyUrls
> > > for the cluster , so that I can ssh to the cluster instances.
> > >
> >
> > --
> > Cloudsoft Corporation Limited, Registered in Scotland No: SC349230.
> > Registered Office: 13 Dryden Place, Edinburgh, EH9 1RP
> >
> > This e-mail message is confidential and for use by the addressee only. If
> > the message is received by anyone other than the addressee, please return
> > the message to the sender by replying to it and then delete the message
> > from your computer. Internet e-mails are not necessarily secure.
> Cloudsoft
> > Corporation Limited does not accept responsibility for changes made to
> this
> > message after it was sent.
> >
> > Whilst all reasonable care has been taken to avoid the transmission of
> > viruses, it is the responsibility of the recipient to ensure that the
> > onward transmission, opening or use of this message and any attachments
> > will not adversely affect its systems or data. No responsibility is
> > accepted by Cloudsoft Corporation Limited in this regard and the
> recipient
> > should carry out such virus and other checks as it considers appropriate.
> >
>
--
Cloudsoft Corporation Limited, Registered in Scotland No: SC349230.
Registered Office: 13 Dryden Place, Edinburgh, EH9 1RP
This e-mail message is confidential and for use by the addressee only. If
the message is received by anyone other than the addressee, please return
the message to the sender by replying to it and then delete the message
from your computer. Internet e-mails are not necessarily secure. Cloudsoft
Corporation Limited does not accept responsibility for changes made to this
message after it was sent.
Whilst all reasonable care has been taken to avoid the transmission of
viruses, it is the responsibility of the recipient to ensure that the
onward transmission, opening or use of this message and any attachments
will not adversely affect its systems or data. No responsibility is
accepted by Cloudsoft Corporation Limited in this regard and the recipient
should carry out such virus and other checks as it considers appropriate.
