Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-papyrus.dev] [PROVENANCE INTERNET] Re: [PROVENANCE INTERNET] Fwd: [Papyrus-ic-steering-committee] Eclipse download server downtimes {Was: Re: LTS Member}
Papyrus is neither a member not an enterprise. However, CEA is an enterprise and is strategic member.



Envoyé depuis mon smartphone Samsung Galaxy.


-------- Message d'origine --------
De : LE FEVRE FRANCOIS <francois.le-fevre@xxxxxx>
Date : 15/09/2017 08:20 (GMT+01:00)
À : Papyrus Project list <mdt-papyrus.dev@xxxxxxxxxxx>
Objet : [PROVENANCE  INTERNET] Re: [mdt-papyrus.dev] [PROVENANCE INTERNET] Fwd: [Papyrus-ic-steering-committee] Eclipse download server downtimes {Was: Re: LTS Member}

Sebastien,

Thanks for this element.

Could you confirm if Papyrus project belongs to “Enterprise and Strategic Members of the Eclipse Foundation” ?

 

Francois

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de GERARD Sebastien
Envoyé : vendredi 15 septembre 2017 07:42
À : MDT::Papyrus. dev <mdt-papyrus.dev@xxxxxxxxxxx>
Objet : [PROVENANCE INTERNET] [mdt-papyrus.dev] Fwd: [Papyrus-ic-steering-committee] Eclipse download server downtimes {Was: Re: LTS Member}

 

FYI

 

 

 

Envoyé depuis mon smartphone Samsung Galaxy.

 

 

 

-------- Message d'origine --------

De : Mike Milinkovich <mike.milinkovich@xxxxxxxxxxxxxxxxxxxxxx>

Date : 14/09/2017 19:45 (GMT+01:00)

Objet : Re: [Papyrus-ic-steering-committee] Eclipse download server downtimes {Was: Re: LTS Member}

 

-------- Message d'origine --------

De : Mike Milinkovich <mike.milinkovich@xxxxxxxxxxxxxxxxxxxxxx>

Date : 14/09/2017 19:45 (GMT+01:00)

Objet : Re: [Papyrus-ic-steering-committee] Eclipse download server downtimes {Was: Re: LTS Member}

 

All,

Please review our new status page http://status.eclipse.org/

Your comments would be appreciated on the bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=261658

On 2017-09-12 11:24 AM, Mike Milinkovich wrote:

All,

Let me start by saying again that we regret the recent difficulties with our download servers, and the problems those outages have caused many of you.

We will be implementing a public status page at https://status.eclipse.org to help communicate future problems. You can follow the discussion about this development on bug 261658.

For your future reference, the IT Service Level Agreement that the Eclipse Foundation has had in place for many years with its community is documented here. Obviously anyone who is using Eclipse Foundation infrastructure for business critical processes should familiarize themselves with this document. Please note that Enterprise and Strategic Members of the Eclipse Foundation have access to enhanced IT support options.

Again, our apologies.

On 2017-09-08 5:15 AM, Klaas Gadeyne wrote:

Dear Mike,

 

We've been experiencing intermittent issues with download.eclipse.org over the course of four months. In order:

- misconfiguration due to the transparent mirroring system

- Apache httpd bug https://bz.apache.org/bugzilla/show_bug.cgi?id=53555

- Weekly DoS attack since beginning of August from China

- puppet configuration error (our mistake)

We used bug 515596 to track the issues, and an email to eclipse.org-committers on Aug 30 to help keep everyone informed.

The issue was also pointed out and briefly discussed on the cross-project-issues-dev mailing list. In general, that is the mailing list that you should subscribe to if you want to stay informed about any infrastructure issues. The usual pattern is that an issue is first raised there, and if it is not immediately resolved a bug is created. Mailing lists and bugs are the main public channels that we use at Eclipse.

Thank you for the heads up regarding the download.eclipse.org server status and the pointers to the relevant bugs! Yet, in our opinion, there is still room for improvement in terms of communicating to the ‘general public’ (as opposed to eclipse developers).

Typically, large open source projects use a status page (http://status.apache.org/ ) or use ‘low volume’ announce or dedicated infrastructure mailing lists ( https://lists.openstreetmap.org/listinfo/announce ) to communicate about such issues.  Download issues are not a developer only thing.

I personally took the following (non-successful) actions, without arriving at any of the items you described above:

·         Searched on bugs.eclipse.org (too many items, most of them very old)

·         Went over the descriptions in the mailing list summary page (https://dev.eclipse.org/mailman/listinfo ) to search for an appropriate mailing list to report/be informed about infrastructure issues

·         Did a couple of google searches “download.eclipse.org download problems” both with and without the additional “site:eclipse.org”

Several of my colleagues did similar things, and neither did they arrive at the pointers you gave above.

At least improving the mailing list description from the cross-project-issues-dev mailing list seems to be a very lightweight action that might help preventing other users from being frustrated.

At this time, we have identified the patterns and are confident that all issues with download.eclipse.org will be resolved soon.

Great!

Best regards,

Klaas

 

 

--
Mike Milinkovich
mike.milinkovich@xxxxxxxxxxxxxxxxxxxxxx
(m) +1.613.220.3223

EclipseCon Europe 2017



_______________________________________________
Papyrus-ic-steering-committee mailing list
Papyrus-ic-steering-committee@xxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.polarsys.org/mailman/listinfo/papyrus-ic-steering-committee

 

--
Mike Milinkovich
mike.milinkovich@xxxxxxxxxxxxxxxxxxxxxx
(m) +1.613.220.3223

EclipseCon Europe 2017

Back to the top