On Mon, 2010-02-15 at 08:42 -0800, Paul Querna wrote: > On Sun, Feb 14, 2010 at 10:55 AM, Lloyd Cooke <[email protected]> > wrote: > > Dear libcloud, > > > > We recently came across your web page of Cloud providers at > > http://incubator.apache.org/libcloud/ [1] and I would like to ask whether > > you would consider adding our sister company iomart Hosting to your list. > > For more information on the products and the support provided please see > > http://www.iomarthosting.com/cloud-hosting. [2] > > > > Many Thanks > > > > Lloyd Cooke > > > Hello Lloyd, > > Since libcloud is an open source project, we generally are only able > to implement APIs that provide public documentation on how we can do > things like create a server, destroy/reboot etc. I looked over the > iomart hosting website and was unable to find documentation of an API. > > Some examples of what we use from other hosting providers: > ec2: http://docs.amazonwebservices.com/AWSEC2/latest/APIReference/ > rackspace: http://www.rackspacecloud.com/cloud_hosting_products/servers/api > linode: http://www.linode.com/api/ > > Once we have documentation on an API, it enables open source > developers to develop the libcloud code to work with your services, > though to be clear the Apache Software Foundation doesn't actually pay > developers to write the code -- they are employed by 3rd party > companies or do it of their own free will. (but this is starting to > get out of scope for this email :) )
In fact, I'd suggest that the simplest way to get your provider included is to download Libcloud, extend it to work with your provider (you need someone who is competent with Python), and supply Libcloud with a patch. As Paul says, public docs would then enable libcloud devs to ensure that it is working as suggested, as would likely some kind of (free) test account to prove that it actually works as intended. Regards, Upayavira
