llvm dev - Jan 2017 - [SERVER UPDATE] Moving clang, clang-analyzer, libcxxabi, libcxx ... websites to new server

All,

The following websites will be moving to a new web server in the next few days:
clang.llvm.org <http://clang.llvm.org/>
clang-analyzer.llvm.org <http://clang-analyzer.llvm.org/>
compiler-rt.llvm.org <http://compiler-rt.llvm.org/>
dragonegg.llvm.org <http://dragonegg.llvm.org/>
klee.llvm.org <http://klee.llvm.org/>
libclc.llvm.org <http://libclc.llvm.org/>
libcxx.llvm.org <http://libcxx.llvm.org/>
libcxxabi.llvm.org <http://libcxxabi.llvm.org/>
lldb.llvm.org <http://lldb.llvm.org/>
lld.llvm.org <http://lld.llvm.org/>
openmp.llvm.org <http://openmp.llvm.org/>
polly.llvm.org <http://polly.llvm.org/>
vmkit.llvm.org <http://vmkit.llvm.org/>

Please note that llvm.org <http://llvm.org/> proper is NOT moving at this
time. Therefore SVN, Bugzilla, ViewVC, and all the llvm.org/*
<http://llvm.org/*> webpages will remain on that server. I will be
updating on this in a separate email.

How does this impact you?
You may see a very short downtime (< 1 hour) when the switch is made. This is
most likely due to the DNS switch. I will notify the list when all websites
listed have been moved. Since this does not involve SVN, the downtime is
hopefully tolerable.

Are you fixing the SSL problem?
Yes. The new server will have SSL support for all websites and have an updated
certificate.

What about the website auto-update?
Currently, the web sites all automatically update via post-commit hook for SVN.
We have temporarily set up an alternative method and websites will update every
30 minutes.

What about website documentation generation?
There are 3 scripts that generate documentation on the web server. For doxygen,
it will continue to update daily. For sphinx documentation, it will update every
hour instead of immediately after a commit.

In order to increase visibility into the server, these scripts have been
enhanced to now email a list to indicate success or failure. You can either
subscribe to the list or check the archives if you have concerns about
documentation not being updated:
http://lists.llvm.org/cgi-bin/mailman/listinfo/www-scripts
<http://lists.llvm.org/cgi-bin/mailman/listinfo/www-scripts>

Why are you doing this?
We want to increase the reliability, stability, and speed of the LLVN services.
The current machine is outdated and is not set up for our current needs.

If you have any questions, please do not hesitate to ask.

Thank you,
Tanya
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20170105/2bc7bf74/attachment.html>

On Fri, 6 Jan 2017 at 06:26 Tanya Lattner via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> All,
>
> The following websites will be moving to a new web server in the next few
> days:
> clang.llvm.org
> clang-analyzer.llvm.org
> compiler-rt.llvm.org
> dragonegg.llvm.org
> klee.llvm.org
> libclc.llvm.org
> libcxx.llvm.org
> libcxxabi.llvm.org
> lldb.llvm.org
> lld.llvm.org
> openmp.llvm.org
> polly.llvm.org
> vmkit.llvm.org
>
> Please note that llvm.org proper is NOT moving at this time. Therefore
> SVN, Bugzilla, ViewVC, and all the llvm.org/* webpages will remain on
> that server. I will be updating on this in a separate email.
>
> *How does this impact you?*
> You may see a very short downtime (< 1 hour) when the switch is made.
This
> is most likely due to the DNS switch. I will notify the list when all
> websites listed have been moved. Since this does not involve SVN, the
> downtime is hopefully tolerable.
>
> *Are you fixing the SSL problem?*
> Yes. The new server will have SSL support for all websites and have an
> updated certificate.
>
Hi Tanya,

Are there more changes planned for the llvm.org web server? HTTPS is
broken, and this is affecting users of the Go bindings:
https://groups.google.com/d/msg/golang-nuts/cJE-HrH91vk/jgw7wkdxEwAJ

Cheers,
Andrew

> *What about the website auto-update?*
> Currently, the web sites all automatically update via post-commit hook for
> SVN. We have temporarily set up an alternative method and websites will
> update every 30 minutes.
>
> *What about website documentation generation?*
> There are 3 scripts that generate documentation on the web server. For
> doxygen, it will continue to update daily. For sphinx documentation, it
> will update every hour instead of immediately after a commit.
>
> In order to increase visibility into the server, these scripts have been
> enhanced to now email a list to indicate success or failure. You can either
> subscribe to the list or check the archives if you have concerns about
> documentation not being updated:
> http://lists.llvm.org/cgi-bin/mailman/listinfo/www-scripts
>
> *Why are you doing this?*
> We want to increase the reliability, stability, and speed of the LLVN
> services. The current machine is outdated and is not set up for our current
> needs.
>
> If you have any questions, please do not hesitate to ask.
>
> Thank you,
> Tanya
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20170111/7449bb39/attachment.html>

> On Jan 10, 2017, at 5:46 PM, Andrew Wilkins <axwalk at gmail.com>
wrote:
> 
> On Fri, 6 Jan 2017 at 06:26 Tanya Lattner via llvm-dev <llvm-dev at
lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote:
> All,
> 
> The following websites will be moving to a new web server in the next few
days:
> clang.llvm.org <http://clang.llvm.org/>
> clang-analyzer.llvm.org <http://clang-analyzer.llvm.org/>
> compiler-rt.llvm.org <http://compiler-rt.llvm.org/>
> dragonegg.llvm.org <http://dragonegg.llvm.org/>
> klee.llvm.org <http://klee.llvm.org/>
> libclc.llvm.org <http://libclc.llvm.org/>
> libcxx.llvm.org <http://libcxx.llvm.org/>
> libcxxabi.llvm.org <http://libcxxabi.llvm.org/>
> lldb.llvm.org <http://lldb.llvm.org/>
> lld.llvm.org <http://lld.llvm.org/>
> openmp.llvm.org <http://openmp.llvm.org/>
> polly.llvm.org <http://polly.llvm.org/>
> vmkit.llvm.org <http://vmkit.llvm.org/>
> 
> Please note that llvm.org <http://llvm.org/> proper is NOT moving at
this time. Therefore SVN, Bugzilla, ViewVC, and all the llvm.org/*
<http://llvm.org/*> webpages will remain on that server. I will be
updating on this in a separate email.
> 
> How does this impact you?
> You may see a very short downtime (< 1 hour) when the switch is made.
This is most likely due to the DNS switch. I will notify the list when all
websites listed have been moved. Since this does not involve SVN, the downtime
is hopefully tolerable.
> 
> Are you fixing the SSL problem?
> Yes. The new server will have SSL support for all websites and have an
updated certificate.
> 
> Hi Tanya,
> 
> Are there more changes planned for the llvm.org <http://llvm.org/>
web server? HTTPS is broken, and this is affecting users of the Go bindings:
https://groups.google.com/d/msg/golang-nuts/cJE-HrH91vk/jgw7wkdxEwAJ
<https://groups.google.com/d/msg/golang-nuts/cJE-HrH91vk/jgw7wkdxEwAJ>
> 
This will happen soon. Its never worked except for SVN and bugzilla though.

-Tanya

> Cheers,
> Andrew
>  
> What about the website auto-update?
> Currently, the web sites all automatically update via post-commit hook for
SVN. We have temporarily set up an alternative method and websites will update
every 30 minutes.
> 
> What about website documentation generation?
> There are 3 scripts that generate documentation on the web server. For
doxygen, it will continue to update daily. For sphinx documentation, it will
update every hour instead of immediately after a commit.
> 
> In order to increase visibility into the server, these scripts have been
enhanced to now email a list to indicate success or failure. You can either
subscribe to the list or check the archives if you have concerns about
documentation not being updated:
> http://lists.llvm.org/cgi-bin/mailman/listinfo/www-scripts
<http://lists.llvm.org/cgi-bin/mailman/listinfo/www-scripts>
> 
> Why are you doing this?
> We want to increase the reliability, stability, and speed of the LLVN
services. The current machine is outdated and is not set up for our current
needs.
> 
> If you have any questions, please do not hesitate to ask.
> 
> Thank you,
> Tanya
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
<http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20170110/a79daacc/attachment.html>

On Thu, Jan 5, 2017 at 5:26 PM, Tanya Lattner via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> *Are you fixing the SSL problem?*
> Yes. The new server will have SSL support for all websites and have an
> updated certificate.
>
Is there any plan to make the migrated sites SSL-only? That is, have
http://clang.llvm.org/** only serve a redirect to
https://clang.llvm.org/** instead
of serving content over http.

If not, that'd be a great thing to add to the plans. :)
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20170113/b24b8775/attachment.html>

> On Jan 13, 2017, at 12:35 PM, James Y Knight via llvm-dev <llvm-dev at
lists.llvm.org> wrote:
> 
> On Thu, Jan 5, 2017 at 5:26 PM, Tanya Lattner via llvm-dev <llvm-dev at
lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote:
> Are you fixing the SSL problem?
> Yes. The new server will have SSL support for all websites and have an
updated certificate.
> 
> Is there any plan to make the migrated sites SSL-only? That is, have
http://clang.llvm.org/** <http://clang.llvm.org/**> only serve a redirect
to https://clang.llvm.org/** <https://clang.llvm.org/**> instead of
serving content over http.
> 
> If not, that'd be a great thing to add to the plans. :)
I’m curious: why?
I understand that you want anything authenticated (bugzilla, …) or the
binary/source download, but what’s the reason to use SSL for looking up doxygen
or LangRef? (Easier to setup or get it right could be a reason, I don’t know)

— 
Mehdi

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20170113/381a3694/attachment.html>