On Tue, Aug 09, 2016 at 11:26:08AM +0200, Per Jessen wrote:
Theo Chatzimichos wrote:
lists[45].o.o, baloo.o.o and lists.o.o are the same machine.
Okay. Is baloo.o.o also an internal name, it doesn't resolve?
There is no master/slave setup, although (since the migration last year) we have the data in a separate data disk (and the configs in git) it would make sense to set up a secondary machine.
What is the significance of the different addresses then?
We have a naming pattern for the machines, see [1]. The reason is that we keep this name as primary, and the service name as a CNAME. So in service migrations the change would be changing the CNAME only. This was my personal experience from another linux distro admin team I was participating, see [2]. lists.o.o is a great example of this, the lists?.o.o names that you see are coming from machine migrations :) The name baloo (and the rest of the disney names) do not resolve publicly, they resolve only in the network between the virtualization cluster VMs.
gitlab.suse.de is internal suse service, you don't need access there.
It was mentioned in the wiki, that's why I brought it up -
Sorry you are right. This git repo is one of the many cases that we have right now that have mixed suse and opensuse information inside, and we can't just open. So unfortunately for now you will have to ping one of us SUSE OPS-Services people to do that part. I am planning a meeting with my team to discuss about such shared services, git repos, info etc that we need to decide if/how we are going to make them public. PS: I know that most of the information I am presenting above needs to be written on the progress wiki, and I am working on it, but I would appreciate if there are volunteers that can start pages with quick and dirty info there. We can always clean up later. [1] https://progress.opensuse.org/projects/opensuse-admin/wiki/Naming_pattern [2] https://wiki.gentoo.org/wiki/Project:Infrastructure/Servers Theo