Move api.rackspace.com to Nexus
Closed this issue · 11 comments
After the moratorium, we would like to shut down the current api.rackspace.com website. I think it makes sense to redirect anyone who visits api.rackspace.com to developer.rackspace.com/docs. To do this, we could update the DNS so api.rackspace.com goes to Nexus, and that redirects the user.
@smashwilson: do you think we could make this change in January?
Is it possible to do slightly more fine-grained redirects such as to the service page rather than api landing page to docs landing page?
In terms of Deconst work, certainly: we'd only need to add a section to config/rewrites.json in the control repository for this to happen. You wouldn't even need me for that bit at all, it's just a PR to nexus-control, and it'd go live shortly after merge.
The most annoying bit will be getting the TLS certificate re-issued with new SANs. We could add launch.rackspace.com and a few www. variants while we were at it, though.
Is it possible to do slightly more fine-grained redirects such as to the service page rather than api landing page to docs landing page?
Yes, although it would be more tedious. Do we have a full map of api.rackspace.com to use as a reference?
There's not a lotta files, here's the list :)
api-ref-auto-scale.html
api-ref-backup.html
api-ref-big-data.html
api-ref-blockstorage.html
api-ref-databases.html
api-ref-email-and-apps.html
api-ref-files.html
api-ref-identity.html
api-ref-images.html
api-ref-keep2.html
api-ref-monitoring.html
api-ref-networks.html
api-ref-orchestration.html
api-ref-queues.html
api-ref-servers-ext.html
api-ref.html
I can write the PR for the config/rewrites.json and you can choose to merge after January, would that work?
Rackspace CDN - file name api-ref-raxCDN.html, I think - is also in the API reference and should be added to Anne's list above. (api-ref-raxCND.xml is definitely in the source at https://github.com/rackerlabs/docs-api-reference/tree/master/api-ref/src/docbkx.)
Thanks!
also these:
api-ref-raxCDN.html
api-ref-big-data-v2.html
@smashwilson can this issue be closed or do we need to wait on the certs?
@annegentle I've been trying to chase down the new certs for a week now. Just waiting on Thawte to re-issue with the new SANs. Let's keep this open until I get ship them.
From what I can tell, the certs have had api.rackspace.com added, but requests to that domain still route to the old servers. I'll figure out how to get those decommissioned, and then update the corporate DNS entry for api.rackspace.com -> deconst.
I've made a request to have the DNS changed. @annegentle do you know who owned/managed the internal infra for api.rackspace.com?
I think it must be @steveortiz and crew?