Hi Odd,

Thanks. I've looked at constructr and see that it would work fine and is a 
general solution not tied to AWS/ECS. However, it does add more moving 
parts to a deployment and has the potential to get out of sync with the 
source of truth of the cluster definition -- ECS itself. I will, however, 
consider it, as there is some beauty in a general solution.  -- Eric

On Tuesday, February 2, 2016 at 1:15:17 AM UTC-8, Odd Möller wrote:
>
> Hi Eric, have you looked at https://github.com/hseeberger/constructr?
>
> Greetings
> Odd
>
> On Tue, Feb 2, 2016 at 9:26 AM, Roland Kuhn <[email protected] 
> <javascript:>> wrote:
>
>> Yes, this sounds like a good strategy to me.
>>
>> Regards,
>>
>> Roland
>>
>> 1 feb 2016 kl. 23:56 skrev Eric Swenson <[email protected] <javascript:>
>> >:
>>
>> Probably a better roll-my-own solution would involve querying AWS/ECS 
>> dynamically to discover the IP addresses of the containers running in the 
>> cluster, excluding the IP address of node making the query, and setting the 
>> seed nodes to the remaining nodes. This way, the likely of getting the list 
>> of nodes out-of-sync with reality is minimal.  — Eric
>>
>> On Feb 1, 2016, at 2:43 PM, Eric Swenson <[email protected] <javascript:>> 
>> wrote:
>>
>> Are there any good solutions for deploying akka clustered applications in 
>> docker containers running under AWS/ECS?  While there are proposed 
>> solutions for AWS/EC2 with autoscaling, none of them targets AWS/ECS.  In a 
>> nutshell, the issue is this:
>>
>> If your cluster-nodes are implemented as docker containers, and 
>> formalized as ECS tasks that are members of an ECS service (in an ECS 
>> cluster), then when they are started and stopped (by ECS) in response to 
>> load, their IP addresses are impossible to predict. It is not possible to 
>> configure a fixed set of seed nodes at known IP addresses unless these seed 
>> nodes are managed independently of ECS automatic management. And, of 
>> course, having fixed, known seed nodes becomes problematic if/when these 
>> nodes fail.  
>>
>> I could roll my own solution using a key/value store like redis, where 
>> whenever a node comes up, it first publishes its IP addresses (and port, if 
>> not common) to the key/value store, and then queries that store to 
>> configure its seed nodes. Care would have to be taken to clean up old 
>> entries when nodes fail, of course. But it seems like I shouldn't be the 
>> first person to run into akka-cluster issues on AWS/ECS and that other 
>> solutions might be out there. Unfortunately, I've found none.
>>
>> Any ideas?
>>
>> -- Eric
>>
>>
>> -- 
>> >>>>>>>>>> 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 a topic in the 
>> Google Groups "Akka User List" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/akka-user/MnxSZma4QJI/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> [email protected] <javascript:>.
>> To post to this group, send email to [email protected] 
>> <javascript:>.
>> Visit this group at https://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 [email protected] <javascript:>.
>> To post to this group, send email to [email protected] 
>> <javascript:>.
>> Visit this group at https://groups.google.com/group/akka-user.
>> For more options, visit 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/#!/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 [email protected] <javascript:>.
>> To post to this group, send email to [email protected] 
>> <javascript:>.
>> Visit this group at https://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 [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Reply via email to