Skip to main content

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.


Metadata

Release files for mlsysops 0.0.0.post16078422306

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for mlsysops 0.0.0.post16078422306
File Size Uploaded Provenance Actions
mlsysops-0.0.0.post16078422306.tar.gz 53.7 kB Without provenance Details for mlsysops-0.0.0.post16078422306.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for mlsysops 0.0.0.post16078422306
File Interpreter ABI Platform Actions
mlsysops-0.0.0.post16078422306-py3-none-any.whl Python 3 none any Details for mlsysops-0.0.0.post16078422306-py3-none-any.whl

Total release size: 137.8 kB

Release files / mlsysops-0.0.0.post16078422306.tar.gz

Download URL mlsysops-0.0.0.post16078422306.tar.gz
Size 53.7 kB
Tags Source
SHA-256 checksum
How to use checksums
82985027a9e143e5e2c4deafef1751ea1377b178d4b3b712588867eeff8b1745
BLAKE2b-256 checksum
How to use checksums
568f6e7163a06197648a69b0aba6c161cd130eede1718b6fc756096c3a35aa8f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.1.0 CPython/3.12.9

Release files / mlsysops-0.0.0.post16078422306-py3-none-any.whl

Download URL mlsysops-0.0.0.post16078422306-py3-none-any.whl
Size 84.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
cce73c0aff55320f04f7929bf98ea09e7578fc7098af93097800434a3eff6cad
BLAKE2b-256 checksum
How to use checksums
f6930e24574de320b0e3412e3e5daf1d7146bea148a81164d46a58c7dce2b240
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.1.0 CPython/3.12.9

Security for mlsysops 0.0.0.post16078422306

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page