With regard to compute....Perhaps something akin to BES, with support for a very simple RESTful interface which creates RESTful resources for each request that can then be statuses, etc. I'd be happy to help writing up a use case. Krishna Sankar (ksankar) wrote:
IMHO, compute might be the next step and then storage. Cheers <k/>
|-----Original Message----- |From: occi-wg-bounces@ogf.org [mailto:occi-wg-bounces@ogf.org] On Behalf |Of Gary Mazz |Sent: Wednesday, June 10, 2009 1:24 PM |To: Edmonds, AndrewX; occi-wg@ogf.org |Subject: [occi-wg] What next next on the apis ? | |Hi | |Since there's been so much feedback on the cloud model/responsibilities |and the network attributes matrix, I was thinking about the next |analysis. should it be storage, cpu/mem. or ancillary ? | |-gary |_______________________________________________ |occi-wg mailing list |occi-wg@ogf.org |http://www.ogf.org/mailman/listinfo/occi-wg _______________________________________________ occi-wg mailing list occi-wg@ogf.org http://www.ogf.org/mailman/listinfo/occi-wg
-- Michael Behrens R2AD, LLC (571) 594-3008 (cell) (703) 714-0442 (land)