Atlas-connect-l mailing list

[Rob Gardner <rwg AT hep.uchicago.edu>]

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