On Mon, Jan 6, 2020 at 1:48 PM sebb <seb...@gmail.com> wrote: > > On Mon, 6 Jan 2020 at 18:32, Sam Ruby <ru...@intertwingly.net> wrote: > > > On Mon, Jan 6, 2020 at 8:21 AM sebb <seb...@gmail.com> wrote: > > > > > > Do we want to start the process of migrating to whimsy-vm5? > > > > Setup needs to be completed. There still are a number of commented > > out sections in > > infrastructure-p6/data/nodes/whimsy-vm5.apache.org.yaml and > > infrastructure-p6/modules/whimsy_server/manifests/init.pp > > > > > Yes, I assume that is to stop accidental access to the system.
As the one who was setting this up, I can assure you that that wasn't my motivation. > I would rather change the port before attempting to enable these. I don't see the point (one would have to intentionally visit whimsy-vm5, and one could equally intentionally specify a port), but if this is something you would like to do, go for it! > > Some decisions will need to be made. For example, I would recommend > > no rvm this go around - there is really no need to maintain multiple > > versions of Ruby. If the system provided ruby is not good enough, we > > can always use the brightbox debian repositories. > > > > > Almost all the data on the host is derived from SVN or Git, so I think > > most > > > of the code can be run in parallel, at least for testing. > > > > > > Exceptions include: > > > - the secretary workbench maintains a YAML file with details on which > > > emails have been processed. Prior to actual changeover, the files will > > need > > > to be synchronised. > > > > > > - emails are stored for some other lists. Whilst these are not derived > > from > > > SVN or Git, they can safely be captured in parallel, and can be imported > > > from mail archives if necessary > > > > > > - is there any other unique data? > > > > > > To avoid accidental use of the wrong host. I wonder if it would make > > sense > > > to use a non-standard port, especially in the early testing stages? > > > > The way I have done migration in the past is to get whimsy-vm(n+1) up > > and running; > > > Yes, but during this time there is a risk some people could use it by > mistake. Please explain? You are suggesting that people may mistakenly type https://whimsy-vm5.apache.org/ into their browser window? How would a port number change that? > Hence the suggestion to use a different port during the early stages at > least. > > > > change the dns for whimsy.apache.org to point to it, and > > then leave whimsy-vm(n) as a hot backup. > > > > > It cannot be a strict hot backup unless it has all the latest data. > At present there is some data that is only on the local system. True, the switch would involve both changing the dns and copying over selected data. > > Sebb. > > > > - Sam Ruby - Sam Ruby
