Comments (4)
Collector b.collector.ooni.io
and web-connectivity test helper b.web-connectivity.th.ooni.io
on port 443 have been deployed.
Canonical's bouncer configuration should change accordingly and an announcement to the mailing list should follow.
from sysadmin.
In order for the deployment to take place we 'll be needing a bouncer base file pointing to all collectors, and test helpers instances, such as the example below:
collector:
httpo://s2zznrn5jxfgkaom.onion:
collector-alternate:
- { address: 'https://a.collector.stage.ooni.io:4441', type: 'https'}
- { address: 'http://a.collector.stage.ooni.io:8081', type: 'http'}
- { address: 'https://{{ collector_domain }}:{{ tls_collector_port }}', type: 'https'}
- { address: 'http://{{ collector_domain }}:{{ tcp_collector_port }}', type: 'http'}
test-helper:
{dns: '213.138.109.232:57004',
http-return-json-headers: 'http://93.95.227.200',
tcp-echo: '213.138.109.232',
web-connectivity: 'ebckmavdjlxhnw27.onion',
traceroute: '213.138.109.232'}
test-helper-alternate:
web-connectivity:
- {address: 'ebckmavdjlxhnw27.onion', type: 'onion'}
- {address: 'https://a.web-connectivity.th.stage.ooni.io:4442', type: 'https'}
- {address: 'http://a.web-connectivity.th.stage.ooni.io:8082', type: 'http'}
- {address: 'https://{{ web_connectivity_domain }}:{{ tls_web_connectivity_port }}', type: 'https'}
- {address: 'http://{{ web_connectivity_domain }}:{{ tcp_web_connectivity_port }}', type: 'http'}
from sysadmin.
I see that you are specifying in here also staging collectors and test helpers. We should exclude these from the production collector and just include the ones that are production.
I would imagine the bouncer file for the production deployment would become something like this:
current bouncer.yaml
collector:
httpo://ihiderha53f36lsd.onion:
collector-alternate:
- {address: 'https://a.collector.ooni.io:4441', type: https}
- {address: 'https://das0y2z2ribx3.cloudfront.net', front: a0.awsstatic.com, type: cloudfront}
test-helper: {dns: '213.138.109.232:57004', http-return-json-headers: 'http://38.107.216.10:80',
ssl: 'https://213.138.109.232', tcp-echo: 213.138.109.232, traceroute: 213.138.109.232,
web-connectivity: 'httpo://7jne2rpg5lsaqs6b.onion'}
test-helper-alternate:
web-connectivity:
- {address: 'https://a.web-connectivity.th.ooni.io:4442', type: https}
- {address: 'https://d2vt18apel48hw.cloudfront.net', front: a0.awsstatic.com,
type: cloudfront}
new bouncer.yaml
collector:
httpo://ihiderha53f36lsd.onion:
collector-alternate:
- {address: 'https://a.collector.ooni.io', type: https} # <-- Changed this line to be port 443
- {address: 'https://das0y2z2ribx3.cloudfront.net', front: a0.awsstatic.com, type: cloudfront}
test-helper: {dns: '213.138.109.232:57004', http-return-json-headers: 'http://38.107.216.10:80',
ssl: 'https://213.138.109.232', tcp-echo: 213.138.109.232, traceroute: 213.138.109.232,
web-connectivity: 'httpo://7jne2rpg5lsaqs6b.onion'}
test-helper-alternate:
web-connectivity:
- {address: 'https://a.web-connectivity.th.ooni.io', type: https} # <-- Changed this line to be port 443
- {address: 'https://d2vt18apel48hw.cloudfront.net', front: a0.awsstatic.com,
type: cloudfront}
The only two changed that should happen are those related to the https collector and https web connectivity test helpers. It may actually be wiser, though, so that we don't have to worry about synchronising with DNS propagation time, to setup b.collector.ooni.io
as a new record and update the new bouncer to use that.
Do you need anymore information to proceed?
from sysadmin.
This is implemented.
from sysadmin.
Related Issues (20)
- Upgrade TLS used by web-connectivity test-helper HOT 1
- Test master issue
- Child issue
- Bouncer giving out down test-helpers for ~16 hours HOT 5
- Migrate collectors to the oonified host HOT 1
- Make the cans public and move the to the open data account
- Implement a deb based deployment process HOT 2
- Monitoring: fix frequent alerts around .onion services being unreachable
- Prometheus / Grafana: store data for longer times HOT 10
- Incident: very slow rsync between ams-ps1 and datacollector HOT 4
- Incident: blocked pipeline on 2019-12-10 HOT 1
- y3zq5fwelrzkkv3s.onion ams-wcth2 unreachable HOT 2
- Drop brie.darkk.net.ru from monitoring HOT 2
- [FIRING] Lots of `scrape_samples_scraped` lost Now ~ 2.83k, 24h ago ~ 27.96k. HOT 1
- psql: FATAL: database "metadb" does not exist HOT 4
- MetaDB - Time to replication
- Metadb Replica Access - postgres user HOT 1
- no:assignee
- Slack bridge is not transmitting messages to IRC channel HOT 2
- RSS by country feed is not available
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from sysadmin.