Atlas-connect-l mailing list

["Dr. Harinder Singh Bawa" <harinder.singh.bawa AT gmail.com>]

Great! If its not difficult to switch back to old one in case of any problem, then we would like to switch to new one and test that. Let us know what you need from us.

thanks

Harinder

On Tue, Oct 21, 2014 at 1:44 PM, David Lesny <ddl AT illinois.edu> wrote:

Harinder,

When I get a chance I will change AtlasConnect to your new headnode.

I was able to login into it with the glidein account, so I do not believe there should be a problem.

Since it shares the same "home" space as the account on the old head node,
it would not be possible to have two head nodes at the same time with a lot of extra work at my end.

If the new head node fails to work for some reason, it will be easy to switch back to the old

I will let you know when I get the change made. Hopefully late today

dave

On 10/21/2014 2:23 PM, Dr. Harinder Singh Bawa wrote:

Hi Rob,

We have made new headnode for our T3 (Having SLC6). We have connected 2 working nodes on it.  So now, We have old head node with 16 working nodes and new headnode with 4 working nodes. Eventually we will replace our new node with old one. We tested internally and its running great!

Only thing, we would like is to verify is that if our new headnode needs anything special for "atlasconnect" jobs. In order to do this, Is there any way we can connect our new headnode (like we did for old headnode) to atlasconnect, 

Like for old headnode we have pool "fresnoatlas" or I direct atlasconnect through "IS_RCC_fresnostate"

similar, Is it possible that for new head node, we have pool like "newfresnoatlas" or some appropriate name, so that I can direct my jobs through atlas connect to my new headnode for testing purpose. (IS_RCC_newfresnostate).

If all goes well, we can replace our new with old  and our T3 would be having upgraded to SLC6 and latest softwares/

thanks

Harinder

On Tue, Oct 21, 2014 at 12:13 PM, Rob Gardner <rwg AT hep.uchicago.edu> wrote:

Hi Jay,

We don’t have specific pre-production test. What you’ve done is probably sufficient.  Once you’re ready with the new node, let us know.

Rob

On Oct 21, 2014, at 11:47 AM, Jay Fowler <fowler AT csufresno.edu> wrote:

We built a new server to replace our existing head node in our t3 environment.  Is there a way to validate the new instance through atlas connect before making it production?  Initial local testing seems to be good ( setupATLAS, diagnostics, supportInfo )?

    https://ci-connect.atlassian.net/wiki/display/AC/How+to+Select+Sites

I would like to be able to submit a job through Atlas Connect, requiring that it hit a different head node.  Once we can validate our testing, we would like to request that "IS_RCC_fresnostate" point to the new head node.

The new head node will use a different IP and FQDN ... the domain is changing:   t3head.atlas.fresnostate.edu  ...

Jay

--

_______________________________________________
Atlas-connect-l mailing list
Atlas-connect-l AT lists.bnl.gov
https://lists.bnl.gov/mailman/listinfo/atlas-connect-l

_______________________________________________
Atlas-connect-l mailing list
Atlas-connect-l AT lists.bnl.gov
https://lists.bnl.gov/mailman/listinfo/atlas-connect-l

--

Dr. Harinder Singh Bawa

                                          
[web][facebook][youtube][twitter]

_______________________________________________
Atlas-connect-l mailing list
Atlas-connect-l AT lists.bnl.gov
https://lists.bnl.gov/mailman/listinfo/atlas-connect-l

--

David Lesny

Senior Research Physicist (Retired)

High Energy Physics
University of Illinois at Urbana-Champaign

Office: 217-333-4972  |  Fax: 217-333-4990

Skype: ddlesny | mwt2-ddlesny

--

Dr. Harinder Singh Bawa

                                          
[web][facebook][youtube][twitter]