Versions Compared

Old Version 13

changes.mady.by.user Kishan Kavala

Saved on

compared with

New Version 14

changes.mady.by.user Kishan Kavala

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Remaining data is expected to be per-Region(including projects, global config, resource limits) and not shared across databases in other Regions. 

New Tables

Table

Columns

  Description

region

id
name
end_point
api_key
secret_key

Integer - Unique Id of the Region. Number regions are expected to be small, hence using integer instead of long
Name of the Region. Should be unique.
Region end_point. e.g http://10.147.30.11:8080/client
api_key of the admin user
secret_key of the admin user

region_sync

id
region_id
api



created
processed  

Auto incremented id
Id of the region for whom the API call failed
API command and params. e.g command=createAccount&username=a3&password=a3&firstname=a3&lastname=a3&email=dsf%40dsf.com&account=a3&accounttype=0&domainid=1&accountid=68f952dc-69e6-458c-80c7-a3f3911cb9cc&userid=37817353-fed2-4963-b8ca-eaf2c4c9d744&regionid=1

created time stamp
Processed flag. Default 0.

Changes to existing tables

Table

New Columns

Description

user

region_id

ID of the source Region

account

region_id

ID of the source Region

domain

region_id

ID of the source Region

Data synchronization

Accounts:

...

  1. id: Region Id
  2. name: Name of the Region
  3. endpoint: Region end point. e.g. http://10.147.30.11:8080/client
  4. userapikey: API key of the Admin user
  5. usersecretkey: Secret key of Admin user

Admin user api_key/secret_key are used to make sync API calls to peer regions.

updateRegion

Parameters

  1. id: Region Id
  2. name: Name of the Region
  3. endpoint: Region end point. e.g. https://10.147.30.11:8080/client
  4. userapikey: API key of the Admin user
  5. usersecretkey: Secret key of Admin user

...