[ocaml-infra] Github down again

Sylvain Le Gall sylvain+ocaml at le-gall.net
Fri Nov 1 13:01:26 GMT 2013


2013/11/1 Amir Chaudhry <amc79 at cam.ac.uk>:
> I'm still confused by this. What Anil and Gabriel pointed out makes sense to me (having a mirror of certain repos) and was discussed in the past. You seem to be talking about a method for managing a group of users but I don't actually see why that's necessary here.
>

I realize that I am not clear.

The goal is to create a mirror (full ACK here). I have no question
concerning this point.

I am only proposing to host it as a project on the forge. That was the
reason of my question about "what is git.ocaml.org ? (a VM or a
physical host or whatever)". I am not discussing the use or the way to
do it, but just would like to see it the data mirrored project hosted
on the forge.

The reason I am pushing for that: do you remember COCAN ? We should
avoid hosting important services on server that have no admin backup.
If you want something to last long, you should be able to easily share
it with other people. If we spread our ocaml.org admin over multiple
host, that just increase the cost of maintainance.

Cheers
Sylvain

> Best wishes,
> Amir
>
> --
> sent via mobile
>
>> On 1 Nov 2013, at 11:17, Sylvain Le Gall <sylvain+ocaml at le-gall.net> wrote:
>>
>> Just realize that maybe I was not clear on a very simple thing:
>>
>> The point is not to use the Forge VCS repositories infrastructure,
>> this is just to create a group of user and use the fact that you can
>> have cronjob with scripts running. You can just consider this as
>> "hosting" the group and have a place to create, run script and have
>> the result visible (usually on YOURPROJECT.forge.ocamlcore.org but
>> injecting an alias from git.ocaml.org to
>> YOURPROJECT.forge.ocamlcore.org is a 2 minutes work).
>>
>> Is it more clear ?
>>
>> Am I still missing something ?
>>
>> Cheers
>> Sylvain
>>
>> 2013/11/1 Sylvain Le Gall <sylvain+ocaml at le-gall.net>:
>>> ---------- Forwarded message ----------
>>> From: Sylvain Le Gall <sylvain+ocaml at le-gall.net>
>>> Date: 2013/11/1
>>> Subject: Re: [ocaml-infra] Github down again
>>> To: Anil Madhavapeddy <anil at recoil.org>
>>>
>>>
>>> 2013/11/1 Anil Madhavapeddy <anil at recoil.org>:
>>>> I'm a little confused -- the intention behind git.ocaml.org is to act
>>>> as a mirror for major OCaml repositories, so putting a dependency on Forge
>>>> doesn't seem right.  What's the goal of the scripts you are talking about
>>>> below?
>>>>
>>>> I'm thinking that we simply specify a list of Git URLs somewhere, and
>>>> they are picked up by git.ocaml.org to publish as a mirror.  That could
>>>> include a list exported by the Forge of its projects (that use Git), as
>>>> well as others on GitHub.
>>>
>>> Having a project on the forge will provide:
>>> - a public list of member of the project (i.e. you know who to ping
>>> when there is a problem)
>>> - maintenance of the system hosting your project will be taken care by
>>> someone else (including e.g. backup, system upgrade)
>>> - adding a member to the project will be easier (vs if you are hosting
>>> this on your host, you will have to create a user + add his ssh key)
>>>
>>> What is precisely git.ocaml.org ?
>>>
>>> If this is a VM or a physical host, I think you will slightly increase
>>> the TCO of *.ocaml.org. If this is a virtual host inside OCamlLab, you
>>> may have concern to add external contributor. The benefit to have it
>>> separate is that if github and the OCaml forge will be down at the
>>> same time, you still have no problem.
>>>
>>> But all in all, the benefit of hosting it on the forge is not huge,
>>> this may just be convenient for allowing other people to take care of
>>> it and getting rid of some system maintainance. So I am not pushing
>>> hard on this, I just think it is a good idea.
>>>
>>> The scheme to synchronize will be the same in both case (cronjob +
>>> list of url + a shell script).
>>>
>>> Does it make sense to you ?
>>>
>>>> -anil
>>>>
>>>>> On 31 Oct 2013, at 13:21, Sylvain Le Gall <sylvain+ocaml at le-gall.net> wrote:
>>>>>
>>>>> I think the best place to have this kind of mirror is in Forge (but I
>>>>> think you agree if I understand you correctly).
>>>>>
>>>>> Proposal:
>>>>> - create a forge.ocamlcore.org project called "github-mirror"
>>>>> - have a main git repository (in github or in the forge) that contains
>>>>> a file "github-url-to-mirror"
>>>>>
>>>>> In a cronjob on ssh.ocamlcore.org:
>>>>> - checkout the main git repository
>>>>> - loop over the entries of github-url-to-mirror and check them out in
>>>>> /home/group/github-mirror/gitroot/
>>>>>
>>>>> For the nice GitLab interface, contact me so that we can install the
>>>>> required DB and ruby packages. However you'll probably have to install
>>>>> gitlab by yourself, except if you know where I can find a debian
>>>>> package for it, and point it to /home/group/github-mirror/gitroot...
>>>>>
>>>>> User signup -> agree that it should be disabled.
>>>>>
>>>>> Does it make sense ?
>>>>>
>>>>> Regards
>>>>> Sylvain
>>>>>
>>>>>
>>>>> 2013/10/31 Anil Madhavapeddy <anil at recoil.org>:
>>>>>> I took a quick shot a trying out GitLab to act as a mirror.  This is *very* experimental, but here's what it looks like on git.ocaml.org:
>>>>>>
>>>>>> http://git.ocaml.org/ocaml-compiler/ocaml/commits/master
>>>>>> (I didn't set this up on a staging domain due to the pain of reconfiguration).
>>>>>>
>>>>>> There's only one project on there at a moment: a static checkout of the OCaml Git mirror, but I can script up a proper GitHub/Forge mirror quite easily from this.  I'm inclined to disable user signups for this and make it a pure mirror, though.
>>>>>>
>>>>>> -anil
>>>>>> _______________________________________________
>>>>>> Infrastructure mailing list
>>>>>> Infrastructure at lists.ocaml.org
>>>>>> http://lists.ocaml.org/listinfo/infrastructure
>> _______________________________________________
>> Infrastructure mailing list
>> Infrastructure at lists.ocaml.org
>> http://lists.ocaml.org/listinfo/infrastructure


More information about the Infrastructure mailing list