Results 1 to 3 of 3

Thread: SES Planing: keeping ISCSI gates on OSD nodes - is wise?

Hybrid View

  1. #1

    SES Planing: keeping ISCSI gates on OSD nodes - is wise?

    Thinking about how to deploy SES for block-oriented applications "in smart way", I made a conclusion the iSCSI gateways should be deployed at the same servers with OSD nodes.

    Pro:
    - The "locality" of the iSCSI gate and corresponding image container might increase the productivity by removing LAN infrastructure from "local" data path.
    - If the cluster is not tweaked, the possibility of local data hit is 1 / OSD_Number. Thus, the smaller the cluster, the greater the gain.
    - If the CRUSH map will be tweaked to store more container data locally to their iSCSI gates, the gain will be increased.
    - The iSCSI multipathing might increase the performance as well.
    - If the CPU will be saturated, the classic Hi-End approach "one role per node" still might be used.

    Contra:
    - The amount of administrative work is increased.
    - Will SUSE still support such non-standard configuration? For example, 3 nodes for monitors and 10 nodes for OSD+iSCSI...

    Am I right?

  2. #2

    Re: SES Planing: keeping ISCSI gates on OSD nodes - is wise?

    polezhaevdmi,

    It appears that in the past few days you have not received a response to your
    posting. That concerns us, and has triggered this automated reply.

    These forums are peer-to-peer, best effort, volunteer run and that if your issue
    is urgent or not getting a response, you might try one of the following options:

    - Visit http://www.suse.com/support and search the knowledgebase and/or check all
    the other support options available.
    - Open a service request: https://www.suse.com/support
    - You could also try posting your message again. Make sure it is posted in the
    correct newsgroup. (http://forums.suse.com)

    Be sure to read the forum FAQ about what to expect in the way of responses:
    http://forums.suse.com/faq.php

    If this is a reply to a duplicate posting or otherwise posted in error, please
    ignore and accept our apologies and rest assured we will issue a stern reprimand
    to our posting bot..

    Good luck!

    Your SUSE Forums Team
    http://forums.suse.com



  3. #3

    Re: SES Planing: keeping ISCSI gates on OSD nodes - is wise?

    Still seems the idea is good. Here is the example of lrbd configuration file, which allows to serve single iSCSI target with 4-way multipathing to 4 OSD nodes.
    Code:
    {
      "auth": [
        { "target": "iqn.2016-07.org.ses-iscsi.igw.x86:mpath", "authentication": "none" }
      ],
      "targets": [
        {
          "target": "iqn.2016-07.org.ses-iscsi.igw.x86:mpath",
          "hosts": [
              { "host": "osd01", "portal": "portal01" }, 
              { "host": "osd02", "portal": "portal02" }, 
              { "host": "osd03", "portal": "portal03" }, 
              { "host": "osd04", "portal": "portal04" } 
          ]
        }
      ],
      "portals": [
             { "name": "portal01", "addresses": [ "172.18.65.144" ] },
             { "name": "portal02", "addresses": [ "172.18.65.153" ] }, 
             { "name": "portal03", "addresses": [ "172.18.65.154" ] }, 
             { "name": "portal04", "addresses": [ "172.18.65.155" ] }
      ],
      "pools": [
        {
          "pool": "iscsi01",
          "gateways": [ 
            {
              "target": "iqn.2016-07.org.ses-iscsi.igw.x86:mpath",
              "tpg": [ { "image": "iscsivol01" } ]
            }
          ]
        }
      ]
    }

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •