Please enable JavaScript.

Coggle requires JavaScript to display documents.

DevOps Knowledge (Project :!: (Two products one written in Java (with CLI…

- - - - Builder :check:
      - Abstract factory :check:
      - Prototype :check:
      - Singleton :check:
    - - Adapter :check:
      - Decorator :check:
      - Facade :check:
      - Composite
      - Bridge
      - Proxy
      - Flyweight
    - - Interpreter
      - Iterator
      - Chain of responsibility :check:
      - Template method :check:
      - Visitor
      - Strategy :check:
      - Command
- - - - ' ' - won't retrieve value from $
      - " " will retrieve value from $
      - [[ ]] - let you use && and || < >,
      - while getopts, shift
      - if elif then
        
        -gt
        
        -lt
        
        -ge
        
        -ne
      - arrays
        
        farm_hosts[] get all elements in different strings
- - - - New Relic
      - Zabix
      - Nagios
    - - Jenkins
      - TeamCity
    - - Git
      - SVN
      - PErfroce
      - Mercurial
    - - Chef
      - Puppet
      - Ansible
- - - - Connection based
      - Handle retransmissions
      - Three step handshake
        
        SYN
        
        SYN + ACK
        
        ACK
    - - connection less
      - stateless
      - Structure
        
        General header
        
        Request header
        
        Response header
        
        entity header
        
        message body
      - Requests
        
        GET
        
        POST
        
        PUT
        
        DELETE
      - Responses
        
        1xx: Informatuional
        
        2xx: success
        
        200 ok
        
        202 Accepted
        
        201 created
        
        3xx: redirection
        
        4xx: Client error
        
        400 Vad request
        
        403 ^ 301 - unauthorized
        
        404 - not found
        
        5xx: server error
        
        500 internal server error
        
        503 Service unavailable
    - - Connection less
      - no confirmation
      - fast but not realiable
- - - - Product owner
      - Development team
        
        Shared responibility
        
        Schould be cross functional
      - Scrum master
    - - Sprint
      - Planning
        
        What can be done?
        
        How will it be done?
      - Review
        
        Wha has and hasn't been done?
        
        What probles we encountered?
        
        What is role of the story in context of whole the backlog?
        
        What is business value?
      - Retro
        
        What went good?
        
        What went bad?
        
        What and how can we improve?
      - Refinement
        
        Grooming a backlog
        
        Learinging technical and business context for stories
        
        Giving estimates
      - Daily scrum
        
        making sure that we are on track
        
        Synchronizing work
    - - Product backlog
      - Sprint backlog
      - DOD
      - acceptance criteria
      - Burnout chart
  - - - Service support
        
        Service desk
        
        SPOC
        
        Incident management
        
        Problem management
        
        Handling the root cose of incident
        
        Configuration management
        
        CMDB
        
        Change management
        
        Release management
      - Service delivery
      - Security managment
      - Application managment
- - - - Testing functionalities of the system a s a blackbox
    - - Stability
      - Capacity
      - Scalability
      - Performence
      - Security
  - - - Performed not in runtime
      - Like checkstyle
    - - Perfromed during runtime
      - eg. measuring response times, Memory allocation
- - - - everything is stored as snapshots and its bringing up togheter when neccesary
    - - Each object linke trunk, branches, tags has it own directory
  - - - Everything should be commited to master as often as possible
      - Avoids merging hell
      - Simple and closest to CI spirit
    - - feature branches
        
        Every feature has its own branch
        
        master contains only finished fetures
        
        When feature is finished is merged to master
      - Develop and master branch
        
        Master only realeased code with tags for different versions
        
        Develop is tracked branch for developers for everyday coding
      - Release branches
        
        Are stage between feature branches and master branch
        
        Place were all polishing and additional release related task are performed
      - Hot fix
        
        Branch where some hotfix can be done