Welcome!

@DevOpsSummit Authors: Zakia Bouachraoui, Yeshim Deniz, Elizabeth White, Liz McMillan, Pat Romanski

Related Topics: @DevOpsSummit, Linux Containers, @CloudExpo

@DevOpsSummit: Blog Feed Post

Our New Boundary Integration is Here By @VictorOps | @DevOpsSummit [#DevOps]

Network visibility and access to real-time data surrounding your infrastructure is pretty important, don’t you think?

Our New Boundary Integration is Here

By Samantha Haltman

Network visibility and access to real-time data surrounding your infrastructure is pretty important, don’t you think? With Boundary, users can identify problems quickly, and ensure their applications and supporting infrastructure are running smoothly and at peak efficiency.

We are happy to announce that our integration with Boundary, providers of IT monitoring for DevOps teams, is now available. Getting the Boundary integration up and running is as easy as copying and pasting an API key, which can be found in your VictorOps admin interface. Just click on the Integrations tab and choose ‘Boundary’. You will then see an API token to provide to the Boundary UI. Piece of cake.

Here is a little walk through to help you with the process:

1. Log into your VictorOps account (you will need to have admin privileges). Click on settings –> integrations –> Boundary:

Screen Shot 2015-02-26 at 6.11.47 PM

2. Log into your Boundary account. Click “Settings” to open the dialog and go to Actions tab. Click on the “Add Action” button and select “VictorOps” on the next screen and click “Add”:

Screen Shot 2015-02-26 at 6.23.54 PM

3. You will now be redirected to the VictorOps configuration page. Add in the API key which you received from VictorOps admin interface, and an arbitrary routing key (such as ‘Infrastructure’):

Screen Shot 2015-02-26 at 6.29.01 PM

4. Once the VictorOps action is created, you can now attach it to new or existing alarms:

Screen Shot 2015-02-26 at 6.28.22 PM

As always, you can read more about this integration in our Knowledge Base and if you need any help getting your Boundary integration setup, feel free to contact us any time. Happy monitoring!

The post Our New Boundary Integration is Here appeared first on VictorOps.

Read the original blog entry...

More Stories By VictorOps Blog

VictorOps is making on-call suck less with the only collaborative alert management platform on the market.

With easy on-call scheduling management, a real-time incident timeline that gives you contextual relevance around your alerts and powerful reporting features that make post-mortems more effective, VictorOps helps your IT/DevOps team solve problems faster.

@DevOpsSummit Stories
As you know, enterprise IT conversation over the past year have often centered upon the open-source Kubernetes container orchestration system. In fact, Kubernetes has emerged as the key technology -- and even primary platform -- of cloud migrations for a wide variety of organizations. Kubernetes is critical to forward-looking enterprises that continue to push their IT infrastructures toward maximum functionality, scalability, and flexibility.
The Kubernetes vision is to democratize the building of distributed systems. As adoption of Kubernetes increases, the project is growing in popularity; it currently has more than 1,500 contributors who have made 62,000+ commits. Kubernetes acts as a cloud orchestration layer, reducing barriers to cloud adoption and eliminating vendor lock-in for enterprises wanting to use cloud service providers. Organizations can develop and run applications on any public cloud, such as Amazon Web Services, Microsoft Azure, Red Hat OpenShift and Google Cloud Platform.
Because Linkerd is a transparent proxy that runs alongside your application, there are no code changes required. It even comes with Prometheus to store the metrics for you and pre-built Grafana dashboards to show exactly what is important for your services - success rate, latency, and throughput. In this session, we'll explain what Linkerd provides for you, demo the installation of Linkerd on Kubernetes and debug a real world problem. We will also dig into what functionality you can build on top of the tools provided by Linkerd such as alerting and autoscaling.
With container technologies widely recognized as the cloud-era standard for workload scaling and application mobility, organizations are increasingly seeking to support container-based workflows. In particular, the desire to containerize a diverse spectrum of enterprise applications has highlighted the need for reliable, container-friendly, persistent storage. However, to effectively complement today's cloud-centric container orchestration platforms, persistent storage solutions must blend reliability and scalability with a simple, cloud-native user experience. The introduction of Elastifile's CSI driver addresses these needs by augmenting containerized workflows with highly-available, scalable NFS file storage delivered via Elastifile Cloud File System...and with no complex, manual storage provisioning required.
Applications with high availability requirements must be deployed to multiple clusters to ensure reliability. Historically, this has been done by pulling nodes from other availability zones into the same cluster. However, if the cluster failed, the application would still become unavailable. Rancher’s support for multi-cluster applications is a significant step forward, solving this problem by allowing users to select the application and the target clusters, providing cluster specific data. Rancher then initiates deployment to those clusters.