Page Comparison

...

Component	Proposed Github Repo	Description
assessment-service	Sunbird-inQuiry/apiassessment-servicesservice	Microservice for question & questionset api's
questionset-publish	Sunbird-inQuiry/data-pipeline	Asynchronous job for publishing question & questionset
player	Sunbird-inQuiry/player	quml player to render Question & QuestionSet
editor	Sunbird-inQuiry/editor	Editor for creating Question & QuestionSet
portal	Sunbird-inQuiry/portal	A dummy portal to experience inQuiry Capabilities.

...

Cassandra keyspaces will have a building block name. Format is: [ENV]_[BB-NAME]_[KEYSPACE_NAME]
Kafka Topics will also have a building block name. BB name will be appended after ENV name.
All components configuration will be med moved to their respective git repo.

...

Is separate infra monitoring (e.g: monitoring service, grafana dashboard) will be installed for inQuiry?
- Devops response: No. Only for Co-Create BB, it will be installed separately. For Other BB, shared one will be used as of now because k8s cluster is same and the service is going to be common one. BB specific db servers/services can be attached for monitoring purpose.
How load testing will be performed for inQuiry components? Do we get common load test infra?
- Devops Response: Not Yet Decided. Most likely Every BB will have their own load test infra.
Currently, all assessment APIs are onboarded with Content Role (e.g: Content Create or Content Update). Should we change the API roles to Question/QuestionSet Role (e.g: Question Create)?
Note: this will have an impact on SunbirdEd/Diksha/etc)
What will happen to service telemetry (e.g: info/error logs) dashboard such as Graylog? Do we need it? If yes, what all services/components need to be installed?
- Devops Response: For telemetry testing, we need to use sunbird-ed infra and components. So BB specific deployments are not planned as of now.
Some basic functionalities around any objects (e.g: audit history, audit-event ) are currently with Knowlg. Should inQuiry also have these?

Current Code Structure:

Expand

title	Repo: github.com/project-sunbird/knowledge-platform

/knowledge-platform/assessment-api (assessment-service specific code)

/assessment-api/ assessment-service (play application)

/assessment-api/ assessment-actors (actor implementation)

/assessment-api/ qs-hierarchy-manager (hierarchy-manager)

/knowledge-platform/ontology-engine (assessment-service uses entire ontology-engine)

/ontology-engine/graph-common

/ontology-engine/graph-core_2.11

/ontology-engine/graph-dac-api

/ontology-engine/graph-engine_2.11

/ontology-engine/parseq

/knowledge-platform/platform-core (assessment-service uses entire platform-core directly or via ontology-engine)

/platform-core/actor-core

/ontology-engine/schema-validator

/ontology-engine/platform-telemetry

/ontology-engine/platform-common

/ontology-engine/cassandra-connector

/ontology-engine/kafka-client

/knowledge-platform/platform-modules (assessment-service uses only import-manager module)

/platform-modules/import-manager

/platform-modules/mimetype-manager

/platform-modules/url-manager

...

title	Repo: github.com/project-sunbird/knowledge-platform-jobs

/knowledge-platform-jobs/jobs-core (common module for all flink jobs)

/knowledge-platform-jobs/auto-creator-v2 (inQuiry BB job)

/knowledge-platform-jobs/publish-pipeline

/publish-pipeline/publish-core (common module for other publish job)

...

- As of now, these jobs will not be installed in inQuiry BBbecause of below reasons:
  - inQuiry doesn’t have required infra to process audit events.
  - audit history api is still not migrated to Knowlg BB Services.