This service is available as best effort for testing. Be aware when trying this service in your tenancy.
EUMETCast Terrestrial over AMT can serve any user hosted on the EUMETSAT side of the EWC, regardless of native multicast connectivity. The encapsulated data can travel via GEANT network or the commercial internet.
Pre-requisite
During the test phase, credentials have to be added to EUMETSAT allowlist. In order to do that, please contact EWC support before doing the EO Portal registration.
- You need to register to the EO Portal
- Subscribe to data for EUMETCast Terrestrial
- Request credentials in order to provision the service in your tenancy:
| parameter | value or where to take it |
|---|---|
| username | from EO portal |
| userkey | provided by the helpdesk in the pilot phase. You need to open a ticket and request EUMETCast Terrestrial credentials for access from the EWC |
Create security group
Once you enter your tenancy:
- Go to Infrastructure → Network
2. Go to Security Group tab and click the add button:
3. Assign eumetcast-ssh name to the security group and hit save:
In the scoped cloud select your tenancy from the list. If you leave All, the security group cannot be assigned to VMs.
4. Click on the new security group to access it
5. Click on the 'Add rule' button to create a new rule
6. Add the following rule and hit save
| Rule name | Direction | Rule Type | Protocol | Port Range | Source Type | Source | Destination Type |
|---|---|---|---|---|---|---|---|
| 2268-udp | ingress | Custom Rule | UDP | 2268 | Network | 0.0.0.0/0 | Instance |
| 22-ssh-tcp | ingress | Custom Rule | TCP | 22 | Network | 0.0.0.0/0 | Instance |
Now you are ready to provision the client!
Provision the client VM
- Go to Provisioning → Instances and click 'Add' button
2. Go to network category and select 'EUMETCAST TERRESTRIAL ON AMT':
3. Select name for your VM: eumetcast-client
4. Use the following specifications for the provisioning of the client:
CPU | 8 cores |
RAM | 64 GB |
OS | Ubuntu v 18.04 |
Storage | 1.2TB |
EWC Plan | hm.xlarge |
security group | eumetcast-ssh |
Insert your credentials
5. Save and create the VM
Once the service is provisioned, the user will start to receive their subscribed data on their VM (stored by default in /root/data/eumetcast/ but can be changed in the /etc/cast-client-channels_ter-1.ini file).
A crontab is automatically activated in order to prevent the build-up of data on the machine
All data is deleted 5 mins after retrieval by default and this can be changed by the user. (See section below)
How to modify the time to live of the data
sudo crontab -e
You have to setup both crontabs to the same time!
How to have real time logging
The entries to the log file for the tellicast client (/var/log/tellicast-client/recv_ter-1.log) is by default buffered.
In order to get real-time log events:
- ssh into the VM
2. Alter the file /etc/cast-client_ter-1.ini, removing the “>>” in front of the log file path:
log_file=/var/log/tellicast-client/recv_ter-1.log
3. After altering the file, you have to restart the service running the following command:
sudo systemctl restart tellicast-client