DNS entry for git.haskell.org active now!

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

DNS entry for git.haskell.org active now!

Herbert Valerio Riedel
Hello GHC Devs,

Hopefully, the new DNS entry for git.haskell.org should be visible for
all of you by the time you read this. This mostly completes the
migration part of the GitolitePlan[1].

With the new hostname, the URLs to use for `sync-all` to fetch via
git://, http://, or ssh:// (ordered by increasing latency & url length)
are

  ./sync-all -r     git://git.haskell.org remote set-url origin
  ./sync-all -r    http://git.haskell.org remote set-url origin
  ./sync-all -r ssh://git at git.haskell.org remote set-url origin

...and for setting the push-URL (via ssh://) use

  ./sync-all -r ssh://git at git.haskell.org remote set-url --push origin

Please note that the (deprecated) `/libraries` symlink to `/packages` is
only supported at the old http://darcs.haskell.org/ Git repo location.

Finally, the new Gitweb interface[2] to the GHC Git repos should have
become accessible for everyone (w/o hacking `/etc/hosts`).

Cheers,
  hvr

 [1]: http://ghc.haskell.org/trac/ghc/wiki/GitolitePlan
 [2]: http://git.haskell.org/



Reply | Threaded
Open this post in threaded view
|

DNS entry for git.haskell.org active now!

Austin Seipp-4
Thank you Herbert!

On Monday, August 19, 2013, Herbert Valerio Riedel wrote:

> Hello GHC Devs,
>
> Hopefully, the new DNS entry for git.haskell.org should be visible for
> all of you by the time you read this. This mostly completes the
> migration part of the GitolitePlan[1].
>
> With the new hostname, the URLs to use for `sync-all` to fetch via
> git://, http://, or ssh:// (ordered by increasing latency & url length)
> are
>
>   ./sync-all -r     git://git.haskell.org remote set-url origin
>   ./sync-all -r    http://git.haskell.org remote set-url origin
>   ./sync-all -r ssh://git at git.haskell.org <javascript:;> remote set-url
> origin
>
> ...and for setting the push-URL (via ssh://) use
>
>   ./sync-all -r ssh://git at git.haskell.org <javascript:;> remote set-url
> --push origin
>
> Please note that the (deprecated) `/libraries` symlink to `/packages` is
> only supported at the old http://darcs.haskell.org/ Git repo location.
>
> Finally, the new Gitweb interface[2] to the GHC Git repos should have
> become accessible for everyone (w/o hacking `/etc/hosts`).
>
> Cheers,
>   hvr
>
>  [1]: http://ghc.haskell.org/trac/ghc/wiki/GitolitePlan
>  [2]: http://git.haskell.org/
>


--
Sent from my portable turning machine
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/ghc-devs/attachments/20130819/694754a9/attachment.htm>

Reply | Threaded
Open this post in threaded view
|

DNS entry for git.haskell.org active now!

Simon Peyton Jones
In reply to this post by Herbert Valerio Riedel
Thanks.  Some quick questions

1. What's the difference between ghc.haskell.org and git.haskell.org?

2. Is there anything to choose between these two?
  ./sync-all -r     git://git.haskell.org remote set-url origin
  ./sync-all -r    http://git.haskell.org remote set-url origin

3. The repositories page http://ghc.haskell.org/trac/ghc/wiki/WorkingConventions/Repositories says "this page has been replaced by "Repositories" but the link is circular.. leads to the same page.

4. The Gitolite plan page http://ghc.haskell.org/trac/ghc/wiki/GitolitePlan is very helpful, but is in the nature of a "delta"/change-over plan.  Are you planning to replace it (perhaps on "Repositories"?) with instructions for how to use the new setup?  I think that would be v helpful for dolts like me.

Simon

| -----Original Message-----
| From: ghc-devs [mailto:ghc-devs-bounces at haskell.org] On Behalf Of
| Herbert Valerio Riedel
| Sent: 19 August 2013 23:46
| To: ghc-devs
| Subject: DNS entry for git.haskell.org active now!
|
| Hello GHC Devs,
|
| Hopefully, the new DNS entry for git.haskell.org should be visible for
| all of you by the time you read this. This mostly completes the
| migration part of the GitolitePlan[1].
|
| With the new hostname, the URLs to use for `sync-all` to fetch via
| git://, http://, or ssh:// (ordered by increasing latency & url length)
| are
|
|   ./sync-all -r     git://git.haskell.org remote set-url origin
|   ./sync-all -r    http://git.haskell.org remote set-url origin
|   ./sync-all -r ssh://git at git.haskell.org remote set-url origin
|
| ...and for setting the push-URL (via ssh://) use
|
|   ./sync-all -r ssh://git at git.haskell.org remote set-url --push origin
|
| Please note that the (deprecated) `/libraries` symlink to `/packages` is
| only supported at the old http://darcs.haskell.org/ Git repo location.
|
| Finally, the new Gitweb interface[2] to the GHC Git repos should have
| become accessible for everyone (w/o hacking `/etc/hosts`).
|
| Cheers,
|   hvr
|
|  [1]: http://ghc.haskell.org/trac/ghc/wiki/GitolitePlan
|  [2]: http://git.haskell.org/
|
| _______________________________________________
| ghc-devs mailing list
| ghc-devs at haskell.org
| http://www.haskell.org/mailman/listinfo/ghc-devs




Reply | Threaded
Open this post in threaded view
|

DNS entry for git.haskell.org active now!

Herbert Valerio Riedel
Hello Simon,

On 2013-08-20 at 08:48:26 +0200, Simon Peyton-Jones wrote:
> Thanks.  Some quick questions
>
> 1. What's the difference between ghc.haskell.org and git.haskell.org?

ghc.haskell.org *currently* points to the same IP address as
git.haskell.org, so it makes only a difference for services which use
the hostname to differentiate the namespace. This is currently only done
for the http:// protocol. For git:// and ssh:// it doesn't make any
significant difference (currently).

However, in order to facilitate future migrations, git.haskell.org
should be used, as then we could relocate git.haskell.org to a different
IP without needing to update the URLs in all documents again.

> 2. Is there anything to choose between these two?
>   ./sync-all -r     git://git.haskell.org remote set-url origin
>   ./sync-all -r    http://git.haskell.org remote set-url origin

git:// uses port 9418 which may sometimes may be blocked by
firewalls. Otoh, plain http:// gets through corporate firewalls more
easily. (At some point we might even offer https:// if we get SSL certs)

git:// is slightly faster than http:// as it doesn't incur the
HTTP-protocol overhead & processing latency. It's basically the raw
"Git" protocol over a plain TCP connection.

http:// currently uses the same Apache process as is used for serving
http://darcs.haskell.org and http://ghc.haskell.org; so if Apache
becomes non-responsive or dies, so does the http://git.haskell.org
service.  The ssh:// and git:// services however, being independent
processes, would continue to work (if only Apache was affected).

Also, git:// is currently set up in such a way, that it gets restarted
automatically if the git-daemon process dies. So git:// is the
high-availability option here.

Does this answer your question? :-)

> 3. The repositories page
> http://ghc.haskell.org/trac/ghc/wiki/WorkingConventions/Repositories
> says "this page has been replaced by "Repositories" but the link is
> circular.. leads to the same page.
>
> 4. The Gitolite plan page
> http://ghc.haskell.org/trac/ghc/wiki/GitolitePlan is very helpful, but
> is in the nature of a "delta"/change-over plan.  Are you planning to
> replace it (perhaps on "Repositories"?) with instructions for how to
> use the new setup?  I think that would be v helpful for dolts like me.

Yes, we're planning/going to update the Trac documentation to provide
more help understanding the new setup.

Cheers,
  hvr



Reply | Threaded
Open this post in threaded view
|

DNS entry for git.haskell.org active now!

Simon Peyton Jones
| However, in order to facilitate future migrations, git.haskell.org
| should be used, as then we could relocate git.haskell.org to a different
| IP without needing to update the URLs in all documents again.

Why?  If we only had ghc.haskell.org, we could just migrate that couldn't we?  Or are you imagining a situation in which ghc.haskell.org and git.haskell.org were really different servers?  Trac on one, and the repo on another, say?  Hmm. maybe that makes sense.

It'd be good to explain this thinking on the wiki page that you are developing.

| Does this answer your question? :-)

Yes, v helpful. Please copy paste the answer into the new wiki page!

| > 3. The repositories page
| > http://ghc.haskell.org/trac/ghc/wiki/WorkingConventions/Repositories
| > says "this page has been replaced by "Repositories" but the link is
| > circular.. leads to the same page.

You didn't reply to this.

Thanks

S




Reply | Threaded
Open this post in threaded view
|

DNS entry for git.haskell.org active now!

Herbert Valerio Riedel
On 2013-08-20 at 09:48:48 +0200, Simon Peyton-Jones wrote:
> | However, in order to facilitate future migrations, git.haskell.org
> | should be used, as then we could relocate git.haskell.org to a different
> | IP without needing to update the URLs in all documents again.
>
> Why?  If we only had ghc.haskell.org, we could just migrate that
> couldn't we?  Or are you imagining a situation in which
> ghc.haskell.org and git.haskell.org were really different servers?
> Trac on one, and the repo on another, say?  Hmm. maybe that makes
> sense.

Here's some more motivation why a new "git.haskell.org" hostname was desired:

http://permalink.gmane.org/gmane.comp.lang.haskell.infrastructure/103

> It'd be good to explain this thinking on the wiki page that you are developing.

will do

> | Does this answer your question? :-)
>
> Yes, v helpful. Please copy paste the answer into the new wiki page!

will do

> | > 3. The repositories page
> | > http://ghc.haskell.org/trac/ghc/wiki/WorkingConventions/Repositories
> | > says "this page has been replaced by "Repositories" but the link is
> | > circular.. leads to the same page.
>
> You didn't reply to this.

I've fixed this right now; seems the semantics changed for wiki: links
in Trac 0.12, so that "wiki:Repositories" was a link relative to
"/WorkingConventions/" instead of pointing to "/Repositories".

Cheers,
  hvr