l6 Operations Flashcards
IT System-Management: Governance
- Service Catalog
- Knowledge Base
- Asset Management
IT System-Management: Changes / Deployments
- Asset Management
- Change Management
- Problem Management
- Incident Management
IT System-Management: Operations by Process
- Incident Management
- Service Desk
- Service Catalogment
API-Management
All API-Accesses must be provided through a
centralized portal:
* Clear (horizontal) separation of concerns
* Who owns which application?
* Protection of APIs against Brute Force, Internal
Denial of Service “Usages”
* Versioning of APIs becomes necessary
* Automatism necessary
* For Signup
* For registration
* Fits best with Gitops
Incident Management by ITIL
- Input varies, workflow stays static:
One Workflow for all services - If not major, incidents may get stuck
- Hard to determine correlations
- If major, hot potato game starts
- Supplies
- Internal Teams
- Operations
- After major, hot potato game continues
- intransparency
Incidents managed by DevOps
ncidents are handled tool centric / team centric
The workflow must fit the team, the availability must be hold
* Establish structures for services beforehand
* Warroom
* Communication Channels
* Internally
* externally
* Rely on each other à all hands on deck
* If you have a major, you will recognize it
* Be transparent afterwards, identify technical debt and increase availability
Innersource
Innersource refers to the practice of applying open source development methodologies and best practices within an organization. This approach encourages collaboration, transparency, and shared ownership among teams, even though the code remains private to the organization.
Commonly used Software should be owned by one
team but maintained by multiple teams:
* Monitoring Dashboards
* CI/CD-Pipelines
Maintaining together defines de facto standards:
* Open Source for internal usage
* Enforces high quality standards
