Re: [Architecture] Machine Learner - Proposed UX
I have a feeling its better to have Algorithm type and Algorithm in the same level as Algorithm, and then have a tab inside to see all algos to select one, and another tab to help selecting one algo from recommendations. Regards Suho On Wed, Dec 17, 2014 at 12:38 PM, Lochana Menikarachchi loch...@wso2.com wrote: In step 8/9, we ask the questions by default. The user has the option to skip and go to the all algorithms view. What happens after clicking on the build model? I am assuming it redirects into home with current workflow expanded Thanks. On Wed, Dec 17, 2014 at 12:14 PM, Dhanuka De Silva dhanu...@wso2.com wrote: Hi All Proposed UXD/workflow mockups for ML Tool is shared in the below location. Hope these are self explanatory and are based on last few discussion had with team. Feel free to ask if you need any clarification. https://drive.google.com/a/wso2.com/folderview?id=0B4eoLHAhQ246c1NBZWlDQXpjVTgusp=sharing *Order to navigate* ML-1-landing-no-projects (Landing page with no existing projects created) ML-2-landing-with-existing-projects (Landing page with few existing projects and their workflows) ML-3-create-project (Creating a new project) ML-4-project-created (Project is created. Providing feedback for next steps) ML-5-Wizard-Step-1 (Creating a Workflow - Wizard Step 1) ML-6-Wizard-Step-2-a (Selecting and pre-process data - Wizard Step 2) ML-7-Wizard-Step-2-b (Explore existing data - Wizard Step 2) ML-8-Wizard-Step-3 (Select an Algorithm type - Wizard Step 3) ML-9-Wizard-Step-4 (Select an Algorithm from the list or/Suggested Algorithms if Skipped using HELP button from Step 3 - Wizard Step 4) ML-10-Wizard-Step-5-final (Modify parameters for the selected Algorithm - Wizard Step 5) Cheers -- Dhanuka De Silva m: +94 773 887816 e: dhanu...@wso2.com w: http://www.wso2.com -- Lochana Menikarachchi Senior Tech Lead WSO2 Inc. -- *S. Suhothayan* Technical Lead Team Lead of WSO2 Complex Event Processor *WSO2 Inc. *http://wso2.com * http://wso2.com/* lean . enterprise . middleware *cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/ http://suhothayan.blogspot.com/twitter: http://twitter.com/suhothayan http://twitter.com/suhothayan | linked-in: http://lk.linkedin.com/in/suhothayan http://lk.linkedin.com/in/suhothayan* ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
[Architecture] [AF] [MB] Make Appfactory tenant subscription to stratos environments fault tolerant
Hi all, Im working on Making the tenants subscription to stratos environments fault tolerant [1] This has been discussed in mail thread with subject - [Architecture] [AF] Tenant subscribing to stratos environments - making it fault tolerant *Issue* ** There are some possible failure points in AF, hence in App Cloud. One such critical point is making the tenants subscribed to the dev, test and prod stratos environments. Due to any reason, if this step fails, then, thats the end of story for that tenant. Actually in appfactory tenant creation, When a tenant creation request is made, appfactory sends REST calls to stratos environments (dev,prod,test) to create tenants. At the moment there is no way to overcome a situation where tenant creation fails in one or more stratos environments. *Proposal* *===* Here what I'm going to do is, integrate WSO2 Message Broker to take tenant creation requests to a durable topic and manipulate the process in a fault tolerant manner. The durable topic will keep messages around persistently for any suitable consumer to consume them. Appfactory will have a publisher who publishes messages in the topic inside MB when a tenant creation is requested. There will be a subscriber for each stratos environment who is listening to above topic(create_teanant). If subscription is successfull then subscriber will acknowledge to MB and MB will not send that particular request to same subscriber again. If subscription got failed subscriber will not ack. and MB will take care of sending that request until it becomes successful. At the moment we have 3 stratos environments therefore we will have 3 subscribers listening to that particular topic(create_teanant) in MB. In a case of AF having more stratos environments in future, it is possible to add more subscribers. Durable topic subscribers[2] will be used here since it will persist the subscription on behalf of the client subscription when client is not online. This step is not synchronous therefore above changes will not effect the tenant creation flow. *Architectural diagram * *=* Architectural diagram can be found in [3] [1] - https://wso2.org/jira/browse/APPFAC-2436 [2] - https://docs.wso2.com/display/MB220/Creating+a+Durable+Topic+Subscription [3] - https://docs.google.com/a/wso2.com/drawings/d/15CmM3rCTwjUUu4V6lp2WX32nRzufraDXawALNYIoTek/edit -- *Mahesh Chinthaka Vidanagama* | Software Engineer WSO2, Inc | lean. enterprise. middleware. #20, Palm Grove, Colombo 03, Sri Lanka Mobile: +94 71 63 63 083 | Work: +94 112 145 345 Email: mahe...@wso2.com | Web: www.wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Machine Learner - Proposed UX
In step 8/9, we ask the questions by default. The user has the option to skip and go to the all algorithms view. What happens after clicking on the build model? I am assuming it redirects into home with current workflow expanded Thanks. On Wed, Dec 17, 2014 at 12:14 PM, Dhanuka De Silva dhanu...@wso2.com wrote: Hi All Proposed UXD/workflow mockups for ML Tool is shared in the below location. Hope these are self explanatory and are based on last few discussion had with team. Feel free to ask if you need any clarification. https://drive.google.com/a/wso2.com/folderview?id=0B4eoLHAhQ246c1NBZWlDQXpjVTgusp=sharing *Order to navigate* ML-1-landing-no-projects (Landing page with no existing projects created) ML-2-landing-with-existing-projects (Landing page with few existing projects and their workflows) ML-3-create-project (Creating a new project) ML-4-project-created (Project is created. Providing feedback for next steps) ML-5-Wizard-Step-1 (Creating a Workflow - Wizard Step 1) ML-6-Wizard-Step-2-a (Selecting and pre-process data - Wizard Step 2) ML-7-Wizard-Step-2-b (Explore existing data - Wizard Step 2) ML-8-Wizard-Step-3 (Select an Algorithm type - Wizard Step 3) ML-9-Wizard-Step-4 (Select an Algorithm from the list or/Suggested Algorithms if Skipped using HELP button from Step 3 - Wizard Step 4) ML-10-Wizard-Step-5-final (Modify parameters for the selected Algorithm - Wizard Step 5) Cheers -- Dhanuka De Silva m: +94 773 887816 e: dhanu...@wso2.com w: http://www.wso2.com -- Lochana Menikarachchi Senior Tech Lead WSO2 Inc. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [AF] [MB] Make Appfactory tenant subscription to stratos environments fault tolerant
Hi Harsha, I see your point. If you follow tenant creation bpel you may see initializeBuildManager and initializeRepositoryManager happens one after the other in a row. If it got failed in any step the process won't continue. But in last step of bpel you can see that initializeCloudManager is called for all 3 environments at the same time. In order to consider tenant creation as successfull we need to have all 3 subscriptions successful. I think thats why this fault tolerance mechanism is more important in this step than others. Anyway I will discuss more with the team and will update this thread. On Wed, Dec 17, 2014 at 2:45 PM, Harsha Thirimanna hars...@wso2.com wrote: Hi Mahesh, What about the other failure situation within BPEL, like initializeBuildManager and initializeRepositoryManager. Can we do that also consuming this topics ? Because that also mandatory for the tenant creation flow. WDYT ? thanks *Harsha Thirimanna* Senior Software Engineer; WSO2, Inc.; http://wso2.com * http://www.apache.org/* *email: **hars...@wso2.com* az...@wso2.com* cell: +94 71 5186770 , +94 * *774617784twitter: **http://twitter.com/ http://twitter.com/afkham_azeez* *harshathirimannlinked-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 Wed, Dec 17, 2014 at 1:31 PM, Mahesh Chinthaka mahe...@wso2.com wrote: Hi all, Im working on Making the tenants subscription to stratos environments fault tolerant [1] This has been discussed in mail thread with subject - [Architecture] [AF] Tenant subscribing to stratos environments - making it fault tolerant *Issue* ** There are some possible failure points in AF, hence in App Cloud. One such critical point is making the tenants subscribed to the dev, test and prod stratos environments. Due to any reason, if this step fails, then, thats the end of story for that tenant. Actually in appfactory tenant creation, When a tenant creation request is made, appfactory sends REST calls to stratos environments (dev,prod,test) to create tenants. At the moment there is no way to overcome a situation where tenant creation fails in one or more stratos environments. *Proposal* *===* Here what I'm going to do is, integrate WSO2 Message Broker to take tenant creation requests to a durable topic and manipulate the process in a fault tolerant manner. The durable topic will keep messages around persistently for any suitable consumer to consume them. Appfactory will have a publisher who publishes messages in the topic inside MB when a tenant creation is requested. There will be a subscriber for each stratos environment who is listening to above topic(create_teanant). If subscription is successfull then subscriber will acknowledge to MB and MB will not send that particular request to same subscriber again. If subscription got failed subscriber will not ack. and MB will take care of sending that request until it becomes successful. At the moment we have 3 stratos environments therefore we will have 3 subscribers listening to that particular topic(create_teanant) in MB. In a case of AF having more stratos environments in future, it is possible to add more subscribers. Durable topic subscribers[2] will be used here since it will persist the subscription on behalf of the client subscription when client is not online. This step is not synchronous therefore above changes will not effect the tenant creation flow. *Architectural diagram * *=* Architectural diagram can be found in [3] [1] - https://wso2.org/jira/browse/APPFAC-2436 [2] - https://docs.wso2.com/display/MB220/Creating+a+Durable+Topic+Subscription [3] - https://docs.google.com/a/wso2.com/drawings/d/15CmM3rCTwjUUu4V6lp2WX32nRzufraDXawALNYIoTek/edit -- *Mahesh Chinthaka Vidanagama* | Software Engineer WSO2, Inc | lean. enterprise. middleware. #20, Palm Grove, Colombo 03, Sri Lanka Mobile: +94 71 63 63 083 | Work: +94 112 145 345 Email: mahe...@wso2.com | Web: www.wso2.com ___ 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 -- *Mahesh Chinthaka Vidanagama* | Software Engineer WSO2, Inc | lean. enterprise. middleware. #20, Palm Grove, Colombo 03, Sri Lanka Mobile: +94 71 63 63 083 | Work: +94 112 145 345 Email: mahe...@wso2.com | Web: www.wso2.com ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] [Dev][G-Reg]Copy to new version functionality in G-Reg
Hi On Wed, Dec 17, 2014 at 2:23 PM, Isuruwan Herath isuru...@wso2.com wrote: [moved to architecture] Hi Sameera, Please see the comments inline. On Mon, Dec 15, 2014 at 11:00 PM, Sameera Kannangara samee...@wso2.com wrote: Hi all, $Subject refers to the functionality required to fulfill the following scenario in G-Reg 5.0.0. [1] Scenario: User should be able to copy existing resource to new version. Lets say a user has a service in GREG which is attached with a life cycle, and the service is in production life cycle state. User develops a new version of the same service, and he wants to add those meta data to the GREG. Rather than adding them from the beginning, He should be able to copy the existing resource and it's associations to a new version, except life cycle state, life cycle state should be the first state of the associated life cycle. In current service LC functionality, the copy executor will anyway create a new artifact with next version. Hence, if this clone functionality is required to access an copy of certain life cycle state it will exist anyway. Otherwise, if this copy function is used to refer a new service with similar metadata, then, is correct to have the same associations and dependencies (with same versions) in the cloned artifact? IMO there should not be a copy executor, because executors run in the life cycle events. I don't think there is a use case to change the version of the resource within the life cycle. If resource changes the version, then it should be a new life cycle. In the current copy executor it changes the version in the within the life cycle (Ex: Version of the service can be changed to new version using executor when life cycle state of the resource changes from dev to test). IMO having this copy functionality in the life cycle is wrong. Rationale for this requirement is that it reduces the time and effort required to create a new version of an existing service, by removing the time and effort needed to fill all the detail necessary to create the service. This functionality is not supported by the G-Reg's existing copy functionality as it operates on generic resource level. As this requirement is related to governance artifacts (more specifically regarding services) I'm checking how this can be implemented, how user can invoke this functionality and to which package the new functionality should be added. Regarding the scope of this functionality, What are the Extension types which should support this functionality other than Service? I think this must be a generic functionality and should be associated with all extension types. This copy functionality should copy the resource and all it's associated resources to new version. Is this functionality a generic one associated with any extension type that has a version field? IMO, we can allow this functionality for any artifact types with a version, if we make this available for Service. Thank you, SameeraK. [1] https://redmine.wso2.com/issues/2751 -- *Sameera Kannangara* Software Engineer Platform TG; WSO2 Inc. http://wso2.com Contact: phone: +94719541577 Lean . Enterprise . Middleware -- Isuruwan Herath Technical Lead Contact: +94 776 273 296 ___ 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] Notification Management Component and Notification Sending Components.
You mean notification management component parse common configuration file and pass relevant configurations to the notification sending modules at the time of registering Yes, Management component passes the relevant configurations and initialize them. or notification sending modules retrieve required configurations from the management module at the real time? Notification Sending Modules do not retrieve configurations themselves. If configurations are injected to relevant notification module at the time of registering, do we need to restart the notification sending OSGI bundles to effect any configuration changes? Yes, Anyway configurations are only effective after restarting. On Wed, Dec 17, 2014 at 10:09 AM, Hasintha Indrajee hasin...@wso2.com wrote: Hi Prabath, The reason behind using a single configuration file is to avoid the complexity of maintaining multiple configuration files and at the same time, since the configuration parsing is done in a central module and passes relevant configurations to relevant Notification Sending modules, Notification Sending components do not need to build their own configuration parses. Instead they can be initiated from the configuration passed by the management module. At the same time, with this implementation, Notification Sending modules can have/maintain their own configuration files as well. On Tue, Dec 16, 2014 at 9:14 PM, Prabath Ariyarathna prabat...@wso2.com wrote: Hi Hasitha. Is there are any special reason to use single configuration file for all Notification sending modules instead of using a separate file for each component? Regard, On Tue, Dec 16, 2014 at 7:57 PM, Hasintha Indrajee hasin...@wso2.com wrote: Adding image *An Overview of the Architecture * On Tue, Dec 16, 2014 at 7:51 PM, Hasintha Indrajee hasin...@wso2.com wrote: Hi all, The idea is to implement a generic and light weight Notification Management module which is responsible for registering Notification Sending modules dynamically, initialize them with relevant configurations, and trigger the notification sending module on a particular event type if the particular event type is subscribed by a Notification Sending module. E.g. suppose we need to call a REST endpoint with JSON content (PEP) on an event of XACML policy update. The event is published to Notification Management Component by the XACML component, which will trigger REST/JSON notification sending module with the published event. *Notification Management Component* - Exposes an interface for Notification Sending modules to register and publish events. [1] - Events are mediated from this management Component. - Events published by publishers are queued and distributed to Notification Sending modules asynchronously using a configurable size thread pool. - Events are published to Notification Sending Modules only if the particular module is subscribed to the published event. - Holds a common configuration file for all Notification Sending modules and builds it at the time of initialization. At the time of registering a Notification Sending module, it will be initialized using relevant configurations to particular module. - This configuration file is secured using secure vault. A sample Configuration file is included below. *A Notification Sending Module (Email Message Module, REST/JSON module, SMS module)* - Modules are implemented and registered as OSGi services. New Notification Sending Modules can be implemented and registered as per requirements (e.g. - SMS sending module). - A module can subscribe for several events. Each module is configurable per event type. - The two existing modules (Email, REST/JSON) have configurable endpoints per event type and configurable templates per event type and endpoint. These templates have place holders which will be replaced by configurations from module level, subscription level and published event information respectively. *An Overview to the Architecture. * ** Following is a sample configuration property file which is read by Notification Management Component. This could be used to hold properties for all Notification Sending Modules, and will be passed relevant properties to the init() method upon initialization. Sensitive information is encrypted using secure vault. # name of the notification sending module module.name.1=email # name of the subscription email.subscription.1=userOperation # subscription properties email.subscription.userOperation.template=templatePath/template1 email.subscription.userOperation.salutation=Admin email.subscription.userOperation.subject=User operation change information # name of the endpoint email.subscription.userOperation.endpoint.1=privateMail # endpoint properties email.subscription.userOperation.endpoint.privateMail.address=
Re: [Architecture] [AF] [MB] Make Appfactory tenant subscription to stratos environments fault tolerant
Hi Mahesh, +1 for the current design. I assume you have multiple instances of durable subscribers for each subscription made to Stratos cartridges. For example, if we have multiple tenant aware cartridges(App Server, UES Server, BPS Server etc), the durable subscriber should be able to instantiate based on subscription details for each cartridges in all the environments. Further we can consider unsubscribing from cartridges etc. Based on the message received by the topic subscribers, topic subscriber can decide the action plan(subscribe to cartridge, unsubscribe,etc). In case of failure, lets assume subscription to production app server cartridges is failed. Are we going to stop further actions in that particular tenant such as avoiding promoting to production? IMO, notifying to the tenant administrator and system administrators would be sufficient via notification mechanisms(wall,email). thank you. On Wed, Dec 17, 2014 at 3:16 PM, Mahesh Chinthaka mahe...@wso2.com wrote: Hi Harsha, I see your point. If you follow tenant creation bpel you may see initializeBuildManager and initializeRepositoryManager happens one after the other in a row. If it got failed in any step the process won't continue. But in last step of bpel you can see that initializeCloudManager is called for all 3 environments at the same time. In order to consider tenant creation as successfull we need to have all 3 subscriptions successful. I think thats why this fault tolerance mechanism is more important in this step than others. Anyway I will discuss more with the team and will update this thread. On Wed, Dec 17, 2014 at 2:45 PM, Harsha Thirimanna hars...@wso2.com wrote: Hi Mahesh, What about the other failure situation within BPEL, like initializeBuildManager and initializeRepositoryManager. Can we do that also consuming this topics ? Because that also mandatory for the tenant creation flow. WDYT ? thanks *Harsha Thirimanna* Senior Software Engineer; WSO2, Inc.; http://wso2.com * http://www.apache.org/* *email: **hars...@wso2.com* az...@wso2.com* cell: +94 71 5186770 , +94 * *774617784twitter: **http://twitter.com/ http://twitter.com/afkham_azeez* *harshathirimannlinked-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 Wed, Dec 17, 2014 at 1:31 PM, Mahesh Chinthaka mahe...@wso2.com wrote: Hi all, Im working on Making the tenants subscription to stratos environments fault tolerant [1] This has been discussed in mail thread with subject - [Architecture] [AF] Tenant subscribing to stratos environments - making it fault tolerant *Issue* ** There are some possible failure points in AF, hence in App Cloud. One such critical point is making the tenants subscribed to the dev, test and prod stratos environments. Due to any reason, if this step fails, then, thats the end of story for that tenant. Actually in appfactory tenant creation, When a tenant creation request is made, appfactory sends REST calls to stratos environments (dev,prod,test) to create tenants. At the moment there is no way to overcome a situation where tenant creation fails in one or more stratos environments. *Proposal* *===* Here what I'm going to do is, integrate WSO2 Message Broker to take tenant creation requests to a durable topic and manipulate the process in a fault tolerant manner. The durable topic will keep messages around persistently for any suitable consumer to consume them. Appfactory will have a publisher who publishes messages in the topic inside MB when a tenant creation is requested. There will be a subscriber for each stratos environment who is listening to above topic(create_teanant). If subscription is successfull then subscriber will acknowledge to MB and MB will not send that particular request to same subscriber again. If subscription got failed subscriber will not ack. and MB will take care of sending that request until it becomes successful. At the moment we have 3 stratos environments therefore we will have 3 subscribers listening to that particular topic(create_teanant) in MB. In a case of AF having more stratos environments in future, it is possible to add more subscribers. Durable topic subscribers[2] will be used here since it will persist the subscription on behalf of the client subscription when client is not online. This step is not synchronous therefore above changes will not effect the tenant creation flow. *Architectural diagram * *=* Architectural diagram can be found in [3] [1] - https://wso2.org/jira/browse/APPFAC-2436 [2] - https://docs.wso2.com/display/MB220/Creating+a+Durable+Topic+Subscription [3] - https://docs.google.com/a/wso2.com/drawings/d/15CmM3rCTwjUUu4V6lp2WX32nRzufraDXawALNYIoTek/edit -- *Mahesh Chinthaka Vidanagama* |
Re: [Architecture] Machine Learner - Proposed UX
Old UI had that sort of a workflow.. UX team suggested to avoid a wizard inside a wizard for better user experience.. On Wed, Dec 17, 2014 at 12:49 PM, Sriskandarajah Suhothayan s...@wso2.com wrote: I have a feeling its better to have Algorithm type and Algorithm in the same level as Algorithm, and then have a tab inside to see all algos to select one, and another tab to help selecting one algo from recommendations. Regards Suho On Wed, Dec 17, 2014 at 12:38 PM, Lochana Menikarachchi loch...@wso2.com wrote: In step 8/9, we ask the questions by default. The user has the option to skip and go to the all algorithms view. What happens after clicking on the build model? I am assuming it redirects into home with current workflow expanded Thanks. On Wed, Dec 17, 2014 at 12:14 PM, Dhanuka De Silva dhanu...@wso2.com wrote: Hi All Proposed UXD/workflow mockups for ML Tool is shared in the below location. Hope these are self explanatory and are based on last few discussion had with team. Feel free to ask if you need any clarification. https://drive.google.com/a/wso2.com/folderview?id=0B4eoLHAhQ246c1NBZWlDQXpjVTgusp=sharing *Order to navigate* ML-1-landing-no-projects (Landing page with no existing projects created) ML-2-landing-with-existing-projects (Landing page with few existing projects and their workflows) ML-3-create-project (Creating a new project) ML-4-project-created (Project is created. Providing feedback for next steps) ML-5-Wizard-Step-1 (Creating a Workflow - Wizard Step 1) ML-6-Wizard-Step-2-a (Selecting and pre-process data - Wizard Step 2) ML-7-Wizard-Step-2-b (Explore existing data - Wizard Step 2) ML-8-Wizard-Step-3 (Select an Algorithm type - Wizard Step 3) ML-9-Wizard-Step-4 (Select an Algorithm from the list or/Suggested Algorithms if Skipped using HELP button from Step 3 - Wizard Step 4) ML-10-Wizard-Step-5-final (Modify parameters for the selected Algorithm - Wizard Step 5) Cheers -- Dhanuka De Silva m: +94 773 887816 e: dhanu...@wso2.com w: http://www.wso2.com -- Lochana Menikarachchi Senior Tech Lead WSO2 Inc. -- *S. Suhothayan* Technical Lead Team Lead of WSO2 Complex Event Processor *WSO2 Inc. *http://wso2.com * http://wso2.com/* lean . enterprise . middleware *cell: (+94) 779 756 757 %28%2B94%29%20779%20756%20757 | blog: http://suhothayan.blogspot.com/ http://suhothayan.blogspot.com/twitter: http://twitter.com/suhothayan http://twitter.com/suhothayan | linked-in: http://lk.linkedin.com/in/suhothayan http://lk.linkedin.com/in/suhothayan* -- Lochana Menikarachchi Senior Tech Lead WSO2 Inc. ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] Machine Learner - Proposed UX
Suho's comment makes sense. Lets see what we can do about it without affecting the workflow and consistency (without having to run two wizard navigation). Cheers On Thu, Dec 18, 2014 at 8:47 AM, Lochana Menikarachchi loch...@wso2.com wrote: Old UI had that sort of a workflow.. UX team suggested to avoid a wizard inside a wizard for better user experience.. On Wed, Dec 17, 2014 at 12:49 PM, Sriskandarajah Suhothayan s...@wso2.com wrote: I have a feeling its better to have Algorithm type and Algorithm in the same level as Algorithm, and then have a tab inside to see all algos to select one, and another tab to help selecting one algo from recommendations. Regards Suho On Wed, Dec 17, 2014 at 12:38 PM, Lochana Menikarachchi loch...@wso2.com wrote: In step 8/9, we ask the questions by default. The user has the option to skip and go to the all algorithms view. What happens after clicking on the build model? I am assuming it redirects into home with current workflow expanded Thanks. On Wed, Dec 17, 2014 at 12:14 PM, Dhanuka De Silva dhanu...@wso2.com wrote: Hi All Proposed UXD/workflow mockups for ML Tool is shared in the below location. Hope these are self explanatory and are based on last few discussion had with team. Feel free to ask if you need any clarification. https://drive.google.com/a/wso2.com/folderview?id=0B4eoLHAhQ246c1NBZWlDQXpjVTgusp=sharing *Order to navigate* ML-1-landing-no-projects (Landing page with no existing projects created) ML-2-landing-with-existing-projects (Landing page with few existing projects and their workflows) ML-3-create-project (Creating a new project) ML-4-project-created (Project is created. Providing feedback for next steps) ML-5-Wizard-Step-1 (Creating a Workflow - Wizard Step 1) ML-6-Wizard-Step-2-a (Selecting and pre-process data - Wizard Step 2) ML-7-Wizard-Step-2-b (Explore existing data - Wizard Step 2) ML-8-Wizard-Step-3 (Select an Algorithm type - Wizard Step 3) ML-9-Wizard-Step-4 (Select an Algorithm from the list or/Suggested Algorithms if Skipped using HELP button from Step 3 - Wizard Step 4) ML-10-Wizard-Step-5-final (Modify parameters for the selected Algorithm - Wizard Step 5) Cheers -- Dhanuka De Silva m: +94 773 887816 e: dhanu...@wso2.com w: http://www.wso2.com -- Lochana Menikarachchi Senior Tech Lead WSO2 Inc. -- *S. Suhothayan* Technical Lead Team Lead of WSO2 Complex Event Processor *WSO2 Inc. *http://wso2.com * http://wso2.com/* lean . enterprise . middleware *cell: (+94) 779 756 757 %28%2B94%29%20779%20756%20757 | blog: http://suhothayan.blogspot.com/ http://suhothayan.blogspot.com/twitter: http://twitter.com/suhothayan http://twitter.com/suhothayan | linked-in: http://lk.linkedin.com/in/suhothayan http://lk.linkedin.com/in/suhothayan* -- Lochana Menikarachchi Senior Tech Lead WSO2 Inc. -- 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
Re: [Architecture] [Dev][G-Reg]Copy to new version functionality in G-Reg
Hi Sameera, On Wed, Dec 17, 2014 at 3:22 PM, Geeth Munasinghe ge...@wso2.com wrote: Hi On Wed, Dec 17, 2014 at 2:23 PM, Isuruwan Herath isuru...@wso2.com wrote: [moved to architecture] Hi Sameera, Please see the comments inline. On Mon, Dec 15, 2014 at 11:00 PM, Sameera Kannangara samee...@wso2.com wrote: Hi all, $Subject refers to the functionality required to fulfill the following scenario in G-Reg 5.0.0. [1] Scenario: IIRC, this was discussed sometime ago and the idea was to have a copy button next to the save button of a governance artifact(any rxt). The idea back then was to extent the RXT configuration language so that a user can define actions(buttons in UI) and add his/her own custom implementation of that action. As an example, the default 2 actions for a governance artifact is save and clear. With the above mentioned change, a user can define a new action copy in the RXT configuration and then add his implementation of that(like we have done for custom executors in lifecycles) User should be able to copy existing resource to new version. Lets say a user has a service in GREG which is attached with a life cycle, and the service is in production life cycle state. User develops a new version of the same service, and he wants to add those meta data to the GREG. Rather than adding them from the beginning, He should be able to copy the existing resource and it's associations to a new version, except life cycle state, life cycle state should be the first state of the associated life cycle. IIRC, we only have versions from Testing state onward and the Development state only has one version which is the trunk. So the lifecycle state should not be the first state of the lifecyle. Hence the copy functionality should prompt for the new version that needs to be created and we should place it in a different state. Please define the usecases clearly so that we can understand the exact usages of this functionality. In current service LC functionality, the copy executor will anyway create a new artifact with next version. Hence, if this clone functionality is required to access an copy of certain life cycle state it will exist anyway. Otherwise, if this copy function is used to refer a new service with similar metadata, then, is correct to have the same associations and dependencies (with same versions) in the cloned artifact? Is this the copy executor or the service version executor? AFAIK, the copy executor does not do any version change and only the service version executor(which does a copy of an artifact to a new location and changes its version too) does that functionality. Thanks, Janaka IMO there should not be a copy executor, because executors run in the life cycle events. I don't think there is a use case to change the version of the resource within the life cycle. If resource changes the version, then it should be a new life cycle. In the current copy executor it changes the version in the within the life cycle (Ex: Version of the service can be changed to new version using executor when life cycle state of the resource changes from dev to test). IMO having this copy functionality in the life cycle is wrong. Rationale for this requirement is that it reduces the time and effort required to create a new version of an existing service, by removing the time and effort needed to fill all the detail necessary to create the service. This functionality is not supported by the G-Reg's existing copy functionality as it operates on generic resource level. As this requirement is related to governance artifacts (more specifically regarding services) I'm checking how this can be implemented, how user can invoke this functionality and to which package the new functionality should be added. Regarding the scope of this functionality, What are the Extension types which should support this functionality other than Service? I think this must be a generic functionality and should be associated with all extension types. This copy functionality should copy the resource and all it's associated resources to new version. Is this functionality a generic one associated with any extension type that has a version field? IMO, we can allow this functionality for any artifact types with a version, if we make this available for Service. Thank you, SameeraK. [1] https://redmine.wso2.com/issues/2751 -- *Sameera Kannangara* Software Engineer Platform TG; WSO2 Inc. http://wso2.com Contact: phone: +94719541577 Lean . Enterprise . Middleware -- Isuruwan Herath Technical Lead Contact: +94 776 273 296 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture ___ Architecture mailing list Architecture@wso2.org
Re: [Architecture] Machine Learner - Proposed UX
Hi All I have updated the mockups based on the chat I had with Lochana in the morning. Hope the page flow is much clear now. *@Suho*, we have merged Algorithm Type and Algorithm in to the same level based on your feedback (We adjusted it without using tabs.Having tabs in this level makes things more confusing - when you have tabs, you are able to switch in between them and select data from both of the views and click NEXT, making the confusing of from which tab you are submitting data to the next step.) https://drive.google.com/a/wso2.com/folderview?id=0B4eoLHAhQ246c1NBZWlDQXpjVTgusp=sharing#list Cheers On Thu, Dec 18, 2014 at 8:51 AM, Dhanuka De Silva dhanu...@wso2.com wrote: Suho's comment makes sense. Lets see what we can do about it without affecting the workflow and consistency (without having to run two wizard navigation). Cheers On Thu, Dec 18, 2014 at 8:47 AM, Lochana Menikarachchi loch...@wso2.com wrote: Old UI had that sort of a workflow.. UX team suggested to avoid a wizard inside a wizard for better user experience.. On Wed, Dec 17, 2014 at 12:49 PM, Sriskandarajah Suhothayan s...@wso2.com wrote: I have a feeling its better to have Algorithm type and Algorithm in the same level as Algorithm, and then have a tab inside to see all algos to select one, and another tab to help selecting one algo from recommendations. Regards Suho On Wed, Dec 17, 2014 at 12:38 PM, Lochana Menikarachchi loch...@wso2.com wrote: In step 8/9, we ask the questions by default. The user has the option to skip and go to the all algorithms view. What happens after clicking on the build model? I am assuming it redirects into home with current workflow expanded Thanks. On Wed, Dec 17, 2014 at 12:14 PM, Dhanuka De Silva dhanu...@wso2.com wrote: Hi All Proposed UXD/workflow mockups for ML Tool is shared in the below location. Hope these are self explanatory and are based on last few discussion had with team. Feel free to ask if you need any clarification. https://drive.google.com/a/wso2.com/folderview?id=0B4eoLHAhQ246c1NBZWlDQXpjVTgusp=sharing *Order to navigate* ML-1-landing-no-projects (Landing page with no existing projects created) ML-2-landing-with-existing-projects (Landing page with few existing projects and their workflows) ML-3-create-project (Creating a new project) ML-4-project-created (Project is created. Providing feedback for next steps) ML-5-Wizard-Step-1 (Creating a Workflow - Wizard Step 1) ML-6-Wizard-Step-2-a (Selecting and pre-process data - Wizard Step 2) ML-7-Wizard-Step-2-b (Explore existing data - Wizard Step 2) ML-8-Wizard-Step-3 (Select an Algorithm type - Wizard Step 3) ML-9-Wizard-Step-4 (Select an Algorithm from the list or/Suggested Algorithms if Skipped using HELP button from Step 3 - Wizard Step 4) ML-10-Wizard-Step-5-final (Modify parameters for the selected Algorithm - Wizard Step 5) Cheers -- Dhanuka De Silva m: +94 773 887816 e: dhanu...@wso2.com w: http://www.wso2.com -- Lochana Menikarachchi Senior Tech Lead WSO2 Inc. -- *S. Suhothayan* Technical Lead Team Lead of WSO2 Complex Event Processor *WSO2 Inc. *http://wso2.com * http://wso2.com/* lean . enterprise . middleware *cell: (+94) 779 756 757 %28%2B94%29%20779%20756%20757 | blog: http://suhothayan.blogspot.com/ http://suhothayan.blogspot.com/twitter: http://twitter.com/suhothayan http://twitter.com/suhothayan | linked-in: http://lk.linkedin.com/in/suhothayan http://lk.linkedin.com/in/suhothayan* -- Lochana Menikarachchi Senior Tech Lead WSO2 Inc. -- Dhanuka De Silva m: +94 773 887816 e: dhanu...@wso2.com w: http://www.wso2.com -- 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
Re: [Architecture] Machine Learner - Proposed UX
Thanks for the feedback guys! I will start working on the html stuff. Cheers On Thu, Dec 18, 2014 at 12:33 PM, Lochana Menikarachchi loch...@wso2.com wrote: Looks good.. On Thu, Dec 18, 2014 at 12:30 PM, Sriskandarajah Suhothayan s...@wso2.com wrote: On Thu, Dec 18, 2014 at 12:04 PM, Dhanuka De Silva dhanu...@wso2.com wrote: Hi All I have updated the mockups based on the chat I had with Lochana in the morning. Hope the page flow is much clear now. *@Suho*, we have merged Algorithm Type and Algorithm in to the same level based on your feedback (We adjusted it without using tabs.Having tabs in this level makes things more confusing - when you have tabs, you are able to switch in between them and select data from both of the views and click NEXT, making the confusing of from which tab you are submitting data to the next step.) That's great it look more intuitive for me Suho https://drive.google.com/a/wso2.com/folderview?id=0B4eoLHAhQ246c1NBZWlDQXpjVTgusp=sharing#list Cheers On Thu, Dec 18, 2014 at 8:51 AM, Dhanuka De Silva dhanu...@wso2.com wrote: Suho's comment makes sense. Lets see what we can do about it without affecting the workflow and consistency (without having to run two wizard navigation). Cheers On Thu, Dec 18, 2014 at 8:47 AM, Lochana Menikarachchi loch...@wso2.com wrote: Old UI had that sort of a workflow.. UX team suggested to avoid a wizard inside a wizard for better user experience.. On Wed, Dec 17, 2014 at 12:49 PM, Sriskandarajah Suhothayan s...@wso2.com wrote: I have a feeling its better to have Algorithm type and Algorithm in the same level as Algorithm, and then have a tab inside to see all algos to select one, and another tab to help selecting one algo from recommendations. Regards Suho On Wed, Dec 17, 2014 at 12:38 PM, Lochana Menikarachchi loch...@wso2.com wrote: In step 8/9, we ask the questions by default. The user has the option to skip and go to the all algorithms view. What happens after clicking on the build model? I am assuming it redirects into home with current workflow expanded Thanks. On Wed, Dec 17, 2014 at 12:14 PM, Dhanuka De Silva dhanu...@wso2.com wrote: Hi All Proposed UXD/workflow mockups for ML Tool is shared in the below location. Hope these are self explanatory and are based on last few discussion had with team. Feel free to ask if you need any clarification. https://drive.google.com/a/wso2.com/folderview?id=0B4eoLHAhQ246c1NBZWlDQXpjVTgusp=sharing *Order to navigate* ML-1-landing-no-projects (Landing page with no existing projects created) ML-2-landing-with-existing-projects (Landing page with few existing projects and their workflows) ML-3-create-project (Creating a new project) ML-4-project-created (Project is created. Providing feedback for next steps) ML-5-Wizard-Step-1 (Creating a Workflow - Wizard Step 1) ML-6-Wizard-Step-2-a (Selecting and pre-process data - Wizard Step 2) ML-7-Wizard-Step-2-b (Explore existing data - Wizard Step 2) ML-8-Wizard-Step-3 (Select an Algorithm type - Wizard Step 3) ML-9-Wizard-Step-4 (Select an Algorithm from the list or/Suggested Algorithms if Skipped using HELP button from Step 3 - Wizard Step 4) ML-10-Wizard-Step-5-final (Modify parameters for the selected Algorithm - Wizard Step 5) Cheers -- Dhanuka De Silva m: +94 773 887816 e: dhanu...@wso2.com w: http://www.wso2.com -- Lochana Menikarachchi Senior Tech Lead WSO2 Inc. -- *S. Suhothayan* Technical Lead Team Lead of WSO2 Complex Event Processor *WSO2 Inc. *http://wso2.com * http://wso2.com/* lean . enterprise . middleware *cell: (+94) 779 756 757 %28%2B94%29%20779%20756%20757 | blog: http://suhothayan.blogspot.com/ http://suhothayan.blogspot.com/twitter: http://twitter.com/suhothayan http://twitter.com/suhothayan | linked-in: http://lk.linkedin.com/in/suhothayan http://lk.linkedin.com/in/suhothayan* -- Lochana Menikarachchi Senior Tech Lead WSO2 Inc. -- Dhanuka De Silva m: +94 773 887816 e: dhanu...@wso2.com w: http://www.wso2.com -- Dhanuka De Silva m: +94 773 887816 e: dhanu...@wso2.com w: http://www.wso2.com -- *S. Suhothayan* Technical Lead Team Lead of WSO2 Complex Event Processor *WSO2 Inc. *http://wso2.com * http://wso2.com/* lean . enterprise . middleware *cell: (+94) 779 756 757 %28%2B94%29%20779%20756%20757 | blog: http://suhothayan.blogspot.com/ http://suhothayan.blogspot.com/twitter: http://twitter.com/suhothayan http://twitter.com/suhothayan | linked-in: http://lk.linkedin.com/in/suhothayan http://lk.linkedin.com/in/suhothayan* -- Lochana Menikarachchi Senior Tech Lead WSO2 Inc. -- 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
