[TOC]Introduction to Kubernetes DispatchingIn addition to having the Kubernetes cluster scheduler automatically select a node for the pod resource (the default schedule is that the resources are sufficient and the load is as average as possible), there are situations where we want to have more control over how the pod should be dispatched. For example, some of the machines in the cluster are better configur
inside the system. So sometimes the swift project starts with the system framework without caching, and it looks a bit longer. 6 Framework
Now let's compare the situation with the code. Two projects were added to 5 dependencies.This is 6 dependencies of the OC Project:
Pod ' afnetworking ', ' ~> 3.0 '
pod ' masonry ' pod '
mjrefresh '
1. Basic architecture1.1 MasterThe master node consists mainly of four modules: Apiserver, Scheduler, controller manager, ETCD. apiserver. Apiserver is responsible for providing restful Kubernetes API service, it is the unified entrance of the System Management Directive, any operation that increases and deletions the resources should be handed over to apiserver processing and then submitted to ETCD. As shown in the architecture diagram, KUBECTL (the client tool provided by Kubernetes, which
first, the core concept
1, Node
node as a working node in a cluster, running a real application, the smallest unit of Kubernetes managed on node is pod. Node runs kubernetes kubelet, Kube-proxy service processes that are responsible for pod creation, start-up, monitoring, restart, destruction, and load balancing of software patterns.
Node contains information: node address: The IP address of the host, or
Cocoapods Application Part 2-private database-related, cocoapods Part 2This is related to the second part of the first part see http://blog.csdn.net/yohunl/article/details/47982949 or http://www.cocoachina.com/ios/20150906/13323.htmlHere, we use the first part to describe the framework project created using pod lib create YohunlUtilsPod. the creation process will not be repeated here, of course, you can also download the demo https://github.com/yohunl
k8s Basic Concepts1. NodeNode as a working node in the cluster, running a real application, the smallest running unit kubernetes managed on node is the pod. Node runs Kubernetes's kubelet, Kube-proxy service processes, which are responsible for pod creation, startup, monitoring, restart, destruction, and load balancing for software patterns. The information that node contains:
node address: The IP
functions are as follows:
1 Use Docker for application wrapping (package), instantiating (instantiate), running (run).
2 to run and manage the containers across the machine in a cluster manner.
3 to solve the communication problem between Docker and cross machine containers.
4 Kubernetes's self-healing mechanism makes the container cluster always run in the user's desired state.
The current kubernetes support GCE, Vshpere, CoreOS, OpenShift, Azure and other platforms, in addition, can also run
Summary
Project Background (XX Bank customer): The private cloud on the k8s to run like MySQL in the state of the database services, performance and latency are relatively sensitive, not like the web bias application of stateless delay performance almost acceptable. But the network performance and delay is poor based on overlay mode, and the network architecture is more complex. And banks need to be simple and controllable for IP network management. Sr-iov is based on hardware implementation of
KubernetesKubernetes is the Google Open Source container cluster Management system, which provides application deployment, maintenance, extension mechanisms and other functions, using kubernetes can easily manage the cross-machine operation of containerized applications, the main functions are as follows:1) Use Docker for application wrapping (package), instantiation (instantiate), and run.2) Run and manage containers across machines in a clustered manner.3) solve the problem of communication b
KubernetesKubernetes is Google open-source container cluster management system, using Golang development, which provides application deployment, maintenance, extension mechanism and other functions, using kubernetes can easily manage the cross-machine operation of containerized applications, the main functions are as follows:
Use Docker for application wrapping (package), instantiation (instantiate), and run.
Run and manage containers across machines in a clustered way.
Resolve
training is a combination of our theory and practice, from the perspective of Docker should scenario, continuous deployment and delivery, how to improve testing efficiency, storage, network, monitoring, security and so on.
First, kubernetes network modelThere are two kinds of IP (pod IP and Service Cluster IP) in the Kubernetes network, the pod IP address is actually on a network card (can be a virtual d
OverviewRC, Deployment, Daemonset are non-state-oriented services, they manage the pod IP, name, start and stop order is random, and what is Statefulset? As the name implies, a stateful collection that manages all stateful services, such as MySQL, MongoDB clusters, and so on.Statefulset is essentially a variant of the deployment, in order to solve the problem of stateful services, it manages the pod has a f
service designed by the CoreOS team for kubernetes, which simply means that the Docker container created by the different node hosts in the cluster has a unique virtual IP address for the complete cluster. It also creates an overlay network between these IP addresses, which, through this overlay network, passes the packets intact to the target container (Overlay).Here is a schematic diagram of its network:As you can see, flannel first creates a bridge named Flannel0, and one end of the bridge c
OverviewRC, Deployment, Daemonsetstatefulset are non-state-oriented services, they manage the pod IP, name, start and stop order is random, and what is Statefulset? As the name implies, a stateful collection that manages all stateful services, such as MySQL, MongoDB clusters, and so on.Statefulset is essentially a variant of the deployment, it is T is to solve the problem of stateful service, it manages the pod
│├──plugins.go│└──plugins_test.go├──generic_scheduler.go #实现Schedule (),
The main logic of scheduling is realized, such as ├──generic_scheduler_test.go├──metrics│├──build│└──metrics.go ├──scheduler.go #定义Scheduler和Configurator接口, the Logic of Scheduleone () has been realized ├──scheduler_test.go├──schedule
Rcache│├──build│├──cache.go #实现了Cache接口中的函数并定义了schedulerCache接口等 │├──cache_test.go │├──interfacE.go #定义了Cache接口 │├──node_info.go│└──util.go├──testing│├──build│ ├──fake_cache.go
. Main concepts of Kubernetes 2.1 Pods
In the Kubernetes system, the smallest granularity of scheduling is not simply a container, but a Pod. A Pod is the smallest deployment unit that can be created, destroyed, scheduled, and managed. One or more containers (Container) constitute a Pod. Generally, the containers in the Pod
Summary:Developers may be familiar with some of the more well-known open source cocoapods frameworks, but sometimes they may not be able to find a pod that just satisfies their needs, and this article explains in detail how to use Swift to create a cocoapods process.This article is from: Raywenderlich, translation: Development technology Front, translator: Mrloong You might be familiar with some well-known, open-source cocoapods frameworks, such as Al
cluster for Spark application, the submission mechanism is:
L Spark Create Spark Driver, run in a kubernetes pod.
L driver creates executors, runs in kubernetes pods, and executes application code.
L When the application completes, the Executor pods is terminated and cleaned, but driver pod is persisted to the log, and the "Finish" state remains in Kubernetesapi until the final garbage collection or manual
The Resource configuration Checklist orchestrates docker in the form of Yaml, using the Rtetful interface style, where the main resource objects such asAutonomous pod resource (not controlled by controller)资源的清单格式: 一级字段:apiVersion(group/version), kind, metadata(name,namespace,labels,annotations, ...), spec, status(只读)Pod资源: spec.containers Tags: (important features)Key=valueKey: Letters, numbers,、-、.V
Wen/Sky Cloud software Cloud Platform development engineer Zhang Wei
Zhang Wei is mainly responsible for the cloud software Skyform Cloud Platform design and development work. Familiar with a variety of open source IaaS platform, such as Cloudstack,openstack, familiar with various resource management and scheduling framework, such as kubernetes,mesos,yarn,borg.
After six months of continuous optimization, Kubernetes announced that the 1.2 version has been able to support the 1000+ node cluster
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.