Bug 1661809

Summary: python-swift not installed on UC or OC Controller nodes in '14 -p 2018-12-07.2'
Product: Red Hat OpenStack Reporter: Mike Abrams <mabrams>
Component: python-swiftclientAssignee: Christian Schwede (cschwede) <cschwede>
Status: RELEASE_PENDING --- QA Contact: Mike Abrams <mabrams>
Severity: high Docs Contact: Laura Marsh <lmarsh>
Priority: high    
Version: 14.0 (Rocky)CC: cschwede, derekh, dmacpher, lmarsh, tenobreg, zaitcev
Target Milestone: ---Keywords: Triaged, ZStream
Target Release: ---Flags: cschwede: needinfo-
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Comment 2 Christian Schwede (cschwede) 2019-01-03 09:52:12 UTC
Mike and me discussed this moments ago. Actually there are two commands involved that are no longer directly available on the UC/OC nodes, because these are much more lightweight with everything running in the containers nowadays.

For the swift-ring-builder command, it would be sufficient to just execute it directly within the containers. For example:

docker exec -ti -u swift swift_object_server swift-ring-builder /etc/swift/object.builder

For the swift CLI itself, one would need to install the rpm. 

That said, I think this one needs no code fix, but a doc note.

Comment 9 Dan Macpherson 2019-01-22 03:08:33 UTC
Hi Laura,

Was doing a review of the director guide content and came across this item. I think the "Managing containerized services" module isn't the best place for it -- This module is really just for basic container management commands. The content you put together is something more so specific to Swift rather than containers in general. So it might be a good idea to put together a standalone "Managing object storage" module.

Any chance we can put this new content in its own module?

- Dan