Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1812591

Summary: Why are the ceph repositories/containers Opt-Out instead of Opt-In?
Product: Red Hat OpenStack Reporter: David Vallee Delisle <dvd>
Component: openstack-tripleoAssignee: James Slagle <jslagle>
Status: CLOSED DUPLICATE QA Contact: Arik Chernetsky <achernet>
Severity: medium Docs Contact:
Priority: medium    
Version: 16.0 (Train)CC: aschultz, mburns
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-11 16:29:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description David Vallee Delisle 2020-03-11 16:05:20 UTC
Description of problem:
When deploying OSP16 without anything Ceph related, we need to exclude the ceph repositories from the container-prepare-parameters and undefine the TripleO::Services as described here: https://access.redhat.com/solutions/4895201

We would like to confirm if there's any downside with doing this, and our customer was also wondering why it's an Opt-Out process instead of an Opt-In process.

There's some overhead work to either add these repos to satellite, or to disable the ceph services  like this.

Comment 1 Alex Schultz 2020-03-11 16:29:44 UTC
Because prior to containers we always shipped ceph in the overcloud-full image. This is a continuation of that.

*** This bug has been marked as a duplicate of bug 1726606 ***