Thank you for the clarification. I understand and agree with your thought it's clear enough. Thank you for your time and I highly appreciate your responses.
Best Regards, Hisashi Osanai On Thursday, July 24, 2014 2:16 PM, John Dickinson wrote: > Oh I totally agree with what you are saying. A DNS change may be lower > cost than running Swift config/management commands. At the very least, > ops already know how to do DNS updates, regardless of it's "cost", where > they have to learn how to do Swift management. > > I was simply adding clarity to the trickiness of the situation. As I said > originally, it's a balance of offering a feature that has a known cost > (DNS lookups in a large cluster) vs not offering it and potentially making > some management more difficult. I don't think either solution is all that > great, but in the absence of a decision, we've so-far defaulted to "less > code has less bugs" and not yet written or merged it. _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
