Just two hours ago I wrote @claudiu privately that now it is Sunday 21 night in Argentina and
I will not be able to close the current AWS account and to configure the service in the new one until at least Wednesday 23rd; and that the same happens to me with respect to the DO droplet transfer.
So, @son_of_bob, from my part I think it would be great if you could do it sooner yourself.
Thanks for the heads up @Miguel. I will let you and @claudiu know if I hit any blockers.
I will start on it today. I have read through the documentation.
Do you want me to take a live snapshot so as to not shut down the droplet? They mention there can be data inconsistencies via this method, but as we are only testing, should be fine right?
The documentation is outdated, the instruction to Change Owner now seems to be Transfer Snapshot instead.
Additionally, the option is to transfer to a user or a team. If I look at the team option it is blank for me.
I assume I don’t have Member or Owner role in the new default My Team in the new DO account. Do you want to add this permission or shall I transfer via User via the Email address option?
(quote below from documentation)
If you’re transferring a snapshot to a team you’re a member of, you can accept the transfer yourself if you have the Member or Owner role. If you have the Billing role, you may need to contact a Member or Owner.
The whole accept or decline options mentioned in the documentation didn’t happen. It has just appeared in the new team without any additional need to accept or confirm.
With the Create a droplet from snapshot steps I need to define the other plan details.
So we have the following to consider:
Plan
CPU items
Additional block storage : I am assuming this is related to the additional volume you have on the original?
Datacenter region
VPC Network
Authentication
There are some additional options such as enabling monitoring, IPv6, etc.
I would say to just set it up the same as the old one, which seems to be working fine.
For root pwd you can pick one, we need to set up SSH key access anyway, and doubt we’ll need the root pwd much. but store it somehow and you can communicate it to us securely later
Ok, just having to familiarise myself where all the different settings are stored.
We have 20GB additional volume then which seems to be Ext4 filesystem type.
It also seems like backups are also enabled at an additional cost of $2.4/mo.
So, the cost of the new droplet settings I picked with this additional volume and backups enabled would bring the cost to:
$12/mo + $2/mo + $2.40/mo = $16.40/mo
Are we happy with this?
In the original, I can see IPv6 is not enabled, but Monitoring is, at least with the graphs. I wasn’t sure how to confirm if User data setting is on.
Yes, default option was root password so switched to SSH key instead and there is no password needed just have to generate keys.
Should I just accept the hostname as the default applied from the snapshot name and settings? If you have a preferred alternative or other format you would like me to use let me know.
Do you have an SSH key for me to use or you happy for me to generate my own? I have Windows subsystem for Linux, with Ubuntu 20.04 setup, so I can use the command line for that to generate the key?
Sure, in my field we use for signing assemblies but use .snk format files. This is just a slightly different use case and scenario to what I am used to.
My bad, weird tab reload issue. I had both tabs open, one on your team and one on the other. It seems when I have re-opened Chrome this morning the first tab flipped to the AIAFF Team rather than stay on your team, so I was stupidly comparing IP addresses for the same droplet in two tabs lol.
Ignore me, they are different.
Interesting that it didn’t keep that first tab set on the other team, I had to click switch teams again. Is good that you have changed the name of the teams and the colour of the images for teams are different. I will make sure to be careful of re-checking that in future.
So, this means that you just need to sort out DNS settings right?
The IP address is 143.198.48.132 however, it seems to redirect you to https://discuss.actualism.online, i.e. the live version of the site and not the point of data as captured in the droplet.
Ok, let me know if you need me to do anything else.
Could you look into a way to test if it works? I don’t have any ideas currently. Maybe you can reconfigure the domain on it to a temporary one (using no-ip.com ) and then see it works … or maybe there’s a way for it to work just with the IP.