perhaps the Cluster Usage documentation page should be updated with a section containing links to external libraries implementing this glue functionality, similar to how external serializers are mentioned on the Serialization page: http://doc.akka.io/docs/akka/2.3.11/scala/serialization.html#External_Akka_Serializers

The Cluster Usage page is kind of a monster already tho...

-Michael

On 06/22/15 03:30, i...@virgon.eu wrote:
Hello,

Me and my team have successfully managed to bootstrap Akka Cluster with Docker and Mesos, and we're actually running automated performance tests against ephemeral clusters using this combination - so it's working *that* well. The thing that really made it tick (and quickly so - since this part of the implementation took mere minutes) was Marathon - it's exporting Mesos slave's external hostname/ip and port and from there it's really typesafe config. Of course that might not be relevant to your situation, but I'd still suggest that you look at how they've done it. If you're interested in more details, I could prioritise writing a blog post describing the setup in more detail.

Cheers

On Sunday, June 21, 2015 at 9:33:40 AM UTC+2, rkuhn wrote:

    Hi Brian & Greg,

    the bind-host capability does indeed not solve the whole problem,
    but it is what is needed from Akka to enable you to do so (as you
    have done, thanks for sharing!). It might make sense to create
    small libraries that simplify the process for the various clouds
    out there, but in the end such a library would not be
    Akka-specific: it is just needed to obtain a host:port combination
    from a container service so that it can then be passed to another
    library that makes use of the network (like akka-cluster). What
    I’m getting at is that the akka/akka repository does not
    necessarily need to contain all the code, it would be enough (or
    maybe even better) to document how to pass in these pieces of
    information obtained via other means. Of course if large benefits
    are to be had by closely integrating then we’ll discuss this on a
    case by case basis.

    Regards,

    Roland

    20 jun 2015 kl. 23:16 skrev Brian Topping <brian....@gmail.com
    <javascript:>>:

    Interesting responses, thanks!

    As a question to the core team, should the problems Greg raised
    be reported as issues? What would be appropriate release target
    if so?

    Greg, I'm going to be busy with a Java-land client for the next
    couple of weeks, but I will do my best to clone your project and
    build some PRs if I can.

    Cheers, Brian

    On Jun 18, 2015, at 3:04 PM, tigerfoot <gzo...@gmail.com
    <javascript:>> wrote:

    Actually that's not quite right...its not nearly that simple.
     These "oceans" like Mesos need to auto-assign the ports so
    while, yes, 2.4 gives dual binding capabilities this is only
    useful when you know the ports!

    So how do you do that?  That's much more complex.

    I've got a hello-world remote project in github that shows how
    to do this on Amazon's container service ECS, using some
    AWS-specific capabilities, namely to call an api from within a
    running Docker to find the IP of the host its running on (not
    the Docker-internal IP).  From there other magic is possible.  I
    can successfully launch a bunch of Dockers into ECS and it will
    figure out what's-what and bind to the dynamic ports ECS
    assigns, and from there I can talk to them.

    See here for info:
    https://github.com/gzoller/docker-exp/tree/remoting
    <https://github.com/gzoller/docker-exp/tree/remoting>

    (NOTE: The clustering branch of this project is still in-work,
    and will not function properly yet, but soon will using the same
    principles.  My expectations is that a cluster in an ocean will
    need to use pub-sub or similar mechanism to identify actors
    "somewhere" to talk to, but we'll see...)

    You're going to have to adapt this for Mesos.  If you so, shoot
    a pull request to my project so I've got it. :-)

    Remoting in oceans is ok, but I suspect what you're really
    shooting for will be the clustering.... fire a bunch of nodes
    wrapped in Dockers out there and have them self-detect and then
    just talk to them w/o having to know where they are actually
    running.  I'm working on this now....

    Greg

    On Thursday, June 18, 2015 at 1:27:59 PM UTC-5, √ wrote:

        Akka 2.4 solves the docker problem with supporting an
        external address and one internal.

-- Cheers,
        √

        On 18 Jun 2015 19:28, "Jason Martens"
        <m...@jasonmartens.com> wrote:

            I have heard from another co-worker that Akka remoting
            is very difficult on Mesos using Docker, because of the
            random ports that it uses to connect. Docker expects you
            to specify which ports are going to be used by your
            container, and if you don't know ahead of time it can be
            difficult to support. Keep that in mind when considering
            deploying using a container.

            Jason

            On Wednesday, June 17, 2015 at 12:36:52 PM UTC-7, Brian
            Topping wrote:

                Hi all,

                Just curious if anyone on the list has tried to
                blend Akka and Mesos at a level that is more
                granular than the JVM. For those that have heard
                about it but don't know much about it's core, Mesos
                is using kernel cgroups to provide ultra light
                weight virtualization with very low overhead for
                startup and shutdown as well as being able to
                provide resource constraints to requesting entities.

                In one view, it might not make sense to go more
                granular than the JVM. After all, Mesos can't run
                JVM classes without one. On the other hand, I'm
                thinking it might be very useful to have a
                standardized Akka container that would allow actor
                distribution with consistent stream-oriented APIs
                that took care of all the clustering concerns with
                robust, well-established techniques. There's
                certainly a lot that can be done here, for instance
                with "warm nodes" that are pooled for usage spikes
                and could reduce first transaction latency even
                further with no change to semantics.

                WDYT?

                Brian


-- >>>>>>>>>> Read the docs: http://akka.io/docs/
            >>>>>>>>>> Check the FAQ:
            http://doc.akka.io/docs/akka/current/additional/faq.html
            <http://doc.akka.io/docs/akka/current/additional/faq.html>
            >>>>>>>>>> Search the archives:
            https://groups.google.com/group/akka-user
            <https://groups.google.com/group/akka-user>
            ---
            You received this message because you are subscribed to
            the Google Groups "Akka User List" group.
            To unsubscribe from this group and stop receiving emails
            from it, send an email to akka-user+...@googlegroups.com.
            To post to this group, send email to
            akka...@googlegroups.com.
            Visit this group at
            http://groups.google.com/group/akka-user
            <http://groups.google.com/group/akka-user>.
            For more options, visit
            https://groups.google.com/d/optout
            <https://groups.google.com/d/optout>.


-- >>>>>>>>>> Read the docs: http://akka.io/docs/
    >>>>>>>>>> Check the FAQ:
    http://doc.akka.io/docs/akka/current/additional/faq.html
    <http://doc.akka.io/docs/akka/current/additional/faq.html>
    >>>>>>>>>> Search the archives:
    https://groups.google.com/group/akka-user
    <https://groups.google.com/group/akka-user>
    ---
    You received this message because you are subscribed to the
    Google Groups "Akka User List" group.
    To unsubscribe from this group and stop receiving emails from
    it, send an email to akka-user+...@googlegroups.com <javascript:>.
    To post to this group, send email to akka...@googlegroups.com
    <javascript:>.
    Visit this group at http://groups.google.com/group/akka-user
    <http://groups.google.com/group/akka-user>.
    For more options, visit https://groups.google.com/d/optout
    <https://groups.google.com/d/optout>.


-- >>>>>>>>>> Read the docs: http://akka.io/docs/
    >>>>>>>>>> Check the FAQ:
    http://doc.akka.io/docs/akka/current/additional/faq.html
    <http://doc.akka.io/docs/akka/current/additional/faq.html>
    >>>>>>>>>> Search the archives:
    https://groups.google.com/group/akka-user
    <https://groups.google.com/group/akka-user>
    ---
    You received this message because you are subscribed to the
    Google Groups "Akka User List" group.
    To unsubscribe from this group and stop receiving emails from it,
    send an email to akka-user+...@googlegroups.com <javascript:>.
    To post to this group, send email to akka...@googlegroups.com
    <javascript:>.
    Visit this group at http://groups.google.com/group/akka-user
    <http://groups.google.com/group/akka-user>.
    For more options, visit https://groups.google.com/d/optout
    <https://groups.google.com/d/optout>.



    *Dr. Roland Kuhn*
    /Akka Tech Lead/
    Typesafe <http://typesafe.com/> – Reactive apps on the JVM.
    twitter: @rolandkuhn
    <http://twitter.com/#%21/rolandkuhn>

--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>>>>>>> Check the FAQ: http://doc.akka.io/docs/akka/current/additional/faq.html
>>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user
---
You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com <mailto:akka-user+unsubscr...@googlegroups.com>. To post to this group, send email to akka-user@googlegroups.com <mailto:akka-user@googlegroups.com>.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

--
     Read the docs: http://akka.io/docs/
     Check the FAQ: http://doc.akka.io/docs/akka/current/additional/faq.html
     Search the archives: https://groups.google.com/group/akka-user
--- You received this message because you are subscribed to the Google Groups "Akka User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Reply via email to