Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-community] GlassFish and Payara Auto-Clustering in Containers
Hello Ruslan,
 
good hint of Daniel. Thanks for showing that the email included a link with all needed information.
 
Best Regards,
Alex
 
 
 
Gesendet: Donnerstag, 02. November 2017 um 15:37 Uhr
Von: "Daniel Dias Dos Santos" <daniel.dias.analistati@xxxxxxxxx>
An: "EE4J community discussions" <ee4j-community@xxxxxxxxxxx>
Betreff: Re: [ee4j-community] GlassFish and Payara Auto-Clustering in Containers
what an excellent article.

Thanks for sharing .
 
--
Daniel Dias dos Santos
Java Developer
Diretor SouJava & JCP Member Linkedin: http://br.linkedin.com/in/danieldiassantos
 
2017-11-02 12:11 GMT-02:00 Alexander Salvanos <salvanos@xxxxxx>:
Hi Ruslan,
 
I like the whole idea. Have you done Integration-Testings with the GlassFish Server?
Do you have a documentation? Would you mind to show this solution in a web-session?
 
Best Regards
Alex
 

 

 
Gesendet: Donnerstag, 02. November 2017 um 14:34 Uhr
Von: "Ruslan Synytsky" <rs@xxxxxxxxxxxx>
An: ee4j-community@xxxxxxxxxxx
Betreff: [ee4j-community] GlassFish and Payara Auto-Clustering in Containers
Hi everyone,
 
I would like to share our latest achievements on GlassFish/Payara clustering automation. It was quite a long road to discover all related "nuances" and adjust it to the containers approach. The current solution automatically provisions and scales GF cluster inside containers. It enables to go from dev or test mode with a standalone instance to production with domain mode cluster in a single click. This implementation is not just a bunch of standalone instances but a complete cluster fully manageable via single DAS panel.

Each container includes one Instance per Node that lets implement a granular horizontal and vertical scaling. In our case, the cluster is built using Docker application containers for templates packaging and Virtuozzo system containers for more advanced resource management.

Automation is mostly based on standard built-in GF components - session replication, auto-discovery of new nodes, configs propagation across the nodes, deploy and redeploy of applications into the cluster, etc. A running cluster can be easily cloned (das, worker instances & load balancer). It will duplicate the existing instances on the fly and reconfigure the cloned replica updating interconnections across new containers and instances.

At the moment it is Jelastic specific, so we can allocate free resources for those who are ready to provide a feedback. As a next step, with your help, we would like to make this solution more universally applicable. Looking forward to your evaluation of the current implementation and ideas what can be improved, just leave your comments here or drop me a message in person.

Thanks
--
Ruslan
CEO @ Jelastic
 
 
 
_______________________________________________ ee4j-community mailing list ee4j-community@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/ee4j-community

_______________________________________________
ee4j-community mailing list
ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-community
 
_______________________________________________ ee4j-community mailing list ee4j-community@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/ee4j-community

Back to the top