[openstack-dev] [Ironic] How to deal with microversions in 3rdparty tools

Jim Rollenhagen jim at jimrollenhagen.com
Tue Apr 7 13:15:12 UTC 2015

I’m not sure that recommending one or the other is best.

We should lay out the options (as you just did) and let folks decide
what works best for them. For things like discoverd, where you have
many users, perhaps you should allow the user to pass a version (for
example, option 2 depends on the user running an Ironic version
that has a 1.6 at all — they could be at 1.4). For things like the
dashboard my team runs internally, we’ll be passing “latest” to the
API (we don’t use the client). We know we can move fast, and our
dashboard being broken for a short time following a deploy isn’t
the end of the world.

Hope that helps. :)

// jim

On April 7, 2015 at 6:07:57 AM, Dmitry Tantsur (dtantsur at redhat.com) wrote:

Hi again, hope you're not tired of this topic :D  

I'm seeking for advice on what to do with microversions in discoverd.  
Basically I have the following options:  

1. Do nothing. Get whatever behavior I can get from installed Ironic and  
Ironic client. Though unlikely, may get broken by future changes.  

2. Demand version = 1.6. Looks like it keeps compatibility with old  
clients and servers, not sure what downsides are here.  

What are we going to recommend now as upstream?  


OpenStack Development Mailing List (not for usage questions)  
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150407/d6dd2dc7/attachment.html>

More information about the OpenStack-dev mailing list