Smart modeling And design .Configration management techniques and tools.

1. Configuration Management
and Deployment
Somnath More (08)
Vishwajeet Mote (10)
Akanksha Pokale (68)
Amit Puranik (79)

2. TABLE OF CONTENTS
07
05
09
01
02
03
Introduction
Steps of CM
CM tools
Benefits
Why Automation
World with CM and without CM
04 Need
08 SCM tools
10 Challenges
06
How CM fits with
Devops, CI/CD, Agile

3. Introduction
● A systems engineering process for establishing
consistency of a product’s attributes throughout
its life.
● IT management process individual
configuration of an IT system.
● IT systems are composed of IT assets that vary
in granularity.

4. Why Automation?
● Manual configuration is very tedious job.
● If any error occurs, then we first need to
identify the cause of the problem on that
server and then correct it.
● Its is very time consuming.
● Hard to maintain consistency across servers.
● Manual configuration is error prone.

5. What the world looks like with
Configuration Management
● Ensures that our assets are easily
recoverable.
● Site reliability and uptime.
● A frequent cause of downtime is bad
deployments.

6. ● A developer implementing a feature will commonly
install a few bits of software and deploy code.
● the deadline starts pressing, and the task of going back
through and rewriting the installation steps as a script
gets pushed lower and lower in priority.
The World without Configuration
Management

7. Need
Helps to develop
coordination among
stakeholders.
Maximize
productivity by
minimizing mistakes
To control the costs
involved in making
changes to system

8. Steps Of
Configuration
Management

9. Planning and Identification
● The goal is to plan for the development of the software
project and identify the items within the scope.
● Identifying items like test cases, specification
requirements,software configuration and code modules.
● Group basic details of why, when, and what changes will be
made.
● Create a list of necessary resources.

10. Version control
● Problems like Collaboration,Storing Versions,Backup and
Restoring Previous versions.
● System records all changes made by file or set of files so a
specific version maybe called Later.
● Help in managing and protecting the source code.
● Keep track of all the modifications made to the code
● Support developers workflow & not any rigid way of
working.
● eg.Github,Gitlab,TFS,Apache,etc.

11. Change Control
● Used to ensure that any changes that are made
are consistent with the rest of the project.
● Controlling ad-hoc changes requested by the
client
● Checking the merit of the change request by
examining the overall impact they will have on
the project
● Making approved changes or explaining why
change requests were denied.

12. Configuration Status Accounting
● Recording and evaluating changes made from one baseline to the
next
● Monitoring the status and resolution of all change requests
● Maintaining documentation of each change made as a result of
change requests and to reach another baseline
● Checking previous versions for analysis and testing.

13. Audits and Reviews
● Making sure that the goals laid out in the planning and
identification step are met
● Ensuring that the software complies with identified
configuration control standards
● Making sure changes from baselines match the reports
● Validating that the project is consistent and complete
according to the goals of the project.

14. How configuration management fits with
DevOps, CI/CD and agile
● Configuration data is hard to wrangle.
● The data isn't store in primary database and can be
overlooked at times.
● Need of development and adoption of new
patterns
● Complex cloud based management.
● Specifying the hardware resources and network
connections.
● Infrastructure as code.

15. CI/CD Configuration Management
● CI is continuous integration and CD is continuous
delivery.
● CI/CD configuration management utilizes pull
request-based code review workflow.
● Change requests can immediately be deployed
to a running system.

16. DevOps
Configuration
Management
● Configuration is the evolution and
automation of the systems and
contigous integration,
● It also brings system administration
responsibility under the umbrella of
software engineering.

17. Agile Configuration Management
● Configuration management enables agile teams
to clearly triage and prioritize configuration
work.
● Update the production SSL certificates.
● Change the password for dev, staging, and
production email services.

18. CM Tools
CFEngine
Puppet Ansible Docker

19. SCM tools:BitBucket Server
● The Bitbucket server is a combination of the web interface
and the GIT server offered by the Atlassian.
● It is Specially developed for professional teams which
allow to code,manage and collaborate on GIT project.
● Advantages: Provides granular permissions and claims to
provide unlimited repositories.
● Provides easy collaboration among users and enables
massive scaling.

20. ● It is developed by Microsoft to fulfill the essential
requirements of source code management.
● It works quite well for what it was designed.
Advantages:
1. Built in support for visual studio.
2. Graphic user interface.
Team Foundation Server

21. ● A considerable number of projects that are actually useful are either on
the Github or on the.
● Using it ,one can easily share his code ,presentations,and documentations in
a very decent manner.
Advanatages:
● Github is on of the Powerful source code
management tools(SCM tools)
GitHub

22. Gitlab and Gerrit
Advantages:
Single authentication
Debugging issues
Lower operating expense

23. Advantages
● Gerrit provides access control for git
repositories.
● You can push the command without using
additional command line tools.
● Allow and decline permission on repository
level and branch level.
● Supported by Eclipse.

24. Benefits
Increased Efficiency
Cost Reduction
Efficient change
management
Faster restoration
of service

25. Challenges
User involvement is very
minimal in first stage.
Lack of a configuration
management team and tools.

26. Challenges
Initial design will need to
be revisited regularly for
expansion and
contradiction of scope .
It required to ensure quality of
data for input and update of CL
data .It also required Multiple
tool.

27. Conclusión
● Importance of Automation.
● Configuration Management.
● Steps of Configuration
Management
● CM Tools
● Challenges

28. References
● https://itchronicles.com/opinion/configuration-management-
why-bother/
● https://www.atlassian.com/continuous-
delivery/principles/configuration-management
● https://www.slideshare.net/TechWellPresentations/mm-
presentation-30262014

29. Thank You !!