Split synchronizing content by sync type about foreman-documentation

[jeremylenz]

It's always been three "types of ISS" in my mind because it's three different ways of getting content from one Satellite to another. But as far as what the physical connections look like, there are only two.

ISS use case	Physical configuration	What you select in Manifest modal on the disconnected Satellite	How you transfer data between Satellites
Pulpcore import/export	Fully disconnected (Air-gapped)	Export Sync	hammer content-export
Syncable exports/imports	Fully disconnected (Air-gapped)	Export Sync	hammer content-export --format syncable
Network Sync	"Disconnected"	Network Sync	The "disconnected" Satellite consumes content from the connected Satellite

Physical configuration	Description
Fully disconnected (Air-gapped)	The disconnected Satellite is physically disconnected from the internet and all other networks.
"Disconnected"	The "disconnected" Satellite cannot communicate with the Internet, but can communicate over the network with the connected Satellite.

To answer your questions @maximiliankolb, none of these use cases have backups in mind. They are all for operating Satellites that are disconnected from the Internet. For the fully disconnected (air-gapped) configuration, Syncable import/export has some advantages over pulpcore import/exports, mainly that you don't have to have matching Satellite versions.

cc @parthaa who may have more commentary.

[maximiliankolb]

What's the third type of ISS?

• Export sync: ✔️
• Network sync: ✔️
• ???
• misusing (?) ISS for backups: is that somehow possible?

In general, I'd be open to moving the thing to a standalone guide with a bit more context on when to use which procedure. It's currently part of the Managing Content guide. Note that build target "satellite" renders things a bit differently.

If we "just" split it into three assemblies, I'd also consider this a true improvement!

cc @bangelic

[bangelic]

I believe the third type of ISS is Syncable exports & imports - use hammer content-export --format syncable.

[maximiliankolb]

What the intented use case for this? Does it overlap with the other two use cases above? Is it for backups?

[adamlazik1]

I believe @jeremylenz could provide more insight.

[parthaa]

As @jeremylenz said. I'd categorize both regular Import/Export & Syncable Import/Export as Export Sync (as jeremy's table indicates).