Hide Forgot
3. What is the nature and description of the request? OpenStack Swift support for docker-registry 4. Why does the customer need this? (List the business requirements here) To be able to use swift as storage for docker-registry 5. How would the customer like to achieve this? (List the functional requirements here) https://docs.openshift.com/enterprise/3.1/install_config/install/docker_registry.html#production-use 6. For each functional requirement listed in question 5, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. 7. Is there already an existing RFE upstream or in Red Hat bugzilla? > https://github.com/openshift/origin/issues/4672 8. Does the customer have any specific timeline dependencies? > no 9. Is the sales team involved in this request and do they have any additional input? > no 10. List any affected packages or components. 11. Would the customer be able to assist in testing this functionality if implemented? > yes
I'm not sure I'm clear on the ask here. Swift storage should be available with the PR https://github.com/openshift/origin/pull/6400. In the "How would the customer like to achieve this?" you're pointing to the persistent storage documentation for the registry. Is this indicating that you are requesting support via PVCs for this and cannot achieve it today? Brad, can you weigh in here on using swift storage as a volume in Kube?
Yes, they want to be able to have it for the registry storage. I've pointed to the docs as this what they want as end result but with a swift backend.
Can be achieved with 3.2 by editing the registry conf: https://docs.openshift.com/enterprise/3.2/install_config/install/docker_registry.html#advanced-overriding-the-registry-configuration https://docs.docker.com/registry/configuration/
(In reply to Marcel Wysocki from comment #3) > Can be achieved with 3.2 by editing the registry conf: > > https://docs.openshift.com/enterprise/3.2/install_config/install/ > docker_registry.html#advanced-overriding-the-registry-configuration > > https://docs.docker.com/registry/configuration/ Can this card be marked complete then? https://trello.com/c/FdPp5wn2/691-openstack-swift-support-for-registry ^^ I also don't see docs on configuring the registry for swift.
QE already succeed to enable openshift swift backend storage for docker-registry following the docs mentioned in comment 3, run some sanity testing, it is working well. So I think what we need do is to add it into our docs.
BTW, during testing, seem like I found a bug in https://docs.docker.com/registry/configuration/. "rootdirectory" option take no effect for swift backend storage, it should be "prefix".
*** Bug 1342293 has been marked as a duplicate of this bug. ***
https://github.com/openshift/openshift-ansible/pull/1937 I created this ad-hoc ansible playbook for user use-case here.
Can not reproduce BZ#1342293, after scale docker-registry to 2, sti build/docker push are completed successfully. But I also found the same error log in docker-registry log (seem like it is harmless in my cluster, because my build and docker push succeed).
I believe that this documentation is already covered in a recent update that points to upstream storage configuration: https://github.com/openshift/openshift-docs/pull/1917
Re-test this bug on a container install against atomic-openshift-3.2.1.1-1.git.0.96f9555.el7.x86_64, scale docker-registry to 2, everything is working well. About error message described in BZ#1342293, I reproduced it in last testing mentioned in comment 10, while in today's testing, I even can not reproduce it this time. So personally I think the error described in BZ#1342293 is caused by openstack swift performance issue, but not openshift issue.
(In reply to Paul Weil from comment #11) > I believe that this documentation is already covered in a recent update that > points to upstream storage configuration: > https://github.com/openshift/openshift-docs/pull/1917 There are Origin docs referencing Swift here (as noted by pweil) which are not yet in the OSE docs (not yet supported): https://docs.openshift.org/latest/install_config/install/docker_registry.html#registry-configuration-reference Some content referencing these storage drivers accidentally got downstream to OSE 3.1 and 3.2 around 3.2 GA, which was corrected last week: https://docs.openshift.com/enterprise/3.2/welcome/revhistory_full.html#fri-jun-03-2016 https://docs.openshift.com/enterprise/3.1/welcome/revhistory_full.html#fri-jun-03-2016