Devops

It covers the full spectrum of capabilities, starting with development, going through a transition to operations, and ending with operations. Each capability comprises people, procedures, and software and hardware tools. This documentation currently focuses on the capabilities that others can learn from and reuse. See below for a capability map and the different DevOps capability areas. Full screen Analysis & Design CapabilitiesAnalysis & Design Capabilities are the capabilities needed to analyze needs and design solutions and applications for the Altinn 3 platform. »

Analysis Enablement Capabilities Requirement Capture Requirements are gathered through: issues on Github talks with stakeholders using the platform (service owners and others) For some pilots, we choose to create larger epics on Github to group requirements. Some example issues are The issue for supporting Sirius App for tax department The issue for supporting NSM POB See development application components to get an overview of our tools and applications. User story Definition The DevOps teams or stakeholders define user stories in our GitHub repositories »

Below is a list of the capabilities with a short description and possible link to the different components providing that capability. Software Generation Capabilities Code & Config Writing Capability Most of our code is written manually. See development application components to get an overview of our tools and applications. Software Defined Infrastructure Definition Enablement We use Terraform to define infrastructure. Build & Integration Enablement Capabilities Software Compilation & Validation The project uses . »

Altinn Studio, Altinn Apps and Altinn Platform is deployed in serveral environments for different usage. Development Environments Available at staging.altinn.studio for Altinn Studio Test environment We have serveral internal test environments used for testing. Available at at22.altinn.cloud Available at at23.altinn.cloud Available at at24.altinn.cloud Available at dev.altinn.studio for Altinn Studio. Pre Production Environemnt This environment used by the application/service owners to test applications created in Altinn Studio. Available at tt02.altinn.no Production Environment Available at www. »

Over time it is expected that the Altinn 3 platform would consist of hundreds of Kubernetes clusters and other cloud resources. To be able to manage and configure all these cloud resources the architecture that is selected has several capabilities enabled with help of various tools and processes. Infrastructure Configuration and management Capabilities Tools & components For all solutions of Altinn 3 (Altinn Apps, Altinn Platform and Altinn Studio) we use some common tools to configure and manage infrastructure. »

PaaS & IaaS Management Capabilities Automation & Scheduling (batch, scripts) This include running scripts for infrastructure and jobs both manual and scheduled. See operations application components for details about tools and applications used. Infrastructure Configuration & Management The Altinn 3 platform is a large platform with serveral 100 cloud resources. The architecture provides serveral capabilityes to configure and manage all of this resource. See details here. Backup & Recovery The Altinn 3 platform has the capability to backup and restore data created by applications hosted in Altinn Apps. »

Most of the project capabilties is not listed. Most of the project capabilities are not listed. The ones listed are where we use technologies and techniques that can be shared/reused. Backlog managmenent and prioritazion The different product owners manage the backlog for Altinn. Team Studio: FinnurO Team Platform: OddArneSeatervik Team Authorization: sivaglen The overall roadmap is available on this GitHub roadmap project. The issues in the roadmap project are based on the Roadmap repository or the different repositories used by the various teams/components. »

Quality Assurance & Reviews All pull request in GitHub requires approved reviews of the changes before it can be merged in to the master branch. See current and earlier pull request. For infrastructure changes the pull request is done in Azure Devops with the same type of reviews. Defect Tracking & Management Defects are tracked in Gitub as bugs. See active and closed bugs. Static SW Analysis Enablement Every pull requsts needs to adhere to code quality standard verifyed with static code analysis. »