[openstack-dev] [magnum] How to document 'labels'
jamie.hannaford at rackspace.com
Thu May 12 14:04:55 UTC 2016
+1 for 1 and 3.
I'm not sure maintainability should discourage us from exposing information to the user through the client - we'll face the same maintenance burden as we currently do, and IMO it's our job as a team to ensure our docs are up-to-date. Any kind of input which touches the API should also live in the API docs, because that's in line with every other OpenStack service.
I don't think I've seen documentation exposed via the API before (#2). I think it's a lot of work too, and I don't see what benefit it provides.
From: Hongbin Lu <hongbin.lu at huawei.com>
Sent: 11 May 2016 21:52
To: OpenStack Development Mailing List (not for usage questions)
Cc: Qun XK Wang
Subject: [openstack-dev] [magnum] How to document 'labels'
This is a continued discussion from the last team meeting. For recap, 'labels' is a property in baymodel and is used by users to input additional key-pair pairs to configure the bay. In the last team meeting, we discussed what is the best way to document 'labels'. In general, I heard three options:
1. Place the documentation in Magnum CLI as help text (as Wangqun proposed ).
2. Place the documentation in Magnum server and expose them via the REST API. Then, have the CLI to load help text of individual properties from Magnum server.
3. Place the documentation in a documentation server (like developer.openstack.org/...), and add the doc link to the CLI help text.
For option #1, I think an advantage is that it is close to end-users, thus providing a better user experience. In contrast, Tom Cammann pointed out a disadvantage that the CLI help text might be easier to become out of date. For option #2, it should work but incurs a lot of extra work. For option #3, the disadvantage is the user experience (since user need to click the link to see the documents) but it makes us easier to maintain. I am thinking if it is possible to have a combination of #1 and #3. Thoughts?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev