JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for LCG-ROLLOUT Archives


LCG-ROLLOUT Archives

LCG-ROLLOUT Archives


LCG-ROLLOUT@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

LCG-ROLLOUT Home

LCG-ROLLOUT Home

LCG-ROLLOUT  2005

LCG-ROLLOUT 2005

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: VO boxes (was LCG-2_7_0 sooner or later ....)

From:

Markus Schulz <[log in to unmask]>

Reply-To:

LHC Computer Grid - Rollout <[log in to unmask]>

Date:

Wed, 14 Sep 2005 08:59:26 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (119 lines)

Dear Henry,
I have a few comments and a few questions.

As you stated correctly each and every sgm can move code to any of  
her VO's vo-boxes and
run the code as a mapped user.
I don't see a fundamental difference between this and the ability to  
run long running jobs on a batch system through the grid.
In both cases the sysadmin has no effective control over what code  
the users run and a 48h job with external network connectivity is
not so different from what the users can do on a VO box. Since the  
farms give by one way external network access the VOs could implement  
with a bit of
additional complication their service like programs as a series of  
long running jobs that use the local SE for keeping the state.
 From the security point of view I can see no difference between  
giving access to a WN or the VO box. In both cases the users can be  
traced and
are mapped to a local user. In both cases the user can bring non  
security reviewed software to the site.

The question that I have are of practical matter:
You mention that you have to make sure that you are responsible that  
people don't misuse the service (as an example you
mention the storage of ripped movies).
How do you ensure this? Are you in control of what the users store on  
your site and what software they run?

            markus


On Sep 14, 2005, at 2:24 AM, Henry Nebrensky wrote:

> On Wed, 7 Sep 2005, Burke, S (Stephen) wrote:
> ...
>
>> I'd like to add my 2 cents' worth, as someone who has not so far been
>> involved in any of the discussions. To me it seems rather strange  
>> to see
>> that "a VO box" is a vital baseline service - as I understand it  
>> these
>> are not services, but containers for services.
>>
>
> I thought that tomcat (as found in the MON box) was a service  
> container -
> and a Grid-aware one at that...
>
> Anyway, I'm still trying to find out how these VO-boxes are planned  
> to be
> used, in particular what services they make available and where  
> they are
> accessed from. Google threw up
>     https://uimon.cern.ch/twiki/bin/view/Atlas/DDMSc3
> which is a start but still incomplete - is the apache accessed from
> outside the site? How does security monitoring and response work?
> The result is that at present I don't believe we would be ALLOWED to
> deploy a VO-box here, and I get the impression the situation is  
> similar at
> other sites, though some admins may have more power to bend rules.
>
> Let me start at the beginning: in order for us to run an LCG site at
> Brunel, the University has identified some people, e.g. me, whose  
> job it
> is to make sure that Grid services (as an example, gridftp on the  
> SE) are
> firstly installed properly and then maintained (patched); and  
> secondly to
> make sure that people don't misuse the services (no ripped movies  
> in the
> datastore, etc.)
>
> As described in http://goc.grid.sinica.edu.tw/gocwiki/VOBOX_HowTo
> there is no way for a grid-admin like me to supervise a VO-box in that
> fashion - anyone[*] can upload and start a service at any time (and  
> also
> stop and remove an obsolete one).
>
> So if the grid-admins CANNOT be responsible for these services,  
> then the
> situation at least at Brunel University is trivially simple:
>
> ---------------------------------------------------------------------
> Experiments/VOs wishing to operate services on hosts inside Brunel
> University's network and/or externally visible within the brunel.ac.uk
> domain must apply in writing to the head to Computer Services here.
> ----------------------------------------------------------------------
>
> I don't see how anyone proposing something like a VO-box could be
> surprised with that - it's the obvious consequence of the VO-box idea.
>
>
> I probably won't be able to make the upcoming meeting, but I would  
> suggest
> that the details of how these things are supposed to work needs to be
> thrashed out (and not just what lives on which ports, but also things
> like how the thing fits into the incident response framework).
> Most of us directly involved with Grid *are* wanting to get it to
> work (and even do something useful)... but we have to remember that in
> order to do so we depend on others, who don't have that personal  
> interest,
> and have a conflicting set of pressures.
>
> Henry
>
> [*] The list of a VO's SGMs being dynamic and outside Brunel's control
> (and I suspect it would have to be more than one person - or would  
> these
> services all be shut down while the SGM is on holiday and can't  
> react to
> security issues)
>
> -- 
> Dr. Henry Nebrensky                     [log in to unmask]
>                              http://people.brunel.ac.uk/~eesrjjn
> "The opossum is a very sophisticated animal.
>  It doesn't even get up until 5 or 6 p.m."
>

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
March 2024
November 2023
June 2023
May 2023
April 2023
March 2023
February 2023
September 2022
June 2022
May 2022
April 2022
February 2022
December 2021
November 2021
October 2021
September 2021
July 2021
June 2021
May 2021
February 2021
January 2021
November 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
February 2018
January 2018
November 2017
October 2017
September 2017
July 2017
June 2017
May 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
2006
2005
2004
2003


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager