[OpenStack-DefCore] Image APIs in Glance and Nova

Mark Voelker mvoelker at vmware.com
Wed Jun 17 19:42:47 UTC 2015


> try the approaches from an approved/accepted scenarios list and report which ones work and which ones don’t.

So that’s baaaasically what developers have to do today, and it stinks for them.  Monty has elaborated on this at length, but in a nutshell you end up writing all manner of if/else loops into your code to deal with all the peculiarities of different clouds you might want to use.  If DefCore is successful, it means a lot of these if/else situations will go away because anytime you’re using an OpenStack Powered Platform, you can depend on a certain set of capabilities to be available to you.  

Interoperability by if/else loop isn’t interoperability at all.

> If we can't know which paths/workflows a deployer has used

RefStack should eventually help us understand exactly that, since it’ll provide data on all the tests that pass/fail (not just what’s currently DefCore-required).  But it’s early days...

At Your Service,

Mark T. Voelker

> On Jun 17, 2015, at 2:52 PM, Daryl Walleck <daryl.walleck at RACKSPACE.COM> wrote:
> 
> 
>>> To list images, the user could:
>>> * use nova to list images (stable, but project wants to delete it)
>>> * use glance v1 (should never be exposed to end users, was designed as
>>> internal only API)
>>> * use glance v2 (only just fully released (kilo?), not deployed everywhere, yet)
>>> * glance is building a new v3 API (user could help implement that, I suppose)
> 
>> Now I think the best way forward here is to pick the Nova list images,
>> for the moment.
> 
>> Problem 2:
>> Upload an image
> 
>> I would argue there is no truly interoperable way to do this right
>> now. Glance currently has three ways to upload an image, and no way to
>> know which the deployer has picked.
> 
> I think this where the "let things that aren't implemented fail" comes into play. If we can't know which paths/workflows a deployer has used, try the approaches from an approved/accepted scenarios list and report which ones work and which ones don't. Even if only one of those scenarios is the approved or blessed path, I think it would also be helpful for identifying and gathering data around which scenarios deployers support/use the most.
> 
> Daryl
> _______________________________________________
> Defcore-committee mailing list
> Defcore-committee at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee



More information about the Defcore-committee mailing list