Katello inter sync option

Support
1

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

2

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.

··· 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 >
3

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?

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. >
4

> 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?

··· On 07/27/2016 11:47 PM, Unix SA wrote:

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.

5

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.

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. > >> > > >
6

> 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.

··· On 07/28/2016 11:21 PM, Unix SA wrote:

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.

7

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. > >>>> > >>> > >> > > >
8

> 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.
>

Symlinks are not created today in case content is being exported to NFS
or needs to be copied to USB disk. If the servers are able to connect to
each other via http/https (i.e., no airgap), then it can be quite a use
of disk space for not much benefit.

> anyone in katello development team can please comment ? if this is going to
> improve in future?
>

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.

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?

The ability to import/export content views without delving into
repo-level operations has been discussed in the past and is on the
backlog, but I am not sure of its prioritization. I would say the best
bet is to put in a redmine issue if you are an upstream Katello user.

Another option may be to user hammer-cli-csv [1] and export/import your
CVs like that. You may need to export your content views and then edit
the CSV a bit to point to the correct exported repositories before
importing on the other side.

[1] https://github.com/Katello/hammer-cli-csv/

··· On 08/01/2016 03:51 AM, Unix SA wrote:

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.

9

>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?

>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

10

>> 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
>/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.

··· On 08/30/2016 02:38 AM, Unix SA wrote:

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

11

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.

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
  2. in future may be any chances to improve so disk space can be saved.

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/ >/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 > > >
12

> 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.

··· On 08/30/2016 11:30 PM, Unix SA wrote:

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

/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

13

Hi,

sorry coming back again, this time what i did is, created big CCV, and
created link

lrwxrwxrwx. 1 root root 81 Sep 1 07:07 content ->
/var/lib/pulp/published/yum/https/repos/ORG/content_views/CCV_test/2.0/content

Now, i am able to add URL to downstream satellite and able to sync, but
issue is, when sync is completed, i dont see any Erratas … i can see only
packages are synced, how do i see those Erratas as well ? ( there is no
filter added in CCV )

Regards,
DJ

··· On Wednesday, 31 August 2016 20:22:05 UTC+5:30, Chris Duryee wrote: > > > > 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/ 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/ >> > >/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 > >>> > >> > > >
14

> Hi,
>
> sorry coming back again, this time what i did is, created big CCV, and
> created link
>
> lrwxrwxrwx. 1 root root 81 Sep 1 07:07 content ->
> /var/lib/pulp/published/yum/https/repos/ORG/content_views/CCV_test/2.0/content
>
> Now, i am able to add URL to downstream satellite and able to sync, but
> issue is, when sync is completed, i dont see any Erratas … i can see only
> packages are synced, how do i see those Erratas as well ? ( there is no
> filter added in CCV )

Can you confirm that
/var/lib/pulp/published/yum/https/repos/ORG/content_views/CCV_test/2.0/content/repodata/-updateinfo
exists and contains errata XML? It should be a large xml file, it might
be gzipped.

··· On 09/08/2016 07:16 AM, Unix SA wrote:

Regards,
DJ

On Wednesday, 31 August 2016 20:22:05 UTC+5:30, Chris Duryee wrote:

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.

  1. 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/ 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

/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

15

here it is :-

