Good afternoon, I am the mentor responsible for the DBaaS API implementation in libcloud. Thank you first for your submission to libcloud and Google Summer of Code. I have some technical concerns with your implementation of the DBaaS API that I hope we can work on.
First, we do not support pulling in an external dependency, such as boto, as one of the primary purposes of libcloud is to avoid becoming a "library of libraries". I use Amazon's API every day, and I realize how difficult it can be to work with. However, we cannot implement this with boto as a dependency. It would be much better if you utilized libcloud's HTTP primitives as the remainder of the library does. Do you feel confident this is implementable without depending on boto? Second, I don't believe the time is right to limit libcloud to Python 2.6, and I personally feel like that your usage of ABC is a bit overkill for the case at hand. If you look at any of the other drivers in libcloud, we do not use ABCs for this purpose, and the DBaaS API would then be unique in libcloud and strange for other maintainers to work with. Is this implementable without ABCs? Third, in your proposal, I don't get the impression that you'd want to become responsible for this code once GSoC is over. Specifically, this section: > I envision that since more and more of my consulting work for other > customers requires cloud development in one form or another I will > slowly try to begin using libcloud instead of vendor-specific libraries > and, if needed, try to implement more features that are missing from > libcloud. If I read between the lines, here, it sounds like the question posed to you, specifically, about maintenance of the code post-GSoC, isn't a priority for you. Can you elaborate on this point? Have you used libcloud in the past? If not, I encourage you to do so and study its code to see how the rest of the project is built. -- Jed Smith [email protected]
