Re: [Architecture] Improving docker image creation in IntegrationStudio
On Thu, May 30, 2019 at 10:37 AM Nuwan Bandara wrote: > > > On Thu, May 30, 2019 at 11:22 AM Lahiru Sandaruwan > wrote: > >> >> >> On Wed, May 29, 2019 at 4:33 AM Lahiru Madushanka >> wrote: >> >>> Hi all, >>> >>> Please find the description of the proposed model below. >>> >>> I am proposing to handle the single CAPP and multiple CAPPs scenarios >>> differently. >>> >>>- Single CAPP >>> >>> In this case we can add the spotify doker plugin to the pom file of >>> carbon application project. >>> >>> Also we must copy the dockerFile to the CAPP project directly. >>> >>> Then, when user builds the project, spotify plugin is creating the new >>> image using dokerFile. >>> >>> The docerFile is wtriten in such a way that it copy the CAPP inside the >>> target folder to the MI carbonApps folder. >>> >>> [image: docker.jpg] >>> >>> >>>- Multiple CAPPs >>> >>> In this case we have to introduce a new project type called a docker >>> project. ( which contains a pom file, dockerFile and a folder to put CAPPs ) >>> >>> To select CAPPs for the image, we can provide a list of carbon >>> applications in the curent workspace for the customer to choose. >>> >>> When customer choose a project, we can add the maven resource plugin to >>> that carbon application project. >>> >>> Then, upon building those projects the resulting CAPP will be copied to >>> the desired folder of docker project automatically. >>> >>> >> IMO having the same approach for single or multiple CApps is better. >> Therefore +1 for creating separate project type called Docker and allow add >> any number of CApps there. However, I feel little differently on the file >> management process. >> >> Here is my suggestion, >> - Car files are deployed in Maven repo(local or remote), which is what we >> have now >> - We will add the new Docker project type >> - Upon building the Docker project, it will create Dockerfile in the >> target directory >> >> Nuwan, if we use 'Composite Application Project' for Dockerfile creation, >> it will only contain single CApp that is created in that project. Isn't it? >> > > Yes ur correct Lahiru. > > Like ur suggestion. So this means when I build the Docker project type, it > will pull all the .car files from the maven repo to the directory (where am > building) so when I run Docker with the generated Dockerfile, I will get > the image ? > Yes. > > I define all the CApps I want in the container in the Docker project type > pom yeah ? I think That's what @Lahiru Madushanka has > mentioned in #2 approach > That is what I understood as well. Similar to how we get for Synapse artifact references in CApp, we can check boxes for the existing CApps in the Docker project. Thanks. > > > >> >> Thanks. >> >>> Then when we build the docker project, it will create a new image using >>> all the copies of CAPPs resides in the carbon apps folder. >>> >>> [image: docker2.jpg] >>> >>> I tested this scenario with multiple CAPPs and its working fine. >>> Your suggestions are highly appreciated. >>> >>> Thanks, >>> *Lahiru Madushanka* | Software Engineer | WSO2 Inc. >>> 071 7276083 | lahirum...@wso2.com >>> GET INTEGRATION AGILE >>> Integration Agility for Digitally Driven Business >>> <http://wso2.com/signature> >>> >> >> >> -- >> -- >> >> Lahiru Sandaruwan >> WSO2 Inc., http://wso2.com >> >> lean.enterprise.middleware >> >> m: +1 901 530 2379 >> e: lahi...@wso2.com b: https://medium.com/@lahirugmg >> in: *https://www.linkedin.com/in/lahirugmg/ >> <https://www.linkedin.com/in/lahirugmg/>* >> >> ___ >> Architecture mailing list >> Architecture@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> > > > -- > > > *Thanks & Regards,* > *Nuwan Bandara | Director - **Solutions Architecture, WSO2 Inc.* > *+1 646 643 8618 | +1 650 745 2169 Ext 4212 | http://nuwanbando.com > <http://nuwanbando.com> * > <http://www.nuwanbando.com/> > -- -- Lahiru Sandaruwan WSO2 Inc., http://wso2.com lean.enterprise.middleware m: +1 901 530 2379 e: lahi...@wso2.com b: https://medium.com/@lahirugmg in: *https://www.linkedin.com/in/lahirugmg/ <https://www.linkedin.com/in/lahirugmg/>* ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Improving docker image creation in IntegrationStudio
On Wed, May 29, 2019 at 4:33 AM Lahiru Madushanka wrote: > Hi all, > > Please find the description of the proposed model below. > > I am proposing to handle the single CAPP and multiple CAPPs scenarios > differently. > >- Single CAPP > > In this case we can add the spotify doker plugin to the pom file of carbon > application project. > > Also we must copy the dockerFile to the CAPP project directly. > > Then, when user builds the project, spotify plugin is creating the new > image using dokerFile. > > The docerFile is wtriten in such a way that it copy the CAPP inside the > target folder to the MI carbonApps folder. > > [image: docker.jpg] > > >- Multiple CAPPs > > In this case we have to introduce a new project type called a docker > project. ( which contains a pom file, dockerFile and a folder to put CAPPs ) > > To select CAPPs for the image, we can provide a list of carbon > applications in the curent workspace for the customer to choose. > > When customer choose a project, we can add the maven resource plugin to > that carbon application project. > > Then, upon building those projects the resulting CAPP will be copied to > the desired folder of docker project automatically. > > IMO having the same approach for single or multiple CApps is better. Therefore +1 for creating separate project type called Docker and allow add any number of CApps there. However, I feel little differently on the file management process. Here is my suggestion, - Car files are deployed in Maven repo(local or remote), which is what we have now - We will add the new Docker project type - Upon building the Docker project, it will create Dockerfile in the target directory Nuwan, if we use 'Composite Application Project' for Dockerfile creation, it will only contain single CApp that is created in that project. Isn't it? Thanks. > Then when we build the docker project, it will create a new image using > all the copies of CAPPs resides in the carbon apps folder. > > [image: docker2.jpg] > > I tested this scenario with multiple CAPPs and its working fine. > Your suggestions are highly appreciated. > > Thanks, > *Lahiru Madushanka* | Software Engineer | WSO2 Inc. > 071 7276083 | lahirum...@wso2.com > GET INTEGRATION AGILE > Integration Agility for Digitally Driven Business > <http://wso2.com/signature> > -- -- Lahiru Sandaruwan WSO2 Inc., http://wso2.com lean.enterprise.middleware m: +1 901 530 2379 e: lahi...@wso2.com b: https://medium.com/@lahirugmg in: *https://www.linkedin.com/in/lahirugmg/ <https://www.linkedin.com/in/lahirugmg/>* ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Configure token expiry time based on the Service provider (APIM application)
Thanks Harsha. It seems it is available form IS 5.4.0. On Tue, Feb 27, 2018 at 11:58 AM, Harsha Thirimanna <hars...@wso2.com> wrote: > > > On Tue, Feb 27, 2018 at 11:07 PM, Lahiru Sandaruwan <lahi...@wso2.com> > wrote: > >> Hi Harsha, >> >> Did we add application level validity period requirement to Roadmap? Do >> we plan to implement this in near future? >> > > Per service provider wise expire time set to the bellow tokens are already > there in the product. > > User Access Token > Application Access Token > Refresh Token > > https://docs.wso2.com/display/IS540/Configuring+Inbound+ > Authentication+for+a+Service+Provider > > >> >> Thanks. >> >> On Tue, Apr 25, 2017 at 12:48 AM, Sanjeewa Malalgoda <sanje...@wso2.com> >> wrote: >> >>> >>> >>> On Tue, Apr 25, 2017 at 8:46 AM, Harsha Thirimanna <hars...@wso2.com> >>> wrote: >>> >>>> >>>> >>>> On 21 Apr 2017 3:35 p.m., "Asela Pathberiya" <as...@wso2.com> wrote: >>>> >>>> Hi IS/APIM team, >>>> >>>> Is $subject in our roadmap ? >>>> >>>> We will add this to the roadmap. >>>> >>>> This seems to be a required features. Different applications may need >>>> the different user token expiry time based on their security level. >>>> >>>> >>>> >>>> >>>> Yes, it seems the application should have this capability to do. >>>> But what is the real use case to have this per user ? >>>> >>> It depends lets think user know he is going to use this for shorter >>> period(from mobile app) then he can request with smaller time (lets say 5 >>> mins). Then from token issuer logic we can check application level max >>> value and issue token with requested validity period if requested time is >>> below what they allow in application level. So this is not really user >>> level thing but optional parameter we send on demand when we generate >>> tokens. If token generation request allows to send optional parameters like >>> DCR we will be able to send requested_validity(if not sent default >>> application level validity time will apply). >>> >>> Thanks, >>> sanjeewa. >>> >>>> >>>> Just heard that; IOT server may has already requirement with that; It >>>> is needed to define a token expiry level based on their device type. Say; >>>> some device's token may be embedded & these token may have longer expiry >>>> time (never expired). Also; some devices type need a less expiry time >>>> based on their security policies. It is not sure how we are handled this >>>> with APIM feature without $subject. But; this can be easily handled, if >>>> we can have such feature inbuilt. >>>> >>>> Thanks, >>>> Asela >>>> >>>> >>>> -- >>>> Thanks & Regards, >>>> Asela >>>> >>>> ATL >>>> Mobile : +94 777 625 933 <+94%2077%20762%205933> >>>> +358 449 228 979 >>>> >>>> http://soasecurity.org/ >>>> http://xacmlinfo.org/ >>>> >>>> _______ >>>> Architecture mailing list >>>> Architecture@wso2.org >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>>> >>> >>> >>> -- >>> >>> *Sanjeewa Malalgoda* >>> WSO2 Inc. >>> Mobile : +94713068779 <071%20306%208779> >>> >>> <http://sanjeewamalalgoda.blogspot.com/>blog >>> :http://sanjeewamalalgoda.blogspot.com/ >>> <http://sanjeewamalalgoda.blogspot.com/> >>> >>> >>> >>> ___ >>> Architecture mailing list >>> Architecture@wso2.org >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> -- >> >> Lahiru Sandaruwan >> WSO2 Inc., http://wso2.com >> >> lean.enterprise.middleware >> >> m: +1 901 530 2379 <(901)%20530-2379> >> e: lahi...@wso2.com b: https://medium.com/@lahirugmg >> in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 >> >> > -- -- Lahiru Sandaruwan WSO2 Inc., http://wso2.com lean.enterprise.middleware m: +1 901 530 2379 e: lahi...@wso2.com b: https://medium.com/@lahirugmg in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Configure token expiry time based on the Service provider (APIM application)
Hi Harsha, Did we add application level validity period requirement to Roadmap? Do we plan to implement this in near future? Thanks. On Tue, Apr 25, 2017 at 12:48 AM, Sanjeewa Malalgoda <sanje...@wso2.com> wrote: > > > On Tue, Apr 25, 2017 at 8:46 AM, Harsha Thirimanna <hars...@wso2.com> > wrote: > >> >> >> On 21 Apr 2017 3:35 p.m., "Asela Pathberiya" <as...@wso2.com> wrote: >> >> Hi IS/APIM team, >> >> Is $subject in our roadmap ? >> >> We will add this to the roadmap. >> >> This seems to be a required features. Different applications may need >> the different user token expiry time based on their security level. >> >> >> >> >> Yes, it seems the application should have this capability to do. >> But what is the real use case to have this per user ? >> > It depends lets think user know he is going to use this for shorter > period(from mobile app) then he can request with smaller time (lets say 5 > mins). Then from token issuer logic we can check application level max > value and issue token with requested validity period if requested time is > below what they allow in application level. So this is not really user > level thing but optional parameter we send on demand when we generate > tokens. If token generation request allows to send optional parameters like > DCR we will be able to send requested_validity(if not sent default > application level validity time will apply). > > Thanks, > sanjeewa. > >> >> Just heard that; IOT server may has already requirement with that; It is >> needed to define a token expiry level based on their device type. Say; >> some device's token may be embedded & these token may have longer expiry >> time (never expired). Also; some devices type need a less expiry time >> based on their security policies. It is not sure how we are handled this >> with APIM feature without $subject. But; this can be easily handled, if >> we can have such feature inbuilt. >> >> Thanks, >> Asela >> >> >> -- >> Thanks & Regards, >> Asela >> >> ATL >> Mobile : +94 777 625 933 <+94%2077%20762%205933> >> +358 449 228 979 >> >> http://soasecurity.org/ >> http://xacmlinfo.org/ >> >> ___ >> Architecture mailing list >> Architecture@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> >> > > > -- > > *Sanjeewa Malalgoda* > WSO2 Inc. > Mobile : +94713068779 <071%20306%208779> > > <http://sanjeewamalalgoda.blogspot.com/>blog :http://sanjeewamalalgoda. > blogspot.com/ <http://sanjeewamalalgoda.blogspot.com/> > > > > ___ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- -- Lahiru Sandaruwan WSO2 Inc., http://wso2.com lean.enterprise.middleware m: +1 901 530 2379 e: lahi...@wso2.com b: https://medium.com/@lahirugmg in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] C5 clustering
Fair enough :) Thanks. On Fri, Dec 22, 2017 at 7:44 AM, Afkham Azeez <az...@wso2.com> wrote: > No we don't encourage distributed caches anymore. As you may have heard "There > are only two hard things in Computer Science: cache invalidation and > naming things. -- Phil Karlton" :) > > So you are supposed to use a product specific DB and if required, a local > cache. > > Thanks > Azeez > > On Fri, Dec 22, 2017 at 7:12 PM, Lahiru Sandaruwan <lahi...@wso2.com> > wrote: > >> Thank you for the clarification Azeez. I believe each product has to >> build or use a library for distributed cache requirements. Isn’t it a >> strong case to have a common way of clustering? >> >> Thanks. >> >> On Fri, Dec 22, 2017 at 3:53 AM Afkham Azeez <az...@wso2.com> wrote: >> >>> There is no such thing as C5 clustering. For each product, clustering >>> would mean a different thing. Some of the core decisions we have made >>> related to multi-tenancy include, each tenant will be running in separate >>> containers/processes and there will be no in-VM multi-tenancy. >>> >>> So when it comes to clustering, you need to refer to the product >>> specific docs. >>> >>> Thanks >>> Azeez >>> >>> On Fri, Dec 22, 2017 at 12:08 PM, Lahiru Sandaruwan <lahi...@wso2.com> >>> wrote: >>> >>>> Hi All, >>>> >>>> Do we have any docs/ details on $subject? >>>> >>>> Thanks. >>>> >>>> -- >>>> -- >>>> >>>> Lahiru Sandaruwan >>>> Associate Technical Lead, >>>> WSO2 Inc., http://wso2.com >>>> >>>> lean.enterprise.middleware >>>> >>>> m: +1 901 530 2379 <+1%20901-530-2379> >>>> e: lahi...@wso2.com b: https://medium.com/@lahirugmg >>>> in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 >>>> >>>> >>> >>> >>> -- >>> *Afkham Azeez* >>> Senior Director, Platform Architecture; WSO2, Inc.; http://wso2.com >>> Member; Apache Software Foundation; http://www.apache.org/ >>> * <http://www.apache.org/>* >>> *email: **az...@wso2.com* <az...@wso2.com> >>> * cell: +94 77 3320919 <077%20332%200919>blog: **http://blog.afkham.org* >>> <http://blog.afkham.org> >>> *twitter: **http://twitter.com/afkham_azeez* >>> <http://twitter.com/afkham_azeez> >>> *linked-in: **http://lk.linkedin.com/in/afkhamazeez >>> <http://lk.linkedin.com/in/afkhamazeez>* >>> >>> *Lean . Enterprise . Middleware* >>> >> -- >> -- >> >> Lahiru Sandaruwan >> Associate Technical Lead, >> WSO2 Inc., http://wso2.com >> >> lean.enterprise.middleware >> >> m: +1 901 530 2379 <+1%20901-530-2379> >> e: lahi...@wso2.com b: https://medium.com/@lahirugmg >> in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 >> >> > > > -- > *Afkham Azeez* > Senior Director, Platform Architecture; WSO2, Inc.; http://wso2.com > Member; Apache Software Foundation; http://www.apache.org/ > * <http://www.apache.org/>* > *email: **az...@wso2.com* <az...@wso2.com> > * cell: +94 77 3320919 <077%20332%200919>blog: **http://blog.afkham.org* > <http://blog.afkham.org> > *twitter: **http://twitter.com/afkham_azeez* > <http://twitter.com/afkham_azeez> > *linked-in: **http://lk.linkedin.com/in/afkhamazeez > <http://lk.linkedin.com/in/afkhamazeez>* > > *Lean . Enterprise . Middleware* > -- -- Lahiru Sandaruwan Associate Technical Lead, WSO2 Inc., http://wso2.com lean.enterprise.middleware m: +1 901 530 2379 e: lahi...@wso2.com b: https://medium.com/@lahirugmg in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] C5 clustering
Thank you for the clarification Azeez. I believe each product has to build or use a library for distributed cache requirements. Isn’t it a strong case to have a common way of clustering? Thanks. On Fri, Dec 22, 2017 at 3:53 AM Afkham Azeez <az...@wso2.com> wrote: > There is no such thing as C5 clustering. For each product, clustering > would mean a different thing. Some of the core decisions we have made > related to multi-tenancy include, each tenant will be running in separate > containers/processes and there will be no in-VM multi-tenancy. > > So when it comes to clustering, you need to refer to the product specific > docs. > > Thanks > Azeez > > On Fri, Dec 22, 2017 at 12:08 PM, Lahiru Sandaruwan <lahi...@wso2.com> > wrote: > >> Hi All, >> >> Do we have any docs/ details on $subject? >> >> Thanks. >> >> -- >> -- >> >> Lahiru Sandaruwan >> Associate Technical Lead, >> WSO2 Inc., http://wso2.com >> >> lean.enterprise.middleware >> >> m: +1 901 530 2379 <+1%20901-530-2379> >> e: lahi...@wso2.com b: https://medium.com/@lahirugmg >> in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 >> >> > > > -- > *Afkham Azeez* > Senior Director, Platform Architecture; WSO2, Inc.; http://wso2.com > Member; Apache Software Foundation; http://www.apache.org/ > * <http://www.apache.org/>* > *email: **az...@wso2.com* <az...@wso2.com> > * cell: +94 77 3320919blog: **http://blog.afkham.org* > <http://blog.afkham.org> > *twitter: **http://twitter.com/afkham_azeez* > <http://twitter.com/afkham_azeez> > *linked-in: **http://lk.linkedin.com/in/afkhamazeez > <http://lk.linkedin.com/in/afkhamazeez>* > > *Lean . Enterprise . Middleware* > -- -- Lahiru Sandaruwan Associate Technical Lead, WSO2 Inc., http://wso2.com lean.enterprise.middleware m: +1 901 530 2379 e: lahi...@wso2.com b: https://medium.com/@lahirugmg in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
[Architecture] C5 clustering
Hi All, Do we have any docs/ details on $subject? Thanks. -- -- Lahiru Sandaruwan Associate Technical Lead, WSO2 Inc., http://wso2.com lean.enterprise.middleware m: +1 901 530 2379 e: lahi...@wso2.com b: https://medium.com/@lahirugmg in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Storing configs in database for C5
can exist at each node which >>>>>>>>>> periodically reads the table(say once a minute) and updates the >>>>>>>>>> config >>>>>>>>>> values in memory. Products communicate with this config library to >>>>>>>>>> get the >>>>>>>>>> values of a given config. So eventually they will read the updated >>>>>>>>>> value in >>>>>>>>>> a short time. If we were to store at least certain configs at DB >>>>>>>>>> level >>>>>>>>>> there are several advantages. >>>>>>>>>> >>>>>>>>>> 1. Eliminate need for a restart for changes to take affect. I >>>>>>>>>> realize in C5 a restart is relatively cheap so this might not be a >>>>>>>>>> big >>>>>>>>>> deal, but you still need someone to initiate the restart after the >>>>>>>>>> config >>>>>>>>>> change. >>>>>>>>>> >>>>>>>>>> 2. Since the config DB table has a known structure a UI can be >>>>>>>>>> easily developed to do CRUD operations for config changes and used >>>>>>>>>> by all >>>>>>>>>> products. This is a lot more user friendly than asking users to >>>>>>>>>> change >>>>>>>>>> files. >>>>>>>>>> >>>>>>>>>> 3. We can provide a REST API to allow config changes to be done >>>>>>>>>> on the DB table alternatively. >>>>>>>>>> >>>>>>>>>> 4. Simplify dev ops by eliminating complicated puppet config >>>>>>>>>> templates that need to constantly maintained with new releases. >>>>>>>>>> >>>>>>>>>> 5. Since configs are in a central DB its easy to manage them >>>>>>>>>> since all nodes will read from the same table. >>>>>>>>>> >>>>>>>>>> 6. Configs can be backed up by simply backing up the table >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Doing this makes sense for certain use cases of API Manger, I'm >>>>>>>>>> sure there maybe similar benefits for other products as well. It may >>>>>>>>>> not >>>>>>>>>> make sense for all configs but at least for some that govern feature >>>>>>>>>> functionality its great to have. WDYT? >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Regards, >>>>>>>>>> Uvindra >>>>>>>>>> >>>>>>>>>> Mobile: 33962 >>>>>>>>>> >>>>>>>>>> ___ >>>>>>>>>> Architecture mailing list >>>>>>>>>> Architecture@wso2.org >>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Sajith Kariyawasam >>>>>>>>> *Associate Tech Lead* >>>>>>>>> *WSO2 Inc.; http://wso2.com <http://wso2.com/>* >>>>>>>>> *Committer and PMC member, Apache Stratos * >>>>>>>>> *AMIE (SL)* >>>>>>>>> *Mobile: 0772269575 <0772269575>* >>>>>>>>> >>>>>>>>> ___ >>>>>>>>> Architecture mailing list >>>>>>>>> Architecture@wso2.org >>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Regards, >>>>>>>> Uvindra >>>>>>>> >>>>>>>> Mobile: 33962 >>>>>>>> >>>>>>>> ___ >>>>>>>> Architecture mailing list >>>>>>>> Architecture@wso2.org >>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Lakmali Baminiwatta >>>>>>> Associate Technical Lead >>>>>>> WSO2, Inc.: http://wso2.com >>>>>>> lean.enterprise.middleware >>>>>>> mobile: +94 71 2335936 >>>>>>> blog : lakmali.com >>>>>>> >>>>>>> >>>>>>> ___ >>>>>>> Architecture mailing list >>>>>>> Architecture@wso2.org >>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Nuwan Dias >>>>>> >>>>>> Software Architect - WSO2, Inc. http://wso2.com >>>>>> email : nuw...@wso2.com >>>>>> Phone : +94 777 775 729 >>>>>> >>>>>> ___ >>>>>> Architecture mailing list >>>>>> Architecture@wso2.org >>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Lakmali Baminiwatta >>>>> Associate Technical Lead >>>>> WSO2, Inc.: http://wso2.com >>>>> lean.enterprise.middleware >>>>> mobile: +94 71 2335936 >>>>> blog : lakmali.com >>>>> >>>>> >>>>> ___ >>>>> Architecture mailing list >>>>> Architecture@wso2.org >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>>> >>>> >>>> >>>> -- >>>> Nuwan Dias >>>> >>>> Software Architect - WSO2, Inc. http://wso2.com >>>> email : nuw...@wso2.com >>>> Phone : +94 777 775 729 >>>> >>>> ___ >>>> Architecture mailing list >>>> Architecture@wso2.org >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> >>> Srinath Perera, Ph.D. >>>http://people.apache.org/~hemapani/ >>>http://srinathsview.blogspot.com/ >>> >>> ___ >>> Architecture mailing list >>> Architecture@wso2.org >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> Nuwan Dias >> >> Software Architect - WSO2, Inc. http://wso2.com >> email : nuw...@wso2.com >> Phone : +94 777 775 729 >> >> ___ >> Architecture mailing list >> Architecture@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Lakmal Warusawithana > Director - Cloud Architecture; WSO2 Inc. > Mobile : +94714289692 > Blog : http://lakmalsview.blogspot.com/ > > > ___ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- -- Lahiru Sandaruwan Associate Technical Lead, WSO2 Inc., http://wso2.com lean.enterprise.middleware m: +94773325954 e: lahi...@wso2.com b: http://lahiruwrites.blogspot.com/ in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Making Suggestions on Apps/ Assets user might be interesting in Enterprise Store using ML
On Fri, Jun 24, 2016 at 11:12 PM, Nirmal Fernando <nir...@wso2.com> wrote: > We do have a recommendation algorithm in ML and we could leverage it here. > Cool. Let's see if we can do this a Gsoc for next year then. Thanks. > > On Sat, Jun 25, 2016 at 7:40 AM, Lahiru Sandaruwan <lahi...@wso2.com> > wrote: > >> Hi, >> >> Have we thought about $subject? Something like "You might also like >> following Apps/Assets". We can use 'favorites' and 'starts' given as >> features. >> >> A common feature most of the stores has today and might be a good for a >> Gsoc project or similar. >> >> Thanks. >> >> -- >> -- >> Lahiru Sandaruwan >> Associate Technical Lead, >> WSO2 Inc., http://wso2.com >> lean.enterprise.middleware >> >> phone: +94773325954 >> email: lahi...@wso2.com blog: http://lahiruwrites.blogspot.com/ >> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 >> >> > > > -- > > Thanks & regards, > Nirmal > > Team Lead - WSO2 Machine Learner > Associate Technical Lead - Data Technologies Team, WSO2 Inc. > Mobile: +94715779733 > Blog: http://nirmalfdo.blogspot.com/ > > > -- -- Lahiru Sandaruwan Associate Technical Lead, WSO2 Inc., http://wso2.com lean.enterprise.middleware m: +94773325954 e: lahi...@wso2.com b: http://lahiruwrites.blogspot.com/ in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
[Architecture] Making Suggestions on Apps/ Assets user might be interesting in Enterprise Store using ML
Hi, Have we thought about $subject? Something like "You might also like following Apps/Assets". We can use 'favorites' and 'starts' given as features. A common feature most of the stores has today and might be a good for a Gsoc project or similar. Thanks. -- -- Lahiru Sandaruwan Associate Technical Lead, WSO2 Inc., http://wso2.com lean.enterprise.middleware phone: +94773325954 email: lahi...@wso2.com blog: http://lahiruwrites.blogspot.com/ linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [Dev] [REST APIs][Analytics] GET request with a payload
Hi all,
POST for filterings is not an issue for special cases, as document also
clearly confirms.
However, I think the decision has to be made on practical use cases. This
use case doesn't looks like a complex one. As Ayoma mention, it is a good
idea to implement two filters to include and exclude.
Considering the practical use, if url length is not a problem(i.e.
practically user will not have a requirement to use around 400 columns per
search, if we average word length to 5), we should go for GET.
Otherwise, we can go for POST.
Thanks.
On Thu, Mar 24, 2016 at 9:01 AM, Sachith Withana <sach...@wso2.com> wrote:
> Hi Gimantha,
>
> I think the point made by Udara is valid.
> Anyways if the user wants to get a selected number of columns, the chances
> are it won't exceed the url limit.
> ( due to the that number being low).
>
> Thanks,
> Sachith
>
> On Thu, Mar 24, 2016 at 2:21 PM, Gimantha Bandara <giman...@wso2.com>
> wrote:
>
>> Hi Sanjeewa,
>>
>> Thank you for the guidelines doc. The exact problem is discussed in 10.2
>> in the above document. We will be filtering the record values in each
>> records by providing the required columns, so only those column values will
>> be returned with each record. According to the document the POST can be
>> used either for updating/creating a resource or for initializing a
>> processing function. In our case we will be simply retrieving records but
>> need to provide a filter for the record values. So from users perspective,
>> it will be doing some processing and returning filtered records.
>>
>> We can actually implement the following url, but we cannot exactly say if
>> it will exceed the url length limit.
>> GET /analytics/tables/{tableName}?columns=column1,column2]
>>
>> Or we can implement something like below,
>>
>> POST /analytics/tables/tableName/
>>
>> {
>> from:
>> to:
>> start:
>> count:
>> columns :[c1,c2,c3]
>> }
>>
>> or
>>
>> POST /analytics/
>>
>> {
>> tableName :
>> from:
>> to:
>> start:
>> count:
>> columns :[c1,c2,c3]
>> }
>>
>> Considering the url length limit, I think the second option is better.
>> WDYT?
>>
>> On Thu, Mar 24, 2016 at 12:33 PM, Sanjeewa Malalgoda <sanje...@wso2.com>
>> wrote:
>>
>>> Hi Gimantha,
>>> Did you refer REST API guidelines document attached in this mail[1] in
>>> architecture mailing list.
>>> When we develop REST APIs please follow that document and if you see
>>> anything missed there please let us know.
>>>
>>> [1][Architecture] REST API Guidelines
>>>
>>>
>>> Thanks,
>>> sanjeewa.
>>>
>>> On Wed, Mar 23, 2016 at 8:01 PM, Gimantha Bandara <giman...@wso2.com>
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>>
>>>> We have a REST API in DAS to retrieve records in a specific table. It
>>>> supports GET method with the following url format.
>>>>
>>>> /analytics/tables/{tableName}/{from}/{to}/{start}/{count}
>>>>
>>>> Sending a GET request to above url will give the records between given
>>>> "from", "to" time range starting from index "start" with "count" page
>>>> size.
>>>>
>>>> Now we need to change the API, so that the user can define the record
>>>> columns/fields he wants. Current API will return the records with all the
>>>> values/columns. To do that, we can allow the user to define the columns he
>>>> needs, in the payload. But it seems that having a payload with a GET is not
>>>> the convention/the best practice.
>>>>
>>>> POST can be used to send the column names as a payload, but here we are
>>>> not making any updates to {tableName} resource. We will be just retrieving
>>>> records using a POST. So it also seems not the convention/the best
>>>> practice.
>>>>
>>>> The only solution I can think of is, having a different resource path
>>>> to get the records with only specified fields/columns. Are there any other
>>>> solutions?
>>>>
>>>> Thanks,
>>>> Gimantha
>>>>
>>>>
>>>> ___
>>>> Dev mailing list
>>>> d...@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
Re: [Architecture] [Dev] [REST APIs][Analytics] GET request with a payload
Yes, if it is possible to put the columns names in the url as Ayoma
mentioned, we must use that(First i thought it is a complex payload you
want to send).
Unless there are limitations, like column list doesn't exceed the url
length limits, we should use GET.
Thanks.
On Wed, Mar 23, 2016 at 3:54 PM, Ayoma Wijethunga <ay...@wso2.com> wrote:
> Hi,
>
> It is true that using GET request with a payload is not the best option.
> Even though it is not strictly prohibited in specs, it can be confusing
> [1]. REST architecture is very open about how we use HTTP methods, but
> thinking in terms of REST architecture, I do not think using POST is also
> the correct approach here [2] (maybe it is just the personal preference).
>
> Let me summaries few examples on how others have addressed the same
> requirement with GET requests.
>
> Facebook Graph API is using "field" query parameter for this [3]. For
> example :
>
> Following Graph API call
> *https://graph.facebook.com/bgolub?fields=id,name,picture
>> <https://graph.facebook.com/bgolub?fields=id,name,picture>* will only
>> return the id, name, and picture in Ben's profile
>>
>
> SharePoint syntax is not very eye candy [4][5], but it goes like :
>
>
>> http://server/siteurl/_vti_bin/listdata.svc/DocumentsOne?$select=MyDocumentType,Title,Id&$expand=MyDocumentType
>>
>
> YouTube API has the same in below form [6] :
>
> Example 1: Retrieve number of items in feed, index of
>> first item in result set, and all entries in the feed:
>> fields=openSearch:totalResults,openSearch:startIndex,entry
>>
>
> LinkedIn has the same [7]
>
>
>> https://api.linkedin.com/v1/people-search:(people:(id,first-name,last-name,positions:(id,title,summary,start-date,end-date,is-current,company:(id,name,type,size,industry,ticker))
>>
>
> IMO Facebook Graph API has the cleanest mechanism.
>
> I believe that if we use a similar format we will not have to introduce
> new resource paths. Instead we'll be able to provide all the columns,
> unless user specifically request limited set of fields with a query
> parameter. WDYT?
>
> [1]
> http://stackoverflow.com/questions/5216567/is-this-statement-correct-http-get-method-always-has-no-message-body
> [2] https://spring.io/understanding/REST
> [3]
> https://developers.facebook.com/docs/graph-api/using-graph-api#fieldexpansion
> [4]
> http://sharepoint.stackexchange.com/questions/118633/how-to-select-and-filter-list-items-lookup-column-with-sharepoint-2013-rest-feat
> [5]
> http://platinumdogs.me/2013/03/14/sharepoint-adventures-with-the-rest-api-part-1/
> [6]
> https://developers.google.com/youtube/2.0/developers_guide_protocol_partial#Fields_Formatting_Rules
> [7] https://developer.linkedin.com/docs/fields?u=0
>
> Best Regards,
> Ayoma.
>
> On Wed, Mar 23, 2016 at 8:13 PM, Lahiru Sandaruwan <lahi...@wso2.com>
> wrote:
>
>> Hi,
>>
>> I think using a POST with a body, for retrieving information is fine
>> considering the requirement. GET with body is not recommended.
>>
>> Thanks.
>>
>> On Wed, Mar 23, 2016 at 2:31 PM, Gimantha Bandara <giman...@wso2.com>
>> wrote:
>>
>>> Hi all,
>>>
>>>
>>> We have a REST API in DAS to retrieve records in a specific table. It
>>> supports GET method with the following url format.
>>>
>>> /analytics/tables/{tableName}/{from}/{to}/{start}/{count}
>>>
>>> Sending a GET request to above url will give the records between given
>>> "from", "to" time range starting from index "start" with "count" page
>>> size.
>>>
>>> Now we need to change the API, so that the user can define the record
>>> columns/fields he wants. Current API will return the records with all the
>>> values/columns. To do that, we can allow the user to define the columns he
>>> needs, in the payload. But it seems that having a payload with a GET is not
>>> the convention/the best practice.
>>>
>>> POST can be used to send the column names as a payload, but here we are
>>> not making any updates to {tableName} resource. We will be just retrieving
>>> records using a POST. So it also seems not the convention/the best practice.
>>>
>>> The only solution I can think of is, having a different resource path to
>>> get the records with only specified fields/columns. Are there any other
>>> solutions?
>>>
>>> Thanks,
>>> Gimantha
>>>
>>>
>>> ___
>>> Architecture mailing li
Re: [Architecture] [REST APIs][Analytics] GET request with a payload
Hi,
I think using a POST with a body, for retrieving information is fine
considering the requirement. GET with body is not recommended.
Thanks.
On Wed, Mar 23, 2016 at 2:31 PM, Gimantha Bandara <giman...@wso2.com> wrote:
> Hi all,
>
>
> We have a REST API in DAS to retrieve records in a specific table. It
> supports GET method with the following url format.
>
> /analytics/tables/{tableName}/{from}/{to}/{start}/{count}
>
> Sending a GET request to above url will give the records between given
> "from", "to" time range starting from index "start" with "count" page
> size.
>
> Now we need to change the API, so that the user can define the record
> columns/fields he wants. Current API will return the records with all the
> values/columns. To do that, we can allow the user to define the columns he
> needs, in the payload. But it seems that having a payload with a GET is not
> the convention/the best practice.
>
> POST can be used to send the column names as a payload, but here we are
> not making any updates to {tableName} resource. We will be just retrieving
> records using a POST. So it also seems not the convention/the best practice.
>
> The only solution I can think of is, having a different resource path to
> get the records with only specified fields/columns. Are there any other
> solutions?
>
> Thanks,
> Gimantha
>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
--
--
Lahiru Sandaruwan
Committer and PMC member, Apache Stratos,
Senior Software Engineer,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
phone: +94773325954
email: lahi...@wso2.com blog: http://lahiruwrites.blogspot.com/
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [APIM][Analytics] Health monitor for APIM as a separate Java client
Hi Maheshakya, On Mon, Feb 15, 2016 at 11:59 AM, Maheshakya Wijewardena < mahesha...@wso2.com> wrote: > Hi, > > After discussing with API analytics team, the health monitor component for > API analytics has been decided to be implemented as a separate java client. > What is the reason for this decision? The load on the APIM server if a stat publishing agent is run? Thanks. > This is essentially a scheduled program which pings the APIs to check > their statuses. > The conventional way of implementing this is by adding it as a scheduled > task in the ESB. But in the point view of deployment, this adds the > complexity of having an ESB just to host the health monitor for APIM. > > What would be the most appropriate solution to implement this health > monitor, considering both the intricacy of deployment and the standards. > > Best regards. > -- > Pruthuvi Maheshakya Wijewardena > mahesha...@wso2.com > +94711228855 > > > > ___ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- -- Lahiru Sandaruwan Committer and PMC member, Apache Stratos, Senior Software Engineer, WSO2 Inc., http://wso2.com lean.enterprise.middleware phone: +94773325954 email: lahi...@wso2.com blog: http://lahiruwrites.blogspot.com/ linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [MSF4j] Creating an archetype for a microservice
map of students inside MicroService class. >>>> Any suggestions on this? >>>> >>>> >>>> Thank you. >>>> >>>> >>>> >>>> -- >>>> >>>> *Manuri Amaya Perera* >>>> >>>> *Software Engineer* >>>> >>>> *WSO2 Inc.* >>>> >>>> *Blog: http://manuriamayaperera.blogspot.com >>>> <http://manuriamayaperera.blogspot.com>* >>>> >>>> ___ >>>> Architecture mailing list >>>> Architecture@wso2.org >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> *Imesh Gunaratne* >>> Senior Technical Lead >>> WSO2 Inc: http://wso2.com >>> T: +94 11 214 5345 M: +94 77 374 2057 >>> W: http://imesh.gunaratne.org >>> Lean . Enterprise . Middleware >>> >>> >> >> -- >> >> *Manuri Amaya Perera* >> >> *Software Engineer* >> >> *WSO2 Inc.* >> >> *Blog: http://manuriamayaperera.blogspot.com >> <http://manuriamayaperera.blogspot.com>* >> >> > > > -- > > *Manuri Amaya Perera* > > *Software Engineer* > > *WSO2 Inc.* > > *Blog: http://manuriamayaperera.blogspot.com > <http://manuriamayaperera.blogspot.com>* > > ___ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- -- Lahiru Sandaruwan Committer and PMC member, Apache Stratos, Senior Software Engineer, WSO2 Inc., http://wso2.com lean.enterprise.middleware phone: +94773325954 email: lahi...@wso2.com blog: http://lahiruwrites.blogspot.com/ linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Security Analytics
Hi Seshi, I think we can consider Authorization stats also. Since WSO2 IS has a good implementation of XACML spec, we can collect stats on, the requests allowed, denied, with which granularity, etc. Thanks. On Mon, Feb 1, 2016 at 1:59 PM, Seshika Fernando <sesh...@wso2.com> wrote: > Hi all, > > 'Security Analytics' is basically providing useful analytics for the WSO2 > Identity Server product through the use of WSO2 DAS. After discussing with > IS guys (Prabath and Johann) we initiated a Security Analytics roadmap and > I'm currently in the process of identifying and detailing the Security > Analytics needs. > > In this process we discovered that security analytics can be dealt in 2 > ways... > >1. Presentation of Identity Analytics - Analyze available identity >data from logs, audit trails etc; and enable users to view results it in >many ways. >2. Adaptive Analytics - Analyze identity data (historical and >realtime) to identify anomalous patterns and feed the decisions back into >the Identity server to enable additional checks > > We will first focus on Presentation of Identity Analytics and the attached > document is a WIP description of the type of analytics we want to have. > > Open for suggestions. > @Johann, @Prabath: Comments are mandatory from you guys. :) > > seshi > > 1. > https://docs.google.com/a/wso2.com/document/d/1qWzo20hrzOXPyoTuyfk9J40agUnvuSK5yNtwmlTZxcU/edit?usp=sharing > > ___ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- -- Lahiru Sandaruwan Committer and PMC member, Apache Stratos, Senior Software Engineer, WSO2 Inc., http://wso2.com lean.enterprise.middleware phone: +94773325954 email: lahi...@wso2.com blog: http://lahiruwrites.blogspot.com/ linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Removing $CARBON_HOME/repository/ directory from C5 onwards
+1. Most of the other servers simply have conf, bin, lib etc. at server home. Thanks. On Thu, Dec 10, 2015 at 9:32 PM, Sameera Jayasoma <same...@wso2.com> wrote: > Hi Folks, > > How about the @Subject? We've introduced repository directory a long time > back to support deploying our product in other Application servers. Now we > don't support that, therefore there is no need to maintain that directory > structure. > > Thanks, > Sameera. > > -- > Sameera Jayasoma, > Software Architect, > > WSO2, Inc. (http://wso2.com) > email: same...@wso2.com > blog: http://blog.sameera.org > twitter: https://twitter.com/sameerajayasoma > flickr: http://www.flickr.com/photos/sameera-jayasoma/collections > Mobile: 0094776364456 > > Lean . Enterprise . Middleware > > > ___ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- -- Lahiru Sandaruwan Committer and PMC member, Apache Stratos, Senior Software Engineer, WSO2 Inc., http://wso2.com lean.enterprise.middleware phone: +94773325954 email: lahi...@wso2.com blog: http://lahiruwrites.blogspot.com/ linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Private PaaS on Cloudstack
Hi Kambiz, WSO2 Private PaaS is based on Apache Stratos. Stratos devs are currently working on Cloudstack support, but not done yet. You can follow d...@stratos.incubator.apache.org and find more details. Thanks. On Fri, Mar 14, 2014 at 3:16 PM, Kambiz Darabi dar...@m-creations.comwrote: Hi, I searched a lot but didn't find any mention of Cloudstack in conjuction with Private PaaS. Given that jclouds supports Cloudstack and that Cloudstack has an AWS compatible API, I wonder whether it is possible to run Private PaaS on Cloudstack. Any pointer to more information is highly appreciated. Thanks in advance Kambiz Kambiz Darabi -- m-creations gmbh Acker 2 55116 Mainz Germany W: http://www.m-creations.com E: dar...@m-creations.com T: +49 6131 6224417 F: +49 6131 6224418 -- Registered Office: Mainz, HRB Mainz 7382 Managing Directors: Frank Pacholak, Kambiz Darabi ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- -- Lahiru Sandaruwan Software Engineer, Platform Technologies, WSO2 Inc., http://wso2.com lean.enterprise.middleware email: lahi...@wso2.com 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 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [Dev] Developer Studio 3.6.0 RC 1 Released!
in the artifiacts.xml file in CApp [TOOLS-2346] - services.xml file not get updated when creating a new Axis2 Service class [TOOLS-2347] - Cannot drop a 'Drop' mediator into switch mediator case or default branches [TOOLS-2349] - [ESB] Custom task properties get serialized for empty property names and values too [TOOLS-2350] - Some Mediators and Endpoints are not in the alphabetical order in the tool pallet [TOOLS-2355] - It is allowing to add Respond and Loopback Mediators inside a mediator when they are already present in the mediator flow [TOOLS-2356] - It is allowing to add Respond and Loopback Mediators in the middle of the mediator flow [TOOLS-2357] - Maven-Car-Depoy-Plugin is unable to undeploy CAR files with Maven [TOOLS-2358] - Icon should change in the warning messages of ESB Graphical Editor [TOOLS-2367] - Maven Build profile properties updated in only endpoint artifact but not all Improvements [TOOLS-1422] - Support both Dynamic Endpoints and Service URIs in Callout mediator [TOOLS-1689] - Usability improvements in the Property fields for ESB Graphical Editor [TOOLS-2277] - Do not allow to add mediators after Respond or Loopback mediator [TOOLS-2326] - In the CallTemplate mediator's properties window, Value/Expression and Parameter Type columns should swap [TOOLS-2353] - Provide a mechanism to define a custom GroupId and a version to be used across all artifacts [TOOLS-2359] - Provide an option to upgrade maven plugin versions when migrating projects between different Developer Studio versions Task [TOOLS-2335] - Increase the priority of Mediator Project (Class Mediator) in Capp artifact ordering Your feedback is most welcome. Please report issues at [3] and specify the affect version as 3.6.0 RC1. [1] - http://builder1.us1.wso2.org/~developerstudio/developer-studio/3.6.0/RC1/wso2-developer-studio_3.6.0.zip [2] - http://builder1.us1.wso2.org/~developerstudio/developer-studio/3.6.0/RC1/Dev-Studio-Pre-installed-Eclipse/ [3] - https://wso2.org/jira/browse/TOOLS Thanks and Regards, WSO2 Developer Studio Team. -- Susinda Perera Software Engineer Mobile:(+94)716049075 WSO2 Inc. http://wso2.com/ Tel : 94 11 214 5345 Fax :94 11 2145300 ___ Dev mailing list d...@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- -- Lahiru Sandaruwan Software Engineer, Platform Technologies, WSO2 Inc., http://wso2.com lean.enterprise.middleware email: lahi...@wso2.com 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 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- -- Lahiru Sandaruwan Software Engineer, Platform Technologies, WSO2 Inc., http://wso2.com lean.enterprise.middleware email: lahi...@wso2.com 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 d...@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Daya Atapattu, Ph.D. Senior Architect, WSO2 Inc. Phone: +94 77 047 4730, +1 203 484 7099 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- *Jasintha Dasanayake * *Software EngineerWSO2 Inc. | http://wso2.com http://wso2.com/ lean . enterprise . middleware* *mobile :- 0711368118 0711368118 * ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- * Aruna Sujith Karunarathna* | Software Engineer WSO2, Inc | lean. enterprise. middleware. #20, Palm Grove, Colombo 03, Sri Lanka Mobile: +94 71 9040362 | Work: +94 112145345 Email: ar...@wso2.com | Web: www.wso2.com ___ Dev mailing list d...@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Kavith Lokuhewage* Software Engineer WSO2 Inc. - http://wso2.com lean . enterprise . middleware Mobile - +9477-9-145-123 | +9471-455-6-401 Linkedin http://www.linkedin.com/pub/kavith-lokuhewage/49/473/419 Twitter https://twitter.com/KavithThiranga ___ Dev mailing list d...@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- -- Lahiru Sandaruwan Software Engineer, Platform Technologies, WSO2 Inc., http://wso2.com
Re: [Architecture] using MB/JMS as the communication mechanism in depsync
Hi Senaka, On Fri, Sep 13, 2013 at 5:17 PM, Senaka Fernando sen...@wso2.com wrote: Hi all, To add to this, there was a concern on the footprint of MB running inside carbon servers. I guess we plan to start the MB only with the Manager node. So will the footprint be still a concern? Thanks. And, as discussed MB+Cassandra is not what's going to be used here, but probably another mode. There will be 3 modes in total: 1. In-memory 2. SQL-DB 3. Cassandra The Embedded-MB will be like an Embedded Registry or AM, and will be a minimal deployment to support basic requirements. Further, MB is not simply used for DepSync but also for several platform-wide requirements and as a part of the unification process we are working on. For example, Notifications will use this too. Thanks, Senaka. On Fri, Sep 13, 2013 at 5:06 PM, Pradeep Fernando prad...@wso2.comwrote: Hi All, During the recent depsync related meeting, the above $subject came up.. here are the some of the discussion points. - Currently our depsync setup uses cluster messages to send the repository sync message - Message loss is a one issue with the current approach. message replaying can be done, but not the proper way to do it. - We can use JMS/MB as the communication mechanism between depsync nodes. - the solution scales well, message persistence is there by default. Approach, - We ship a embedded MB server with our every product. (p2 feature installation is one/server profile/ etc is open for discussion) - manager node starts up the MB server, worker nodes read from it. - LB can load balance across cluster either using static endpoints or can get the endpoint details from the MB itself - LB doe not have to use clustering anymore.. Concerns, How are we going to incoperate these changes to future releases. Deployment is part of the carbon kernel. If we are to implement above there are kernel changes. what is the expected release version, thanks, --Pradeep -- * http://us13.wso2con.com/ * * * *Senaka Fernando* Senior Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- -- Lahiru Sandaruwan Software Engineer, Platform Technologies, WSO2 Inc., http://wso2.com lean.enterprise.middleware email: lahi...@wso2.com 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 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [Stratos2] CLI Tool Improvements
Hi Azeez, I had a chat with PrabathA sometime ago, and got to know that he wrote such a tool(for deployment of artifacts). Not sure where did it end up. May be we can use that as a starting point(of course after this S2 release as Pual mentioned). Thanks. Thanks. On Thu, May 9, 2013 at 10:51 PM, Afkham Azeez az...@wso2.com wrote: It would be good if you could make this a generic CLI tooling framework for Carbon. We need it not only in Stratos 2, but in many other areas. We can provide CLI tooling to deploy artifacts into a server, for example. On Fri, May 10, 2013 at 1:23 AM, Isuru Perera isu...@wso2.com wrote: Hi, For Stratos 2.0 release, we are planning to improve the existing CLI Tool [1]. We are planning to support following features in Stratos2 CLI Tool - Command history [2] - Auto-completion of commands - Character masking (for passwords) [3] For above features, we are planning to use jline2 library [4]. *Existing Design* Currently the CLI tool has two modes. (Stratos2 CLI source can be found at [5]) 1. Interactive Mode - In this mode, user is logged in by passing only username password as arguments. $stratos username password After successful login, the user get a prompt as stratos 2. Single Command Line Mode - In this mode, all the commands are passed as arguments including username and password $stratos username password list This will list all the cartridges. AFAIK, we can support above features only when the CLI tool is in prompt mode. In order to provide auto-complete features at the terminal, we need to use OS specific functions, for example /etc/bash_completion [6] *Drawbacks of existing Beta 2 CLI Tool Possible Solutions* 1. A drawback of existing design is that we have to login every time the stratos command is executed. Solution: Login only once. The back-end service is an admin service and we login as a tenant. I'm thinking of a way to save session in the file system. For example inside user.home/.stratos/ If we can save the session id, then we use the same for authenticate next requests. In this way, the user can use the CLI tool, until the session times out. Or else we can keep the username and password cached (encrypted form). In this way, user can keep using the tool without worrying about the session time out. Which is the better way? 2. Currently the password is entered in the command line itself Solution: With jline2, we can use masking for password input. 3. Command history not support. Solution: jline2 can provide command history. Additionally if we can login only once, user can execute commands directly in terminal and use the history available in the terminal environment. *New Design* I'm going to introduce following commands to the tool 1. $stratos setup This will prompt for Stratos Controller hostname port. These values will be saved in user.home/.stratos/stratos.config 2. $stratos login This will have arguments for username and password. Password will be prompted with masked character. Authentication details will be saved in user.home/.stratos/ 3. $stratos logout Logout user. After successful login, user can go into interactive mode by just entering stratos or user can execute commands in single line. For example stratos list, stratos subscribe etc. CLI Tool will also be improved to use a single '-' for short option names and '--' for longer option names [7]. WDYT? [1] https://wso2.org/jira/browse/SPI-234 [2] https://wso2.org/jira/browse/SPI-111 [3] https://wso2.org/jira/browse/SPI-241 [4] http://jline.github.io/jline2/ [5] https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.1.0/components/stratos/artifact-deployment-coordinator/org.wso2.carbon.adc.mgt.cli/2.1.1 [6] http://www.debian-administration.org/articles/316 [7] https://wso2.org/jira/browse/SPI-240 -- Isuru Perera Senior Software Engineer | WSO2, Inc. | http://wso2.com/ Lean . Enterprise . Middleware Twitter: http://twitter.com/chrishantha | LinkedIn: http://lk.linkedin.com/in/chrishantha/ ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- -- Lahiru Sandaruwan Software Engineer, Platform Technologies, WSO2 Inc., http://wso2.com lean.enterprise.middleware
