Cool initiative, indeed. On 03 Oct 2013, at 11:12, Olivier Auverlot <olivier.auverlot@gmail.com> wrote:
why not ! it would be very cool to have an abstraction layer. The difficulty is to communicate with the virtualisation product. For Proxmox, it's easy because it uses HTTP but I don't know the other products.
I think that most cloud/virtualization products have APIs that are essentially REST based underneath, but that does not yet make it easy. In the case of AWS EC2, for example, it is quite a challenge, with their signing and XML, although it can be done of course.
Le 3 oct. 2013 à 10:05, Christophe Demarey a écrit :
Hi Olivier,
Cool. Do you think it is possible to do a more generic Cloud interface in Pharo? I mean an API agnostic to the used cloud manage (proxmox, cloudstack, openstack, amazon)? There is a Java project called jclouds[1] that does that. It may be cool that other people can define more cloud providers.
Regards, Christophe.
[1] : http://jclouds.incubator.apache.org/
Le 3 oct. 2013 à 08:06, Olivier Auverlot a écrit :
Hi,
I just started since 3 days to work on a new framework for Pharo. It's named "PROXimity". The goal of this framework is to control a Proxmox virtualization solution with Pharo.
Proxmox uses a REST API. With Zinc and STON, it's very easy to give orders as creating a virtual machine, managing the boot and stop, etc.
I'm working on this project because it is a subpart of another application but I think that it could interest other Pharo users (for example: seaside hosting).
The first Pharo classes are published on SmalltalkHub. If you're interested and want join your forces with me, don't hesitate to contact me.
http://pve.proxmox.com/wiki/Proxmox_VE_API
Best regards Olivier ;-)