on executing RingBuild, builder files are created in current directory
Bug #1699741 reported by
Adeeb khan
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Object Storage (swift) |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
In swift RingBuild usecase, a user can create the builder files at any current directory. Ideally, these should be placed in /etc/swift. All the builder files and their backups will be stored even if they are built at some other path. This can be a performance risk as these files are never removed from the other directories.
make the creation of the builder file at an absolute path through the configuration file swift.conf
Revision history for this message
| Thiago da Silva (thiagodasilva) wrote | #1 |
| Changed in swift: | |
| status: | New → Won't Fix |
To post a comment you must log in.
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.