Share This:

23390123_b6caaefc16_m.jpgDevOps is a great promise for organizations of all kinds to rapidly develop and deliver software products and web services to their users.

By addressing the interdependence of software development and IT operations, DevOps accelerates code delivery, enforces quality in the early stages of the development cycles, and encourages build, testing, provisioning and deployment automation.

 

Enterprises that engage in such transformation are also aware that introducing changes more often in customer-facing systems has potential to generate greater disasters.

 

“Things are going swimmingly, until the system breaks, and nobody can get it back up" (Avishai Ish-Shalom, CTO at Fewbytes Technologies).

 

 

In order to reach high degrees of agility, DevOps teams tend to initially ignore traditional IT best practices, which are impractical due to the frequency of change introduced.

However, they will not pay off in the long term as the risks of outages and inappropriate changes can far outweigh the benefits.

Moreover, whilst the trend to adopt DevOps is pushed by business needs, it does not necessarily apply to all applications, and in most cases there is co-existence of DevOps and traditional organizations, processes, infrastructure and tools.

DevOps cannot afford to be shadow IT.

Relying on automatically and accurately gathered infrastructure maps is even more critical with DevOps, which requires properly managed, monitored, and compliant infrastructure and tools.

 

Atrium Discovery (Discovery provides the most comprehensive insight into your development and production, including DevOps components. It has the ability to perform fast and in-depth scans of the largest networks, gathering information that can be leveraged to create dynamic application maps, reduce the risk of changes, lower the time to resolve incidents, and assess the security and compliance of the entire datacenter estate.

 

The patterns included in monthly Technology Knowledge Updates (TKU) offer a broad coverage of the different categories of components that need to be managed in a DevOps environment. Some examples:

• Operating Systems (Linux, Windows, Unix, Mac OS X, OpenStack)

• Virtualization Platforms (VMware, KVM, Xen, VirtualBox)

• Containerization Tools (Solaris Containers, Docker, Jetty)

• Configuration Management (Puppet, Chef, CFEngine, SaltStack, GitHub, Stash, Perforce)

• Test and Build Systems (Jenkins, Bamboo)

• Application Deployment (BMC Release Lifecycle Management)

• Application Servers (JBoss, Tomcat, Glassfish, Websphere, Weblogic)

• Web Servers (nginx, Apache, IIS)

• Queues and Caches (ActiveMQ, RabbitMQ)

• Databases (Percona Server, MySQL, PostgreSQL, OpenLDAP, MongoDB, Cassandra, Oracle, MS SQL, Redis, memcached)

• Monitoring (BMC Truesight, BMC BPPM, Sensu, New Relic, Logstash, Nagios, Sumologic, Tripwire)

 

There are more products planned in upcoming TKUs so feel free to comment on this article, post (or vote for) ideas to extend coverage, or provide any feedback.

 

Read more about DevOps:

DevOps

The Phoenix Project

BMC DevOps blog