Page MenuHomePureOS Tracker

Create master.pureos.net
Closed, ResolvedPublic

Description

We need a server master.pureos.net which serves information about the status of the NEW queue and various QA data about the archive, including log files.
It will likely run the to-be-written Laniakea web frontend at some point in time.

The data is on the dak server at time, to publish it we can run a web server on that machine, or, to improve security, have another server which the data gets uploaded to from dak (that way we can keep the dak machine as isolated as possible).

This task is quite high priority, as not having the site makes developing PureOS much harder (at time, people have to ask me to look up diagnostic information).

Event Timeline

mak created this task.Nov 23 2016, 12:04

@mak. I will create an LXC container for this. Any idea on specs (CPU, RAM, Storage)?

mak added a comment.Dec 4 2016, 15:22

For now, I will have it serve just static data - when I go forward with the QA web app, it will likely be based on Vibe.d or Flask, and at least the former is pretty low on CPU (it uses almost zero system resources if not in use, but can grow quite RAM-heavy if you cache stuff there).

So, for now I think we don't need much resources, and since it's LXC, we can upscale it as soon as we do :-)

@mak @todd @zlatan.todoric

I am trying to switch the nameserver and glue records of pureos.net to ns1 and ns2.puri.sm. It's not very clear how to do that. I opened a ticket. Todd can you please forward to me any reply from their support?

In case this is not possible (just a hunch for now) we may have to move the domain to a more friendly registrar.

@mak 1 CPU, 4096MB RAM, 16GB storage. Let me know if we need more.

Access it with (for now):

ssh -p 3376 root@138.201.228.38

@mak It seems I was overreacting about Dreamhost :)

You can try this as well:

ssh -p 3376 root@master.pureos.net

My provider hasn't refreshed its DNS cache though. Try a dig master.pureos.net and let me know if there is a problem on your side.

mak added a comment.Dec 14 2016, 17:48

@theodotos.andreou Excellent! I will need to think a bit about how to send data there properly while we do not yet have a database server storing it (will likely be just a data-upload from the dak machine).
I hope I can do that on Sunday, if not then hopefully next week.

mak added a comment.Dec 18 2016, 11:15

@theodotos.andreou Looks like by SSH public key isn't registered with the root account (I can't log in at master.po.n)

@mak proxmox has the nasty habit of messing up all the keys excpet the first one. Can you try now?

mak closed this task as Resolved.Mar 19 2017, 17:29
mak claimed this task.

Everything works now :-)