You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The purpose of CM is different from these tools. While libcloud and boot provide a compatibility layer between IaaS on the API level. We do develop with CM a tool that can manage conveniently VMs by a user across clouds. This includes also the creation and management of hundreds of VMs.
We started using libcloud and are still interested in it, but for some reason the native openstack client did not work on FG. We did get the ECE2 provider working, however this was less than ideal.
Instead we just wrote a compatibility layer based on novaclient for Openstack which as obvious is not that difficult to do. Once one of our students can point me to a working version of libcloud using the native OpenStack provider we will consider switching to libcloud.
However, it is important that we obtain all metadata that is attached with the cloud as is provided trough novaclient for example, or through the native curl calls (we did for now not use them as the effort of implementing against them was greater than using nova client.
CM provides an API, a set of comands that are easy and fast to use to manage hundrets of VMs, and soon a GUI.
These tools are for managing multiple clouds.
Same idea but different approaches for software development.
apache-libcloud
boto = amazon ec2
rabbitmq + celery (also django)
The text was updated successfully, but these errors were encountered: