Re: [Architecture] [Identity Cloud] Custom theming support for Identity Cloud User Portal

[Dmitry Sotnikov]

In API Cloud's developer portal, we allow custom CSS code, fonts as SVG,
TTF, EOT, WOFF , WOFF2 and OTF files, and images as JPG, PNG, and GIF files.

Sometimes customers do want to go beyond that: for example, remove certain
sections of the site - but we do not have such a capability at the moment.

On Thu, Apr 27, 2017 at 3:23 AM, Ashen Weerathunga  wrote:

> Hi all,
>
> We are in the process of implementing custom theming support for identity
> cloud user portal. This will allow customers to do the following tasks
> based on their preference.
>
>- Change the color theme of the user portal.
>- Change company logo on the header.
>
> Users will be provided a UI to upload and delete themes from the admin
> portal and they need to upload the customized theme as a zip file. Then the
> uploaded theme will be deployed tenant wise in the user portal. The
> wireframe design for the UI can be found at [1][2].
>
> [1]https://github.com/wso2-dev-ux/product-cloud/blob/
> master/Wireframes/identity_cloud/1.2.0/017%20Identity%
> 20Cloud%20-%20Theme%20-%20Upload%20.png
> [2]https://github.com/wso2-dev-ux/product-cloud/blob/
> master/Wireframes/identity_cloud/1.2.0/018%20Identity%
> 20Cloud%20-%20Theme%20-%20after%20adding%20a%20custom%20theme.png
>
> Appreciate any suggestions regarding this.
>
> Thanks,
> Ashen
>
> --
> *Ashen Weerathunga*
> Software Engineer
> WSO2 Inc.: http://wso2.com
> lean.enterprise.middleware
>
> Email: as...@wso2.com
> Mobile: +94716042995 <94716042995>
> LinkedIn: *http://lk.linkedin.com/in/ashenweerathunga
> <http://lk.linkedin.com/in/ashenweerathunga>*
> <http://wso2.com/signature>
>



-- 
Dmitry Sotnikov
VP of Cloud; WSO2, Inc.;  http://wso2.com/
email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov
Lean . Enterprise . Middleware

<http://wso2.com/signature>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Horizontal autoscaling of containers in AppCloud

[Dmitry Sotnikov]

We don't have to have 0 in server-mode operations right now, but we will
have to have this as we transition to serverless. And yes, obviously, this
will have to be done by something different than CPU utilization. :)

On Wed, Nov 2, 2016 at 7:46 PM, Lakmal Warusawithana 
wrote:

>
>
> On Wed, Nov 2, 2016 at 11:27 PM, Dmitry Sotnikov  wrote:
>
>> My point is that for serverless architecture, if load balancer can deal
>> with the "0" situation (no containers are running, requests come in, a
>> container is spun up and gets the request), then 1 also works.
>>
>
> AFAIK, you can't put 0 as min count. (unless we support and send
> upstream). Main reason is autoscaling currently implemented based on CPU
> utilization, if it is 0 you can't calculate it. If we want to do this, we
> should introduce autoscaling factor based on LB queue.
>
>
>
>>
>> 2 as the minimum for HA configuration is a good approach for
>> the server-oriented model.
>>
>> On Wed, Nov 2, 2016 at 10:46 AM, Deependra Ariyadewa 
>> wrote:
>>
>>>
>>>
>>> On Wed, Nov 2, 2016 at 10:22 PM, Dmitry Sotnikov 
>>> wrote:
>>>
>>>> Not for transactional stuff, right? If this is just a mediation or
>>>> proxy service request and the host fails - the request would not
>>>> automatically go to a second node anyway, right?
>>>>
>>>
>>> Load balancer is the entry point to the Integration / AppCloud. If one
>>> replica fails LB can route the request based on the liveness check. This
>>> use case is valid for endpoint need high uptimes.
>>>
>>>>
>>>> On Wed, Nov 2, 2016 at 9:41 AM, Deependra Ariyadewa 
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Wed, Nov 2, 2016 at 9:48 PM, Dmitry Sotnikov 
>>>>> wrote:
>>>>>
>>>>>> Wouldn't minimum be set to 0 in true serverless experience?
>>>>>>
>>>>>
>>>>> Yes, in the initial stage replica count should be 0 but in the running
>>>>> state we have to have two copies of each instance to face server failures.
>>>>>
>>>>>>
>>>>>> On Wed, Nov 2, 2016 at 9:16 AM, Deependra Ariyadewa 
>>>>>> wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Nov 2, 2016 at 1:04 PM, Kasun De Silva 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi All,
>>>>>>>>
>>>>>>>> Past couple of days I was working on a POC for the $subject.
>>>>>>>>
>>>>>>>> Following is the current model that AppCloud use to create
>>>>>>>> application / services. Basically for each application / service 
>>>>>>>> AppCloud
>>>>>>>> will create a *Deployment >> ReplicaSet >> Pod* in Kubernetes
>>>>>>>> cluster. At this point each ReplicaSet created has only one replica 
>>>>>>>> which
>>>>>>>> is a Pod. This deployment does not scale up or scale down under any
>>>>>>>> circumstances.
>>>>>>>>
>>>>>>>> This effort is to bring up a new feature to autoscale the
>>>>>>>> application / service deployed in AppCloud according to certain 
>>>>>>>> metrics.
>>>>>>>>
>>>>>>>> Basically as usual AppCloud will create a *Deployment >> RS >> Pod*
>>>>>>>> in Kubernetes for each application / service created as in above 
>>>>>>>> scenario.
>>>>>>>>
>>>>>>>> With the new feature, user can set auto-scaling parameters in the
>>>>>>>> application settings level. We are using Kubernetes v1.3.4, and by 
>>>>>>>> default
>>>>>>>> it accepts following parameters for *Horizontal Pod Autoscaler*
>>>>>>>> (HPA).
>>>>>>>>
>>>>>>>>1. Minimum # of pods
>>>>>>>>2. Maximum # of pods
>>>>>>>>3. Target CPU Utilization
>>>>>>>>
>>>>>>>>
>>>>>>>> and the autoscaling logic will be following,
>>>>>>>>
>>>>>>>> TargetNumOfP

Re: [Architecture] Horizontal autoscaling of containers in AppCloud

[Dmitry Sotnikov]

My point is that for serverless architecture, if load balancer can deal
with the "0" situation (no containers are running, requests come in, a
container is spun up and gets the request), then 1 also works.

2 as the minimum for HA configuration is a good approach for
the server-oriented model.

On Wed, Nov 2, 2016 at 10:46 AM, Deependra Ariyadewa  wrote:

>
>
> On Wed, Nov 2, 2016 at 10:22 PM, Dmitry Sotnikov  wrote:
>
>> Not for transactional stuff, right? If this is just a mediation or proxy
>> service request and the host fails - the request would not automatically go
>> to a second node anyway, right?
>>
>
> Load balancer is the entry point to the Integration / AppCloud. If one
> replica fails LB can route the request based on the liveness check. This
> use case is valid for endpoint need high uptimes.
>
>>
>> On Wed, Nov 2, 2016 at 9:41 AM, Deependra Ariyadewa 
>> wrote:
>>
>>>
>>>
>>> On Wed, Nov 2, 2016 at 9:48 PM, Dmitry Sotnikov  wrote:
>>>
>>>> Wouldn't minimum be set to 0 in true serverless experience?
>>>>
>>>
>>> Yes, in the initial stage replica count should be 0 but in the running
>>> state we have to have two copies of each instance to face server failures.
>>>
>>>>
>>>> On Wed, Nov 2, 2016 at 9:16 AM, Deependra Ariyadewa 
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Wed, Nov 2, 2016 at 1:04 PM, Kasun De Silva 
>>>>> wrote:
>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> Past couple of days I was working on a POC for the $subject.
>>>>>>
>>>>>> Following is the current model that AppCloud use to create
>>>>>> application / services. Basically for each application / service AppCloud
>>>>>> will create a *Deployment >> ReplicaSet >> Pod* in Kubernetes
>>>>>> cluster. At this point each ReplicaSet created has only one replica which
>>>>>> is a Pod. This deployment does not scale up or scale down under any
>>>>>> circumstances.
>>>>>>
>>>>>> This effort is to bring up a new feature to autoscale the application
>>>>>> / service deployed in AppCloud according to certain metrics.
>>>>>>
>>>>>> Basically as usual AppCloud will create a *Deployment >> RS >> Pod*
>>>>>> in Kubernetes for each application / service created as in above 
>>>>>> scenario.
>>>>>>
>>>>>> With the new feature, user can set auto-scaling parameters in the
>>>>>> application settings level. We are using Kubernetes v1.3.4, and by 
>>>>>> default
>>>>>> it accepts following parameters for *Horizontal Pod Autoscaler*
>>>>>> (HPA).
>>>>>>
>>>>>>1. Minimum # of pods
>>>>>>2. Maximum # of pods
>>>>>>3. Target CPU Utilization
>>>>>>
>>>>>>
>>>>>> and the autoscaling logic will be following,
>>>>>>
>>>>>> TargetNumOfPods = ceil(sum(CurrentPodsCPUUtilization)
>>>>>> / TargetCPUUtilization)
>>>>>>
>>>>>> But target number of pods will be bounded by the values provided for
>>>>>> the MinPods and MaxPods values.
>>>>>>
>>>>>> MinPods <= TargetNumOfPods <= MaxPods
>>>>>>
>>>>>> When user set the auto scale parameters AppCloud will basically
>>>>>> create a Kubernetes HPA kind for the particular appllication / service
>>>>>> version (This is on demand. we do not create an HPA kind for each
>>>>>> application / service version that user creates.). So that HPA for that
>>>>>> particular version will take responsibility of scaling up, scaling down 
>>>>>> of
>>>>>> pods according to the given threshold. Following will be the model that 
>>>>>> we
>>>>>> are using in Kubernetes with the autoscaling feature in AppCloud.
>>>>>>
>>>>>
>>>>> In the server less paradigm user should get a simple application
>>>>> creation user experience, therefore making the auto scaling feature as the
>>>>> default behavior is a good option. Also we have to send the minimum pod
>>>>> count to 2 t

Re: [Architecture] Horizontal autoscaling of containers in AppCloud

[Dmitry Sotnikov]

Wouldn't minimum be set to 0 in true serverless experience?

On Wed, Nov 2, 2016 at 9:16 AM, Deependra Ariyadewa  wrote:

>
>
> On Wed, Nov 2, 2016 at 1:04 PM, Kasun De Silva  wrote:
>
>> Hi All,
>>
>> Past couple of days I was working on a POC for the $subject.
>>
>> Following is the current model that AppCloud use to create application /
>> services. Basically for each application / service AppCloud will create a 
>> *Deployment
>> >> ReplicaSet >> Pod* in Kubernetes cluster. At this point each
>> ReplicaSet created has only one replica which is a Pod. This deployment
>> does not scale up or scale down under any circumstances.
>>
>> This effort is to bring up a new feature to autoscale the application /
>> service deployed in AppCloud according to certain metrics.
>>
>> Basically as usual AppCloud will create a *Deployment >> RS >> Pod* in
>> Kubernetes for each application / service created as in above scenario.
>>
>> With the new feature, user can set auto-scaling parameters in the
>> application settings level. We are using Kubernetes v1.3.4, and by default
>> it accepts following parameters for *Horizontal Pod Autoscaler* (HPA).
>>
>>1. Minimum # of pods
>>2. Maximum # of pods
>>3. Target CPU Utilization
>>
>>
>> and the autoscaling logic will be following,
>>
>> TargetNumOfPods = ceil(sum(CurrentPodsCPUUtilization)
>> / TargetCPUUtilization)
>>
>> But target number of pods will be bounded by the values provided for the
>> MinPods and MaxPods values.
>>
>> MinPods <= TargetNumOfPods <= MaxPods
>>
>> When user set the auto scale parameters AppCloud will basically create a
>> Kubernetes HPA kind for the particular appllication / service version (This
>> is on demand. we do not create an HPA kind for each application / service
>> version that user creates.). So that HPA for that particular version will
>> take responsibility of scaling up, scaling down of pods according to the
>> given threshold. Following will be the model that we are using in
>> Kubernetes with the autoscaling feature in AppCloud.
>>
>
> In the server less paradigm user should get a simple application creation
> user experience, therefore making the auto scaling feature as the default
> behavior is a good option. Also we have to send the minimum pod count to 2
> to support node failures.
>
>>
>> Your thoughts and comments are welcome on this.
>>
>> Thanks,
>> Kasun
>> ​
>> --
>> *Kasun de Silva*
>> Senior Software Engineer | Cloud TG
>>
>> WSO2 Inc <http://wso2.com>*. *|* E*mail : kas...@wso2.com | Mobile: +94
>> 77 794 4260
>>
>>
>
>
> --
> Deependra Ariyadewa
> WSO2, Inc. http://wso2.com/ http://wso2.org
>
> email d...@wso2.com; cell +94 71 403 5996 ;
> Blog http://risenfall.wordpress.com/
> PGP info: KeyID: 'DC627E6F'
>
> *WSO2 - Lean . Enterprise . Middleware*
>



-- 
Dmitry Sotnikov
VP of Cloud; WSO2, Inc.;  http://wso2.com/
email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov
Lean . Enterprise . Middleware

<http://wso2.com/signature>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Horizontal autoscaling of containers in AppCloud

[Dmitry Sotnikov]

Not for transactional stuff, right? If this is just a mediation or proxy
service request and the host fails - the request would not automatically go
to a second node anyway, right?

On Wed, Nov 2, 2016 at 9:41 AM, Deependra Ariyadewa  wrote:

>
>
> On Wed, Nov 2, 2016 at 9:48 PM, Dmitry Sotnikov  wrote:
>
>> Wouldn't minimum be set to 0 in true serverless experience?
>>
>
> Yes, in the initial stage replica count should be 0 but in the running
> state we have to have two copies of each instance to face server failures.
>
>>
>> On Wed, Nov 2, 2016 at 9:16 AM, Deependra Ariyadewa 
>> wrote:
>>
>>>
>>>
>>> On Wed, Nov 2, 2016 at 1:04 PM, Kasun De Silva  wrote:
>>>
>>>> Hi All,
>>>>
>>>> Past couple of days I was working on a POC for the $subject.
>>>>
>>>> Following is the current model that AppCloud use to create application
>>>> / services. Basically for each application / service AppCloud will create 
>>>> a *Deployment
>>>> >> ReplicaSet >> Pod* in Kubernetes cluster. At this point each
>>>> ReplicaSet created has only one replica which is a Pod. This deployment
>>>> does not scale up or scale down under any circumstances.
>>>>
>>>> This effort is to bring up a new feature to autoscale the application /
>>>> service deployed in AppCloud according to certain metrics.
>>>>
>>>> Basically as usual AppCloud will create a *Deployment >> RS >> Pod* in
>>>> Kubernetes for each application / service created as in above scenario.
>>>>
>>>> With the new feature, user can set auto-scaling parameters in the
>>>> application settings level. We are using Kubernetes v1.3.4, and by default
>>>> it accepts following parameters for *Horizontal Pod Autoscaler* (HPA).
>>>>
>>>>1. Minimum # of pods
>>>>2. Maximum # of pods
>>>>3. Target CPU Utilization
>>>>
>>>>
>>>> and the autoscaling logic will be following,
>>>>
>>>> TargetNumOfPods = ceil(sum(CurrentPodsCPUUtilization)
>>>> / TargetCPUUtilization)
>>>>
>>>> But target number of pods will be bounded by the values provided for
>>>> the MinPods and MaxPods values.
>>>>
>>>> MinPods <= TargetNumOfPods <= MaxPods
>>>>
>>>> When user set the auto scale parameters AppCloud will basically create
>>>> a Kubernetes HPA kind for the particular appllication / service version
>>>> (This is on demand. we do not create an HPA kind for each application /
>>>> service version that user creates.). So that HPA for that particular
>>>> version will take responsibility of scaling up, scaling down of pods
>>>> according to the given threshold. Following will be the model that we are
>>>> using in Kubernetes with the autoscaling feature in AppCloud.
>>>>
>>>
>>> In the server less paradigm user should get a simple application
>>> creation user experience, therefore making the auto scaling feature as the
>>> default behavior is a good option. Also we have to send the minimum pod
>>> count to 2 to support node failures.
>>>
>>>>
>>>> Your thoughts and comments are welcome on this.
>>>>
>>>> Thanks,
>>>> Kasun
>>>> ​
>>>> --
>>>> *Kasun de Silva*
>>>> Senior Software Engineer | Cloud TG
>>>>
>>>> WSO2 Inc <http://wso2.com>*. *|* E*mail : kas...@wso2.com | Mobile: +94
>>>> 77 794 4260
>>>>
>>>>
>>>
>>>
>>> --
>>> Deependra Ariyadewa
>>> WSO2, Inc. http://wso2.com/ http://wso2.org
>>>
>>> email d...@wso2.com; cell +94 71 403 5996 ;
>>> Blog http://risenfall.wordpress.com/
>>> PGP info: KeyID: 'DC627E6F'
>>>
>>> *WSO2 - Lean . Enterprise . Middleware*
>>>
>>
>>
>>
>> --
>> Dmitry Sotnikov
>> VP of Cloud; WSO2, Inc.;  http://wso2.com/
>> email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov
>> Lean . Enterprise . Middleware
>>
>> <http://wso2.com/signature>
>>
>
>
>
> --
> Deependra Ariyadewa
> WSO2, Inc. http://wso2.com/ http://wso2.org
>
> email d...@wso2.com; cell +94 71 403 5996 ;
> Blog http://risenfall.wordpress.com/
> PGP info: KeyID: 'DC627E6F'
>
> *WSO2 - Lean . Enterprise . Middleware*
>



-- 
Dmitry Sotnikov
VP of Cloud; WSO2, Inc.;  http://wso2.com/
email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov
Lean . Enterprise . Middleware

<http://wso2.com/signature>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] ESB 5.0 Data Mapper plan - Dynamic schema generation for connectors.

[Dmitry Sotnikov]

ilva
>>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>>> Blog : http://mrmalakasilva.blogspot.com/
>>>
>>> WSO2, Inc.
>>> lean . enterprise . middleware
>>> http://www.wso2.com/
>>> http://www.wso2.com/about/team/malaka-silva/
>>> <http://wso2.com/about/team/malaka-silva/>
>>> https://store.wso2.com/store/
>>>
>>> Save a tree -Conserve nature & Save the world for your future. Print
>>> this email only if it is absolutely necessary.
>>>
>>
>>
>
>
> --
>
> Best Regards,
>
> Malaka Silva
> Senior Technical Lead
> M: +94 777 219 791
> Tel : 94 11 214 5345
> Fax :94 11 2145300
> Skype : malaka.sampath.silva
> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
> Blog : http://mrmalakasilva.blogspot.com/
>
> WSO2, Inc.
> lean . enterprise . middleware
> http://www.wso2.com/
> http://www.wso2.com/about/team/malaka-silva/
> <http://wso2.com/about/team/malaka-silva/>
> https://store.wso2.com/store/
>
> Save a tree -Conserve nature & Save the world for your future. Print this
> email only if it is absolutely necessary.
>



-- 
Dmitry Sotnikov
VP of Cloud; WSO2, Inc.;  http://wso2.com/
email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov
Lean . Enterprise . Middleware

<http://wso2.com/events/>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Log Analyzer Tool logs are displayed in GMT

[Dmitry Sotnikov]

+1

Indeed, showing local (browser) time with clear timezone indication is the
best approach for the UI.

Dmitry
On Jun 13, 2016 9:32 AM, "Ishara Cooray"  wrote:

> With the workaround provided by Sameera, it shows the local TZ as below.
>
> *Welcome to the live log viewer.*
> *Mon Jun 13 2016 09:46:14 GMT+0530 (IST)
> org.wso2.carbon.core.deployment.DeploymentInterceptor*
>
> Ishara Cooray
> Senior Software Engineer
> Mobile : +9477 262 9512
> WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> On Mon, Jun 13, 2016 at 11:47 AM, Sameera Ramasinghe 
> wrote:
>
>> @Ruwan
>>
>> Yah storing in epoch time is correct. But in the thread, it was mentioned
>> that in the DAS, the time is displayed as IST. That time is not relevent to
>> us. That's why I mentioned it is only the log published time to DAS :).
>>
>> On Mon, Jun 13, 2016 at 11:43 AM, Sameera Ramasinghe 
>> wrote:
>>
>>> Hi,
>>>
>>> as a quick work around, in main.js of the livelogviewer, there is a line
>>>
>>> var tempDay = new 
>>> Date(parseInt(obj[i].values._eventTimeStamp)).toUTCString();
>>>
>>>
>>> change it to
>>>
>>> var tempDay = new Date(parseInt(obj[i].values._eventTimeStamp)).toString();
>>>
>>> this will change the timezone to browser time zone.
>>>
>>> On Mon, Jun 13, 2016 at 11:32 AM, Sameera Ramasinghe 
>>> wrote:
>>>
 Hi,

 That IST time-zone showing in the DAS explorer is the time the logs are
 published to the DAS. Not the time contained in the logs. The log times are
 in the "eventimestamp" field as epoch time. So we need to convert this
 epoch time in JS level. I will work on a fix and let you know. If we can
 get the server time zone, we can do as Ruwan said.

 On Mon, Jun 13, 2016 at 11:27 AM, Ruwan Abeykoon 
 wrote:

> Hi All,
> The time zone is something we need on all the Log Analyzer gadgets to
> handle properly, in the same way.
>
> Why we can not get the server time zone in AWS?
>
> What time zone a user is interested while looking at the logs and
> errors. I think it is the server time zone. This is the time the logs are
> being printed in respective carbon.log (if any).
>
>
> Cheers,
> Ruwan
>
> On Mon, Jun 13, 2016 at 11:16 AM, Ishara Cooray 
> wrote:
>
>> (+ architecture)
>>
>>
>> On Mon, Jun 13, 2016 at 10:48 AM, Ishara Cooray 
>> wrote:
>>
>>> In fact, in cloud we cannot get the server time zone as hosted in
>>> AWS. So need to get the Browser Time Zone.
>>>
>>> *@Sameera,*
>>> Can we have this option in Log Analyzer Tool?
>>>
>>> Ishara Cooray
>>> Senior Software Engineer
>>> Mobile : +9477 262 9512
>>> WSO2, Inc. | http://wso2.com/
>>> Lean . Enterprise . Middleware
>>>
>>> On Mon, Jun 13, 2016 at 10:20 AM, Ruwan Abeykoon 
>>> wrote:
>>>
 +1
 This should be based on Server Time Zone rather than Browser Time
 Zone, I guess.
 Or should there be an option to set the TZ as server or Browser ?
 If so all the Log Analyzer gadgets should have the same option.


 Cheers,
 Ruwan

 On Mon, Jun 13, 2016 at 10:02 AM, Ishara Cooray 
 wrote:

> Hi,
>
> In the Log Analyzer tool, the logs are shown with GMT time where
> as in DAS Data Explorer it is shown for me in IST.
>
> So i guess Log Analyzer Tool should show the localized time.
>
> *@Amila,*
> WDUT?
>
> Thanks.
> Ishara Cooray
> Senior Software Engineer
> Mobile : +9477 262 9512
> WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>



 --

 *Ruwan Abeykoon*
 *Associate Director/Architect**,*
 *WSO2, Inc. http://wso2.com  *
 *lean.enterprise.middleware.*

 email: ruw...@wso2.com

>>>
>>>
>>
>
>
> --
>
> *Ruwan Abeykoon*
> *Associate Director/Architect**,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: ruw...@wso2.com
>



 --
 *Sameera Ramasinghe*
 Software Engineer, WSO2 Inc.; http://wso2.com
 mobile: *+94 714489682*

>>>
>>>
>>>
>>> --
>>> *Sameera Ramasinghe*
>>> Software Engineer, WSO2 Inc.; http://wso2.com
>>> mobile: *+94 714489682*
>>>
>>
>>
>>
>> --
>> *Sameera Ramasinghe*
>> Software Engineer, WSO2 Inc.; http://wso2.com
>> mobile: *+94 714489682*
>>
>
>
> ___
> 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/architect

Re: [Architecture] App Factory Tier Implementation

[Dmitry Sotnikov]

It looks like Plans set limits on the number of container specifications -
which is probably a typo or something. Higher plans will likely allow to
have more *instances* (not types) of the containers and probably higher
variety (e.g. Free plan only having the small ones).

Also, after the plans are defined, it makes sense to let users sign-up to
them on Application rather than Organization level. So developers of
Application A pick the limits that work for them - maybe they use Free
because it is a PoC thing, and Application B needs small - because it is a
low traffic internal app, and then Application C needs extra-large because
it is a popular production app.

Plan can have some sort of monthly subscription price, container specs
allowed, max number of instances, maybe other limits (e.g. team size, or
shared storage), and maybe some sort of overage pricing (allowing to get
outside the limits and pay extra).

Dmitry

On Tue, Dec 15, 2015 at 8:48 PM, Nadeeshani Pathirennehelage <
nadeesha...@wso2.com> wrote:

> Hi All,
>
> *​Further clarification of Tier User Stories.*
>
> Appfactoery set up engineer will define the container_specs. As an example
> t2.small with the features CPU 1, memory 2 and memeory 4GB.
> He will also be defining the subscription plans.
>
> Then organizations(Tenants) can subscribe to the plans. Then that tenant
> would get assigned to the free tier. Free tier will allow to choose the
> containers of t2.small, t2.medium, t2.large with maximum of 6 containers
> where the Appfactory controls the maximum number of containers.
>
> So if a container is chosen, the containers that can be selected would
> reduce by one.
> If want tenant can upgrade their plan to paid tier.
>
> Kubernetes Quotas will control the container specs' Resources.
>
> Updated table structure is given below.
>
>
> ​
> ​Thanks,
>
> Nadeeshani.
>
> On Wed, Dec 16, 2015 at 6:41 AM, Imesh Gunaratne  wrote:
>
>> Thanks for the clarifications Kasun!
>>
>> On Tue, Dec 15, 2015 at 5:41 PM, Kasun De Silva  wrote:
>>
>>> Hi Imesh,
>>>
>>> See my comments inline,
>>>
>>>>
>>>>- I can see the term "gear" is used in the tables but it's not
>>>>described. Is this an unit of resources (CPU, memory, disk, etc)? If so 
>>>> how
>>>>do we plan to control that for a cluster of containers?
>>>>
>>>> Yes "Gear" is an unit of resources, but  AFAIU we should not use this
>>> word since openshift already use it.
>>> @Nadeeshani please use "Container Spec" instead for now until we figure
>>> out something better.
>>>
>>>>
>>>>- What would be the entity that a tenant admin would subscribe to?
>>>>Is this a container cluster or a composite container deployment (which
>>>>would have a multiple clusters) or a set of app types?
>>>>
>>>> Tenant would subscribe to a Plan that is the main entity. Plan consist
>>> of a container cluster. He can use this container cluster to do his
>>> deployments.
>>>
>>>>
>>>>- Are we planning to expose an API for billing integration?
>>>>
>>>> Yes, REST API will be provided for billing and subscription plan
>>> applications since we are planning to have payment modules and subscription
>>> modules separate from AF.  (Could be existing Cloudmgt app)
>>>
>>>>
>>>>- Do we have a plan to integrate with an existing billing solution
>>>>to demonstrate billing capabilities?
>>>>
>>>> +1 for this, @AF team WDYT?
>>>
>>> Thanks,
>>> Kasun
>>>
>>> --
>>> *Kasun de Silva*
>>> Software Engineer | *WSO2 Inc.*; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> email   : kas...@wso2.com
>>> mobile : +94 77 794 4260
>>>
>>>
>>
>>
>> --
>> *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
>>
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Pathirennehelage Nadeeshani
> Software Engineering Intern : WSO2 Inc
> Mobile : +94 (0) 716 545223
> nadeesha...@wso2.com
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Dmitry Sotnikov
VP of Cloud; WSO2, Inc.;  http://wso2.com/
email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov
Lean . Enterprise . Middleware

<http://wso2.com/events/>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [AppFactory][GSoC] CLI Tool for App Factory

[Dmitry Sotnikov]

All these proposals sound good to me.
On Sep 15, 2015 10:08 PM, "Anuruddha Premalal"  wrote:

> Hi Dmitry,
>
> On Tue, Sep 15, 2015 at 2:27 AM, Dmitry Sotnikov  wrote:
>
>> For App Cloud scenarios, should we have the executable available for
>> download from Settings? Another alternative is to have both the executable
>> and source code referenced from the corresponding tutorial (which we need
>> to be created by the way :))
>>
>> IMO it's best if we can host the CLI details and installation
> instructions in a separate page, may be in the Docs and point to a
> downloadable url.  Here's how other have done it [1], [2].
>
> And we need it to be preconfigured to run against App Cloud, and make sure
>> it works against the cloud identity system.
>>
>> Yes
>
>> Also, might need to rename the executable for App Cloud - otherwise
>> appfac might not be understood as the name.
>>
>> Perhaps we could use 'appc' ?
>
> [1] https://devcenter.heroku.com/articles/heroku-command
> [2] https://docs.cloudfoundry.org/devguide/installcf/
>
> Dmitry
>>
>> P.S. I loved the video. Great way to present the results of work, and
>> very impressive work creating the CLI tool itself!
>>
>> On Sun, Sep 13, 2015 at 5:51 PM, Fathima Dilhasha > > wrote:
>>
>>> Hi Anuruddha, Manjula & Appfactory team,
>>>
>>> Thanks for all the support you gave to complete this successfully.
>>> +1. I will send a pull request with the necessary updates.
>>>
>>> Thank You.
>>> Regards,
>>> Dilhasha
>>>
>>> Fathima Dilhasha Nazeer <http://lk.linkedin.com/in/dilhasha/>
>>> (M.N.F.Dilhasha)
>>> Undergraduate | Department of Computer Science and Engineering
>>> University of Moratuwa
>>> Sri Lanka
>>>
>>> On Thu, Sep 10, 2015 at 10:42 AM, Manjula Rathnayake 
>>> wrote:
>>>
>>>> Hi Fathima,
>>>>
>>>> +1, Great job on the CLI tool. Lets release it with AF-2.2.0-M5 release
>>>> as Anuruddha mentioned.
>>>>
>>>> thank you.
>>>>
>>>> On Thu, Sep 10, 2015 at 10:39 AM, Anuruddha Premalal <
>>>> anurud...@wso2.com> wrote:
>>>>
>>>>> Hi Fathima,
>>>>>
>>>>> Great work. We are looking forward to merge the CLI tool code the main
>>>>> AppFactory repo.
>>>>>
>>>>> Can you send a pull request with necessary updates?. It's god if you
>>>>> place the code under product-af/modules/tools.
>>>>>
>>>>> Also you'll have to update product distribution scripts and related
>>>>> pom files to build the CLI tool when   building the product. Since this
>>>>> requires GO run-time to build, make sure to add a pre-requisite section to
>>>>> the README.
>>>>>
>>>>> Regards,
>>>>> Anuruddha.
>>>>>
>>>>>
>>>>> On Sat, Aug 22, 2015 at 9:42 AM, Fathima Dilhasha <
>>>>> dilhasha@gmail.com> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I have completed the main requirements for $subject.
>>>>>> You can find a demo for the CLI Tool at [1]
>>>>>> <https://drive.google.com/file/d/0B5jf9n7hxy8YV1VQMTJGZ3ZKeU0/view?usp=sharing>
>>>>>> The presentation can be found at [2]
>>>>>> <https://docs.google.com/presentation/d/1yNojFbikh09V57tMtcoaacyc_17Ev1xQrraQCBxjezY/edit?usp=sharing>
>>>>>> Project Documentation can be found at [3]
>>>>>> <https://docs.google.com/document/d/1bD9ouBR2HeDWQ-bmx7OxKQ9q8Km4u6S6UyqlFx0ASfQ/edit?usp=sharing>
>>>>>>
>>>>>> [1]
>>>>>> https://drive.google.com/file/d/0B5jf9n7hxy8YV1VQMTJGZ3ZKeU0/view?usp=sharing
>>>>>> [2]
>>>>>> https://docs.google.com/presentation/d/1yNojFbikh09V57tMtcoaacyc_17Ev1xQrraQCBxjezY/edit?usp=sharing
>>>>>> [3]
>>>>>> https://docs.google.com/document/d/1bD9ouBR2HeDWQ-bmx7OxKQ9q8Km4u6S6UyqlFx0ASfQ/edit?usp=sharing
>>>>>>
>>>>>> There were few suggestions pointed out during the demo,
>>>>>>  -To make the base url configurable from the tool itself.
>>>>>>  -To add auto-complete functionality.
>>>>>>
>>>>>> I will work on these improvements as an extens

Re: [Architecture] [AppFactory][GSoC] CLI Tool for App Factory

[Dmitry Sotnikov]

Fathima Dilhasha Nazeer <http://lk.linkedin.com/in/dilhasha/>
>>>>>>>> (M.N.F.Dilhasha)
>>>>>>>> Undergraduate | Department of Computer Science and Engineering
>>>>>>>> University of Moratuwa
>>>>>>>> Sri Lanka
>>>>>>>>
>>>>>>>> On Thu, May 7, 2015 at 4:38 AM, Fathima Dilhasha <
>>>>>>>> dilhasha@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Hi Jasintha,
>>>>>>>>>
>>>>>>>>> Thank you for the valuable suggestions. I'll have a look at WSO2
>>>>>>>>> Developer Studio as well.
>>>>>>>>>
>>>>>>>>> Thanks.
>>>>>>>>> Regards,
>>>>>>>>> Dilhasha
>>>>>>>>>
>>>>>>>>> Fathima Dilhasha Nazeer <http://lk.linkedin.com/in/dilhasha/>
>>>>>>>>> (M.N.F.Dilhasha)
>>>>>>>>> Undergraduate | Department of Computer Science and Engineering
>>>>>>>>> University of Moratuwa
>>>>>>>>> Sri Lanka
>>>>>>>>>
>>>>>>>>> On Tue, May 5, 2015 at 9:57 AM, Jasintha Dasanayake <
>>>>>>>>> jasin...@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> Similar functionalities  have been implemented  in the WSO2
>>>>>>>>>> Developer Studio, so you may refer[1] that as well,there you may 
>>>>>>>>>> find some
>>>>>>>>>> useful API calls and logics too.
>>>>>>>>>>
>>>>>>>>>> Thanks and Regards
>>>>>>>>>> /Jasintha
>>>>>>>>>>
>>>>>>>>>> [1] -
>>>>>>>>>> https://github.com/wso2/developer-studio/tree/master/appfactory
>>>>>>>>>>
>>>>>>>>>> On Mon, May 4, 2015 at 5:10 PM, Fathima Dilhasha <
>>>>>>>>>> dilhasha@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> As the initial step, I have come up with the following set of
>>>>>>>>>>> basic functionalities to be implemented for AppFactory CLI tool 
>>>>>>>>>>> considering
>>>>>>>>>>> CLI tools available for other platforms ( similar to App Factory ) 
>>>>>>>>>>> as well.
>>>>>>>>>>>
>>>>>>>>>>> *General Commands*
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>- list supported commands
>>>>>>>>>>>- manage app creation and deletion
>>>>>>>>>>>- list App details
>>>>>>>>>>>- authentication to App Factory (login, logout)
>>>>>>>>>>>- API Management (listing API keys)
>>>>>>>>>>>- Database/Data source management
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> *Application Specific Commands*
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> I think there should be command to list the all application
>>>>>>>>>> first, then should be a command to get information for a select 
>>>>>>>>>> application.
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>- List information about Application
>>>>>>>>>>>- Life Cycle Management for an aplication
>>>>>>>>>>>- Display logs for an application
>>>>>>>>>>>- Manage App versioning
>>>>>>>>>>>- Application User Management
>>>>>>>>>>>- Get Latest Build Info for app
>>>>>>>>>>>
>>>>>>>>>>> This tool will take use of system native shell rather than a
>>>>>>>>>>> separate App Factory specific shell. This approach is expected to 
>>>>>>>>>>> provide
>>>>>>>>>>> better user experience. The tool will be built in 'GO' since it 
>>>>>>>>>>> caters for
>>>>>>>>>>> easy adoption to different OSs with cross compilation support, easy
>>>>>>>>>>> integration of functionalities into system native shell.
>>>>>>>>>>>
>>>>>>>>>>> Your feedback and suggestions on this approach are highly
>>>>>>>>>>> appreciated.
>>>>>>>>>>>
>>>>>>>>>>> Thanks.
>>>>>>>>>>>
>>>>>>>>>>> Regards,
>>>>>>>>>>>
>>>>>>>>>>> Dilhasha
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Fathima Dilhasha Nazeer <http://lk.linkedin.com/in/dilhasha/>
>>>>>>>>>>> (M.N.F.Dilhasha)
>>>>>>>>>>> Undergraduate | Department of Computer Science and Engineering
>>>>>>>>>>> University of Moratuwa
>>>>>>>>>>> Sri Lanka
>>>>>>>>>>>
>>>>>>>>>>> ___
>>>>>>>>>>> Architecture mailing list
>>>>>>>>>>> Architecture@wso2.org
>>>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>>
>>>>>>>>>> *Jasintha Dasanayake*
>>>>>>>>>>
>>>>>>>>>> *Senior Software EngineerWSO2 Inc. | http://wso2.com
>>>>>>>>>> <http://wso2.com/>lean . enterprise . middleware*
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> *mobile :- 0711368118*
>>>>>>>>>>
>>>>>>>>>> ___
>>>>>>>>>> Architecture mailing list
>>>>>>>>>> Architecture@wso2.org
>>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> *Anuruddha Premalal*
>>>>>> Software Eng. | WSO2 Inc.
>>>>>> Mobile : +94710461070
>>>>>> Web site : www.regilandvalley.com
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> *Anuruddha Premalal*
>>> Software Eng. | WSO2 Inc.
>>> Mobile : +94710461070
>>> Web site : www.anuruddha.org
>>>
>>>
>>
>>
>> --
>> Manjula Rathnayaka
>> Associate Technical Lead
>> WSO2, Inc.
>> Mobile:+94 77 743 1987
>>
>
>


