Hi Carlos, I am developing a Python driver for Verizon Cloud Compute, and I just had a couple questions about getting started with Libcloud. I hope you can help me out.
1. Why is your libcloud-vagrant driver not in the Libcloud repo? Is it common practice to release the first version outside of the libcloud repo? Did you follow the libcloud coding standards? 2. Will you be listed as a ³Third Party Provider² on the Libcloud developers page? 3. Are there any things you wish you knew when you started writing the driver that you now know? About me: I am an intern at Verizon Enterprise Services for the summer. I am writing a Python driver for the Verizon Cloud Compute IaaS. I am hoping to leave behind an ongoing open-source project when I leave, and Libcloud would allow me to do that.¹ If you see helping me, that would be awesome. Thanks! Best Regards, Michael Kaldawi Partner Integration Engineering Intern Verizon Enterprise Services On 7/19/14, 12:03 PM, "Carlos Valiente" <[email protected]> wrote: >Hi! I have just released version 0.1.0 of libcloud-vagrant, a compute >provider for Apache Libcloud which uses Vagrant and VirtualBox to >create nodes, networks and volumes: > > https://github.com/carletes/libcloud-vagrant > > >C
