Bug 1308978 - [Doc] [Director] Need to add a guide for configuring a deployment with SAT5. [NEEDINFO]
[Doc] [Director] Need to add a guide for configuring a deployment with SAT5.
Status: POST
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation (Show other bugs)
7.0 (Kilo)
Unspecified Unspecified
unspecified Severity high
: ga
: 7.0 (Kilo)
Assigned To: Dan Macpherson
Alexander Chuzhoy
: Documentation
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-02-16 10:58 EST by Alexander Chuzhoy
Modified: 2017-09-12 01:37 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
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: ---
dmacpher: needinfo? (sasha)


Attachments (Terms of Use)

  None (edit)
Description Alexander Chuzhoy 2016-02-16 10:58:37 EST
[Doc] Need to add a guide for configuring a deployment with SAT5.


The undercloud node is registered with:
 sudo rhnreg_ks --activationkey=[key] --serverUrl=https://[SAT5 FQDN]/XMLRPC --sslCACert=/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT  --force


The overcloud deployment command should include:
--rhel-reg --reg-method satellite --reg-sat-url https://[SAT5 FQDN]  --reg-org [ORG ID] --reg-activation-key [KEY] --reg-force
Comment 7 Dan Macpherson 2017-09-12 01:37:13 EDT
Hi Sasha,

I'm clearing out my backlog and saw this bug. What did you want to do about it? Here's the current content for Overcloud registration:

https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/11/html/advanced_overcloud_customization/sect-registering_the_overcloud

And there's an example for Sat 5:

https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/11/html/advanced_overcloud_customization/sect-registering_the_overcloud#example_3_registering_to_a_red_hat_satellite_5_server

Do we need anything further with this BZ?

Note You need to log in before you can comment on or make changes to this bug.