On Wed, Jan 23, 2013 at 9:27 AM, Nirmal Fernando <[email protected]> wrote:
> > > > On Wed, Jan 23, 2013 at 9:05 AM, Lahiru Sandaruwan <[email protected]>wrote: > >> >> >> >> On Wed, Jan 23, 2013 at 8:44 AM, Nirmal Fernando <[email protected]> wrote: >> >>> >>> On Jan 23, 2013 8:28 AM, "Lahiru Sandaruwan" <[email protected]> wrote: >>> > >>> > >>> > >>> > >>> > On Wed, Jan 23, 2013 at 5:56 AM, Ramith Jayasinghe <[email protected]> >>> wrote: >>> >> >>> >> Hi, >>> >> is the $subject possible? >>> >> Cli tool gave me an error while trying to use same alias from two >>> instances: >>> >> for sample (from CLI tool) >>> >> subscribe php sampleapp2 >>> >> >>> >> Error message thrown at CLI command: >>> >> >>> >> "Cartridge subscribe failure >>> >> Error while subscribing the cartridge php" >>> > >>> > Can not. because, >>> > Two tenants cannot use same alias for same cartridge type(PHP). >>> >>> Out of my mind, I don't see a reason for this. AFAIR our git repo url >>> template allows this. What prevents us allowing this? >>> >> We create an unique clustering domain with the alias. >> e.g. alias is "wordpress". Then ELB access url will be " >> wordpress.php.slive.com". >> >> So two tenants cannot have same. >> > > I see an usability issue here. Cause if I'm the tenant, I've no idea about > the aliases that other tenants have used on a cartridge. > And here we have a typical user in Ramith, who's finding it difficult to > figure out an alias for his tenant. > Agree. also if a tenant can use same alias for different cartridge types. eg. wso2 can get "wso2.php.slive.com" and "wso2.jetty.slive.com" But we have limitations. Thanks. > > >> Thanks. >> >>> > Also a tenant cannot use same alias for different cartridges of that >>> tenant. >>> > That means you only can use the same alias to different cartridge >>> types of different tenants. >>> > >>> > BTW. We have improved the cli error messages now. You will get the >>> update. >>> > >>> > Thanks. >>> >> >>> >> >>> >> >>> >> >>> >> -- >>> >> Ramith Jayasinghe >>> >> Technical Lead >>> >> WSO2 Inc., http://wso2.com >>> >> lean.enterprise.middleware >>> >> >>> >> E: [email protected] >>> >> P: +1 (469) 583-2035 >>> >> >>> >> >>> >> _______________________________________________ >>> >> Dev mailing list >>> >> [email protected] >>> >> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >> >>> > >>> > >>> > >>> > -- >>> > -- >>> > Lahiru Sandaruwan >>> > Software Engineer, >>> > Cloud Team, >>> > >>> > WSO2 Inc., http://wso2.com >>> > lean.enterprise.middleware >>> > >>> > email: [email protected] cell: (+94) 773 325 954 >>> > blog: http://lahiruwrites.blogspot.com/ >>> > twitter: http://twitter.com/lahirus >>> > linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 >>> > >>> > >>> > _______________________________________________ >>> > Dev mailing list >>> > [email protected] >>> > http://wso2.org/cgi-bin/mailman/listinfo/dev >>> > >>> >> >> >> >> -- >> -- >> Lahiru Sandaruwan >> Software Engineer, >> Cloud Team, >> WSO2 Inc., http://wso2.com >> lean.enterprise.middleware >> >> email: [email protected] cell: (+94) 773 325 954 >> blog: http://lahiruwrites.blogspot.com/ >> twitter: http://twitter.com/lahirus >> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 >> <http://wso2con.com/> >> > > > > -- > > Thanks & regards, > Nirmal > > Software Engineer- Platform Technologies Team, WSO2 Inc. > Mobile: +94715779733 > Blog: http://nirmalfdo.blogspot.com/ > > <http://nirmalfdo.blogspot.com/> > -- -- Lahiru Sandaruwan Software Engineer, Cloud Team, WSO2 Inc., http://wso2.com lean.enterprise.middleware email: [email protected] cell: (+94) 773 325 954 blog: http://lahiruwrites.blogspot.com/ twitter: http://twitter.com/lahirus linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 <http://wso2con.com/>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
