on executing RingBuild, builder files are created in current directory
Bug #1699740 reported by
Adeeb khan
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Object Storage (swift) |
Opinion
|
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
| Christian Schwede (cschwede) wrote | #1 |
| Changed in swift: | |
| status: | New → Opinion |
To post a comment you must log in.
I prefer to not build the ring files based on a setting in swift.conf (or any other configuration file, for that matter). Currently it's done based on the filename given on the command line, and that worked fine for years. Many operators are managing multiple clusters with different ring files, often not building on a cluster node (and therefore without any /etc/swift files). These files are then distributed to the nodes that need them.