[root@upstream repodata]# pwd
/var/lib/pulp/published/yum/https/repos/ORG/content_views/CCV_test/2.0/content/dist/rhel/server/7/7.2/x86_64/rhscl/1/os/repodata
[root@upstream repodata]#
[root@upstream repodata]#
[root@upstream repodata]# ls -ltr
total 13592
-rw-r–r--. 1 apache apache 93 Aug 30 06:12
325e4792e1c8e355251d07340f9915bc6fbac716e1eadf69ae5ecf92abd36f7f-updateinfo.xml.gz
-rw-r–r--. 1 apache apache 130 Aug 30 06:12
3e800f8eb4bfc89f8e320cda3dd709a8e0bef5f4884e3b622df63b17249e8242-comps.xml
-rw-r–r--. 1 apache apache 429326 Aug 30 06:12
0b0f6a624ade8c015c3c499b0b21eac60176c4d5-updateinfo.xml.gz
-rw-r–r--. 1 apache apache 93 Aug 30 06:12
c52f1349c09f6534368b08b646adf122362bc37f-updateinfo.xml.gz
-rw-r–r--. 1 apache apache 4750 Aug 30 06:12
58b11d7002885f079b17aacc1141560a07577c27-updateinfo.xml.gz
-rw-r–r--. 1 apache apache 130 Aug 30 06:12
406ca46e811cbb67669659067e496c49a203ebc8-comps.xml
-rw-r–r--. 1 apache apache 8490 Aug 30 06:12
1be89a5ce8aa72147eb0473481fcf7f9a564555a-updateinfo.xml.gz
-rw-r–r--. 1 apache apache 93 Aug 30 06:12
627403e3c69fc0e42c8650ce306f4f2d40eb8d9b-updateinfo.xml.gz
-rw-r–r--. 1 apache apache 9712205 Aug 30 06:12
fab57608e10adfdf822ab9fdc6d40f61c2ae1846-filelists.xml.gz
-rw-r–r--. 1 apache apache 1795771 Aug 30 06:12
26125c4e7940746874289c5bc43e1f575cacbe98-other.xml.gz
-rw-r–r--. 1 apache apache 1919056 Aug 30 06:12
709e9ab737e71bc3ceeb84329b0f1b74b88ed3aa-primary.xml.gz
-rw-r–r--. 1 apache apache 93 Aug 30 06:12
16978ce66abe57082d1fe4c08e78aa6b34ea4fdf-updateinfo.xml.gz
lrwxrwxrwx. 1 apache apache 126 Aug 30 12:03 productid ->
/var/lib/pulp/content/units/yum_repo_metadata_file/45/c8c4b57d98266ce8bdfbd46ebe885e82bca462280bcb9dfb1d9a896338575f/productid
-rw-r–r--. 1 apache apache 2002 Aug 30 12:03 repomd.xml
[root@upstream repodata]#

After sync downstream :-

[root@sownstream repodata]# ls -ltr
total 13248
-rw-r–r--. 1 apache apache 2008 Sep 8 07:09 repomd.xml
-rw-r–r--. 1 apache apache 130 Sep 8 07:09
3e800f8eb4bfc89f8e320cda3dd709a8e0bef5f4884e3b622df63b17249e8242-comps.xml
-rw-r–r--. 1 apache apache 93 Sep 8 07:09
2c2f4b66bb8476d86203ee64c9667d6ada958814a8382e2e8f7bd029f4fe3416-updateinfo.xml.gz
-rw-r–r--. 1 apache apache 9725738 Sep 8 07:09
ff66db38042d7620628d676a0a1b71e3936c790a-filelists.xml.gz
-rw-r–r--. 1 apache apache 1868738 Sep 8 07:09
2fe4680f4139c3596e8d558c489d8b3d16982391-other.xml.gz
lrwxrwxrwx. 1 apache apache 126 Sep 8 07:09 productid ->
/var/lib/pulp/content/units/yum_repo_metadata_file/45/c8c4b57d98266ce8bdfbd46ebe885e82bca462280bcb9dfb1d9a896338575f/productid
-rw-r–r--. 1 apache apache 93 Sep 8 07:09
f2f08dee82e5d8768331f8c672ffc7b4c8f8b9dd-updateinfo.xml.gz
-rw-r–r--. 1 apache apache 1939318 Sep 8 07:09
667d00282aa96c53f8f51b6b502afb8be8f7ddd6-primary.xml.gz
-rw-r–r--. 1 apache apache 130 Sep 8 07:09
406ca46e811cbb67669659067e496c49a203ebc8-comps.xml
[root@downstream repodata]#

[root@upstream repodata]# pwd
/var/lib/pulp/published/yum/https/repos/ORG/Library/content/dist/rhel/server/7/7.2/x86_64/rhscl/1/os/repodata

i dont see all updateinfo files.

Regards,
DJ

16

please ignore for now, looks like due to some certificate issue, celery was
giving some errors and that may be reason it was not able to sync complete
repository, after fixing certificate now i do see erratas as well.

Thanks,
DJ

