Open Stack

+1 for commas. Configuration files with JSON is OK but commas for CLIs.

Tim

From: John Dewey [mailto:john at dewey.ws]
Sent: 27 January 2015 23:12
To: Jesse Keating
Cc: openstack-operators at lists.openstack.org
Subject: Re: [Openstack-operators] Specifying multiple tenants for aggregate_multitenancy_isolation_filter



On Tuesday, January 27, 2015 at 2:03 PM, Jesse Keating wrote:
On 1/27/15 1:54 PM, Sam Morrison wrote:
Hi operators,

I have a review up to fix this filter to allow multiple tenants, there
are 2 proposed ways in which this can be specified.

1. using a comma e.g., tenantid1,tenantid2
2. Using a json list eg. [“tenantid1”, “tenantid2”]

Which one do you think is better?

https://review.openstack.org/148807

Is this intended to be written by a human using the command line tools,
or to be filled in via other methods?

For command line tools, making it json seems wrong, and a comma list
would be more friendly. Internally the command line tools could easily
format it as a json list to pass along.
Yeah, I agree with this perspective.


What do the other various things that take lists expect? I'd say that's
more of a consideration too, uniformity across the inputs.

--
-jlk

_______________________________________________
OpenStack-operators mailing list
OpenStack-operators at lists.openstack.org<mailto:OpenStack-operators at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20150128/091dbcd5/attachment.html>