Hello, Duncan and Monty,

The discussion is more and more concrete, very good.

"maybe we should just slap a REST api on it". The challenge of Node-pool REST 
API is "What it will look like for these API, totally new API? current OS-API 
?". From cloud operators' feed back, OS-API is preferred. If we developed 
totally new API for Node-pool, it takes long time to grow API-ecosystem or 3rd 
party APP for it.

Best Regards
Chaoyi Huang ( joehuang )

-----Original Message-----
From: Duncan Thomas [mailto:duncan.tho...@gmail.com] 
Sent: Tuesday, October 07, 2014 11:44 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [all] [tc] Multi-clouds integration by OpenStack 

On 7 October 2014 16:30, Monty Taylor <mord...@inaugust.com> wrote:

> Second BTW - you're certainly right about the first two in the global 
> list - we keep track of quota and usage ourselves inside of nodepool.
> Actually - since nodepool already does a bunch of these things - maybe 
> we should just slap a REST api on it...

Whether or not it does much for this use-case, Nodepool-aaS would definitely be 
useful I think, particularly if it was properly multi-tenant. It isn't /hard/ 
to set up, but it's effort and yet another cog to understand and debug.

OpenStack-dev mailing list

Reply via email to