• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Diferent multicast addresses for a storage group

Scheduled Pinned Locked Moved
General
2
7
3.4k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • F
    Frank
    last edited by Jul 15, 2014, 9:22 AM

    Hi,
    we know that in order to make multicast deployments Fog uses udp-sender which in default uses a multicast address based on host IP. As you sure know that makes only one multicast deployment possible at once.
    Is there an easy way to change that and allow multiple multicast deployments in a single storage repository or do you have plans to change that in future versions?

    Thanks and regards.

    Frank

    1 Reply Last reply Reply Quote 0
    • T
      Tom Elliott
      last edited by Jul 15, 2014, 9:33 AM

      You can have multiple multicast deployments at once from a single FOG Server. If you were trying to use the same port you’d be running into issues, but as I randomize the port so this doesn’t happen you shouldn’t have any issues.

      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

      Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

      Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

      1 Reply Last reply Reply Quote 0
      • F
        Frank
        last edited by Jul 15, 2014, 9:45 AM

        Hi Tom,
        I’m not a guru of multicast, but I am quite sure that multicast groups depend only on multicas IP not port. In fact, in udp-sender there is no option for multicast port, only for unicast.

        So I don’t see that different multicasts deployment perform well if you don’t change multicast IP. Of course you can launch several multicast deployments, but all of them will be on the same multicast group, which leads to a poor network performance.

        Frank

        1 Reply Last reply Reply Quote 0
        • T
          Tom Elliott
          last edited by Jul 15, 2014, 10:42 AM

          I’m no guru on multicast myself. That said, isn’t multicast port driven? While you can specify different multicast IP’s and it may help in cases where people have multiple nic’s to give up, it’s ultimately dependent on the port to know where to get the data from. At least from the client side. The only people who care about the data are the one’s listening for that port.

          I am under the impression, that while the multicast IP can be changed, it’s usually set for 224.0.0.X range. Source specific is generally in the 232.0.0.X range and SSDP is done on 239.255.255.250

          A good read:
          [url]http://en.wikipedia.org/wiki/Multicast_address[/url]

          At any rate it’s standard, but not necessarily something people must follow. In their own environments they may want to use other custom addresses for handling this, but this is NOT the norm. The Ports that are sending AND/OR listening are the important parts, otherwise a single multicast system would DESTROY a network.

          Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

          Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

          Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

          1 Reply Last reply Reply Quote 0
          • F
            Frank
            last edited by Jul 15, 2014, 11:08 AM

            What I can tell you it’s that we have been fighting with multicast transfers for log time ago with several deployment systems as rembo an Tivoli later, so we have some experience on that. I’m not an expert with network, but we have a network team group here with great experience and we have been working closely with them.

            It’s true that for multicast as for unicast there is an IP and a port, but what makes possible different multicast transfers is what is called a multicast group, and that depends only on IP as I said. If you monitor multicast info in switches you can notice that. Also note that neither udp-sender manual page nor the wiki page you told me don’t talk about multicast port settings but only IP settings. So one multicast address mean only one multicast group and that’s why I posted my question.

            Check that if you want to in a test environment and you will see that only one multicast group is created for all the multicasts transfers, which of course makes that all hosts in the group receive packets from all multicasts transfers.

            Frank

            1 Reply Last reply Reply Quote 0
            • T
              Tom Elliott
              last edited by Jul 15, 2014, 11:41 AM

              I’m not trying to say you haven’t done your own research. In Fact, I am certain you are correct. But it’s not a road I’m willing to go down. If you want to change the IP’s and configs to do such a thing, be my guest. I prefer not using Multicast and have very limited experience even when using it.

              Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

              Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

              Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

              1 Reply Last reply Reply Quote 0
              • F
                Frank
                last edited by Jul 16, 2014, 6:07 AM

                Thanks Tom. I didn’t pretend to criticized Fog in any way because I think it is a great tool and there is an excellent work behind it.
                We think that multicast is a very good way to get the best from network bandwidth if you are sending the same image to multiple clients, so we think that a product like fog could take profit of this.
                From you answer I guess that multicast is not a priority so I will follow your advise and I will try to modify code to allow multiple multicast transfers. The only thing I wanted to know it was if that was in your roadmap.

                Thanks a lot anyway.

                Frank

                1 Reply Last reply Reply Quote 0
                • 1 / 1
                1 / 1
                • First post
                  5/7
                  Last post

                298

                Online

                12.0k

                Users

                17.3k

                Topics

                155.2k

                Posts
                Copyright © 2012-2024 FOG Project