Confuson about which user to use in SAIO documentation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Object Storage (swift) |
Fix Released
|
Low
|
Kun Huang |
Bug Description
The documentation http://
"So, swift:swift ought to be used in every place where this manual calls for <your-user-
This doesn't seem right. Isn't the swift user meant to be running the daemons? He doesn't have a home dir nor a login shell. If this was intended, I would expect that the manual would directly say "swift" instead of "<your-user-name>".
Also, it's sometimes unclear if you should be running commands as root or as a normal user. I guess there should be a note about using a normal account in the "Getting the code and setting up test environment" and "Setting up scripts for running Swift" sections.
Changed in swift: | |
assignee: | nobody → Kun Huang (academicgareth) |
Changed in swift: | |
milestone: | none → 1.9.0 |
Changed in swift: | |
status: | Fix Committed → Fix Released |
I'm not sure why the Fedora guide differs form the Ubuntu guide in this regard? I've apparently never looked at it too closely.
On my development saio (which happens to be ubuntu), there is no swift user or group. Swift is installed from git, and all the configuration and starting of swift services is done manually - according to the description in the rest of the guide. For my development machine, all services run as the same user I log in with (clayg as it happens) - and so that's what I put where the configs call for <your-user-name>.
If you installed the swift rpm's according to the fedora guide you may very well want the daemons to run as the swift user and artifacts to be owned by that user.
Otherwise, you may want to skip that first step:
yum install openstack-swift openstack- swift-proxy openstack- swift-account openstack- swift-container openstack- swift-object
And just install swift from source as described later:
http:// docs.openstack. org/developer/ swift/developme nt_saio. html#getting- the-code- and-setting- up-test- environment
I think it is confusing, defiantly a doc bug. Why should the Fedora instructions be so different. Maybe the original author will comment on this bug, or someone can spin up a Fedora vm and update the docs as appropriate. (You wanna do it?!)