I'm looking to create a module that will be a perl interface to Verizon Cloud services. I haven't decided if this should be an OO module or more a "traditional" approach
That is: use Vz::Ecloud::VirtualMachine; my $vm = Vz::Ecloud::VirtualMachine->new; $vm->set... $vm->launch; vs use Vz::Ecloud qw(create_vm) create_vm(%args) Leaning towards to the latter as it just seems simpler/easier (Welcome your feedback on this as well...) I envision that there would be different components for VCC (Verizon Cloud Compute), VCS (Verizon Cloud Storage), Verizon Enterprise Cloud (Ecloud), and future products. use Vz::Ecloud qw(list_environments) list_environments(%args) use Vz::VCC qw(create_vm) create_vm(%args) use Vz::VCS qw(create_bucket) create_bucket(%args) Also, I plan on including a command line tool to use: $ vz vcs create_bucket.... Thinking of VzCloudTools or similar name. Not sure if I should create a top level name space. I'm not a super-experienced Perl developer, so I'd like to get your recommendation for naming/structuring the module. Thanks very much for taking the time to review/respond. Best, Jason Goth
