Skip to main content

The core python package for MLSysOps Agents Framework.

Project description

MLSysOps Framework

XMPP Service Configuration

This project uses the XMPP (Extensible Messaging and Presence Protocol) service for communication between agents. The XMPP service is powered by an ejabberd container, which we have set up for easy deployment and automatic configuration.

kubectl create configmap ejaberd-config --from-file=ejabberd.yml -n mlsysops-framework

Prerequisites

Before running the XMPP service, ensure you have the following installed on your system:

How It Works

The XMPP service is managed through a Docker container running ejabberd. We've provided an automatic configuration process that simplifies setup on any host machine.

Setup Instructions

To set up and run the XMPP service, follow these steps:

  1. Ensures that you have all the necessary packages installed

    Install the libraries of the requirements.txt file

    pip install -r requirements.txt
    
  2. Set the IP Address of the Host

    • Open the .env file in the root directory.
    • Set the IP_SEL environment variable to the IP address of the host machine where the service will run.

    Example .env file:

    IP_SEL=10.96.82.195

  3. Configure ejabberd

    • After setting the IP address in the .env file, run the configuration script to update the ejabberd.yml file with the IP address provided in the .env file.
    • This script will automatically configure the XMPP service for you.

    Command to run the script:

    python config_script.py
    
  4. Run the XMPP Service

    Once the configuration is complete, you can start the XMPP service using Docker Compose.

    Run the following command to start up the service:

    docker-compose up -d
    

    During the setup process, an admin user will be automatically registered with a default password. If the process completes successfully, the console output should show the following confirmation message:

    User admin@10.96.82.195 successfully registered
    

    This confirms that the admin user has been correctly registered in the XMPP service.

  5. Agent connection test

    This repository contains a simple example to test the connection between an agent and an XMPP service using a DummyAgent. The goal is to ensure that the agent can successfully authenticate and communicate with the XMPP server.

    • Ensure that the host machine running the test script has network connectivity to the XMPP server. You can check this by pinging the server:

    • Configure the agent using the following Python code snippet. Please double check that you are using the admin user and the IP address previously configured.

      dummy = DummyAgent("admin@10.96.82.195", "1234")
      
    • Run the script, If the connection succeeds, you will see the following message printed in the console:

      Hello World! I'm agent admin@10.96.82.195
      
  6. Agent registration

    To register the agents that will be supported by the XMPP service, you can use the user_reg.py script. This script reads usernames and passwords from the users.txt file and registers the users on the XMPP service.

    Once the XMPP service is up and running, simply execute the script to create and register the JIDs (Jabber IDs) that the agents will use for communication.

    The format of the users.txt needs to be as follows:

       agentid1,password1
       agentid2,password2
    

Following the previous steps, an agent can be instantiated to communicate with any other agent in the framework through the XMPP service


Node Agent

In this use case, the node agent is responsible for gathering telemetry data from the application running on the node. This includes monitoring the application's behavior as well as collecting CPU and memory metrics from the node itself. Using this information, the agent performs a machine learning (ML) model inference to predict the application's future behavior. The prediction results are then sent to the cluster agent, which uses this data to make decisions.

The node agent uses OpenTelemetry (OTEL) to collect performance data from both the node and the application. Additionally, the agent uses OTEL to share the inference results with the cluster agent for further processing.

Configuring the Node Agent Install OpenTelemetry: First, install the OTEL library, which is required for telemetry collection and data exchange.

        pip install -r requirements.txt

Set Up OTEL Variables: You need to configure the necessary OTEL environment variables as follows:

        TELEMETRY_ENDPOINT="172.25.27.228:4317" to push
        LOCAL_OTEL_ENDPOINT="http://172.25.27.228:9999/metrics"

Configure Agent Information, providing the following information in the environment configuration:

    NODE_NAME=node                   
    NODE_PASSWORD=1234
    CLUSTER_NAME=cluster                        
    EJABBERD_DOMAIN=10.96.82.195        
                      
  • Node agent name: The name of the agent running on the node.
  • Agent password: The password of the node agent.
  • Cluster agent name: The cluster agent to which the node agent will be subscribed.
  • XMPP domain: The domain of the XMPP service used for communication.
  • Note: is worth to say that the jids need to be previously registered as in the previous steps.

Once the environment is set up, you can run the node agent to start collecting telemetry and performing ML inferences.

N_agent.service file is also provide to run the agent script as a daemon in linux systems.

Project status

Testing phase.


Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

mlsysops-0.0.0.post16076697794.tar.gz (53.7 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

mlsysops-0.0.0.post16076697794-py3-none-any.whl (84.1 kB view details)

Uploaded Python 3

File details

Details for the file mlsysops-0.0.0.post16076697794.tar.gz.

File metadata

File hashes

Hashes for mlsysops-0.0.0.post16076697794.tar.gz
Algorithm Hash digest
SHA256 7c9b16cd79d8dd535cb7572437561604951cb6cc904780b38b37db87dcd8ccfc
MD5 5208eee0aff46758ccf64d2290220806
BLAKE2b-256 e0f283792f547ca96690b1eb8c827ff018dfac68ced4a2b304e22028e5d39f56

See more details on using hashes here.

File details

Details for the file mlsysops-0.0.0.post16076697794-py3-none-any.whl.

File metadata

File hashes

Hashes for mlsysops-0.0.0.post16076697794-py3-none-any.whl
Algorithm Hash digest
SHA256 302d0ae32c1712116d5f65db280fca4b6109f29768f1619218cfc401c413af55
MD5 5e89ecd5ebc0e25a4b215f6a30ffe999
BLAKE2b-256 16cc1a508eae5707d68a22a79b2df01385443e78ef7fe2b364ecb0213efc5696

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page