On 8/28/2015 2:38 AM, Tim Bell wrote:
-----Original Message-----
From: Matt Riedemann [mailto:[email protected]]
Sent: 28 August 2015 02:29
To: [email protected]
Subject: Re: [openstack-dev] --detailed-description for OpenStack items
On 8/27/2015 12:23 PM, Tim Bell wrote:
Some project such as cinder include a detailed description option
where you can include an arbitrary string with a volume to remind the
admins what the volume is used for.
Has anyone looked at doing something similar for Nova for instances
and Glance for images ?
In many cases, the names get heavily overloaded with information.
Tim
__________________________________________________________
____________
____ OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
[email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
The nova instances table already has a display_description column:
http://git.openstack.org/cgit/openstack/nova/tree/nova/db/sqlalchemy/mo
dels.py#n287
Couldn't that just be used? It doesn't look like the nova boot command in
the CLI exposes it though. Seems like an easy enough add.
Although the server create API would have to be changed since today it just
sets the description to be the same as the name:
http://git.openstack.org/cgit/openstack/nova/tree/nova/api/openstack/co
mpute/servers.py#n589
That could be enabled with a microversion change in mitaka though.
This would be great. I had not checked the schema, only the CLI.
Should I submit a bug report (or is there a way of doing an enhancement
request) ? A display function would also be needed in Horizon for the novice
users (who are the ones who are asking for this the most)
Tim
--
Thanks,
Matt Riedemann
__________________________________________________________
________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-
[email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Tim, sounds like a perfect case of writing a backlog spec that then one
of the developers in nova can pick up for mitaka:
http://git.openstack.org/cgit/openstack/nova-specs/tree/README.rst#n57
--
Thanks,
Matt Riedemann
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev