From f5819922c057d71aa86d4cefebe36f54c757420a Mon Sep 17 00:00:00 2001 From: Weblate Date: Mar 16 2023 15:34:34 +0000 Subject: Added translation using Weblate (Finnish) Co-authored-by: Weblate --- diff --git a/po/fi/master/pages/terminology/use_cases.po b/po/fi/master/pages/terminology/use_cases.po new file mode 100644 index 0000000..7e67332 --- /dev/null +++ b/po/fi/master/pages/terminology/use_cases.po @@ -0,0 +1,312 @@ +# SOME DESCRIPTIVE TITLE +# Copyright (C) YEAR Free Software Foundation, Inc. +# This file is distributed under the same license as the PACKAGE package. +# FIRST AUTHOR , YEAR. +# +msgid "" +msgstr "" +"Project-Id-Version: PACKAGE VERSION\n" +"POT-Creation-Date: 2020-12-15 22:31+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"Language: fi\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. type: Title === +#: ./pages/terminology/use_cases.adoc:1 +#, no-wrap +msgid "Container Use Cases" +msgstr "" + +#. type: Plain text +#: ./pages/terminology/use_cases.adoc:4 +msgid "" +"There are many types of Container design patterns forming. Since containers " +"are the runtime version of a container image, the way a container is built " +"is tightly coupled to how it is run." +msgstr "" + +#. type: Plain text +#: ./pages/terminology/use_cases.adoc:7 +msgid "" +"Some Container Images are designed to be run without privileges while others " +"are more specialized and require root-like privileges. There are many " +"dimensions in which patterns can be evaluated and often users will see " +"multiple patterns or use cases tackled together in one container " +"image/container." +msgstr "" + +#. type: Plain text +#: ./pages/terminology/use_cases.adoc:9 +msgid "" +"This section will delve into some of the common use cases that users are " +"tackling with containers." +msgstr "" + +#. type: Title ==== +#: ./pages/terminology/use_cases.adoc:11 +#, no-wrap +msgid "Application Containers" +msgstr "" + +#. type: Plain text +#: ./pages/terminology/use_cases.adoc:15 +msgid "" +"Applications containers are the most popular form of containers. These are " +"what developers and application owners care about. Application containers " +"contain the code that developers work on. These include, for example, MySQL, " +"Apache, MongoDB, and Node.js." +msgstr "" + +#. type: Title ==== +#: ./pages/terminology/use_cases.adoc:17 +#, no-wrap +msgid "Cattle vs Pet Containers" +msgstr "" + +#. type: Plain text +#: ./pages/terminology/use_cases.adoc:21 +msgid "" +"Containers are usually perceived as a technology that serves for deploying " +"applications that are immutable and can be therefore redeployed or killed " +"any time without severe consequences. As an analogy, these are often " +"referred to as \"cattle\". Containers in this development environment don't " +"have \"identity\", the user doesn't need to care where the contianers live " +"in the cluster, the containers are automatically recovered after failures " +"and can be scaled up or down as needed. In contrast, when a pet container " +"fails, the running application will be directly affected and might fail as " +"well. Similarly as pets, pet containers require user's closer attention and " +"management and are usually accompanied with regular health checks. A typical " +"example would be a containerized database." +msgstr "" + +#. type: Title ==== +#: ./pages/terminology/use_cases.adoc:23 +#, no-wrap +msgid "Super Privileged Containers" +msgstr "" + +#. type: Plain text +#: ./pages/terminology/use_cases.adoc:32 +msgid "" +"When building container infrastructure on dedicated container hosts such as " +"Atomic Host, system administrators still need to perform administrative " +"tasks. Whether used with distributed systems, such as Kubernetes or " +"OpenShift or standalone container hosts, Super Privileged Containers (SPCs) " +"are a powerful tool. SPCs can even do things like load specialized kernel " +"modules, such as with systemtap. In an infrastructure that is built to run " +"containers, administrators will most likely need SPCs to do things like " +"management, monitoring, backups, etc. It's important to realize that there " +"is typically a tighter coupling between SPCs and the host kernel, so " +"administrators need to choose a rock solid container host and standardize on " +"it, especially in a large clustered/distributed environment where things are " +"more difficult to troubleshoot. They then need to select a user space in " +"the SPC that is compatible with the host kernel." +msgstr "" + +#. type: Title === +#: ./pages/terminology/use_cases.adoc:34 +#, no-wrap +msgid "Image Types" +msgstr "" + +#. type: Title ==== +#: ./pages/terminology/use_cases.adoc:37 +#, no-wrap +msgid "Base Images" +msgstr "" + +#. type: Plain text +#: ./pages/terminology/use_cases.adoc:42 +msgid "" +"A base image is one of the simplest types of images, but you will find a lot " +"of definitions. Sometimes users will also refer an application image as the " +"“base image.” However, technically, this is not a base image, these are " +"link:#intermediate_images[Intermediate images]." +msgstr "" + +#. type: Plain text +#: ./pages/terminology/use_cases.adoc:51 +msgid "" +"Simply put, a base image is an image that has no parent layer. Typically, a " +"base image contains a fresh copy of an operating system. Base images " +"normally include core system tools, such as bash or coreutils and tools " +"necessary to install packages and make updates to the image over time (yum, " +"rpm, apt-get, dnf, microdnf...) While base images can be “hand crafted”, in " +"practice they are typically produced and published by open source projects " +"(like Debian, Fedora or CentOS) and vendors (like Red Hat). The provenance " +"of base images is critical for security. In short, the sole purpose of a " +"base image is to provide a starting place for creating your derivative " +"images. When using a Dockerfile, the choice of which base image you are " +"using is explicit: ``` FROM registry.fedoraproject.org/fedora ```" +msgstr "" + +#. type: Title ==== +#: ./pages/terminology/use_cases.adoc:53 +#, no-wrap +msgid "Builder Images" +msgstr "" + +#. type: Plain text +#: ./pages/terminology/use_cases.adoc:57 +msgid "" +"These are a specialized form of container images which produce application " +"container images as offspring. They include everything but a developer's " +"source code. Builder images include operating system libraries, language " +"runtimes, middleware, and the source-to-image tooling." +msgstr "" + +#. type: Plain text +#: ./pages/terminology/use_cases.adoc:60 +msgid "" +"When a builder image is run, it injects the developers source code and " +"produces a ready-to-run offspring application container image. This newly " +"created application container image can then be run in development or " +"production." +msgstr "" + +#. type: Plain text +#: ./pages/terminology/use_cases.adoc:65 +msgid "" +"For example, if a developer has PHP code and they want to run it in a " +"container, they can use a PHP builder image to produce a ready to run " +"application container image. The developer passes the GitHub URL where the " +"code is stored and the builder image does the rest of the work for them. " +"The output of a Builder container is an Application container image which " +"includes Red Hat Enterprise Linux, PHP from Software Collections, and the " +"developer’s code, all together, ready to run. Builder images provide a " +"powerful way to go from code to container quickly and easily, building off " +"of trusted components." +msgstr "" + +#. type: Plain text +#: ./pages/terminology/use_cases.adoc:68 +msgid "" +"Some Builder images are created in a way that allows developers to not only " +"provide their source code, but also custom configuration for software built " +"into the image. One such example is the " +"https://github.com/openshift/source-to-image/tree/master/examples/nginx-centos7#configuring-nginx[Nginx " +"Builder image] in the source-to-image upstream repository." +msgstr "" + +#. type: Title ==== +#: ./pages/terminology/use_cases.adoc:70 +#, no-wrap +msgid "Intermediate Images" +msgstr "" + +#. type: Plain text +#: ./pages/terminology/use_cases.adoc:74 +msgid "" +"An Intermediate image is any container image which relies on a base " +"image. Typically, core builds, middleware and language runtimes are built as " +"layers on “top of” a base image. These images are then referenced in the " +"FROM directive of another image. These images are not used on their own, " +"they are typically used as a building block to build a standalone image." +msgstr "" + +#. type: Plain text +#: ./pages/terminology/use_cases.adoc:78 +msgid "" +"It is common to have different teams of specialists own different layers of " +"an image. Systems administrators may own the core build layer, while " +"“developer experience” may own the middleware layer. Intermediate Images " +"are built to be consumed by other teams building images, but can sometimes " +"be ran standalone too, especially for testing." +msgstr "" + +#. type: Title ==== +#: ./pages/terminology/use_cases.adoc:80 +#, no-wrap +msgid "Intermodal Images" +msgstr "" + +#. type: Plain text +#: ./pages/terminology/use_cases.adoc:83 +msgid "" +"Intermodal container images are images that have hybrid architectures. For " +"example, many Red Hat Software Collections images can be used in two ways." +msgstr "" + +#. type: Plain text +#: ./pages/terminology/use_cases.adoc:85 +msgid "" +"First, they can be used as simple Application Containers running a fully " +"contained Ruby on Rails and Apache server." +msgstr "" + +#. type: Plain text +#: ./pages/terminology/use_cases.adoc:88 +msgid "" +"Second, they can be used as Builder Images inside of OpenShift Container " +"Platform. In this case, the output child images which contain Ruby on " +"Rails, Apache, and the application code which the source-to-image process " +"was pointed towards during the build phase." +msgstr "" + +#. type: Plain text +#: ./pages/terminology/use_cases.adoc:90 +msgid "" +"The intermodal pattern is becoming more and more common to solve two " +"business problems with one container image." +msgstr "" + +#. type: Title ==== +#: ./pages/terminology/use_cases.adoc:92 +#, no-wrap +msgid "Deployer Images" +msgstr "" + +#. type: Plain text +#: ./pages/terminology/use_cases.adoc:96 +msgid "" +"A deployer image is a specialized kind of container which, when run, deploys " +"or manages other containers. This pattern enables sophisticated deployment " +"techniques such as mandating the start order of containers, or first run " +"logic such as populating schema or data." +msgstr "" + +#. TBD: Container patterns could nicely add to this +#. type: Title ==== +#: ./pages/terminology/use_cases.adoc:100 +#, no-wrap +msgid "Containerized Components" +msgstr "" + +#. type: Plain text +#: ./pages/terminology/use_cases.adoc:103 +msgid "" +"A container that is meant to be deployed as part of a larger software " +"system, not on its own. Two major trends are driving this." +msgstr "" + +#. type: Plain text +#: ./pages/terminology/use_cases.adoc:106 +msgid "" +"First, microservices are driving the use of best-of-breed components - this " +"is also driving the use of more components combined together to build a " +"single application. Containerized components are meeting the need to deploy " +"an expanding quantity of complex software more quickly and easily." +msgstr "" + +#. type: Plain text +#: ./pages/terminology/use_cases.adoc:109 +msgid "" +"Second, not all pieces of software are easy to deploy as " +"containers. Sometimes, it makes sense to containerize only certain " +"components which are easier to move to containers or provide more value to " +"the overall project. With multi-service application, some services may be " +"deployed as containers, while others may be deployed through traditional a " +"traditional methodology such as an RPM or installer script." +msgstr "" + +#. type: Plain text +#: ./pages/terminology/use_cases.adoc:111 +msgid "" +"It’s important to understand that containerized components are not designed " +"to function on their own. They provide value to a larger piece of software, " +"but provide very little value on their own." +msgstr ""