Uploaded image for project: 'LAVA'
  1. LAVA
  2. LAVA-1235

Use zmq for lava-coordinator messages

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Closed
    • Priority: Undecided
    • Resolution: Deferred
    • Fix Version/s: LAVA Community Project
    • Labels:
      None

      Description

      Some of these may be best done as sub-tasks or split into different issues.

      1. Replace the manual socket handling in LavaCoordinator with ZMQ message handling
      2. Use methods from lava-master to keep state in a SQLITE database so that the coordinator can be restarted clearnly
      3. Move lava-coordinator configuration into lava-server configuration as /etc/lava-server/settings.conf and /etc/lava-server/lava-coordinator
      4. Have only one and always one lava-coordinator per lava-master, enabled by default
      5. Instruct each worker to use the associated lava-coordinator for the master controlling that worker (LAVA-196)
      6. Update documentation
      7. move lava-coordinator to a systemd service and drop use of python-daemon
      8. migrate the current status check to lava-server manage check --deploy
      9. Presence or absence of /etc/lava-coordinator/lava-coordinator.conf on a worker is to be ignored.
      10. Update Debian packaging as lava-coordinator will no longer exist as a separate binary package.
      11. remove lava-coordinator source package from Debian Buster.

        Attachments

          Issue Links

            Structure

              Activity

                People

                • Assignee:
                  remi.duraffort@linaro.org Remi Duraffort
                  Reporter:
                  remi.duraffort@linaro.org Remi Duraffort
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel