Skip to content

Latest commit

 

History

History
87 lines (70 loc) · 3.07 KB

drp.md

File metadata and controls

87 lines (70 loc) · 3.07 KB
Raw

CORTX-DRP Integration

Background

What is DRP?
DRP stands for Declarative Resource Protocol. It is an open source service mesh project with data mesh extensions. While originally developed for use with infrastructure sources, it was adapted for use with mock civic data sets using CORTX storage for this project.

Demo Video

A quick video describing this project, what DRP is and how it leverages CORTX storage Demo on YouTube.

Project Repository

The DRP project GitHub Repo.

Demo Steps

Set up CORTX Storage

Prepare your environment and have the Endpoint, AccessIDKey and SecretAccessKey values ready.

Run Docker Container

Run the adhdtech/drp-nodejs container with "node serverCortx.js". Substitute the S3ENDPOINT, S3ACCESSKEYID and S3SECRETACCESSKEY values with your

> docker run --name drpcortx -P 8080 -e REGISTRYURL=ws://localhost:8080 -e PORT=8080 -e S3ENDPOINT=https://192.168.5.148 -e S3ACCESSKEYID=AKIAT7y9JwKbREyMsCX08G3blg -e S3SECRETACCESSKEY=IHQRZ8U/06tboLFyLduRdLfWvkSt9gl1rHQUeATQ adhdtech/drp-nodejs node serverCortx.js

The service should now be listening on port 8080 for you to access with your browser.

Open DRP Desktop

In a browser, go to https://localhost:8080. Enter any username and password to get access.

View Mesh Topology

Once the DRP Desktop is open, click Go -> DRP Topology to view the microservices on the mesh.

Class Data

The sample microservices advertise class definitions to the mesh. Class records are retrieved from CORTX then dynamically related using UML field stereotypes. These records are visible in Go -> Hive Browser. Type "Springfield" in the Search box and hit Enter.

To see a sample class definition via CLI in Go -> DRP Shell...

dsh> ls Mesh/Services/FireDept/Classes
Station         UMLClass        11
Person          UMLClass        11
Equipment       UMLClass        11

dsh> cat Mesh/Services/FireDept/Classes/Station/GetDefinition
{
    "Name": "Station",
    "Stereotypes": [],
    "Attributes": {
        "stationID": {
            "Name": "stationID",
            "Stereotype": "stationID",
            "Visibility": null,
            "Derived": false,
            "Type": "int",
            ...

Or even see the raw records...

dsh> cat Mesh/Services/FireDept/Classes/Station/GetRecords   
{
    "1000": {
        "_objClass": "Station",
        "_objPK": 1000,
        "_serviceName": "FireDept",
        "_snapTime": "2021-04-27T08:00:00.000Z",
        "stationID": 1000,
        "description": "East side of town",
        "city": "Springfield",
        "address": "123 Pine St"
    },
    "2000": {
        "_objClass": "Station",
        ...

Streaming Data

Streaming data emitted from services can be watched via CLI in Go -> DRP Shell.

dsh> watch firedept
Subscribed to stream firedept

[firedept] {"TimeStamp":"20210428065806","Message":"a random fire event","Route":["adb571bf7456-1"]}
[firedept] {"TimeStamp":"20210428065811","Message":"a random fire event","Route":["adb571bf7456-1"]}

Author

  • Pete Brown