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 <[email protected]> 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 <[email protected]>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<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
>>
>
>