-- 
Dmitry Sotnikov
VP of Cloud; WSO2, Inc.;  http://wso2.com/
email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov
Lean . Enterprise . Middleware

<http://wso2.com/events/>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [AppFactory] - Show a progress bar while uploading artifacts

[Dmitry Sotnikov]

+1 for overlay
On Mar 25, 2015 2:56 AM, "Aiyadurai Rajeevan"  wrote:

> Hi Manjula,
>
> Progress bar will be shown once user clicked on the "Upload Application"
> button, That means user has provided all required details(including icon
> image) to upload application.
>
> Thanks & Regards,
> S.A.Rajeevan
> Software Engineer WSO2 Inc
> E-Mail: rajeev...@wso2.com | Mobile : +94776411636
>
> On Wed, Mar 25, 2015 at 3:15 PM, Manjula Rathnayake 
> wrote:
>
>> Hi Rajeevan,
>>
>> +1 for option 4.
>> It is more visible and get the attention of the user to wait until upload
>> is completed. And user can not move into other controls too.
>>
>> One drawback is, user can not upload the image at the same time.
>>
>> thank you.
>>
>>
>> On Wed, Mar 25, 2015 at 1:01 PM, Aiyadurai Rajeevan 
>> wrote:
>>
>>> Hi All,
>>>
>>> I Have been working on Jira [1]
>>>  & [2]
>>>  where we need to show a
>>> progress bar in the up-loadable artifact flow while upload in progress.
>>>
>>> Have had few discussions with  Dhanuka & Dashika and have come up with
>>> below suggestions, screenshot attached in [3].
>>>
>>> 1) Change the choose file functionality in the upload form to upload
>>> files to temp directory and move from temp to deploy location once user
>>> submits the form. Hence, Place the progress bar against the choose file
>>> button, Noted Option 1 as in the attachment [3].
>>>
>>> 2) Keep the existing upload form functionality as it is and place the
>>> progress bar just above to the Upload Application button, Noted as Option 2.
>>>
>>> 3) Place the progress bar on top of the button and disable the button
>>> once upload button clicked, Noted as Option 3
>>>
>>> 4) As of now we use an overlay and a spinner while the upload
>>> in-progress. Replace spinner by progress bar from upload application work
>>> flow, Screenshot attached [4]
>>>
>>> Appreciate your views here please.
>>>
>>> [1]:https://wso2.org/jira/browse/APPFAC-2497
>>> [2]: https://wso2.org/jira/browse/APPFAC-3064
>>> [3]: ProgressBarOptions.png
>>> [4]: ProgressOnOverlay.png
>>>
>>> Thanks & Regards,
>>> S.A.Rajeevan
>>> Software Engineer WSO2 Inc
>>> E-Mail: rajeev...@wso2.com | Mobile : +94776411636
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Manjula Rathnayaka
>> Software Engineer
>> WSO2, Inc.
>> Mobile:+94 77 743 1987
>>
>> ___
>> 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
>
>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] App Factory Performance

[Dmitry Sotnikov]

I would add to that plan working with the registry team on optimizing the
performance from their side. We had huge success doing that for API Cloud -
told GReg team which query was too slow and why and they created a fix that
helped us.

Dmitry

On Fri, Mar 13, 2015 at 2:28 AM, Gayan Dhanushka  wrote:

