As the migration deadline of June 15th is getting closer, I am happy to report things are well underway with the migration of our environments. Earlier this month, @Daryl Herzmann, @Dave Cridland and myself started having regular meetings with @John Atherton and his coworkers at Surevine. A battle plan is being drafted, and the first few steps towards creating our new home have been completed. Thing are moving faster and faster these last few days. We now have access to our new environment, in which the first few components are starting to materialize.
3 Likes
Ā”Thanks for your support!
Will the hardware be replaced by virtual machines? Getting rid of some users, outdated $HOME-data and sudos may make sense.
Thanks for the update
So, what is the state of the migration? I know that it is mostly done. Not sure if you still going to use same online document, but i have added a few things (ssl for website and jira (bamboo also?) and bamboo build plans (many are in failing or queued state)).
I have virtual Mac software if you need it. Its very simple to set up - it only requires Vmware (obviously), patch software (Windows/Linux/ESX/OSX), and the VM files (about 20gb). Its quite up to date - its OSX 10.11 El Capitan. If you like i can upload it somewhere for you?
1 Like
Well, the migration is getting there. Yesterday, our old servers were switched off, and I heard no-one that actually noticed that - so thatās a good sign. There indeed are some loose ends. To address your questions:
- SSL for the website: that should already be working? Ignite Realtime: a real time collaboration community site works fine for me.
- For the Atlassian Stack, we need new certificates. Thatās a work-in-progress.
- The Bamboo plans are another work in progress. Restoring all build plans is time-consuming, as weāre using build agents that are slightly different from the old ones - which makes a big difference for Bamboo. Weāre getting there, though.
If you go specifically to https, then yes. But the links in the top menu go to non-ssl. So maybe they should be changed, or at least some redirection introduced.
HTTP for the web site is fine for me. I donāt think that one can log in there or transfer sensitive data.
One could use SSL for the downloads.
I donāt care much myself about using SSL on a simple website. But if we already have one, one not leverage it? For consistency. And hey, whole Internet is jumping into SSL band wagon (even with purely representative sites). I think Google also promotes that by putting https sites higher in the search results.
A scary trend, even with HTTP2. And we do not yet support HTTP2. Caching getās impossible and thus traffic (=costs) increase. Also SSL handshakes consume CPU cycles (=energy) so one may want to avoid them.
For Jira and the Community it makes sense for loggeg in users, while lurkers/anonymous may use HTTP.
LG will ālikeā this https://letsencrypt.org//2016/06/22/https-progress-june-2016.html