Академический Документы
Профессиональный Документы
Культура Документы
2 CSD
3
11 Background
2 1.1 Overview
3
4ETCD issues like Key not found, have been identified occasionally during CSD/SM
5instantiation and Upgrade, this is because of the slow disk response, the disk on which ETCD
6DB is mounted.
7
8ETCD (a key value pair db) is integrated in the CSD VNF Application Blueprint to supply
9service discovery and configuration functionality for all the platform components like, HA,
10SNMP, DNS, NTP, IPCONFIG, HTTP, ZABBIX, MARIADB, METRICS, etc.
11
12Some of the custom functionalities from CSD application are also have bare minimum (optional)
13ETCD uses, such as, route add, multiple diameter address groups, dde_config.
14
15ETCD is currently running on 3 Nodes within CSD/SM VNF, and forms as a cluster with below
16VNFC’s
17OAM-1 (index 0)
18OAM-2 (index 1)
19DB-1 (index 0)
20
21All the ETCD hosted nodes are connected over Internal network (192.x.x.x) with TCP on 2379
22port.
23
24Hardware recommendations:
25ETCD usually runs well with limited resources for development or testing purposes; it’s common
26to develop with etcd on a laptop or a cheap cloud machine. However, when running etcd clusters
27in production, some hardware guidelines are useful for proper administration. These suggestions
28are not hard rules; they serve as a good starting point for a robust production deployment. As
29always, deployments should be tested with simulated workloads before running in production.
30For more information please refer to below article.
31https://github.com/etcd-io/etcd/blob/master/Documentation/op-guide/hardware.md#hardware-
32recommendations
33
34Tuning:
35The default settings in etcd should work well for installations on a local network where the
36average network latency is low. However, when using etcd across multiple data centers or over
37networks with high latency, the heartbeat interval and election timeout settings may need tuning.
38The network isn't the only source of latency. Each request and response may be impacted by
39slow disks on both the leader and follower. Each of these timeouts represents the total time from
40request to successful response from the other machine. For more information please refer to
41below article.
42https://github.com/etcd-io/etcd/blob/master/Documentation/tuning.md
43
4
Version: 1.0 Version Date: 06/03/2019
Nokia Proprietary - Use Pursuant to Company Instructions
Page 1 of 3
5
6 Nokia
7 CSD
8
14
Version: 1.0 Version Date: 06/03/2019
Nokia Proprietary - Use Pursuant to Company Instructions
Page 3 of 3
15