> Hi all,
>
> I have been working on improving the performance in the user home page as
> a result of the above findings.
>
> *Getting all applications of the user from the back end only when users
> are added to new applications*
>
> I have removed getting all applications of the user when the user home
> page is accessed after a certain period of time. Getting the whole
> application list of a particular user needs multiple calls to read rxts and
> particular information like the branch count from the runtime database.
> Hence this is a very costly operation. Therefore I have introduced a cache
> in the back end so that whenever a user is added to a newly created
> application the cache entry is created. So whenever the user home page is
> loaded first this cache will be searched for that particular user and
> unless the used exists in the cache application home data will not be
> loaded from the rxts and the runtime database.
>
> *Introducing a ApplicationSummary object*
>
> Up until now we had a ApplicationInfoBean object which contained all the
> data I have created a new ApplicationSummary object which contains only the
> applicationName, applicationKey and applicationType which are the only
> attributed that is needed to populate the user home page. By doing this the
> database calls to retrieve the branch count is removed. These database
> calls were made while retrieving information for each application.
> Therefore this would make a considerable improvement when it comes to users
> with a number of applications.
>
> Furthermore I am +1 for removing the application creation status from the
> database as well since it can be ignored when retrieving user home
> information. The only use case that I can think of it is that when some one
> creates an application and if he immediately logs out and logs in. This is
> very unlikely to happen. Please share your thoughts about this.
>
> Regards
> Gayan
>
>
>
> On Fri, Mar 13, 2015 at 11:58 AM, Dimuthu Leelarathne 
> wrote:
>
>> Hi all,
>>
>> In our efforts to improve performance this is going to be our approach.
>>
>> *BE Performance* - We are going to keep profiling and improving the BE
>> performance. This includes registry and db access. So the idea is to cache
>> data in session when applicable and cache data at Carbon cache layer when
>> applicable.
>>
>> As a start we have profiled the user home data. I am attaching java
>> profiler snapshot. And as a result Gayan is working on  put app home data
>> to session and clear it when the user is invited to the app (happen over
>> the cluster). Likewise we'll keep on profiling and caching appropriately
>> when it is applicable/appropriate. Even though registry is aching rxts,
>> accessing it is costly at times. We'll keep updating architecture@ and
>> dev@ with our efforts.
>>
>> *FE Performance* - Next step is to use browser local cache with web
>> sockets when applicable. Nginx is supporting web sockets. For example we
>> can cache the Application object in the browser cache whenever app home is
>> loaded and keep updating certain fields via web sockets. As discussed with
>> the UI team we'll be writing a generic layer to do that.
>>
>> thanks,
>> dimuthu
>>
>> --
>> Dimuthu Leelarathne
>> Architect & Product Lead of App Factory
>>
>> WSO2, Inc. (http://wso2.com)
>> email: dimut...@wso2.com
>> Mobile : 0773661935
>>
>> Lean . Enterprise . Middleware
>>
>
>
>
> --
> Gayan Dhanuska
> Software Engineer
> http://wso2.com/
> Lean Enterprise Middleware
>
> Mobile
> 071 666 2327
>
> Office
> Tel   : 94 11 214 5345
> Fax  : 94 11 214 5300
>
> Twitter : https://twitter.com/gayanlggd
>



-- 
Dmitry Sotnikov
VP of Cloud; WSO2, Inc.;  http://wso2.com/
email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov
Lean . Enterprise . Middleware

<http://wso2.com/events/>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Fwd: [AppFactory] Integrating JIRA for projects on WSO2 Cloud

[Dmitry Sotnikov]

What happens if they already have a JIRA project? E.g. they have an
existing project and are using JIRA, and then decide to start using AF.
They can import the source code - e.g. from Github - but for JIRA they
would have to start from scratch?

This might be a bit of an edge case that we can address later. I am not
sure how many users will want that. But for sure something to keep in mind
and implement at some point in the future.

Dmitry

On Fri, Feb 27, 2015 at 4:18 AM, Fathima Dilhasha  wrote:

> I had a meeting with Anuruddha regarding $subject and following were
> discussed.
>
> 1. Create a project on JIRA when user creates a project on appfactory.
> (Evaluate the best way to do it either via Soap or by writing a REST API
> plugin)
>
> 2. Create a class diagram for the component dealing with issue tracking
> (org.wso2.carbon.appfactory.issuetracking) and extend it to add JIRA issue
> connector as well
>
> 3. "IssueTrackerConnector" class needs to be replaced with an interface,
> which decides on the implementation depending on particular issue tracker
> type (default, jira, ..etc) selected by the user
>
> 4. Currently, the issue tracker connector configurations are loaded from
> appfactory.xml. But this is not suitable for the cloud since this restricts
> all the tenants to same set of issue trackers, repositories etc.
> This needs to be changed to allow storing tenant specific preferences to a
> database and load configurations from database in future.
>
> Please give your opinions regarding above suggestions.
>
> Thanks.
>
> Regards,
> Dilhasha
>
>
>
> *M.N.F. Dilhasha*
> Software Engineering Intern | *WSO2 Lanka*
>
> email   :
> *dilha...@wso2.com *mobile : +94 77 8449321
>
> On Wed, Feb 18, 2015 at 10:08 AM, Fathima Dilhasha 
> wrote:
>
>> Hi,
>>
>> Thanks Dimuthu. I'll have a look.
>>
>> Regards,
>> Dilhasha
>>
>> *M.N.F. Dilhasha*
>> Software Engineering Intern | *WSO2 Lanka*
>>
>> email   :
>> *dilha...@wso2.com *mobile : +94 77 8449321
>>
>> On Wed, Feb 18, 2015 at 9:02 AM, Dimuthu Leelarathne 
>> wrote:
>>
>>> Hi,
>>>
>>> I suggested to shift focus to self service mode for configuring JIRA
>>> because I believe that is more Cloud friendly. But architecturally we
>>> should have proper class structure to make it reusable.
>>>
>>> Please take a look at OSLC spec as well.
>>>
>>> Thanks,
>>> Dimuthu
>>> On Feb 18, 2015 7:26 AM, "Fathima Dilhasha"  wrote:
>>>
>>>>
>>>> *M.N.F. Dilhasha*
>>>> Software Engineering Intern | *WSO2 Lanka*
>>>>
>>>> email   :
>>>> *dilha...@wso2.com *mobile : +94 77 8449321
>>>>
>>>> -- Forwarded message --
>>>> From: Fathima Dilhasha 
>>>> Date: Wed, Feb 18, 2015 at 7:25 AM
>>>> Subject: Re: [Architecture] [AppFactory] Integrating JIRA for projects
>>>> on WSO2 Cloud
>>>> To: Dmitry Sotnikov 
>>>>
>>>>
>>>> Hi,
>>>>
>>>> Thanks for the feedback Dmitry.
>>>>
>>>> Yeah we would need to synchronize version numbers and branch labels.
>>>> The existing issue tracker gives that option when user creates an issue. We
>>>> can allow the same feature for JIRA issues.
>>>>
>>>> Dimuthu also pointed that we should give user the option to configure
>>>> JIRA or use the existing issue tracker. When he configures he would be able
>>>> to pull in data from an existing JIRA project or we can create a new JIRA
>>>> project for him.
>>>>
>>>> AFAIK, JIRA  supports access via OAuth. So, we should be able to pull
>>>> data.
>>>>
>>>> Thanks.
>>>>
>>>> Dilhasha
>>>>
>>>> *M.N.F. Dilhasha*
>>>> Software Engineering Intern | *WSO2 Lanka*
>>>>
>>>> email   :
>>>> *dilha...@wso2.com *mobile : +94 77 8449321
>>>>
>>>> On Wed, Feb 18, 2015 at 5:40 AM, Dmitry Sotnikov 
>>>> wrote:
>>>>
>>>>> Would also need to synchronize version numbers in JIRA with Branch
>>>>> labels in AF, right?
>>>>>
>>>>> Plus, pull in stats on the number of issues, and either pull in data
>>>>> on JIRAs and render inside AF or find another way to "embed" JIRA. Not 
>>>>> sure
>>>>> if it possible to do any sort of federation/SSO

Re: [Architecture] [AppFactory] Integrating JIRA for projects on WSO2 Cloud

[Dmitry Sotnikov]

Would also need to synchronize version numbers in JIRA with Branch labels
in AF, right?

Plus, pull in stats on the number of issues, and either pull in data on
JIRAs and render inside AF or find another way to "embed" JIRA. Not sure if
it possible to do any sort of federation/SSO.

Dmitry

On Mon, Feb 16, 2015 at 11:09 PM, Fathima Dilhasha 
wrote:

> Hi everyone,
>
> Please give your opinions on the following features for the first cut.
>
> *Basic requirements :*
>
>
>- When a project is created on cloud, a project is created on the JIRA
>instance.
>- Anyone who has access to the project gets access to above project on
>JIRA
>- Owner of the application can restrict selected users from accessing
>the JIRA issues related to the project
>- When the project is deleted from cloud, the related project on JIRA
>needs to be deleted
>
> Regards,
> Dilhasha
>
> *M.N.F. Dilhasha*
> Software Engineering Intern | *WSO2 Lanka*
>
> email   :
> *dilha...@wso2.com *mobile : +94 77 8449321
>
> On Tue, Feb 17, 2015 at 12:34 PM, Fathima Dilhasha 
> wrote:
>
>> Hi Rajeevan,
>>
>> Thanks for the valuable feedback. I'll go through the code and see.
>>
>> Regards,
>> Dilhasha
>>
>>
>> *M.N.F. Dilhasha*
>> Software Engineering Intern | *WSO2 Lanka*
>>
>> email   :
>> *dilha...@wso2.com *mobile : +94 77 8449321
>>
>> On Tue, Feb 17, 2015 at 11:48 AM, Aiyadurai Rajeevan 
>> wrote:
>>
>>> Hi Dilasha,
>>>
>>> +1 for the proposal.
>>>
>>> IMO, Addition to the above architecture you might have to think about
>>> how you are going to give access to the team for a created project in Jira.
>>> As you aware the app owner/admin can invite team members. So, Eventually
>>> those team members should get the access to that application.
>>>
>>> And you shall obviously think about below tasks.
>>> 1. Deleting an application from Jira
>>> 2. Removing the team members from Jira for an App
>>>
>>> Below [1] code would help for app creation.
>>>
>>> https://bitbucket.org/doklovic_atlassian/atlassian-beer-supply/src/master/src/main/java/com/example/beersupply/components/BeerSupplyProjectCreator.java?at=master
>>>
>>> Thanks & Regards,
>>> S.A.Rajeevan
>>> Software Engineer WSO2 Inc
>>> E-Mail: rajeev...@wso2.com | Mobile : +94776411636
>>>
>>> On Tue, Feb 17, 2015 at 7:47 AM, Fathima Dilhasha 
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> Following is what I have figured out so far regarding $Subject.
>>>>
>>>> REST API for JIRA [1] can be used to get any data related to a JIRA
>>>> instance. I tried creating a JIRA account on cloud and accessed it via REST
>>>> API call using Curl from terminal. I tried for a local instance of JIRA as
>>>> well.
>>>>
>>>> These API calls successfully returned results in JSON format, which can
>>>> be used to render the relevant data.
>>>>
>>>> *For example:*
>>>>
>>>> API call to get all the dashboards available in my JIRA instance,
>>>> returned a JSON object which included URLs of each dashboard.
>>>>
>>>> So the dashboards can be rendered using the URL.
>>>>
>>>>
>>>> *Next Steps:*
>>>>
>>>>
>>>>- Figure out how to create a project in JIRA, when user creates a
>>>>project on the cloud. (I think I can use a similar aproach as creation 
>>>> of
>>>>git repository)
>>>>- Access REST API via java or JavaScript to get relevant details
>>>>- Test all the functionality against a test jaggery app (or a java
>>>>project)
>>>>    - Port that functionality into appmgt
>>>>
>>>>
>>>> I highly appreciate your feedback on this approach or suggestions on a
>>>> better approach.
>>>>
>>>> [1]  https://docs.atlassian.com/jira/REST/latest/#d2e86
>>>>
>>>>
>>>> Thanks.
>>>>
>>>> Dilhasha
>>>>
>>>> *M.N.F. Dilhasha*
>>>> Software Engineering Intern | *WSO2 Lanka*
>>>>
>>>> email   :
>>>> *dilha...@wso2.com *mobile : +94 77 8449321
>>>>
>>>> ___
>>>> 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
>>>
>>>
>>
>


-- 
Dmitry Sotnikov
VP of Cloud; WSO2, Inc.;  http://wso2.com/
email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov
Lean . Enterprise . Middleware

<http://wso2.com/events/>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Developing appmgt Jaggery app using App Cloud by AF team

[Dmitry Sotnikov]

Can you use Codenvy to run and debug there (provided that the runtime used
by Codenvy works within the context of your tenant and has the required
backend server)?

Dmitry

On Mon, Jan 5, 2015 at 8:59 PM, Dimuthu Leelarathne 
wrote:

> Hi all,
>
> I am trying to see the possibility of doing that in the cloud. Here is the
> user story,
>
> - As a developer I should be able to able code using Codevny
> - Test my changes in a runtime
> - Once I am happy with my changes merge it to the main branch
>
> So here is the workflow
>
> - I will fork from master repo and code using Codevny/Dev Studio
> - Then test it on my machine or a preferred setup. This is by pulling from
> the S2-GitBlit
> - Once I am happy with the result merge it to branch
>
> In order to achieve this we need following functionalities,
> - Fork repos
> - Fork repo building
> - Auto deployment of fork repo
> - Merging
>
> But right now we don't have Auto deployment for forked repos. So I will do
> a feasibility check on this and update the thread.
>
> thanks,
> dimuthu
> --
> Dimuthu Leelarathne
> Architect & Product Lead of App Factory
>
> WSO2, Inc. (http://wso2.com)
> email: dimut...@wso2.com
> Mobile : 0773661935
>
> Lean . Enterprise . Middleware
>



-- 
Dmitry Sotnikov
VP of Cloud; WSO2, Inc.;  http://wso2.com/
email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov
Lean . Enterprise . Middleware

<http://wso2.com/events/>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] ESB Recipes for iPaaS - Last meeting notes/updates

[Dmitry Sotnikov]

Why not go away from food analogy and just use regular computer science
terms?

You have *Tasks* that are scheduled/running ("Jobs" is another
alternative). E.g.:

*Tasks:*

  *Task*

*Schedule*

*Next Execution*

*Last Execution*

*Last Result*

*Send daily tweet report*

*Daily, 8:00 PST*

10/11/14 8:00 PST

*10/10/14 8:00 PST*

*Sent email with 54 tweets*

*Deals to Netsuite*

*Not scheduled*

Not scheduled

*10/10/14 11:05 PST*

*1 object created*

(Hyperlinks taking to Task details/editing, Schedule modification, Logs of
last execution, List of created/modified objects)

Tasks are based on *Templates*. So when you want to add a new Task, the
product lets you browse the Templates available (e.g. "All your tweets in
Google Spreadsheet", etc.)

There are no ingredients - you just configure the task based on a template.
You might need to call them Inputs and Outputs. Or maybe you do not need
terminology here at all since the UI shows the data flow graphically.

Rename Deploy to Schedule to match task terminology.

*Connections* seem to be fine and well understood.

Tasks can also be based on ESB artifacts - in which case user uploads the
files generated by Dev Studio.

Let's not make people think and learn new terminology.

Also, note that the UI needs to fit into WSO2 Cloud pages - so will have
the same top menu shared with other services. So logout, etc. - are from
there:
[image: Inline image 1]

Finally, what is the timeline of this development effort?

When will we be able to deploy in in WSO2 Cloud?

Dmitry

On Sun, Oct 5, 2014 at 8:53 PM, Dhanuka De Silva  wrote:

> Hi All
>
> Here's the list of changes discussed during our last meeting;
>
>
> 1. A way to create a new connection if no connections are available
> 2. Set properties to be renamed to "*Set Parameters*"
> 3. Example to be corrected (renaming spreadsheet extension from *doc* to
> *gsheet*)
> 4. Multiple connections with same connector to be labeled meaningfully for
> better separation/ identification (eg:- Twiter-My Account, Twitter-My
> FriendsAccount .. etc etc)
> 5. My dishes - Add last run time stamp/no of run cycles
> 6. Connection specific page needed.
> 7. Connections details - Display Last used/TPS rate.
> 8. A hidden/trigger-able menu to appear in the Recipe Store so the users
> can show/hide
> 9. My Dishes to be renamed to "*My Cafe*". This item is open for
> suggestions  :)
> 10. Create a dish button to appear on My Cafe if no dishes are created. -
> Need to finalize the workflow for this button
> 11. Once logged in, take the user to the *My Cafe*.
> 12. *Assumption* : Maximum dishes a user will have is 5-10
>
> Feel free to add anything if you think that I have missed during our last
> meeting;
>
> *Pls note that the wireframes are also updated *(check the link below)*
> based on above discussion points. *
>
>
> https://dhanuka-wso2.mybalsamiq.com/projects/ipaas/prototype/Store%20-%20Landing%20Page?key=3ee248badbc234bdf3206ccc03c098f1bf584261
>
> *Next Steps:*
> I will be getting my github location mapped today and then getting into
> actual design changes/theming.
>
> Will keep you guys posted on progress;
>
>
> --
> Dhanuka De Silva
> m: +94 773 887816
> e: dhanu...@wso2.com
> w: http://www.wso2.com
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Dmitry Sotnikov
VP of Cloud; WSO2, Inc.;  http://wso2.com/
email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov
Lean . Enterprise . Middleware

<http://wso2.com/events/>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] API Manager - Self Signup for tenant's API Store

[Dmitry Sotnikov]

Perfect! Thanks Chamila!

Dmitry

On Wed, Oct 1, 2014 at 8:33 PM, Chamila Adhikarinayake 
wrote:

> Hi Dmitry,
> This feature is already done and we ship this with APIM 1.8. Sorry for not
> updating this thread.
>
> Regarding the scenarios, We have provided facility to add custom workflow
> extension. Currently we ship UserSignUpWSWorkflowExecutor which also has a
> user approval process [1]. We can also create custom workflow extension to
> suit the scenario mentioned and plug them in. We can also deploy scenario
> as a business process in WSO2 BPS and connect using our
> UserSignUpWSWorkflowExecutor.
>
> [1] https://docs.wso2.com/display/AM170/Adding+a+User+Signup+Workflow
>
> Thanks,
> Chamila.
>
> On Thu, Oct 2, 2014 at 3:05 AM, Dmitry Sotnikov  wrote:
>
>> Any update on that?
>>
>> What is the ETA for the feature?
>>
>> Is there something we can review yet?
>>
>> Were you able to satisfy all the end-user experience requirements?
>>
>> Dmitry
>>
>> On Fri, Sep 5, 2014 at 10:09 AM, Dmitry Sotnikov  wrote:
>>
>>> Thanks Chamila!
>>>
>>> Here is the workflow that I would like to see in the API Cloud:
>>>
>>> Scenario A: User Self Sign-Up:
>>>
>>> 1. Plato is an app developer and  wants to develop an app for the
>>> population of the Atlantis island to track the water level and notify when
>>> the island goes under the sea. He finds that gods have set up a website
>>> with the developer program: apis.atlantisisland.gr and goes to the site
>>> to read about the APIs.
>>> 2. When browsing the API Store at some point Plato tries to access
>>> functionality which requires authentication (e.g. Subscribe to an API),
>>> 3. Plato is presented to choice to log in or sign-up,
>>> 4. If Plato clicks Sign Up, he is asked provide his email address.
>>> 5. Plato provides his gmail address,
>>> 6. He gets an email inviting him to join the Atlatis developer program
>>> with a one-time link that takes him to the Store, asks him to specify and
>>> confirm new password.
>>> 7. Plato is now logged into the Atlastic API Store, and can perform all
>>> activity there.
>>> 8. Plato has Subscriber role - so he cannot actually go to Atlatis API
>>> Publisher, etc.
>>>
>>> Possible variations of that:
>>>
>>> Scenario B: Approval is required: Zeus is the administrator of the API
>>> program and gets a request to approve Plato's membership. In this case,
>>> this needs to be properly communicated to both Zeus and Plato, so they know
>>> what is going on, what is expected of them, current status, etc.
>>>
>>> Scenario C: Zeus actually wants to invite Plato to the development
>>> program: Zeus goes to the corresponding UI, provides Plato's email address,
>>> and Plato receives email with the invitation and one-time link (obviously
>>> approvals are not required in this case.)
>>>
>>> Scenario D:
>>> 1. Homer decides to also write an Atlatis app, and wants to sign-up.
>>> 2. When he tries to sign-up he gets notified that he already has an
>>> account from WSO2 which he used for his Trojan app and which he can reuse.
>>>
>>> All the emails that get sent need to be brandable by the tenant
>>> administrators so when Troy have their API program, Trojan emails look
>>> different from the ones for Atlantis.
>>>
>>> I understand that some of these steps will be different in the cloud and
>>> in on-premise API Manager because of the custom authentication. You will
>>> need to discuss with the cloud team to make sure that the implementation is
>>> compatible, etc.
>>>
>>> I hope this helps. :)
>>>
>>> Dmitry
>>>
>>>
>>> On Thu, Sep 4, 2014 at 11:09 PM, Chamila Adhikarinayake <
>>> chami...@wso2.com> wrote:
>>>
>>>> looping Dmitry to the thread
>>>>
>>>>
>>>> On Fri, Sep 5, 2014 at 10:26 AM, Chamila Adhikarinayake <
>>>> chami...@wso2.com> wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> The current user signup method (jsFunction_addUser() [1]) in API
>>>>> manager uses addUser method in UserRegistrationService[2] (through
>>>>> UserRegistrationAdminService from APIM) to register the user and suggested
>>>>> to use that same method for tenant user signup as well (Shariq has 
>>>>> modified
>>>>> this so that t

Re: [Architecture] API Manager - Self Signup for tenant's API Store

[Dmitry Sotnikov]

Any update on that?

What is the ETA for the feature?

Is there something we can review yet?

Were you able to satisfy all the end-user experience requirements?

Dmitry

On Fri, Sep 5, 2014 at 10:09 AM, Dmitry Sotnikov  wrote:

> Thanks Chamila!
>
> Here is the workflow that I would like to see in the API Cloud:
>
> Scenario A: User Self Sign-Up:
>
> 1. Plato is an app developer and  wants to develop an app for the
> population of the Atlantis island to track the water level and notify when
> the island goes under the sea. He finds that gods have set up a website
> with the developer program: apis.atlantisisland.gr and goes to the site
> to read about the APIs.
> 2. When browsing the API Store at some point Plato tries to access
> functionality which requires authentication (e.g. Subscribe to an API),
> 3. Plato is presented to choice to log in or sign-up,
> 4. If Plato clicks Sign Up, he is asked provide his email address.
> 5. Plato provides his gmail address,
> 6. He gets an email inviting him to join the Atlatis developer program
> with a one-time link that takes him to the Store, asks him to specify and
> confirm new password.
> 7. Plato is now logged into the Atlastic API Store, and can perform all
> activity there.
> 8. Plato has Subscriber role - so he cannot actually go to Atlatis API
> Publisher, etc.
>
> Possible variations of that:
>
> Scenario B: Approval is required: Zeus is the administrator of the API
> program and gets a request to approve Plato's membership. In this case,
> this needs to be properly communicated to both Zeus and Plato, so they know
> what is going on, what is expected of them, current status, etc.
>
> Scenario C: Zeus actually wants to invite Plato to the development
> program: Zeus goes to the corresponding UI, provides Plato's email address,
> and Plato receives email with the invitation and one-time link (obviously
> approvals are not required in this case.)
>
> Scenario D:
> 1. Homer decides to also write an Atlatis app, and wants to sign-up.
> 2. When he tries to sign-up he gets notified that he already has an
> account from WSO2 which he used for his Trojan app and which he can reuse.
>
> All the emails that get sent need to be brandable by the tenant
> administrators so when Troy have their API program, Trojan emails look
> different from the ones for Atlantis.
>
> I understand that some of these steps will be different in the cloud and
> in on-premise API Manager because of the custom authentication. You will
> need to discuss with the cloud team to make sure that the implementation is
> compatible, etc.
>
> I hope this helps. :)
>
> Dmitry
>
>
> On Thu, Sep 4, 2014 at 11:09 PM, Chamila Adhikarinayake  > wrote:
>
>> looping Dmitry to the thread
>>
>>
>> On Fri, Sep 5, 2014 at 10:26 AM, Chamila Adhikarinayake <
>> chami...@wso2.com> wrote:
>>
>>> Hi all,
>>>
>>> The current user signup method (jsFunction_addUser() [1]) in API manager
>>> uses addUser method in UserRegistrationService[2] (through
>>> UserRegistrationAdminService from APIM) to register the user and suggested
>>> to use that same method for tenant user signup as well (Shariq has modified
>>> this so that tenant-wise roles can be taken from the registry and assign
>>> them to the tenant user ). But with that modification, This method cannot
>>> be used for tenant signup with the current user signup workflow in the api
>>> manager.
>>>
>>> When signing up an user to super user store, first add a user by calling
>>> adduser method (from this method, user is assigned with default
>>> internal/identity role from UserRegistrationService) and then follow the
>>> signup workflow and finally add the role to that user. In the signup
>>> workflow, user approval process is managed and till then the user cannot
>>> log in.  But when addUser method is called for tenant signup, a tenant user
>>> is created and all his roles are assigned to him at the creation point. As
>>> a result, second point (approval process) cannot be done. (user can log in
>>> before the approval process is done). As a result,  method to assign roles
>>> by using '/_system/governance/repository/identity/sign-up-config'
>>> (mentioned in 'User roles for tenants' in my first mail ) cannot be used in
>>> this case.
>>>
>>> *Modified method to add user roles for tenants*
>>>
>>> As a result of above mentioned problem, a registry entry in
>>> /_system/governance/repository/identity/sign-up-config won't be created as
>>> mentioned in the first 

Re: [Architecture] BAM Log monitoring for Cloud

[Dmitry Sotnikov]

Gimantha,

The important pieces of functionality from my perspective (also, including
Amila, Dimuthu, and Majula - they are using current non-BAM workaround so
might have a lot of feedback as well) are:

1. Like you mentioned, ability to set time/date period with custom values
and presets like last hour/day/week/month/year.
2. Ability to set grouping interval (minute, hour, day, week, month, year),
3. Be able to tag sources of data for grouping (WSO2 Cloud has many logs
from many servers, these servers jointly form solutions like "App Cloud",
"API Cloud") - we need to be able to specify that so we can see not just
joint picture but split by solutions,
4. Filter by any field for drill-down: severity
(error/warning/informational), solution (see #3), server, component,
message, tenant, user,
5. For the currently selected time period and filters, see grouping/count
by any of the fields: e.g.:

App Cloud: 55% (110),
API Cloud: 45% (90).

OR

Error: 7% (14),
Warning: 3% (6),
Informational: 90% (180).

Etc.

6. Preserve last view - so I can quickly get to the view of my favorite
filters (ideally have ability to also have multiple shortcuts),

7. Views encoded as URL parameters, so I can just forward the URL to a team
mate,

8. Be able to see all messages that fall under current filters, and drill
into any of these to see full error trace, get the actual log file, etc.

I also like your suggestion on supporting search and regex - would help
troubleshooting!

Hope this helps!
Dmitry





On Wed, Sep 24, 2014 at 10:48 AM, Sanjiva Weerawarana 
wrote:

> Yes we should use the same library everywhere .. no need to be different
> just to be different :-).
>
> On Wed, Sep 24, 2014 at 5:36 PM, Gimantha Bandara 
> wrote:
>
>> Hi Dakshika,
>>
>> There is no specific reason. It seems like both jqplot and Flot have the
>> same customization capabilities.
>> It will not be hard to change the graph libraries, if it is needed.
>>
>> Thanks,
>>
>> On Wed, Sep 24, 2014 at 3:28 PM, Dakshika Jayathilaka 
>> wrote:
>>
>>> Is there any specific reason for using jqplot?
>>>
>>> AFAIK platform wide, we are using flotchart lib[1] due to advance
>>> customization capabilities.
>>>
>>> 1. http://www.flotcharts.org/
>>>
>>> *Dakshika Jayathilaka*
>>> Software Engineer
>>> WSO2, Inc.
>>> lean.enterprise.middleware
>>> 0771100911
>>>
>>> On Wed, Sep 24, 2014 at 2:48 PM, Gimantha Bandara 
>>> wrote:
>>>
>>>> Hi All,
>>>>
>>>>
>>>> Currently I am working on the Front end. These were developed keeping
>>>> Kibana as the reference. Currently the UI supports the following tasks.
>>>>
>>>>1. Setting the refresh rate ( Refresh the logging graph and the log
>>>>table / Log view )*
>>>>2. Setting the Time range ( custom time range or in the format of
>>>>''Last 5 min, Last 10 mins...etc) *
>>>>3. Searchbox for searching ( Queries will be regex or Lucene )
>>>>4. Filters (For searching)
>>>>5. Log graph ( hits per time)
>>>>6. Filters for log table/view
>>>>7. Log table view (in progress)
>>>>8. Micro panel which is similar to Kibana micro panel (in progress)
>>>>
>>>> The graph is created using jqplot[1] library. So the graph support all
>>>> the features jqplot offers.
>>>> Other UIs are based on JQuery/JQueryUI[2]
>>>> The Micro Panel will be developed using Bootstrap[3].
>>>>
>>>> Note that the theme used for the UI can be changed and the log table is
>>>> still in progress.
>>>> Currently the UI is integrated with ElasticSearch to view real log data.
>>>>
>>>> Here are some screenshots of the current UIs.
>>>> ​
>>>>  Update-24.09.2014
>>>> <https://docs.google.com/a/wso2.com/folderview?id=0B7luxEF9AEBxSHc3aEI3YUxYRVk&usp=drive_web>
>>>> ​
>>>>
>>>> [1] http://www.jqplot.com/
>>>> [2] https://jquery.org/projects/
>>>> [3] http://getbootstrap.com/javascript/
>>>>
>>>> --
>>>> Gimantha Bandara
>>>> Software Engineer
>>>> WSO2. Inc : http://wso2.com
>>>> Mobile : +94714961919
>>>>
>>>> ___
>>>> Architecture mailing list
>>>> Architecture@wso2.org
>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>
>>>>
>>>
>

Re: [Architecture] AppFactory Custom URL improvement - Phase 2 - Add complete custom URLs

[Dmitry Sotnikov]

Samith,

Why do we need validationkey.sampleapp.userdomain.com and not
sampleapp.userdomain.com <http://validationkey.sampleapp.userdomain.com/> just
 CNAME record?

Adding either of them would require the same DNS ownership of the domain,
right?

Dmitry

On Fri, Sep 12, 2014 at 2:58 PM, Samith Dassanayake  wrote:

> In current implementation users can only specify the subdomain of the
> custom URL, which is mapped under the domain wso2apps.com. In the 2nd
> phase of usability improvement for custom URL, we will allow users to add
> complete custom URL by having  domain owner verification before setting up
> the custom URL. On app creation, we will assign a production URL by
> default, in the format of appid.tenantdomain.wso2apps.com and users can
> change the URL as they want, based on the permissions and validity of the
> domain.
>
> *User scenario:*
> 1. User creates an app and gets sampleapp.tenantdomain.wso2apps.com URL
> from AF,
> 2. User wants to use sampleapp.userdomain.com <http://www.superapp.com/> 
> (which
> he owns) apart from the given URL.
> 3. User goes to his hosting service and adds CNAME mapping
> sampleapp.userdomain.com <http://www.superapp.com/> to
> sampleapp.tenantdomain.wso2apps.com.
> 4. User goes to AF UI and tells AF to use sampleapp.userdomain.com
> <http://www.superapp.com/> as production URL,
> 5  AF will generate a validation key and ask user to add CNAME mapping
> validationkey.sampleapp.userdomain.com to apps.cloud.wso2.com  for
> ownership validation.
> 5. AF verifies that the ownership of the custom domain
> 5.a. If YES: the LB is configured to accept the requests,
> 5.b. If NO: user is asked to first add the CNAME DNS record at registrar
> or retry in a few hours if record has been added recently and has not yet
> propagated.
>
> For the ownership verification we planing to reuse the existing carbon
> domain validation component[1]. When a user specifies a custom URL, AF will
> generate a validation key and user has to add a CNAME record from
> validationkey.sampleapp.userdomain.com to apps.cloud.wso2.com (AF).  The
> generated verification key will be saved against the custom URL(
> sampleapp.userdomain.com <http://www.superapp.com/>) in the AF registry
> and AF will verify the custom URL, by accessing the registry via
> validationkey.sampleapp.userdomain.com.  Once the custom URL is
> validated, AF will send a request to LB to map sampleapp.userdomain.com
> <http://www.superapp.com/> to app which is pointed by the
> sampleapp.tenantdomain.wso2apps.com. Therefore once AF verify the custom
> URL, user can use custom URL after the CNAME DNS record of
> sampleapp.userdomain.com <http://www.superapp.com/> to
> sampleapp.tenantdomain.wso2apps.com is propagated.
>
> [1]
> https://github.com/wso2/platform/tree/master/components/stratos/domain-validator
>
> Suggestions, improvements and alternatives are welcome.
>
> Thank you
>
> --
> Best Regards
>
> Samith Dassanayake
> Software Engineer, WSO2 Inc.
>
>


-- 
Dmitry Sotnikov
VP of Cloud; WSO2, Inc.;  http://wso2.com/
email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov
Lean . Enterprise . Middleware

<http://wso2.com/events/>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] API Manager - Self Signup for tenant's API Store

[Dmitry Sotnikov]

ith tenants signups for superuser. Existing code uses configuration
>>>>>> in the carbon super user's registry entry
>>>>>> '/_system/governance/apimgt/applicationdata/workflow-extensions.xml' for
>>>>>> tenants as well ( see jsFunction_addUser() in
>>>>>> org.wso2.carbon.apimgt.hostobjects.APIStoreHostObject class. ). When
>>>>>> registering a tenant user for different tenant, configuration in the
>>>>>> tenant's workflow-extensions.xml needed to be used.
>>>>>>
>>>>>> I have implemented basic functionality[1] as requested by AmilaM
>>>>>> (Users can signup for tenant stores. But Tenant admin has to manually add
>>>>>> the registry entry with user roles to the given location. If this entry 
>>>>>> is
>>>>>> not there, a default 'identity' user role is assigned to the user.  Only
>>>>>> UserSignUpSimpleWorkflowExecutor for the workflow can be used with this. 
>>>>>> If
>>>>>> UserSignUpWSWorkflowExecutor is used to connect to the BPS, the tenant
>>>>>> approval tasks are not created properly)
>>>>>>
>>>>>
>>>>> Do we know the reason for the tasks of the BPS not being created when
>>>>> the UserSignUpWSWorkflowExecutor is used? We will need to dig into that
>>>>> IMO.
>>>>>
>>>>>>
>>>>>> [1] https://wso2.org/jira/browse/APIMANAGER-2785
>>>>>>
>>>>>> Comments are highly appreciated
>>>>>> Thanks,
>>>>>> Chamila.
>>>>>>
>>>>>> --
>>>>>> Regards,
>>>>>> Chamila Adhikarinayake
>>>>>> Software Engineer
>>>>>> WSO2, Inc.
>>>>>> Mobile - +94712346437
>>>>>> Email  - chami...@wso2.com
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Nuwan Dias
>>>>>
>>>>> Associate Tech Lead - WSO2, Inc. http://wso2.com
>>>>> email : nuw...@wso2.com
>>>>> Phone : +94 777 775 729
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Regards,
>>>> Chamila Adhikarinayake
>>>> Software Engineer
>>>> WSO2, Inc.
>>>> Mobile - +94712346437
>>>> Email  - chami...@wso2.com
>>>>
>>>
>>>
>>>
>>> --
>>> *Amila De Silva*
>>>
>>> WSO2 Inc.
>>> mobile :(+94) 775119302
>>>
>>>
>>
>>
>> --
>> Regards,
>> Chamila Adhikarinayake
>> Software Engineer
>> WSO2, Inc.
>> Mobile - +94712346437
>> Email  - chami...@wso2.com
>>
>
>
>
> --
> Regards,
> Chamila Adhikarinayake
> Software Engineer
> WSO2, Inc.
> Mobile - +94712346437
> Email  - chami...@wso2.com
>



-- 
Dmitry Sotnikov
VP of Cloud; WSO2, Inc.;  http://wso2.com/
email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov
Lean . Enterprise . Middleware

<http://wso2.com/events/>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [AF] Capturing BAM events with an objective of understanding user activity

[Dmitry Sotnikov]

Got it. Thanks Dimuthu!
On Sep 3, 2014 5:01 PM, "Dimuthu Leelarathne"  wrote:

> Hi Dmitry,
>
> Yes. It makes perfect sense. But the only problem is current
> implementation is not transferring each and every event when it happens.
> What I do is record the events and periodically send to the backend. The
> time period is large. (note: timestamp is recorded at the browser, so the
> actual time is preserved even though recording happens in 2 mins).
>
> So what happens if a person browse away or hit cancel/ok before the next
> time slice? We are going to loose some events, unless we use the unload
> method. That was why I am looking for it.
>
> Other option is to reduce the time slice but that would increase the
> recording period.
>
> Chanaka's solution worked when used properly!
>
> thanks,
> dimuthu
>
>
>
>
>
>
>
>
> On Wed, Sep 3, 2014 at 6:24 AM, Dmitry Sotnikov  wrote:
>
>> Quick thought (maybe not relevant or inferior to the current direction
>> ;)):
>>
>> Maybe instead of "abandoning events", we concentrate on events that show
>> success (and thus detect "failure" is "not achieving success")?
>>
>> For example, to invite team members you go through the following steps:
>> 1. Go to the team invitation page,
>> 2. Do something on the page (start filling out the forms to specify the
>> usernames/email addresses, roles, etc.),
>> 3. Send the invite,
>> 4. New member actually accepts and logs in,
>> 5. You add the user to an app,
>> 6. New member actually does something meaningful.
>>
>> If we have events for some of these steps but not all the way through #6
>> - we know that the overall scenario failed, and we can also track the
>> percentage of users that got lost on each step.
>>
>> Does this make sense?
>>
>> Dmitry
>>
>>
>> On Mon, Sep 1, 2014 at 4:46 AM, Chanaka Jayasena 
>> wrote:
>>
>>> Use "beforeunload" with jQuery bind to catch this event. It works with
>>> FF, Chrome, and IE 7+ but not supported by Opera. Following is a sample
>>> code.
>>>
>>> $(window).bind('beforeunload', function() {
>>> //put code to save data
>>> return "Give a message to alert the user. Or
>>> simply remove the return statement.";
>>> });
>>>
>>>  thanks,
>>> Chanaka
>>>
>>>
>>> On Mon, Sep 1, 2014 at 3:00 PM, Dimuthu Leelarathne 
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>> This feature is almost complete. But facing issues in identifying
>>>> window abandoning events such as hitting the back button of the browser. Is
>>>> there a possible way to do this? Otherwise background saving will have to
>>>> done more frequently and would cause a lot more traffic.
>>>>
>>>> thanks,
>>>> dimuthu
>>>>
>>>>
>>>>
>>>> On Fri, Aug 8, 2014 at 6:08 PM, Amila Maha Arachchi 
>>>> wrote:
>>>>
>>>>> Hi Dimuthu,
>>>>>
>>>>> Thanks for the explanation.
>>>>>
>>>>> With this kind of recording, I see another great advantage. That is to
>>>>> lineup all the activities done by a user. If we filter out activities of a
>>>>> user and sort them by time we'll get something like
>>>>>
>>>>> Clicked Create new application -> submitted application creation ->
>>>>> clicked application xyz -> clicker open button -> clicked repos and builds
>>>>> page etc.
>>>>>
>>>>>
>>>>> On Fri, Aug 1, 2014 at 11:25 PM, Dimuthu Leelarathne <
>>>>> dimut...@wso2.com> wrote:
>>>>>
>>>>>> Hi Amila,
>>>>>>
>>>>>> This is how you can do it. Let me tell you by example.
>>>>>>
>>>>>> App creation page loads (we record timestamp here). And only one of
>>>>>> the following happens and pls note we record all timestamps.
>>>>>>
>>>>>> 1 - App creation button clicked
>>>>>> OR
>>>>>> 2 - Page unloads (meaning user browsed away)
>>>>>> OR
>>>>>> 3 - You see 2 on the same page messages
>>>>>> OR
>>>>>> 4 - User hit cacle
>>>>>>
>>>>>>

Re: [Architecture] [App Factory] Improvements to application wall

[Dmitry Sotnikov]

Excellent news, Manisha!

I am in Colombo starting Tue, Sept 9 - so demos and sync-ups will be quite
easy. :)

