Opened 7 years ago

Closed 7 years ago

#5204 closed task (implemented)

Set up VM running Apache for Atlas/TorStatus

Reported by: karsten Owned by: phobos
Priority: Medium Milestone:
Component: Company Version:
Severity: Keywords:
Cc: atagar, hellais, weasel Actual Points:
Parent ID: #5189 Points:
Reviewer: Sponsor:

Description

Damian, Arturo, and I would like to have a new Tor VM for Atlas/TorStatus.

At first this VM should just run Apache and serve static content, so 1 GB of free disk space and 256 MB RAM should be fine.

(In a month or two it should run a Python cronjob and JSON-serving Python thing that we still need to write. We will want to have some more disk space and maybe RAM by then.)

We'd also want atlas.torproject.org to point to that VM.

atagar, hellais, and I would want access to the VM. It should have a torstatus user that we can all sudo into and that runs stuff.

Andrew, can we have such a VM? Can you or weasel create it?

Child Tickets

Change History (6)

comment:1 Changed 7 years ago by phobos

After thinking about this, here are my thoughts:

  1. if the site is static, we can serve it off the current static-content webservers.
  1. the python bits can run on the current wgsi-serving webservers.

do you still need a vm?

if everything is pushed to appropriate git repos, weasel or I can just git pull and update the services.

comment:2 in reply to:  1 Changed 7 years ago by phobos

Replying to phobos:

if everything is pushed to appropriate git repos, weasel or I can just git pull and update the services.

weasel rejects this sentence and substitutes, 'a shared account can be created and own the service directories needed'

comment:3 Changed 7 years ago by weasel

Cc: weasel added

comment:4 in reply to:  1 ; Changed 7 years ago by karsten

Replying to phobos:

After thinking about this, here are my thoughts:

  1. if the site is static, we can serve it off the current static-content webservers.

Yes, I think that would work. Three questions remain:

  1. We wouldn't hurt same origin policy if the static HTML lives on atlas.tpo and the data comes from somewhereelse.tpo, right?
  1. Would hellais be able to update the static content? (I wouldn't need/want access to the static pages, nor would atagar.)
  1. Would the static pages be available as http://atlas.tpo/index.html ?
  1. the python bits can run on the current wgsi-serving webservers.

Not sure about that. There will be two Python bits: 1) a Python cronjob that requires a few gigs of disk space and a database and 2) a JSON-serving Python thing that can get plugged into Apache. I'd guess 1 shouldn't live on the current WGSI-serving webservers. 1 and 2 should live on the same host.

do you still need a vm?

We don't need a VM for the Python parts now, but maybe in a month or two from now. I can open a new ticket then.

if everything is pushed to appropriate git repos, weasel or I can just git pull and update the services.

I can maintain this service, possibly together with atagar.

comment:5 in reply to:  4 ; Changed 7 years ago by weasel

Replying to karsten:

Replying to phobos:

After thinking about this, here are my thoughts:

  1. if the site is static, we can serve it off the current static-content webservers.

Yes, I think that would work.

Great. Set up an atlas dir on vescum.

Three questions remain:

  1. We wouldn't hurt same origin policy if the static HTML lives on atlas.tpo and the data comes from somewhereelse.tpo, right?

We can move it to a different host if you have progressed further.

  1. Would hellais be able to update the static content? (I wouldn't need/want access to the static pages, nor would atagar.)

weasel@vescum:~$ getent group atlas
atlas:x:1535:art,atagar,karsten

  1. Would the static pages be available as http://atlas.tpo/index.html ?

yes.

  1. the python bits can run on the current wgsi-serving webservers.

Not sure about that. There will be two Python bits: 1) a Python cronjob that requires a few gigs of disk space and a database and 2) a JSON-serving Python thing that can get plugged into Apache. I'd guess 1 shouldn't live on the current WGSI-serving webservers. 1 and 2 should live on the same host.

What kind of database? sqlite or postgres?

We don't need a VM for the Python parts now, but maybe in a month or two from now. I can open a new ticket then.

Do that.

I can maintain this service, possibly together with atagar.

Good.

comment:6 in reply to:  5 Changed 7 years ago by karsten

Resolution: implemented
Status: newclosed

Replying to weasel:

Great. Set up an atlas dir on vescum.

Thanks!

  1. We wouldn't hurt same origin policy if the static HTML lives on atlas.tpo and the data comes from somewhereelse.tpo, right?

We can move it to a different host if you have progressed further.

Okay.

  1. Would hellais be able to update the static content? (I wouldn't need/want access to the static pages, nor would atagar.)

weasel@vescum:~$ getent group atlas
atlas:x:1535:art,atagar,karsten

Works.

  1. Would the static pages be available as http://atlas.tpo/index.html ?

yes.

Looks good!

  1. the python bits can run on the current wgsi-serving webservers.

Not sure about that. There will be two Python bits: 1) a Python cronjob that requires a few gigs of disk space and a database and 2) a JSON-serving Python thing that can get plugged into Apache. I'd guess 1 shouldn't live on the current WGSI-serving webservers. 1 and 2 should live on the same host.

What kind of database? sqlite or postgres?

Most likely Postgres, maybe MySQL, probably not SQLite.

We don't need a VM for the Python parts now, but maybe in a month or two from now. I can open a new ticket then.

Do that.

Okay. Closing this ticket.

I can maintain this service, possibly together with atagar.

Good.

:)

Thanks!

Note: See TracTickets for help on using tickets.