The new install's ready to launch, we'll be combining www.gluster.org and blog.gluster.org to one install at gluster.wpengine.com. Let me know what's required to complete this before EOD Friday. Thanks!
What about the existing redirections we did put in place: e.g. all stuff that can be fond in the various files here: https://github.com/gluster/gluster.org_ansible_configuration/blob/master/roles/httpd_www/tasks/main.yml Also, why is the infra team not warned more in advance of any change ?
Another notes: - if the plan is to change the DNS, we would need more than 48h to do it in advance. The change is fast to do (< 5 minutes), but we can't be sure it is gonna be propagated everywhere without doing more preparation (due to world wide cache) - I also want to remind that doing change on friday is frowned upon because I am not on-call. As I said before, people can contact HR in Paris that will be happy to explain why this is not the case (and the required compensation for that).
When would be a better time for this? We're looking at a release late this week/early next week so ideally we'll plan around that as well. I know that we may also need to look at the Let's Encrypt certificate, WPEngine supports Let's Encrypt. It's my preference to deprecate blog.gluster.org as a domain name and just use www.g.o as we may not be able to have a wildcard SSL cert on this.
Well, for a start, I am still unsure on what is requested exactly. A dns change would need to be done in advance, would requires to change the vhost on wpengine side (which wasn't done on friday, hence no change until further clarification). A redirect would be immediate, but would be not optimal (but we keep existing redirects). It may requires further redirects to be added too, in which case we need to know what should be redirected and where, espeially for the older url. So if you want the DNS change, I need to know what I should point too, I guess a CNAME on gluster.wpengine.com.
Pretty sure that WPEngine won't let us do vhost editing, but we can do redirect rules in regex. https://wpengine.com/support/regex/ Does this meet the requirement for better redirects?
So without vhost change on wpengine side, we have to do it on the http level, and that's basically a redirection on supercolony, as being asked. So to be clear, you want the integrality of the requests coming to www.gluster.org and blog.gluster.org to be redirected to gluster.wpengine.com ? If you want sometime more fine grained, please tell me the mapping you want and I will add it to the long list we already have. We can also do a reverse proxy, but the current reverse proxy setup is not production ready and I was hoping to work on it (e.g., reinstall it at will) in the coming weeks. I can do something hackish on supercolony, but since that's a EL6 host, we didn't test the automation there and it may break in interesting way so I would rather avoid that. So tell me which options: - redirect, fast, easy, less fragile and easy to revert if things go wrong, but the urls will change - proxy, no url change, more flexibility around, but may not work since that wasn't tested with that setup (and more fragile for now) Due to urgency of the request, I will use the option "redirect" if I didn't heard otherwise by noon CEST ( 6 a.m. EST, 3 a.m. PDT )
Done, the redirections are in place.
Ouch! I don't need to expose the gluster.wpengine.com to everyone -- I need this to stay the same as www.gluster.org. I really wish that we'd gotten confirmation on this instead of just pushing ahead.
Ok I revert, no problem.
Please have www.gluster.org be the publicly available URL. CNAME record gluster.wpengine.com A record 35.197.52.145 Primary domain gluster.wpengine.com
So as asked on irc, I changed the DNS: commit d2bfdf9cb849648f0295057dd48d58c93f723640 Author: Michael Scherer <mscherer> Date: Thu Aug 31 16:42:43 2017 +0200 Move the CNAME to go on wpengine diff --git a/prod/external-default/gluster.org b/prod/external-default/gluster.org index c7a60c2..1a49c46 100644 --- a/prod/external-default/gluster.org +++ b/prod/external-default/gluster.org @@ -1,6 +1,6 @@ $TTL 300 @ IN SOA ns1.redhat.com. noc.redhat.com. ( - 2017083101 ; Serial + 2017083102 ; Serial 3600 ; Refresh 1800 ; Retry 604800 ; Expire @@ -16,8 +16,8 @@ $TTL 300 IN A 198.61.169.132 mx1 IN A 198.61.169.132 supercolony IN A 198.61.169.132 -www IN CNAME supercolony -blog IN CNAME supercolony +www IN CNAME gluster.wpengine.com. +blog IN CNAME gluster.wpengine.com. lists IN CNAME supercolony planet IN CNAME supercolony
Is this bug fixed?
The issues that have arisen from this ticket have been ticketed separately. Marking as closed.