Mission

Building an urban governance platform to catalyze digital transformation across towns and cities - changing the way citizens interact with government bodies.

Overview

DIGIT Urban Stack is a set of Open APIs, services, and reference implementations, set up as a public good, to allow government entities, businesses, startups, and civil society to use a unique digital Infrastructure and build solutions for urban India at a large scale. It provides a set of open standards, specifications and documentation to create a level playing field and enable ecosystem players to innovate on the stack. As a public good, the platform is provided without profit or restriction to all members of society.

Goals

The urban mission offers digital governance solutions that encapsulate the core platform principles. The apps provide

• Secure & reliable governance tools

• Simple reusable modules for effective integration

• Scalable & standardized solutions

• Open APIs to promote interoperability

• Multiple channel support

• Configurable building blocks that support customization at each stage

Approach

DIGIT-Urban focuses on inclusion and is designed on the principle of enhancing both platform openness and choice for citizens. The platform uses open APIs and standards, creating a powerful framework to drive convergence across the multiple systems currently in use and to lower the barrier to entry for locally-developed solutions.

Keeping in mind that most Indians use the internet through their phones, we follow and advocate a “mobile-first” approach, while supporting multi-channel access to accommodate diverse needs and preferences.

• Open Source - DIGIT is Open Source and has been built using the best in class Open Source technology stacks powering the most advanced companies in the world. DIGIT is able to provide the lowest total cost of ownership and helps ensure that governments retain strategic control of their systems and data.

• Mobile-Enabled - DIGIT has adopted a mobile-first approach, with robust mobile applications enabling citizens to easily access government services through their phones. Government officials and field workers are also empowered with mobile applications that enable them to deliver 24×7 governance with ease.

• Real-time Dashboards - DIGIT’s real-time dashboards provide governments with actionable insights on demand. Administrators and department heads are empowered with verified data that enables them to manage their work and budgets better. Field-level employee reports enable effective performance management and ensure efficient usage of government resources.

Useful Links

Contact Us

Release Summary

DIGIT 2.7 release has got new modules, a few functional changes, and non-functional changes.

Functional changes

• National Dashboard for PT, TL, OBPS, PGR, W&S, mCollect, and Fire NOC;

• State level DSS of OBPS, W&S, Fire NOC and mCollect;

• PT UI/UX Audit Feedbacks, TL UI/UX Audit Feedbacks, PGR UI/UX Enhancements Audit Feedbacks;

• PT common Search, PT lightweight create and integrate with TL;

• Notification for different channels - W&S, PT, and TL;

• Common UI/UX - Citizen Profile, Employee Profile;

• Multi Tenancy Selection, Birth and Death module, State DSS and National Dashboard for Birth and Death

Non-functional changes

• National Dashboard Ingest API and NUGP STQC Security fixes

New ‌Feature Additions

Enhancements

‌Document Resources and Links

UI Technical Documents

Backend Service Documents

MDMS Changes

Config Changes

Infra Changes

QA Test Cases

UAT Regression Test Cases

MDMS Changes

Config Changes

Infra Changes

Service Build Updates

TL Renewal Alert & Owner Type Test Cases

PT UI Audit Test Cases

PGR Enhancement Test Cases

PT Common Search & TL Integration Test Cases

Notifications Based On Channel Test Cases

Update Mobile Number Feature Test Cases

National Dashboard & DSS Test Cases

Birth & Death Test Cases

Download Our Test Cases

Release Summary

This note consists of common UI/UX elements revamped for employee and citizen Profiles.

New ‌Feature Additions

Detailed user Manuals

Common UI/UX: Common UI/UX

Overview

In this release of the National Urban Dashboard, both state and national level DSS instances were developed for some modules and only the national level instance for a few others.

Release Highlights

All the module dashboards have the following common features:

• Filters for the date range, States, ULBs

• Denominations to change the revenue metrics view

• Drill down feature in the service report where state wise, ULB wise, and ward wise reports are available by clicking on the boundary name

• Definitions for all the metrics and chart elements are viewable by hovering over the desired element/metric

• The search feature in the filter boxes and service tabular reports

• Download, share (WhatsApp, email) for individual cards and overall dashboard