Dmitry


On Tue, Sep 2, 2014 at 11:46 PM, Manisha Gayathri  wrote:

> Hi Dmitry,
>
> Since Gayan is in support now, I will continue to work on this.
> The doc attached, contains the items completed by Gayan so far.
>
> I will be able to do a demo on next Monday with the completed items. And
> we will be able to ship the completed feature for M6.
>
> Thanks
> Manisha
>
>
>
> On Fri, Aug 15, 2014 at 7:18 AM, Gayan Dhanushka  wrote:
>
>> Hi Dmitry,
>>
>> I have scheduled a demo o Monday. I will do a sample implementation of
>> the two scenarios and give a demo to you on Monday.
>>
>> GayanD
>>
>>
>> On Fri, Aug 15, 2014 at 1:05 AM, Dmitry Sotnikov  wrote:
>>
>>> Yes, some sort of PoC would be good. I am not sure what you mean by
>>> showing the Type B messages on the page - so would be great to see it in
>>> action or at least on mockups...
>>> On Aug 14, 2014 8:02 PM, "Dimuthu Leelarathne" 
>>> wrote:
>>>
>>>> Hi Dmitry,
>>>>
>>>> Please see my comments inline.
>>>>
>>>>
>>>> On Thu, Aug 14, 2014 at 12:17 PM, Dmitry Sotnikov 
>>>> wrote:
>>>>
>>>>> Gayan and Dimuthu,
>>>>>
>>>>> From my perspective, one-off UX exceptions are bad, because they make
>>>>> the UI inconsistent.
>>>>>
>>>>> There are two types of messages:
>>>>> A. High-level external notifications of someone taking some action
>>>>> (e.g. "John created a new app") and
>>>>> B. Low-level ongoing processes happening in AF as result of what the
>>>>> current user clicks ("Creating initial GIT repository", etc.)
>>>>>
>>>>> Type A are more social and shown across team, and only when something
>>>>> is actually successfully finished.
>>>>>
>>>>> Spinning wheels / progress indications are only relevant to type B.
>>>>> These messages are only related to the current particular user and show
>>>>> work in progress, starting immediately once the user clicks something.
>>>>>
>>>>> So from my perspective, either we show both types in one pane, or have
>>>>> two different panes (or other UX metaphors) for the two types.
>>>>>
>>>>
>>>> What I am suggesting is a different approach. Which is to show the type
>>>> B messages on the page itself where the information is related. For example
>>>> the fact that build is in progress should be on the Build & Repo page
>>>> itself. What if we do a POC for the same scenario
>>>>
>>>> 1 - on the wall
>>>> 2 - on the page
>>>>
>>>> And see which is user friendly? I agree two panes are not going to be a
>>>> good solution.
>>>>
>>>> thanks,
>>>> dimuthu
>>>>
>>>>
>>>>> My understanding is that the current idea is to try to re-use the same
>>>>> App Wall for everything, right?
>>>>>
>>>>> Dmitry
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Aug 14, 2014 at 9:39 AM, Gayan Dhanushka 
>>>>> wrote:
>>>>>
>>>>>> Hi Dimuthu,
>>>>>>
>>>>>> I tried a sample implementation to show the implementation on the
>>>>>> application wall. This was done by looking at the content of the message.
>>>>>> It was successful. But this may not be ideal since for different kind of
>>>>>> start-inprogress-ended messages we may need to have different logic.
>>>>>>
>>>>>> Meanwhile I can share some wire frames of the approach suggested
>>>>>> above to show the in progress activities on the pages themselves.
>>>>>>
>>>>>> Thanks
>>>>>> GayanD
>>>>>>
>>>>>>
>>>>>> On Thu, Aug 14, 2014 at 4:43 AM, Dimuthu Leelarathne <
>>>>>> dimut...@wso2.com> wrote:
>>>>>>
>>>>>>> Hi Gayan,
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Aug 13, 2014 at 2:28 PM, Gayan Dhanushka 
>>>>>>> wrote:
>>>>>>>
>>>>>&g

Re: [Architecture] [AF] Capturing BAM events with an objective of understanding user activity

[Dmitry Sotnikov]

Quick thought (maybe not relevant or inferior to the current direction ;)):

Maybe instead of "abandoning events", we concentrate on events that show
success (and thus detect "failure" is "not achieving success")?

For example, to invite team members you go through the following steps:
1. Go to the team invitation page,
2. Do something on the page (start filling out the forms to specify the
usernames/email addresses, roles, etc.),
3. Send the invite,
4. New member actually accepts and logs in,
5. You add the user to an app,
6. New member actually does something meaningful.

If we have events for some of these steps but not all the way through #6 -
we know that the overall scenario failed, and we can also track the
percentage of users that got lost on each step.

Does this make sense?

Dmitry


On Mon, Sep 1, 2014 at 4:46 AM, Chanaka Jayasena  wrote:

> Use "beforeunload" with jQuery bind to catch this event. It works with FF,
> Chrome, and IE 7+ but not supported by Opera. Following is a sample code.
>
> $(window).bind('beforeunload', function() {
> //put code to save data
> return "Give a message to alert the user. Or
> simply remove the return statement.";
> });
>
>  thanks,
> Chanaka
>
>
> On Mon, Sep 1, 2014 at 3:00 PM, Dimuthu Leelarathne 
> wrote:
>
>> Hi all,
>>
>> This feature is almost complete. But facing issues in identifying window
>> abandoning events such as hitting the back button of the browser. Is there
>> a possible way to do this? Otherwise background saving will have to done
>> more frequently and would cause a lot more traffic.
>>
>> thanks,
>> dimuthu
>>
>>
>>
>> On Fri, Aug 8, 2014 at 6:08 PM, Amila Maha Arachchi 
>> wrote:
>>
>>> Hi Dimuthu,
>>>
>>> Thanks for the explanation.
>>>
>>> With this kind of recording, I see another great advantage. That is to
>>> lineup all the activities done by a user. If we filter out activities of a
>>> user and sort them by time we'll get something like
>>>
>>> Clicked Create new application -> submitted application creation ->
>>> clicked application xyz -> clicker open button -> clicked repos and builds
>>> page etc.
>>>
>>>
>>> On Fri, Aug 1, 2014 at 11:25 PM, Dimuthu Leelarathne 
>>> wrote:
>>>
>>>> Hi Amila,
>>>>
>>>> This is how you can do it. Let me tell you by example.
>>>>
>>>> App creation page loads (we record timestamp here). And only one of the
>>>> following happens and pls note we record all timestamps.
>>>>
>>>> 1 - App creation button clicked
>>>> OR
>>>> 2 - Page unloads (meaning user browsed away)
>>>> OR
>>>> 3 - You see 2 on the same page messages
>>>> OR
>>>> 4 - User hit cacle
>>>>
>>>> What you have to do is write queries to figure out which event occur
>>>> after the app creation page loads - 1,2,3 or 4th. You can also calculate
>>>> with what probability each of these events occur after app creation page
>>>> occur. You can also measure average times.
>>>>
>>>> thanks,
>>>> dimuthu
>>>>
>>>>
>>>> On Fri, Aug 1, 2014 at 7:32 PM, Amila Maha Arachchi 
>>>> wrote:
>>>>
>>>>> Hi Dimuthu,
>>>>>
>>>>> You have said that we want to know how much time did a user spend on
>>>>> completing an action. For this you need to publish an event when a button
>>>>> is clicked. And then, how are you going to publish the finished event?
>>>>>
>>>>>
>>>>> On Thu, Jul 31, 2014 at 8:12 PM, Dmitry Sotnikov 
>>>>> wrote:
>>>>>
>>>>>> Looks good. I assume that Timestamp is Date/Time and not just time
>>>>>> (examples just have time - but I assume this is a typo).
>>>>>>
>>>>>> Dmitry
>>>>>>
>>>>>>
>>>>>> On Thu, Jul 31, 2014 at 6:13 PM, Dimuthu Leelarathne <
>>>>>> dimut...@wso2.com> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> In addition let me give you some samples
>>>>>>>
>>>>>>>
>>>>>>> Tenant Id | Username(email) | Item | Action  | Timestamp | Context
>>>>&

