On Wed, Apr 30, 2014 at 11:46 AM, Shiroshica Kulatilake <[email protected]>wrote:
> > > > On Wed, Apr 30, 2014 at 11:37 AM, Amila Maha Arachchi <[email protected]>wrote: > >> Hi Punnadi, >> >> You don't need to add any DNS entries for the ELB. That will be done at >> the deployment time. You only need to add a CNAME record [1]. >> >> [1] http://en.wikipedia.org/wiki/CNAME_record >> >> >> On Wed, Apr 30, 2014 at 10:51 AM, Punnadi Gunarathna <[email protected]>wrote: >> >>> 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 >>> >> This is not needed. >> >>> 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> >>> >> >> This is correct and this needs to be added via the API. In the >> documentation, I don't see a sample for adding a CNAME, but it will be >> similar to what is there in the sample of the AWS documentation. >> >>> >>> >>> 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. >>>> >>> > Though this is done within AppFactory we need to write it in such a way > that it is not AWS specific since AF should not be tightly coupled to AWS. > AF needs to define an interface (with methods such as domainMappingAdded, domainMappingRemoved, etc.) for listeners to notify domain mapping. Then we can implement this as a separate jar and use only in a AWS deployment. So, AF will notify the listeners. If there are no listeners, it will just move on. For another IaaS, we can use another implementation. This way, the impl will not get bound to AWS. > > Thank you, > Shiro > > > > >> >>>> 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/> >>> >> >> >> >> -- >> *Amila Maharachchi* >> Senior Technical Lead >> WSO2, Inc.; http://wso2.com >> >> Blog: http://maharachchi.blogspot.com >> Mobile: +94719371446 >> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Shiroshica Kulatilake > > Architect, > WSO2, Inc. http://wso2.com/ > Phone: +94 776523867 > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Amila Maharachchi* Senior Technical Lead WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
