Forum Discussion

DanBuck's avatar
DanBuck
Icon for Contributor rankContributor
6 months ago

Elevated Privileges for Python3 Libraries

We are stuck trying to recreate some of the metrics we collect in our current Python2 snippets using pipes. The specific example is 'ping', which required subprocesses, no longer allowed. We don't b...
Python3
  • MattH's avatar
    MattH
    5 months ago

    Dan,

    I can address the first question. You should be able to pull in that ping3 wheel/library using these instructions: https://docs.sciencelogic.com/latest/Content/Web_Content_Dev_and_Integration/ScienceLogic_Libraries/chapter_02_managing_libraries.htm?Highlight=science%20logic%20library#manually-building-a-sciencelogic-library

    That library is fairly simple to pull in because it doesn't require to be compiled and it has no other dependent libraries or wheels. The instructions should boil down:

    • Saving that wheel from pypi
    • Creating a metadata.json file describing the library and the wheels is contained in the SL library (see below)
    • Creating a tar file that contains the wheel(s) and the metadata.json file.

    Your metadata.json should look like this...

    {
    "meta_version": "0.2",
    "fields": {
        "description": "Ping3 Library",
        "manifest": [
            "ping3-4.0.8-py3-none-any.whl"
        ],
        "name": "ping3",
        "type": "py_package",
        "version": "4.0.8",
        "requires_python": ">=3.5"
    }
}

    From there you should be able to import and align the SL library into your SL1.

    Your tar file listing should look like this...

    [workspace]# tar tvf ping3+4.0.8.py36.tar
-rw-r--r-- root/root       287 2024-06-20 13:35 metadata.json
-rw-r--r-- root/root     14007 2024-06-20 13:33 ping3-4.0.8-py3-none-any.whl

    Some gotchas is that you need to prepare the SL library on an OracleLinux or RedHat variant.

    Hope that helps and let me know how it goes!

     

MattH's avatar
MattH
Icon for Moderator rankModerator
5 months ago

Dan,

I can address the first question. You should be able to pull in that ping3 wheel/library using these instructions: https://docs.sciencelogic.com/latest/Content/Web_Content_Dev_and_Integration/ScienceLogic_Libraries/chapter_02_managing_libraries.htm?Highlight=science%20logic%20library#manually-building-a-sciencelogic-library

That library is fairly simple to pull in because it doesn't require to be compiled and it has no other dependent libraries or wheels. The instructions should boil down:

  • Saving that wheel from pypi
  • Creating a metadata.json file describing the library and the wheels is contained in the SL library (see below)
  • Creating a tar file that contains the wheel(s) and the metadata.json file.

Your metadata.json should look like this...

{
    "meta_version": "0.2",
    "fields": {
        "description": "Ping3 Library",
        "manifest": [
            "ping3-4.0.8-py3-none-any.whl"
        ],
        "name": "ping3",
        "type": "py_package",
        "version": "4.0.8",
        "requires_python": ">=3.5"
    }
}

From there you should be able to import and align the SL library into your SL1.

Your tar file listing should look like this...

[workspace]# tar tvf ping3+4.0.8.py36.tar
-rw-r--r-- root/root       287 2024-06-20 13:35 metadata.json
-rw-r--r-- root/root     14007 2024-06-20 13:33 ping3-4.0.8-py3-none-any.whl

Some gotchas is that you need to prepare the SL library on an OracleLinux or RedHat variant.

Hope that helps and let me know how it goes!

 

  • DanBuck's avatar
    DanBuck
    Icon for Contributor rankContributor
    5 months ago

    That does help, we will give that a shot. TY!

    • Ishanc's avatar
      Ishanc
      Icon for Contributor II rankContributor II
      5 months ago

      I tried, it's the same permission problem. Needs elevated permission to create sockets since ping3 uses that.

      Error encountered while executing snippet. Error explanation: App: 2025, Snippet: 2384 threw exception: [Errno 13] Permission denied (PermissionError: [Errno 13] Permission denied _socket.socket.__init__(self, family, type, proto, fileno))

       
      • MattH's avatar
        MattH
        Icon for Moderator rankModerator
        5 months ago

        If you have access to the collector and can create a user that has the elevated privileges to run ping3 in your newly created EE I think I would take that route.  

        I created a user, em7ping3, and added this new user to my /etc/sudeors file on my collector like this

        em7ping3 ALL=(ALL) NOPASSWD: /opt/em7/envs/eeguid_with_ping3_installed/bin/ping3

        Then I created a Dynamic Application (snippet config) using the SSH requester in Low-code Tools v101 and the resultant snippet argument looked like this

        low_code:
  version: 2
  steps:
    - ssh: 'sudo /opt/em7/envs/eeguid_with_ping3_installed/bin/ping3 8.8.8.8'

        Then I aligned an SSH credential with em7ping3 to my collector and ran the collection. Again, this assumes that the EE with ping3 has been deployed on the collector with the newly created em7ping user.