On 08/30/2016 02:38 AM, Unix SA wrote: >> It sounds like the feature you want is to be able to select multiple >> content views and export/import them into a different satellite, without >> having to work with content at the repository level. > > yes, that's right, but i have question, > > - I have CV with repositories like “Kickstart”, “7 Server rpms”, > “Software collection”, “custom repository”, now after I export contents for > this CV, how can I sync individual repositories on “Downstream” Satellite > ?? or I need to create one custom repository and sync everything there ?? > if yes, then I will not need to enable repositories in RedHat > subscriptions, will kickstart and all work ?? > > > How can I manage above scenario?
I set up an example with Product A and B with a CV named "CV1" and repos "zoo" and "zoo2". I also synced RHEL 7.2 kickstart. After exporting version #2 of CV1, it created a dir structure like this: Repo A: /var/lib/pulp/katello-export/Default_Organization-CV1-v2.0/Default_Organization/content_views/CV1/2.0/custom/A/zoo/ Repo B: /var/lib/pulp/katello-export/Default_Organization-CV1-v2.0/Default_Organization/content_views/CV1/2.0/custom/B/zoo2/ kickstart: /var/lib/pulp/katello-export/Default_Organization-CV1-v2.0/Default_Organization/content_views/CV1/2.0/content/dist/rhel/server/7/7.2/x86_64/kickstart/ If I wanted to import these on the downstream sat, the easiest way would be to create two custom repos for zoo and zoo2, and enable kickstart by setting my cdn url to http://upstream/<exported prefix>/Default_Organization-CV1-v2.0/Default_Organization/content_views/CV1/2.0/. At that point, I should be able to enable the 7.2 kickstart repo. I could also just create a third custom repo with the 7.2 kickstart content instead of using the CDN url functionality, either should work ok. > >> Just confirming, your production Katello instance is able to connect to >> the engineering instance via http or https, it just can't connect to the >> internet. Is this correct? > > our requirement is to sync tested contents from "upstream" to downstream > satellite, and it can be http/https > > The sync should work, similar to how RedHat repositories sync work when we > give URL like https://cnd.redhat.com/ and it takes care of where the > contents are. So you only update “Downstream” satellite’s URL to > https://upstream.satellite.com, and just enable repositories and sync > contents. ( from exported repositories or CVs > -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