··· On Friday, 9 September 2016 08:49:23 UTC+5:30, Unix SA wrote: > > here it is :- > > [root@upstream repodata]# pwd > > /var/lib/pulp/published/yum/https/repos/ORG/content_views/CCV_test/2.0/content/dist/rhel/server/7/7.2/x86_64/rhscl/1/os/repodata > [root@upstream repodata]# > [root@upstream repodata]# > [root@upstream repodata]# ls -ltr > total 13592 > -rw-r--r--. 1 apache apache 93 Aug 30 06:12 > 325e4792e1c8e355251d07340f9915bc6fbac716e1eadf69ae5ecf92abd36f7f-updateinfo.xml.gz > -rw-r--r--. 1 apache apache 130 Aug 30 06:12 > 3e800f8eb4bfc89f8e320cda3dd709a8e0bef5f4884e3b622df63b17249e8242-comps.xml > -rw-r--r--. 1 apache apache 429326 Aug 30 06:12 > 0b0f6a624ade8c015c3c499b0b21eac60176c4d5-updateinfo.xml.gz > -rw-r--r--. 1 apache apache 93 Aug 30 06:12 > c52f1349c09f6534368b08b646adf122362bc37f-updateinfo.xml.gz > -rw-r--r--. 1 apache apache 4750 Aug 30 06:12 > 58b11d7002885f079b17aacc1141560a07577c27-updateinfo.xml.gz > -rw-r--r--. 1 apache apache 130 Aug 30 06:12 > 406ca46e811cbb67669659067e496c49a203ebc8-comps.xml > -rw-r--r--. 1 apache apache 8490 Aug 30 06:12 > 1be89a5ce8aa72147eb0473481fcf7f9a564555a-updateinfo.xml.gz > -rw-r--r--. 1 apache apache 93 Aug 30 06:12 > 627403e3c69fc0e42c8650ce306f4f2d40eb8d9b-updateinfo.xml.gz > -rw-r--r--. 1 apache apache 9712205 Aug 30 06:12 > fab57608e10adfdf822ab9fdc6d40f61c2ae1846-filelists.xml.gz > -rw-r--r--. 1 apache apache 1795771 Aug 30 06:12 > 26125c4e7940746874289c5bc43e1f575cacbe98-other.xml.gz > -rw-r--r--. 1 apache apache 1919056 Aug 30 06:12 > 709e9ab737e71bc3ceeb84329b0f1b74b88ed3aa-primary.xml.gz > -rw-r--r--. 1 apache apache 93 Aug 30 06:12 > 16978ce66abe57082d1fe4c08e78aa6b34ea4fdf-updateinfo.xml.gz > lrwxrwxrwx. 1 apache apache 126 Aug 30 12:03 productid -> > /var/lib/pulp/content/units/yum_repo_metadata_file/45/c8c4b57d98266ce8bdfbd46ebe885e82bca462280bcb9dfb1d9a896338575f/productid > -rw-r--r--. 1 apache apache 2002 Aug 30 12:03 repomd.xml > [root@upstream repodata]# > > > *After sync downstream :-* > > [root@sownstream repodata]# ls -ltr > total 13248 > -rw-r--r--. 1 apache apache 2008 Sep 8 07:09 repomd.xml > -rw-r--r--. 1 apache apache 130 Sep 8 07:09 > 3e800f8eb4bfc89f8e320cda3dd709a8e0bef5f4884e3b622df63b17249e8242-comps.xml > -rw-r--r--. 1 apache apache 93 Sep 8 07:09 > 2c2f4b66bb8476d86203ee64c9667d6ada958814a8382e2e8f7bd029f4fe3416-updateinfo.xml.gz > -rw-r--r--. 1 apache apache 9725738 Sep 8 07:09 > ff66db38042d7620628d676a0a1b71e3936c790a-filelists.xml.gz > -rw-r--r--. 1 apache apache 1868738 Sep 8 07:09 > 2fe4680f4139c3596e8d558c489d8b3d16982391-other.xml.gz > lrwxrwxrwx. 1 apache apache 126 Sep 8 07:09 productid -> > /var/lib/pulp/content/units/yum_repo_metadata_file/45/c8c4b57d98266ce8bdfbd46ebe885e82bca462280bcb9dfb1d9a896338575f/productid > -rw-r--r--. 1 apache apache 93 Sep 8 07:09 > f2f08dee82e5d8768331f8c672ffc7b4c8f8b9dd-updateinfo.xml.gz > -rw-r--r--. 1 apache apache 1939318 Sep 8 07:09 > 667d00282aa96c53f8f51b6b502afb8be8f7ddd6-primary.xml.gz > -rw-r--r--. 1 apache apache 130 Sep 8 07:09 > 406ca46e811cbb67669659067e496c49a203ebc8-comps.xml > [root@downstream repodata]# > > [root@upstream repodata]# pwd > > /var/lib/pulp/published/yum/https/repos/ORG/Library/content/dist/rhel/server/7/7.2/x86_64/rhscl/1/os/repodata > > i dont see all updateinfo files. > > Regards, > DJ > >
17

> please ignore for now, looks like due to some certificate issue, celery was
> giving some errors and that may be reason it was not able to sync complete
> repository, after fixing certificate now i do see erratas as well.
>

cool, glad to hear it's working:)

··· On 09/09/2016 04:12 AM, Unix SA wrote:

Thanks,
DJ

On Friday, 9 September 2016 08:49:23 UTC+5:30, Unix SA wrote:

here it is :-

[root@upstream repodata]# pwd

