Hi all,
At some point, it would be good to see fedrtc.org migrate to Fedora
infrastructure and use the fedoraproject.org domain
I'd be happy to submit the full request for resources[1] but I just want
to see if there is any initial comment on it. Here is a list of what is
involved:
- it uses a PostgreSQL database schema[2]
- it requires some DNS entries (SRV and NAPTR), examples[3]
- it needs a TLS cert for fedoraproject.org on the host(s) where it runs
- it has static HTTP content and PHP that is currently hosted with all
but one problem[4] on a RHEL7 httpd. Content is in Github[5], it could
be presented as an RPM if necessary.
- all packages are in EPEL7, except:
cajun-json in EPEL6, in testing for EPEL7
resiprocate in Fedora, builds from SRPM on RHEL7
- the SIP proxy is a single daemon, managed by systemctl. All settings
in a single file, /etc/repro/repro.config
- the TURN server process is also a single daemon, managed by systemctl.
All settings in a single file, /etc/reTurn/reTurnServer.config
Just to clarify the scope of this: it is not a full telephony service
like Asterisk, just a SIP proxy and TURN server. There is no persistent
state information (as there would be for voicemail, email service, etc)
and no customized routing.
Ongoing maintenance requirements:
- TLS certificate renewals
- monitoring the ports
- package updates from time to time
It currently runs on a lab machine, I'd be happy to arrange SSH access
to the Fedora Infrastructure team to see exactly what is involved and
verify that it is manageable.
Regards,
Daniel
1. https://fedoraproject.org/wiki/Request_For_Resources
2.
https://github.com/resiprocate/resiprocate/blob/master/repro/create_postgresql_reprodb.sql
3. http://rtcquickstart.org/guide/multi/dns.html
4. https://bugzilla.redhat.com/show_bug.cgi?id=1222649
5. https://github.com/opentelecoms-org/fedrtc-org
_______________________________________________
infrastructure mailing list
infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/infrastructure
