Daniela/All
The outcome of the request for more status information on release components going through into an EGI release has resulted in this from SA2:
"it was decided to provide read access to the software provisioning queue in RT, and the corresponding dashboard for everyone with an SSO account:
http://go.egi.eu/SoftwareProvisioningQueue
http://go.egi.eu/SoftwareProvisioningDashboard"
This looks like a useful summary that will be kept updated. Perhaps the only issue is the need for an SSO account. I suspect many of you will have an account but probably not all.
Jeremy
On 17 Jun 2011, at 10:09, Jeremy Coles wrote:
> Hi Daniela
>
> I agree that the status and further information should be readily accessible. I hunted around and found some sources but nothing as useful as the gLite example. I took this up with Mario et. al. and they will now discuss ideas (such as using RSS and a digest page) in Monday's EGI ops meeting. He suggested in the meantime that we refer to
> the "staged-rollout" RT queue which is read accessible to everyone: https://rt.egi.eu/rt/index.html. Reading RT queues is not a great way to quickly find out the status but it may be helpful until a proper summary page is put in place.
>
> Jeremy
>
>
>
>
> On 16 Jun 2011, at 12:02, Daniela Bauer wrote:
>
>> Hi Jeremy,
>>
>> thanks for the update, but this (the status) should be on the web and
>> not hidden in some minutes !!!
>>
>> Cheers,
>>
>> Daniela
>>
>>
>>
>> On 16 June 2011 11:56, Jeremy Coles <[log in to unmask]> wrote:
>>> Hi Daniela/All
>>>
>>> To add to the previous responses.
>>>
>>> The picture given at the GDB last week is given in these slides http://indico.cern.ch/materialDisplay.py?contribId=4&sessionId=0&materialId=slides&confId=106645. EMI has released EMI-1 but many components are still in staged-rollout so not fully tested and approved for wider rollout on the EGI infrastructure as part of the Unified MIddleware Distribution. There was discussion at the GDB about taking components needed by WLCG earlier than EGI approve them but we would still need to validate. It looks like ARGUS is not ready. The WMS was also rejected during staged rollout.
>>>
>>> (Sorry if this repeats other emails I've just seen arrive!)
>>>
>>> Jeremy
>>>
>>>
>>>
>>>
>>>
>>> On 16 Jun 2011, at 11:49, Sam Skipsey wrote:
>>>
>>>> On 16 June 2011 11:46, Stephen Burke <[log in to unmask]> wrote:
>>>>> Testbed Support for GridPP member institutes [mailto:TB-
>>>>>> [log in to unmask]] On Behalf Of Daniela Bauer said:
>>>>>> I thought the EMI release means exactly that: It's out and we should
>>>>>> sue it.
>>>>>>
>>>>>> What am I missing ?
>>>>>
>>>>> That the infrastructure is run by EGI and not EMI ... the theory is that EGI is supposed to certify and repackage the middleware from EMI (and potentially other sources) in something called the UMD (Unified Middleware Distribution), and then put it to staged rollout before officially releasing it. I believe the target date for the release is 4th July.
>>>>
>>>> Really? That seems faster than I'd been led to believe (certainly, an
>>>> early estimate was that the certification would take more weeks than
>>>> that).
>>>>
>>>>> Whether that turns out to be sustainable is not obvious, it may be that people will just start installing things directly from EMI. In EGEE you could have done the same by grabbing rpms from etics as soon as they were certified, but it was more hidden so there was less temptation.
>>>>>
>>>>
>>>> From a GridPP Storage perspective, we're happy to for people to
>>>> upgrade from EMI rather from UMD/EGI, for the record.
>>>>
>>>> Sam
>>>>
>>>>> Stephen
>>>>>
>>>
>>
>>
>>
>> --
>> -----------------------------------------------------------
>> [log in to unmask]
>> HEP Group/Physics Dep
>> Imperial College
>> Tel: +44-(0)20-75947810
>> http://www.hep.ph.ic.ac.uk/~dbauer/
|