/var/lib/pulp/published/yum/https/repos/ORG/content_views/CCV_test/2.0/content/dist/rhel/server/7/7.2/x86_64/rhscl/1/os/repodata
[root@upstream repodata]#
[root@upstream repodata]#
[root@upstream repodata]# ls -ltr
total 13592
-rw-r–r--. 1 apache apache 93 Aug 30 06:12
325e4792e1c8e355251d07340f9915bc6fbac716e1eadf69ae5ecf92abd36f7f-updateinfo.xml.gz
-rw-r–r--. 1 apache apache 130 Aug 30 06:12
3e800f8eb4bfc89f8e320cda3dd709a8e0bef5f4884e3b622df63b17249e8242-comps.xml
-rw-r–r--. 1 apache apache 429326 Aug 30 06:12
0b0f6a624ade8c015c3c499b0b21eac60176c4d5-updateinfo.xml.gz
-rw-r–r--. 1 apache apache 93 Aug 30 06:12
c52f1349c09f6534368b08b646adf122362bc37f-updateinfo.xml.gz
-rw-r–r--. 1 apache apache 4750 Aug 30 06:12
58b11d7002885f079b17aacc1141560a07577c27-updateinfo.xml.gz
-rw-r–r--. 1 apache apache 130 Aug 30 06:12
406ca46e811cbb67669659067e496c49a203ebc8-comps.xml
-rw-r–r--. 1 apache apache 8490 Aug 30 06:12
1be89a5ce8aa72147eb0473481fcf7f9a564555a-updateinfo.xml.gz
-rw-r–r--. 1 apache apache 93 Aug 30 06:12
627403e3c69fc0e42c8650ce306f4f2d40eb8d9b-updateinfo.xml.gz
-rw-r–r--. 1 apache apache 9712205 Aug 30 06:12
fab57608e10adfdf822ab9fdc6d40f61c2ae1846-filelists.xml.gz
-rw-r–r--. 1 apache apache 1795771 Aug 30 06:12
26125c4e7940746874289c5bc43e1f575cacbe98-other.xml.gz
-rw-r–r--. 1 apache apache 1919056 Aug 30 06:12
709e9ab737e71bc3ceeb84329b0f1b74b88ed3aa-primary.xml.gz
-rw-r–r--. 1 apache apache 93 Aug 30 06:12
16978ce66abe57082d1fe4c08e78aa6b34ea4fdf-updateinfo.xml.gz
lrwxrwxrwx. 1 apache apache 126 Aug 30 12:03 productid ->
/var/lib/pulp/content/units/yum_repo_metadata_file/45/c8c4b57d98266ce8bdfbd46ebe885e82bca462280bcb9dfb1d9a896338575f/productid
-rw-r–r--. 1 apache apache 2002 Aug 30 12:03 repomd.xml
[root@upstream repodata]#

After sync downstream :-

[root@sownstream repodata]# ls -ltr
total 13248
-rw-r–r--. 1 apache apache 2008 Sep 8 07:09 repomd.xml
-rw-r–r--. 1 apache apache 130 Sep 8 07:09
3e800f8eb4bfc89f8e320cda3dd709a8e0bef5f4884e3b622df63b17249e8242-comps.xml
-rw-r–r--. 1 apache apache 93 Sep 8 07:09
2c2f4b66bb8476d86203ee64c9667d6ada958814a8382e2e8f7bd029f4fe3416-updateinfo.xml.gz
-rw-r–r--. 1 apache apache 9725738 Sep 8 07:09
ff66db38042d7620628d676a0a1b71e3936c790a-filelists.xml.gz
-rw-r–r--. 1 apache apache 1868738 Sep 8 07:09
2fe4680f4139c3596e8d558c489d8b3d16982391-other.xml.gz
lrwxrwxrwx. 1 apache apache 126 Sep 8 07:09 productid ->
/var/lib/pulp/content/units/yum_repo_metadata_file/45/c8c4b57d98266ce8bdfbd46ebe885e82bca462280bcb9dfb1d9a896338575f/productid
-rw-r–r--. 1 apache apache 93 Sep 8 07:09
f2f08dee82e5d8768331f8c672ffc7b4c8f8b9dd-updateinfo.xml.gz
-rw-r–r--. 1 apache apache 1939318 Sep 8 07:09
667d00282aa96c53f8f51b6b502afb8be8f7ddd6-primary.xml.gz
-rw-r–r--. 1 apache apache 130 Sep 8 07:09
406ca46e811cbb67669659067e496c49a203ebc8-comps.xml
[root@downstream repodata]#

[root@upstream repodata]# pwd

/var/lib/pulp/published/yum/https/repos/ORG/Library/content/dist/rhel/server/7/7.2/x86_64/rhscl/1/os/repodata

i dont see all updateinfo files.

Regards,
DJ