Project user guide¶
1. Accept the invitation¶
- Open the link from the invitation email. Set a password that follows the policy shown under the field, and enter your name, mobile number (international format, starting with "+"), city (typed in) and photo.
- Set up two-factor authentication: the portal asks for it right after you accept, before anything else. Use any authenticator app (TOTP). It is required for every user and can't be turned off.
- Optionally, add a passkey on your profile page: Touch ID, Face ID, Windows Hello, a phone or a security key. After the password, the second step of the sign-in then takes either the authenticator app's code or the passkey. Keep the authenticator app: it is the way back when a device with the passkey is lost. A passkey works only on the portal's own address. Failed attempts count together with wrong codes: after five, the sign-in starts again.
An invitation that was revoked, or whose account was blocked or archived, cannot be accepted any more - even from a page opened before; an invitation is accepted once.
2. What you see¶
| Project admin | The projects you were given: resources, storage split, networks, gateway keys, the OpenNebula admin password and the log. You can invite project users. |
| Project user | The projects you were given, without changes. |
| Read only | Every project of the organization, without changes. |
The OpenNebula link in the menu opens the console.
3. Work in the console¶
- Sign in to the OpenNebula console as the project's admin (
<org>-<project>-adm). A project admin can show its password on the project page. - Create VMs from templates, images or marketplace appliances. Choose the project's cluster.
- Attach VMs to the main public network for public addresses, or to private networks you create. Private networks reach the internet through the project gateway.
- Use OneFlow to run applications of several VMs with roles and scaling. Its address and the XML-RPC API's are on
the project's credentials e-mail (e.g.
https://one-dc1.example.com/oneflow,.../RPC2); both are reachable from any address and ask for your OpenNebula login. For OneGate, a VM needsTOKEN="YES"in its context. When the platform reaches OneGate through hosts, the VM needs a route169.254.16.9 dev <its NIC> scope linkand reaches it athttp://169.254.16.9:5030through its own host, on private networks too; otherwise it reaches the front end's VIP,http://<VIP>:5030, on the internal network. Allow TCP 5030 out if its security groups limit outbound traffic. - Watch your quotas in the console. If you need more, a project admin requests it in the portal.
4. The project gateway¶
- Connect over ssh with your key to the gateway's address. The address and admin name are on the project page.
- Add your private networks to the gateway so they get address translation. Route extra public networks through it.
- Ask a project admin to add your ssh key on the project page.
5. Help¶
Service status, announcements and news are on the front page. For anything else, contact your organization admin or the provider's support.