openSUSE admin

Closing here, as it looks like Pharaoh_Atem already provided all relevant documentation.

On Donnerstag, 5. Januar 2023, 16:18:51 CET Lubos Kocman wrote:
> Hello autobuild team!
> 
> We've discussed this with Adrian yesterday as part of
> https://etherpad.opensuse.org/p/ReleaseEngineering-20230104
> 
> I'd like to ask you to set up custom "repodata-only" publishing for our 
> openh264 projects which are using <access><disabled/></access> to 
> control who can access them and utilize redirect rule for rpms to cisco 
> infra (will be discussed with *heroes later today).

The way how fedora implemented this is actually independend of
repository building.

They offer the full repository on their server, but they redirect
for the rpm files to the cisco server.

So all what we need to do is to publish to a special directory on
some vhost (like cpdecs.fedoraproject.org), but all the setup 
magic for this must be done on that vhost setup.

so, just tell use to which rsync module on which server we need to sync.

thanks
adrian


> openSUSE:Factory:openh264
> openSUSE:Factory:openh264:POST (snapshot of not yet published rpms 
> emailed to cisco)
> openSUSE:Factory:openh264:PUBLISHED (published repodata on download-o-o)
> 
> I think it would be safest to "get rid of rpms" as part of publishing 
> for all of these projects above as we've already faced accidentally 
> enabled publishing in the past. And this would be considered a safety 
> mechanism.
> 
> The publish flag would be enabled only for 
> openSUSE:Factory:openh264:PUBLISHED to where I'd release data *manually.
> 
> As part of the publishing, we expect to publish repodata for both 
> version-less openSUSE_Leap (for all Leap versions built against the 
> oldest supported) and openSUSE_Tumbleweed.
> 
> The publish location for Leap would by default have Tumbleweed in the 
> path which looks a bit odd. If you could think of any solution for a 
> "single Leap repo" I'd be more than happy.
> 
> 
> [0] https://progress.opensuse.org/issues/121288
> [1] https://github.com/openSUSE/openSUSE-release-tools/pull/2911
> 
> Thank you very much in advance
> 
> Lubos Kocman
> 

So we need a custom rsync module to which we will publish from https://build.opensuse.org/package/show/openSUSE:Factory:openh264/openh264:PUBLISHED

with either download.opensuse.org/openh264 (that would be excluded from offering to mirrors)
or codecs.opensuse.org/openh264

This needs to be set up with apache redirect of rpm files: (host depends on the rsync module / subdomain above)

opensuse.org/openh264/openSUSE_Tumbleweed/$arch/libopenh264-7-2.3.1-8.suse1500.1.x86_64.rpm -> http://ciscobinary.openh264.org/libopenh264-7-2.3.1-8.suse1500.1.x86_64.rpm
opensuse.org/openh264/openSUSE_Leap/$arch/libopenh264-7-2.3.1-8.suse1500.1.x86_64.rpm -> http://ciscobinary.openh264.org/libopenh264-7-2.3.1-8.suse1500.1.x86_64.rpm

(this is just example rpm we need *.rpm -> *.rpm)

Leaving unassigned.

http[s]://codecs.opensuse.org set up. RPM files redirect to example.com for now, will change to ciscobinary.openh264.org once the rest of the setup is complete.

Q's:

• how do I reload rsyncd-internal.conf ?
• how do I configure the new vhost to use the modern directory listing ?

Questions resolved, directory index theme configured (besides some minor CSS artifacts).

Redirect for codecs.opensuse.org/./.rpm to ciscobinary.openh264.org configured.