On Wed, 23 Jul 2014 08:54:30 -0700
John Dickinson wrote:
> So basically, it's a question of do we add the feature, knowing that
> most people who use it will in fact be making their lives more difficult,
> or do we keep it out, knowing that we won't be serving those who actually
> require the fea
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
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 th
Thank you for the quick response.
On Thursday, July 24, 2014 12:51 PM, John Dickinson wrote:
> you can actually do the same today
> with the IP-based system. You can use the set_info command of
> swift-ring-builder to change the IP for existing devices and this avoids
> any rebalancing in the cl
While your correct that a chassis replacement can avoid data rebalancing in the
FQDN case if you update DNS, you can actually do the same today with the
IP-based system. You can use the set_info command of swift-ring-builder to
change the IP for existing devices and this avoids any rebalancing i
I would like to discuss this topic more deeply.
I understand we need to prepare DNS systems and add a lot of operational
complexity and burden to use the DNS system when we use FQDN in Ring files.
However I think most datacenter have DNS systems to manage network resources
such as ip addresses
Using hostnames instead of IPs is, as mentioned above, something under
consideration in that patch.
However, note that until now, we've intentionally kept it as just IP addresses
since using hostnames adds a lot of operational complexity and burden. I
realize that hostnames may be preferred in
Hi,
Thank you for the info.
I was able to understand that hostname support is under developing.
Best Regards,
Kenichiro Matsuda.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/opens
Hi,
Here's a patch to allow hostname in Ring which is under developing you
might be interested in.
https://review.openstack.org/#/c/80421/
-Edward Zhang
"Matsuda,
