As containers gain popularity for a broad variety of use cases, entrepreneurs and infrastructure software investors are focused on investing in the machinery around containers. But there is a particular notion that is emerging, which needs a name. Today I’m proposing that we start using the term container-native to refer to this notion.

I researched (googled) the term to learn how it was being used today. Turns out it is being used to refer to the idea of running containers on bare metal (rather than on VMs).What a narrow use of a beautiful term! There should be a new definition for container-native that aims to better represent the magnitude of impact that containers will have on software development and operations.

Pretty much as in other once-an era shifts, legacy players infrequently make the move meaningfully. This happens for a couple reasons: either (a) they don’t comprehend the size or essentialness of the movement, or (b) they comprehend it however are stuck offering the wrong design and have motivations to treat parts of the new engineering as registration things in their informing to the business sector, or (c) they are irritated or baffled by the early overhype.

To delineate what holder local can mean from an assortment of edges, here are brisk case in (i) bundling, (ii) persistent combination and arrangement, (iii) application lifecycle administration (ALM), (iv) queueing and lambda structures, (v) checking, and (vi) securityPackaging

Joe Beda (formerly of Google, now an EIR at Accel, and advisor to Shippable and CoreOS)argues that the container community has focused heavily on environments to host containers (such as CoreOS and others), and tools to orchestrate containers (such asDocker Swarm, Kubernetes, Mesosphere and others), but not enough on tools to better understand what’s going inside the container itself. He calls out the following specific problems:
3bf8a129b.jpgNo package introspection. At the point when the following security issue tags along it is hard to effortlessly see which pictures are powerless. Moreover, it is difficult to compose mechanized strategy to keep those pictures from running.

No simple sharing of bundles. In the event that [two] pictures introduce the same bundle, the bits for that bundle are downloaded twice. It isn’t remarkable for clients to develop confused “inheritence” chains to work around this issue.

No surgical bundle upgrading. Redesigning a bundle requires reproducing a picture and re-running all downstream activities in the Dockerfile. In the event that clients are great about following which sources go into which picture, it ought to be conceivable to simply overhaul the bundle yet that is troublesome and blunder inclined.

Request subordinate picture constructs. Request matters in a Dockerfile — notwithstanding when it doesn’t need to. In many cases two activities have zero collaboration with each other. In any case, Docker has no chance to get of realizing that so should accept that each activity relies on upon all first activities.

Package manager cruft

Immutable Servers are a deployment model that mandates that no application updates, security patches, or configuration changes happen on production systems. If any of these layers needs to be modified, a new image is constructed, pushed and cycled into production. The advantages of this approach include higher confidence in the code that is running in production, integration of testing into deployment workflows, verifiability that systems have not been compromised.

Once you become a believer in the concept of immutable servers, then speed of deployment and minimizing vulnerability surface area become objectives. Containers promote the idea of single-service-per-container (microservices), and unikernels take this idea even further.

Companies such as Nirmata and Mesosphere (with Velocity) have been pushing similar messages; notice that containers are in the process of changing the best practices for DevOps reflecting the need for container-native and not general purpose tools:

“Containers require new tooling for automation and management of applications.”

Security & Monitoring

Obviously, as compartments get put into generation, ventures need the same affirmations around holder based advances that they’ve had for their legacy stacks. Security and checking are both key zones where more established items miss the mark. Compartment particular methodologies are fundamental.

Driving the charge in checking is Sysdig (divulgence: Bain Capital is a speculator, and a week ago we declared a $15M Series B financing that we co-drove with Accel Partners), who reported as of late their associations with Kubernetes and Mesosphere to empower more steady application arrangement.

The fame of Sysdig’s open source holder investigating arrangement, and the interest for their business checking item, in a focused observing business sector with a lot of existing open source systems (Zabbix, Zenoss) and all around financed business merchants (New Relic, AppDynamics) confirmations the requirement for a compartment local item to fill the crevices left by different sellers.

In security, Sysdig’s holder local methodology permits it to see each and every framework bring in each procedure in each compartment; other essential holder local methodologies incorporate CoreOS, with their rkt system. The message that conventional security approaches don’t address the difficulties postured by holder is resounding:

The very components of holders that make them so practical and simple to utilize, additionally achieve another arrangement of security difficulties. Compartments are helpless against digital assaults in three principle ways: 1. Compartments work on a mutual portion, making them adaptable, additionally making it less demanding for programmers to taint every single other holder running on the same host; 2. The clients of virtual holders have not very many controls to farthest point or screen their product use, making them prime insider dangers; 3. Since holders are independent, they regularly incorporate obsolete, powerless and resistant parts, subsequently putting the whole framework at danger. — Scalock.

You may contend that being compartment local may not be adequately separating to create enduring business, and that holder local may turn into a subset of usefulness offered by legacy sellers. Surely, numerous huge organizations will have the capacity to create items that are “sufficient” to adapt to a large number of holder use cases. My gut however, is that it’s an outlook change.

Source: http://www.theatlantic.com/technology/archive/2013/12/the-shipping-container/281888/




SMC Containers supplies a diverse complement of premier quality shipping containers to meet varied specifications. SMC supplies special and standard containers, container fittings, marine equipment, shipbuilding steel products used for storage, workshops and can be converted into offices, ablutions etc. For more information, please refer to our website.





Shanghai Metal Corporation

As an integrated global manufacturer, supplier of metal related products and reliable services we dedicate this blog to manifest our interests on different topics that would surely brighten your mind everyday. Each article is suited for every types of reader because we value simplicity as the key to transmit messages. Follow us and stay updated ~! Visit our main website to learn more about us : http://www.shanghaimetal.com/ Our address : 20th Floor Yuan Mansion, 738 Dongfang Road, Shanghai, China 200122 Email : shanghaimetalcorp@gmail.com Skype : shanghaimetal Telephone : +86 21 6875 6127 Monday - Friday : 9am - 5pm Saturday & Sunday : Available by appointment


Fill in your details below or click an icon to log in:

WordPress.com 徽标

您正在使用您的 WordPress.com 账号评论。 注销 /  更改 )

Facebook photo

您正在使用您的 Facebook 账号评论。 注销 /  更改 )

Connecting to %s