Docker delivers both an engine for innovation that modernizes without disruption while reducing total costs by more than 50%. The Docker platform is the only container platform to build, secure and manage the widest array of applications from development to production both on premises and in the cloud. Unlike other solutions that specialize in a narrow slice of the enterprise IT portfolio, Docker delivers operations at scale by addressing a diverse set of applications and infrastructure for both developers and IT. Docker Community Edition [CE] empowers developers with tools to build applications and Docker Enterprise Edition [EE] provides IT with multi-architecture operations at scale.
The audience for this document includes, but is not limited to, sales engineers, field consultants, professional services, IT managers, partner engineers, IT architects, and customers who want to take advantage of an infrastructure that is built to deliver IT efficiency and enable IT innovation. The reader of this document is expected to have the necessary training and background to install and configure Red Hat Enterprise Linux, Cisco Unified Computing System (UCS) and Cisco Nexus Switches as well as high level understanding of Docker Container components. External references are provided where applicable and it is recommended that the reader be familiar with these documents.
This capability is useful in multi-tenant cloud computing. Policy Based Resource Classification —Once a compute resource is discovered by UCS Manager, it can be automatically classified to a given resource pool based on policies defined. This CVD showcases the policy based resource classification of UCS Manager.
This provides great flexibility where different experts from different domains, such as network, storage, security, server and virtualization work together to accomplish a complex task. Loose Referential Integrity —In UCS Manager, a service profile, port profile or policies can refer to other policies or logical resources with loose referential integrity. A referred policy cannot exist at the time of authoring the referring policy or a referred policy can be deleted even though other policies are referring to it. This provides different subject matter experts to work independently from each-other.
Cisco and Docker have joined hands to offer Container Management Solution on Cisco UCS Infrastructure with Docker Datacenter. The combination of Docker container technology and Cisco UCS server hardware enables a highly scalable, resilient, and elastic application deployment environment with the simplicity of the on-premise cloud like experience. This enables enterprises to modernize traditional applications and build Microservices architecture using the Docker platform and tools on Cisco’s proven Cisco UCS Integrated Infrastructure.
A couple of months ago Shameerali Kolothum Thodi (or Shameer for short) from HiSilicon, a subsidiary of Huawei, contacted me and asked for help to get Docker running on their brand-new ARMv8 development board. We agreed on a collaboration and I got remote access to a 16-core ARMv8 Cortex-A57 machine.
Since one application would have problems and affect other applications, we decided to invest in separating our concerns and move each application to its own set of servers. At the same time, we thought it would be more cost effective for us to move to the cloud rather than run and manage our own data centers. After some price comparisons and consulting with other nonprofits, we decided to go with Amazon and their OpsWorks service to help with automation.
Cisco UCS Fabric Interconnect – Cisco UCS has Fabric Interconnects in redundant mode to provide no-single point of failure for the application container’s data path. Following tests were performed and have passed with no impact on the container application’s data path:. Since vNICs are configured for Fabric failover, in the event of any uplink, upstream Cisco Nexus 9000 Series switch and Cisco Fabric Interconnect failure data path of the application containers fails over automatically to the redundant fabric interconnect.
All host traffic is carried across these two vNICs in this design. To create virtual network interface card (vNIC) templates for Cisco UCS hosts, complete the following steps. Two vNICs are created for redundancy – one through Fabric A and another through Fabric B.
· Host – In this type of network, a newly created container shares its network namespace with the host, providing higher performance and eliminating the need for NAT. The bottle-neck in this type of network is port-conflicts and since container has full-access to hosts interfaces it run into security risks.
Cisco and Docker announced a partnership to automate containers for UCS. An example IBM gives is. Facebook Refreshes Its Server Hardware Fleet. AMD Previews Its New Naples. Today at the Open Compute Summit (OCP) 2017. This is a major development in terms of data storage density.
Docker is great for running containers in one host, and provides all required functionality for that purpose. But in today’s distributed services environment, the real challenge is to manage resources and workloads across servers and complex infrastructures.