It would be also nice to have:
https://fedorahosted.org/sssd/report/* -> https://pagure.io/SSSD/sssd/issues
(I don't think we need more fine-grained rules and redirect each report type, we just need to let people know that fedorahosted is no longer around)

about the repo, if there is an easy way to just keep mirroring the repo from pagure to fedorahosted, that would be nice. Otherwise, we can remove all files from the current repo after the migration and just put a README telling people we have moved until the fedorahosted domain is up even in a read-only mode..

So, the usual redirects we have been doing are:

RedirectMatch permanent ^/sssd/report https://pagure.io/SSSD/sssd/issues
RedirectMatch permanent ^/sssd/ticket/(.*) https://pagure.io/SSSD/sssd/issue/$1
RedirectMatch permanent ^/sssd https:///pagure.io/SSSD/sssd
RedirectMatch permanent ^/sssd/ https://pagure.io/SSSD/sssd/

Since you haven't moved wiki yet, I can comment the last 2 and put them in when you like.

We don't really have any mirroring solution for fedorahosted (although pagure has or is about to get such functionality I think).

Feel free to add further needs here.

Would it be possible to Provide also redirect for released tarballs as I mentioned in ticket description?

RedirectMatch permanent ^/released/sssd/ -> https://releases.pagure.org/SSSD/sssd/

We don't really have any mirroring solution for fedorahosted (although pagure has or is about to get such functionality I think).
Feel free to add further needs here.

I did not get a point here. Was it about git?
If yes then I am little bit confused. ATM sssd.git on fedorahosted is mirrored to github. IIRC it was done by @puiterwijk. And We would like to have the same for git on pagure https://pagure.io/SSSD/sssd.git.

And it would be good to disable ssh access to fedorahosted git so people will not accidentally push patches there.

And if mirroring from pagure git -> to fedorahosted git is not a good idea then it would be good to remove it as jakub mentioned in comment https://pagure.io/fedora-infrastructure/issue/5828#comment-243720

ok. I added:

RedirectMatch permanent ^/releases/s/s/sssd/ https://releases.pagure.org/SSSD/sssd/

I talked with @puiterwijk and he is going to see if he can come up with some solution for the mirroring. We do not currently have any support for that in pagure.

I have also chowned the git repo on fedorahosted, so no one can push changes to it now.

@puiterwijk indicated he can set up an admittedly lower-security way that relies on gitolite security completely. We are fine with that and would appreciate help with having the github mirror automatic again.

The github push should be setup now.

I pushed patches to pagure 10 hours ago and they were not mirrored.
And comment was added 11 hours ago at the time of writing.

The ticket is reopened. I will take this opportunity and I will ask for few more redirects. previously ding-libs and sssd shared trac. But we changed that together with migration.

Please provide redirect for ding-libs releases
https://fedorahosted.org/released/ding-libs/ -> https://releases.pagure.org/SSSD/ding-libs/

And it would be good to disable ssh access to fedorahosted ding-libs.git so people will not accidentally push patches there.

Can do.

I have already disabled ssh, as today is retirement day.

Do you need me to keep access open for anything? Or are you all done/moved?

Sorry, I had made a mistake setting up the mirror script.
I've fixed this now, so please try again.

We haven't migrated the wiki yet. The rest should be all good.

Unfortunately, RHEL deadlines force us to prioritize work these days and lately even a read only wiki was good enough for us. Is the wiki also going away today?

yeah, I know how it goes. :frowning:

Well, I was going to redirect all the web pages to our retirement announcement page.

We could do one of these for you:

1. Except sssd trac wiki from redirect so you can pull data whenever.

2. Do a trac wiki export which dumps all the wiki pages as text files

3. Give you the tracdb sqlite which I think has all the data in it.

Any preference?

I went ahead and setup the redirects, let me know if what you want to do about the wiki data and I can do that.

From the options you outlined, we already have 3 thanks to Patrick.

1. Would be appreciated, because it's easier to work with than the dump, but I have no idea how much work it is for you.

2. would be /much/ appreciated for some time. I guess I /can/ dedicate an hour or two even in this crunch period, but it is not realistic for us to migrate the whole wiki at a moment's notice. I totally see why you wouldn't want to create exceptions, so could we maybe set a deadline after which you'd retire the wiki? Maybe two weeks so we can migrate it?

I think you have swapped 1 and 2 around? :)
I have made an exception for the SSSD wiki: https://fedorahosted.org/sssd/wiki and all its sub-urls will no longer redirect.

