Comment 1 for bug 1699741
Revision history for this message
| Thiago da Silva (thiagodasilva) wrote | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I think this is done by design. I can think of at least a couple of scenarios where I don't want to have the ring-builder write directly to /etc/swift.
1. I might be using a staging node that is not part of the swift cluster to build the ring, so it doesn't make sense to copy to /etc/swift.
2. I want to inspect the result of ring building before moving and overwriting whatever is in /etc/swift. So I prefer to write to a temp directory and copy to /etc/swift later on all nodes of the cluster.
Please feel free to re-open this bug in case I did not understand your original description.