[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14367902#comment-14367902
 ] 

Amarnath Beedimane Hanumantharaya commented on CLOUDSTACK-8207:
---------------------------------------------------------------

Hi,
my name is Amarnath Beedimane Hanumantharaya am a master student at University 
of Missouri- Kansas city.can i take up this project since i have a prior 
experience of Working as Quality Engineer in SAP Labs India Pvt Ltd.I was 
responsible for maintaining, modifying, creating and monitoring process chains 
and recording, modifying scripts as and when the new scenario arrived. I was 
also involved in unit testing and regression testing.and i have intermediate 
skill in Python.

> Set of small CloudStack tools
> -----------------------------
>
>                 Key: CLOUDSTACK-8207
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8207
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>            Reporter: Rohit Yadav
>              Labels: cloud, golang, gsoc2015, java, python
>             Fix For: 4.6.0
>
>
> Develop tools for CloudStack:
> - CloudMonkey enhancements: Refactor CloudMonkey so anyone can write color, 
> output, network and other plugins for CloudMonkey. Add library support to 
> merge cloudmonkey and marvin, so cloudmonkey can also be used to write Python 
> scripts. Add Bash helper methods so it can be used to write bash based 
> automation scripts. Write Ansible module for CloudStack using CloudMonkey or 
> Marvin.
> - Write a new Database tool using DatabaseUpgraderClass in Python or other 
> language for CloudStack to do db dump, upgrades, backups etc
> - Write a new tool to do smoke testing (on Jenkins or TravisCI) or 
> integration testing
> - Write a tool to import/save a CloudStack deployment and export a CloudStack 
> cloud using a saved configuration



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to