Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-2492

Deploy some DataPlaneService across all NodeSets

XMLWordPrintable

    • Deploy some DataPlaneService accross all NodeSets
    • False
    • Hide

      None

      Show
      None
    • False
    • OSPRH-811Red Hat OpenStack 18.0 Greenfield Deployment
    • Committed
    • Committed
    • To Do
    • OSPRH-811 - Red Hat OpenStack 18.0 Greenfield Deployment
    • Committed
    • Committed
    • 0% To Do, 0% In Progress, 100% Done
    • Automated
    • EDPM
    • Approved

      Problem:

      There are DataPlaneServices that needs to distribute information across multiple NodeSets. For example: Today the edpm_ssh_known_hosts role can only generate a proper ssh known_hosts file for the EDPM nodes within the given NodeSet. This means If there are multiple NodeSets in a Deployment then an ssh connection between nodes in different NodeSets will not be secure as the host keys will be not known between different NodeSets.

      Limitation:

      The current per NodeSet known_hosts file limits the VM move operations(live-migration, resize, cold-migration). If a single nova cell consists of multiple set of differently configured EDPM compute nodes (e.g. different cpu_shared_ and cpu_dedicated_set) then those sets of computes are deployed as separate NodeSets and therefore VM move operations between those set of computes will not be possible.

       

      Solution:

      Operator will be able to specify services they want deployed across all node sets, simultaneously. This will be accomplished by supplying all, node set specific, inventories to ansibleEE operator, while at the same time overriding default play target to `all`.

       

      Further context:

       Possible solution (quoting jslagle@redhat.com):

      if ansible merges the inventories as we expect, then we could have a separate service that uses a playbook just to configure known_hosts that uses hosts: all in the playbook. Then we would have to change all the playbooks to use hosts: <some other group> to mean just the one nodeset for this execution

       

      Original slack discussion: https://redhat-internal.slack.com/archives/CQXJFGMK6/p1696419778959799
      Revisited discussion: https://redhat-internal.slack.com/archives/CQXJFGMK6/p1702387896179729

            pweeks@redhat.com Phillip Weeks
            rh-ee-bgibizer Balazs Gibizer
            Jason Grosso Jason Grosso
            rhos-dfg-df
            Votes:
            0 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: