IS RESPONSIBLE TO ACCEPT ALL GLOBAL REQUESTS IN IBM CLOUD FOR THAT REGION
API SVC
Everything under pkg—>loadbalancer.go Receiving the request from rias svc and process all dats and gives a quick response to customer whether all parameters are right or wrong, do you proper access or not, etc and store it in db. DO VALIDATION (OF ALL PARAMTERS), IAM authorisation , checking other microsvc like sg,pdns, etc and then creating db entries , create a resource in Resource controller to track all activities on lb and then workflow will pick it ip(600 lines of code)
Any actions taken on the lb , the 1st response comes to client from API svc API HAD ALL ENTRY POINTS TO LBS, LISTENERS, POOLS, MEMBERS, POLICY ETC
UTIL:
Your functions the api and activity relies on.
Anything need to process(small ,small functions) like Lb validation, all find in utility.
Helper functions to support micro svcs WORKFLOW AND ACTIVITY
THE STATE FROM CREATE_PENDING TO ACTIVE TAKEN CARE BY WORKFLOW AND ACTIVITY
WORKFLOW:
TO CREATE A MAP HOW THE FLOW SHOULD LOOK LIKE IF SOMEONE WANT TO CREATE LB
WORKFLOW WILL CREATE A PROCESS TO MANAGE HOW THE EXECUTIONS HAPPENS AND DETERMINE HOW THE DEFINITIONS LOOKS LIKE
ACTIVITY:
ACTIVITY IS THE ONE WHICH CREATES THE EXECUTIONS
Show process executions processed ——
Executions
—
INTERNAL API svc:
GARAGESHELL : INTERNAL CALLS LIKE RECOVER, details etc, it goes to api svc directly
THREE MOST IMP WHILE TRUBLESHOOT:
API
UTIL relies ON ANI AND ACTIVITY SVCS ACTIVITY
CREATE LB AND IF YOU GET ERROR—> TAKE TRACEID—>LOGDNA—CHECK ERROR —>GO TO CODE AND CHECK WHERE IT’S GIVING ERROR
ALL OUR APIS ARE IN V1 LOADBALANCER PATH
RIAS CIS
IS RESPONSIBLE TO ACCEPT ALL GLOBAL REQUESTS IN IBM CLOUD FOR THAT REGION
API SVC
Everything under pkg—>loadbalancer.go Receiving the request from rias svc and process all dats and gives a quick response to customer whether all parameters are right or wrong, do you proper access or not, etc and store it in db. DO VALIDATION (OF ALL PARAMTERS), IAM authorisation , checking other microsvc like sg,pdns, etc and then creating db entries , create a resource in Resource controller to track all activities on lb and then workflow will pick it ip(600 lines of code)
Any actions taken on the lb , the 1st response comes to client from API svc API HAD ALL ENTRY POINTS TO LBS, LISTENERS, POOLS, MEMBERS, POLICY ETC
UTIL: Your functions the api and activity relies on. Anything need to process(small ,small functions) like Lb validation, all find in utility. Helper functions to support micro svcs WORKFLOW AND ACTIVITY
THE STATE FROM CREATE_PENDING TO ACTIVE TAKEN CARE BY WORKFLOW AND ACTIVITY
WORKFLOW: TO CREATE A MAP HOW THE FLOW SHOULD LOOK LIKE IF SOMEONE WANT TO CREATE LB
WORKFLOW WILL CREATE A PROCESS TO MANAGE HOW THE EXECUTIONS HAPPENS AND DETERMINE HOW THE DEFINITIONS LOOKS LIKE
ACTIVITY: ACTIVITY IS THE ONE WHICH CREATES THE EXECUTIONS
Show process executions processed —— Executions —
INTERNAL API svc:
GARAGESHELL : INTERNAL CALLS LIKE RECOVER, details etc, it goes to api svc directly THREE MOST IMP WHILE TRUBLESHOOT:
API UTIL relies ON ANI AND ACTIVITY SVCS ACTIVITY
CREATE LB AND IF YOU GET ERROR—> TAKE TRACEID—>LOGDNA—CHECK ERROR —>GO TO CODE AND CHECK WHERE IT’S GIVING ERROR