Devops

DevOps as the name suggests is composed of two words, Dev and Ops, i.e. Development and Operations. Development as in Application or Software development and Operations as in IT Operations. Traditionally these two streams have been distinct with a strict boundary between the two work streams.

 DevOps is a melding of these two work streams to bring in cohesion between the Development and IT Operations teams for better and transparent communication and collaboration.

 Even though these are two different streams (Development and IT Operations) with specific skill set, DevOps (Dev and IT Ops) brings in faster and smooth deployment cycles. Earlier or traditional Development handing off to Operations was slow and had rigid deployments. If things broke in production, the version is sent back to Development for a fix with a bug report, Development would reproduce the issue, provide a fix and send to Operations for deployment. This traditional cycle from Application Development, to testing and finally to deployment in Operations introduced delays and lacked agility. DevOps philosophy promises to bring in faster deployment of code and Application to production. DevOps is an approach to software delivery. DevOps facilitates Development team think like Ops and Ops folks think like Dev. In other words DevOps breaks the silo mindset and introduces the culture of collaboration between the two teams, resulting in faster deployment of code into production. The focus of DevOps is on end to end responsibility of Application deployment and delivery, the lifecycle, from plan, design, build, test, release to deployment in production.




Devops is a Philosophy, not a methodology (yet)

Project Management has PMBOK published best practices
Agile has a Agile Manifesto

 Framework, Methodology, Best Practice, Standard

Comments

  1. Azure DevOpsSeptember 5, 2019 at 3:39 AM

    This blog is having the good information.
    DevOps Online Training

    ReplyDelete
  2. Basit MehtabJanuary 27, 2020 at 1:36 AM

    Amazing write-up
    what a fantastic post, this is so useful information cant wait to utilize, thank you for sharing this post, looking more form your side.

    ReplyDelete

Post a Comment

Popular posts from this blog

VMware fix for Invalid manifest and ova file import failed errors

Image
Recently we got a OVA file for a virtual machine. The vendor instructions were to import the ova file in vmware Workstation, Player for Windows/Linux, Fusion for Mac, and VirtualBox as well.  The instructions were to take the available package and launch the VM with VMware workstation. The package contained  Module.mf, Module.ovf and Module-disk.vmdk and a Module.ova file. The .mf and .ovf file were 2 KB each whereas the vmdk was several gigs. The package also contained a Module.ova file which was several gigs as well. OVF           Open Virtualization Format MF             Manifest file VMDK       Virtual Machine Disk OVA           Open Virtualization Appliance The ovf file is a xml file that contains metadata for the ovf package The mf file contains the SHA1 hash codes of all files in the package The vmdk file is the disk image of the virtual machine,  VMware Workstation or VirtualBox. (vmdk format was originally developed by VMware and is an open format now). All of
Read more

SOAPUI - import certificate

Image
Note: SoapUI has two versions, one is open source and second Professional version. The open source can be download here . (confirmed link 12/19/2018). SSL Handshake issue:   There is an Issue in SoapUI version 5.3.0 (and 5.2.0 version) with SSL handshake error. It was resolved by updating below in vmoptions file ( refer here ). However, the error that shows up while trying to load wsdl is "Error loading WSDL" as below The fix is to Enable TLS 1.2 protocol for SOAP/REST calls in SoapUI, by ammending the vmoptions file to add the directive for TLS as (-Dsoapui.https.protocols=TLSv1.2). Refer here . Update: Version 5.5.0 does not have this issue. If you are on 5.3.0 better upgrade to 5.5.0 which is available now (Feb 2019). I had above issue as well as another issue reaching to https endpoint. Upgrade to 5.5.0 resolved issue. Select "Check for updates" under the Help menu and you will get option for upgrade. Select upgrade current version and accept all defaul
Read more

Session Timeout in Oracle Access Manager

Image
Session Timeout in Oracle Access Manager (OAM) The session lifetime and Idle timeout entries control how long a user's session is valid. In OAM, a user session is an object which represents an authenticated user. This object is stored in the server memory and if Database session persistence is enabled, this object is stored or available in the database. Each session is unique and is identified by both a userid and Session ID (session identifier), see screenshot below "OAM User Session Management".  A valid session means a user has been authenticated with OAM. A session can have following three states: 1) active 2) inactive 3) expired When a session is created it is in active state and is available as an object in the OAM. After a set time - idle timeout, the session moves or transitions to inactive state. And finally after the Session Lifetime time, the session is marked as expired. Expired sessions are removed from server memory. Read more about Session Lifetime
Read more