Hi all,
I think some clarification is needed here.
- There will be no gLite-MON in gLite3.2. The reason is simple: the next version of APEL is not based on RGMA and there is no need of a gLite-MON
- If there is no monbox, we still need to define where the APEL publisher will be deployed in 3.2. We are now in the process of introducing a gLite-APEL node for that purpose (this is what will replace the monbox)
- certification of this new node type, as well as of the new APEL publisher code, is underway. It has been decided that we will certify it for 3.2 only.
- We are currently beta-testing the whole ActiveMQ architecture, proposing to volunteering sites a non-certified 3.1 version of APEL publisher (as an upgrade of the Monbox). This client version will never be certified but this still validates the server side architecture.
- We want to keep the number of beta-testing sites low, but if all tests are successful we might also propose the package to sites having recurrent problems with RGMA.
Cheers,
Gilles
--
Gilles Mathieu
EGEE/WLCG - GOCDB development team
RAL-STFC, Didcot OX110QX, UK
+44 1235 446 340
"deadline for complaints was yesterday"
> -----Original Message-----
> From: LHC Computer Grid - Rollout [mailto:[log in to unmask]]
> On Behalf Of Burke, Stephen (STFC,RAL,PPD)
> Sent: 13 May 2010 00:10
> To: [log in to unmask]
> Subject: Re: [LCG-ROLLOUT] gLite 3.2 :: MON (???)
>
>
> "Cristi Magherusan" <[log in to unmask]> said:
> > It seems this patch got stalled for almost
> > a month now, so I wonder
> > what's blocking this from getting into production.
>
> It isn't really stalled, this is a new node type which is still under
> construction. Patches can stay in "with provider" for some time, the
> release process doesn't start until they get moved on from that state.
>
> Stephen
|