Xen project Mailing List

Def not SOAP-based. Uses the JSON descriptions provided by botocore[0], along with static type overrides from amazonka[1] to generate code that uses the query API.

The error parsing's a little busted right now (produces unhelpful messages), which is the last thing that needs to be fixed before it can be released. I'll try and dedicate some time to it this week. Mindy, if you want to get a head start I can give you access the the repo before the release.

-Spiros E.

[0]:Âhttps://github.com/boto/botocore

[1]:Âhttps://github.com/brendanhay/amazonka

On Mon, Nov 23, 2015 at 11:20 AM, Anil Madhavapeddy <anil@xxxxxxxxxx> wrote:

> On 23 Nov 2015, at 16:19, Gareth Rushgrove <gareth@xxxxxxxxxxxxxxxxx> wrote:
>
> On 23 November 2015 at 16:05, Anil Madhavapeddy <anil@xxxxxxxxxx> wrote:
>> On 23 Nov 2015, at 12:08, Mindy <mindy@xxxxxxxxxxxxxxxxxxx> wrote:
>>>
>>> Hi folks!
>>>
>>> I'm itching to replace the janky shell script[1] I use to deploy my unikernel blog to EC2 with something less hacky, ideally in OCaml so I don't need another set of tools in addition to the ones I use to build things with Mirage.Â I recall talk of OCaml libraries for interfacing with Amazon Web Services some months ago; can anyone speak to whether they've used such a thing (or libraries for interfacing with another cloud provider)?
>>>
>>> [1] - https://gist.github.com/yomimono/9559263
>>
>> I would really really really also like to replace my very shaky shell script with something more Cohttp-based.
>>
>> I think the most mature effort is by Spiros, and involves a full WSDL compiler -> OCaml. This ensures that it's actually possible to maintain against the upstream EC2 APIs. Spiros, are these available yet or still under development?
>>
>
> The EC2 SOAP API is deprecated. In 8 days that API will stop working.
> So I'm guessing that route won't work out alas.
>
> http://docs.aws.amazon.com/AWSEC2/latest/APIReference/using-soap-api.html
>
> The scale of these APIs is past the point where manually maintaining
> clients is sane, so auto-generating them is definitely the way to go.
> The AWS Go clients have some prior-art which might be a useful
> starting point.
>
> https://github.com/aws/aws-sdk-go/blob/master/service/generate.go
>
> All the new Azure clients are also going that way. You can see the
> generators here:
>
> https://github.com/Azure/autorest/tree/master/AutoRest/Generators

Here's hoping that Spiros' version isn't a SOAP-based generator... :-)

-anil

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

Re: [MirageOS-devel] ocaml libraries for interfacing with cloud providers?