Each module dashboard presents the aggregated urban data from the ward, ULB, and state levels in concise charts, graphs, and also in raw numbers as per the KPIs defined. Except for Landing Page, all the other modules are similar for both national and state-level instances.

Click on the file link below to find the detailed definitions of each KPI in the dashboard.

Release Features

The individual dashboard features are listed in the table below:

Known Issues

None.

Upcoming Release Features

• Sidebar navigation

• About, Purpose pages

Reference Doc Links

DIGIT is India’s largest open-source platform for digital governance. It is built on OpenAPI (OAS 2.0) and provides API-based access to a variety of urban/municipal services enabling state governments and city administrators to provide citizen services with relevant new services and also integrating the existing system into the platform and run seamlessly on any commercial/on-prem cloud infrastructure with scale and speed.

Key Architecture Highlights

• DIGIT is a microservices-based platform that is built to scale. Microservices are small, autonomous and developer-friendly services that work together.

• A big software or system can be broken down into multiple small components or services. These components can be designed, developed & deployed independently without compromising the integrity of the application.

• Parallelism in development: Microservices architectures are mainly business-centric.

• MicroServices have smart endpoints that process info and apply logic. They receive requests, process them, and generate a response accordingly.

• Decentralized control between teams, so that its developers strive to produce useful tools that can then be used by others to solve the same problems.

• MicroServices architecture allows its neighbouring services to function while it bows out of service. This architecture also scales to cater to its clients’ sudden spike in demand.

• MicroService is ideal for evolutionary systems where it is difficult to anticipate the types of devices that may be accessing our application.

Multi-layer Architecture

DIGIT follows Multilayer or n-tiered distributed architecture pattern. As seen in the illustration above there are different horizontal layers with some set of components eg. Data Access Layer, Infra Services, Business Services, different modules layers, client Apps and some vertical adapters. Every layer consists of a set of microservices. Each layer of the layered architecture pattern has a specific role and responsibility within the application.

• Layered architecture increases flexibility, maintainability, and scalability

• Multiple applications can reuse the components

• Parallelism

• Different components of the application can be independently deployed, maintained, and updated, on different time schedules

• Layered architecture also makes it possible to configure different levels of security to different components

• Layered architecture also helps users test the components independent of each other