Re: [Architecture] [App Factory] Improvements to application wall

[Dmitry Sotnikov]

Yes, some sort of PoC would be good. I am not sure what you mean by showing
the Type B messages on the page - so would be great to see it in action or
at least on mockups...
On Aug 14, 2014 8:02 PM, "Dimuthu Leelarathne"  wrote:

> Hi Dmitry,
>
> Please see my comments inline.
>
>
> On Thu, Aug 14, 2014 at 12:17 PM, Dmitry Sotnikov  wrote:
>
>> Gayan and Dimuthu,
>>
>> From my perspective, one-off UX exceptions are bad, because they make the
>> UI inconsistent.
>>
>> There are two types of messages:
>> A. High-level external notifications of someone taking some action (e.g.
>> "John created a new app") and
>> B. Low-level ongoing processes happening in AF as result of what the
>> current user clicks ("Creating initial GIT repository", etc.)
>>
>> Type A are more social and shown across team, and only when something is
>> actually successfully finished.
>>
>> Spinning wheels / progress indications are only relevant to type B. These
>> messages are only related to the current particular user and show work in
>> progress, starting immediately once the user clicks something.
>>
>> So from my perspective, either we show both types in one pane, or have
>> two different panes (or other UX metaphors) for the two types.
>>
>
> What I am suggesting is a different approach. Which is to show the type B
> messages on the page itself where the information is related. For example
> the fact that build is in progress should be on the Build & Repo page
> itself. What if we do a POC for the same scenario
>
> 1 - on the wall
> 2 - on the page
>
> And see which is user friendly? I agree two panes are not going to be a
> good solution.
>
> thanks,
> dimuthu
>
>
>> My understanding is that the current idea is to try to re-use the same
>> App Wall for everything, right?
>>
>> Dmitry
>>
>>
>>
>> On Thu, Aug 14, 2014 at 9:39 AM, Gayan Dhanushka  wrote:
>>
>>> Hi Dimuthu,
>>>
>>> I tried a sample implementation to show the implementation on the
>>> application wall. This was done by looking at the content of the message.
>>> It was successful. But this may not be ideal since for different kind of
>>> start-inprogress-ended messages we may need to have different logic.
>>>
>>> Meanwhile I can share some wire frames of the approach suggested above
>>> to show the in progress activities on the pages themselves.
>>>
>>> Thanks
>>> GayanD
>>>
>>>
>>> On Thu, Aug 14, 2014 at 4:43 AM, Dimuthu Leelarathne 
>>> wrote:
>>>
>>>> Hi Gayan,
>>>>
>>>>
>>>> On Wed, Aug 13, 2014 at 2:28 PM, Gayan Dhanushka 
>>>> wrote:
>>>>
>>>>> Hi Dimuthu,
>>>>>
>>>>> Following are a set of actions that we want to give
>>>>> "started-inprogress-ended" messages and places where we would put the
>>>>> spinning wheel and messages.
>>>>>
>>>>> 1) Application Creation - User home near the application thumbnail
>>>>> (This is already implemented)
>>>>> 2) Application Upload - Application creation page (This is already
>>>>> implemented. Spinning wheel is shown on the application creation page 
>>>>> until
>>>>> the application is uploaded)
>>>>> 3) Build - Repos Builds page near last build status
>>>>> 4) Deployment - Repos Builds page near last deploy id
>>>>> 5) Promote / Demote - Lifecycle page under the particular version
>>>>>
>>>>> I am tentative on having an in progress state for resource creation
>>>>> since it does not take much time.
>>>>>
>>>>>
>>>> It doesn't take much time in Dev setups. But takes considerable time in
>>>> Cloud. I think for resources we need to give "started" and "ended" 
>>>> messages.
>>>>
>>>> @ Dmitry: What do you think about the new proposal? Giving
>>>> progress-reporting on the page itself, rather than on the wall?
>>>>
>>>> We can do some wireframes and then can finalise. WDYT?
>>>>
>>>> thanks,
>>>> dimuthu
>>>>
>>>>
>>>> What are your thoughts?
>>>>>
>>>>> Regards
>>>>> Gayan
>>>>>
>>>>>
>>>>> On Wed, Aug 13, 2014 at 12:28 PM, Dimuthu Leelarath

Re: [Architecture] [App Factory] Improvements to application wall

[Dmitry Sotnikov]

n Dhanushka 
>>>>> wrote:
>>>>>
>>>>>> Hi Anuruddha / Dimuthu,
>>>>>>
>>>>>> The more global this ID is for all the events makes it more
>>>>>> consistent. Otherwise we'll have to render these messages according to
>>>>>> different parameters which are there in each message. Having said that we
>>>>>> need to figure out a common way of doing this. Doing this by looking at 
>>>>>> the
>>>>>> message content is not a good approach I guess. Need to figure out a 
>>>>>> better
>>>>>> way of doing this.
>>>>>>
>>>>>> Gayan
>>>>>>
>>>>>>
>>>>>> On Wed, Aug 13, 2014 at 10:38 AM, Dimuthu Leelarathne <
>>>>>> dimut...@wso2.com> wrote:
>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> Good question. How about generating an ID that can be generated
>>>>>>> equally from both sides. For example, if it is build then buildID. If 
>>>>>>> it is
>>>>>>> deployment then md5 sum. The more unique the the ID is, then we have 
>>>>>>> less
>>>>>>> work in identifying decoding user/event.
>>>>>>>
>>>>>>> thanks,
>>>>>>> dimuthu
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Aug 13, 2014 at 10:30 AM, Anuruddha Premalal <
>>>>>>> anurud...@wso2.com> wrote:
>>>>>>>
>>>>>>>> Hi Gayan,
>>>>>>>>
>>>>>>>> We'll also need to consider about the failure events while tracking
>>>>>>>> the progress.
>>>>>>>>
>>>>>>>> eg. Deployment failure should stop the progress of the deployment
>>>>>>>> event.
>>>>>>>>
>>>>>>>> So we'll have to keep track on start, failure and stop status of a
>>>>>>>> particular event.
>>>>>>>>
>>>>>>>> Other concern is assigning UUID's for events. These events are not
>>>>>>>> fired from a central point how are we going to associate a UUID to 
>>>>>>>> track
>>>>>>>> them?
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Anuruddha.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Aug 13, 2014 at 5:37 AM, Dimuthu Leelarathne <
>>>>>>>> dimut...@wso2.com> wrote:
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> There can be several methods, one being subscription management.
>>>>>>>>> However since master branch is shared by all it would be interesting 
>>>>>>>>> to
>>>>>>>>> know whether a build was triggered on it by all. However even in the 
>>>>>>>>> first
>>>>>>>>> phase we must filter out activities happening on the fork repos. I 
>>>>>>>>> think
>>>>>>>>> the approach Manjula mentioned should be applied to forked repos.
>>>>>>>>>
>>>>>>>>> Lets add all events to the doc life cycle and issue tracker events
>>>>>>>>> as well.
>>>>>>>>>
>>>>>>>>> thanks,
>>>>>>>>> dimuthu
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Tue, Aug 12, 2014 at 8:42 PM, Gayan Dhanushka 
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Hi Manjula,
>>>>>>>>>>
>>>>>>>>>> Thanks for the input. I will try to utilize the above mentioned
>>>>>>>>>> method in the second phase when trying to make the app wall more
>>>>>>>>>> personalized.
>>>>>>>>>>
>>>>>>>>>> Regards
>>>>>>>>>> GayanD
>>>>>>>>>>
>>>>>>>>>>
>

Re: [Architecture] [App Factory] Improvements to application wall

[Dmitry Sotnikov]

Gayan,

Indeed, looks like Udara and I are thinking along the same lines. :) This
is more than just a build. E.g. when I am creating an application, there
are a lot of things that happen (borrowing from your list):

   1. application creation started
   2. initial git repo creation
   3. jenkins space creation
   4. issue tracker space creation
   5. app authorization in cloud environments
   6. application creation completed

If I am creating an app - I'd like to see them all - because this takes the
mystery out of the process and makes me more comfortable with the platform.

If my team-member is creating an app - these 6 events and their progress
are just noise. All I need to do is: "Jane created a new Java app
HelloWorld" (if my role allows me to even know that this new app exists).

Again, obviously this all can be phase two.

Dmitry


On Tue, Aug 12, 2014 at 1:07 PM, Gayan Dhanushka  wrote:

> Hi Dmitry,
>
> Thanks for pointing things out. IMO that would be phase two Dmitry. As
> soon as I complete publishing all the relevant events I will look to
> accommodate the noise-reduction filter as well. WDYT of the suggestion made
> by Udara in the above reply? I think that is a valid comment as well.
>
> Hi Udara,
>
> The point that you are making is valid I think. With the suggestion made
> by Dmitry in the above reply I think this will come into the picture.
>
> Thanks
> GayanD
>
>
> On Tue, Aug 12, 2014 at 2:27 PM, Udara Rathnayake  wrote:
>
>> Hi Gayan,
>>
>> See my comment in-line.
>>
>> On Tue, Aug 12, 2014 at 1:54 PM, Gayan Dhanushka  wrote:
>>
>>> Hi all,
>>>
>>> We have identified that the events in the doc attached herewith are the
>>> events which are triggered within each page. While some of them are already
>>> published, some of them needs to be published to the social component in
>>> order to enhance the user experience and collaboration. While doing this we
>>> have encountered some issues and some resolutions are proposed to overcome
>>> those issues.
>>>
>>> *Problem*: There is no way to track whether a certain build or a
>>> deployment instance triggered by someone is completed.(No association
>>> between start and finish events for a certain instance). There is no way to
>>> represent an ongoing process. (e.g. application creation in progress, build
>>> is in progress etc.)
>>>
>> Here we have to think about the user experience.
>> IMO the user who triggered the build only interested to see the progress
>> of that particular build, others may be interested to see the start and the
>> end but not the progress.
>>
>> WDYT?
>>
>>>
>>> The same problem would be applied to any scenario where it takes some
>>> time for a certain event to finish and app factory needs to capture both
>>> start and completion events related to a particular instance.
>>>
>>> *Solution* : Use a UUID to track events which takes time to complete
>>>
>>> Publishing both start and complete events with the same UUID as a event
>>> property would solve the problem. Then by looking at the event content we
>>> are able to find whether there is a completion event for a certain start
>>> event. This would be a global thing so the notification wall logic can be
>>> written in such a manner that we need to have a look at only the UUID. If
>>> we use different mechanisms for tracking start and completion events of
>>> different events the notification wall logic would be more complex when
>>> filtering out the events
>>>
>>> Your thoughts are welcome.
>>>
>>> [1] https://redmine.wso2.com/issues/3065
>>>
>>> Thanks
>>> GayanD
>>>
>>> --
>>> Gayan Dhanuska
>>> Software Engineer
>>> http://wso2.com/
>>> Lean Enterprise Middleware
>>>
>>> Mobile
>>> 071 666 2327
>>>
>>> Office
>>> Tel   : 94 11 214 5345
>>> Fax  : 94 11 214 5300
>>>
>>> Twitter : https://twitter.com/gayanlggd
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> *Udara Rathnayake*
>> Software Engineer
>> WSO2 Inc. : http://wso2.com
>>
>> Mobile : +94 772207239
>> Twitter : http://twitter.com/udarakr
>> Blog: http://udarakr.blogspot.com
>>
>>
>

Re: [Architecture] [App Factory] Improvements to application wall

[Dmitry Sotnikov]

Gayan,

A few items seem to be missing:

   - Issue tracker events,
   - Lifecycle: production URL assignment, ToDo checkbox selected/cleared.

Also, are we adding additional noise-reduction filter so user by default
sees more events related to his/her activity and smaller number of events
related to team-members?

OK if that is phase 2 - but I think this will be something we will have to
do in the future to make the solution practical.

Dmitry


On Tue, Aug 12, 2014 at 12:24 PM, Gayan Dhanushka  wrote:

> Hi all,
>
> We have identified that the events in the doc attached herewith are the
> events which are triggered within each page. While some of them are already
> published, some of them needs to be published to the social component in
> order to enhance the user experience and collaboration. While doing this we
> have encountered some issues and some resolutions are proposed to overcome
> those issues.
>
> *Problem*: There is no way to track whether a certain build or a
> deployment instance triggered by someone is completed.(No association
> between start and finish events for a certain instance). There is no way to
> represent an ongoing process. (e.g. application creation in progress, build
> is in progress etc.)
>
> The same problem would be applied to any scenario where it takes some time
> for a certain event to finish and app factory needs to capture both start
> and completion events related to a particular instance.
>
> *Solution* : Use a UUID to track events which takes time to complete
>
> Publishing both start and complete events with the same UUID as a event
> property would solve the problem. Then by looking at the event content we
> are able to find whether there is a completion event for a certain start
> event. This would be a global thing so the notification wall logic can be
> written in such a manner that we need to have a look at only the UUID. If
> we use different mechanisms for tracking start and completion events of
> different events the notification wall logic would be more complex when
> filtering out the events
>
> Your thoughts are welcome.
>
> [1] https://redmine.wso2.com/issues/3065
>
> Thanks
> GayanD
>
> --
> Gayan Dhanuska
> Software Engineer
> http://wso2.com/
> Lean Enterprise Middleware
>
> Mobile
> 071 666 2327
>
> Office
> Tel   : 94 11 214 5345
> Fax  : 94 11 214 5300
>
> Twitter : https://twitter.com/gayanlggd
>



-- 
Dmitry Sotnikov
VP of Cloud; WSO2, Inc.;  http://wso2.com/
email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov
Lean . Enterprise . Middleware

 <http://wso2.com/events/>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [AF] Capturing BAM events with an objective of understanding user activity

[Dmitry Sotnikov]

Looks good. I assume that Timestamp is Date/Time and not just time
(examples just have time - but I assume this is a typo).

Dmitry


On Thu, Jul 31, 2014 at 6:13 PM, Dimuthu Leelarathne 
wrote:

> Hi,
>
> In addition let me give you some samples
>
>
> Tenant Id | Username(email) | Item | Action  | Timestamp | Context
> (Application) | App Type | Comments
>   450 | d...@aha.com | X-Button | Clicked | 12:09:40 | app1 | WAR |
> Additional data (optional)
>  780 | d...@man.com | url of home page | loaded | 12:10:50 | none | none |
>  Additional data (optional)
>  thanks,
> dimuthu
>
>
>
>
>
>
>
>
>
>
>  On Thu, Jul 31, 2014 at 7:26 PM, Dimuthu Leelarathne 
> wrote:
>
>> Hi,
>>
>> We can capture App Type event as well. So the even stream would be
>> updated as follows.
>>
>> Tenant Id : Username(email) : Item : Action : Timestamp : Context
>> (Application) : App Type : Comments
>>
>> thanks,
>> dimuthu
>>
>>
>> On Thu, Jul 31, 2014 at 4:07 PM, Dmitry Sotnikov  wrote:
>>
>>> Dimuthu,
>>>
>>> Are "comments" parameters of the action? For example, the type of
>>> application user chose when creating the new app?
>>>
>>> That would be good to have so administrators know which app types are in
>>> use in their App Factory deployment.
>>>
>>> Dmitry
>>>
>>>
>>> On Thu, Jul 31, 2014 at 1:57 PM, Dimuthu Leelarathne 
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>>
>>>> A sample set of events a user would do,
>>>>
>>>> User x logged in
>>>>
>>>> App home loads
>>>>
>>>> Clicked on “Add New Application” button
>>>>
>>>> Create application page loads
>>>>
>>>> Clicked upload/create from scratch
>>>>
>>>> Clicked “Create Application”
>>>>
>>>> App home loads
>>>>
>>>> Clicked on application tile
>>>>
>>>> Clicked on repo url
>>>>
>>>> Did a commit === Not by browser but by a Git client
>>>>
>>>> Set the production URL
>>>>
>>>> Edit description
>>>>
>>>> Click on expand icons on current status on home page
>>>>
>>>> Clicked on “Open URL”
>>>>
>>>> Clicked on “Open Issues” from home page
>>>>
>>>> Clicked “Delete Application”
>>>>
>>>> User home loads
>>>>
>>>> User x logged out
>>>>
>>>>
>>>> *What we need to do*
>>>>
>>>> Record these user’s events with the objective of understanding user
>>>> interactions with App Factory
>>>>
>>>> *What we need to understand about user interactions?*
>>>>
>>>> - How much time user spend to between start action and end action
>>>> (Create application button and completing of that task)
>>>>
>>>> - What are the most frequent actions a user would perform
>>>>
>>>> - What are the actions user started but never completed and why?
>>>> Session timeout, Hit Cancel, Or just browse away
>>>>
>>>> - What is the most frequently loaded page
>>>>
>>>> - What is the most frequently accessed application of a user?
>>>>
>>>>
>>>> *This we are going record*
>>>>
>>>> Tenant Id : Username(email) : Item : Action : Timestamp : Context
>>>> (Application) : Comments
>>>>
>>>> *Methodology*
>>>>
>>>> Each time an event happens we are going to keep it in the JavaScript
>>>> data structure. Then these data will be transferred to backend
>>>>
>>>> - Periodically (5 minutes) with another action called “on the same page
>>>> after 5 mins”- this is because if a session invalidates we can identify it
>>>> by this action
>>>>
>>>> - Or each time the page unloads
>>>>
>>>> When backend receive(Jaggery) the data it will be published to the BAM.
>>>> Then in the Java layer also we'll identify points that user would interact
>>>> for example - commits and publish it to BAM.
>>>>
>>>>
>>>> Any thoughts?
>>>>
>>>> thanks,
>>>> dimuthu
>>>>
>>>> --
>>>> Dimuthu Leelarathne
>&g

