First attempt at registering new AP40 Pelican origin (INF-1796) #3784
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
brianhlin
force-pushed
the
INF-1796.new-ap40-origin
branch
from
5e92202 to
e70e684
Compare
brianhlin
force-pushed
the
INF-1796.new-ap40-origin
branch
2 times, most recently
from
075db1a to
0b5485e
Compare
Co-authored-by: Matyas Selmeci <[email protected]>
The previous URL is the CNAME that points to ospool-ap2040.chtc.wisc.edu
brianhlin
force-pushed
the
INF-1796.new-ap40-origin
branch
from
0b5485e to
aeaebe5
Compare
matyasselmeci
approved these changes
May 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is going to be a very odd registration: we currently have the production AP running on
ap40.uw.osg-htc.org, akaospool-2040.chtc.wisc.edu. However, we need to stand up a new origin on decent hardware asorigin-auth2001is falling over under load. We are using the new AP40 hardware,ospool-2140.chtc.wisc.edufor this in a similar setup to the UC APs (we plan to do an in-place replacement of the old AP40 with the new AP40).I'm not sure what the right registrations are here exactly:
/ospool/PROTECTEDfrom the new origin to address the acute issue/ospool/ap40/datawith the future AP40 transitionI'm not entirely sure what the issuers should be and the relevant FQDNs across the different fields.