Skip to content

Latest commit

 

History

History
98 lines (60 loc) · 4.2 KB

README.md

File metadata and controls

98 lines (60 loc) · 4.2 KB

Remote Provisioning Server

CodeQL API Tests Build Codecov OSSF-Scorecard Score Discord Docker Pulls

Disclaimer: Production viable releases are tagged and listed under 'Releases'. All other check-ins should be considered 'in-development' and should not be used in production

The Remote Provisioning Server (RPS) enables the configuration and activation of Intel® AMT devices based on a defined profile. RPS utilizes the Remote Provision Client (RPC) deployed onto edge devices to connect the devices to the Management Presence Server (MPS) and enable remote manageability features.



For detailed documentation about Getting Started or other features of the Open AMT Cloud Toolkit, see the docs.


Prerequisites

To successfully deploy RPS, the following software must be installed on your development system:

Deploy the Remote Provisioning Server (RPS) Microservice

To deploy the RPS on a local development system:

  1. Clone the repo and switch to the rps directory.

    git clone https://github.com/open-amt-cloud-toolkit/rps.git && cd rps
    
  2. Install the dependencies from the working rps directory.

    npm install
  3. Start the service.

    npm start
  4. The RPS listens on port 8081 by default. Successful installation produces the command line message:

    RPS Microservice Rest APIs listening on https://:8081.
    

For detailed documentation about RPS, see the docs


Deploy with Docker and Run API Tests

We leverage Postman and Docker for executing RESTful API tests. Once you have Postman and Docker installed, you can follow the steps below:

  1. Clone the repo and switch to the rps directory.

    git clone https://github.com/open-amt-cloud-toolkit/rps.git && cd rps
    
  2. Build the docker image.

    docker build -t rps-microservice:v1 .
    
  3. Ensure RPS is running in a docker container.

    docker-compose up -d
    
  4. Import the test collection located at ./src/test/collections/rps.postman_collection.json.

  5. Run the tests using the Collection Runner in postman. If any of the tests fail, file a github issue here: #34


Additional Resources