MoMs \ MON-FRI \ 12th-16th DEC 2016

[peeyush-tm]

Time 12:00 PM - 2:30 PM

@veris-abhinavanand @veris-amoghbanta - complete the requirements for #16 Order fulfillment Work Details for V2

@veris-ankitpopli @veris-neerajdhiman - we need to bring the system together - Hello World !

System Concepts

Concept	Where it fits?	What Software?	Commercial
Widgets and Processes ( @veris-ankitpopli you were right about the orchestration theory)	Configurable processes set by the Org Admin	Storm St2	AWS Lambda
API Gateway	Manage the API endpoints to various services	Kong	Marketplace Kong
Message Queues	To enable pub/sub between the process and widget	Redis/ Kafka	~NA~
Process Gateway	Manage the process call and authentication of veris runtime	~NA~

System Components

Veris Systems	Use
Admin Panel	Member Management, Organization Management, Process Management, Widget Management
User Management	User Onboarding, User Profile Management
Veris Runtime	Serve Instant Apps to the user

System Architecture

The Veris Widget/ Process Workflow

[Veris Runtime] -------> [ Process Gateway ]
1. (widget call)                  1.  authenticate the VRT
                                          1.  authenticate the Widget
                                          1.  authenticate the Widget Data Request
                                          1. Checks for SESSION ID or creates one
                                          1.  Forwards request to  [Process Executioner (ST2)]
                              <------2.  Responds back to the Veris Runtime with #SESSION ID for pub/sub
2. subscribe to the          
#SESSION ID pub/sub (.....LISTEN......)

[ Process Gateway ] ------> [Process Executioner]
3. Calls Process                     3. start execution
                                                3. call the [API Gateway]
                                                3. enrich the response from API GATEWAY data 
                                    <----- 4. on completion/ on error send data to #SESSION ID pub/sub
4. Veris runtime reads the data from #SESSION ID pub/sub (.....LISTEN......)

[ Process Gateway ] ------> [API Gateway]
call with data            <------ respond with data

The Veris Admin Architecture Flow

[Veris Admin] -------- (register resource on API Gateway) -----> API Gateway
[Veris Admin] -------- (register process on Proces Executioner) -----> [Process Executioner (ST2)]
[Veris Admin] -------- (register Veris Runtime) -----> [Runtime]
[Veris Admin] -------- (register Members) -----> [Organization/ Members/ Users]
[Veris Admin] -------- (register Processes on Process Gateway) -----> [Process Gateway]

Widget data sharing

1. based on the scope of the data
   1. managed by the Process Gateway
   2. managed by the Veris Runtime
2. Same sharing rules as we had discussed previously
   1. same data point will be shared by all the widgets (eg: user.user_name: unique data key)
   2. all the widgets can override their own instance of the data
   3. final version of the required data can also be created

      
      eg: 
      widget1 = {
      widget_name="who are you",
      user.user_name = "Jim"
      }
      widget2 = {
      widget_name="whom to meet"
      user.user_name = "Joddy"
      user.is_member = False
      }

Same keys can be shared between the widgets, but the data can be separate. Final data entry in the KEEN would be

widget1 = { widget_name="who are you", user.user_name = "Jim" user.is_member = False } widget2 = { widget_name="whom to meet" user.user_name = "Joddy" user.is_member = True } widget3= { widget_name="action" action.action = "check in" action.time = 12:00 PM }

Multiple widgets can have same keys registered to them, that will share the data, but the data is a local copy per widget

😄💡 Android type service registration, with Intent as API `i am good 😎 `

# Work Details till Friday

1. Bring V3 Together @veris-neerajdhiman @veris-ankitpopli 
    1. api gateway
    2. process gateway
    3. admin panel
    4. user management
    5. process executioner
    6. mobile
1. V3 work @veris-neerajdhiman @veris-ankitpopli 
    1. widget => hello world
    1. widget => hello "John"
1. V2 complete @veris-amoghbanta @veris-abhinavanand 
    1. Ref #16 
1. V2 Start with User App @veris-amoghbanta @veris-abhinavanand 

