Hi Amila, So the AF listener has to implement a logic in such a way that DNS entries need to be added to each mapped url via AWS R53 service as follows. Are the given below entries correct?
192.168.10.11 lb.dev.stratos.com lb.dev.stratos.com myapp1-1.0.0-dev.wso2apps.com<http://myapp-1.0.0-dev.wso2apps.com> lb.dev.stratos.commyapp2-1.0.0-dev.wso2apps.com<http://myapp-1.0.0-dev.wso2apps.com> 192.168.10.12 lb.test.stratos.com lb.test.stratos.com myapp1-1.0.0-test.wso2apps.com<http://myapp-1.0.0-dev.wso2apps.com> lb.test.stratos.com myapp2-1.0.0-test.wso2apps.com<http://myapp-1.0.0-dev.wso2apps.com> 192.168.10.13 lb.prod.stratos.com lb.prod.stratos.com myapp1-1.0.0-prod.wso2apps.com<http://myapp-1.0.0-dev.wso2apps.com> lb.prod.stratos.com myapp2-1.0.0-prod.wso2apps.com<http://myapp-1.0.0-dev.wso2apps.com> On Wed, Apr 30, 2014 at 3:17 AM, Dmitry Sotnikov <[email protected]> wrote: > I'd say that for public App Cloud it makes sense to use AWS functionality > to avoid the extra steps. > > Also, I would have URLs that put the app name first - and not version > first - like: > myapp-1.0.0-dev.wso2apps.com > > This would get them mentally grouped by app which makes sense. > > Dmitry > > > > > On Tue, Apr 29, 2014 at 5:43 AM, Amila Maha Arachchi <[email protected]>wrote: > >> Hi all, >> >> At the moment AF team is working on implementing the URL mapping feature. >> Following are some examples of URLs to be mapped. >> >> 1.0.0-dev-myapp.cloudapps.com - DNS should get resolved to stratos dev >> ELB >> 2.1.0-test-myapp.cloudapps.com - DNS should get resolved to stratos test >> ELB >> 1.1.0-prod-myapp.cloudapps.com - DNS should get resolved to stratos prod >> ELB >> >> To add the DNS entries, most clean way seems to be using the AWS R53 >> service. With this, when you create a URL to be mapped, you will have to >> call the AWS api [1] and add a DNS entry (add a CName to ELB's host name). >> >> An alternative options is to use an Nginx in from of dev,test,prod ELBs >> and route requests based on the url pattern. But, this will introduce an >> additional hop. >> >> If we agree to use the AWS R53 api, Af code will have to be implemented >> in a way that this does not cause any issues in a non-EC2 infrastructure. >> i.e. a listener implementation is needed. >> >> If there are no objections, AF team, please note this. >> >> BTW, are there any arguments on whether this needs to be done by AF or >> Stratos? My understanding is, this needs to be done by AF when creating the >> nice url. >> >> [1] >> http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/RRSchanges_API.html >> >> Regards, >> AmilaM. >> >> -- >> *Amila Maharachchi* >> Senior Technical Lead >> WSO2, Inc.; http://wso2.com >> >> Blog: http://maharachchi.blogspot.com >> Mobile: +94719371446 >> >> > > > -- > Dmitry Sotnikov > VP of Cloud; WSO2, Inc.; http://wso2.com/ > email: [email protected]; cell: +1.949.303.9653; Skype: DSotnikov > Lean . Enterprise . Middleware > > <http://wso2.com/events/> > -- Thanks and Regards, Punnadi Gunarathna Senior Software Engineer, WSO2, Inc.; http://wso2.com <http://wso2> Blog: http://hi-my-world.blogspot.com/ Tel : 94 11 214 5345 Fax :94 11 2145300 <http://lalajisureshika.blogspot.com/>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
