Uploaded image for project: 'Operator Ecosystem'
  1. Operator Ecosystem
  2. OPECO-1972

POC2 for exposing custom metrics via Ansible (using an HTTP server)

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • Ansible-Operator
    • OSDK Sprint 65

      The current POC (from OSDK-1924) abuses the ansible event logging system to communicate to the binary. There are several issues with this method, chief among them that there is no way to communicate back to the module whether the operation succeeded or failed. The second POC will do exactly what the first POC did, create a single counter metric from Ansible, but rather than using the eventing system, will create a new api endpoint served by the binary that allows creating/setting the prometheus metrics. The ansible module will be updated to use this endpoint.

       

      Acceptance Criteria:

      • api for creating/updating metrics that supports at least counters
      • Ansible module that supports at least counters, and uses this API to set them
      • Sample operator that uses this module to create and update a prometheus counter object

       
      POC1 ansible module: https://github.com/fabianvf/operator-sdk-ansible-util/tree/ansible-add-metrics

      POC1 ansible-operator integration: https://github.com/fabianvf/operator-sdk/tree/ansible-add-metrics

              fvonfeil@redhat.com Fabian von Feilitzsch (Inactive)
              fvonfeil@redhat.com Fabian von Feilitzsch (Inactive)
              Jia Fan Jia Fan
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: