...
| parameter | value or where to take it |
|---|---|
| username | from EO portal |
| userkey | provided by the helpdesk in the pilot phase. (opening 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 rules and hit save
| 2268-udp | ingress | Custom Rule | UDP | 2268 | Network | 0.0.0.0/0 | Instance |
| 22-ssh-tcp | ingress | Custom Rule | TCP | 22 | Network | 10.0.0.0/24 | Instance |
| 8500-tcp | ingress | Custom Rule | TCP | 8500 | 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
...
6. Select the following security group:
- ssheumetcast-internalssh
| Warning |
|---|
The ssh-internal is added for security reasons after public IP was required for the eumetcast machine.The login to this machine is allowed only from the internal network (10.0.0.0/24) even if there is a public IP! This is for security reasons after public IP was required for the eumetcast machine. (See point 7 below) In other words, if you want to login to the machine you need to first login to a machine in the EWC (for example a proxy or one machine with the security group that allow ssh 22 from external network) and then login using the internal IP of the eumetcast machine, not the public IP, because it won't work otherwise. You can find the internal IP of the machine going to Morpheus → eumetcast instance/VM → select Tab Network for the machine and look at Interfaces, as shown below:
|
...