| Re: [camf-dev] Plugin is not working |
| Dear Danilo hi, Thanks for reaching out to the list. Since you wrote a quite extensive and complete email, let’s take things one at a time. I would be happy to assist you in anyway possible. Some generic comments: 1) Regarding Openstack, we have some limitations with which versions are supported by CAMF. The reason being that we are currently utilising a somehow older version of Apache JClouds libs, namely v1.8.0. We have tested it with Juno (not Liberty), and we have found that major functions work as expected. However there might be some ‘hickups’ that we can try to resolve. The contributions of the community are more that welcome here. 2) Regarding the installation / MAVEN errors you experience, I urge you not to worry. Specifically, we are in process of removing Maven totally from the build process and utilising P2 repositories for all 3rd party libs. All 3rd party libs have now been committed to the Eclipse Orbit project [1], and are available in the respective Git repo [2]. We are in discussions with the Orbit project to include these libs in the new synthetic repos that will be build in EBR recipes [3]. Therefore, the cumbersome and time-consuming steps of Maven will soon be removed completely. 3) Can you give me some detailed information, on what scenario are you trying to execute via CAMF? What application topology are you trying to build and deploy? More specific comments: 3) Concerning the Cloud Information Tool , can you please provide some more details on what was the error specifically?? Removing the edit plugin from the feature.xml, does not make sense why the Tool was running. Maybe there is something else that causes this error, that we need to look deeper to find it. Therefore, any details are more than welcome. 4) There is some initial code for Ceilometer in the Monitoring plugins, however we have not fully implement that functionality, due to external dependencies (Apache jclouds) that need to undergo IP due-dilligence review from the Eclipse IP team. If this is something that you require and willing to contribute, then we can submit these libs for review asap. 5) The elasticity functionality is based on the Monitoring plugins. You need to assign some monitoring probes to VM's that obtain the metrics you need. Given point (4) above, this is not possible for Openstack. However, it is possible for AWS if you would like to have a look at it. 6) What you see from the Palette is expected. You only need the Component & Composite Component actions for generating the basis of your VM’s. Then you can drag and drop from the Cloud Information Tool, any artifact you want (i.e image, network, security keys and groups, etc). Feel free to open a discussion here in the mailing list. Sincerely, Nicholas |
Attachment:
smime.p7s
Description: S/MIME cryptographic signature