DIGIT is an open-source platform licensed under the MIT license (https://opensource.org/licenses/MIT) compliant with the NUIS digital blueprint.

Detailed mapping of DIGIT’s capabilities with the core requirements mentioned in the NUIS digital blueprint has been done below:

Interoperability

Data specifications/models are available for domain entities. DIGIT is designed as an API-first platform wherein data specs/models are created for all key entities thus ensuring interoperability through open APIs and open standards. Taxonomies are available for the key domain entities/registries. These can later be harmonised with standard taxonomies in the domain as and when they are made available.

DIGIT data models and APIs are published as Open APIs freely available to everyone in the ecosystem. In Punjab, the DIGIT module was easily integrated with 3rd party payment apps like Paytm, Airtel Money, BBPS, etc to increase citizen access and improve collections. At present, DIGIT provides at least 3 key distinct APIs for all domain entities - create, update and search.

Deactivation/Cancellation of key entities in DIGIT is achieved through updating their status to inactive as per their defined specification/API contracts. Given the API-first and micro-services-driven nature of DIGIT, current APIs and models can be quickly harmonised with national standards as and when they are made available. DIGIT strives to leverage established domain standards (national/international) wherever available.

Data Privacy And Security By Design

Data Privacy

Data privacy capabilities are available to mark and protect sensitive data. The core service layer of DIGIT includes signing and encryption service as one of the core services that provide capabilities to sign/encrypt/mask sensitive data. It is designed such that it can work against software key stores and can be extended to integrate with any kind of hardware key store to store and protect signing and encryption keys.

Encryption requirements can be defined and adhered to for the storage of sensitive data. DIGIT requires the User PII data to be stored in its User service which is by default enabled for encryption of sensitive data as User Data Vault. All other services in DIGIT are required to access PII data by explicitly calling the User service - which in turn audits all access to PII. In addition, individual services in DIGIT can leverage DIGIT’s signing and encryption service (which is what User Service leverages to create User Data Vault) to further protect additional sensitive data available with the services.

DIGIT provides the capability to define workflows for data modification that can be configured to have approval steps to get needed consent for any data modification activities. DIGIT currently provides RBAC (Role-Based Access Control) based access control for access (search) to data.

Security

Appropriate access controls can be defined in the APIs to ensure authorised access to sensitive data. DIGIT is designed to handle authentication and authorisation as perimeter control at its API gateway layer to ensure unauthorised calls are not allowed to even contact the respective micro-services. DIGIT provides an RBAC (Role-Based Access Control) mechanism where users are explicitly provided access to relevant resources by assigning them appropriate roles. By default, DIGIT supports OAUTH-based authentication for individual users and APIs. However, the Authentication and Authorization filter on DIGIT is designed to be easily extendable to support any further Auth and Auth needs.

Perimeter security mechanism in DIGIT also helps developers in focusing on the functional developments in further services and offloading the access control requirements for new resources and their APIs to the API gateway using simple configurations.

DIGIT also ensures that risks like the following are taken care of:

• Privilege escalation – form field manipulation

• Failure to restrict URL access

• Insecure direct object references (IDOR)

• Malicious file upload leads to cross-site scripting

• Improper authentication

• Missing account lockout

• Request throttling attack

• Weak encoding mechanism

• Sensitive information in URL

• Lack of automatic session expiration

• Insecure banner implementation

• Concurrent session

• Clickjacking

• Improper error handling

Transparency And Accountability Through Data

DIGIT has the capability to define key registries in OpenAPI 3.0 specs formats and easily achieve key APIs like create/update/search using its building blocks in core services mainly through configurations and using lightweight extensions on a needs basis.

DIGIT has the capability to protect person-specific sensitive data by encrypting them in the user data vault (User Registry) which allows configuration-based protection of sensitive PII. DIGIT requires additional registries to reference PII using this mechanism. In addition, registries in DIGIT can leverage its data protection (Signing and Encryption) core service to provide additional protection to registry-specific attributes.

Registry data in DIGIT can be signed for tamper-proofing using its signing and encryption core service. A proof of concept for this has already been done on the ePass module that was built on the DIGT platform. All key data modifications in DIGIT are access logged to provide an audit trail, which can be accessed through APIs. The upcoming version of DIGIT is planning to bring in the concept of immutable event logs to further strengthen this capability. DIGIT leverages open-source telemetry to provide the ability to gather telemetry data and extends it for the DIGIT-specific processing pipeline. This framework allows for additional event definitions and contextual extension of the telemetry processing pipeline thereby future-proofing this capability in DIGIT.

Reusability and Extensibility

DIGIT platform is designed as a collection of more than 50+ atomic microservices which are bundled together in a given context to provide end solutions. Microservices in DIGIT can be mainly categorized in three categories: Data services (Registries, reference Master data management, etc.), Tech infrastructure services (Authentication, authorisation, notification engine etc.) and domain services (Assessment, NOC etc.). Citizen, employee and administrative interfaces in DIGIT use these microservices to achieve the needed functionality.

Data models and APIs in DIGIT are defined as OpenAPI 3.0 specifications and can be extended by using a combination of configuration and extension techniques. E.g. if the additional attributes are only needed to be stored with format validation, it can be a simple schema extension, while if the additional business checks/functionality need to be implemented using the extended attributes then it can be achieved using pre/post request filters or extending underlying microservices.

DIGIT allows extension of existing capabilities without needing architectural interventions. As described above extension of existing functionality on DIGIT can be achieved using additional configurations, additional extension services or request/response filters.

Several partners have extended DIGIT modules to cater to new use cases. For instance DIGIT mCollect module caters to collection of fees for more than 50 services on the counter, but it did not have a citizen interface for payment of these services online. Directorate General Defence Estates (DGDE) wanted to introduce this interface for the citizen’s of cantonment boards in India and were able to easily enhance the mCollect module to include this capability. Similarly Punjab has reused several DIGIT core services to develop new modules on the platform with minimum efforts.

DIGIT supports single-instance multi-tenancy to enable sharing of the underlying infrastructure, also all DIGIT data models and services are designed to be multi-tenanted.

DIGIT uses API first approach in its design and development to ensure loose coupling between its various components. These APIs are clearly defined using OpenAPI 3.0 specifications to ensure clear documentation.

Evolvability and Scale

As described above, extension of existing functionality on DIGIT can be achieved using additional configurations, additional extension services or request/response filters. Similarly new functionality can be added by rebundling existing building blocks in context of new use cases and implementing only additionally required services without requiring any architectural overhaul. Additionally due to its loosely coupled API driven design DIGIT allows for new components to be implemented in the technology that is most useful for that use case.

API driven, microservices based architecture of DIGIT enables its components to evolve separately. On DIGIT Individual components can evolve separately to enable heterogeneous evolution of the system.

DIGIT uses SemVer 2.0 for versioning of its microservices and interfaces. Semantic versioning is a formal convention for specifying compatibility using a three-part version number: major version; minor version; and patch. More details on this can be found on this link: https://semver.org/.

DIGIT is designed to be horizontally scalable. Microservices based architecture of DIGIT also enables it to scale only needed components/services, thereby providing resource efficiency. E.g. Billing and Collection services can be scaled separately during financial year closing if the load pattern indicates increasing volume of bill payments during that period.

DIGIT is designed to be hardware agnostic and can be run on any hardware. It has been tested on multiple commercial clouds and state sponsored bare metal infrastructure. Components of DIGIT that need to use underlying hardware have been carefully chosen (in case where DIGIT is using other open source components) or designed (DIGIT’s own components) to provide a layer of abstraction that can be extended for any types of hardware.

Multi-channel Access

DIGIT is designed using API first approach, therefore enabling any user interface channel to leverage it. DIGIT’s own user interfaces (Web/mobile app, WhatsApp chatbot) are implemented using its APIs to ensure offered platform capabilities and data are accessible to any delivery channel based on configured policies. In states like Punjab and AP where DIGIT modules are being used, the citizens have been given multi-channel access - ULB counters, Web portals, Mobile App, WhatsApp Chatbot and 3rd party applications like Paytm, BBPS to avail local government services.

DIGIT’s access control mechanism can be configured to provide different levels of access based on channels and roles.

Ecosystem-driven

DIGIT platform and its user interfaces are completely open source. Also, all external components used in DIGIT are also Open Source. Due to its API based and event driven architecture DIGIT can be integrated with any existing stack. Wherever appropriate, DIGIT also provides out of box integrations with crucial stacks/platforms. The most common integrations are to payment gateways, SMS providers and SMTP email servers for a typical implementation.

More than 14 organizations have already partnered with us to implement DIGIT across multiple implementations in the country and have built more than 20 new solutions on top of the platform.

DIGIT also provides the capability to gather feedback from the ecosystem in a digital manner. Feedback capability in DIGIT can be looked at the following levels:

• Service Delivery feedback on services offered through DIGIT - DIGIT provides a highly configurable and extensible Public Grievance module to enable this kind of feedback/redressal for functional users (Citizens, employees etc)

• Service Usage feedback - DIGIT user interfaces include a telemetry SDK which is backed by telemetry infrastructure in DIGIT platform. Coupled with API access logs, this enables DIGIT to gather usage feedback through live action and can be used for fine tuning interfaces and APIs

• Design/Feature feedback - As an open source project on github, DIGIT provides a mechanism to provide comments/feedback on its various components using github. This feedback can be leveraged to create a Point of View on the future roadmap for the platform.

Release Summary

FSM 1.1 is a release that has a few functional changes.

• Functional: Pre-pay and post-pay service, multi-trip, capturing gender Information, desludging request flow enhancements, FSTPO vehicle log flow enhancements, DSO flow enhancements, and FSM generic enhancements.

New ‌Feature Additions

Enhancements

Document Resources and Links

UI Technical Documents

Backend Service Documents

This section contains docs and information resources that guide you through the key DevOps concepts and its role in managing the DIGIT platform.

All content on this page by is licensed under a .

Overview

This release offers the pre-payment and post-payment options to users while submitting the request for desludging operations along with multi-trip support.

Release Highlights

• Payment preference

• Multiple trips per service request

Release Features

Enhancements

Known Issues

• FSTPO inbox sort

Upcoming Release Features

• Better UX/UI for citizen application flow

• Dashboard with insights on Payment Preference, Gender, Request Status and Customer Rating

Reference Doc Links

Overview

DIGIT is the largest urban governance platform built for billions and billions of transactions between citizens and the state govt through various municipal services/integration. The platform is built with key capabilities like scale, speed, integration, configurable, customizable, extendable, multi-tenanted, security, etc. Here, we shall discuss the key requirements and capabilities.

Pre-requisites

Before proceeding to set up DIGIT, it is essential to know some of the key technical details about DIGIT, like architecture, tech stack and how it is packaged and deployed on various infrastructures. Some of these details are explained in the previous sections. Below are some of the key capabilities to know about DIGIT as a platform.

1. DIGIT is a collection of various services built as RESTFul APIs with OpenAPI standard

2. DIGIT is built as MSA (Microservices Architecture)

3. DIGIT services are packaged as containers and deployed as docker Images.

4. DIGIT is deployed on Kubernetes which abstracts any Cloud/Infra suitable and standardised for DIGIT deployment.

5. DIGIT deployment, configuration and customization are done through Helm Charts.

6. Kubernetes cluster setup is done through code like terraform/ansible suitably.

Why

The OpenAPI Specification (OAS) defines a standard, programming language-agnostic interface description for REST APIs, which allows both humans and computers to discover and understand the capabilities of a service without requiring access to source code, additional documentation, or inspection of network traffic. When properly defined via OpenAPI, a consumer can understand and interact with the remote service with a minimal amount of implementation logic. Similar to what interface descriptions have done for lower-level programming, the OpenAPI Specification removes the guesswork in calling a service.

Why

Microservices are nothing but breaking big beasts into smaller units that can independently be developed, enhanced and scaled as a categorized and layered stack that gives better control over each component of an application that exists in its own container, independently managed and updated. This means that developers can build applications from multiple components and program each component in the language best suited to its function, rather than having to choose a single less-than-ideal language to use for everything. Optimizing software all the way down to the components of the application helps you increase the quality of your products. No time and resources are wasted managing the effects of updating one application on another.

Comparatively the best infra choice for running a microservices application architecture is application containers. Containers encapsulate a lightweight runtime environment for the application, presenting a consistent environment that can follow the application from the developer's desktop to testing to final production deployment, and you can run containers on cloud infra with physical or virtual machines.

As most modern software developers can attest, containers have provided us with dramatically more flexibility for running cloud-native applications on physical and virtual infrastructure. Kubernetes allows you to deploy cloud-native applications anywhere and manage them exactly as you like everywhere. For more details refer to the above link that explains various advantages of Kubernetes.

For being successful in the DIGIT Setup, below are certain requirements that need to be ascertained:

Skills Needed

• On-premise/private cloud accounts

  • Interface to access and provision required infra

  • In the case of SDC, NIC or private DC, it'll be VPN to an allocated VLAN

  • SSH access to the VMs/machines

• Infra Skills

  • Public cloud

    • Managed Kubernetes services like AKS or EKS or GKE on Azure, AWS and GCP respectively

  • Private Clouds (SDC, NIC)

    • Clouds like VMware, OpenStack, Nutanix and more, may or may not have Kubernetes as a managed service. If yes we may have to estimate only the worker nodes depending on the number of ULBs and DIGIT's municipal services that you opt.

    • In the absence of the above, you have to provision the Kubernetes cluster from the plain VMs as per the general Kubernetes setup instruction and add worker nodes.

• Operations Skills

  • Understanding of Linux, containers, VM Instances, Load Balancers, Security Groups/Firewalls, Nginx, DB Instance, Data Volumes

  • Experience with Kubernetes, Docker, Jenkins, Helm, Infra-as-code, Terraform

  • Experience in DevOps/SRE practice on microservices and modern infrastructure

High-level Action To Deploy DIGIT

2. • ZooKeeper

   • Kafka

   • Elastic Search

3. Setting up the Postgres DB

   • On a public cloud, provision a Postgres RDS instance.

   • Private cloud, provision a Postgres DB on a VM with the backup, HA/DRS

4. • K8s Secrets

   • K8s ConfigMaps

   • Environment variables of each microservices

5. Deploy the stable released version of DIGIT and the required services

6. Setting up Jenkins job to build, bake images and deploy the components for the rolling updates

Overview

The Birth and Death module provides a digital interface, allowing citizens to search for and download the Birth and Death certificate. Also, the correctness of the certificate can be verified by scanning the QR code. The module enables the following:

• Reduced physical touchpoints as citizens are not required to visit offices

• Reduced time with the instantaneous download of certificates

• Verification of the correctness of the certificate by scanning the QR Code

The Birth & Death module also enables ULB employees to create new registrations and also search for any previous applications through the employee side interface of the module.

In addition to the module, the DSS(Decision Support System) at the state level and national level instances enables administrators to view the records and have an aggregate view of the certificate downloads and other metrics for research and analysis purposes. The demographic data of the birth and death records also helps administrators to detect anomalies and make data-driven decisions.

Release Highlights

In this release of the Birth & Death module, the following modules were developed

1. Birth & Death Module

   • Employee side interface

   • Citizen side interface

   • User access for

     1. Birth record creator - Can only create new applications

     2. Death record creator - Can only create new applications

     3. Birth record viewer - Can only search and view applications

     4. Death record viewer - Can only search and view applications

     5. Birth record editor - Can edit existing applications

     6. Death record editor - Can edit existing applications

     7. DSS viewer - View DSS

2. Birth & Death State DSS

3. Birth & Death National DSS

Release Features

Birth & Death Module

For an employee, the B&D module gives access to create birth records and death applications based on the registration details that they receive from the hospital, morgue, or from concerned authorities. They can also search the existing records of birth and death registrations based on date ranges, view them in tabular forms, and take printouts.

For a citizen, the Birth & Death module offers the convenience of downloading birth and death certificates using a simple search interface. They can also make payments if required for downloading the certificates, view past records and payments, and also download payment receipts.

Birth & Death Module - State DSS

The Birth & Death module shows the aggregated values for the certificate downloads and payment collections on the overview page of state DSS. Furthermore, in the individual module page, it shows

1. Distinct birth and death tabs that display metrics and charts for each segment

2. Number of certificate downloads and collection from payments

3. Certificate download trend across time

4. Chart showing certificate downloads by channel

5. Number of delayed registrations where the date of registration and date of birth/death differs by more than a year

6. Chart showing births and deaths by gender

7. Chart showing deaths by age category

The module also has the capability to show the ULB and ward-wise drill down for the delayed registrations and downloads by channel

Birth & Death Module - National DSS

The Birth & Death module shows the aggregated values of the certificate downloads and payment collections on the overview page of the National DSS. The application numbers and collection amounts are also aggregated and shown in the Total Collection and Total applications metrics on the Landing Page. Furthermore, in the individual module page, it shows

1. Distinct birth and death tabs that display metrics and charts for each segment

2. Number of certificate downloads and collection from payments

3. Certificate download trend across time

4. Chart showing certificate downloads by channel

5. Number of delayed registrations where the date of registration and date of birth/death differs by more than a year

6. Chart showing births and deaths by gender

7. Chart showing deaths by age category

The module also has the capability to show the ULB and ward-wise drill down for the delayed registrations and downloads by channel

Known Issues

None.

Upcoming Release Features

1. Birth & Death Report

2. User roles for - Birth Report viewer, Death Report Viewer

Reference Doc Links

Introduction

This document aims to put together all the items which will enable us to come up with a proper training plan for a partner team who will be working on the eDCR service used for the plan scrutiny.

Technical Pre-requisites

Below listed are the technical skillsets that are required to work on eDCR service. It is expected that the team planning on attending training is well versed with the mentioned technologies before they attend eGov training sessions.

Skillset for the Development team

• Java and REST APIS

• Postgres

• Maven

• Spring framework

• Basics of 2D CAD Drawings

• Git

• Postman

• YAML/JSON

Skill Set for the DevOps team

• Strong working knowledge of Linux, command, VM Instances, networking, storage

• The session, cache, and tokens handling (Redis-server)

• Understanding of VM types, Linux OS types, LoadBalancer, VPC, Subnets, Security Groups, Firewall, Routing, DNS

• Experience setting up CI like Jenkins and creating pipelines

• Artifactory - Nexus, verdaccio, DockerHub, etc

• Experience in setting up SSL certificates and renewal

• Gitops, Git branching, PR review process. Rules, Hooks, etc.

• JBoss Wildfly, Apache, Nginx, Redis and Postgres

Hardware prerequisites

Trainees are expected to have laptops/ desktops configured as mentioned below with all the software required to run the eDCR service application

• Laptop for hands-on training with 16GB RAM and OS preferably Ubuntu

• All developers need to have Git ids

• Install VSCode/IntelliJ/Eclipse

• Install Git

• Install JDK 8 update 112 or higher

• Install maven v3.2.x

• Install PostgreSQL v9.6

• Postman

• Install LibreCAD

• Application Server JBoss Wildfly v11.x

Software Assets

There are knowledge assets available on the Net for general items and eGov assets for DIGIT services. Here you can find references to each of the topics of importance. It is mandated the trainees do a self-study of all the software mentioned in the prerequisites using the reference materials shared.

Overview

This release provides features which are identified as GAP between old UI and New UI.

Release Highlights

UI audit of property tax covers the features given below.

Citizen

1. Property Registration

2. Property Update

3. Search Property

4. Search Application

5. My Payments

6. Search and Pay

7. View Property

8. View Mutation Application

9. Pay Mutation Fee

Employee

1. View Payment History

2. Search Property

3. Search Application

4. Assess Property

5. View Mutation Application

6. Collect Mutation Fee

7. Update Property

Release Features

Known Issues

None.

Upcoming Release Features

1. Reports revamp

2. Output Documents PDF revamp

Reference Doc Links

Introduction

This document aims to put together all the items which will enable us to come up with a proper training plan for a partner team that will be working on the DIGIT platform.

Technical Prerequisites

Below listed are the technical skill sets that are required to work on the DIGIT stack. It is expected the team planning on attending training is well versed with the mentioned technologies before they attend eGov training sessions.

Skillset for the Development team

• Open API Contract - Swagger2.0

• YAML/JSON

• Postman

• Postgres

• Java and REST APIS

• Basics of Elasticsearch

• Maven

• Springboot

• Kafka

• Zuul

• NodeJS, ReactJS

• WordPress

• PHP

Skill Set for the DevOps team

• Understanding of the microservice architecture.

• Experience of AWS, Azure, GCP, NIC Cloud.

• Strong working knowledge of Linux, command, VM Instances, networking, storage.

• To create Kubernetes cluster on AWS, Azure, GCP on NIC Cloud.

• Kubectl installation & commands (apply, get, edit, describe k8s objects)

• Terraform for infra-as-code for cluster or VM provisioning.

• Understanding of VM types, Linux OS types, LoadBalancer, VPC, Subnets, Security Groups, Firewall, Routing, DNS)

