适用于系统工程师的Docker [英] Docker for system engineers

问题描述

我接受了学习码头工作的任务。由于我不是开发人员，而是系统工程师，我想知道我们系统人员和开发人员之间是否存在严格的分界线，当涉及到docker和windows容器时。最终我没有开发人员帮助我们定制任何自定义应用程序的机会很远，因为我们的应用程序并不简单 - 我所在的部门提供基于EMC Documentum平台的自定义DMS应用程序（包括桌面和Web应用程序）在.NET / Java中。

我很清楚DevOps概念，但是在docker世界中sys eng和devs之间必须有明确的分离，否则我错了，这意味着我必须学会编写.NET / Java代码？ ： - ）

解决方案

有多种方法可以看看这个。

你能容器化吗？ "传统的"多层企业应用程序？ 一般来说，是的。

您可以将前端服务器，数据库服务器，工作服务器等全部放在容器中。 或者将其中一些组件放入容器中。

现在，这种说法是通用的吗？ 号 您必须尝试了解。

"docker"是一个管理引擎。 它管理Windows和Linux之上的容器。 容器化技术本身并不是"码头"。

'windows containers'给你一个windows内核。  "Linux容器"为您提供Linux内核。

如果您的应用程序具有易于理解的安装和配置过程，您就有可能进行DevOps样式的容器构建和发布过程。  ;但这并不意味着你需要以这种方式部署到容器中。

签出（关闭你的搜索垃圾）：  Image2Docker，Docker项目和ConvertTo-DockerFile 翻译/转换。

查看"Docker Enterprise Edition"

如果您的开发人员正在考虑Docker，因为他们想要开始构建微服务，那里有一些逻辑。 从IT角度来看，它是一个大规模扩展的企业应用程序。

Docker为您提供的另一件事，是一种非常快速地回滚到以前的图像的方法。 / p>

但同样，你可以不吞咽地啜饮DevOps Cool-Aide。 它们只是工具和查看运行和管理服务器/服务的不同方式。

Hi, I was given a task to learn docker. Since I am not developer but system engineer I want to know is there a strict dividing line between us system guys and developers when it comes to docker and windows containers in general. In the end chances of me dockerize any our custom application without developer's help are very remote since our applications are not simple - I am in a department which provides custom DMS applications based on EMC Documentum platform (both desktop and web apps written in .NET/Java).

I am well aware of DevOps concept but there must be clear separation between sys eng and devs in docker world or I am wrong meaning I would have to learn to write .NET/Java code? :-)

解决方案

There are multiple ways to look at this.

Can you containerize a 'traditional' multi-tier enterprise application?  Generally speaking, yes.

You can put the front end server, the db server, worker servers, etc. all in containers.  Or some of those components into containers.

Now, is this statement universal?  No.  You have to try to know.

"docker' is a management engine.  it manages containers on top of windows and Linux.  the containerization technology itself is not 'docker'.

'windows containers' give you a windows kernel.  'Linux containers' give you a Linux kernel.

If you have an application with a well understood installation and configuration process, you have the potential for a DevOps style Container build and publish process.  But that does not mean you need to deploy into containers that way.

Check out (dust off your search-fu):  Image2Docker, Docker Project, and ConvertTo-DockerFile  for translation / conversion.

Look at "Docker Enterprise Edition"

If your developers are thinking Docker, because they want to start building microservices, there is some logic there.  From an IT perspective, it is a massively scaled out enterprise application.

the other thing that Docker gives you, is a way to roll back to a previous image, really quickly.

But again, you can sip the DevOps Cool-Aide without swallowing.  they are just tools and different ways to look at running and managing your servers / services.

这篇关于适用于系统工程师的Docker的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！