Closed mark-dce closed 4 years ago
The services are on this ECS in Spinup: https://spinup.internal.yale.edu/r/spinup-0010eb-cantaloupeIIIF
Ports Cantaloupe: 8182 Manifest: 80 Blacklight: 3000
I've also mapped the Cantaluope and manifest services (/manifests/*
URLs) servers through Nginx on spinup-0010ef.spinup.yale.edu, using a self-signed cert. This instance can be discarded when we have the F5 up and running.
Note that to work with the new URLs we'll need to make some updates:
config.hosts
variable to the deployed URL (see https://github.com/yalelibrary/yul-dc-blacklight/issues/18 )instead of:
https://dl-test.library.yale.edu/ -> http://container:3000 https://iiif-test.library.yale.edu/manifests -> http://container:80 https://iiif-test.library.yale.edu/images -> http://container:8182
is it possible we could do:
https://dl-test.library.yale.edu/ -> http://container:3000 https://iiif-manifests-test.library.yale.edu/ -> http://container:80 https://iiif-images-test.library.yale.edu/ -> http://container:8182
This has some advantages, namely simplifies load balancer config, also allows us to move/scale these services around w/ less effort (i.e. separate containers) if ever needed.
ServiceNow ticket INC1746404 created:
Please create the following DNS entries using IP's from 172.18.68.0/22 (dev)
vip-dl-test.library.yale.edu CNAME: dl-test.library.yale.edu
vip-iiif-manifests-test.library.yale.edu CNAME: iiif-manifests-test.library.yale.edu
vip-iiif-images-test.library.yale.edu CNAME: iiif-images-test.library.yale.edu
Submitted INC1747621 for F5 VIP https://dl-test.library.yale.edu -> spinup-0010eb-cantaloupeIIIF.svc.spinup.yale.edu:80 . (Ports 3000 and 8182 to follow)
Ended up working with ITS and went the "cloud native" route. Waiting INC1747859 to re-point DNS to the Amazon IP.
dl-test.library.yale.edu as a CNAME for internal-library-it-internal-1983206671.us-east-1.elb.amazonaws.com
iiif-manifests-test.library.yale.edu as a CNAME for internal-library-it-internal-1983206671.us-east-1.elb.amazonaws.com
iiif-images-test.library.yale.edu as a CNAME for internal-library-it-internal-1983206671.us-east-1.elb.amazonaws.com
DNS entries pointing to AWS load balancer are in effect now:
$ host dl-test.library.yale.edu
dl-test.library.yale.edu is an alias for internal-library-it-internal-1983206671.us-east-1.elb.amazonaws.com.
internal-library-it-internal-1983206671.us-east-1.elb.amazonaws.com has address 10.5.36.237
internal-library-it-internal-1983206671.us-east-1.elb.amazonaws.com has address 10.5.32.126
$ host iiif-manifests-test.library.yale.edu iiif-manifests-test.library.yale.edu is an alias for internal-library-it-internal-1983206671.us-east-1.elb.amazonaws.com. internal-library-it-internal-1983206671.us-east-1.elb.amazonaws.com has address 10.5.32.126 internal-library-it-internal-1983206671.us-east-1.elb.amazonaws.com has address 10.5.36.237
$ host iiif-images-test.library.yale.edu iiif-images-test.library.yale.edu is an alias for internal-library-it-internal-1983206671.us-east-1.elb.amazonaws.com. internal-library-it-internal-1983206671.us-east-1.elb.amazonaws.com has address 10.5.32.126 internal-library-it-internal-1983206671.us-east-1.elb.amazonaws.com has address 10.5.36.237
We are getting what looks like a Rails error on https://dl-test.library.yale.edu/
This is on SpinUp, not ECS, so need a separate ticket for this problem for ECS (McClain seems to know how to fix this?).
STORY Build out the service paths for the the
test
environment on SpinUpACCEPTANCE I can reach
For additional context and details see https://docs.google.com/presentation/d/1p58-Prs_ZQAqAj73uYvt8YIRhl02edc-ivNUkj8RtY4/edit#slide=id.g722593bcb2_1_0