• Experience setting up CI like Jenkins and create pipelines.

• Deployment strategies - Rolling updates, Canary, Blue/Green.

• Scripting - Shell, Groovy, Python and GoLang.

• Experience in Baking Containers and Dockers.

• Artifactory - Nexus, Verdaccio, DockerHub, etc.

• Experience on Kubernetes ingress, setting up SSL certificates and renewal

• Understanding on Zuul gateway

• Gitops, Git branching, PR review process. Rules, Hooks, etc.

• Experience in Helm, packaging and deploying.

• JBoss Wildfly, Apache, Nginx, Redis and Postgres.

Hardware prerequisites

Trainees are expected to have laptops/ desktops configured as mentioned below with all the software required to run the DIGIT application

• Laptop for hands-on training with 16GB RAM and OS preferably Ubuntu

• All developers need to have Git ids

• Install VSCode/IntelliJ/Eclipse

• Install Git

• Install JDK 8 update 112 or higher

• Install maven v3.2.x

• Install PostgreSQL v9.6

• Install Elastic Search v2.4.x

• Postman

Software Assets

There are knowledge assets available in the Net for general items and eGov assets for DIGIT services. Here you can find references to each of the topics of importance. It is mandated the trainees do a self-study of all the software mentioned in the prerequisites using the reference materials shared.