Note that https://fedorahosted.org/sssd does redirect so you need to add the /wiki (I'm fixing the place it redirects to, see #5855, should be done shortly).

well, I'm more concerned about people having bookmarks to the troubleshooting guides, or howtos as we send them out to users all the time. The wiki not being browsable is also a problem, but not that much.

Could you give me one of those links, so I know what kind to exempt?
Since I was under the impression that all trac wiki is under /wiki/

After confirmation on IRC that these are under /wiki/, I think this is no longer an issue, as those urls are excempted for sssd at the moment.

Sorry, I had made a mistake setting up the mirror script.
I've fixed this now, so please try again.

Thank you.
It works.

@puiterwijk I think there is a small problem with mail hook after recent change.

I can see:

remote: Sending to redis to log activity
remote: Pushing to github...
remote: ./hooks/post-receive.ghpush: line 4: cd: /srv/git/sssd.git: No such file or directory

And we received just a summary mail [SSSD/sssd] branch master updated (bd5e09b -> 6dd271f)
But there is missing a mail with patch.

Ah, that error was a typo in my check line, and should be fixed.
Please try now.

I went ahead and setup the redirects, let me know if what you want to do about the wiki data and I can do that.

@kevin Could you temporary allow also URL for jronrpc?
I would like to download html version of wiki because neither of converters from wiki get reasonable results due to usage of code blocks {{{ }}}. And I occidentally removed my local backup.

URL https://fedorahosted.org/sssd/login/rpc

The logged in JSON RPC url is still available for all projects.
Please use https://fedorahosted.org/sssd/login/jsonrpc

The logged in JSON RPC url is still available for all projects.
Please use https://fedorahosted.org/sssd/login/jsonrpc
Thank you it works.

I think we can close ticket.

Okay. Let us know if we can help with anything else.

May I know why the redirect https://fedorahosted.org/released/sssd/ -> https://releases.pagure.org/SSSD/sssd/ was removed?

Because https://fedorahosted.org/released/ding-libs/ -> https://releases.pagure.org/SSSD/ding-libs/
still works.

According to what I can see, /released/sssd/ was never setup, only /releases/s/s/sssd/.
I did now add that redirect.

Hmm, I probably didn't tested it after comment.
https://pagure.io/fedora-infrastructure/issue/5828#comment-243807

Thank you very much.

a month ago
After confirmation on IRC that these are under /wiki/, I think this is no longer an issue, as those urls are excempted for sssd at the moment.

it is broken now. Is it expected or by mistake?
You can test with following link
https://fedorahosted.org/sssd/wiki/Troubleshooting

It's now broken because we have moved the redirects to our main proxy servers to allow for us to power off/undefine the old fedorahosted instance.

I guess that means that you all never got around to migrating the wiki?

The old content is still at:
https://140.211.169.199/sssd/wiki/Troubleshooting
but I was really really hoping to actually shut that machine off.

Would you be able to migrate the wiki asap?
Or perhaps I can get you the trac.db and you can extract it from there as you like?
Or I can redirect the wiki to some other place?

What do you want to do here?

@lslebodn Any news here? I'm happy to try and accomodate you folks, but I really would prefer to power the old hosted03 off.

Additionally to the above I can dump all the wiki pages as plain txt for importing somewhere else if it helps.

We will try to convert pages as soon as possible. It would be good If you could keep kosted03(140.211.169.199) keep running for a while. Missing redirects will force us to do it faster :-). But we still need to fight with rhel7 bugs/deadlines.

Thank you very much for understanding.

Hey. Any chance to get this closed out so we can shutdown that host?

The main issue is that there are not wiki converters which can properly handle following syntax {{{ }}} . I will write a script to download all html version of wiki pages with json API. So we will have reasonable backup.

I am so sorry that it takes such long from our side. Thank you very much for you patience and understanding.

If it helps any I can use a trac-admin tool to dump the pages as text, but I think that drops any formatting that they may have had.

Any status update here?

Hey folks, been another few weeks. Any news?

I really need to shutdown the old instance... I can delay until the end of the month I guess, but then I really need to take it down.

Hey folks, been another few weeks. Any news?
I really need to shutdown the old instance... I can delay until the end of the month I guess, but then I really need to take it down.

I am so sorry that it took so long. I did a backup of page using jsonrpc a nice recursive wget :-). You can shutdown the machine and close this ticket.

Great. Let us know if there's anything else we can do for you.

:dragon: