| 2024-05-21 15:38:04 |
Francisco Álvarez Terribas |
description |
Objective
Validate that a resource manager can onboard manually-managed nodes in NebulOuS
Preconditions
A NebulOuS core installation is up and running. It’s IP is known.
Two users exist:
Device owner: A user with “device owner” role in NebulOuS.
Resource manager: A user with “resource manager” role in NebulOuS.
A machine with minimum requirements for NebulOuS agent is available. NebulOuS has network visibility over it. A pair of SSH keys of the machine linked with a user account with appropriate rights to install new software are known by the user “device owner”.
Steps
Step 1
Action
User “device owner” logs in to NebulOuS and fills in a device registration request as described in XXX. It provides a device Id, the public IP and the SSH keys.
Expected results
A device registration request is created.
NebulOuS automatically collects the device capabilities.
Step 2
Action
User “resource manager” logs in to NebulOuS and performs the “ask device-onboarding” step of the resource discovery mechanism for the recently created registration request.
Expected results
NebulOuS installs the NebulOuS agent in the device and the device registration process is completed successfully.
Users Device owner and resource manager are informed about the status of the process.
The device is made available to NebulOuS for deploying payloads. |
Objective
Validate that a resource manager can onboard manually-managed nodes in NebulOuS
Preconditions
A NebulOuS core installation is up and running. It’s IP is known.
Two users exist:
Device owner: A user with “device owner” role in NebulOuS.
Resource manager: A user with “resource manager” role in NebulOuS.
A machine with minimum requirements for NebulOuS agent is available. NebulOuS has network visibility over it. A pair of SSH keys of the machine linked with a user account with appropriate rights to install new software are known by the user “device owner”.
Steps
Step 1
Action
User “device owner” logs in to NebulOuS and fills in a device registration request as described in XXX. It provides a device Id, the public IP and the SSH keys.
Expected results
A device registration request is created.
NebulOuS automatically collects the device capabilities.
Step 2
Action
User “resource manager” logs in to NebulOuS and performs the “ask device-onboarding” step of the resource discovery mechanism for the recently created registration request.
Expected results
NebulOuS installs the NebulOuS agent in the device and the device registration process is completed successfully.
Users Device owner and resource manager are informed about the status of the process.
The device is made available to NebulOuS for deploying payloads.
Result
Doesn't pass https://bugs.launchpad.net/nebulous/+bug/2065319 |
|