Hiring DevOps Resources

Anyone involved in hiring DevOps engineers will realize that it is hard to find prospective candidates who have all the skills listed in this section.

Ultimately, the skill set needed for an incoming DevOps engineer would depend on the current and short-term focus of the operations team. A brand new team that is rolling out a new software service would require someone with good experience in infrastructure provisioning, deployment automation, and monitoring. A team that supports a stable product might require the service of an expert who could migrate home-grown automation projects to tools and processes around standard configuration management and continuous integration tools.

DevOps practice is a glue between engineering disciplines. An experienced DevOps engineer would end up working in a very broad swath of technology landscapes that overlaps with software development, system integration, and operations engineering.

An experienced DevOps engineer would be able to describe most of the technologies that is described in the following sections. This is a comprehensive list of DevOps skills for comparing one’s expertise and a reference template for acquiring new skills.

In theory, a template like this should be used only for assessing the current experience of a prospective hire. The needed skills can be picked up on the jobs that demand deep knowledge in certain areas. Therefore, the focus should be to hire smart engineers who have a track record of picking up new skills, rolling out innovative projects at work, and contributing to reputed open-source projects.

1. Knowledge of Infrastructure

A DevOps engineer should have a good understanding of both classic (data centre-based) and cloud infrastructure components, even if the team has a dedicated infrastructure team.