**Are we?**
![quality of work -2](https://cloud.githubusercontent.com/assets/5212023/21095915/8e38dc44-c083-11e6-8d20-879fee75f062.png)

# MoM - TUE - 13th DEC 2016

@veris-abhinavanand @veris-amoghbanta - wrap it up. start with V2 user app, using react native framework for cross-compilations.
Train the new trainee and evaluate per month basis 
(if he proves to be better than "you know who (all)" - we would let him be part of the team, else we would have least helped in his career (elsewhere))
- html/ js/ css => V2 portal
- jquery/ js => V2 portal
- react js / frontend => V2 portal

If he tops the minimum entry barrier- 
- react / redux
- react-native

@veris-ankitpopli @veris-ankitpopli - explore the rules execution and process handover for StormSt2
Everything is a form! => Client Side

[================== shared data caching ===================] [Veris Runtime] => [ Process Gateway ] => [ Process ] <=> [ API Gateway ] [================= shared message queue =================] [====================== shared logs =====================]

` [ Process Gateway ] ` - serialization and authentication layer
- validates the call before initiating the process
- validates the client calling the process
- generates request-id for reference
- manages the channel in MQ

# MoM - WED - 14th DEC 2016

1. Mistral - workflow as a service - open foundry 
1. horizon - django dashboard for managing mistral
1. kong
    1. api gateway. 
        - manage authentication and authorization of api
    1. process gateway
        - manage authentication and authorization of VRT, widget
1. RabbitMQ
1. ST2 - rules. protocols/ actions. trigger
1. Microservices
    - auth - all auth
        - user
    - org
        - member
    - invite
    - notification
    - mfa
    - keen
1. admin panel to manage the ecosystem
    - wicked.io
1. widget -> mistral
1. widget -> process -> mistral
1. process -> mistral
1. mistral to manage states
1. all the components of the platform, would perform, very specific task. no overlap of tasks.
1. @veris-neerajdhiman - good job on making things configurable in r&d repo 👍 

# MoM - THU - 15th DEC 2016

1. reverse engineer process calling - st2 
1. reverse engineer process registration - st2 
1. reverse engineer - st2 
    - mongodb
    - rabbit mq
    - mistral
1. rabbit mq
    - exchange 
    - exchange types
    - publisher
    - consumer
    - consumer <-> queue <-> exchange
    - publisher <-> exchange <-> queue

@veris-abhinavanand @veris-amoghbanta 
[just do it](https://www.youtube.com/watch?v=Wy7SJaq6Hnw) be a fire-starter 

# MoM - FRI - 16th DEC 2016

5 Steps to win @veris-ankitpopli @veris-neerajdhiman 

- Trace the function calling
- Trace the data flow
- Trace the worker calling
    - queues
    - data store
    - data flow
    - data binding and data tracing
- How to control the function flow
    - pre-hook
    - process
    - post hook
    - how would mistral handle this
    - how would mistral manage the state of the process
    - how would the client know about the function parameters
    - do - hello world
    - do - hello jon
- fit the MFA use case
    - define all the microservices

@veris-abhinavanand 
- wrap up V2
- start with user app 
    - minimum version of the user app will just have the user profile

@veris-amoghbanta 
- proxyclick - landscape mode for terminal

@veris-abhinavanand @veris-amoghbanta 
- video in background - [can be made open-source as individual View](https://github.com/peeyush-tm/v-fun/issues/3)
- fullscreen background image

[veris-abhinavanand]

:congratulations: activity logged successfully on the server. Walkin cases are buggy. Will be fixed and terminal will be wrapped up by tomorrow.

PS: :congratulations: => congratulations

[veris-amoghbanta]

🆙 comment 🎉 A little bit of finishing touch tomorrow and we are all set! 😄

[peeyush-tm]

Moved to #24

MoMs \ MON-FRI \ 19th-23rd DEC 2016

FYI - It has been 6 weeks since we initiated the V3

@veris-ankitpopli @veris-neerajdhiman - good job, but the work has just started Coming week's plan for you guys would be to

• Monday
  • understand the data storage
  • data passing, data correlation, and data tracing
  • workflow - mistral & action chain
• Tuesday
  • chat-ops and workflow
• Wednesday
  • hello world
• Thursday
  • hello "jon"
• Friday
  • MFA
• How to manage "pre" and "post" Veris hooks
  • pre is for validating the request and handling the data requirements to call the process
  • post it for validating the response and sending out the response to the client
• How would the data be cleared of sensitive data and returned to the client
• How any of the session or state, is traced and maintained
• How to "resume" process
• How to "cancel and return" a process
• What is Pushpin ? and how can we use it?

Must have an app ready on 23rd DEC 🙇

@veris-abhinavanand @veris-amoghbanta - Time's up !

Coming week's plan for you guys would be to

• Monday
  • Exponent - Basic User App
  • Landscape mode - terminal - proxyclick
• Tuesday
  • Exponent - Basic User App
  • Landscape mode - terminal - proxyclick
• Wednesday
  • Exponent - Basic User App
  • Landscape mode - terminal - proxyclick
• Thursday
  • Exponent - Basic User App
  • check if a video in the background is possible
• Friday
  • check if a video in the background is possible

And then some meetings !

[peeyush-tm]

@veris-abhinavanand @veris-amoghbanta @veris-ankitpopli @veris-neerajdhiman - please update the work status for the week, next work and summary of discussions please, so that we can quickly resume the work

Might be in the same comments that you have made above.