Versions Compared

Old Version 8

changes.mady.by.user Gauraw Kumar

Saved on

compared with

New Version 9

changes.mady.by.user Kartheek Palla

Saved on

Key

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

...


Proposed inQuiry BB Changes:

Proposed Git Repos:

Expand
titleSunbird-inQuiry/quml-service (for assessment-service )

/quml-service/assessment-service
/quml-service/assessment-actors
/quml-service/qs-hierarchy-manager
/quml-service/build (build script)
/quml-service/schema (question & questionset schema)
/quml-service/definition (sunbird supported primary category & its definition script for quml)
/quml-service/tests (API Functional Test Script/Code)

Expand
titleSunbird-inQuiry/quml-jobs (for backend jobs)

/quml-jobs/questionset-publish (for Question/QuestionSet Publish)
/quml-jobs/auto-creator-v2 (for import of Question/QuestionSet)

Expand
titleplayer & editor repos

Sunbird-inQuiry/quml-editor (for questionset editor)

Sunbird-inQuiry/quml-player (for quml player)

Sunbird-inQuiry/quml-portal (dummy portal for experiencing inQuiry feature)

Expand
titleDevops repos

Sunbird-inQuiry/devops (devops script for provisining, deployements)

Sunbird-inQuiry/devops-cred or devops-private (private repo)

...

quml-

...

quml-service:

configuration change:

...

Deployment Structure:

  • inQuiry is dependent on the below services and jobs from Knowlg BB:

    • search-service

    • taxonomy-service

    • content-service

    • search-indexer flink job

  • inQuiry will install all dependent services/jobs in its own infra.

inQuiry

...

& Knowlg using Same DB:

...

inQuiry portal will use Knowlg channel, category definition, asset & search api'sAPIs.

Micro Services

assessment-service:

  • assessment-service will be deployed with its own configuration.

  • assessment-service will be configured to make db calls for category definitions.

flink jobs

...

  • questionset-publish:

    • It will be installed with inQuiry specific configuration.

  • auto-creator-v2:

    • the job makes 2 api call (get hierarchy & add to hierarchy).

    • the api calls will be made using internal content-service url and end points (url & endpoint will be a configuration)

  • search-indexer:

    • No need to install search-indexer job for inQuiry, as graph db is same.

DB’s

  • Neo4j:

    • inQuiry doesn't need to install db extension, if graph db is same.

  • Logstash:

    • No need to install for inQuiry

  • Kafka:

    • assessment-service will use its own kafka topic for publishing question/questionset.

  • Cassandra:

    • inQuiry will have its own keyspace names.

  • Redis:

    • inQuiry will use db number assigned to BB.

  • ES:

    • inQuiry will use Knowlg search-indexer job and will write data to Knowlg Index (e.g: compositesearch)

    • inQuiry will use Knowlg search-service and consume data

inQuiry

...

& Knowlg using Different DB:

...

inQuiry portal will use Knowlg channel, category definition, asset & search api's.

Micro Services

assessment-service:

  • assessment-service will be configured to make db calls to get the category definition as taxonomy-service will be installed.

flink jobs

...

  • questionset-publish:

    • It will be installed with inQuiry specific configuration.

  • auto-creator-v2:

    • the job makes 2 api call (get hierarchy & add to hierarchy).

    • the api calls will be made using internal content-service url and end points (url & endpoint will be a configuration)

  • search-indexer:

    • inQuiry will install search-indexer job with inQuiry specific configuration.

    • The job will write data to inQuiry Index (e.g: inquiry_searchindex)

DB’s

  • Neo4j:

    • inQuiry need to install db extension, because graph db server is different.

  • Logstash:

    • Need to install for inQuiry

  • Kafka:

    • a inQuiry specific topic need to create for search-indexer job also.

    • assessment-service will use its own kafka topic for publishing question/questionset.

  • Cassandra:

    • inQuiry will have its own keyspace names.

  • Redis:

    • inQuiry will use db number assigned to BB.

  • ES:

    • inQuiry will use its own search-indexer job and will write data to own Index (e.g: inquiry_searchindex)

    • inQuiry need to deploy search-service from Knowlg BB to consume the data. the service will point to inQuiry index.