Glossary of terms
The following is a list of the definitions related to DevOps Intelligence:
- Pipeline: a pipeline is a combination of tools that they use in order to move their software through the development cycle and into production. Normally this means bringing together information from many disparate sources such as:
- SCM (Source Code Management) tools such as GIT and Mercurial
- CI/CD/CD (continuous integration) tools such as Jenkins, Travis-CI, Circle-CI and Team City
- CI/CD/CD Continuous Delivery tools such as Travis-CI, Spinnaker and Circle-CI.
- CI/CD/CD Continuous Deployment tools which are often the same set as continuous delivery tools
- Technical services: Technical services are the primary resources that DevOps Intelligence provides visibility into. A technical service can also consist of other services.
Technical services can:
- Be supported by one or more Git repositories. A repository can also support multiple technical services.
- Include build and unit testing processes.
- Be used by one or more applications.
- Be developed and managed by a single team.
- Have the same development and management team, although this is not required.
Be deployed using:
- A Kubernetes service definition.
- A pod or replica set.
- A template in AWS, Azure, or Google Cloud for VM-based or non-Kubernetes deployments.
- Cardinality: Repositories are associated with a single service. Technical Services can be associated with zero, one or more applications.
- Applications: an application is a higher level service. Application and Technical Service are somewhat similar and based on the approach undertaken by a given development organization they will choose what constitutes an application as they see fit. Common service used by many applications are likely to be grouped together as applications like a CORE application or an IAM service. The granularity will likely vary, and the best statement is it would be whatever the customer feels qualifies as the granularity that fits their needs.
- Tenant Roles: Tenant-level roles are separate from organization roles and are limited to administrative capabilities within the system. All users who are invited or authorized to use the system are considered tenant members. A Tenant Administrator can:
- Invite new tenant members.
- Remove users from the tenant.
- Assign the Tenant Administrator role to other users.
- Remove the Tenant Administrator role from other users.