The base approach would be to implement the ComputeServiceAdapter interface [1] (it has just a few methods), and create a subclass of the ComputeServiceAdapterContextModule to configure the bindings for your compute implementation.
Basically those bindings will provide functions to transform your domain objects (VMs, etc) to the jclouds domain objects (Location, Node, Image). Those objects are the ones used in the ComputeService interface, and jclouds will take care of transforming them to your domain model. openstack-nova, even if it performs much more than what you need should be a good example to follow in both cases. [1] https://github.com/jclouds/jclouds/blob/master/compute/src/main/java/org/jclouds/compute/ComputeServiceAdapter.java On 4 July 2013 13:53, fivos <fivos....@gmail.com> wrote: > Hi I looked at the standalone-compute skeleton and it definitely looks it is > what I need, a server-manager for the new provider, just creating VMs, > pausing, resuming them etc. > > i can't understand though how I will be able to still use code like : > > ComputeServiceContext context = ContextBuilder.newBuilder(provider) > .credentials(username, apiKey) > .overrides(overrides) > .buildView(ComputeServiceContext.class); > compute = context.getComputeService(); > > > since in the skeleton the ComputeService interface is not implemented. On > the other hand implementations of ComputeService in providers such as > openstack-nove look far too complicated and include many unnecessary to me > features. > > > > On Tue, Jun 25, 2013 at 5:48 PM, fivos <fivos....@gmail.com> wrote: >> >> Thanks for the fast reply, It's a compute provider so I will have a look >> at the link you provided >> >> >> On Tue, Jun 25, 2013 at 5:34 PM, Andrew Phillips <andr...@apache.org> >> wrote: >>>> >>>> Hi I was looking into adding basic support for a cloud provider that is >>>> not >>>> supported at the time being (Flexiant Cloud Orchestrator). I have >>>> managed >>>> to do this using Dasein but I am not sure how to proceed in jclouds. >>> >>> >>> Is this a compute provider, or a blobstore? For a compute provider you >>> can have a look at: >>> >>> >>> https://github.com/jclouds/jclouds/tree/master/skeletons/standalone-compute >>> >>> And of course please feel free to ask question here or (more likely) on >>> the dev@ list, or hop on to IRC! >>> >>> Regards >>> >>> ap >> >> >
