Thanks Rajika, that´s what we need to use CSG. We will test Stratos with Eucalyptus and come back with the feedback.
Jorge. De: [email protected] [mailto:[email protected]] En nombre de Rajika Kumarasiri Enviado el: jueves, 28 de julio de 2011 0:52 Para: [email protected] Asunto: Re: [Carbon-dev] CSG component. Jorge, comments are inline. On Wed, Jul 27, 2011 at 11:36 PM, Jorge Infante Osorio <[email protected]> wrote: +1. My scenario it´s very similar to one that it´s describe in a wso2 presentation for soa patterns in the cloud: We have our AS in a LAN for private use of services and applications and we have the need to expose some of this services through the DMZ to the outside. So we saw this post: http://kscottmorrison.com/2010/02/09/how-to-safely-publish-internal-services -to-the-outside-world/ about how Layer7 do this and right now we are interesting in do the same but with WSO2 and CSG. Great! By what you say I assume we need to use Stratos in the DMZ with ESB and MB. Is that correct? Correct but you don't need MB process since CSG uses inbuilt Qpid broker component inside ESB service. Currently CSG server component distribute with ESB service only. You can always install CSG server feature into a standalone product. But we need to make the domain name optional and if domain is provided we need to compute the user name as 'user-name@domain-name' otherwise just 'user-name'. https://wso2.org/jira/browse/STRATOS-1652 In the meantime we want to test with Eucalyptus as the "Infrastructure as Service", to used it to deploy Stratos in a private Cloud. Are you test this scenario or have the hardware requirements we need to follow to deploy Stratos? Yes have tested Stratos on Eucalyptus and we do recommend it for private cloud deployments. We are in the process of compiling hardware sizing document for various Straros deployment. Thanks for your suggestions. Rajika _______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
