yes, that could be a workaround, but not appropriate solution. also exporting content again takes lot of space, i think it should create links similar to PULP.
anyone in katello development team can please comment ? if this is going to improve in future? On Saturday, 30 July 2016 00:18:22 UTC+5:30, Chris Duryee wrote: > > > > On 07/28/2016 11:21 PM, Unix SA wrote: > > Hi, > > > >>> Can you give more detail about your use case? It sounds like there are > >>> multiple users in the same org, each wanting to manage their own CV of > >>> exported content, and each with their own set of repos to import on > the > >>> downstream Katello server? > > > > that's correct, i have one satellite in Engineering and one in > Production ( > > downstream ), now we download contents from Redhat to our Engineering > > satellite test it and release it to Production. > > > > so for example, we have RHEL6.5 kickstart, RHE6.5 rpms, RHEL6 satellite > > tools in one content view, and RHEL7.2 kickstart, RHEL7.2 rpms, RHEL7 > > satellite tools in another content view, similar things will happen for > > RHEL7.3 later. apart from that we have other content views for > middleware, > > db and all. > > > > now i want to periodically allow production satellite to sync contents > from > > engineering satellite, using current approach, i will only able to sync > > either RHEL6 or RHEL7, unless i change URL > > > > ideally this export/import feature should allow, individual repository > > sync, by providing URL, that may work for custom contents but not sure > how > > it will work for RHEL contents. > > > > That is allowed today, but via hammer. If you use 'hammer repository > sync' with the '--source-url' option, you can set it to any URL desired. > > Unfortunately, it's difficult to import from multiple CVs without > changing the URL, since the CDN URL is tied to the organization/manifest > and not to a particular product or repo. One workaround would be to set > your CDN URLs and enable repos to get everything created, then use the > --source-url method above once the repos were created to sync content > down. > > > > Regads, > > DJ > > > > On Thursday, 28 July 2016 19:38:45 UTC+5:30, Chris Duryee wrote: > >> > >> > >> > >> On 07/27/2016 11:47 PM, Unix SA wrote: > >>> Well that's not the right way, if it allows to export CV version, it > >> should > >>> allow different CVs, also i dont want to mix my contents in single CVs > >> as > >>> there are different people manage their own CVs, also why i will > include > >> my > >>> RHEL6.5 and RHEL7 in single content view? > >>> > >> > >> The tricky part is that if you are using the CDN URL to manage the > >> import location, the exported contents need to be in the same tree > >> format as what Katello expects. > >> > >> Can you give more detail about your use case? It sounds like there are > >> multiple users in the same org, each wanting to manage their own CV of > >> exported content, and each with their own set of repos to import on the > >> downstream Katello server? > >> > >> > >>> Regards, > >>> DJ > >>> > >>> On Wednesday, 27 July 2016 18:36:36 UTC+5:30, Chris Duryee wrote: > >>>> > >>>> > >>>> > >>>> On 07/27/2016 04:38 AM, Unix SA wrote: > >>>>> > >>>>> Hello, > >>>>> > >>>>> I am following procedure below to sync contents from my upstream > >>>> satellite > >>>>> to downstream. > >>>>> > >>>>> > >>>> > >> > https://access.redhat.com/documentation/en/red-hat-satellite/6.2-beta/paged/content-management-guide/appendix-c-synchronizing-content-between-satellite-servers > > >>>>> > >>>>> now after updating my organization to URL mention in document, i am > >> able > >>>> to > >>>>> sync one CV > >>>>> > >>>>> "" > >>>>> > >>>>> $ hammer organization update \ > >>>>> --name "Mega Subsidiary" \ > >>>>> --redhat-repository-url \ > >>>>> http://megacorp.com/pub/cdn-latest > >>>>> > >>>>> Organization updated > >>>>> """ > >>>>> > >>>>> but for another CV, the URL is different, do i have to update URL > >>>> everytime when i want to sync different CVs ? or am i missing > >> something? > >>>>> > >>>>> > >>>>> Procedure i followed is:- > >>>>> 1) set export path to /var/lib/html/pub/export > >>>>> 2) set selinux permissions > >>>>> 3) set "immediate" for my RHEL7 kickstart repository > >>>>> 4) export repository with "hammer repository export --id 2 > >>>> --export-to-iso > >>>>> 0" > >>>>> 5) in downstream URL update manifest with URL > >>>>> " > >>>> > >> > https://upstream/pub/export/ORG-Red_Hat_Enterprise_Linux_Server-Red_Hat_Enterprise_Linux_7_Server_Kickstart_x86_64_7_2/ORG/Library/"; > > > >> > >>>> > >>>>> > >>>>> sync works for "kickstart" , but then how to sync for "rpm > repository" > >>>> now > >>>>> as URL will be different for it? > >>>>> > >>>>> Regards, > >>>>> DJ > >>>>> > >>>> > >>>> Typically, the easiest way to do this is to create a single CV that > has > >>>> all the content you'd like to export. That way if you export multiple > >>>> items, the CDN url on the downstream server stays the same. > >>>> > >>> > >> > > > -- 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.
