Proposal to Move Diaspora Pod to Noida datacentre
Hi Praveen,
I would like to propose the migration of Diaspora Pod from our Gurgaon Server to Noida data-centre server.
More resources can be provided to the pod in Datacentre as compared to the existing resources.
Let me know wdyt.
Regards,
Saurabh J
Pirate Praveen Mon 4 Apr 2016 4:54AM
@isaagar volunteered to update diaspora in our current setup. He'll have to update ruby too.
We'll track progress of it here https://gitlab.com/piratemovin/diasp.in/issues/3
Pirate Praveen Wed 21 Sep 2016 8:25AM
@saurabh I think we should migrate the vm as soon as possible. OS migration can be considered later. I think we can just copy the virtual disk. How soon can we do it?
Rahul Krishnan R A Thu 22 Sep 2016 12:01PM
@praveenarimbrathod @saurabh @isaagar we would schedule a time for the diasp.in migration
Pirate Praveen Fri 30 Sep 2016 1:59PM
We discussed about it on our XMPP room (diasp.in@groups.poddery.com). It seems @amardeepsingh is busy for next 2-3 weeks and we can do the migration only when he is available.
Pirate Praveen Fri 30 Sep 2016 2:01PM
The plan is to import the kvm qcow2 image (in Gurgaon) directly into openstack (in Noida).
Pirate Praveen Sat 1 Oct 2016 10:55AM
@amardeepsingh assigned a new ip for diasp.in (182.74.5.230) on airtel connection (our current connection is tata) as a backup yesterday. We have configured the server with new ip, but we are not able to ping the server yet, possibly firewall needs adjustments. Amardeep is checking the issue.
Once we fix the issue with new ip address, we can add the second ip to dns and use the round robin method to fix the current reliability issue. If the reliability issue is fixed by this step, we can postpone the server migration until hamara sugam with debian is released.
Fayad Fami Fri 13 Jan 2017 5:22PM
We got removed from podupti.me again on 11th for the outdated version.
So there is work required before migration like testing the update path and taking full backup.
Just a thought. Instead of updating from the existing version can we restore data onto a fresh install of 0.6.0.0. If yes then as @praveenarimbrathod mentioned we can try on stretch and make it hamara by adding hamara repository when ready.
If @amardeepsingh can join us I think we can plan this better.
Pirate Praveen Sat 14 Jan 2017 3:06AM
I suggest we update on the current hamara as we don't know when the debian based hamara is going to be released (we already got delayed a lot waiting for that initially). If at all we are going to move to debian first, we still have to move to 0.5.2.0 first and then do an upgrade as it is not a good idea to change too many things at once.
I Sagar Sat 21 Jan 2017 7:19AM
I think as @praveenarimbrathod said we should update to 0.6.0 on current hamara . Hamara sugam is still in pre-alpha stage so it will take time for stable release.
@praveenarimbrathod can you list out steps for upgrade process ??
Pirate Praveen · Sun 3 Apr 2016 8:31AM
@saurabh @vik @amardeepsingh @rajudvindane with so frequent down times, I think moving to new data centre has to be a priority. With Hamara Sugam getting delayed, I suggest we move to debian stretch directly and switch repos to Sugam when it is ready.