A. Classic Infrastructure

This involves how real hardware (servers and storage devices) are racked, networked, and accessed from both the corporate network and the internet. It also involves the provisioning of shared storage to be used across multiple servers and the methods available for that, as well as infrastructure and methods for load balancing.

Virtualization Basics

• Hypervisors.

• Virtual machines.

• Object storage.

• Running virtual machines on PC and Mac (Vagrant, VMWare, etc.).

B. Cloud Infrastructure

Cloud infrastructure has to do with core cloud computing and storage components as they are implemented in one of the popular virtualization technologies (VMWare or OpenStack). It also involves the idea of elastic infrastructure and options available to implement it.

Networking Basics

• Network layers

• Routers, domain controllers, etc.

• Networks and subnets

• IP address

• VPN

• DNS

• Firewall

• IP tables

• Network access between applications (ACL)

• Networking in the cloud (i.e., Amazon AWS)

Load Balancing

• Load balancing infrastructure and methods

• Geographical load balancing

• Understanding of CDN

• Load balancing in the cloud

2. DevOps Toolchain

A DevOps engineer should have experience using specialized tools for implementing various DevOps processes. While Jenkins, Dockers, Kubernetes, Terraform, Ansible, and the like are known to most DevOps guys, other tools might be obscure or not very obvious (such as the importance of knowing one major monitoring tool in and out). Some tools like, source code control systems, are shared with development teams.

The list here has only examples of basic tools. An experienced DevOps engineer would have used some application or tool from all or most of these categories.

Source Code Management (SCM) System

• Expert-level knowledge of an SCM system such as Git or Subversion.

• Knowledge of code branching best practices, such as Git-Flow.

• Knowledge of the importance of checking in Ops code to the SCM system.

• Experience using GitHub.

Bug Management System

• Experience using a major bug management system such as Bugzilla or Jira.

• Ability to have a workflow related to the bug filing and resolution process.

• Experience integrating SCM systems with the bug resolution process and using triggers or REST APIs.

Collaborative Documentation System

• Knowledge of Wiki basics.

• Experience using MediaWiki, Confluence, etc.

• Knowledge of why DevOps projects have to be documented.

• Knowledge of how documents were organized on a Wiki-based system.

Build and CI

• Experience building on Jenkins standalone, or dockerized.

• Experience using Jenkins as a Continuous Integration (CI) platform.

• CI/CD pipeline scripting using groovy

• Experience with CI platform features such as:

  • Integration with SCM systems.

  • Secret management and SSH-based access management.

  • Scheduling and chaining of build jobs.

  • Source-code change based triggers.

  • Worker and slave nodes.

  • REST API support and Notification management.