I had the opportunity to catch up with Chris Corriere – DevOps Engineer at AutoTrader – to talk about his experiences in the realm of Rugged DevOps. We discussed automation, culture and collaboration, and which thought leaders he is following.
Chris Corriere: Hey, I’m Chris Corriere. I’m a DevOps Engineer AutoTrader.
Derek Weeks: Today we’re going to talk about Rugged DevOps. It’s a subject that’s gaining a lot of traction in the community but not a lot of people are really familiar with what it is.
IoT Will Transform Commerce | @ThingsExpo #IoT #DigitalTransformation
From fitness trackers to connected refrigerators to coffee makers, there is no end to how smart even the most inane technology can become. The Internet of Things (IoT) isn’t just changing how consumers manage their home security or order their coffee filters – it’s revolutionizing the very fabric of commerce.
However, according to Gartner, IoT is still in its early days of maturity. Gartner predicts that through 2018 there will be no one prevailing IoT ecosystem platform. This means that in the next few years there will be a proliferation of different devices, products and approaches to IoT. In fact, Cisco predicts that there will be a whopping 50 billion connected devices by 2020.
[session] Redis Functions and Data Structures By @DaveNielsen | @CloudExpo #Cloud
Redis is not only the fastest database, but it has become the most popular among the new wave of applications running in containers. Redis speeds up just about every data interaction between your users or operational systems.
In his session at 18th Cloud Expo, Dave Nielsen, Developer Relations at Redis Labs, will shares the functions and data structures used to solve everyday use cases that are driving Redis’ popularity.
Rackspace and Cloud Technology Partners announce strategic partnership
Rackspace and Cloud Technology Partners have announced a strategic partnership to deliver professional and managed services, geared around the AWS public cloud offering.
The partnership will focus on a number of areas including cloud strategy & economics, security & governance, application portfolio assessment, DevOps & automation and application modernisation, migration & development, with the aim of accelerating enterprise adoption of cloud technologies.
“We are seeing increasing demand from enterprises that are seeking help moving to AWS and Azure, and then successfully managing their environments once deployed,” said Taylor Rhodes, CEO of Rackspace. “CTP is a recognised leader in helping enterprises move to the cloud and is a natural complement to our managed services expertise. Together, we provide the market leading solution that helps enterprises accelerate their realisation of cloud benefits.”
The partnership is seemingly build on the perception an enterprises adoption of cloud technologies is slowed due to the digital transformation programmes which are needed before the benefits of the cloud can be realized. The new partnership claims this process can be accelerated through combining the expertise of both organizations into one offering; Cloud Technology Partners will offer initial integrations and ongoing optimization work, whereas Rackspace provide managed services.
“Working with Rackspace was an obvious fit based on their managed cloud leadership and our shared emphasis on supporting customers through every phase of their cloud journey,” said Chris Greendale, CEO of Cloud Technology Partners. “Our prescriptive approach to public cloud adoption has been hugely successful for enterprise customers and we are very excited at the opportunity these combined services provide for both companies.”
[session] Don’t Forget the Ops: Build Operations into Your Cloud By @BMCSoftware | @CloudExpo #Cloud
Many private cloud projects were built to deliver self-service access to development and test resources. While those clouds delivered faster access to resources, they lacked visibility, control and security needed for production deployments.
In their session at 18th Cloud Expo, Steve Anderson, Product Manager at BMC Software, and Rick Lefort, Principal Technical Marketing Consultant at BMC Software, will discuss how a cloud designed for production operations not only helps accelerate developer innovation, it also delivers the control that IT Operations needs to run a production cloud without getting in the way.
Docker security: How to monitor and patch containers in the cloud
(c)iStock.com/bugphai
Nearly a quarter of enterprises are already using Docker and an additional 35% plan to use it. Even sceptical IT executives are calling it the future. One of the first questions enterprises ask about containers is: What is the security model? What is the fallout from containerisation on your existing infrastructure security tools and processes?
The truth is that many of your current tools and processes will have to change. Often your existing tools and processes are not “aware” of containers, so you must apply creative alternatives to meet your internal security standards. The good news is that these challenges are by no means insurmountable for companies that are eager to containerise.
Monitoring & IDS
The most important impact of Docker containers on infrastructure security is that most of your existing security tools — monitoring, intrusion detection, etc. — are not natively aware of sub-virtual machine components, i.e. containers. Most monitoring tools on the market are just beginning to have a view of transient instances in public clouds, but are far behind offering functionality to monitor sub-VM entities.
In most cases, you can satisfy this requirement by installing your monitoring and IDS tools on the virtual instances that host your containers. This will mean that logs are organised by instance, not by container, task, or cluster. If IDS is required for compliance, this is currently the best way to satisfy that requirement.
Key takeaway: Consider installing monitoring and security tools on the host, not the container.
Incident forensics and response
Every security team has developed a runbook or incident response plan that outlines what actions to take in the case of an incident or attack. Integrating Docker into this response process requires a significant adjustment to existing procedures and involves educating and coordinating GRC teams, security teams, and development teams.
Traditionally, if your IDS picks up a scan with a fingerprint of a known security attack, the first step is usually to look at how traffic is flowing through an environment. Docker containers by nature force you to care less about your host and you cannot track inter-container traffic or leave a machine up to see what is in memory (there is no running memory in Docker). This could potentially make it more difficult to see the source of the alert and the potential data accessed.
The use of containers is not really understood by the broader infosec and auditor community yet, which is potential audit and financial risk. Chances are that you will have to explain Docker to your QSA — and you will have few external parties that can help you build a well-tested, auditable Docker-based system.
That said, the least risk-averse companies are already experimenting with Docker and this knowledge will trickle down into risk-averse and compliance-focused enterprises within the next year. Logicworks has already helped PCI-compliant retailers implement Docker and enterprises are very keen to try Docker in non-production or non-compliance-driven environments.
Key takeaway: Before you implement Docker on a broad scale, talk to your GRC team about the implications of containerisation for incident response and work to develop new runbooks. Or try Docker in a non-compliance-driven or non-production workload first.
Patching
In a traditional virtualised or AWS environment, security patches are installed independently of application code. The patching process can be partially automated with configuration management tools, so if you are running VMs in AWS or elsewhere, you can update the Puppet manifest or Chef recipe and “force” that configuration to all your instances from a central hub.
A Docker image has two components: the base image and the application image. To patch a containerised system, you must update the base image and then rebuild the application image. So in the case of a vulnerability like Heartbleed, if you want the ensure that the new version of SSL is on every container, you would update the base image and recreate the container in line with your typical deployment procedures. A sophisticated deployment automation process (which is likely already in place if you are containerised) would make this fairly simple.
One of the most promising features of Docker is the degree to which application dependencies are coupled with the application itself, offering the potential to patch the system when the application is updated, i.e., frequently and potentially less painfully. But somewhat counterintuitively, Docker also offers a bright line between systems and development teams: systems teams support the infrastructure, the compute clusters, and patch the virtual instances; development teams support the containers. If you are trying to get to a place where your development and systems teams work closely together and responsibilities are clear, this is an attractive feature. If you are using are a Managed Service Provider (like Logicworks), there is a clear delineation between internal and external teams’ responsibilities.
Key takeaway: To implement a patch, update the base image and then rebuild the application image. This will require systems and development teams to work closely together, and responsibilities are clear.
Almost ready for prime time
If you are eager to implement Docker and are ready to take on a certain amount of risk, then the methods described here can help you monitor and patch containerised systems. At Logicworks, this is how we manage containerised systems for enterprise clients every day.
As AWS and Azure continue to evolve their container support and more independent software vendors enter the space, expect these “canonical” Docker security methods to change rapidly. Nine months from now or even three months from now, a tool could develop that automates much of what is manual or complex in Docker security.
When enterprises are this excited about a new technology, chances are that a whole new industry will follow.
The post Docker Security: How to Monitor and Patch Containers in the Cloud appeared first on Logicworks Gathering Clouds.
Bringing Automation to the Helpdesk | @CloudExpo #Cloud
Automation and ITSM-driven insights endow help desk personnel with more knowledge and provide a single point of support for end users, regardless of their needs while still catering to their preferred method of help.
We’ll learn how automation and ITSM-driven insights endow help desk personnel with more knowledge and provide a single point of support for end users, regardless of their needs while still catering to their preferred method of help.
[session] Multi-Layer DDoS Mitigation Strategies by @WebairInc | @CloudExpo #Cloud
In his session at 18th Cloud Expo, Sagi Brody, Chief Technology Officer at Webair Internet Development Inc., will focus on real world deployments of DDoS mitigation strategies in every layer of the network. He will give an overview of methods to prevent these attacks and best practices on how to provide protection in complex cloud platforms. He will also outline what we have found in our experience managing and running thousands of Linux and Unix managed service platforms and what specifically can be done to offer protection at every layer. He will offer insight and examples from both a business and technical perspective.
Ericsson restructures to prioritize cloud market segments
Swedish networking giant Ericsson accompanied its Q1 2016 numbers with a new company structure and a reshuffle of the executive leadership team, writes Telecoms.com.
The top-line numbers were pretty much flat year-on-year, as you can see from the table below, with a strong quarter for IPR and licensing revenue offset by a weak macroeconomic environment in emerging markets. Telecoms.com spoke to Ericsson CFO Jan Frykhammar to get the inside view.
“Our quarter had its challenges and strengths as always,” he said. “We have a weak macroeconomic environment in some parts of the world, mainly emerging markets. While this is nothing strange after many quarters, even years, of challenges on the macro side, driven by things like oil price and other factors, it’s tough for many of our customers to keep up their investment levels. And then we have lower mobile broadband activity in Europe at the back end of this quarter, including one big customer project that has been completed.
“So we focus on doing everything we can to take care of the things we can control. We continue to deliver on the cost and efficiency programme and we are adding additional measures related to lower volumes. So we’re adapting the company to a challenging environment.”
The restructure essentially splits the company more clearly into its core, legacy, networks business and the areas it has been openly targeting for growth, as follows:
- Business Unit (BU) Network Products, headed by Arun Bansal
- BU Network Services, headed by Fredrik Jejdling
- BU IT & Cloud Products, headed by Anders Lindblad
- BU IT & Cloud Services, headed by Jean-Philippe Poirault
- BU Media with central go-to-market model, headed by Per Borgklint
- Customer Group Industry & Society with central go-to-market model, headed by Charlotta Sund
As you can see both the legacy networks and higher growth cloud segments are sub-divided into products and services, while media seems to be semi-autonomous. The industry and society group is more of a formal sales channel to make Ericson better at targeting industries outside of its core markets, especially utilities, transport and public safety.
“The purpose of this new set-up is to get enough focus, dedicated people and accountability to drive both sales in growth areas and at the same time make sure we remain focused on our core customers,” said Frykhammar. “This business unit structure will also help the market to better follow our progress in these areas. We’ve been talking a lot about targeted areas and now the investment buckets will fall wholly into these new business units.”
The changes to the executive leadership team seem to amount to a refresh, rather than a major overhaul. “The last time we had a major global reorganisation of the company was in 2010 and our industry has undergone a lot of change in that time,” said Frykhammar. “We think this is a good opportunity to bring some new people into the leadership team.”
Frykhammar was keen to stress the ongoing challenges in the broader macroeconomic environment and that Ericsson is acutely aware of them. For a while Ericsson’s quarterlies have been about trying to create a narrative around an essentially flat growth story and the company will be hoping to be able to focus attention on solid growth numbers in the from the cloud and media business when it starts reporting along those lines in Q1 2017.
CTERA aims for converged infrastructure customers with updated cloud storage portfolio
(c)iStock.com/JackyLeung
CTERA Networks has introduced a number of updates to its cloud storage gateway portfolio to improve flexibility, efficiency and storage capacity for remote office IT environments.
The new line-up can be deployed from KVM or VMware servers, which is suited for organisations investing in virtualised or converged infrastructure IT. It also includes a virtual application configuration for enterprises to use current their remote office/branch office (ROBO) hardware, while also getting the full benefits and functionality of their CTERA cloud storage gateway.
Additionally, CTERA has re-engineered its gateway file management system, with the primary file system executed and maintained within the cloud. It selectively syncs files to branch or remote offices according to the policies defined by the user or IT administrator. The appliances work as extra storage tiers in a cloud-based file synchronisation and management system. CTERA Sync Gateways can now support up to 64 TB of local volume size, which is a fourfold rise from older models.
CTERA’s virtual and physical cloud storage gateways can function as comprehensive storage applications to replace legacy tape backup, file/NAS servers and proprietary systems with a single cloud-integrated system. The gateway is part of the Enterprise File Services Platform from CTERA, enabling organisations to protect and manage data cross applications and offices from their own virtual or private cloud.
The company’s new cloud storage portfolio aims to lower total cost of ownership with its virtual form factor, implement high-availability office file services for remote environments, and expand virtual storage volume. The portfolio also enables on-demand file and data protection service deployments using a virtual appliance, and provides a path for converged IT.
Previous research from the company, released in July last year, found that three quarters of organisations were looking at an alternative for their public file, sync and share services. Speaking to CloudTech at the time, VP strategic marketing Rani Osnat explained how both public SaaS services and enterprise-grade storage can harmonise together. «The market is growing so much there is room for both of these things,» he said. «Companies like Box will continue to grow while private deployments also grow in parallel; these things will live side by side.»