Opened 3 years ago

Closed 3 years ago

#21652 closed defect (fixed)

Finishing touches for onionperf setup on papillare.

Reported by: hiro Owned by: tpa
Priority: Medium Milestone:
Component: Internal Services/Tor Sysadmin Team Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Hi,

To finish onionperf setup on papillare I would need to complete the following:

  1. Be able to access the twisted service on port 80 (it runs on 8081). The twisted service starts when onionperf is run. To start onionperf the run_onionperf script under /srv/onionperf.torproject.org/bin is used. What it does is activate the virtualenv and run the service.
  1. It would be ideal if we could have this under the subdomain onionperf.torproject.org. Is that possible?
  1. To finish the setup I'd like to setup letsencrypt for the host. What's the usual procedure in this case?

Please let me know if any of the tasks isn't clear of if I can assist you with anything.

Child Tickets

Change History (4)

comment:1 Changed 3 years ago by weasel

I'm trying to understand this service a bit btter.

Is this twisted thing a website or is it part of some dynamic service stuff that isn't really meant for people to consume? If it's meant for people, does it need to be dynamic or can it also just dump a bunch of static files regularly? (Then we wouldn't need a webserver on papillare and could avoid having another SPOF for serving files to users.)

If it needs to be dynamic, do you really need port 80 in twisted, or do you just need whatever gets requested on https to be forwarded to localhost:8081 in the clear?

[virtualenv: making sure you keep running insecure software even when your OS updates.]

Last edited 3 years ago by weasel (previous) (diff)

comment:2 Changed 3 years ago by hiro

Hi,

so a little bit of background.

Twisted serves the directory of files and it is started by onionperf in measurement mode. If it is possible I'd like to keep the setup as in the other machines and have the server running. We can redirect to port 8081 all the request, it doesn't need to run on port 80. Sorry for the confusion. In fact, I would redirect everything over https (80 included).

We can get rid of virtualenv it is not strictly needed. I used to pull a few (very few) updated packages, but we can use the deb version.

Here are the packages that I would need installed to get rid of virtualenv:

python-stem python-twisted python-lxml python-networkx python-matplotlib python-numpy python-scipy

I hope this clarifies everything.

Let me know if is there anything else I should add.

comment:3 in reply to:  2 Changed 3 years ago by weasel

Replying to hiro:

Twisted serves the directory of files and it is started by onionperf in
measurement mode. If it is possible I'd like to keep the setup as in the other
machines and have the server running.

If it's really just serving static files, I'd prefer we don't expose twisted to
the network. How much data is in those static files and how often do they change?

Here are the packages that I would need installed to get rid of virtualenv:
python-stem python-twisted python-lxml python-networkx python-matplotlib python-numpy python-scipy

Installed.

comment:4 Changed 3 years ago by weasel

Resolution: fixed
Status: newclosed

ok, thanks for explaining things on IRC.

After the nightly job has created all the files on papillare, please run static-update-component onionperf.torproject.org - that will update the user visible content on https://onionperf.torproject.org/

Cheers,

Note: See TracTickets for help on using tickets.