On 08/30/2016 11:30 PM, Unix SA wrote: > Thanks Chris, > > i figured out yesterday, i have created CV with "RHEL7.2 kickstart", > "RHEL7.2 rpms", "RHEL7.2 software collections", "Satellite tools 6.2 for > RH7", and did export. > > after export is completed i created "Link" for content directory > > lrwxrwxrwx. 1 root root 68 Aug 30 11:04 content -> > CV-export_test-v4.0/ORG/content_views/export_test/4.0/content > > and in "downstream", i have added URL like "http://upstream/katello-export"; > > and now i am able to enable all above repositories without any issues.
Great, glad to hear things are working. > > Only thing i am having problem is, if i have repositories in different CVs, > then that soft link to content directory will fail, so workaround i have to > do is, create BIG, CCV. with all cvs added and export that. ( Another thing > may be i can do is ( have not tried it ), export CV, and once export is > completed, move content directory from there to actual content directory ( > soft link, ), but not sure then how i will keep track of contents ). > > 1) if you can give me example of 2 or more CV export and sync ( not custom > repos, redhat only ), without changing URL in manifest Currently the manifest URL has to be changed for this, since there can only be one manifest URL set per organization. You could use the --source-url option on the RH repo when syncing, but this just substitutes one type of URL replacement for another. > 2) in future may be any chances to improve so disk space can be saved. As a workaround, you may be able to symlink from /var/lib/pulp/katello-export to /var/lib/pulp/published/<path to rpm publish location> and sync from there. We have a backlog task to handle the connected sync scenario more gracefully, without having multiple copies of RPMs on disk. > > Regards, > DJ > > > On Wednesday, 31 August 2016 02:02:01 UTC+5:30, Chris Duryee wrote: >> >> >> >> 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.
