[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-relays] automation needs of big relay ops (implemented as ansible role)



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Moritz Bartl:
> On 02/17/2015 06:29 PM, Nusenu wrote:
>>> Arzhel and Moritz, could you comment on whether you prefer to
>>> manually create/specify tor instances (via 'proc_instances') as
>>> you do here [1], or whether you would make use of an instance
>>> auto configuration (two instances per IP - see example here
>>> [2])?
> Automate away please!! :-)

I somehow expected it - great (this is basically done ;)

> In my ideal world, someone would write a "wizard" as wrapper around
> the ansible stuff (or whatever really), so people who run it can
> either specify attributes in a clear CLI language that feels "more
> native" to the domain, or answer questions asked by the wizard. The
> knowledge spectrum is "Moritz wants to use this", and "Uh. I have
> zero knowledge of computers, but I want to run a Tor relay. I have
> this cheap $5 VPS, please turn it into something useful. I don't
> know if it should be a bridge, or a relay. I don't even really want
> to know.".

Understood.

> In practice and for simplicity, I wouldn't mind if you completely
> ignore the "make processes handle as much traffic as possible". The
> default should be "as automated as possible, even if suboptimal".

Agreed :)
I'm wondering if simply (blindly) running two tor processes per
available IP is any worse than anything else from a pure "lets push as
much traffic as we can" (on a host not on a tor process level).

> As long as you expose the "expert options for tuning", that's
> totally fine with me. :-)

> Does this help?

Thanks for your answer.
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJU47/UAAoJEFv7XvVCELh0jVkP+QHDYwica6a2GLKhgkuapqOc
NmxMMD5vRmoyx51FyUbtVUaQ8sYHeNQHe+axVIgGMWepsH5puIfQT4aH1g18VXle
h7DuU+/QYaAij+lHxrGU7UJhaEXZAi6OJ0NxNd67ivf+TBCJKYkybFBUgwBeHgVW
0RYhK24xT9yzeTEOd1C6ppJaIXAI/WzJdpnoQZADYiMfra34rzo8QD9xO/EW+QXw
LT8vIegT3NIdc6cDFHnB0+sWiHEn26N8PrHiRnq2FsvbclJqg0fePnlj900ZynF1
YBxXSGQuzJ5Z8K/q+5jj8Q8DikXm45QH55kdqQStD7id9Es2j7ygGb1ywKSW6FjU
edrgQUskJuFv0YwuY/pwxyJLuB7dpm4OT4cZNQrEzo3aFM0lPWthfXkQsvrZXItP
RCorU6Y3Dwczqn21EEWE1w+m2oit5+Wdm7n3qE/sYI78LB5780UKrvR16n7ujGii
QsX8dTei+F6wgvgIsdPfIxycnRL6uKsoUCDTHMGhiSJW8v6ZbxKDVlw5uf+Ex7KQ
FX6Ux6q8dgHFZQGGk1q0ImvvrIU5KCUfRWlIOdZgdSlieyhSkur5sTeFDuXxnF9N
2t+Jo4iJPulZ1vd7WOPlO6N2zyQCG4oOO3FxCp8D0iQV4h1tPo/nZBVCDGcCobxR
r+VSy8W3vy5+01fBfFuT
=PEcd
-----END PGP SIGNATURE-----
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays