I've been attempting to experiment with the recently updated  Solr Scale
Tool Kit mentioned here:

http://searchhub.org/2014/06/03/introducing-the-solr-scale-toolkit/

After making the very well documented configuration changes at AWS and
installing Python, I was able to use the toolkit to connect to AWS;
however, when the demo command (fab demo:demo1,n=1) is executed, the
following access denied error message is returned:

C:\Temp\sk\solr-scale-tk>fab demo:demo1,n=1
←[33mGoing to launch 1 new EC2 m3.medium instances using AMI
ami-1e6b9d76←[0m
←[32mSetup Instance store BlockDeviceMapping: /dev/sdb -> ephemeral0←[0m
Traceback (most recent call last):
  File "c:\python27\lib\site-packages\fabric\main.py", line 743, in main
    *args, **kwargs
  File "c:\python27\lib\site-packages\fabric\tasks.py", line 405, in execute
    results['<local-only>'] = task.run(*args, **new_kwargs)
  File "c:\python27\lib\site-packages\fabric\tasks.py", line 171, in run
    return self.wrapped(*args, **kwargs)
  File "C:\Temp\sk\solr-scale-tk\fabfile.py", line 1314, in demo
    ec2hosts = new_ec2_instances(cluster=demoCluster, n=n,
instance_type=instance_type)
  File "C:\Temp\sk\solr-scale-tk\fabfile.py", line 776, in new_ec2_instances
    placement_group=placement_group)
  File "c:\python27\lib\site-packages\boto\ec2\connection.py", line 943, in
run_instances
    verb='POST')
  File "c:\python27\lib\site-packages\boto\connection.py", line 1177, in
get_object
    raise self.ResponseError(response.status, response.reason, body)
boto.exception.EC2ResponseError: EC2ResponseError: 400 Bad Request
<?xml version="1.0" encoding="UTF-8"?>
<Response><Errors><Error><Code>AuthFailure</Code><Message>Not authorized
for images:
[ami-1e6b9d76]</Message></Error></Errors><RequestID>cbdcb582-3d21-4fab-a7ea
-fe68ba696e23</RequestID></Response>

My guess is that the customized toolkit AMI (ami-1e6b9d76) at AWS is not
accessible by my AWS credentials.  Is this an AMI permissioning issue or is
it a problem with my particular account or how it is configured at AWS.  I
did not experience this specific problem when working with the previous
iteration of the Solr Scale Toolkit back toward the latter part of May.  It
appears that the AMI was updated from ami-96779efe to ami-1e6b9d76 with the
newest version of the toolkit.

Many thanks to Timothy Potter to assembling this excellent toolkit for
deploying and managing SolrCloud at AWS (and hopefully other cloud
providers in the future).

Thanks.


Mark Gershman

Reply via email to