Flashcards for:
DevOps Lifecycle

Continuous Development involves planning and coding. Tools used include version control tools like git, SVN, Mercurial, CVS, and JIRA, along with build tools like Ant, Maven, and Gradle.

Automation tools like Jenkins offer advantages such as speed, reliability, consistency, and the ability to run tests automatically upon code commits, which helps in early bug detection and continuous feedback.

The iterative nature of DevOps stages allows continuous improvement and refinements, ensuring that the product quality is incrementally enhanced with each cycle until the desired level of quality is achieved.

DevOps is a combination of Development and Operations aimed at managing the entire application lifecycle including development, testing, deployment, and operations. Its primary goals are to develop high-quality software quickly and reliably, shorten the system development lifecycle, and closely align with business objectives.

Monitoring tools like Splunk and Nagios provide real-time insights into system performance, log management, issue detection, and preventive maintenance, thus improving overall system reliability and operational efficiency.

The main drawbacks are: time-consuming nature, inability to move to the next stage without completing the previous one, unsuitability for changing requirements, no working software until late stages, and not being fit for large/object-oriented projects.

Automated Testing in Continuous Testing helps in quickly identifying bugs and saving time. Tools used include Selenium, TestNG, JUnit, and Docker (for simulating test environments). Jenkins often triggers these tests.

Continuous Integration ensures that new code integrates well with existing code by frequently merging changes into a central repository, followed by automated builds and tests to detect integration issues early.

Primary tools for Continuous Deployment include Puppet, Chef, SaltStack, Ansible, Docker, and Vagrant. The main purpose is to deploy code to production while maintaining consistency, scaling instances, and avoiding errors or failures.

Continuous Integration involves integrating new code with existing code, fetching the latest code from the repository, producing a build, and deploying it to test or production servers. Jenkins is the primary tool used for this process.

A key drawback is that it makes it difficult to validate requirements and design aspects early in the project, potentially leading to late discovery of significant issues, thus increasing cost and development time.

Continuous Deployment maintains consistency and scalability by using automation tools to ensure that deployments are repeatable and reliable. These tools manage configuration, enabling fast scaling and reducing human errors.

Version control tools in Continuous Development are significant because they help maintain and manage the code base, allowing multiple developers to collaborate efficiently, track changes, and manage different versions of the software.

The Agile Model improves upon the Waterfall Model by breaking development into iterative cycles with continuous feedback and release. A major drawback is that while it speeds up the development team, the operations team may lag, leading to conflicts between the Development and Operations teams.

Continuous Monitoring is crucial for tracking application performance and user activity, enhancing productivity, reliability, and promptly reporting issues to the development team. Tools used include Splunk, ELK Stack, Nagios, and New Relic.