eclipse.org infrastructure support [message #18095] |
Mon, 28 March 2005 17:26 |
Kim Moir Messages: 39 Registered: July 2009 |
Member |
|
|
Hi
First of all, many thanks to the foundation for sucessfully migrating
the eclipse.org infrastructure. The shiny new hardware and software
upgrades will make our days much more productive :-)
Secondly, is there is an updated status of the items on the committer
infrastructure requests list?
http://www.eclipse.org/webtools/committers/list.html
Specifically, item #7 regarding acquiring additional system
administrator resources. During milestone week, such as this week's 3.1
M6, we run five builds a day to allow developers in multiple timezones
to contribute to our builds. However, if there was a critical problem
with the eclipse.org infrastrucure, for instance at 1am EST, committers
lack a mechanism to contact the foundation and receive an immediate
response. This could be very costly in terms of team productivity.
Given the importance of eclipse.org infrastructure to the committers and
its visibility as a web site, additional human resources should be
allocated to supporting it. It would also allow the items on the above
list above to be implemented more quickly.
Kim Moir
Eclipse Platform Release Engineering
|
|
|
Re: eclipse.org infrastructure support [message #18103 is a reply to message #18095] |
Mon, 28 March 2005 17:35 |
Eclipse Webmaster Messages: 607343 Registered: July 2009 |
Senior Member |
|
|
This list does appear to be outdated, and with the recent migration,
some items have been successfully implemented. I suggest the page be
updated to reflect this.
3. (item #16) Newer Faster Hardware.
This item is done. We currently have enough horsepower to grow 10-times
over, and perhaps more.
6. (item #7) Short URLs. Direct (short) URLs to project sections
This is available, and although I have sent out memos advising projects
to switch from ViewCVS to this, I have had medium response. ViewCVS is
inefficient for serving static html content, so the added bonus of
projects that switch over is releasing server cycles for something more
useful (like cvs itself)
16. (item #14) Central Password Authentication System.
Although Bugzilla is not using this mechanism, committers now only have
one userid/password for downloads, cvs and upcoming web-based self-serve
tools. New services added to the eclipse.org infrastructure must use
this centralized authentication.
17. (item #17) Leverage Mirrors. Leverage the mirrors to reduce
bandwidth. (see also 26)
This is done, and tools are available to leverage mirrors even more.
Many (many) thanks to the Platform releng team who proceeded to switch
over to this new mechanism, reducing our bandwidth consumption by at
least 30%.
I have also advised every download maintainer to switch to using the
"find a mirror" script for their downloadable content, but some pages
have not yet switched over, and link directly to download.eclipse.org.
Also, some links on downloads pages link directly to other project
downloads directly, bypassing the "find a mirror" script. Please see
the Requirements links on this sample page:
http://download.eclipse.org/webtools/downloads/drops/S-1.0M3 -200502260707/index.html
* Automatically redirect users to a geographically close mirror
based on the locale setting in their browser.
Although redirection is not automatic, users pick a mirror close to
them, like the MySQL downloads.
* Mirroring of all projects, not just the platform.
This is done. All projects are mirrored. Mirror sites choose the
projects they want to mirror, and currently each project has at least 6
mirrors.
20. (item #24) QoS Bandwidth Throttling.
This is already in place. CVS and mirrors have priority bandwidth (up to
a combined 72 %) over regular downloads.
Denis
Kim Moir wrote:
> Hi
>
> First of all, many thanks to the foundation for sucessfully migrating
> the eclipse.org infrastructure. The shiny new hardware and software
> upgrades will make our days much more productive :-)
>
> Secondly, is there is an updated status of the items on the committer
> infrastructure requests list?
>
> http://www.eclipse.org/webtools/committers/list.html
>
> Specifically, item #7 regarding acquiring additional system
> administrator resources. During milestone week, such as this week's 3.1
> M6, we run five builds a day to allow developers in multiple timezones
> to contribute to our builds. However, if there was a critical problem
> with the eclipse.org infrastrucure, for instance at 1am EST, committers
> lack a mechanism to contact the foundation and receive an immediate
> response. This could be very costly in terms of team productivity.
>
> Given the importance of eclipse.org infrastructure to the committers and
> its visibility as a web site, additional human resources should be
> allocated to supporting it. It would also allow the items on the above
> list above to be implemented more quickly.
>
> Kim Moir
> Eclipse Platform Release Engineering
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03552 seconds