Assigning to Stephen for review.

Hello


The part in the 6.1 guide "Disconnected Satellite" is similar too:

Recommended Practices for Deploying Satellite 6 in Disconnected/Air-Gapped Environments — https://access.redhat.com/articles/1375133

That KBase article has links to 6.0 guides. I should fix that when this bug is resolved.

Hello


How about this section:

Appendix B. Importing Content ISOs into a Disconnected Satellite[1]

Would it be enough if we just linked to that?

There is a link to it from the Architecture Guide, in the "Disconnected Satellite" section[2], where it says:

"The above methods for importing content to a disconnected Satellite Server can also be used to speed up the initial population of a connected Satellite. "

Thank you

[1] https://access.redhat.com/documentation/en-us/red_hat_satellite/6.2/html/content_management_guide/importing_content_isos_into_disconnected_satellite

[2] https://access.redhat.com/documentation/en-us/red_hat_satellite/6.2/html-single/architecture_guide/#sect-Red_Hat_Satellite-Architecture_Guide-Disconnected_Satellite

> Would it be enough if we just linked to that?
I don't think so. If it's applicable to online (connected) satellite, the note should be added into the section about online (conntected) satellite.

(In reply to Satoru SATOH from comment #5)
> > Would it be enough if we just linked to that?
> I don't think so. If it's applicable to online (connected) satellite, the
> note should be added into the section about online (conntected) satellite.

Hello Satoru, I wonder if we have a slight misunderstanding? I meant link to that section "Importing Content ISOs into a Disconnected Satellite" from various places in the guide.

For example, from the intro to  section "Synchronizing Content"[1]

We can also add a paragraph to the intro to "Importing Content ISOs into a Disconnected Satellite" to say you can also use it for initial sync of connected (online) Satellite.

I will check also in the Installation Guide for a suitable place.

Let me know if that sounds better.

Thank you

[1] https://access.redhat.com/documentation/en-us/red_hat_satellite/6.2/html/content_management_guide/importing_red_hat_content#Importing_Red_Hat_Content-Synchronizing_Content

Hello again

I think we need to resolve this bug[1] about the placement of the manifest sections in the Installation Guide first, before we try and add links from the Installation Guide to the "Importing Content ISOs into a Disconnected Satellite" section in the Content Management Guide.



[1] Bug 1448927 - Manifest section should be moved

(In reply to Stephen Wadeley from comment #6)
> (In reply to Satoru SATOH from comment #5)
> > > Would it be enough if we just linked to that?
> > I don't think so. If it's applicable to online (connected) satellite, the
> > note should be added into the section about online (conntected) satellite.
> 
> Hello Satoru, I wonder if we have a slight misunderstanding? I meant link to
> that section "Importing Content ISOs into a Disconnected Satellite" from
> various places in the guide.
> 
> For example, from the intro to  section "Synchronizing Content"[1]
> 
> We can also add a paragraph to the intro to "Importing Content ISOs into a
> Disconnected Satellite" to say you can also use it for initial sync of
> connected (online) Satellite.

If my understanding is correct, the way you mentioned is intended to use for disconnected Satellite only because it requires to replace all of RH CDN URLs to local ones.

---------------------------------------------------------------------------
     The Satellite Server now contains the content from the Content ISOs. However, the Satellite Server needs to point to this location as the CDN URL. In the Satellite Web UI, navigate to Content > Red Hat Subscriptions. .
    Click Manage Manifest.
    On the Subscription Manifest information screen, select the Actions tab.

    Scroll to Red Hat Provider Details. Click the edit icon on the Red Hat CDN URL and change the URL to the Satellite host name with the newly created directory, for example:

    http://server.example.com/pub/sat-import/
    Click Save and then upload your manifest using Section 3.4, “Importing a Subscription Manifest into the Satellite Server”. 

The Satellite is now acting as its own CDN with the files located in http://server.example.com/pub/sat-import/. This is not a requirement. The CDN can be hosted on a different machine inside the same disconnected network as long as it is accessible to the Satellite Server using HTTP. 
---------------------------------------------------------------------------

[https://access.redhat.com/documentation/en-us/red_hat_satellite/6.2/html/content_management_guide/Importing_Content_ISOs_into_Disconnected_Satellite]

On the other hand, the way I noted does not require to modify RH CDN URLs, AFAIK.

> Satellite 6.1 Installation Guide, 4.1.4. Using a Content ISO for Initial Synchronization: https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html/Installation_Guide/chap-Red_Hat_Satellite-Installation_Guide-Populating_Red_Hat_Satellite_with_Content.html#sect-Red_Hat_Satellite-Installation_Guide-Alterante_CS

Hello Satoru

Re comment 8

Sorry I missed that important difference in the procedures.


What do you feel about this bit:
Such synchronization is not limited by network bandwidth and therefore is usually faster, especially when synchronizing large repositories for the first time.


Given that 6.2 has Download Policy settings of "On Demand" and "Background", I wonder if the total time taken to download the ISOs, configure the local repos, and later remove local repo configs, is really faster.

Perhaps a statement like this is in order?

For locations with bandwidth limitations, using an *On Demand* or *Background* download policy might be more efficient than downloading and importing Content ISOs.



Thank you

Hello


These changes are now live on the customer portal.


Importing Content ISOs into a Connected Satellite

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.2/html/content_management_guide/importing_content_isos_into_connected_satellite



Thank you