Re: [Architecture] [AF] Capturing BAM events with an objective of understanding user activity

[Dmitry Sotnikov]

Dimuthu,

Are "comments" parameters of the action? For example, the type of
application user chose when creating the new app?

That would be good to have so administrators know which app types are in
use in their App Factory deployment.

Dmitry


On Thu, Jul 31, 2014 at 1:57 PM, Dimuthu Leelarathne 
wrote:

> Hi,
>
>
> A sample set of events a user would do,
>
> User x logged in
>
> App home loads
>
> Clicked on “Add New Application” button
>
> Create application page loads
>
> Clicked upload/create from scratch
>
> Clicked “Create Application”
>
> App home loads
>
> Clicked on application tile
>
> Clicked on repo url
>
> Did a commit === Not by browser but by a Git client
>
> Set the production URL
>
> Edit description
>
> Click on expand icons on current status on home page
>
> Clicked on “Open URL”
>
> Clicked on “Open Issues” from home page
>
> Clicked “Delete Application”
>
> User home loads
>
> User x logged out
>
>
> *What we need to do*
>
> Record these user’s events with the objective of understanding user
> interactions with App Factory
>
> *What we need to understand about user interactions?*
>
> - How much time user spend to between start action and end action (Create
> application button and completing of that task)
>
> - What are the most frequent actions a user would perform
>
> - What are the actions user started but never completed and why? Session
> timeout, Hit Cancel, Or just browse away
>
> - What is the most frequently loaded page
>
> - What is the most frequently accessed application of a user?
>
>
> *This we are going record*
>
> Tenant Id : Username(email) : Item : Action : Timestamp : Context
> (Application) : Comments
>
> *Methodology*
>
> Each time an event happens we are going to keep it in the JavaScript data
> structure. Then these data will be transferred to backend
>
> - Periodically (5 minutes) with another action called “on the same page
> after 5 mins”- this is because if a session invalidates we can identify it
> by this action
>
> - Or each time the page unloads
>
> When backend receive(Jaggery) the data it will be published to the BAM.
> Then in the Java layer also we'll identify points that user would interact
> for example - commits and publish it to BAM.
>
>
> Any thoughts?
>
> thanks,
> dimuthu
>
> --
> Dimuthu Leelarathne
> Architect & Product Lead of App Factory
>
> WSO2, Inc. (http://wso2.com)
> email: dimut...@wso2.com
> Mobile : 0773661935
>
> Lean . Enterprise . Middleware
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Dmitry Sotnikov
VP of Cloud; WSO2, Inc.;  http://wso2.com/
email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov
Lean . Enterprise . Middleware

 <http://wso2.com/events/>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Appfactory - Support for WAR deployment for Tomcat Single tenant Cartridge

[Dmitry Sotnikov]

t; Application Creation: Steps:
>>>>>>>
>>>>>>> 1. A user navigates to ‘Create Application’ page.
>>>>>>>
>>>>>>> 2. Selects the application type as Web Application (app type = war).
>>>>>>>
>>>>>>> 3. Appfactory would populate a drop down list that displays the
>>>>>>> available runtimes:
>>>>>>>
>>>>>>> WSO2 Application Server v 5.1.0
>>>>>>>
>>>>>>> Apache Tomcat v 7.0.54
>>>>>>>
>>>>>>> 4. User selects ‘Apache Tomcat’ as his preferred runtime and creates
>>>>>>> the application
>>>>>>>
>>>>>>> (Appfactory will record this information for later use).
>>>>>>>
>>>>>>>
>>>>>>> Application Deployment:
>>>>>>>
>>>>>>> 1. Upon the very first deployment of any application version onto a
>>>>>>> particular stage, Appfactory would make a subscription in Stratos, 
>>>>>>> based on
>>>>>>> the selected runtime during the application creation (git repository
>>>>>>> containing the war artifact is provided during the subscription).
>>>>>>>
>>>>>>> Examples:
>>>>>>>
>>>>>>> a) A trunk version of the application is auto-built and
>>>>>>> auto-deployed onto the ‘Development’ stage. Before the very first
>>>>>>> deployment happens (after the auto build) Appfactory should make the
>>>>>>> subscription.
>>>>>>>
>>>>>>> b) Promotion of an application
>>>>>>>
>>>>>>>
>>>>>>>- A developer promotes a particular version of an application
>>>>>>>from the Development stage to the Testing stage.
>>>>>>>- A QA Engineer clicks on the ‘Deploy’ button of that version.
>>>>>>>- Appfactory checks whether there is a subscription available
>>>>>>>for this application in Testing stage.
>>>>>>>- If there is no such subscription already, then Appfactory
>>>>>>>would make a new subscription based on the runtime selected during 
>>>>>>> the
>>>>>>>application creation.
>>>>>>>- Appfactory would deploy the particular application version
>>>>>>>onto the server in the Test Stage.
>>>>>>>
>>>>>>>
>>>>>>> 2. If the runtime selected by the user is based on a single tenanted
>>>>>>> cartridge, Stratos will spin up a new cartridge once a subscription is
>>>>>>> made. If the runtime provided is a multi-tenanted cartridge, the 
>>>>>>> instances
>>>>>>> are created  when cartridge definition is provisioned (as specified by 
>>>>>>> the
>>>>>>> autoscaling and deployment policy).
>>>>>>>
>>>>>> Here what is the strategy for spawning single tenant cartridges?Is it
>>>>> cartridge per application? Or one cartridge per tenant?
>>>>>
>>>>
>>>> What about the JNDI look up isolation we have done in App Server? Is it
>>>> portable to Tomcat?
>>>>
>>> In tomcat each web app will get their own JNDI context but the problem
>>> is Tomcat does not allow adding/editing and deleting JNDI resource without
>>> a redeploy.So we will not able to register datasources for web app
>>> dynamically.We can port the same idea to tomcat ,we may need to extend
>>> tomcat's JNDI factory and plug.
>>>
>>>>
>>>> thanks,
>>>> dimuthu
>>>>
>>>>
>>>>
>>>>>
>>>>>>> Improvements:
>>>>>>>
>>>>>>> User could be given the option to select the runtime per application
>>>>>>> per stage.
>>>>>>>
>>>>>>> (e.g. Apache tomcat dev/test stages , WSO2 Application server for
>>>>>>> Production stage)
>>>>>>>
>>>>>>>
>>>>>>>
>>>>
>>>>>
>>>>>>> --
>>>>>>> Regards,
>>>>

Re: [Architecture] WSO2 App Factory User Home page UI improvements

[Dmitry Sotnikov]

+1 on the comments from Shiro & Dimuthu and the new look&feel.

Also, I suggest that we change Subdomain to "Production URL". By default,
this has http://myappkey.wso2apps.com, and user can click "Change Custom
URL" which will let specify custom URL, give instructions on DNS setup, and
test DNS to ensure that records are indeed in proper order.

Dmitry


On Wed, Apr 30, 2014 at 7:21 AM, Dimuthu Leelarathne wrote:

> Hi all,
>
> Pages are looking more interesting.
>
> +1 for suggestions. Specifically I like using just "Accept".
>
> Thanx,
> Dimuthu
>
> On 30 Apr 2014 16:22, "Shiroshica Kulatilake"  wrote:
> >
> > Hi Chanaka,
> >
> > On Wed, Apr 30, 2014 at 3:45 PM, Chanaka Jayasena 
> wrote:
> >>
> >> Hi all,
> >>
> >> I created few mockups with usability improvements to the application
> home page. In the current UI, editing the description and uploading an
> application icon is not consistent. From the attached  images I am showing
> default state, mouse over state and editing state of each component.
> >>
> >> The "Current Status" section has few changes. I think to have the git
> icon instead of the globe icon is better to represent the "Browse URL"
> link. Also replace the copy git URL link with a control that's been
> commonly use in github. The launching URL of each application version is
> displayed and given an option to copy it to clip board.
> >
> >
> > The clickable URL for each application will be shown when application
> artifacts have been deployed. If they are not - then the button will be
> displayed (wording should be either "Deploy" or "Accept deployment") - so
> there will be no scenario where both the link and the button are available.
> >
> > Thank you,
> > Shiro
> >
> >
> >>
> >>
> >> thanks,
> >> Chanaka
> >> --
> >> Chanaka Jayasena
> >> Senior Software Engineer; WSO2, Inc.;  http://wso2.com/
> >> email: chan...@wso2.com; cell: +94 77 785 5565
> >> blog: http://chanaka3d.blogspot.com
> >
> >
> >
> >
> > --
> > Shiroshica Kulatilake
> >
> > Architect,
> > WSO2, Inc. http://wso2.com/
> > Phone: +94 776523867
>



-- 
Dmitry Sotnikov
VP of Cloud; WSO2, Inc.;  http://wso2.com/
email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov
Lean . Enterprise . Middleware

 <http://wso2.com/events/>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Setting DNS for URLs to be mapped in AF URL Mapper story

[Dmitry Sotnikov]

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 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: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov
Lean . Enterprise . Middleware

 <http://wso2.com/events/>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] UI fixes for App Factory Repos and Builds page

[Dmitry Sotnikov]

gt; 3. Instead of using highlighted color to forked repository version
>>>>>> record, keep it as same as others. But put very clear separater in 
>>>>>> between
>>>>>> master and forked repositories.
>>>>>>
>>>>>>
>>>>>> I feel other changes are very cool.
>>>>>>
>>>>>> thanks
>>>>>>
>>>>>>
>>>>>> *Harsha Thirimanna*
>>>>>>
>>>>>> Senior Software Engineer; WSO2, Inc.; http://wso2.com
>>>>>> * <http://www.apache.org/>*
>>>>>> * email: **hars...@wso2.com* * cell: +94 71 5186770*
>>>>>> * twitter: **http://twitter.com/ <http://twitter.com/afkham_azeez>*
>>>>>> *harshathirimann linked-in: **http:
>>>>>> <http://lk.linkedin.com/in/afkhamazeez>**//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122
>>>>>> <http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122>*
>>>>>>
>>>>>>  *Lean . Enterprise . Middleware*
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Fri, Apr 25, 2014 at 7:56 AM, Chanaka Jayasena 
>>>>>> wrote:
>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> Harsha and I was discussing about the improvements that can be done
>>>>>>> to the UI base on previous Usability reviews. We came up with the 
>>>>>>> following
>>>>>>> two screens. I am working with Harsha with the changes.
>>>>>>>
>>>>>>> thanks,
>>>>>>> Chanaka
>>>>>>>
>>>>>>> --
>>>>>>> Chanaka Jayasena
>>>>>>> Senior Software Engineer; WSO2, Inc.;  http://wso2.com/
>>>>>>> email: chan...@wso2.com; cell: +94 77 785 5565
>>>>>>> blog: http://chanaka3d.blogspot.com
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Dimuthu Leelarathne
>>>>> Architect & Product Lead of App Factory
>>>>>
>>>>> WSO2, Inc. (http://wso2.com)
>>>>> email: dimut...@wso2.com
>>>>> Mobile : 0773661935
>>>>>
>>>>> Lean . Enterprise . Middleware
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Chanaka Jayasena
>>>> Senior Software Engineer; WSO2, Inc.;  http://wso2.com/
>>>> email: chan...@wso2.com; cell: +94 77 785 5565
>>>> blog: http://chanaka3d.blogspot.com
>>>>
>>>
>>>
>>>
>>> --
>>> Shiroshica Kulatilake
>>>
>>> Architect,
>>> WSO2, Inc. http://wso2.com/
>>> Phone: +94 776523867
>>>
>>
>>
>>
>> --
>> Dimuthu Leelarathne
>> Architect & Product Lead of App Factory
>>
>> WSO2, Inc. (http://wso2.com)
>> email: dimut...@wso2.com
>> Mobile : 0773661935
>>
>> Lean . Enterprise . Middleware
>>
>
>
>
> --
> Shiroshica Kulatilake
>
> Architect,
> WSO2, Inc. http://wso2.com/
> Phone: +94 776523867
>



-- 
Dmitry Sotnikov
VP of Cloud; WSO2, Inc.;  http://wso2.com/
email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov
Lean . Enterprise . Middleware

 <http://wso2.com/events/>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Using special characters in the tenant admin user name

[Dmitry Sotnikov]

All these threads make me wonder if there is a way to give user some sort
of hidden "internal id" (that has proper characters, has no issues with our
systems, etc. but is never displayed) and then use Email as some sort of
"display id" that user is using and seeing everywhere in the UI?

The issues that you describe are not the only ones that we are seeing. E.g.:

- If email is used as the real ID everywhere we will still have some issues
- e.g. when user is changing email address.

- And also in App Factory when you use email today we are still having UI
show something like email@tenantid - like 'j...@gmail.com@
johnswonderfulcompany.com' - which looks very awkward and still requires
change.

Is there a way to just separate what user sees & types, and what the system
is using internally - and solve all these issues.

Does this make any sense? I do not know the underlying architecture well
enough to know whether this makes sense from dev perspective.

Dmitry


On Wed, Apr 23, 2014 at 11:18 PM, Sumedha Kodithuwakku wrote:

> Hi all,
>
> Using special characters in the email seems to cause another issue. When
> resetting passwords this will cause a issue (refer to mail: [1] ).
>
> When resetting the password a confirmation key is generated which is send
> in the email. This confirmation key is stored in the registry with the user
> name in the path. But since user name (i.e. email) may contain special
> characters such as ~!@#;%^*()+={}|\<>"', which is illegal for registry
> paths, it is not possible to store this in registry. So the password reset
> will not work with these characters by default. If we allow these we will
> have to replace these characters when we store the confirmation key in the
> registry.
>
>
> [1]
> http://wso2.markmail.org/message/flsizcz2ibzwx3ik?q=list:org%2Ewso2%2Edev
> [2] https://support.google.com/a/answer/33386?hl=en
>
> Thanks
> SumedhaS
>
>
> On Thu, Apr 24, 2014 at 12:07 AM, Dmitry Sotnikov  wrote:
>
>> If I understand the code right, the issue is with ~!#$;%^*()+={}[]|\<>
>>  Right?
>>
>> Geeks (with gmail addresses) are using '+' quite often (to avoid spamming
>> and set filtering) so why getting someone rejected every day? Based on my
>> experience + is definitely being used in more than 0.01% signups. ;) Others
>> might indeed be more rare... Are there really issues with each of them or
>> is that a matter of "we never tested these so we do not know whether or not
>> something breaks"?
>>
>> If we had understanding of which ones are difficult to fix, we could make
>> a more meaningful decision and indeed allow the ones that are OK (hopefully
>> '+' is one of them) and add graceful UI validation for the remaining
>> characters.
>>
>> Dmitry
>>
>>
>> On Wed, Apr 23, 2014 at 6:39 AM, Afkham Azeez  wrote:
>>
>>> Let's keep it simple. No special characters allowed. 99.99% of the time
>>> there is no special character.
>>>
>>>
>>> On Wed, Apr 23, 2014 at 7:04 PM, Sumedha Kodithuwakku >> > wrote:
>>>
>>>> Hi all,
>>>>
>>>> In the new cloud user model email will be used as the user name. This
>>>> will result in tenant admin also having a email as the user name.
>>>>
>>>> There can be email addresses with some special characters such as +
>>>> sign. However when we create a tenant, there is  a validation for the
>>>> tenant admin user name ( validateAdminUserName() in [1] ), and this
>>>> validation will fail when there is a + sign in the email. Therefore we
>>>> can't create a tenant with such a user name.
>>>>
>>>> If we remove the validation, will it cause any issue in other places..?
>>>> To do this we need to modify [1] to remove the validation as the validated
>>>> characters are hard coded. Or else we can read this from a config file.
>>>>
>>>> Also we can validate this at the UI level and reject user names with
>>>> these special characters which might reduce the usability (i.e Users will
>>>> have to use email addresses without these characters when creating
>>>> tenants).
>>>>
>>>> What is the correct solution for this..?
>>>>
>>>> Any thoughts, suggestions are welcome.
>>>>
>>>> [1]
>>>> https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/components/stratos/tenant-mgt/org.wso2.carbon.tenant.mgt.core/2.2.0/src/main/java/org/wso2/carbon/tenant/mgt/core/TenantPersistor.java
>>>>
&g

Re: [Architecture] Using special characters in the tenant admin user name

[Dmitry Sotnikov]

If I understand the code right, the issue is with ~!#$;%^*()+={}[]|\<>
 Right?

Geeks (with gmail addresses) are using '+' quite often (to avoid spamming
and set filtering) so why getting someone rejected every day? Based on my
experience + is definitely being used in more than 0.01% signups. ;) Others
might indeed be more rare... Are there really issues with each of them or
is that a matter of "we never tested these so we do not know whether or not
something breaks"?

If we had understanding of which ones are difficult to fix, we could make a
more meaningful decision and indeed allow the ones that are OK (hopefully
'+' is one of them) and add graceful UI validation for the remaining
characters.

Dmitry


