Re: adding parameters to create_volume function - encryption

From: Rayson Ho <no email>
Date: Wed, 2 Jul 2014 18:35:00 -0400

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
>
>
Received on Wed Jul 02 2014 - 18:35:02 EDT