Hi All, Yes we are using a single JVM stratos.
Current AF cartridges get Application server packs through *wget* while spawning the instance. Shall we move to puppet instead?. If so we'll be modifying and provisioning new cartridges for php and appservers. On Tue, Nov 4, 2014 at 3:34 AM, Dimuthu Leelarathne <[email protected]> wrote: > Hi all, > > At the startos side we have to use single JVMs to make our 8GB target a > reality. Are we using single JVM stratots? If not we need to change that. > > @Udara - Can we have one puppet master with 3 envs? > > thanks, > dimuthu > > On Sun, Nov 2, 2014 at 8:07 PM, Udara Liyanage <[email protected]> wrote: > >> Hi, >> >> Are you going to have three puppet masters, one puppet master for each >> env? >> >> You need to install three ActiveMQ servers in the machine. [1] may help >> you to guide on that. Run boot.sh without "-s" option, otherwise it tries >> to install ActiveMQ. Anyhow you need to parameterized (or edit before >> servers starting up) ActiveMQ Ip and Port >> >> >> [1] >> http://udaraliyanage.wordpress.com/2014/02/05/start-multiple-activemq-brokers-in-the-same-server/ >> >> >> >> Touched, not typed. Erroneous words are a feature, not a typo. >> On Oct 31, 2014 12:04 PM, "Anuruddha Premalal" <[email protected]> >> wrote: >> > >> > Hi, >> > >> > I'm working on making the appfactory puppet scripts to be able to setup >> in a single node. >> > >> > Problem >> > >> > Current puppet scripts can be used (in a single run) to do a >> distributed setup where all app-factory related servers setup in different >> nodes. In single node setup, we cannot reference the same resource more >> than once in puppet. >> > >> > The other challenge is AF needs three private-paases and current paas >> scripts are written with the focus of single node deployment, hence it >> lacks some port offset configs. >> > >> > Solution >> > >> > Idea is to create a developer setup of Appfactory in a single run with >> minimal effort using puppet. >> > To overcome this resource conflict we are going to use a bash script >> to run puppet agent iteratively changing the hostname/certname. That way it >> will ensure appfactory node first and then the build server node and so on. >> > >> > For private-pass installation we are going to parameterise the entire >> setup with all the needed port offsets and use the puppet as explained >> above. >> >> can't we have another offset in puppet like privatePaasOffSet. This >> offset is parameterized. So a normal port >> > >> > Regards, >> > -- >> > Anuruddha Premalal >> > Software Eng. | WSO2 Inc. >> > Mobile : +94710461070 >> > Web site : www.regilandvalley.com >> > >> > >> > _______________________________________________ >> > Architecture mailing list >> > [email protected] >> > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> > >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Dimuthu Leelarathne > Architect & Product Lead of App Factory > > WSO2, Inc. (http://wso2.com) > email: [email protected] > Mobile : 0773661935 > > Lean . Enterprise . Middleware > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Anuruddha Premalal* Software Eng. | WSO2 Inc. Mobile : +94710461070 Web site : www.regilandvalley.com
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