On Wed, Apr 23, 2014 at 6:39 AM, Afkham Azeez  wrote:

> Let's keep it simple. No special characters allowed. 99.99% of the time
> there is no special character.
>
>
> On Wed, Apr 23, 2014 at 7:04 PM, Sumedha Kodithuwakku 
> wrote:
>
>> Hi all,
>>
>> In the new cloud user model email will be used as the user name. This
>> will result in tenant admin also having a email as the user name.
>>
>> There can be email addresses with some special characters such as + sign.
>> However when we create a tenant, there is  a validation for the tenant
>> admin user name ( validateAdminUserName() in [1] ), and this validation
>> will fail when there is a + sign in the email. Therefore we can't create a
>> tenant with such a user name.
>>
>> If we remove the validation, will it cause any issue in other places..?
>> To do this we need to modify [1] to remove the validation as the validated
>> characters are hard coded. Or else we can read this from a config file.
>>
>> Also we can validate this at the UI level and reject user names with
>> these special characters which might reduce the usability (i.e Users will
>> have to use email addresses without these characters when creating
>> tenants).
>>
>> What is the correct solution for this..?
>>
>> Any thoughts, suggestions are welcome.
>>
>> [1]
>> https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/components/stratos/tenant-mgt/org.wso2.carbon.tenant.mgt.core/2.2.0/src/main/java/org/wso2/carbon/tenant/mgt/core/TenantPersistor.java
>>
>> Thanks
>> SumedhaS
>>
>> --
>> *Sumedha Kodithuwakku*
>> Software Engineer
>> WSO2 Inc. : wso2.com
>> lean . enterprise . middleware
>>
>> Email: sumed...@wso2.com;  Mobile: +94 71 808 1124
>> Blog: http://sumedhask.blogspot.com/
>>
>>
>
>
> --
> *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* 
> * cell: +94 77 3320919 <%2B94%2077%203320919> 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*
>



-- 
Dmitry Sotnikov
VP of Cloud; WSO2, Inc.;  http://wso2.com/
email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov
Lean . Enterprise . Middleware

 <http://wso2.com/events/>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Auto generate the tenant domain for cloud registration

[Dmitry Sotnikov]

Amila,

+1 on autogeneration without prompting user.

I think that if we have smart enough substitution rules (e.g. remove spaces
and if necessary add numbers to disambiguate) the ID will be recognizable
enough, and also - to your point - indeed, customers who care about URLs
will use their custom URLs anyway, so our internal Customer ID will not
affect them at all.

Dmitry


On Mon, Apr 21, 2014 at 10:05 PM, Amila Maha Arachchi wrote:

> Hi all,
>
> In the current registration model we are working for WSO2 Cloud, we are
> registering the user with the email. Then when we are creating the tenant,
> we prompt the user for a display name and a company id. This display name
> will be used in all the UIs and company id (which will be taken as the
> tenant domain) will be used in functional stuff.
>
> There is a suggestion to avoid asking for a company id from the user and
> generate it from the display name provided by him.
>
> For example, if the user provides the display name for the organisation as
> "My organization", we can generate the company id (tenant domain) as
> "myorg" or "myorganiz345" in a unique manner. If the user provides
> something like "john.com" we can use it as it is.
>
> Although we are using the display name everywhere in the UI, there will be
> places which display the company id such as the URLs shown in API Manager.
> One disadvantage I see is, if we assign a company id in the likes of
> "myorganiz345", user will find it difficult to remember a URL (unless/until
> url mapping is there/not there).
>
> WDYT?
>
> 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: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov
Lean . Enterprise . Middleware

 <http://wso2.com/events/>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [Appfactory] Usability Improvements for External Apis

[Dmitry Sotnikov]

Dimuthu,

+1 on all the points.

Indeed need a unified approach, and indeed the screenshot that you attached
is a step in that direction but needs further work to make its UX better.

Dmitry


On Sat, Apr 19, 2014 at 6:15 AM, Dimuthu Leelarathne wrote:

> Hi all,
>
> I am attaching the current UI we have for APIs. So in this screenshot, it
> is grouped by the name and we can see the behaviour of it's value in
> Development,Testing and Production.
>
> Personally, I don't like the look-and-feel of this control, but it has the
> correct concept. We can develop a control with better look-and-feel and use
> it across everything - APIs, DBs and Properties.
>
> In addition to points Dmitry highlighted, I would like to highlight
> editing fuctionality of resources. The idea behind the editing
> functionality improvement is "when we are editing a particular resource, we
> should know what is the stage that we are editing and what values". Right
> now the editing functionality is not user-friendly because we go to edit
> page without the knowledge of the stage. Perhaps we can incorporate that
> into the control as well.
>
> When we develop this control (html or methodology or tag - i don't know
> the exact term), we can use it across all resources (APIs, DBs and
> Properties).
>
> Furthermore, we only have to review one of these - either APIs, DBs or
> Properties. Ideally everything else follows the same style and need not
> even be reviewed. It must be that consistent!
>
> thanks,
> dimuthu
>
>
>
>
> On Sat, Apr 19, 2014 at 12:58 AM, Dmitry Sotnikov  wrote:
>
>> Asanka,
>>
>> From my perspective, all resource management in App Factory exists within
>> the ALM conceptual model. The coolness of App Factory is *not* that you
>> can list the resources (properties, APIs, databases), but that you can get
>> them automatically switched as the application moves from dev to test to
>> prod.
>>
>> This means that for all resources (properties, APIs, databases) - we need
>> to follow the same conceptual model:
>>
>> Resource A:
>>
>>- It's work in Dev,
>>- It's work in Test,
>>- It's work in Prod,
>>
>> Resource B:
>>
>>- It's work in Dev,
>>- It's work in Test,
>>- It's work in Prod,
>>
>> And for them all we need to have:
>> 1. Code samples on how to use them,
>> 2. Ability to simply get them to be the same or separate for the
>> different stages of ALM.
>>
>> To your question, the URL naming of the column is fine.
>>
>> Thanks!
>> Dmitry
>>
>>
>> On Fri, Apr 18, 2014 at 5:32 AM, Asanka Dissanayake wrote:
>>
>>> Hi All,
>>> Please find the inline image after @subject .
>>>
>>> ​
>>> The main improvement that has been carried out is , listing APIs per the
>>> environment. In addition to that I made a small change renaming the
>>> "Values" column to "URL". The rationale behind that change is , Earlier the
>>> only value shown in that column  is url (There are some other values
>>> also,they are not shown ATM.Since this is a summary page, showing the URL
>>> only is sufficient IMO) , so there is no point of naming the column as
>>> "Values" and showing only the URL.
>>>
>>> WDYT?
>>>
>>> Thanks,
>>> Asanka D
>>>
>>>
>>>
>>> --
>>>
>>>
>>> *Asanka Dissanayake Software Engineer*
>>> *WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>>> <http://wso2.com/>*
>>>
>>> *email: asan...@wso2.com ,   blog:
>>> cyberwaadiya.blogspot.com
>>> <http://cyberwaadiya.blogspot.com>, asankastechtalks.wordpress.com
>>> <http://asankastechtalks.wordpress.com>  mobile: +94 71 8373821*
>>>
>>
>>
>>
>> --
>> Dmitry Sotnikov
>> VP of Cloud; WSO2, Inc.;  http://wso2.com/
>> email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov
>> Lean . Enterprise . Middleware
>>
>>  <http://wso2.com/events/>
>>
>
>
>
> --
> Dimuthu Leelarathne
> Architect & Product Lead of App Factory
>
> WSO2, Inc. (http://wso2.com)
> email: dimut...@wso2.com
> Mobile : 0773661935
>
> Lean . Enterprise . Middleware
>



-- 
Dmitry Sotnikov
VP of Cloud; WSO2, Inc.;  http://wso2.com/
email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov
Lean . Enterprise . Middleware

 <http://wso2.com/events/>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [Appfactory] Usability Improvements for External Apis

[Dmitry Sotnikov]

Asanka,

>From my perspective, all resource management in App Factory exists within
the ALM conceptual model. The coolness of App Factory is *not* that you can
list the resources (properties, APIs, databases), but that you can get them
automatically switched as the application moves from dev to test to prod.

This means that for all resources (properties, APIs, databases) - we need
to follow the same conceptual model:

Resource A:

   - It's work in Dev,
   - It's work in Test,
   - It's work in Prod,

Resource B:

   - It's work in Dev,
   - It's work in Test,
   - It's work in Prod,

And for them all we need to have:
1. Code samples on how to use them,
2. Ability to simply get them to be the same or separate for the different
stages of ALM.

To your question, the URL naming of the column is fine.

Thanks!
Dmitry


On Fri, Apr 18, 2014 at 5:32 AM, Asanka Dissanayake wrote:

> Hi All,
> Please find the inline image after @subject .
>
> ​
> The main improvement that has been carried out is , listing APIs per the
> environment. In addition to that I made a small change renaming the
> "Values" column to "URL". The rationale behind that change is , Earlier the
> only value shown in that column  is url (There are some other values
> also,they are not shown ATM.Since this is a summary page, showing the URL
> only is sufficient IMO) , so there is no point of naming the column as
> "Values" and showing only the URL.
>
> WDYT?
>
> Thanks,
> Asanka D
>
>
>
> --
>
>
> *Asanka Dissanayake Software Engineer*
> *WSO2 Inc. - lean . enterprise . middleware |  wso2.com <http://wso2.com/>*
>
> *email: asan...@wso2.com ,   blog:
> cyberwaadiya.blogspot.com
> <http://cyberwaadiya.blogspot.com>, asankastechtalks.wordpress.com
> <http://asankastechtalks.wordpress.com>  mobile: +94 71 8373821*
>



-- 
Dmitry Sotnikov
VP of Cloud; WSO2, Inc.;  http://wso2.com/
email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov
Lean . Enterprise . Middleware

 <http://wso2.com/events/>
<>___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [AppFactory] Incorporating usability improvements

[Dmitry Sotnikov]

mate production url of
>the application. Showing this on the application home page and making it
>editable.
>- Introducing help messages which is done in accordance with i18n.
>Externalized tool tips which is also in accordance with i18n.
>- Improving the UIs by fixing some UI related improvements.
>
> Following are the screenshots of the new UIs after improvements. Please
> note that the icons used here are sample icons.(A new set of icons will be
> incorporated next week.)
>
> User Home
>
>
>  
> userhome.png<https://docs.google.com/a/wso2.com/file/d/0B5OmHe7M-ZSHYXBZRXZqSkxoOVU/edit?usp=drive_web>
>
> Application Creation
>
>
>  
> appcreation.png<https://docs.google.com/a/wso2.com/file/d/0B5OmHe7M-ZSHNFNYaVNqWWpmWFE/edit?usp=drive_web>
>
> Application Home
>
>
>  
> apphome.png<https://docs.google.com/a/wso2.com/file/d/0B5OmHe7M-ZSHcklUT045Ukc3d1U/edit?usp=drive_web>
>
> Please share your thoughts.
>
> Thanks
>
> GayanD
>
>
> Gayan Dhanuska
> Software Engineer
> http://wso2.com/
> Lean Enterprise Middleware
>
> Mobile
> 071 666 2327
>
> Office
> Tel   : 94 11 214 5345
> Fax  : 94 11 214 5300
>
> Twitter : https://twitter.com/gayanlggd
>



-- 
Dmitry Sotnikov
VP of Cloud; WSO2, Inc.;  http://wso2.com/
email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov
Lean . Enterprise . Middleware

 <http://wso2.com/events/>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [AF] Domain and url mapping in App Factory

[Dmitry Sotnikov]

Punnadi,

I doubt "http://appserver.prod./webapps/-/"
is a desirable solution for many customers. We need to just let them use
their custom domains without the extra "stuff".

Are the issues arising from us insisting on internal paths like "
http://appserver.prod.milestones.appfactory.wso2.com/t/myorg.com/webapps/sampleapp-1.0.0/";
compared to, say, heroku's myappname.herokuapp.com? Is there a reason why
we cannot - for production - cannot do what others are doing without having
to modify each and every app server?

Also, to add to the complexity, will we be able to support apex/naked/root
domains like myapp.com? If we cannot do this via A-records (e.g. because of
lack of static IP addresses?) - we can use workarounds a-la Heroku's:
https://devcenter.heroku.com/articles/custom-domains#root-domain

Dmitry


On Thu, Mar 13, 2014 at 2:21 AM, Punnadi Gunarathna wrote:

> Some problems with the New approach:
>
> 1. If a particular user set the mapped domain name as "amazon.com" it
> will be an issue. How can we avoid such situations?
> 2. If we implement the url mapping logic in wso2 AS and if a particualr
> customer wants to use another application server instead what will happen?
>
>
> On Thu, Mar 13, 2014 at 1:53 PM, Punnadi Gunarathna wrote:
>
>>
>> Hi All,
>>
>> This requirement came for Dmitry's uberstories. The idea is to let users
>> to have the freedom to decide the actual production url of a deployed
>> application. I will describe the details it as follows.
>>
>> *The Problem:*
>> In App Factory, Application Servers will be fronted with Apache Stratos
>> LB where it's proxyPort attribute are set to 80(HTTP) and 443(HTTPS).
>> Say a web application of a particular tenant is ready to use. Therefore
>> it is now deployed in Production stage and the url to access this
>> application
>> is similar to below pattern in the current implementation.
>>
>> http://appserver.prod.milestones.appfactory.wso2.com/t/
>> /webapps/-/
>>
>> e.g:
>>
>> http://appserver.prod.milestones.appfactory.wso2.com/t/myorg.com/webapps/sampleapp-1.0.0/
>>
>> *The Requirement:*
>> Rather than having a lengthy url with unnecessary information is it
>> possible to map this url to a more user-friendly and meaningful pattern?
>>
>> *The solution*
>>
>> *Initial Plan (Had a discussion with Lakmal to implement this feature in
>> Apache Stratos LB):*
>>
>> In order to implement this requirement in Apache Stratos LB front, the
>> solution has to be generic and with a minimal impact to it's performance.
>> Moreover following facts need to be taken into consideration while
>> designing the mapped url from App Factory perspective.
>>
>> 1. It's not particle to let the user to decide the mapped url. Because
>> certain data has to be added to url for it's uniqueness.
>>  - Cartridge type (Which has the capability to deploy PHP, ESB, Web,
>> jaggery Applications)
>>  - Stage (Dev, Test, Prod)
>>  - App name with the version (Because there can be multiple versions of
>> the same application in Production)
>>
>> The mapped url pattern can be as follows:
>>
>> http://appserver.prod./webapps/-/
>>
>> e.g:
>> http://appserver.prod.myorg.com/webapps/sampleapp-1.0.0/
>>
>> Note: If we remove the version from this mapped url again the number of
>> mappings that we need to keep in LB front will increase which is not a good
>> solution.
>>
>> If the above solution is implemented only below mapping is required to
>> have in Straos LB front and the rest can be generated with the facts comes
>> with the mapped url.
>>
>> myorg.com - milestones.appfactory.wso2.com
>>
>>
>> *New direction (Had a discussion with Lakmal and Azeez):*
>>
>> With the initial plan the actual requirement of having a custom url
>> cannot be achieved properly. Because the mapped url pattern has lot of
>> restrictions.
>> Now the solution is to implement the url mapping logic in AS and domain
>> mapping logic in Apache Stratos LB. In that case a mapped url can be a
>> simple and meaningful url.
>> By having the domain mapping in LB front, the corresponding cluster can
>> be identified when the mapped url is hit from the browser.
>> Wso2 AS previously had this url mapper component and it requires to be
>> added back to implement this solution.
>> What was the reason that this url mapper was removed from AS?
>>
>> Please share your thoughts and ideas...
>>
>> --
>> Thanks and Regards,
>>
>> Punnadi Gunar

Re: [Architecture] APIM / ES Store Supporting custom themes for tenants.

[Dmitry Sotnikov]

This makes sense to me.

Need to make sure that this CSS customization is sufficient for complete
rebranding including for example company logo, etc.

Dmitry


On Mon, Feb 24, 2014 at 2:07 AM, Joseph Fonseka  wrote:

>
> Hi All
>
> In an APIM multi-tenanted deployment there might be a requirement for the
> tenants to customize the store look and feel. We are hoping to support this
> by providing tenants to upload custom themes.
>
> Custom themes can be supported in two levels.
>
> 1. CSS based customizations.
>- In the first level users are allowed to customize and upload the
> style sheets with the supported resources ( images and fonts ).
>
> 2. Template base customizations.
>- In the second level user will be able to upload a custom caramel
> theme with modified templates , CSS , and JavaScript. To implement this we
> need to ensure Template files will be executed within a sandbox environment
> for security reasons.
>
> Initially we decided to support CSS based theming.
>
> *Implementation*.
> 1. Tenant user will be given and interface to upload the custom themes.
> 2. The application would accept a zip file containing CSS , images and
> font files.
> 3. Uploaded themes will be stored in directories having the tenant
> name, within the application.
>
> Ex :
> Tenants
> -- / Tenant1
> -- / -- / Theme
> -- / Tenant2
> -- / -- / Theme
>
> 4. When the store is loading If a tenant has a custom theme it would
> replace / override the default theme.
>
> *Design Decisions*
> 1. We decided to store custom themes in a directory considering they
> will get synced by dep sync in a clustered setup.
> 2. If we are storing them in the registry we need to implement caching
> when serving those resources.
>
> Please let us know your thoughts.
>
> Thanks
> Jo
>
>
>
>
>
> --
> *Joseph Fonseka*
>  WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 772 512 430
> skype: jpfonseka
>
> * <http://lk.linkedin.com/in/rumeshbandara>*
>
>


-- 
Dmitry Sotnikov
VP of Cloud; WSO2, Inc.;  http://wso2.com/
email: dmi...@wso2.com; cell: +1.949.303.9653; Skype: DSotnikov
Lean . Enterprise . Middleware

 <http://wso2.com/events/>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture