[StarCluster] adding parameters to create_volume function - encryption
ronen artzi
ronen.artzi at gmail.com
Thu Jul 3 01:55:38 EDT 2014
Thank you so much!!
All I needed was that pointer to the actual create_volume that was called
the problem is solved not sure how I missed that path.
I had changed awsutils.py to the following and it works for me:
def create_volume(self, size, zone, snapshot_id=None , encrypt =False):
...
return self.conn.create_volume(size, zone, snapshot_id,
encrypted=encrypt)
I have a GlusterFS plugin that create encrypted EBS that are used as
GlusterFS brick.
This one does not solve (?) the protocol encryption ( hence the encryption
on the fly challenge but provide encryption at rest ).
On Wed, Jul 2, 2014 at 11:58 PM, Rayson Ho <raysonlogin at gmail.com> wrote:
> Hmm, I was not very clear in my previous email...
>
> create_volume() called in volume.py is defined in the StarCluster's
> EasyAWS class (awsutils.py). So if you want to pass encypted=True to boto's
> create_volume(), you will need to add the extra parameter in awsutils.py:
>
> def create_volume(self, size, zone, snapshot_id=None):
> ...
> return self.conn.create_volume(size, zone, snapshot_id,
> encypted=True)
>
> So you just need to work your way up the call chain so that you can
> determine the value passed in by the user from the command line.
>
> (When your code is general purpose enough to be included in the
> StarCluster repo, create a pull request in github.)
>
> Rayson
>
> ==================================================
> Open Grid Scheduler - The Official Open Source Grid Engine
> http://gridscheduler.sourceforge.net/
> http://gridscheduler.sourceforge.net/GridEngine/GridEngineCloud.html
>
>
> On Wed, Jul 2, 2014 at 11:07 PM, ronen artzi <ronen.artzi at gmail.com>
> wrote:
>
>> Thanks Rayson for your prompt response.
>>
>> I am running on the "Cluster Launcher/controller" node with Boto 2.30.0
>> installed.
>> in my code I am using (encrypt is the option I am getting from the user :
>> True/False):
>>
>> log.info(">>>>>>>>>>>> Creating new Volume with
>> encrypt option : %s" % encrypt)
>> vol = self.ec2.create_volume(size, zone,
>> None,None,None,encrypt,None)
>> log.info("New volume id: %s" % vol.id)
>>
>> The error I am getting :
>>
>> File "/home/ubuntu/.starcluster/plugins/glusterfsencrypt.py", line 110,
>> in run
>> volume = self._create_ec2_volume(self.name, self.ebs_size, zone ,
>> self.encrypt)
>>
>> File "/home/ubuntu/.starcluster/plugins/glusterfsencrypt.py", line 363,
>> in _create_ec2_volume
>> vol = self.ec2.create_volume(size, zone, None,None,None,encrypt)
>>
>> TypeError: create_volume() takes at most 4 arguments (8 given)
>>
>>
>>
>> On another note : when I am calling the create_function with
>> encypted=encrypt
>>
>> i am getting :
>>
>> vol = self.ec2.create_volume(size, zone, None,encrypted=encrypt)
>> TypeError: create_volume() got an unexpected keyword argument 'encrypted'
>>
>>
>>
>>
>> On Wed, Jul 2, 2014 at 6:35 PM, Rayson Ho <raysonlogin at gmail.com> wrote:
>>
>>> StarCluster only needs the first 3 function parameters, thus it relies
>>> on the default parameters for boto's create_volume() function. If all you
>>> want is to pass in the encrypted boolean, then you can add encrypted=True
>>> to the list of parameters for create_volume().
>>>
>>> For you code to be general purpose enough to be included, you will need
>>> to add logic so that is does not always pass the encrypted=True bool into
>>> the function all the time, and instead read the user's choice from the
>>> command line (see createvolume.py).
>>>
>>> Rayson
>>>
>>> ==================================================
>>> Open Grid Scheduler - The Official Open Source Grid Engine
>>> http://gridscheduler.sourceforge.net/
>>> http://gridscheduler.sourceforge.net/GridEngine/GridEngineCloud.html
>>>
>>>
>>> On Wed, Jul 2, 2014 at 5:42 PM, ronen artzi <ronen.artzi at gmail.com>
>>> wrote:
>>>
>>>> Hello,
>>>>
>>>> I am trying to extend a glusterfs plugin we have , and would like to
>>>> introduce the options of encrypting the ESB bricks.
>>>>
>>>> I'd like to be able to use the full parameter list coming with ec2 fro
>>>> volume creation :
>>>>
>>>> create_volume(*size*, *zone*, *snapshot=None*, *volume_type=None*,
>>>> *iops=None*, *encrypted=False*, *dry_run=False*)
>>>>
>>>> Being very new to the starcluster code base I am not sure what areas
>>>> are dealign with such volume creation.
>>>>
>>>> it seems that under star cluster python packages area , volume.py
>>>> support only the first 4 parameters.
>>>>
>>>> Any insights here are appreciated.
>>>> --
>>>> Ronen
>>>>
>>>>
>>>> _______________________________________________
>>>> StarCluster mailing list
>>>> StarCluster at mit.edu
>>>> http://mailman.mit.edu/mailman/listinfo/starcluster
>>>>
>>>>
>>>
>>
>>
>> --
>> - Ronen
>> Cell: +1-508-308-2417
>> My profiles: [image: LinkedIn]
>> <http://www.linkedin.com/pub/ronen-artzi/0/30/4b9> [image: Tungle.me]
>> <http://tungle.me/ronenartzi>
>>
>>
>
--
- Ronen
Cell: +1-508-308-2417
My profiles: [image: LinkedIn]
<http://www.linkedin.com/pub/ronen-artzi/0/30/4b9> [image: Tungle.me]
<http://tungle.me/ronenartzi>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/starcluster/attachments/20140703/14d99b63/attachment.htm
More information about the StarCluster
mailing list