EIC/BNL Computing discussion

[Maxim Potekhin <potekhin AT bnl.gov>]

Hello Jerome,

Perhaps the EICUG Steering Committee can give some answers to that.

One important detail however is that the EICUG is expressly not
a "DOE experiment". It's an international community.

This makes a difference in a few separate ways.
EICUG is not subject to same requirements and according to
many should stay this way.

Maxim




On 6/9/21 3:43 PM, Jerome LAURET via Eic-bnl-comp-l wrote:
>     Relying on a hosting service and moving to ... another hosting
> service with different technology solution, how easier they seem, will
> not change the underlying issue: dependencies in what your provider
> imposes / decides.
>
>     There is expertise at the SDCC for Drupal. Upgrades would not
> be on a "casual admin/user" but experts. it is not that the EIC UG
> instance have used that many modules (and I am not aware of custom
> modules).
>
>     Continuing the path of hosting DOE experiment's information in
> the wild is not good in my opinion. There will be a lack of integration
> with community standards and wide move across all DOE agencies and
> facilities (such as Federated ID) and soon enough, a divergence from
> DOE requirements.
>
>     Regards,
>
>
> On 2021-06-09 15:32, Maxim Potekhin via Eic-bnl-comp-l wrote:
> > Hello Jerome,
> >
> > This was discussed in a long thread with Thomas and Elke and recently at
> > the EICUG Steering Committee as well as mentioned in the software group
> > discussions.
> >
> > The issue is this:
> >
> > a) there are mandated PHP version bumps required by the hosting 
> > service - the BlueHost
> > This trigger (or will trigger) Drupal version migration
> >
> > b) there is compatibility matrix of PHP vis a vis Drupal itself and 
> > the installed modules
> >
> > c) previously Drupal upgrades were direct (and I've done one or two), 
> > and now with version 8
> > to be required within the next few months this is no longer 
> > transparent. Then there will be
> > version 9 of course.
> >
> > These migrations are now quite involved and require level of 
> > expertise way above
> > casual admin/user.
> >
> > Instead of being subject to the continued tech debt/liability of 
> > keeping up with the version
> > creep and complex upgrades it was proposed to shift to a platform 
> > which is a lot simpler
> > to maintain.
> >
> > Best regards,
> >
> > Maxim
> >
> >
> >
> >
> >
> > On 6/9/21 2:51 PM, Jerome LAURET via Eic-bnl-comp-l wrote:
> > > From the bi-weekly EIC news, I read
> > >
> > > > The EICUG is facing increasing issues with maintaining their Drupal 
> > > > based web site (eicug.org). The
> > > > agreed plan is to drop Drupal and redesign the web site based on 
> > > > possibly Jekyll in conjunction with
> > > > github. Main concern is to maintain the links to important EICUG 
> > > > documents that are referenced
> > > > extensively (White Paper, Yellow Report etc).
> > >
> > > Where was that discussed exactly and what kind of "increasing issues"
> > > did the EIC faced? I have not seen anything discussed in the standard
> > > mailing lists.
> >
> > _______________________________________________
> > Eic-bnl-comp-l mailing list
> > Eic-bnl-comp-l AT lists.bnl.gov
> > https://lists.bnl.gov/mailman/listinfo/eic-bnl-comp-l