Ubuntu Server Guide 18.04........................................................................... 312 5. As a Domain Controller .............................................................................................. to install the system as a vanilla Ubuntu server, a MAAS5 bare-metal cloud rack controller or a MAAS6 region controller. If you select one of the MAAS options you will be asked for some details. • The system knows about both drives and actively maintains both of them) or hardware (where a special controller makes the OS think there's only one drive and maintains the drives 'invisibly'). The RAID software0 码力 | 413 页 | 1.40 MB | 1 年前3
openEuler OS Technical Whitepaper
Innovation Projects
(June, 2023)system/directory Maximized node performance Application cluster Storage cluster (multi-node/multi-controller) /A /A /B /C /D /E /F Multipath NFS/RDMA or NFS/TCP Maximized cluster performance in client-server for each single NFS mount point to support I/O transmission over those links, achieving cross- controller and cross-site reliability. All configurations are recorded in one file, making it easy to deploy and reliability. GearOS can be used in automotive control, robotic control, programmable logic controller (PLC), and machine tool control. Challenges Modern industries must be equipped with intelligent0 码力 | 116 页 | 3.16 MB | 1 年前3
ubuntu server guidecontrols 3 samba-apparmor-profile Create AppArmor profile 3 Legacy pages 4 samba-domain-controller NT4 domain controller 4 samba-openldap-backend OpenLDAP backend 2 Mail services 3 mail-postfix Install Postfix server Set up a print server Set up share access control Set up an AppArmor profile NT4 domain controller (legacy) OpenLDAP backend (legacy) Mail services These guides will help you get started with credentials to join a machine to that domain. • The domain controller is acting as an authoritative DNS server for the domain. • The domain controller is the primary DNS resolver (check with systemd-resolve0 码力 | 486 页 | 3.33 MB | 1 年前3
Cilium v1.6 Documentationon all worker nodes Recommended: Enable PodCIDR allocation (--allocate-node-cidrs) in the kube-controller-manager (recommended) Refer to the section Requirements for detailed instruction on how to prepare on all worker nodes Recommended: Enable PodCIDR allocation (--allocate-node-cidrs) in the kube-controller-manager (recommended) Refer to the section Requirements for detailed instruction on how to prepare filesystem mounted on all worker nodes Enable PodCIDR allocation (--allocate-node-cidrs) in the kube- controller-manager (recommended) Refer to the section Requirements for detailed instruction on how to prepare0 码力 | 734 页 | 11.45 MB | 1 年前3
Cilium v1.8 Documentationon all worker nodes Recommended: Enable PodCIDR allocation (--allocate-node-cidrs) in the kube-controller-manager (recommended) Refer to the section Requirements for detailed instruction on how to prepare on all worker nodes Recommended: Enable PodCIDR allocation (--allocate-node-cidrs) in the kube-controller-manager (recommended) Refer to the section Requirements for detailed instruction on how to prepare show a Mellanox ConnectX-3 or ConnectX-4 Lx NIC: $ lspci | grep Ethernet 2846:00:02.0 Ethernet controller: Mellanox Technologies MT27710 Family [ConnectX-4 Lx Virtual Function] (rev 80) In order to run0 码力 | 1124 页 | 21.33 MB | 1 年前3
Cilium v1.10 Documentationon all worker nodes Recommended: Enable PodCIDR allocation (--allocate-node-cidrs) in the kube-controller-manager (recommended) Refer to the section Requirements for detailed instruction on how to prepare terway-eni terway-eniip Note If you are using ACK with Flannel (DaemonSet kube-flannel-ds), the Cloud Controller Manager (CCM) will create route (Pod CIDR) in VPC. If your cluster is an Managed Kubernetes you show a Mellanox ConnectX-3 or ConnectX-4 Lx NIC: $ lspci | grep Ethernet 2846:00:02.0 Ethernet controller: Mellanox Technologies MT27710 Family [ConnectX-4 Lx Virtual Function] (rev 80) In order to run0 码力 | 1307 页 | 19.26 MB | 1 年前3
Cilium v1.9 Documentationon all worker nodes Recommended: Enable PodCIDR allocation (--allocate-node-cidrs) in the kube-controller-manager (recommended) Refer to the section Requirements for detailed instruction on how to prepare on all worker nodes Recommended: Enable PodCIDR allocation (--allocate-node-cidrs) in the kube-controller-manager (recommended) Refer to the section Requirements for detailed instruction on how to prepare show a Mellanox ConnectX-3 or ConnectX-4 Lx NIC: $ lspci | grep Ethernet 2846:00:02.0 Ethernet controller: Mellanox Technologies MT27710 Family [ConnectX-4 Lx Virtual Function] (rev 80) In order to run0 码力 | 1263 页 | 18.62 MB | 1 年前3
Cilium v1.11 Documentationon all worker nodes Recommended: Enable PodCIDR allocation (--allocate-node-cidrs) in the kube-controller-manager (recommended) Refer to the section Requirements for detailed instruction on how to prepare terway-eni terway-eniip Note If you are using ACK with Flannel (DaemonSet kube-flannel-ds), the Cloud Controller Manager (CCM) will create route (Pod CIDR) in VPC. If your cluster is an Managed Kubernetes you show a Mellanox ConnectX-3 or ConnectX-4 Lx NIC: $ lspci | grep Ethernet 2846:00:02.0 Ethernet controller: Mellanox Technologies MT27710 Family [ConnectX-4 Lx Virtual Function] (rev 80) In order to run0 码力 | 1373 页 | 19.37 MB | 1 年前3
Cilium v1.7 Documentationon all worker nodes Recommended: Enable PodCIDR allocation (--allocate-node-cidrs) in the kube-controller-manager (recommended) Refer to the section Requirements for detailed instruction on how to prepare on all worker nodes Recommended: Enable PodCIDR allocation (--allocate-node-cidrs) in the kube-controller-manager (recommended) Refer to the section Requirements for detailed instruction on how to prepare ion labels any:!pod-template-hash Ignore all pod-template-hash labels any:!controller-revision-hash Ignore all controller-revision-hash labels any:!annotation.* Ignore all annotation labels any:!etcd_node0 码力 | 885 页 | 12.41 MB | 1 年前3
Cilium v1.5 Documentationfilesystem mounted on all worker nodes Enable PodCIDR alloca�on ( --allocate-node-cidrs ) in the kube-controller-manager (recommended) Refer to the sec�on Requirements for detailed instruc�on on how to prepare filesystem mounted on all worker nodes Enable PodCIDR alloca�on ( --allocate-node-cidrs ) in the kube-controller-manager (recommended) Refer to the sec�on Requirements for detailed instruc�on on how to prepare NodeMonitor: Listening for events on 1 CPUs with 64x4096 of sha Cilium health daemon: Ok Controller Status: 6/6 healthy Proxy Status: OK, ip 10.15.28.238, port-range 10000-20000 Cluster0 码力 | 740 页 | 12.52 MB | 1 年前3
共 33 条
- 1
- 2
- 3
- 4













