[
https://issues.apache.org/jira/browse/CAMEL-9748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15471095#comment-15471095
]
Jan Bouska commented on CAMEL-9748:
-----------------------------------
[~ancosen] I am thinking about a structure of the uri in component
configuration. Because OpenStack is very complex system and there are very much
use cases. This can leads to confusions in component settings.
OpenStack is divided to services and each service is divided to subsystems.
Each subsystem can perform several operations.
I am considering 3 solutions:
1) *openstack:https://uri?service=nova&subsystem=flavours&operation=create*
configuration of new flavour would be send in exchange body
(_FlavourConfiguration.class_)
cons:
- it would be created very much operation options, each would be valid only for
exactly one service/subsystem setting
- there would be needed Configuration.class for each subsystems which could be
very much
2) something inspired by google-drive component:
*openstack://nova/https://uri?subsystem=flavours&operation=create*
This solution is better than previous because here we could use only the
options which are suitable for certain service. The other cons are remaining.
It also needs to parse componet uri to 'service' and 'uri' part. I do not like
this solution at all.
3) Divide openstack component to smaller components.
For Example:
*openstack-nova:uri?[options]
openstack-neutron:uri?[options]*
etc.
This solution will solve all cons listed above because in each component will
be only options needed by appropritate service.
Because OpenStack is also composed from various projects I think this solution
is the best.
What are you thinking about this? Do you have any other solution?
> Create Openstack Component
> --------------------------
>
> Key: CAMEL-9748
> URL: https://issues.apache.org/jira/browse/CAMEL-9748
> Project: Camel
> Issue Type: New Feature
> Reporter: Andrea Cosentino
> Priority: Minor
> Fix For: Future
>
>
> We can create a new big component related to Openstack by using
> http://www.openstack4j.com/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
