Skip to content

4. Database Structure

Giuseppe Tricomi edited this page Nov 20, 2017 · 1 revision

Database Structure

Data, is grouped in several databases, one for each federation tenant (called borrower), and a common database called "ManagementDB". Each borrower's database has a series of required collection of document needed for the BB works; these collections contains the information related to clouds involved in federation. Below are listed the collection that need to be constructedby federation administrator when a new borrower is included in the federation:

a) Inside borrower database:

  • Countries: each document represents a multipoligon able to identify a nation. More in general in this collection are stored the multipolygon usefull for the borrower deployment;

  • credentials: it contains a series document in which are represented the user (we are talking about user of the federation) credential in a target federated cloud;

  • datacenters: it contains information about cloud in which borrower has an agreement/contract and that are used in the federated deployment;

  • faInfo: It contains the information related to BNA component for each federated cloud;

b) Inside ManagementDB some document have to be added in the listed below collection

  • Federation_Credential: it contains information about borrower's name, token and password

  • fedtenanttoBor: it contains information about borrower's name, uuid of its tenant in afederated cloud and the endpoint of that cloud.

An important collection present inside "ManagementDB" database is "SystemInfos", this collection contains the pointer for the module involved in the federation like BNM.

Examples of document present in the collection managed by administrator are available here: https://github.com/BeaconFramework/BeaconBroker/tree/master/Collection_Template

Clone this wiki locally