diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index 7e2e4f8e..1894db0b 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -1,7 +1,6 @@ #image: "git.mesalab.cn:7443/mesa_platform/build-env:master" variables: GIT_STRATEGY: "clone" - BUILD_BASED_IMAGE_CENTOS7: "git.mesalab.cn:7443/mesa_platform/build-env:master" BUILD_BASED_IMAGE_ROCKYLINUX8: "git.mesalab.cn:7443/mesa_platform/build-env:rockylinux-dindind" GIT_DEPTH: 1 @@ -11,18 +10,6 @@ stages: - deploy - notify -.build_tsg-buildimage: - script: - - env | sort - - sed -i 's+https://download.docker.com+https://mirrors.tuna.tsinghua.edu.cn/docker-ce+' /etc/yum.repos.d/docker-ce.repo - - yum -y install pbzip2 ansible - - make DALIY_BUILD_VERSION=$DALIY_BUILD_VERSION - - chmod +x ./tools/upload.sh - - ./tools/upload.sh - tags: - - tsg-os-installer - resource_group: global - .build_onie_bin_x86_64_COTS: script: - env | sort @@ -94,32 +81,6 @@ stages: - tsg-os-builder-el8 resource_group: global -# feature_branch_build_7400_mcn0: -# image: $BUILD_BASED_IMAGE_CENTOS7 -# stage: build -# extends: .build_tsg-buildimage -# variables: -# PROFILE_LIST: 7400MCN0P01R01 -# DALIY_BUILD_VERSION: 1 -# except: -# - tags -# - /^dev-.*$/i -# - /^rel-.*$/i -# - /^update-.*$/i - -# feature_branch_build_7400_mcn123: -# image: $BUILD_BASED_IMAGE_CENTOS7 -# stage: build -# extends: .build_tsg-buildimage -# variables: -# PROFILE_LIST: 7400MCN123P01R01 -# DALIY_BUILD_VERSION: 1 -# except: -# - tags -# - /^dev-.*$/i -# - /^rel-.*$/i -# - /^update-.*$/i - feature_branch_build_container_images_x86_64_COTS: image: $BUILD_BASED_IMAGE_ROCKYLINUX8 stage: build @@ -182,34 +143,6 @@ feature_branch_notify_jobs_done_x86_64_COTS: - /^rel-.*$/i - /^update-.*$/i -# develop_build_7400_mcn0: -# image: $BUILD_BASED_IMAGE_CENTOS7 -# stage: build -# extends: .build_tsg-buildimage -# variables: -# PROFILE_LIST: 7400MCN0P01R01 -# UPLOAD_TO_FILE_REPO: 1 -# PULP3_FILE_REPO_NAME: tsg-os-images-develop -# PULP3_FILE_DIST_NAME: tsg-os-images-develop -# DALIY_BUILD_VERSION: 1 -# FILE_REPO_PATH: install/develop/tsg-os-images -# only: -# - /^dev-.*$/i - -# develop_build_7400_mcn123: -# image: $BUILD_BASED_IMAGE_CENTOS7 -# stage: build -# extends: .build_tsg-buildimage -# variables: -# PROFILE_LIST: 7400MCN123P01R01 -# UPLOAD_TO_FILE_REPO: 1 -# PULP3_FILE_REPO_NAME: tsg-os-images-develop -# PULP3_FILE_DIST_NAME: tsg-os-images-develop -# DALIY_BUILD_VERSION: 1 -# FILE_REPO_PATH: install/develop/tsg-os-images -# only: -# - /^dev-.*$/i - develop_build_container_images_x86_64_COTS: image: $BUILD_BASED_IMAGE_ROCKYLINUX8 stage: build @@ -273,34 +206,6 @@ develop_notify_jobs_done_x86_64_COTS: only: - /^dev-.*$/i -# testing_build_7400_mcn0: -# image: $BUILD_BASED_IMAGE_CENTOS7 -# stage: build -# extends: .build_tsg-buildimage -# variables: -# PROFILE_LIST: 7400MCN0P01R01 -# UPLOAD_TO_FILE_REPO: 1 -# PULP3_FILE_REPO_NAME: tsg-os-images-testing -# PULP3_FILE_DIST_NAME: tsg-os-images-testing -# FILE_REPO_PATH: install/testing/tsg-os-images -# DALIY_BUILD_VERSION: 1 -# only: -# - /^rel-.*$/i - -# testing_build_7400_mcn123: -# image: $BUILD_BASED_IMAGE_CENTOS7 -# stage: build -# extends: .build_tsg-buildimage -# variables: -# PROFILE_LIST: 7400MCN123P01R01 -# UPLOAD_TO_FILE_REPO: 1 -# PULP3_FILE_REPO_NAME: tsg-os-images-testing -# PULP3_FILE_DIST_NAME: tsg-os-images-testing -# FILE_REPO_PATH: install/testing/tsg-os-images -# DALIY_BUILD_VERSION: 1 -# only: -# - /^rel-.*$/i - testing_build_container_images_x86_64_COTS: image: $BUILD_BASED_IMAGE_ROCKYLINUX8 stage: build @@ -366,34 +271,6 @@ testing_notify_jobs_done_x86_64_COTS: only: - /^rel-.*$/i -# rc_build_7400_mcn0: -# image: $BUILD_BASED_IMAGE_CENTOS7 -# stage: build -# extends: .build_tsg-buildimage -# variables: -# PROFILE_LIST: 7400MCN0P01R01 -# UPLOAD_TO_FILE_REPO: 1 -# DALIY_BUILD_VERSION: 0 -# PULP3_FILE_REPO_NAME: tsg-os-images-rc -# PULP3_FILE_DIST_NAME: tsg-os-images-rc -# FILE_REPO_PATH: install/rc/tsg-os-images -# only: -# - /^.*-rc.*$/i - -# rc_build_7400_mcn123: -# image: $BUILD_BASED_IMAGE_CENTOS7 -# stage: build -# extends: .build_tsg-buildimage -# variables: -# PROFILE_LIST: 7400MCN123P01R01 -# UPLOAD_TO_FILE_REPO: 1 -# DALIY_BUILD_VERSION: 0 -# PULP3_FILE_REPO_NAME: tsg-os-images-rc -# PULP3_FILE_DIST_NAME: tsg-os-images-rc -# FILE_REPO_PATH: install/rc/tsg-os-images -# only: -# - /^.*-rc.*$/i - rc_build_container_images_x86_64_COTS: image: $BUILD_BASED_IMAGE_ROCKYLINUX8 stage: build @@ -459,39 +336,6 @@ rc_notify_jobs_done_x86_64_COTS: only: - /^.*-rc.*$/i - -# release_build_7400_mcn0: -# image: $BUILD_BASED_IMAGE_CENTOS7 -# stage: build -# extends: .build_tsg-buildimage -# variables: -# PROFILE_LIST: 7400MCN0P01R01 -# UPLOAD_TO_FILE_REPO: 1 -# DALIY_BUILD_VERSION: 0 -# PULP3_FILE_REPO_NAME: tsg-os-images-release -# PULP3_FILE_DIST_NAME: tsg-os-images-release -# FILE_REPO_PATH: install/release/tsg-os-images -# only: -# - tags -# except: -# - /^.*-rc.*$/i - -# release_build_7400_mcn123: -# image: $BUILD_BASED_IMAGE_CENTOS7 -# stage: build -# extends: .build_tsg-buildimage -# variables: -# PROFILE_LIST: 7400MCN123P01R01 -# UPLOAD_TO_FILE_REPO: 1 -# DALIY_BUILD_VERSION: 0 -# PULP3_FILE_REPO_NAME: tsg-os-images-release -# PULP3_FILE_DIST_NAME: tsg-os-images-release -# FILE_REPO_PATH: install/release/tsg-os-images -# only: -# - tags -# except: -# - /^.*-rc.*$/i - release_build_container_images_x86_64_COTS: image: $BUILD_BASED_IMAGE_ROCKYLINUX8 stage: build diff --git a/Makefile b/Makefile index 8b457983..cd1be79b 100644 --- a/Makefile +++ b/Makefile @@ -114,8 +114,6 @@ all: $(PROFILE_LIST) $(Q) chmod 0755 $(TOOLSDIR)/* $(Q) sed -i -e 's/PULP_REPO_USERNAME/$(PULP_REPO_USERNAME)/g' $(CONFDIR)/yum-RockyLinux-8.conf $(Q) sed -i -e 's/PULP_REPO_PASSWORD/$(PULP_REPO_PASSWORD)/g' $(CONFDIR)/yum-RockyLinux-8.conf - $(Q) sed -i -e 's/PULP_REPO_USERNAME/$(PULP_REPO_USERNAME)/g' $(CONFDIR)/yum-CentOS-7.conf - $(Q) sed -i -e 's/PULP_REPO_PASSWORD/$(PULP_REPO_PASSWORD)/g' $(CONFDIR)/yum-CentOS-7.conf $(Q) echo "=== Building $< $(OS_RELEASE_VER) ===" $(Q) echo "=== Building chart version $< $(HELM_CHART_VER) ===" $(Q) $(MAKE) -f make/Makefile.$< all diff --git a/ansible/HAL_deploy.yml b/ansible/HAL_deploy.yml index 78bf762b..61d3bfbc 100644 --- a/ansible/HAL_deploy.yml +++ b/ansible/HAL_deploy.yml @@ -1,51 +1,3 @@ -- hosts: 7400-MCN0-P01R01 - remote_user: root - vars_files: - - install_config/group_vars/HAL_7400MCN0P01R01.yml - - install_config/group_vars/rpm_version.yml - roles: - - {role: tsg-os-provision, tags: tsg-os-provision} - - {role: coredump, tags: coredump} - - {role: system-init-7400-mcn0, tags: system-init-7400-mcn0} - - {role: tsg_device_tag, tags: tsg_device_tag} - - {role: tsg_sn, tags: tsg_sn} - - {role: docker, tags: docker} - - {role: framework, tags: framework} - - {role: mrzcpd, tags: mrzcpd} - - {role: sapp, tags: sapp} - - {role: kni, tags: kni} - - {role: firewall, tags: firewall} - - {role: http_healthcheck,tags: http_healthcheck} - - {role: redis, tags: redis} - - {role: maat-redis, tags: maat-redis} - - {role: certstore, tags: certstore} - - {role: telegraf, tags: telegraf} - - {role: sysctl, tags: sysctl} - - {role: exporter, tags: exporter} - - {role: tsg-diagnose, tags: tsg-diagnose} - - {role: system-init, tags: system-init} - - {role: consul, tags: consul} - - {role: hasp, tags: hasp} - -- hosts: 7400-MCN123-P01R01 - remote_user: root - vars_files: - - install_config/group_vars/HAL_7400MCN123P01R01.yml - - install_config/group_vars/rpm_version.yml - roles: - - {role: tsg-os-provision, tags: tsg-os-provision} - - {role: coredump, tags: coredump} - - {role: system-init-7400-mcn123, tags: system-init-7400-mcn123} - - {role: tsg_device_tag, tags: tsg_device_tag} - - {role: framework, tags: framework} - - {role: mrzcpd, tags: mrzcpd} - - {role: exporter, tags: exporter} - - {role: tsg_sn, tags: tsg_sn} - - {role: tfe, tags: tfe} - - {role: sysctl, tags: sysctl} - - {role: system-init, tags: system-init} - - {role: hasp, tags: hasp} - - hosts: x86_64_COTS remote_user: root vars_files: @@ -53,7 +5,6 @@ - install_config/group_vars/rpm_version.yml roles: - {role: k3s-install, tags: k3s-install} - - {role: coredump, tags: coredump} - {role: coredump-tools, tags: coredump-tools} - {role: clixon, tags: clixon} - {role: tsg-os-HAL, tags: tsg-os-HAL} @@ -77,14 +28,6 @@ - {role: tsg-os-oobc, tags: tsg-os-oobc} - {role: tsg-os-logfile-cleaner, tags: tsg-os-logfile-cleaner} -- hosts: x86_64_COTS-init - remote_user: root - vars_files: - - install_config/group_vars/HAL_x86_64_COTS.yml - - install_config/group_vars/rpm_version.yml - roles: - - {role: tsg_sn, tags: tsg_sn} - - hosts: x86_64_COTS-firewall remote_user: root vars_files: diff --git a/ansible/install_config/group_vars/HAL_7400MCN0P01R01.yml b/ansible/install_config/group_vars/HAL_7400MCN0P01R01.yml deleted file mode 100644 index 7af2315f..00000000 --- a/ansible/install_config/group_vars/HAL_7400MCN0P01R01.yml +++ /dev/null @@ -1,59 +0,0 @@ -# TOD: TSG-6386 调整 TSG-OS 中的脚本， 适配 TSG-7400 硬件平台 -# variable format {role_name}.{configname}.{section}.{var} configname 用 "_" 替代 "." 和 - -control_and_policy: - nic_name: eth_ctl - -workload_zcpd: - cpu_affinity: 52,53,54,55 - hugepage_num_1G: 32 - -workload_firewall: - cpu_affinity: 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43 - worker_threads: 42 - send_only_threads_max: 1 - -dp_steering_proxy: - ###### location: value {local, foreign} - location: foreign - node_count: 3 - node_list: - - id: 0 - nic_name: eth_mcn1 - addr: 192.168.100.2 - - id: 1 - nic_name: eth_mcn2 - addr: 192.168.100.3 - - id: 2 - nic_name: eth_mcn3 - addr: 192.168.100.4 - nic_cmsg_and_watchdog: eth_pf.100 - -dp_traffic_mirror: - nic_name: eth_mirr_d - traffic_mirror_vlan_id: 0 - -dp_steering_firewall: - #deloyment value: mirror,inline, transparent. mirror = one arm + mirror, inline = one arm + series, transparent = two arm + series - deployment: inline - #encapsulation value: vlan, vxlan, raw, provision - encapsulation: provision - # capture_packet value: pcap, driver - capture_packet: driver - nic_internal: eth_raw - enable_mirror: 0 - -diagnose: - virtual_server_nic: eth_dign_s - virtual_client_nic: eth_dign_c - -prefix_path: - mrzcpd: /opt/tsg/mrzcpd - framework: /opt/tsg/framework - sapp: /opt/tsg/sapp - -monitor: - enable_redis_exporter: 1 - enable_ipmi_exporter: 1 -### TSG-7400-mcn0 TSG-7400-mcn123 TSG-9140 -runtime_env: TSG-7400-mcn0 \ No newline at end of file diff --git a/ansible/install_config/group_vars/HAL_7400MCN123P01R01.yml b/ansible/install_config/group_vars/HAL_7400MCN123P01R01.yml deleted file mode 100644 index cd5ee5a2..00000000 --- a/ansible/install_config/group_vars/HAL_7400MCN123P01R01.yml +++ /dev/null @@ -1,43 +0,0 @@ -# TOD: TSG-6386 调整 TSG-OS 中的脚本， 适配 TSG-7400 硬件平台 -# variable format {role_name}.{configname}.{section}.{var} configname 用 "_" 替代 "." 和 - -control_and_policy: - nic_name: eth_ctl - -workload_zcpd: - cpu_affinity: 53,54 - hugepage_num_1G: 32 - -dp_traffic_mirror: - nic_name: eth_mirr_d - traffic_mirror_vlan_id: 0 - -prefix_path: - mrzcpd: /opt/tsg/mrzcpd - framework: /opt/tsg/framework - -dp_steering_proxy: - ###### location: value {local, foreign} - location: foreign - node_list: - - nic_name: eth_vf_kni - -workload_proxy: - enable_cpu_affinity: 0 - cpu_affinity: 1-8 - worker_thread: 32 - -dp_proxy: - nic_name_data_incoming: eth_pxy - mac_addr_data_incoming: aa:bb:cc:dd:ee:ff - enable_traffic_mirror: 1 - traffic_mirror_type: 1 - -dp_certstore: - location: foreign - -monitor: - enable_redis_exporter: 0 - enable_ipmi_exporter: 1 - -runtime_env: TSG-7400-mcn123 \ No newline at end of file diff --git a/ansible/roles/coredump/files/coredump_setup_override.conf.TSGXNXR620G40R01P0906 b/ansible/roles/coredump/files/coredump_setup_override.conf.TSGXNXR620G40R01P0906 deleted file mode 100644 index c7a76a0f..00000000 --- a/ansible/roles/coredump/files/coredump_setup_override.conf.TSGXNXR620G40R01P0906 +++ /dev/null @@ -1,8 +0,0 @@ -[Coredump] -Storage=none -ProcessSizeMax=0G -ExternalSizeMax=0G -JournalSizeMax=0G -Compress=no -MaxUse=80 -KeepFree=80 \ No newline at end of file diff --git a/ansible/roles/coredump/files/coredump_setup_override.conf.j2.j2 b/ansible/roles/coredump/files/coredump_setup_override.conf.j2.j2 deleted file mode 100644 index 0b70aa80..00000000 --- a/ansible/roles/coredump/files/coredump_setup_override.conf.j2.j2 +++ /dev/null @@ -1,15 +0,0 @@ -[Coredump] -{% if coredump.format == 'core' %} -Storage=external -ProcessSizeMax=256G -ExternalSizeMax=256G -JournalSizeMax=256G -{% else %} -Storage=none -ProcessSizeMax=0G -ExternalSizeMax=0G -JournalSizeMax=0G -{% endif %} -Compress=no -MaxUse=80 -KeepFree=80 \ No newline at end of file diff --git a/ansible/roles/coredump/tasks/main.yml b/ansible/roles/coredump/tasks/main.yml deleted file mode 100644 index 6e339247..00000000 --- a/ansible/roles/coredump/tasks/main.yml +++ /dev/null @@ -1,16 +0,0 @@ -- name: "mkdir -p /usr/lib/systemd/coredump.conf.d/" - file: - path: /usr/lib/systemd/coredump.conf.d/ - state: directory - -- name: "copy coredump config file to dest -- tsg-x-p0906" - copy: - src: '{{ role_path }}/files/coredump_setup_override.conf.TSGXNXR620G40R01P0906' - dest: /usr/lib/systemd/coredump.conf.d/coredump_setup_override.conf - when: runtime_env == 'TSG-X-P0906' - -- name: "copy coredump config file to dest -- not tsg-x-p0906" - copy: - src: '{{ role_path }}/files/coredump_setup_override.conf.j2.j2' - dest: /opt/tsg/tsg-os-provision/templates/coredump_setup_override.conf.j2 - when: runtime_env != 'TSG-X-P0906' diff --git a/ansible/roles/docker/files/daemon.json b/ansible/roles/docker/files/daemon.json deleted file mode 100644 index 51247976..00000000 --- a/ansible/roles/docker/files/daemon.json +++ /dev/null @@ -1 +0,0 @@ -{"iptables":false,"bridge": "none"} diff --git a/ansible/roles/docker/files/docker-compose-Linux-x86_64 b/ansible/roles/docker/files/docker-compose-Linux-x86_64 deleted file mode 100644 index d5fb2583..00000000 Binary files a/ansible/roles/docker/files/docker-compose-Linux-x86_64 and /dev/null differ diff --git a/ansible/roles/docker/tasks/main.yml b/ansible/roles/docker/tasks/main.yml deleted file mode 100644 index d314e6ff..00000000 --- a/ansible/roles/docker/tasks/main.yml +++ /dev/null @@ -1,21 +0,0 @@ -- name: "docker: copy daemon.json to target" - copy: - src: '{{ role_path }}/files/daemon.json' - dest: /etc/docker/ - -#- name: "docker: download docker-compose" -# get_url: -# url: https://github.com/docker/compose/releases/download/1.29.2/docker-compose-Linux-x86_64 -# dest: /usr/bin/docker-compose -# mode: '0755' - -- name: "docker: copy docker-compose binary to target" - copy: - src: '{{ role_path }}/files/docker-compose-Linux-x86_64' - dest: /usr/bin/docker-compose - mode: 0755 - -- name: "enable docker" - systemd: - name: docker - enabled: yes \ No newline at end of file diff --git a/ansible/roles/kni/tasks/main.yml b/ansible/roles/kni/tasks/main.yml deleted file mode 100644 index 151e853f..00000000 --- a/ansible/roles/kni/tasks/main.yml +++ /dev/null @@ -1,19 +0,0 @@ ---- -- name: "download rpm packages: kni" - yum: - name: - - "{{ kni_rpm_version.kni }}" - conf_file: "{{ rpm_repo_config_path }}" - state: present - download_only: yes - download_dir: "{{ path_download }}" - -- name: "Install kni that is sapp plugin with prefix option" - shell: rpm -i /tmp/rpm_download/{{ kni_rpm_version.kni }}* --prefix {{ prefix_path.sapp }} - -- name: Template the kni.conf - template: - src: "{{ role_path }}/templates/kni.conf.j2" - dest: /opt/tsg/sapp/etc/kni/kni.conf - tags: template - when: runtime_env != 'TSG-X-P0906' diff --git a/ansible/roles/kni/templates/kni.conf.j2 b/ansible/roles/kni/templates/kni.conf.j2 deleted file mode 100644 index 098f52de..00000000 --- a/ansible/roles/kni/templates/kni.conf.j2 +++ /dev/null @@ -1,188 +0,0 @@ -[global] -log_path = ./log/kni/kni.log -log_level = 30 -{% if dp_steering_proxy.location == 'local' %} -tfe_node_count = 1 -{% endif %} -{% if dp_steering_proxy.location == 'foreign' %} -tfe_node_count = {{ dp_steering_proxy.node_count }} -{% endif %} -manage_eth = {{ control_and_policy.nic_name }} -# deploy_mode: normal/tap -{% if dp_steering_proxy.tap_mode is defined %} -deploy_mode = tap -{% else %} -deploy_mode = normal -{% endif %} -src_mac_addr = 00:0e:c6:d6:72:c1 -dst_mac_addr = fe:65:b7:03:50:bd - -[tap] -{% for tfe_node_info in dp_steering_proxy.node_list %} -tap_name= {{ tfe_node_info.nic_name }} -{% endfor %} - -# tap_allow_mutilthread=1 load bpf -# tap_allow_mutilthread=0 not load bpf -tap_allow_mutilthread=1 -bpf_obj=/opt/tsg/sapp/plug/business/kni/bpf_tun_rss_steering.o -bpf_default_queue=-1 -# tap_bpf_debug_log: cat /sys/kernel/debug/tracing/trace_pipe -bpf_debug_log=0 -# 2: BPF 使用二元组分流; 4: BPF 使用四元组分流 -bpf_hash_mode=2 - -tap_rps_enable=1 -# cat /sys/class/net/tap0/queues/rx-%{d}/rps_cpus -tap_rps_mask="{% raw %}{{ tfe_env_rps_info.rps_mask }}{% endraw %}" - -[io_uring] -enable_iouring=1 -enable_debuglog=0 -ring_size=1024 -buff_size=2048 -flags=0 -sq_thread_idle=0 - -{% for tfe_node_info in dp_steering_proxy.node_list %} -{% if dp_steering_proxy.location == 'local' %} -[tfe0] -{% endif %} -{% if dp_steering_proxy.location == 'foreign' %} -[tfe{{ tfe_node_info.id }}] -{% endif %} -enabled = 1 -dev_eth_symbol = {{ tfe_node_info.nic_name }} -{% if dp_steering_proxy.location == 'local' %} -ip_addr = 127.0.0.1 -{% endif %} -{% if dp_steering_proxy.location == 'foreign' %} -ip_addr = {{ tfe_node_info.addr }} -{% endif %} -{% endfor %} - -[tfe_cmsg_receiver] -{% if dp_steering_proxy.location == 'local' %} -listen_eth = lo -{% endif %} -{% if dp_steering_proxy.location == 'foreign' %} -listen_eth = {{ dp_steering_proxy.nic_cmsg_and_watchdog }} -{% endif %} -listen_port = 2475 - -[watch_dog] -switch = 1 -{% if dp_steering_proxy.location == 'local' %} -listen_eth = lo -{% endif %} -{% if dp_steering_proxy.location == 'foreign' %} -listen_eth = {{ dp_steering_proxy.nic_cmsg_and_watchdog }} -{% endif %} -listen_port = 2476 -keepalive_idle = 2 -keepalive_intvl = 1 -keepalive_cnt = 3 - -[marsio] -appsym = knifw - -[dup_traffic] -switch = 0 -action = 2 -capacity = 10000000 -error_rate = 0.00001 -expiry_time = 60 - -[traceid2pme_htable] -mho_screen_print_ctrl = 0 -mho_thread_safe = 1 -mho_mutex_num = 160 -mho_hash_slot_size = 640000 -mho_hash_max_element_num = 2560000 -mho_expire_time = 30 -mho_eliminate_type = LRU - -#per thread -[tuple2stream_htable] -mho_screen_print_ctrl = 0 -mho_thread_safe = 0 -mho_mutex_num = 160 -mho_hash_slot_size = 80000 -mho_hash_max_element_num = 320000 -mho_expire_time = 0 -mho_eliminate_type = LRU - -[field_stat] -remote_switch = 1 -remote_ip = 127.0.0.1 -remote_port = 58100 -local_path = ./fs2_kni.status -stat_cycle = 1 -print_mode = 1 -# 1:FS_OUTPUT_STATSD; 2:FS_OUTPUT_INFLUX_LINE -statsd_format = 2 -APP_NAME = fs2_kni - -#self test Shunt rules security policy id -[tsg_diagnose] -enabled = 1 -security_policy_id = 3,4 - - -[ssl_dynamic_bypass] -enabled = 0 - -#kni dynamic bypass -[traceid2sslinfo_htable] -mho_screen_print_ctrl = 0 -mho_thread_safe = 1 -mho_mutex_num = 160 -mho_hash_slot_size = 80000 -mho_hash_max_element_num = 320000 -mho_expire_time = 300 -mho_eliminate_type = FIFO - -[sslinfo2bypass_htable] -mho_screen_print_ctrl = 0 -mho_thread_safe = 1 -mho_mutex_num = 160 -mho_hash_slot_size = 640000 -mho_hash_max_element_num = 2560000 -mho_expire_time = 300 -mho_eliminate_type = FIFO - -[proxy_tcp_option] -enabled = 1 -maat_table_compile = PXY_TCP_OPTION_COMPILE -maat_table_addr = PXY_TCP_OPTION_ADDR -maat_table_fqdn = PXY_TCP_OPTION_SERVER_FQDN -enable_override = 0 -client_tcp_maxseg_enable = 0 -client_tcp_maxseg = 1460 -client_tcp_nodelay = 1 -client_tcp_ttl = 70 -client_tcp_keepalive_enable = 1 -client_tcp_keepalive_keepcnt = 8 -client_tcp_keepalive_keepidle = 30 -client_tcp_keepalive_keepintvl = 15 -client_tcp_user_timeout = 600 -server_tcp_maxseg_enable = 0 -server_tcp_maxseg = 1460 -server_tcp_nodelay = 1 -server_tcp_ttl = 75 -server_tcp_keepalive_enable = 1 -server_tcp_keepalive_keepcnt = 8 -server_tcp_keepalive_keepidle = 30 -server_tcp_keepalive_keepintvl = 15 -server_tcp_user_timeout = 600 -bypass_duplicated_packet = 0 -tcp_passthrough = 0 - -[share_session_attribute] -SESSION_ATTRIBUTE_LABEL=TSG_MASTER_INTERNAL_LABEL - -[proxy_hits] -interval_ms=1000 -telegraf_port=8900 -telegraf_ip=127.0.0.1 -app_name="proxy_rule_hits" diff --git a/ansible/roles/maat-redis/files/maat-redis-exporter.service b/ansible/roles/maat-redis/files/maat-redis-exporter.service deleted file mode 100644 index 42a07c27..00000000 --- a/ansible/roles/maat-redis/files/maat-redis-exporter.service +++ /dev/null @@ -1,12 +0,0 @@ -[Unit] -Description=Redis Exporter for MAAT-REDIS -After=network.target maat-redis.service -Requires=maat-redis.service - -[Service] -ExecStart=/opt/tsg/exporter/redis_exporter -redis.addr=redis://localhost:7002 -redis-only-metrics -Type=simple - -[Install] -WantedBy=multi-user.target - diff --git a/ansible/roles/maat-redis/files/maat-redis.service b/ansible/roles/maat-redis/files/maat-redis.service deleted file mode 100644 index 588188e3..00000000 --- a/ansible/roles/maat-redis/files/maat-redis.service +++ /dev/null @@ -1,13 +0,0 @@ -[Unit] -Description=Redis persistent key-value database -After=network.target - -[Service] -ExecStart=/usr/bin/redis-server /etc/maat-redis.conf --supervised systemd -ExecStop=/usr/libexec/redis-shutdown maat-redis -Type=notify -TimeoutSec=300s - -[Install] -WantedBy=multi-user.target - diff --git a/ansible/roles/maat-redis/tasks/main.yml b/ansible/roles/maat-redis/tasks/main.yml deleted file mode 100644 index 78a11019..00000000 --- a/ansible/roles/maat-redis/tasks/main.yml +++ /dev/null @@ -1,58 +0,0 @@ -- name: "copy maat-redis file to dest" - copy: - src: "{{ role_path }}/files/maat-redis.service" - dest: "/usr/lib/systemd/system" - mode: 0644 - -- name: "copy maat-redis exporter file to dest" - copy: - src: "{{ role_path }}/files/maat-redis-exporter.service" - dest: "/usr/lib/systemd/system" - mode: 0644 - -- name: "Create /usr/lib/systemd/system/maat-redis.service.d directory if it does not exist" - file: - path: "{{ item }}" - state: directory - mode: '0755' - with_items: - - /usr/lib/systemd/system/maat-redis.service.d - -- name: "Create /usr/lib/systemd/system/maat-redis-exporter.service.d directory if it does not exist" - file: - path: "{{ item }}" - state: directory - mode: '0755' - with_items: - - /usr/lib/systemd/system/maat-redis-exporter.service.d - -- name: "copy slice file to maat-redis.service.d" - copy: - src: "{{ role_path }}/templates/service_override_slice.conf.j2" - dest: /usr/lib/systemd/system/maat-redis.service.d/service_override_slice.conf - mode: 0644 - when: runtime_env != 'TSG-X-P0906' - -- name: "copy slice file to maat-redis-exporter.service.d" - copy: - src: "{{ role_path }}/templates/service_override_slice.conf.j2" - dest: /usr/lib/systemd/system/maat-redis-exporter.service.d/service_override_slice.conf - mode: 0644 - when: runtime_env != 'TSG-X-P0906' - -- name: "Template the maat-redis.conf" - template: - src: "{{ role_path }}/templates/maat-redis.conf.j2.j2" - dest: /opt/tsg/tsg-os-provision/templates/maat-redis.conf.j2 - tags: template - when: runtime_env != 'TSG-X-P0906' - -- name: "replace action: replace service WantedBy from multi-user.target to workload.target" - replace: - path: "{{ item }}" - regexp: 'WantedBy=multi-user.target' - replace: 'WantedBy=workload.target' - with_items: - - /usr/lib/systemd/system/maat-redis.service - - /usr/lib/systemd/system/maat-redis-exporter.service - when: runtime_env != 'TSG-X-P0906' diff --git a/ansible/roles/maat-redis/templates/maat-redis.conf.j2.j2 b/ansible/roles/maat-redis/templates/maat-redis.conf.j2.j2 deleted file mode 100644 index 0cf44406..00000000 --- a/ansible/roles/maat-redis/templates/maat-redis.conf.j2.j2 +++ /dev/null @@ -1,2052 +0,0 @@ -# Redis configuration file example. -# -# Note that in order to read the configuration file, Redis must be -# started with the file path as first argument: -# -# ./redis-server /path/to/redis.conf - -# Note on units: when memory size is needed, it is possible to specify -# it in the usual form of 1k 5GB 4M and so forth: -# -# 1k => 1000 bytes -# 1kb => 1024 bytes -# 1m => 1000000 bytes -# 1mb => 1024*1024 bytes -# 1g => 1000000000 bytes -# 1gb => 1024*1024*1024 bytes -# -# units are case insensitive so 1GB 1Gb 1gB are all the same. - -################################## INCLUDES ################################### - -# Include one or more other config files here. This is useful if you -# have a standard template that goes to all Redis servers but also need -# to customize a few per-server settings. Include files can include -# other files, so use this wisely. -# -# Note that option "include" won't be rewritten by command "CONFIG REWRITE" -# from admin or Redis Sentinel. Since Redis always uses the last processed -# line as value of a configuration directive, you'd better put includes -# at the beginning of this file to avoid overwriting config change at runtime. -# -# If instead you are interested in using includes to override configuration -# options, it is better to use include as the last line. -# -# include /path/to/local.conf -# include /path/to/other.conf - -################################## MODULES ##################################### - -# Load modules at startup. If the server is not able to load modules -# it will abort. It is possible to use multiple loadmodule directives. -# -# loadmodule /path/to/my_module.so -# loadmodule /path/to/other_module.so - -################################## NETWORK ##################################### - -# By default, if no "bind" configuration directive is specified, Redis listens -# for connections from all available network interfaces on the host machine. -# It is possible to listen to just one or multiple selected interfaces using -# the "bind" configuration directive, followed by one or more IP addresses. -# Each address can be prefixed by "-", which means that redis will not fail to -# start if the address is not available. Being not available only refers to -# addresses that does not correspond to any network interfece. Addresses that -# are already in use will always fail, and unsupported protocols will always BE -# silently skipped. -# -# Examples: -# -# bind 192.168.1.100 10.0.0.1 # listens on two specific IPv4 addresses -# bind 127.0.0.1 ::1 # listens on loopback IPv4 and IPv6 -# bind * -::* # like the default, all available interfaces -# -# ~~~ WARNING ~~~ If the computer running Redis is directly exposed to the -# internet, binding to all the interfaces is dangerous and will expose the -# instance to everybody on the internet. So by default we uncomment the -# following bind directive, that will force Redis to listen only on the -# IPv4 and IPv6 (if available) loopback interface addresses (this means Redis -# will only be able to accept client connections from the same host that it is -# running on). -# -# IF YOU ARE SURE YOU WANT YOUR INSTANCE TO LISTEN TO ALL THE INTERFACES -# JUST COMMENT OUT THE FOLLOWING LINE. -# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -#bind 127.0.0.1 -::1 - -# Protected mode is a layer of security protection, in order to avoid that -# Redis instances left open on the internet are accessed and exploited. -# -# When protected mode is on and if: -# -# 1) The server is not binding explicitly to a set of addresses using the -# "bind" directive. -# 2) No password is configured. -# -# The server only accepts connections from clients connecting from the -# IPv4 and IPv6 loopback addresses 127.0.0.1 and ::1, and from Unix domain -# sockets. -# -# By default protected mode is enabled. You should disable it only if -# you are sure you want clients from other hosts to connect to Redis -# even if no authentication is configured, nor a specific set of interfaces -# are explicitly listed using the "bind" directive. -protected-mode no - -# Accept connections on the specified port, default is 6379 (IANA #815344). -# If port 0 is specified Redis will not listen on a TCP socket. -port 7002 - -# TCP listen() backlog. -# -# In high requests-per-second environments you need a high backlog in order -# to avoid slow clients connection issues. Note that the Linux kernel -# will silently truncate it to the value of /proc/sys/net/core/somaxconn so -# make sure to raise both the value of somaxconn and tcp_max_syn_backlog -# in order to get the desired effect. -tcp-backlog 511 - -# Unix socket. -# -# Specify the path for the Unix socket that will be used to listen for -# incoming connections. There is no default, so Redis will not listen -# on a unix socket when not specified. -# -# unixsocket /run/redis.sock -# unixsocketperm 700 - -# Close the connection after a client is idle for N seconds (0 to disable) -timeout 0 - -# TCP keepalive. -# -# If non-zero, use SO_KEEPALIVE to send TCP ACKs to clients in absence -# of communication. This is useful for two reasons: -# -# 1) Detect dead peers. -# 2) Force network equipment in the middle to consider the connection to be -# alive. -# -# On Linux, the specified value (in seconds) is the period used to send ACKs. -# Note that to close the connection the double of the time is needed. -# On other kernels the period depends on the kernel configuration. -# -# A reasonable value for this option is 300 seconds, which is the new -# Redis default starting with Redis 3.2.1. -tcp-keepalive 300 - -################################# TLS/SSL ##################################### - -# By default, TLS/SSL is disabled. To enable it, the "tls-port" configuration -# directive can be used to define TLS-listening ports. To enable TLS on the -# default port, use: -# -# port 0 -# tls-port 6379 - -# Configure a X.509 certificate and private key to use for authenticating the -# server to connected clients, masters or cluster peers. These files should be -# PEM formatted. -# -# tls-cert-file redis.crt -# tls-key-file redis.key -# -# If the key file is encrypted using a passphrase, it can be included here -# as well. -# -# tls-key-file-pass secret - -# Normally Redis uses the same certificate for both server functions (accepting -# connections) and client functions (replicating from a master, establishing -# cluster bus connections, etc.). -# -# Sometimes certificates are issued with attributes that designate them as -# client-only or server-only certificates. In that case it may be desired to use -# different certificates for incoming (server) and outgoing (client) -# connections. To do that, use the following directives: -# -# tls-client-cert-file client.crt -# tls-client-key-file client.key -# -# If the key file is encrypted using a passphrase, it can be included here -# as well. -# -# tls-client-key-file-pass secret - -# Configure a DH parameters file to enable Diffie-Hellman (DH) key exchange: -# -# tls-dh-params-file redis.dh - -# Configure a CA certificate(s) bundle or directory to authenticate TLS/SSL -# clients and peers. Redis requires an explicit configuration of at least one -# of these, and will not implicitly use the system wide configuration. -# -# tls-ca-cert-file ca.crt -# tls-ca-cert-dir /etc/ssl/certs - -# By default, clients (including replica servers) on a TLS port are required -# to authenticate using valid client side certificates. -# -# If "no" is specified, client certificates are not required and not accepted. -# If "optional" is specified, client certificates are accepted and must be -# valid if provided, but are not required. -# -# tls-auth-clients no -# tls-auth-clients optional - -# By default, a Redis replica does not attempt to establish a TLS connection -# with its master. -# -# Use the following directive to enable TLS on replication links. -# -# tls-replication yes - -# By default, the Redis Cluster bus uses a plain TCP connection. To enable -# TLS for the bus protocol, use the following directive: -# -# tls-cluster yes - -# By default, only TLSv1.2 and TLSv1.3 are enabled and it is highly recommended -# that older formally deprecated versions are kept disabled to reduce the attack surface. -# You can explicitly specify TLS versions to support. -# Allowed values are case insensitive and include "TLSv1", "TLSv1.1", "TLSv1.2", -# "TLSv1.3" (OpenSSL >= 1.1.1) or any combination. -# To enable only TLSv1.2 and TLSv1.3, use: -# -# tls-protocols "TLSv1.2 TLSv1.3" - -# Configure allowed ciphers. See the ciphers(1ssl) manpage for more information -# about the syntax of this string. -# -# Note: this configuration applies only to <= TLSv1.2. -# -# tls-ciphers DEFAULT:!MEDIUM - -# Configure allowed TLSv1.3 ciphersuites. See the ciphers(1ssl) manpage for more -# information about the syntax of this string, and specifically for TLSv1.3 -# ciphersuites. -# -# tls-ciphersuites TLS_CHACHA20_POLY1305_SHA256 - -# When choosing a cipher, use the server's preference instead of the client -# preference. By default, the server follows the client's preference. -# -# tls-prefer-server-ciphers yes - -# By default, TLS session caching is enabled to allow faster and less expensive -# reconnections by clients that support it. Use the following directive to disable -# caching. -# -# tls-session-caching no - -# Change the default number of TLS sessions cached. A zero value sets the cache -# to unlimited size. The default size is 20480. -# -# tls-session-cache-size 5000 - -# Change the default timeout of cached TLS sessions. The default timeout is 300 -# seconds. -# -# tls-session-cache-timeout 60 - -################################# GENERAL ##################################### - -# By default Redis does not run as a daemon. Use 'yes' if you need it. -# Note that Redis will write a pid file in /var/run/redis.pid when daemonized. -# When Redis is supervised by upstart or systemd, this parameter has no impact. -daemonize no - -# If you run Redis from upstart or systemd, Redis can interact with your -# supervision tree. Options: -# supervised no - no supervision interaction -# supervised upstart - signal upstart by putting Redis into SIGSTOP mode -# requires "expect stop" in your upstart job config -# supervised systemd - signal systemd by writing READY=1 to $NOTIFY_SOCKET -# on startup, and updating Redis status on a regular -# basis. -# supervised auto - detect upstart or systemd method based on -# UPSTART_JOB or NOTIFY_SOCKET environment variables -# Note: these supervision methods only signal "process is ready." -# They do not enable continuous pings back to your supervisor. -# -# The default is "no". To run under upstart/systemd, you can simply uncomment -# the line below: -# -supervised no - -# If a pid file is specified, Redis writes it where specified at startup -# and removes it at exit. -# -# When the server runs non daemonized, no pid file is created if none is -# specified in the configuration. When the server is daemonized, the pid file -# is used even if not specified, defaulting to "/var/run/redis.pid". -# -# Creating a pid file is best effort: if Redis is not able to create it -# nothing bad happens, the server will start and run normally. -# -# Note that on modern Linux systems "/run/redis.pid" is more conforming -# and should be used instead. -pidfile /var/run/redis_7002.pid - -# Specify the server verbosity level. -# This can be one of: -# debug (a lot of information, useful for development/testing) -# verbose (many rarely useful info, but not a mess like the debug level) -# notice (moderately verbose, what you want in production probably) -# warning (only very important / critical messages are logged) -loglevel notice - -# Specify the log file name. Also the empty string can be used to force -# Redis to log on the standard output. Note that if you use standard -# output for logging but daemonize, logs will be sent to /dev/null -logfile /var/log/redis/redis.log - -# To enable logging to the system logger, just set 'syslog-enabled' to yes, -# and optionally update the other syslog parameters to suit your needs. -# syslog-enabled no - -# Specify the syslog identity. -# syslog-ident redis - -# Specify the syslog facility. Must be USER or between LOCAL0-LOCAL7. -# syslog-facility local0 - -# To disable the built in crash log, which will possibly produce cleaner core -# dumps when they are needed, uncomment the following: -# -# crash-log-enabled no - -# To disable the fast memory check that's run as part of the crash log, which -# will possibly let redis terminate sooner, uncomment the following: -# -# crash-memcheck-enabled no - -# Set the number of databases. The default database is DB 0, you can select -# a different one on a per-connection basis using SELECT where -# dbid is a number between 0 and 'databases'-1 -databases 256 - -# By default Redis shows an ASCII art logo only when started to log to the -# standard output and if the standard output is a TTY and syslog logging is -# disabled. Basically this means that normally a logo is displayed only in -# interactive sessions. -# -# However it is possible to force the pre-4.0 behavior and always show a -# ASCII art logo in startup logs by setting the following option to yes. -always-show-logo yes - -# By default, Redis modifies the process title (as seen in 'top' and 'ps') to -# provide some runtime information. It is possible to disable this and leave -# the process name as executed by setting the following to no. -set-proc-title yes - -# When changing the process title, Redis uses the following template to construct -# the modified title. -# -# Template variables are specified in curly brackets. The following variables are -# supported: -# -# {title} Name of process as executed if parent, or type of child process. -# {listen-addr} Bind address or '*' followed by TCP or TLS port listening on, or -# Unix socket if only that's available. -# {server-mode} Special mode, i.e. "[sentinel]" or "[cluster]". -# {port} TCP port listening on, or 0. -# {tls-port} TLS port listening on, or 0. -# {unixsocket} Unix domain socket listening on, or "". -# {config-file} Name of configuration file used. -# -proc-title-template "{title} {listen-addr} {server-mode}" - -################################ SNAPSHOTTING ################################ - -# Save the DB to disk. -# -# save -# -# Redis will save the DB if both the given number of seconds and the given -# number of write operations against the DB occurred. -# -# Snapshotting can be completely disabled with a single empty string argument -# as in following example: -# -save "" -# -# Unless specified otherwise, by default Redis will save the DB: -# * After 3600 seconds (an hour) if at least 1 key changed -# * After 300 seconds (5 minutes) if at least 100 keys changed -# * After 60 seconds if at least 10000 keys changed -# -# You can set these explicitly by uncommenting the three following lines. -# -# save 900 1 -# save 300 10 -# save 60 10000 - -# By default Redis will stop accepting writes if RDB snapshots are enabled -# (at least one save point) and the latest background save failed. -# This will make the user aware (in a hard way) that data is not persisting -# on disk properly, otherwise chances are that no one will notice and some -# disaster will happen. -# -# If the background saving process will start working again Redis will -# automatically allow writes again. -# -# However if you have setup your proper monitoring of the Redis server -# and persistence, you may want to disable this feature so that Redis will -# continue to work as usual even if there are problems with disk, -# permissions, and so forth. -stop-writes-on-bgsave-error yes - -# Compress string objects using LZF when dump .rdb databases? -# By default compression is enabled as it's almost always a win. -# If you want to save some CPU in the saving child set it to 'no' but -# the dataset will likely be bigger if you have compressible values or keys. -rdbcompression yes - -# Since version 5 of RDB a CRC64 checksum is placed at the end of the file. -# This makes the format more resistant to corruption but there is a performance -# hit to pay (around 10%) when saving and loading RDB files, so you can disable it -# for maximum performances. -# -# RDB files created with checksum disabled have a checksum of zero that will -# tell the loading code to skip the check. -rdbchecksum yes - -# Enables or disables full sanitation checks for ziplist and listpack etc when -# loading an RDB or RESTORE payload. This reduces the chances of a assertion or -# crash later on while processing commands. -# Options: -# no - Never perform full sanitation -# yes - Always perform full sanitation -# clients - Perform full sanitation only for user connections. -# Excludes: RDB files, RESTORE commands received from the master -# connection, and client connections which have the -# skip-sanitize-payload ACL flag. -# The default should be 'clients' but since it currently affects cluster -# resharding via MIGRATE, it is temporarily set to 'no' by default. -# -# sanitize-dump-payload no - -# The filename where to dump the DB -dbfilename dump.rdb - -# Remove RDB files used by replication in instances without persistence -# enabled. By default this option is disabled, however there are environments -# where for regulations or other security concerns, RDB files persisted on -# disk by masters in order to feed replicas, or stored on disk by replicas -# in order to load them for the initial synchronization, should be deleted -# ASAP. Note that this option ONLY WORKS in instances that have both AOF -# and RDB persistence disabled, otherwise is completely ignored. -# -# An alternative (and sometimes better) way to obtain the same effect is -# to use diskless replication on both master and replicas instances. However -# in the case of replicas, diskless is not always an option. -rdb-del-sync-files no - -# The working directory. -# -# The DB will be written inside this directory, with the filename specified -# above using the 'dbfilename' configuration directive. -# -# The Append Only File will also be created inside this directory. -# -# Note that you must specify a directory here, not a file name. -dir /var/lib/redis - -################################# REPLICATION ################################# - -# Master-Replica replication. Use replicaof to make a Redis instance a copy of -# another Redis server. A few things to understand ASAP about Redis replication. -# -# +------------------+ +---------------+ -# | Master | ---> | Replica | -# | (receive writes) | | (exact copy) | -# +------------------+ +---------------+ -# -# 1) Redis replication is asynchronous, but you can configure a master to -# stop accepting writes if it appears to be not connected with at least -# a given number of replicas. -# 2) Redis replicas are able to perform a partial resynchronization with the -# master if the replication link is lost for a relatively small amount of -# time. You may want to configure the replication backlog size (see the next -# sections of this file) with a sensible value depending on your needs. -# 3) Replication is automatic and does not need user intervention. After a -# network partition replicas automatically try to reconnect to masters -# and resynchronize with them. -# -# replicaof -{% raw %}replicaof {{ cm.policy_server.address }} {{ cm.policy_server.port }} -{% endraw %} -# If the master is password protected (using the "requirepass" configuration -# directive below) it is possible to tell the replica to authenticate before -# starting the replication synchronization process, otherwise the master will -# refuse the replica request. -# -# masterauth -# -# However this is not enough if you are using Redis ACLs (for Redis version -# 6 or greater), and the default user is not capable of running the PSYNC -# command and/or other commands needed for replication. In this case it's -# better to configure a special user to use with replication, and specify the -# masteruser configuration as such: -# -# masteruser -# -# When masteruser is specified, the replica will authenticate against its -# master using the new AUTH form: AUTH . - -# When a replica loses its connection with the master, or when the replication -# is still in progress, the replica can act in two different ways: -# -# 1) if replica-serve-stale-data is set to 'yes' (the default) the replica will -# still reply to client requests, possibly with out of date data, or the -# data set may just be empty if this is the first synchronization. -# -# 2) If replica-serve-stale-data is set to 'no' the replica will reply with -# an error "SYNC with master in progress" to all commands except: -# INFO, REPLICAOF, AUTH, PING, SHUTDOWN, REPLCONF, ROLE, CONFIG, SUBSCRIBE, -# UNSUBSCRIBE, PSUBSCRIBE, PUNSUBSCRIBE, PUBLISH, PUBSUB, COMMAND, POST, -# HOST and LATENCY. -# -replica-serve-stale-data yes - -# You can configure a replica instance to accept writes or not. Writing against -# a replica instance may be useful to store some ephemeral data (because data -# written on a replica will be easily deleted after resync with the master) but -# may also cause problems if clients are writing to it because of a -# misconfiguration. -# -# Since Redis 2.6 by default replicas are read-only. -# -# Note: read only replicas are not designed to be exposed to untrusted clients -# on the internet. It's just a protection layer against misuse of the instance. -# Still a read only replica exports by default all the administrative commands -# such as CONFIG, DEBUG, and so forth. To a limited extent you can improve -# security of read only replicas using 'rename-command' to shadow all the -# administrative / dangerous commands. -replica-read-only yes - -# Replication SYNC strategy: disk or socket. -# -# New replicas and reconnecting replicas that are not able to continue the -# replication process just receiving differences, need to do what is called a -# "full synchronization". An RDB file is transmitted from the master to the -# replicas. -# -# The transmission can happen in two different ways: -# -# 1) Disk-backed: The Redis master creates a new process that writes the RDB -# file on disk. Later the file is transferred by the parent -# process to the replicas incrementally. -# 2) Diskless: The Redis master creates a new process that directly writes the -# RDB file to replica sockets, without touching the disk at all. -# -# With disk-backed replication, while the RDB file is generated, more replicas -# can be queued and served with the RDB file as soon as the current child -# producing the RDB file finishes its work. With diskless replication instead -# once the transfer starts, new replicas arriving will be queued and a new -# transfer will start when the current one terminates. -# -# When diskless replication is used, the master waits a configurable amount of -# time (in seconds) before starting the transfer in the hope that multiple -# replicas will arrive and the transfer can be parallelized. -# -# With slow disks and fast (large bandwidth) networks, diskless replication -# works better. -repl-diskless-sync no - -# When diskless replication is enabled, it is possible to configure the delay -# the server waits in order to spawn the child that transfers the RDB via socket -# to the replicas. -# -# This is important since once the transfer starts, it is not possible to serve -# new replicas arriving, that will be queued for the next RDB transfer, so the -# server waits a delay in order to let more replicas arrive. -# -# The delay is specified in seconds, and by default is 5 seconds. To disable -# it entirely just set it to 0 seconds and the transfer will start ASAP. -repl-diskless-sync-delay 5 - -# ----------------------------------------------------------------------------- -# WARNING: RDB diskless load is experimental. Since in this setup the replica -# does not immediately store an RDB on disk, it may cause data loss during -# failovers. RDB diskless load + Redis modules not handling I/O reads may also -# cause Redis to abort in case of I/O errors during the initial synchronization -# stage with the master. Use only if you know what you are doing. -# ----------------------------------------------------------------------------- -# -# Replica can load the RDB it reads from the replication link directly from the -# socket, or store the RDB to a file and read that file after it was completely -# received from the master. -# -# In many cases the disk is slower than the network, and storing and loading -# the RDB file may increase replication time (and even increase the master's -# Copy on Write memory and salve buffers). -# However, parsing the RDB file directly from the socket may mean that we have -# to flush the contents of the current database before the full rdb was -# received. For this reason we have the following options: -# -# "disabled" - Don't use diskless load (store the rdb file to the disk first) -# "on-empty-db" - Use diskless load only when it is completely safe. -# "swapdb" - Keep a copy of the current db contents in RAM while parsing -# the data directly from the socket. note that this requires -# sufficient memory, if you don't have it, you risk an OOM kill. -repl-diskless-load disabled - -# Replicas send PINGs to server in a predefined interval. It's possible to -# change this interval with the repl_ping_replica_period option. The default -# value is 10 seconds. -# -# repl-ping-replica-period 10 - -# The following option sets the replication timeout for: -# -# 1) Bulk transfer I/O during SYNC, from the point of view of replica. -# 2) Master timeout from the point of view of replicas (data, pings). -# 3) Replica timeout from the point of view of masters (REPLCONF ACK pings). -# -# It is important to make sure that this value is greater than the value -# specified for repl-ping-replica-period otherwise a timeout will be detected -# every time there is low traffic between the master and the replica. The default -# value is 60 seconds. -# -repl-timeout 300 - -# Disable TCP_NODELAY on the replica socket after SYNC? -# -# If you select "yes" Redis will use a smaller number of TCP packets and -# less bandwidth to send data to replicas. But this can add a delay for -# the data to appear on the replica side, up to 40 milliseconds with -# Linux kernels using a default configuration. -# -# If you select "no" the delay for data to appear on the replica side will -# be reduced but more bandwidth will be used for replication. -# -# By default we optimize for low latency, but in very high traffic conditions -# or when the master and replicas are many hops away, turning this to "yes" may -# be a good idea. -repl-disable-tcp-nodelay no - -# Set the replication backlog size. The backlog is a buffer that accumulates -# replica data when replicas are disconnected for some time, so that when a -# replica wants to reconnect again, often a full resync is not needed, but a -# partial resync is enough, just passing the portion of data the replica -# missed while disconnected. -# -# The bigger the replication backlog, the longer the replica can endure the -# disconnect and later be able to perform a partial resynchronization. -# -# The backlog is only allocated if there is at least one replica connected. -# -# repl-backlog-size 1mb - -# After a master has no connected replicas for some time, the backlog will be -# freed. The following option configures the amount of seconds that need to -# elapse, starting from the time the last replica disconnected, for the backlog -# buffer to be freed. -# -# Note that replicas never free the backlog for timeout, since they may be -# promoted to masters later, and should be able to correctly "partially -# resynchronize" with other replicas: hence they should always accumulate backlog. -# -# A value of 0 means to never release the backlog. -# -# repl-backlog-ttl 3600 - -# The replica priority is an integer number published by Redis in the INFO -# output. It is used by Redis Sentinel in order to select a replica to promote -# into a master if the master is no longer working correctly. -# -# A replica with a low priority number is considered better for promotion, so -# for instance if there are three replicas with priority 10, 100, 25 Sentinel -# will pick the one with priority 10, that is the lowest. -# -# However a special priority of 0 marks the replica as not able to perform the -# role of master, so a replica with priority of 0 will never be selected by -# Redis Sentinel for promotion. -# -# By default the priority is 100. -replica-priority 100 - -# ----------------------------------------------------------------------------- -# By default, Redis Sentinel includes all replicas in its reports. A replica -# can be excluded from Redis Sentinel's announcements. An unannounced replica -# will be ignored by the 'sentinel replicas ' command and won't be -# exposed to Redis Sentinel's clients. -# -# This option does not change the behavior of replica-priority. Even with -# replica-announced set to 'no', the replica can be promoted to master. To -# prevent this behavior, set replica-priority to 0. -# -# replica-announced yes - -# It is possible for a master to stop accepting writes if there are less than -# N replicas connected, having a lag less or equal than M seconds. -# -# The N replicas need to be in "online" state. -# -# The lag in seconds, that must be <= the specified value, is calculated from -# the last ping received from the replica, that is usually sent every second. -# -# This option does not GUARANTEE that N replicas will accept the write, but -# will limit the window of exposure for lost writes in case not enough replicas -# are available, to the specified number of seconds. -# -# For example to require at least 3 replicas with a lag <= 10 seconds use: -# -# min-replicas-to-write 3 -# min-replicas-max-lag 10 -# -# Setting one or the other to 0 disables the feature. -# -# By default min-replicas-to-write is set to 0 (feature disabled) and -# min-replicas-max-lag is set to 10. - -# A Redis master is able to list the address and port of the attached -# replicas in different ways. For example the "INFO replication" section -# offers this information, which is used, among other tools, by -# Redis Sentinel in order to discover replica instances. -# Another place where this info is available is in the output of the -# "ROLE" command of a master. -# -# The listed IP address and port normally reported by a replica is -# obtained in the following way: -# -# IP: The address is auto detected by checking the peer address -# of the socket used by the replica to connect with the master. -# -# Port: The port is communicated by the replica during the replication -# handshake, and is normally the port that the replica is using to -# listen for connections. -# -# However when port forwarding or Network Address Translation (NAT) is -# used, the replica may actually be reachable via different IP and port -# pairs. The following two options can be used by a replica in order to -# report to its master a specific set of IP and port, so that both INFO -# and ROLE will report those values. -# -# There is no need to use both the options if you need to override just -# the port or the IP address. -# -# replica-announce-ip 5.5.5.5 -# replica-announce-port 1234 - -############################### KEYS TRACKING ################################# - -# Redis implements server assisted support for client side caching of values. -# This is implemented using an invalidation table that remembers, using -# a radix key indexed by key name, what clients have which keys. In turn -# this is used in order to send invalidation messages to clients. Please -# check this page to understand more about the feature: -# -# https://redis.io/topics/client-side-caching -# -# When tracking is enabled for a client, all the read only queries are assumed -# to be cached: this will force Redis to store information in the invalidation -# table. When keys are modified, such information is flushed away, and -# invalidation messages are sent to the clients. However if the workload is -# heavily dominated by reads, Redis could use more and more memory in order -# to track the keys fetched by many clients. -# -# For this reason it is possible to configure a maximum fill value for the -# invalidation table. By default it is set to 1M of keys, and once this limit -# is reached, Redis will start to evict keys in the invalidation table -# even if they were not modified, just to reclaim memory: this will in turn -# force the clients to invalidate the cached values. Basically the table -# maximum size is a trade off between the memory you want to spend server -# side to track information about who cached what, and the ability of clients -# to retain cached objects in memory. -# -# If you set the value to 0, it means there are no limits, and Redis will -# retain as many keys as needed in the invalidation table. -# In the "stats" INFO section, you can find information about the number of -# keys in the invalidation table at every given moment. -# -# Note: when key tracking is used in broadcasting mode, no memory is used -# in the server side so this setting is useless. -# -# tracking-table-max-keys 1000000 - -################################## SECURITY ################################### - -# Warning: since Redis is pretty fast, an outside user can try up to -# 1 million passwords per second against a modern box. This means that you -# should use very strong passwords, otherwise they will be very easy to break. -# Note that because the password is really a shared secret between the client -# and the server, and should not be memorized by any human, the password -# can be easily a long string from /dev/urandom or whatever, so by using a -# long and unguessable password no brute force attack will be possible. - -# Redis ACL users are defined in the following format: -# -# user ... acl rules ... -# -# For example: -# -# user worker +@list +@connection ~jobs:* on >ffa9203c493aa99 -# -# The special username "default" is used for new connections. If this user -# has the "nopass" rule, then new connections will be immediately authenticated -# as the "default" user without the need of any password provided via the -# AUTH command. Otherwise if the "default" user is not flagged with "nopass" -# the connections will start in not authenticated state, and will require -# AUTH (or the HELLO command AUTH option) in order to be authenticated and -# start to work. -# -# The ACL rules that describe what a user can do are the following: -# -# on Enable the user: it is possible to authenticate as this user. -# off Disable the user: it's no longer possible to authenticate -# with this user, however the already authenticated connections -# will still work. -# skip-sanitize-payload RESTORE dump-payload sanitation is skipped. -# sanitize-payload RESTORE dump-payload is sanitized (default). -# + Allow the execution of that command -# - Disallow the execution of that command -# +@ Allow the execution of all the commands in such category -# with valid categories are like @admin, @set, @sortedset, ... -# and so forth, see the full list in the server.c file where -# the Redis command table is described and defined. -# The special category @all means all the commands, but currently -# present in the server, and that will be loaded in the future -# via modules. -# +|subcommand Allow a specific subcommand of an otherwise -# disabled command. Note that this form is not -# allowed as negative like -DEBUG|SEGFAULT, but -# only additive starting with "+". -# allcommands Alias for +@all. Note that it implies the ability to execute -# all the future commands loaded via the modules system. -# nocommands Alias for -@all. -# ~ Add a pattern of keys that can be mentioned as part of -# commands. For instance ~* allows all the keys. The pattern -# is a glob-style pattern like the one of KEYS. -# It is possible to specify multiple patterns. -# allkeys Alias for ~* -# resetkeys Flush the list of allowed keys patterns. -# & Add a glob-style pattern of Pub/Sub channels that can be -# accessed by the user. It is possible to specify multiple channel -# patterns. -# allchannels Alias for &* -# resetchannels Flush the list of allowed channel patterns. -# > Add this password to the list of valid password for the user. -# For example >mypass will add "mypass" to the list. -# This directive clears the "nopass" flag (see later). -# < Remove this password from the list of valid passwords. -# nopass All the set passwords of the user are removed, and the user -# is flagged as requiring no password: it means that every -# password will work against this user. If this directive is -# used for the default user, every new connection will be -# immediately authenticated with the default user without -# any explicit AUTH command required. Note that the "resetpass" -# directive will clear this condition. -# resetpass Flush the list of allowed passwords. Moreover removes the -# "nopass" status. After "resetpass" the user has no associated -# passwords and there is no way to authenticate without adding -# some password (or setting it as "nopass" later). -# reset Performs the following actions: resetpass, resetkeys, off, -# -@all. The user returns to the same state it has immediately -# after its creation. -# -# ACL rules can be specified in any order: for instance you can start with -# passwords, then flags, or key patterns. However note that the additive -# and subtractive rules will CHANGE MEANING depending on the ordering. -# For instance see the following example: -# -# user alice on +@all -DEBUG ~* >somepassword -# -# This will allow "alice" to use all the commands with the exception of the -# DEBUG command, since +@all added all the commands to the set of the commands -# alice can use, and later DEBUG was removed. However if we invert the order -# of two ACL rules the result will be different: -# -# user alice on -DEBUG +@all ~* >somepassword -# -# Now DEBUG was removed when alice had yet no commands in the set of allowed -# commands, later all the commands are added, so the user will be able to -# execute everything. -# -# Basically ACL rules are processed left-to-right. -# -# For more information about ACL configuration please refer to -# the Redis web site at https://redis.io/topics/acl - -# ACL LOG -# -# The ACL Log tracks failed commands and authentication events associated -# with ACLs. The ACL Log is useful to troubleshoot failed commands blocked -# by ACLs. The ACL Log is stored in memory. You can reclaim memory with -# ACL LOG RESET. Define the maximum entry length of the ACL Log below. -acllog-max-len 128 - -# Using an external ACL file -# -# Instead of configuring users here in this file, it is possible to use -# a stand-alone file just listing users. The two methods cannot be mixed: -# if you configure users here and at the same time you activate the external -# ACL file, the server will refuse to start. -# -# The format of the external ACL user file is exactly the same as the -# format that is used inside redis.conf to describe users. -# -# aclfile /etc/redis/users.acl - -# IMPORTANT NOTE: starting with Redis 6 "requirepass" is just a compatibility -# layer on top of the new ACL system. The option effect will be just setting -# the password for the default user. Clients will still authenticate using -# AUTH as usually, or more explicitly with AUTH default -# if they follow the new protocol: both will work. -# -# The requirepass is not compatable with aclfile option and the ACL LOAD -# command, these will cause requirepass to be ignored. -# -# requirepass foobared - -# New users are initialized with restrictive permissions by default, via the -# equivalent of this ACL rule 'off resetkeys -@all'. Starting with Redis 6.2, it -# is possible to manage access to Pub/Sub channels with ACL rules as well. The -# default Pub/Sub channels permission if new users is controlled by the -# acl-pubsub-default configuration directive, which accepts one of these values: -# -# allchannels: grants access to all Pub/Sub channels -# resetchannels: revokes access to all Pub/Sub channels -# -# To ensure backward compatibility while upgrading Redis 6.0, acl-pubsub-default -# defaults to the 'allchannels' permission. -# -# Future compatibility note: it is very likely that in a future version of Redis -# the directive's default of 'allchannels' will be changed to 'resetchannels' in -# order to provide better out-of-the-box Pub/Sub security. Therefore, it is -# recommended that you explicitly define Pub/Sub permissions for all users -# rather then rely on implicit default values. Once you've set explicit -# Pub/Sub for all existing users, you should uncomment the following line. -# -# acl-pubsub-default resetchannels - -# Command renaming (DEPRECATED). -# -# ------------------------------------------------------------------------ -# WARNING: avoid using this option if possible. Instead use ACLs to remove -# commands from the default user, and put them only in some admin user you -# create for administrative purposes. -# ------------------------------------------------------------------------ -# -# It is possible to change the name of dangerous commands in a shared -# environment. For instance the CONFIG command may be renamed into something -# hard to guess so that it will still be available for internal-use tools -# but not available for general clients. -# -# Example: -# -# rename-command CONFIG b840fc02d524045429941cc15f59e41cb7be6c52 -# -# It is also possible to completely kill a command by renaming it into -# an empty string: -# -# rename-command CONFIG "" -# -# Please note that changing the name of commands that are logged into the -# AOF file or transmitted to replicas may cause problems. - -################################### CLIENTS #################################### - -# Set the max number of connected clients at the same time. By default -# this limit is set to 10000 clients, however if the Redis server is not -# able to configure the process file limit to allow for the specified limit -# the max number of allowed clients is set to the current file limit -# minus 32 (as Redis reserves a few file descriptors for internal uses). -# -# Once the limit is reached Redis will close all the new connections sending -# an error 'max number of clients reached'. -# -# IMPORTANT: When Redis Cluster is used, the max number of connections is also -# shared with the cluster bus: every node in the cluster will use two -# connections, one incoming and another outgoing. It is important to size the -# limit accordingly in case of very large clusters. -# -# maxclients 10000 - -############################## MEMORY MANAGEMENT ################################ - -# Set a memory usage limit to the specified amount of bytes. -# When the memory limit is reached Redis will try to remove keys -# according to the eviction policy selected (see maxmemory-policy). -# -# If Redis can't remove keys according to the policy, or if the policy is -# set to 'noeviction', Redis will start to reply with errors to commands -# that would use more memory, like SET, LPUSH, and so on, and will continue -# to reply to read-only commands like GET. -# -# This option is usually useful when using Redis as an LRU or LFU cache, or to -# set a hard memory limit for an instance (using the 'noeviction' policy). -# -# WARNING: If you have replicas attached to an instance with maxmemory on, -# the size of the output buffers needed to feed the replicas are subtracted -# from the used memory count, so that network problems / resyncs will -# not trigger a loop where keys are evicted, and in turn the output -# buffer of replicas is full with DELs of keys evicted triggering the deletion -# of more keys, and so forth until the database is completely emptied. -# -# In short... if you have replicas attached it is suggested that you set a lower -# limit for maxmemory so that there is some free RAM on the system for replica -# output buffers (but this is not needed if the policy is 'noeviction'). -# -# maxmemory - -# MAXMEMORY POLICY: how Redis will select what to remove when maxmemory -# is reached. You can select one from the following behaviors: -# -# volatile-lru -> Evict using approximated LRU, only keys with an expire set. -# allkeys-lru -> Evict any key using approximated LRU. -# volatile-lfu -> Evict using approximated LFU, only keys with an expire set. -# allkeys-lfu -> Evict any key using approximated LFU. -# volatile-random -> Remove a random key having an expire set. -# allkeys-random -> Remove a random key, any key. -# volatile-ttl -> Remove the key with the nearest expire time (minor TTL) -# noeviction -> Don't evict anything, just return an error on write operations. -# -# LRU means Least Recently Used -# LFU means Least Frequently Used -# -# Both LRU, LFU and volatile-ttl are implemented using approximated -# randomized algorithms. -# -# Note: with any of the above policies, when there are no suitable keys for -# eviction, Redis will return an error on write operations that require -# more memory. These are usually commands that create new keys, add data or -# modify existing keys. A few examples are: SET, INCR, HSET, LPUSH, SUNIONSTORE, -# SORT (due to the STORE argument), and EXEC (if the transaction includes any -# command that requires memory). -# -# The default is: -# -# maxmemory-policy noeviction - -# LRU, LFU and minimal TTL algorithms are not precise algorithms but approximated -# algorithms (in order to save memory), so you can tune it for speed or -# accuracy. By default Redis will check five keys and pick the one that was -# used least recently, you can change the sample size using the following -# configuration directive. -# -# The default of 5 produces good enough results. 10 Approximates very closely -# true LRU but costs more CPU. 3 is faster but not very accurate. -# -# maxmemory-samples 5 - -# Eviction processing is designed to function well with the default setting. -# If there is an unusually large amount of write traffic, this value may need to -# be increased. Decreasing this value may reduce latency at the risk of -# eviction processing effectiveness -# 0 = minimum latency, 10 = default, 100 = process without regard to latency -# -# maxmemory-eviction-tenacity 10 - -# Starting from Redis 5, by default a replica will ignore its maxmemory setting -# (unless it is promoted to master after a failover or manually). It means -# that the eviction of keys will be just handled by the master, sending the -# DEL commands to the replica as keys evict in the master side. -# -# This behavior ensures that masters and replicas stay consistent, and is usually -# what you want, however if your replica is writable, or you want the replica -# to have a different memory setting, and you are sure all the writes performed -# to the replica are idempotent, then you may change this default (but be sure -# to understand what you are doing). -# -# Note that since the replica by default does not evict, it may end using more -# memory than the one set via maxmemory (there are certain buffers that may -# be larger on the replica, or data structures may sometimes take more memory -# and so forth). So make sure you monitor your replicas and make sure they -# have enough memory to never hit a real out-of-memory condition before the -# master hits the configured maxmemory setting. -# -# replica-ignore-maxmemory yes - -# Redis reclaims expired keys in two ways: upon access when those keys are -# found to be expired, and also in background, in what is called the -# "active expire key". The key space is slowly and interactively scanned -# looking for expired keys to reclaim, so that it is possible to free memory -# of keys that are expired and will never be accessed again in a short time. -# -# The default effort of the expire cycle will try to avoid having more than -# ten percent of expired keys still in memory, and will try to avoid consuming -# more than 25% of total memory and to add latency to the system. However -# it is possible to increase the expire "effort" that is normally set to -# "1", to a greater value, up to the value "10". At its maximum value the -# system will use more CPU, longer cycles (and technically may introduce -# more latency), and will tolerate less already expired keys still present -# in the system. It's a tradeoff between memory, CPU and latency. -# -# active-expire-effort 1 - -############################# LAZY FREEING #################################### - -# Redis has two primitives to delete keys. One is called DEL and is a blocking -# deletion of the object. It means that the server stops processing new commands -# in order to reclaim all the memory associated with an object in a synchronous -# way. If the key deleted is associated with a small object, the time needed -# in order to execute the DEL command is very small and comparable to most other -# O(1) or O(log_N) commands in Redis. However if the key is associated with an -# aggregated value containing millions of elements, the server can block for -# a long time (even seconds) in order to complete the operation. -# -# For the above reasons Redis also offers non blocking deletion primitives -# such as UNLINK (non blocking DEL) and the ASYNC option of FLUSHALL and -# FLUSHDB commands, in order to reclaim memory in background. Those commands -# are executed in constant time. Another thread will incrementally free the -# object in the background as fast as possible. -# -# DEL, UNLINK and ASYNC option of FLUSHALL and FLUSHDB are user-controlled. -# It's up to the design of the application to understand when it is a good -# idea to use one or the other. However the Redis server sometimes has to -# delete keys or flush the whole database as a side effect of other operations. -# Specifically Redis deletes objects independently of a user call in the -# following scenarios: -# -# 1) On eviction, because of the maxmemory and maxmemory policy configurations, -# in order to make room for new data, without going over the specified -# memory limit. -# 2) Because of expire: when a key with an associated time to live (see the -# EXPIRE command) must be deleted from memory. -# 3) Because of a side effect of a command that stores data on a key that may -# already exist. For example the RENAME command may delete the old key -# content when it is replaced with another one. Similarly SUNIONSTORE -# or SORT with STORE option may delete existing keys. The SET command -# itself removes any old content of the specified key in order to replace -# it with the specified string. -# 4) During replication, when a replica performs a full resynchronization with -# its master, the content of the whole database is removed in order to -# load the RDB file just transferred. -# -# In all the above cases the default is to delete objects in a blocking way, -# like if DEL was called. However you can configure each case specifically -# in order to instead release memory in a non-blocking way like if UNLINK -# was called, using the following configuration directives. - -lazyfree-lazy-eviction no -lazyfree-lazy-expire no -lazyfree-lazy-server-del no -replica-lazy-flush no - -# It is also possible, for the case when to replace the user code DEL calls -# with UNLINK calls is not easy, to modify the default behavior of the DEL -# command to act exactly like UNLINK, using the following configuration -# directive: - -lazyfree-lazy-user-del no - -# FLUSHDB, FLUSHALL, and SCRIPT FLUSH support both asynchronous and synchronous -# deletion, which can be controlled by passing the [SYNC|ASYNC] flags into the -# commands. When neither flag is passed, this directive will be used to determine -# if the data should be deleted asynchronously. - -lazyfree-lazy-user-flush no - -################################ THREADED I/O ################################# - -# Redis is mostly single threaded, however there are certain threaded -# operations such as UNLINK, slow I/O accesses and other things that are -# performed on side threads. -# -# Now it is also possible to handle Redis clients socket reads and writes -# in different I/O threads. Since especially writing is so slow, normally -# Redis users use pipelining in order to speed up the Redis performances per -# core, and spawn multiple instances in order to scale more. Using I/O -# threads it is possible to easily speedup two times Redis without resorting -# to pipelining nor sharding of the instance. -# -# By default threading is disabled, we suggest enabling it only in machines -# that have at least 4 or more cores, leaving at least one spare core. -# Using more than 8 threads is unlikely to help much. We also recommend using -# threaded I/O only if you actually have performance problems, with Redis -# instances being able to use a quite big percentage of CPU time, otherwise -# there is no point in using this feature. -# -# So for instance if you have a four cores boxes, try to use 2 or 3 I/O -# threads, if you have a 8 cores, try to use 6 threads. In order to -# enable I/O threads use the following configuration directive: -# -# io-threads 4 -# -# Setting io-threads to 1 will just use the main thread as usual. -# When I/O threads are enabled, we only use threads for writes, that is -# to thread the write(2) syscall and transfer the client buffers to the -# socket. However it is also possible to enable threading of reads and -# protocol parsing using the following configuration directive, by setting -# it to yes: -# -# io-threads-do-reads no -# -# Usually threading reads doesn't help much. -# -# NOTE 1: This configuration directive cannot be changed at runtime via -# CONFIG SET. Aso this feature currently does not work when SSL is -# enabled. -# -# NOTE 2: If you want to test the Redis speedup using redis-benchmark, make -# sure you also run the benchmark itself in threaded mode, using the -# --threads option to match the number of Redis threads, otherwise you'll not -# be able to notice the improvements. - -############################ KERNEL OOM CONTROL ############################## - -# On Linux, it is possible to hint the kernel OOM killer on what processes -# should be killed first when out of memory. -# -# Enabling this feature makes Redis actively control the oom_score_adj value -# for all its processes, depending on their role. The default scores will -# attempt to have background child processes killed before all others, and -# replicas killed before masters. -# -# Redis supports three options: -# -# no: Don't make changes to oom-score-adj (default). -# yes: Alias to "relative" see below. -# absolute: Values in oom-score-adj-values are written as is to the kernel. -# relative: Values are used relative to the initial value of oom_score_adj when -# the server starts and are then clamped to a range of -1000 to 1000. -# Because typically the initial value is 0, they will often match the -# absolute values. -oom-score-adj no - -# When oom-score-adj is used, this directive controls the specific values used -# for master, replica and background child processes. Values range -2000 to -# 2000 (higher means more likely to be killed). -# -# Unprivileged processes (not root, and without CAP_SYS_RESOURCE capabilities) -# can freely increase their value, but not decrease it below its initial -# settings. This means that setting oom-score-adj to "relative" and setting the -# oom-score-adj-values to positive values will always succeed. -oom-score-adj-values 0 200 800 - - -#################### KERNEL transparent hugepage CONTROL ###################### - -# Usually the kernel Transparent Huge Pages control is set to "madvise" or -# or "never" by default (/sys/kernel/mm/transparent_hugepage/enabled), in which -# case this config has no effect. On systems in which it is set to "always", -# redis will attempt to disable it specifically for the redis process in order -# to avoid latency problems specifically with fork(2) and CoW. -# If for some reason you prefer to keep it enabled, you can set this config to -# "no" and the kernel global to "always". - -disable-thp yes - -############################## APPEND ONLY MODE ############################### - -# By default Redis asynchronously dumps the dataset on disk. This mode is -# good enough in many applications, but an issue with the Redis process or -# a power outage may result into a few minutes of writes lost (depending on -# the configured save points). -# -# The Append Only File is an alternative persistence mode that provides -# much better durability. For instance using the default data fsync policy -# (see later in the config file) Redis can lose just one second of writes in a -# dramatic event like a server power outage, or a single write if something -# wrong with the Redis process itself happens, but the operating system is -# still running correctly. -# -# AOF and RDB persistence can be enabled at the same time without problems. -# If the AOF is enabled on startup Redis will load the AOF, that is the file -# with the better durability guarantees. -# -# Please check https://redis.io/topics/persistence for more information. - -appendonly no - -# The name of the append only file (default: "appendonly.aof") - -appendfilename "appendonly.aof" - -# The fsync() call tells the Operating System to actually write data on disk -# instead of waiting for more data in the output buffer. Some OS will really flush -# data on disk, some other OS will just try to do it ASAP. -# -# Redis supports three different modes: -# -# no: don't fsync, just let the OS flush the data when it wants. Faster. -# always: fsync after every write to the append only log. Slow, Safest. -# everysec: fsync only one time every second. Compromise. -# -# The default is "everysec", as that's usually the right compromise between -# speed and data safety. It's up to you to understand if you can relax this to -# "no" that will let the operating system flush the output buffer when -# it wants, for better performances (but if you can live with the idea of -# some data loss consider the default persistence mode that's snapshotting), -# or on the contrary, use "always" that's very slow but a bit safer than -# everysec. -# -# More details please check the following article: -# http://antirez.com/post/redis-persistence-demystified.html -# -# If unsure, use "everysec". - -# appendfsync always -appendfsync everysec -# appendfsync no - -# When the AOF fsync policy is set to always or everysec, and a background -# saving process (a background save or AOF log background rewriting) is -# performing a lot of I/O against the disk, in some Linux configurations -# Redis may block too long on the fsync() call. Note that there is no fix for -# this currently, as even performing fsync in a different thread will block -# our synchronous write(2) call. -# -# In order to mitigate this problem it's possible to use the following option -# that will prevent fsync() from being called in the main process while a -# BGSAVE or BGREWRITEAOF is in progress. -# -# This means that while another child is saving, the durability of Redis is -# the same as "appendfsync none". In practical terms, this means that it is -# possible to lose up to 30 seconds of log in the worst scenario (with the -# default Linux settings). -# -# If you have latency problems turn this to "yes". Otherwise leave it as -# "no" that is the safest pick from the point of view of durability. - -no-appendfsync-on-rewrite no - -# Automatic rewrite of the append only file. -# Redis is able to automatically rewrite the log file implicitly calling -# BGREWRITEAOF when the AOF log size grows by the specified percentage. -# -# This is how it works: Redis remembers the size of the AOF file after the -# latest rewrite (if no rewrite has happened since the restart, the size of -# the AOF at startup is used). -# -# This base size is compared to the current size. If the current size is -# bigger than the specified percentage, the rewrite is triggered. Also -# you need to specify a minimal size for the AOF file to be rewritten, this -# is useful to avoid rewriting the AOF file even if the percentage increase -# is reached but it is still pretty small. -# -# Specify a percentage of zero in order to disable the automatic AOF -# rewrite feature. - -auto-aof-rewrite-percentage 100 -auto-aof-rewrite-min-size 64mb - -# An AOF file may be found to be truncated at the end during the Redis -# startup process, when the AOF data gets loaded back into memory. -# This may happen when the system where Redis is running -# crashes, especially when an ext4 filesystem is mounted without the -# data=ordered option (however this can't happen when Redis itself -# crashes or aborts but the operating system still works correctly). -# -# Redis can either exit with an error when this happens, or load as much -# data as possible (the default now) and start if the AOF file is found -# to be truncated at the end. The following option controls this behavior. -# -# If aof-load-truncated is set to yes, a truncated AOF file is loaded and -# the Redis server starts emitting a log to inform the user of the event. -# Otherwise if the option is set to no, the server aborts with an error -# and refuses to start. When the option is set to no, the user requires -# to fix the AOF file using the "redis-check-aof" utility before to restart -# the server. -# -# Note that if the AOF file will be found to be corrupted in the middle -# the server will still exit with an error. This option only applies when -# Redis will try to read more data from the AOF file but not enough bytes -# will be found. -aof-load-truncated yes - -# When rewriting the AOF file, Redis is able to use an RDB preamble in the -# AOF file for faster rewrites and recoveries. When this option is turned -# on the rewritten AOF file is composed of two different stanzas: -# -# [RDB file][AOF tail] -# -# When loading, Redis recognizes that the AOF file starts with the "REDIS" -# string and loads the prefixed RDB file, then continues loading the AOF -# tail. -aof-use-rdb-preamble yes - -################################ LUA SCRIPTING ############################### - -# Max execution time of a Lua script in milliseconds. -# -# If the maximum execution time is reached Redis will log that a script is -# still in execution after the maximum allowed time and will start to -# reply to queries with an error. -# -# When a long running script exceeds the maximum execution time only the -# SCRIPT KILL and SHUTDOWN NOSAVE commands are available. The first can be -# used to stop a script that did not yet call any write commands. The second -# is the only way to shut down the server in the case a write command was -# already issued by the script but the user doesn't want to wait for the natural -# termination of the script. -# -# Set it to 0 or a negative value for unlimited execution without warnings. -lua-time-limit 5000 - -################################ REDIS CLUSTER ############################### - -# Normal Redis instances can't be part of a Redis Cluster; only nodes that are -# started as cluster nodes can. In order to start a Redis instance as a -# cluster node enable the cluster support uncommenting the following: -# -# cluster-enabled yes - -# Every cluster node has a cluster configuration file. This file is not -# intended to be edited by hand. It is created and updated by Redis nodes. -# Every Redis Cluster node requires a different cluster configuration file. -# Make sure that instances running in the same system do not have -# overlapping cluster configuration file names. -# -# cluster-config-file nodes-6379.conf - -# Cluster node timeout is the amount of milliseconds a node must be unreachable -# for it to be considered in failure state. -# Most other internal time limits are a multiple of the node timeout. -# -# cluster-node-timeout 15000 - -# A replica of a failing master will avoid to start a failover if its data -# looks too old. -# -# There is no simple way for a replica to actually have an exact measure of -# its "data age", so the following two checks are performed: -# -# 1) If there are multiple replicas able to failover, they exchange messages -# in order to try to give an advantage to the replica with the best -# replication offset (more data from the master processed). -# Replicas will try to get their rank by offset, and apply to the start -# of the failover a delay proportional to their rank. -# -# 2) Every single replica computes the time of the last interaction with -# its master. This can be the last ping or command received (if the master -# is still in the "connected" state), or the time that elapsed since the -# disconnection with the master (if the replication link is currently down). -# If the last interaction is too old, the replica will not try to failover -# at all. -# -# The point "2" can be tuned by user. Specifically a replica will not perform -# the failover if, since the last interaction with the master, the time -# elapsed is greater than: -# -# (node-timeout * cluster-replica-validity-factor) + repl-ping-replica-period -# -# So for example if node-timeout is 30 seconds, and the cluster-replica-validity-factor -# is 10, and assuming a default repl-ping-replica-period of 10 seconds, the -# replica will not try to failover if it was not able to talk with the master -# for longer than 310 seconds. -# -# A large cluster-replica-validity-factor may allow replicas with too old data to failover -# a master, while a too small value may prevent the cluster from being able to -# elect a replica at all. -# -# For maximum availability, it is possible to set the cluster-replica-validity-factor -# to a value of 0, which means, that replicas will always try to failover the -# master regardless of the last time they interacted with the master. -# (However they'll always try to apply a delay proportional to their -# offset rank). -# -# Zero is the only value able to guarantee that when all the partitions heal -# the cluster will always be able to continue. -# -# cluster-replica-validity-factor 10 - -# Cluster replicas are able to migrate to orphaned masters, that are masters -# that are left without working replicas. This improves the cluster ability -# to resist to failures as otherwise an orphaned master can't be failed over -# in case of failure if it has no working replicas. -# -# Replicas migrate to orphaned masters only if there are still at least a -# given number of other working replicas for their old master. This number -# is the "migration barrier". A migration barrier of 1 means that a replica -# will migrate only if there is at least 1 other working replica for its master -# and so forth. It usually reflects the number of replicas you want for every -# master in your cluster. -# -# Default is 1 (replicas migrate only if their masters remain with at least -# one replica). To disable migration just set it to a very large value or -# set cluster-allow-replica-migration to 'no'. -# A value of 0 can be set but is useful only for debugging and dangerous -# in production. -# -# cluster-migration-barrier 1 - -# Turning off this option allows to use less automatic cluster configuration. -# It both disables migration to orphaned masters and migration from masters -# that became empty. -# -# Default is 'yes' (allow automatic migrations). -# -# cluster-allow-replica-migration yes - -# By default Redis Cluster nodes stop accepting queries if they detect there -# is at least a hash slot uncovered (no available node is serving it). -# This way if the cluster is partially down (for example a range of hash slots -# are no longer covered) all the cluster becomes, eventually, unavailable. -# It automatically returns available as soon as all the slots are covered again. -# -# However sometimes you want the subset of the cluster which is working, -# to continue to accept queries for the part of the key space that is still -# covered. In order to do so, just set the cluster-require-full-coverage -# option to no. -# -# cluster-require-full-coverage yes - -# This option, when set to yes, prevents replicas from trying to failover its -# master during master failures. However the replica can still perform a -# manual failover, if forced to do so. -# -# This is useful in different scenarios, especially in the case of multiple -# data center operations, where we want one side to never be promoted if not -# in the case of a total DC failure. -# -# cluster-replica-no-failover no - -# This option, when set to yes, allows nodes to serve read traffic while the -# the cluster is in a down state, as long as it believes it owns the slots. -# -# This is useful for two cases. The first case is for when an application -# doesn't require consistency of data during node failures or network partitions. -# One example of this is a cache, where as long as the node has the data it -# should be able to serve it. -# -# The second use case is for configurations that don't meet the recommended -# three shards but want to enable cluster mode and scale later. A -# master outage in a 1 or 2 shard configuration causes a read/write outage to the -# entire cluster without this option set, with it set there is only a write outage. -# Without a quorum of masters, slot ownership will not change automatically. -# -# cluster-allow-reads-when-down no - -# In order to setup your cluster make sure to read the documentation -# available at https://redis.io web site. - -########################## CLUSTER DOCKER/NAT support ######################## - -# In certain deployments, Redis Cluster nodes address discovery fails, because -# addresses are NAT-ted or because ports are forwarded (the typical case is -# Docker and other containers). -# -# In order to make Redis Cluster working in such environments, a static -# configuration where each node knows its public address is needed. The -# following four options are used for this scope, and are: -# -# * cluster-announce-ip -# * cluster-announce-port -# * cluster-announce-tls-port -# * cluster-announce-bus-port -# -# Each instructs the node about its address, client ports (for connections -# without and with TLS) and cluster message bus port. The information is then -# published in the header of the bus packets so that other nodes will be able to -# correctly map the address of the node publishing the information. -# -# If cluster-tls is set to yes and cluster-announce-tls-port is omitted or set -# to zero, then cluster-announce-port refers to the TLS port. Note also that -# cluster-announce-tls-port has no effect if cluster-tls is set to no. -# -# If the above options are not used, the normal Redis Cluster auto-detection -# will be used instead. -# -# Note that when remapped, the bus port may not be at the fixed offset of -# clients port + 10000, so you can specify any port and bus-port depending -# on how they get remapped. If the bus-port is not set, a fixed offset of -# 10000 will be used as usual. -# -# Example: -# -# cluster-announce-ip 10.1.1.5 -# cluster-announce-tls-port 6379 -# cluster-announce-port 0 -# cluster-announce-bus-port 6380 - -################################## SLOW LOG ################################### - -# The Redis Slow Log is a system to log queries that exceeded a specified -# execution time. The execution time does not include the I/O operations -# like talking with the client, sending the reply and so forth, -# but just the time needed to actually execute the command (this is the only -# stage of command execution where the thread is blocked and can not serve -# other requests in the meantime). -# -# You can configure the slow log with two parameters: one tells Redis -# what is the execution time, in microseconds, to exceed in order for the -# command to get logged, and the other parameter is the length of the -# slow log. When a new command is logged the oldest one is removed from the -# queue of logged commands. - -# The following time is expressed in microseconds, so 1000000 is equivalent -# to one second. Note that a negative number disables the slow log, while -# a value of zero forces the logging of every command. -slowlog-log-slower-than 10000 - -# There is no limit to this length. Just be aware that it will consume memory. -# You can reclaim memory used by the slow log with SLOWLOG RESET. -slowlog-max-len 128 - -################################ LATENCY MONITOR ############################## - -# The Redis latency monitoring subsystem samples different operations -# at runtime in order to collect data related to possible sources of -# latency of a Redis instance. -# -# Via the LATENCY command this information is available to the user that can -# print graphs and obtain reports. -# -# The system only logs operations that were performed in a time equal or -# greater than the amount of milliseconds specified via the -# latency-monitor-threshold configuration directive. When its value is set -# to zero, the latency monitor is turned off. -# -# By default latency monitoring is disabled since it is mostly not needed -# if you don't have latency issues, and collecting data has a performance -# impact, that while very small, can be measured under big load. Latency -# monitoring can easily be enabled at runtime using the command -# "CONFIG SET latency-monitor-threshold " if needed. -latency-monitor-threshold 0 - -############################# EVENT NOTIFICATION ############################## - -# Redis can notify Pub/Sub clients about events happening in the key space. -# This feature is documented at https://redis.io/topics/notifications -# -# For instance if keyspace events notification is enabled, and a client -# performs a DEL operation on key "foo" stored in the Database 0, two -# messages will be published via Pub/Sub: -# -# PUBLISH __keyspace@0__:foo del -# PUBLISH __keyevent@0__:del foo -# -# It is possible to select the events that Redis will notify among a set -# of classes. Every class is identified by a single character: -# -# K Keyspace events, published with __keyspace@__ prefix. -# E Keyevent events, published with __keyevent@__ prefix. -# g Generic commands (non-type specific) like DEL, EXPIRE, RENAME, ... -# $ String commands -# l List commands -# s Set commands -# h Hash commands -# z Sorted set commands -# x Expired events (events generated every time a key expires) -# e Evicted events (events generated when a key is evicted for maxmemory) -# t Stream commands -# d Module key type events -# m Key-miss events (Note: It is not included in the 'A' class) -# A Alias for g$lshzxetd, so that the "AKE" string means all the events -# (Except key-miss events which are excluded from 'A' due to their -# unique nature). -# -# The "notify-keyspace-events" takes as argument a string that is composed -# of zero or multiple characters. The empty string means that notifications -# are disabled. -# -# Example: to enable list and generic events, from the point of view of the -# event name, use: -# -# notify-keyspace-events Elg -# -# Example 2: to get the stream of the expired keys subscribing to channel -# name __keyevent@0__:expired use: -# -# notify-keyspace-events Ex -# -# By default all notifications are disabled because most users don't need -# this feature and the feature has some overhead. Note that if you don't -# specify at least one of K or E, no events will be delivered. -notify-keyspace-events "" - -############################### GOPHER SERVER ################################# - -# Redis contains an implementation of the Gopher protocol, as specified in -# the RFC 1436 (https://www.ietf.org/rfc/rfc1436.txt). -# -# The Gopher protocol was very popular in the late '90s. It is an alternative -# to the web, and the implementation both server and client side is so simple -# that the Redis server has just 100 lines of code in order to implement this -# support. -# -# What do you do with Gopher nowadays? Well Gopher never *really* died, and -# lately there is a movement in order for the Gopher more hierarchical content -# composed of just plain text documents to be resurrected. Some want a simpler -# internet, others believe that the mainstream internet became too much -# controlled, and it's cool to create an alternative space for people that -# want a bit of fresh air. -# -# Anyway for the 10nth birthday of the Redis, we gave it the Gopher protocol -# as a gift. -# -# --- HOW IT WORKS? --- -# -# The Redis Gopher support uses the inline protocol of Redis, and specifically -# two kind of inline requests that were anyway illegal: an empty request -# or any request that starts with "/" (there are no Redis commands starting -# with such a slash). Normal RESP2/RESP3 requests are completely out of the -# path of the Gopher protocol implementation and are served as usual as well. -# -# If you open a connection to Redis when Gopher is enabled and send it -# a string like "/foo", if there is a key named "/foo" it is served via the -# Gopher protocol. -# -# In order to create a real Gopher "hole" (the name of a Gopher site in Gopher -# talking), you likely need a script like the following: -# -# https://github.com/antirez/gopher2redis -# -# --- SECURITY WARNING --- -# -# If you plan to put Redis on the internet in a publicly accessible address -# to server Gopher pages MAKE SURE TO SET A PASSWORD to the instance. -# Once a password is set: -# -# 1. The Gopher server (when enabled, not by default) will still serve -# content via Gopher. -# 2. However other commands cannot be called before the client will -# authenticate. -# -# So use the 'requirepass' option to protect your instance. -# -# Note that Gopher is not currently supported when 'io-threads-do-reads' -# is enabled. -# -# To enable Gopher support, uncomment the following line and set the option -# from no (the default) to yes. -# -# gopher-enabled no - -############################### ADVANCED CONFIG ############################### - -# Hashes are encoded using a memory efficient data structure when they have a -# small number of entries, and the biggest entry does not exceed a given -# threshold. These thresholds can be configured using the following directives. -hash-max-ziplist-entries 512 -hash-max-ziplist-value 64 - -# Lists are also encoded in a special way to save a lot of space. -# The number of entries allowed per internal list node can be specified -# as a fixed maximum size or a maximum number of elements. -# For a fixed maximum size, use -5 through -1, meaning: -# -5: max size: 64 Kb <-- not recommended for normal workloads -# -4: max size: 32 Kb <-- not recommended -# -3: max size: 16 Kb <-- probably not recommended -# -2: max size: 8 Kb <-- good -# -1: max size: 4 Kb <-- good -# Positive numbers mean store up to _exactly_ that number of elements -# per list node. -# The highest performing option is usually -2 (8 Kb size) or -1 (4 Kb size), -# but if your use case is unique, adjust the settings as necessary. -list-max-ziplist-size -2 - -# Lists may also be compressed. -# Compress depth is the number of quicklist ziplist nodes from *each* side of -# the list to *exclude* from compression. The head and tail of the list -# are always uncompressed for fast push/pop operations. Settings are: -# 0: disable all list compression -# 1: depth 1 means "don't start compressing until after 1 node into the list, -# going from either the head or tail" -# So: [head]->node->node->...->node->[tail] -# [head], [tail] will always be uncompressed; inner nodes will compress. -# 2: [head]->[next]->node->node->...->node->[prev]->[tail] -# 2 here means: don't compress head or head->next or tail->prev or tail, -# but compress all nodes between them. -# 3: [head]->[next]->[next]->node->node->...->node->[prev]->[prev]->[tail] -# etc. -list-compress-depth 0 - -# Sets have a special encoding in just one case: when a set is composed -# of just strings that happen to be integers in radix 10 in the range -# of 64 bit signed integers. -# The following configuration setting sets the limit in the size of the -# set in order to use this special memory saving encoding. -set-max-intset-entries 512 - -# Similarly to hashes and lists, sorted sets are also specially encoded in -# order to save a lot of space. This encoding is only used when the length and -# elements of a sorted set are below the following limits: -zset-max-ziplist-entries 128 -zset-max-ziplist-value 64 - -# HyperLogLog sparse representation bytes limit. The limit includes the -# 16 bytes header. When an HyperLogLog using the sparse representation crosses -# this limit, it is converted into the dense representation. -# -# A value greater than 16000 is totally useless, since at that point the -# dense representation is more memory efficient. -# -# The suggested value is ~ 3000 in order to have the benefits of -# the space efficient encoding without slowing down too much PFADD, -# which is O(N) with the sparse encoding. The value can be raised to -# ~ 10000 when CPU is not a concern, but space is, and the data set is -# composed of many HyperLogLogs with cardinality in the 0 - 15000 range. -hll-sparse-max-bytes 3000 - -# Streams macro node max size / items. The stream data structure is a radix -# tree of big nodes that encode multiple items inside. Using this configuration -# it is possible to configure how big a single node can be in bytes, and the -# maximum number of items it may contain before switching to a new node when -# appending new stream entries. If any of the following settings are set to -# zero, the limit is ignored, so for instance it is possible to set just a -# max entries limit by setting max-bytes to 0 and max-entries to the desired -# value. -stream-node-max-bytes 4096 -stream-node-max-entries 100 - -# Active rehashing uses 1 millisecond every 100 milliseconds of CPU time in -# order to help rehashing the main Redis hash table (the one mapping top-level -# keys to values). The hash table implementation Redis uses (see dict.c) -# performs a lazy rehashing: the more operation you run into a hash table -# that is rehashing, the more rehashing "steps" are performed, so if the -# server is idle the rehashing is never complete and some more memory is used -# by the hash table. -# -# The default is to use this millisecond 10 times every second in order to -# actively rehash the main dictionaries, freeing memory when possible. -# -# If unsure: -# use "activerehashing no" if you have hard latency requirements and it is -# not a good thing in your environment that Redis can reply from time to time -# to queries with 2 milliseconds delay. -# -# use "activerehashing yes" if you don't have such hard requirements but -# want to free memory asap when possible. -activerehashing yes - -# The client output buffer limits can be used to force disconnection of clients -# that are not reading data from the server fast enough for some reason (a -# common reason is that a Pub/Sub client can't consume messages as fast as the -# publisher can produce them). -# -# The limit can be set differently for the three different classes of clients: -# -# normal -> normal clients including MONITOR clients -# replica -> replica clients -# pubsub -> clients subscribed to at least one pubsub channel or pattern -# -# The syntax of every client-output-buffer-limit directive is the following: -# -# client-output-buffer-limit -# -# A client is immediately disconnected once the hard limit is reached, or if -# the soft limit is reached and remains reached for the specified number of -# seconds (continuously). -# So for instance if the hard limit is 32 megabytes and the soft limit is -# 16 megabytes / 10 seconds, the client will get disconnected immediately -# if the size of the output buffers reach 32 megabytes, but will also get -# disconnected if the client reaches 16 megabytes and continuously overcomes -# the limit for 10 seconds. -# -# By default normal clients are not limited because they don't receive data -# without asking (in a push way), but just after a request, so only -# asynchronous clients may create a scenario where data is requested faster -# than it can read. -# -# Instead there is a default limit for pubsub and replica clients, since -# subscribers and replicas receive data in a push fashion. -# -# Both the hard or the soft limit can be disabled by setting them to zero. -client-output-buffer-limit normal 0 0 0 -client-output-buffer-limit replica 256mb 64mb 60 -client-output-buffer-limit pubsub 32mb 8mb 60 - -# Client query buffers accumulate new commands. They are limited to a fixed -# amount by default in order to avoid that a protocol desynchronization (for -# instance due to a bug in the client) will lead to unbound memory usage in -# the query buffer. However you can configure it here if you have very special -# needs, such us huge multi/exec requests or alike. -# -# client-query-buffer-limit 1gb - -# In the Redis protocol, bulk requests, that are, elements representing single -# strings, are normally limited to 512 mb. However you can change this limit -# here, but must be 1mb or greater -# -# proto-max-bulk-len 512mb - -# Redis calls an internal function to perform many background tasks, like -# closing connections of clients in timeout, purging expired keys that are -# never requested, and so forth. -# -# Not all tasks are performed with the same frequency, but Redis checks for -# tasks to perform according to the specified "hz" value. -# -# By default "hz" is set to 10. Raising the value will use more CPU when -# Redis is idle, but at the same time will make Redis more responsive when -# there are many keys expiring at the same time, and timeouts may be -# handled with more precision. -# -# The range is between 1 and 500, however a value over 100 is usually not -# a good idea. Most users should use the default of 10 and raise this up to -# 100 only in environments where very low latency is required. -hz 10 - -# Normally it is useful to have an HZ value which is proportional to the -# number of clients connected. This is useful in order, for instance, to -# avoid too many clients are processed for each background task invocation -# in order to avoid latency spikes. -# -# Since the default HZ value by default is conservatively set to 10, Redis -# offers, and enables by default, the ability to use an adaptive HZ value -# which will temporarily raise when there are many connected clients. -# -# When dynamic HZ is enabled, the actual configured HZ will be used -# as a baseline, but multiples of the configured HZ value will be actually -# used as needed once more clients are connected. In this way an idle -# instance will use very little CPU time while a busy instance will be -# more responsive. -dynamic-hz yes - -# When a child rewrites the AOF file, if the following option is enabled -# the file will be fsync-ed every 32 MB of data generated. This is useful -# in order to commit the file to the disk more incrementally and avoid -# big latency spikes. -aof-rewrite-incremental-fsync yes - -# When redis saves RDB file, if the following option is enabled -# the file will be fsync-ed every 32 MB of data generated. This is useful -# in order to commit the file to the disk more incrementally and avoid -# big latency spikes. -rdb-save-incremental-fsync yes - -# Redis LFU eviction (see maxmemory setting) can be tuned. However it is a good -# idea to start with the default settings and only change them after investigating -# how to improve the performances and how the keys LFU change over time, which -# is possible to inspect via the OBJECT FREQ command. -# -# There are two tunable parameters in the Redis LFU implementation: the -# counter logarithm factor and the counter decay time. It is important to -# understand what the two parameters mean before changing them. -# -# The LFU counter is just 8 bits per key, it's maximum value is 255, so Redis -# uses a probabilistic increment with logarithmic behavior. Given the value -# of the old counter, when a key is accessed, the counter is incremented in -# this way: -# -# 1. A random number R between 0 and 1 is extracted. -# 2. A probability P is calculated as 1/(old_value*lfu_log_factor+1). -# 3. The counter is incremented only if R < P. -# -# The default lfu-log-factor is 10. This is a table of how the frequency -# counter changes with a different number of accesses with different -# logarithmic factors: -# -# +--------+------------+------------+------------+------------+------------+ -# | factor | 100 hits | 1000 hits | 100K hits | 1M hits | 10M hits | -# +--------+------------+------------+------------+------------+------------+ -# | 0 | 104 | 255 | 255 | 255 | 255 | -# +--------+------------+------------+------------+------------+------------+ -# | 1 | 18 | 49 | 255 | 255 | 255 | -# +--------+------------+------------+------------+------------+------------+ -# | 10 | 10 | 18 | 142 | 255 | 255 | -# +--------+------------+------------+------------+------------+------------+ -# | 100 | 8 | 11 | 49 | 143 | 255 | -# +--------+------------+------------+------------+------------+------------+ -# -# NOTE: The above table was obtained by running the following commands: -# -# redis-benchmark -n 1000000 incr foo -# redis-cli object freq foo -# -# NOTE 2: The counter initial value is 5 in order to give new objects a chance -# to accumulate hits. -# -# The counter decay time is the time, in minutes, that must elapse in order -# for the key counter to be divided by two (or decremented if it has a value -# less <= 10). -# -# The default value for the lfu-decay-time is 1. A special value of 0 means to -# decay the counter every time it happens to be scanned. -# -# lfu-log-factor 10 -# lfu-decay-time 1 - -########################### ACTIVE DEFRAGMENTATION ####################### -# -# What is active defragmentation? -# ------------------------------- -# -# Active (online) defragmentation allows a Redis server to compact the -# spaces left between small allocations and deallocations of data in memory, -# thus allowing to reclaim back memory. -# -# Fragmentation is a natural process that happens with every allocator (but -# less so with Jemalloc, fortunately) and certain workloads. Normally a server -# restart is needed in order to lower the fragmentation, or at least to flush -# away all the data and create it again. However thanks to this feature -# implemented by Oran Agra for Redis 4.0 this process can happen at runtime -# in a "hot" way, while the server is running. -# -# Basically when the fragmentation is over a certain level (see the -# configuration options below) Redis will start to create new copies of the -# values in contiguous memory regions by exploiting certain specific Jemalloc -# features (in order to understand if an allocation is causing fragmentation -# and to allocate it in a better place), and at the same time, will release the -# old copies of the data. This process, repeated incrementally for all the keys -# will cause the fragmentation to drop back to normal values. -# -# Important things to understand: -# -# 1. This feature is disabled by default, and only works if you compiled Redis -# to use the copy of Jemalloc we ship with the source code of Redis. -# This is the default with Linux builds. -# -# 2. You never need to enable this feature if you don't have fragmentation -# issues. -# -# 3. Once you experience fragmentation, you can enable this feature when -# needed with the command "CONFIG SET activedefrag yes". -# -# The configuration parameters are able to fine tune the behavior of the -# defragmentation process. If you are not sure about what they mean it is -# a good idea to leave the defaults untouched. - -# Enabled active defragmentation -# activedefrag no - -# Minimum amount of fragmentation waste to start active defrag -# active-defrag-ignore-bytes 100mb - -# Minimum percentage of fragmentation to start active defrag -# active-defrag-threshold-lower 10 - -# Maximum percentage of fragmentation at which we use maximum effort -# active-defrag-threshold-upper 100 - -# Minimal effort for defrag in CPU percentage, to be used when the lower -# threshold is reached -# active-defrag-cycle-min 1 - -# Maximal effort for defrag in CPU percentage, to be used when the upper -# threshold is reached -# active-defrag-cycle-max 25 - -# Maximum number of set/hash/zset/list fields that will be processed from -# the main dictionary scan -# active-defrag-max-scan-fields 1000 - -# Jemalloc background thread for purging will be enabled by default -jemalloc-bg-thread yes - -# It is possible to pin different threads and processes of Redis to specific -# CPUs in your system, in order to maximize the performances of the server. -# This is useful both in order to pin different Redis threads in different -# CPUs, but also in order to make sure that multiple Redis instances running -# in the same host will be pinned to different CPUs. -# -# Normally you can do this using the "taskset" command, however it is also -# possible to this via Redis configuration directly, both in Linux and FreeBSD. -# -# You can pin the server/IO threads, bio threads, aof rewrite child process, and -# the bgsave child process. The syntax to specify the cpu list is the same as -# the taskset command: -# -# Set redis server/io threads to cpu affinity 0,2,4,6: -# server_cpulist 0-7:2 -# -# Set bio threads to cpu affinity 1,3: -# bio_cpulist 1,3 -# -# Set aof rewrite child process to cpu affinity 8,9,10,11: -# aof_rewrite_cpulist 8-11 -# -# Set bgsave child process to cpu affinity 1,10,11 -# bgsave_cpulist 1,10-11 - -# In some cases redis will emit warnings and even refuse to start if it detects -# that the system is in bad state, it is possible to suppress these warnings -# by setting the following config which takes a space delimited list of warnings -# to suppress -# -# ignore-warnings ARM64-COW-BUG diff --git a/ansible/roles/maat-redis/templates/service_override_slice.conf.j2 b/ansible/roles/maat-redis/templates/service_override_slice.conf.j2 deleted file mode 100644 index db248c50..00000000 --- a/ansible/roles/maat-redis/templates/service_override_slice.conf.j2 +++ /dev/null @@ -1,2 +0,0 @@ -[Service] -Slice=workload.slice \ No newline at end of file diff --git a/ansible/roles/system-init-7400-mcn0/files/setup b/ansible/roles/system-init-7400-mcn0/files/setup deleted file mode 100644 index 791a1724..00000000 --- a/ansible/roles/system-init-7400-mcn0/files/setup +++ /dev/null @@ -1,133 +0,0 @@ -#!/bin/bash -# set -x - -CURRENT_PATH=`dirname $0` -TP_SVR=192.168.100.5 -TP_PORT=10000 - -function get_netdev_by_pci() -{ - DEV_LIST=`ifconfig -a |grep flags |awk -F: '{print $1}'` - for i in ${DEV_LIST} - do - ethtool -i ${i} |grep bus-info |grep "$1" > /dev/null 2>&1 - if [ $? -eq 0 ];then - TARGET=${i} - break - fi - done - - echo ${TARGET} -} - -function pf_setup() -{ - echo 1 > /proc/sys/net/ipv6/conf/eth_pf/disable_ipv6 - ifconfig eth_pf up - - modprobe 8021q - vconfig add eth_pf 100 - vconfig set_flag eth_pf.100 1 1 - ifconfig eth_pf.100 192.168.100.1 netmask 255.255.255.0 up - sleep 1 -} - -function vf_setup() -{ - echo 8 > /sys/class/net/eth_pf/device/sriov_numvfs - sleep 5 - - ifconfig eth_ctl up - ifconfig eth_ctl mtu 2000 - ip link set eth_pf vf 2 vlan 200 - ifconfig eth_ctl 192.168.200.1 netmask 255.255.255.0 - - ifconfig eth_dign_s up - ifconfig eth_rsv up - ifconfig eth_ctl up - ifconfig eth_raw up - ifconfig eth_mcn1 up - ifconfig eth_mcn2 up - ifconfig eth_mcn3 up - ifconfig eth_dign_c up - - sleep 5 -} - -function bring_down_pfvf() -{ - echo 0 > /sys/class/net/eth_pf/device/sriov_numvfs - ifconfig eth_pf down - sleep 3 -} - - -# Main loop -while : -do - FAIL_FLAG=0 - - # Make sure PF is valid - ping ${TP_SVR} -c 1 - if [ $? -ne 0 ];then - echo "Please make sure switch board is up." - bring_down_pfvf - pf_setup - continue - fi - - # Make sure TestPoint is up. - echo "show version" | nc ${TP_SVR} ${TP_PORT} - if [ $? -ne 0 ];then - echo "Cannot reach TestPoint!" - echo "Please make sure TestPoint is up and in remote-listen mode." - sleep 5 - continue - fi - - # Create VFs and get MAC addresses - vf_setup - - PF=`get_netdev_by_pci 01:00.0` - VF1=`get_netdev_by_pci 01:00.1` - VF2=`get_netdev_by_pci 01:00.2` - VF3=`get_netdev_by_pci 01:00.3` - VF4=`get_netdev_by_pci 01:00.4` - VF5=`get_netdev_by_pci 01:00.5` - VF6=`get_netdev_by_pci 01:00.6` - VF7=`get_netdev_by_pci 01:00.7` - VF8=`get_netdev_by_pci 01:01.0` - - MAC1=`ifconfig ${VF1} |grep ether |awk -F' ' '{print $2}'` - MAC2=`ifconfig ${VF2} |grep ether |awk -F' ' '{print $2}'` - MAC3=`ifconfig ${VF3} |grep ether |awk -F' ' '{print $2}'` - MAC4=`ifconfig ${VF4} |grep ether |awk -F' ' '{print $2}'` - MAC5=`ifconfig ${VF5} |grep ether |awk -F' ' '{print $2}'` - MAC6=`ifconfig ${VF6} |grep ether |awk -F' ' '{print $2}'` - MAC7=`ifconfig ${VF7} |grep ether |awk -F' ' '{print $2}'` - MAC8=`ifconfig ${VF8} |grep ether |awk -F' ' '{print $2}'` - MAC9=`ifconfig ${PF} |grep ether |awk -F' ' '{print $2}'` - - # Make sure VFs are valid - MAC_TABLE=$(echo "show mac table all" | nc ${TP_SVR} ${TP_PORT}) - - for i in ${MAC1} ${MAC2} ${MAC3} ${MAC4} ${MAC5} ${MAC6} ${MAC7} ${MAC8} ${MAC9} - do - echo ${MAC_TABLE} |grep ${i} > /dev/null 2>&1 - if [ $? -ne 0 ];then - echo "MAC ${i} is not in table!" - FAIL_FLAG=1 - break - fi - done - - if [ ${FAIL_FLAG} -eq 1 ];then - bring_down_pfvf - continue - fi - - echo "PF/VF setup successful." - exit 0 -done - - diff --git a/ansible/roles/system-init-7400-mcn0/files/tsg-env.service b/ansible/roles/system-init-7400-mcn0/files/tsg-env.service deleted file mode 100644 index 26ef2746..00000000 --- a/ansible/roles/system-init-7400-mcn0/files/tsg-env.service +++ /dev/null @@ -1,15 +0,0 @@ -[Unit] -Description=tsg sled-mcn0 env init -Requires=network.target -After=network.target -Before=mrenv.service tsg-os-provision.service - -[Service] -ExecStart=/opt/tsg/env/setup -ExecStop=/opt/tsg/env/tsg-env_stop -Type=oneshot -RemainAfterExit=yes - -[Install] -WantedBy=multi-user.target -RequiredBy=mrenv.service diff --git a/ansible/roles/system-init-7400-mcn0/files/tsg-env_stop b/ansible/roles/system-init-7400-mcn0/files/tsg-env_stop deleted file mode 100644 index a378ea61..00000000 --- a/ansible/roles/system-init-7400-mcn0/files/tsg-env_stop +++ /dev/null @@ -1,6 +0,0 @@ -#!/bin/bash -# -echo 0 >/sys/class/net/eth_pf/device/sriov_numvfs -ifconfig eth_pf.100 down -vconfig rem eth_pf.100 -ifconfig eth_pf down diff --git a/ansible/roles/system-init-7400-mcn0/tasks/main.yml b/ansible/roles/system-init-7400-mcn0/tasks/main.yml deleted file mode 100644 index 9dc979f5..00000000 --- a/ansible/roles/system-init-7400-mcn0/tasks/main.yml +++ /dev/null @@ -1,130 +0,0 @@ ---- -- name: "set 60-7400MCN0P01R01.rules" - template: - src: "{{ role_path }}/templates/60-7400MCN0P01R01.rules.j2" - dest: /usr/lib/udev/rules.d/60-7400MCN0P01R01.rules - mode: 0644 - tags: template - -- name: "disable NetworkManager" - systemd: - name: NetworkManager.service - enabled: no - -- name: "set 90-7400-dracut.rules" - template: - src: "{{ role_path }}/templates/90-7400-dracut.rules.j2" - dest: /usr/lib/dracut/dracut.conf.d/90-7400-dracut.conf - mode: 0644 - tags: template - -- name: "update depmod" - shell: depmod -v 5.4.159-1.el7.elrepo.x86_64 - -- name: "set eth_pf" - template: - src: "{{ role_path }}/templates/ifcfg-eth_pf.j2" - dest: /etc/sysconfig/network-scripts/ifcfg-eth_pf - tags: template - -- name: "copy setup script" - copy: - src: "{{ role_path }}/files/setup" - dest: "/opt/tsg/env/" - mode: 0755 - -- name: "copy tsg-env.service" - copy: - src: "{{ role_path }}/files/tsg-env.service" - dest: "/usr/lib/systemd/system/" - mode: 0644 - -- name: "copy tsg-env_stop" - copy: - src: "{{ role_path }}/files/tsg-env_stop" - dest: "/opt/tsg/env/" - mode: 0755 - -- name: "enable tsg-env" - systemd: - name: tsg-env - enabled: yes - -# 禁用 IPMI -- name: "disable ipmi" - systemd: - name: ipmi - enabled: no - -# 禁用 Watchdog -- name: "disable watchdog" - systemd: - name: watchdog - enabled: no - -# systemctl set-property user.slice CPUShares=1500 MemoryLimit=13G -# systemctl set-property system.slice CPUShares=1000 MemoryLimit=13G -# systemctl set-property workload.slice CPUShares=7500 MemoryLimit=99G - -# workload.slice -- name: "Create /usr/lib/systemd/system/workload.slice.d/ directory if it does not exist" - file: - path: "{{ item }}" - state: directory - mode: '0755' - with_items: - - /usr/lib/systemd/system/workload.slice.d/ - -- name: "copy 50-CPUShares.conf to workload.slice.d" - copy: - src: "{{ role_path }}/templates/override_workload_slice_cpu.conf.j2" - dest: /usr/lib/systemd/system/workload.slice.d/50-CPUShares.conf - mode: 0644 - -- name: "copy 50-MemoryLimit.conf to workload.slice.d" - copy: - src: "{{ role_path }}/templates/override_workload_slice_mem.conf.j2" - dest: /usr/lib/systemd/system/workload.slice.d/50-MemoryLimit.conf - mode: 0644 - -# user.slice -- name: "Create /usr/lib/systemd/system/user.slice.d/ directory if it does not exist" - file: - path: "{{ item }}" - state: directory - mode: '0755' - with_items: - - /usr/lib/systemd/system/user.slice.d/ - -- name: "copy 50-CPUShares.conf to user.slice.d" - copy: - src: "{{ role_path }}/templates/override_user_slice_cpu.conf.j2" - dest: /usr/lib/systemd/system/user.slice.d/50-CPUShares.conf - mode: 0644 - -- name: "copy 50-MemoryLimit.conf to user.slice.d" - copy: - src: "{{ role_path }}/templates/override_user_slice_mem.conf.j2" - dest: /usr/lib/systemd/system/user.slice.d/50-MemoryLimit.conf - mode: 0644 - -# system.slice -- name: "Create /usr/lib/systemd/system/system.slice.d/ directory if it does not exist" - file: - path: "{{ item }}" - state: directory - mode: '0755' - with_items: - - /usr/lib/systemd/system/system.slice.d/ - -- name: "copy 50-CPUShares.conf to system.slice.d" - copy: - src: "{{ role_path }}/templates/override_system_slice_cpu.conf.j2" - dest: /usr/lib/systemd/system/system.slice.d/50-CPUShares.conf - mode: 0644 - -- name: "copy 50-MemoryLimit.conf to system.slice.d" - copy: - src: "{{ role_path }}/templates/override_system_slice_mem.conf.j2" - dest: /usr/lib/systemd/system/system.slice.d/50-MemoryLimit.conf - mode: 0644 diff --git a/ansible/roles/system-init-7400-mcn0/templates/60-7400MCN0P01R01.rules.j2 b/ansible/roles/system-init-7400-mcn0/templates/60-7400MCN0P01R01.rules.j2 deleted file mode 100644 index 52aa1f4c..00000000 --- a/ansible/roles/system-init-7400-mcn0/templates/60-7400MCN0P01R01.rules.j2 +++ /dev/null @@ -1,26 +0,0 @@ -# rename ens1 to eth_pf -ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:01:00.0", NAME:="eth_pf" - -# rename ens1s1 to eth_dign_c -ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:01:01.0", NAME:="eth_dign_c" - -# rename ens1f1 to eth_dign_s -ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:01:00.1", NAME:="eth_dign_s" - -# rename ens1f2 to eth_rsv -ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:01:00.2", NAME:="eth_rsv" - -# rename ens1f3 to eth_ctl -ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:01:00.3", NAME:="eth_ctl" - -# rename ens1f4 to eth_raw -ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:01:00.4", NAME:="eth_raw" - -# rename ens1f5 to eth_mcn1 -ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:01:00.5", NAME:="eth_mcn1" - -# rename ens1f6 to eth_mcn2 -ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:01:00.6", NAME:="eth_mcn2" - -# rename ens1f7 to eth_mcn3 -ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:01:00.7", NAME:="eth_mcn3" \ No newline at end of file diff --git a/ansible/roles/system-init-7400-mcn0/templates/90-7400-dracut.rules.j2 b/ansible/roles/system-init-7400-mcn0/templates/90-7400-dracut.rules.j2 deleted file mode 100644 index c5089e3b..00000000 --- a/ansible/roles/system-init-7400-mcn0/templates/90-7400-dracut.rules.j2 +++ /dev/null @@ -1 +0,0 @@ -omit_dracutmodules+="ifcfg network" diff --git a/ansible/roles/system-init-7400-mcn0/templates/ifcfg-eth_pf.j2 b/ansible/roles/system-init-7400-mcn0/templates/ifcfg-eth_pf.j2 deleted file mode 100644 index c49e7e63..00000000 --- a/ansible/roles/system-init-7400-mcn0/templates/ifcfg-eth_pf.j2 +++ /dev/null @@ -1,15 +0,0 @@ -TYPE=Ethernet -PROXY_METHOD=none -BROWSER_ONLY=no -BOOTPROTO=static -DEFROUTE=yes -IPV4_FAILURE_FATAL=no -IPV6INIT=yes -IPV6_AUTOCONF=yes -IPV6_DEFROUTE=yes -IPV6_FAILURE_FATAL=no -IPV6_ADDR_GEN_MODE=stable-privacy -NAME=eth_pf -#UUID=2af69d2b-6746-489f-9e05-97a8b25e259b -DEVICE=eth_pf -ONBOOT=yes diff --git a/ansible/roles/system-init-7400-mcn0/templates/override_system_slice_cpu.conf.j2 b/ansible/roles/system-init-7400-mcn0/templates/override_system_slice_cpu.conf.j2 deleted file mode 100644 index f28071c2..00000000 --- a/ansible/roles/system-init-7400-mcn0/templates/override_system_slice_cpu.conf.j2 +++ /dev/null @@ -1,2 +0,0 @@ -[Slice] -CPUShares=1000 diff --git a/ansible/roles/system-init-7400-mcn0/templates/override_system_slice_mem.conf.j2 b/ansible/roles/system-init-7400-mcn0/templates/override_system_slice_mem.conf.j2 deleted file mode 100644 index 38c3bf72..00000000 --- a/ansible/roles/system-init-7400-mcn0/templates/override_system_slice_mem.conf.j2 +++ /dev/null @@ -1,2 +0,0 @@ -[Slice] -MemoryLimit=13G diff --git a/ansible/roles/system-init-7400-mcn0/templates/override_user_slice_cpu.conf.j2 b/ansible/roles/system-init-7400-mcn0/templates/override_user_slice_cpu.conf.j2 deleted file mode 100644 index bca6bd76..00000000 --- a/ansible/roles/system-init-7400-mcn0/templates/override_user_slice_cpu.conf.j2 +++ /dev/null @@ -1,2 +0,0 @@ -[Slice] -CPUShares=1500 diff --git a/ansible/roles/system-init-7400-mcn0/templates/override_user_slice_mem.conf.j2 b/ansible/roles/system-init-7400-mcn0/templates/override_user_slice_mem.conf.j2 deleted file mode 100644 index 38c3bf72..00000000 --- a/ansible/roles/system-init-7400-mcn0/templates/override_user_slice_mem.conf.j2 +++ /dev/null @@ -1,2 +0,0 @@ -[Slice] -MemoryLimit=13G diff --git a/ansible/roles/system-init-7400-mcn0/templates/override_workload_slice_cpu.conf.j2 b/ansible/roles/system-init-7400-mcn0/templates/override_workload_slice_cpu.conf.j2 deleted file mode 100644 index 0ad6b44b..00000000 --- a/ansible/roles/system-init-7400-mcn0/templates/override_workload_slice_cpu.conf.j2 +++ /dev/null @@ -1,2 +0,0 @@ -[Slice] -CPUShares=7500 diff --git a/ansible/roles/system-init-7400-mcn0/templates/override_workload_slice_mem.conf.j2 b/ansible/roles/system-init-7400-mcn0/templates/override_workload_slice_mem.conf.j2 deleted file mode 100644 index ae1dd0e7..00000000 --- a/ansible/roles/system-init-7400-mcn0/templates/override_workload_slice_mem.conf.j2 +++ /dev/null @@ -1,2 +0,0 @@ -[Slice] -MemoryLimit=99G diff --git a/ansible/roles/system-init-7400-mcn123/files/setup b/ansible/roles/system-init-7400-mcn123/files/setup deleted file mode 100644 index 0efd8463..00000000 --- a/ansible/roles/system-init-7400-mcn123/files/setup +++ /dev/null @@ -1,140 +0,0 @@ -#!/bin/bash -# set -x - -CURRENT_PATH=`dirname $0` -TP_SVR=192.168.100.5 -TP_PORT=10000 -modprobe 8021q - -function get_netdev_by_pci() -{ - DEV_LIST=`ifconfig -a |grep flags |awk -F: '{print $1}'` - for i in ${DEV_LIST} - do - ethtool -i ${i} |grep bus-info |grep -E "$1" > /dev/null 2>&1 - if [ $? -eq 0 ];then - TARGET=${i} - break - fi - done - - echo ${TARGET} -} - -function pf_setup() -{ - echo 1 > /proc/sys/net/ipv6/conf/eth_pf/disable_ipv6 - ifconfig eth_pf up - vconfig add eth_pf 100 - vconfig set_flag eth_pf.100 1 1 - ifconfig eth_pf.100 192.168.100.$1 netmask 255.255.255.0 up - sleep 1 -} - -function vf_setup() -{ - echo 4 > /sys/class/net/eth_pf/device/sriov_numvfs - sleep 5 - - ifconfig eth_ctl up - ip link set eth_pf vf 2 vlan 200 - ifconfig eth_ctl 192.168.200.$1 netmask 255.255.255.0 - - ifconfig eth_pxy up - ifconfig eth_mirr_d up - ifconfig eth_ctl up - ifconfig eth_rsv up - sleep 5 -} - -function bring_down_pfvf() -{ - echo 0 > /sys/class/net/eth_pf/device/sriov_numvfs - ifconfig eth_pf down - sleep 3 -} - -# Main loop -while : -do - FAIL_FLAG=0 - # 1:mcn0; 2:mcn1; 3:mcn2; 4:mcn3 - mcn_mgnt_id=0 - - card_info=$(ipmitool raw 0x2e 0x32 0x13 0x5f 0x00 | awk '{print $NF}') - case ${card_info} in - 90) - # mcn0 - mcn_mgnt_id=1 - ;; - 80) - # mcn1 - mcn_mgnt_id=2 - ;; - 98) - # mcn2 - mcn_mgnt_id=3 - ;; - 88) - # mcn3 - mcn_mgnt_id=4 - ;; - *) - echo "ipmitool get unknown card id" - ;; - esac - - # Make sure PF is valid - ping ${TP_SVR} -c 1 - if [ $? -ne 0 ];then - echo "Please make sure switch board is up." - bring_down_pfvf - pf_setup ${mcn_mgnt_id} - continue - fi - - # Make sure TestPoint is up. - echo "show version" | nc ${TP_SVR} ${TP_PORT} - if [ $? -ne 0 ];then - echo "Cannot reach TestPoint!" - echo "Please make sure TestPoint is up and in remote-listen mode." - sleep 5 - continue - fi - - # Create VFs and get MAC addresses - vf_setup ${mcn_mgnt_id} - - PF=`get_netdev_by_pci "01:00.0|85:00.0"` - VF1=`get_netdev_by_pci "01:00.1|85:00.1"` - VF2=`get_netdev_by_pci "01:00.2|85:00.2"` - VF3=`get_netdev_by_pci "01:00.3|85:00.3"` - VF4=`get_netdev_by_pci "01:00.4|85:00.4"` - - MAC0=`ifconfig ${PF} |grep ether |awk -F' ' '{print $2}'` - MAC1=`ifconfig ${VF1} |grep ether |awk -F' ' '{print $2}'` - MAC2=`ifconfig ${VF2} |grep ether |awk -F' ' '{print $2}'` - MAC3=`ifconfig ${VF3} |grep ether |awk -F' ' '{print $2}'` - MAC4=`ifconfig ${VF4} |grep ether |awk -F' ' '{print $2}'` - - # Make sure VFs are valid - MAC_TABLE=$(echo "show mac table all" | nc ${TP_SVR} ${TP_PORT}) - - for i in ${MAC0} ${MAC1} ${MAC2} ${MAC3} ${MAC4} - do - echo ${MAC_TABLE} |grep ${i} > /dev/null 2>&1 - if [ $? -ne 0 ];then - echo "MAC ${i} is not in table!" - FAIL_FLAG=1 - break - fi - done - - if [ ${FAIL_FLAG} -eq 1 ];then - bring_down_pfvf - continue - fi - - echo "PF/VF setup successful." - exit 0 -done diff --git a/ansible/roles/system-init-7400-mcn123/files/tsg-env.service b/ansible/roles/system-init-7400-mcn123/files/tsg-env.service deleted file mode 100644 index ae55686b..00000000 --- a/ansible/roles/system-init-7400-mcn123/files/tsg-env.service +++ /dev/null @@ -1,15 +0,0 @@ -[Unit] -Description=tsg sled-mcn1/2/3 env init -Requires=network.target -After=network.target -Before=tfe-env.service mrenv.service tsg-os-provision.service - -[Service] -ExecStart=/opt/tsg/env/setup -ExecStop=/opt/tsg/env/tsg-env_stop -Type=oneshot -RemainAfterExit=yes - -[Install] -WantedBy=multi-user.target -RequiredBy=tfe-env.service mrenv.service \ No newline at end of file diff --git a/ansible/roles/system-init-7400-mcn123/files/tsg-env_stop b/ansible/roles/system-init-7400-mcn123/files/tsg-env_stop deleted file mode 100644 index a378ea61..00000000 --- a/ansible/roles/system-init-7400-mcn123/files/tsg-env_stop +++ /dev/null @@ -1,6 +0,0 @@ -#!/bin/bash -# -echo 0 >/sys/class/net/eth_pf/device/sriov_numvfs -ifconfig eth_pf.100 down -vconfig rem eth_pf.100 -ifconfig eth_pf down diff --git a/ansible/roles/system-init-7400-mcn123/tasks/main.yml b/ansible/roles/system-init-7400-mcn123/tasks/main.yml deleted file mode 100644 index 94752c36..00000000 --- a/ansible/roles/system-init-7400-mcn123/tasks/main.yml +++ /dev/null @@ -1,130 +0,0 @@ ---- -- name: "set 60-7400MCN123P01R01.rules" - template: - src: "{{ role_path }}/templates/60-7400MCN123P01R01.rules.j2" - dest: /usr/lib/udev/rules.d/60-7400MCN123P01R01.rules - mode: 0644 - tags: template - -- name: "disable NetworkManager" - systemd: - name: NetworkManager.service - enabled: no - -- name: "set 90-7400-dracut.rules" - template: - src: "{{ role_path }}/templates/90-7400-dracut.rules.j2" - dest: /usr/lib/dracut/dracut.conf.d/90-7400-dracut.conf - mode: 0644 - tags: template - -- name: "update depmod" - shell: depmod -v 5.4.159-1.el7.elrepo.x86_64 - -- name: "set eth_pf" - template: - src: "{{ role_path }}/templates/ifcfg-eth_pf.j2" - dest: /etc/sysconfig/network-scripts/ifcfg-eth_pf - tags: template - -- name: "copy setup script" - copy: - src: "{{ role_path }}/files/setup" - dest: "/opt/tsg/env/" - mode: 0755 - -- name: "copy tsg-env.service" - copy: - src: "{{ role_path }}/files/tsg-env.service" - dest: "/usr/lib/systemd/system/" - mode: 0644 - -- name: "copy tsg-env_stop" - copy: - src: "{{ role_path }}/files/tsg-env_stop" - dest: "/opt/tsg/env/" - mode: 0755 - -- name: "enable tsg-env" - systemd: - name: tsg-env - enabled: yes - -# 禁用 IPMI -- name: "disable ipmi" - systemd: - name: ipmi - enabled: no - -# 禁用 Watchdog -- name: "disable watchdog" - systemd: - name: watchdog - enabled: no - -# systemctl set-property user.slice CPUShares=1500 MemoryLimit=13G -# systemctl set-property system.slice CPUShares=1000 MemoryLimit=13G -# systemctl set-property workload.slice CPUShares=7500 MemoryLimit=99G - -# workload.slice -- name: "Create /usr/lib/systemd/system/workload.slice.d/ directory if it does not exist" - file: - path: "{{ item }}" - state: directory - mode: '0755' - with_items: - - /usr/lib/systemd/system/workload.slice.d/ - -- name: "copy 50-CPUShares.conf to workload.slice.d" - copy: - src: "{{ role_path }}/templates/override_workload_slice_cpu.conf.j2" - dest: /usr/lib/systemd/system/workload.slice.d/50-CPUShares.conf - mode: 0644 - -- name: "copy 50-MemoryLimit.conf to workload.slice.d" - copy: - src: "{{ role_path }}/templates/override_workload_slice_mem.conf.j2" - dest: /usr/lib/systemd/system/workload.slice.d/50-MemoryLimit.conf - mode: 0644 - -# user.slice -- name: "Create /usr/lib/systemd/system/user.slice.d/ directory if it does not exist" - file: - path: "{{ item }}" - state: directory - mode: '0755' - with_items: - - /usr/lib/systemd/system/user.slice.d/ - -- name: "copy 50-CPUShares.conf to user.slice.d" - copy: - src: "{{ role_path }}/templates/override_user_slice_cpu.conf.j2" - dest: /usr/lib/systemd/system/user.slice.d/50-CPUShares.conf - mode: 0644 - -- name: "copy 50-MemoryLimit.conf to user.slice.d" - copy: - src: "{{ role_path }}/templates/override_user_slice_mem.conf.j2" - dest: /usr/lib/systemd/system/user.slice.d/50-MemoryLimit.conf - mode: 0644 - -# system.slice -- name: "Create /usr/lib/systemd/system/system.slice.d/ directory if it does not exist" - file: - path: "{{ item }}" - state: directory - mode: '0755' - with_items: - - /usr/lib/systemd/system/system.slice.d/ - -- name: "copy 50-CPUShares.conf to system.slice.d" - copy: - src: "{{ role_path }}/templates/override_system_slice_cpu.conf.j2" - dest: /usr/lib/systemd/system/system.slice.d/50-CPUShares.conf - mode: 0644 - -- name: "copy 50-MemoryLimit.conf to system.slice.d" - copy: - src: "{{ role_path }}/templates/override_system_slice_mem.conf.j2" - dest: /usr/lib/systemd/system/system.slice.d/50-MemoryLimit.conf - mode: 0644 \ No newline at end of file diff --git a/ansible/roles/system-init-7400-mcn123/templates/60-7400MCN123P01R01.rules.j2 b/ansible/roles/system-init-7400-mcn123/templates/60-7400MCN123P01R01.rules.j2 deleted file mode 100644 index db9833a5..00000000 --- a/ansible/roles/system-init-7400-mcn123/templates/60-7400MCN123P01R01.rules.j2 +++ /dev/null @@ -1,19 +0,0 @@ -# rename ens1/ens8 to eth_pf -ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:01:00.0", NAME:="eth_pf" -ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:85:00.0", NAME:="eth_pf" - -# rename ens1f1/ens8f1 to eth_pxy -ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:01:00.1", NAME:="eth_pxy" -ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:85:00.1", NAME:="eth_pxy" - -# rename ens1f2/ens8f2 to eth_mirr_d -ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:01:00.2", NAME:="eth_mirr_d" -ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:85:00.2", NAME:="eth_mirr_d" - -# rename ens1f3/ens8f3 to eth_ctl -ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:01:00.3", NAME:="eth_ctl" -ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:85:00.3", NAME:="eth_ctl" - -# rename ens1f4/ens8f4 to eth_rsv -ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:01:00.4", NAME:="eth_rsv" -ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:85:00.4", NAME:="eth_rsv" \ No newline at end of file diff --git a/ansible/roles/system-init-7400-mcn123/templates/90-7400-dracut.rules.j2 b/ansible/roles/system-init-7400-mcn123/templates/90-7400-dracut.rules.j2 deleted file mode 100644 index c5089e3b..00000000 --- a/ansible/roles/system-init-7400-mcn123/templates/90-7400-dracut.rules.j2 +++ /dev/null @@ -1 +0,0 @@ -omit_dracutmodules+="ifcfg network" diff --git a/ansible/roles/system-init-7400-mcn123/templates/ifcfg-eth_pf.j2 b/ansible/roles/system-init-7400-mcn123/templates/ifcfg-eth_pf.j2 deleted file mode 100644 index c49e7e63..00000000 --- a/ansible/roles/system-init-7400-mcn123/templates/ifcfg-eth_pf.j2 +++ /dev/null @@ -1,15 +0,0 @@ -TYPE=Ethernet -PROXY_METHOD=none -BROWSER_ONLY=no -BOOTPROTO=static -DEFROUTE=yes -IPV4_FAILURE_FATAL=no -IPV6INIT=yes -IPV6_AUTOCONF=yes -IPV6_DEFROUTE=yes -IPV6_FAILURE_FATAL=no -IPV6_ADDR_GEN_MODE=stable-privacy -NAME=eth_pf -#UUID=2af69d2b-6746-489f-9e05-97a8b25e259b -DEVICE=eth_pf -ONBOOT=yes diff --git a/ansible/roles/system-init-7400-mcn123/templates/override_system_slice_cpu.conf.j2 b/ansible/roles/system-init-7400-mcn123/templates/override_system_slice_cpu.conf.j2 deleted file mode 100644 index f28071c2..00000000 --- a/ansible/roles/system-init-7400-mcn123/templates/override_system_slice_cpu.conf.j2 +++ /dev/null @@ -1,2 +0,0 @@ -[Slice] -CPUShares=1000 diff --git a/ansible/roles/system-init-7400-mcn123/templates/override_system_slice_mem.conf.j2 b/ansible/roles/system-init-7400-mcn123/templates/override_system_slice_mem.conf.j2 deleted file mode 100644 index 38c3bf72..00000000 --- a/ansible/roles/system-init-7400-mcn123/templates/override_system_slice_mem.conf.j2 +++ /dev/null @@ -1,2 +0,0 @@ -[Slice] -MemoryLimit=13G diff --git a/ansible/roles/system-init-7400-mcn123/templates/override_user_slice_cpu.conf.j2 b/ansible/roles/system-init-7400-mcn123/templates/override_user_slice_cpu.conf.j2 deleted file mode 100644 index bca6bd76..00000000 --- a/ansible/roles/system-init-7400-mcn123/templates/override_user_slice_cpu.conf.j2 +++ /dev/null @@ -1,2 +0,0 @@ -[Slice] -CPUShares=1500 diff --git a/ansible/roles/system-init-7400-mcn123/templates/override_user_slice_mem.conf.j2 b/ansible/roles/system-init-7400-mcn123/templates/override_user_slice_mem.conf.j2 deleted file mode 100644 index 38c3bf72..00000000 --- a/ansible/roles/system-init-7400-mcn123/templates/override_user_slice_mem.conf.j2 +++ /dev/null @@ -1,2 +0,0 @@ -[Slice] -MemoryLimit=13G diff --git a/ansible/roles/system-init-7400-mcn123/templates/override_workload_slice_cpu.conf.j2 b/ansible/roles/system-init-7400-mcn123/templates/override_workload_slice_cpu.conf.j2 deleted file mode 100644 index 0ad6b44b..00000000 --- a/ansible/roles/system-init-7400-mcn123/templates/override_workload_slice_cpu.conf.j2 +++ /dev/null @@ -1,2 +0,0 @@ -[Slice] -CPUShares=7500 diff --git a/ansible/roles/system-init-7400-mcn123/templates/override_workload_slice_mem.conf.j2 b/ansible/roles/system-init-7400-mcn123/templates/override_workload_slice_mem.conf.j2 deleted file mode 100644 index ae1dd0e7..00000000 --- a/ansible/roles/system-init-7400-mcn123/templates/override_workload_slice_mem.conf.j2 +++ /dev/null @@ -1,2 +0,0 @@ -[Slice] -MemoryLimit=99G diff --git a/ansible/roles/telegraf/files/telegraf-1.30.2-1.x86_64.rpm b/ansible/roles/telegraf/files/telegraf-1.30.2-1.x86_64.rpm deleted file mode 100644 index 70182d62..00000000 Binary files a/ansible/roles/telegraf/files/telegraf-1.30.2-1.x86_64.rpm and /dev/null differ diff --git a/ansible/roles/telegraf/files/telegraf_proxy.service b/ansible/roles/telegraf/files/telegraf_proxy.service deleted file mode 100644 index 62a7d4f2..00000000 --- a/ansible/roles/telegraf/files/telegraf_proxy.service +++ /dev/null @@ -1,16 +0,0 @@ -[Unit] -Description=Security information -Documentation=https://github.com/influxdata/telegraf -After=network.target - -[Service] -EnvironmentFile=-/etc/default/telegraf -User=telegraf -ExecStart=/usr/bin/telegraf -config /etc/telegraf/telegraf_proxy.conf -config-directory /etc/telegraf/telegraf_statistic.d $TELEGRAF_OPTS -ExecReload=/bin/kill -HUP $MAINPID -Restart=on-failure -RestartForceExitStatus=SIGPIPE -KillMode=control-group - -[Install] -WantedBy=multi-user.target diff --git a/ansible/roles/telegraf/tasks/main.yml b/ansible/roles/telegraf/tasks/main.yml deleted file mode 100644 index 2e29f80b..00000000 --- a/ansible/roles/telegraf/tasks/main.yml +++ /dev/null @@ -1,66 +0,0 @@ -- name: "copy telegraf.rpm to destination server" - copy: - src: "{{ role_path }}/files/telegraf-1.30.2-1.x86_64.rpm" - dest: /tmp - -- name: "install telegraf" - yum: - name: - - /tmp/telegraf-1.30.2-1.x86_64.rpm - state: present - disable_gpg_check: yes - -- name: "Templates telegraf_proxy.conf" - template: - src: "{{role_path}}/templates/telegraf_proxy.conf.j2.j2" - dest: /opt/tsg/tsg-os-provision/templates/telegraf_proxy.conf.j2 - tags: template - when: runtime_env == 'TSG-7400-mcn0' or runtime_env == 'TSG-7400-mcn123' - -- name: "copy telegraf_proxy.service to destination server" - copy: - src: "{{ role_path }}/files/telegraf_proxy.service" - dest: /usr/lib/systemd/system - mode: 0644 - when: runtime_env == 'TSG-7400-mcn0' or runtime_env == 'TSG-7400-mcn123' - -- name: "Create service override dictionary" - file: - path: "{{ item }}" - state: directory - mode: '0755' - with_items: - - /usr/lib/systemd/system/telegraf_proxy.service.d - when: runtime_env == 'TSG-7400-mcn0' or runtime_env == 'TSG-7400-mcn123' - -- name: "Copy slice override file to dest" - copy: - src: "{{ role_path }}/templates/service_override_slice.conf.j2" - dest: "{{ item }}" - mode: 0644 - with_items: - - /usr/lib/systemd/system/telegraf_proxy.service.d/service_override_slice.conf - when: runtime_env == 'TSG-7400-mcn0' or runtime_env == 'TSG-7400-mcn123' - -- name: "Change service WantedBy target" - replace: - path: "{{ item }}" - regexp: 'WantedBy=multi-user.target' - replace: 'WantedBy=workload.target' - with_items: - - /usr/lib/systemd/system/telegraf_proxy.service - when: runtime_env == 'TSG-7400-mcn0' or runtime_env == 'TSG-7400-mcn123' - -##################### telegraf ##################### - -- name: "disable telegraf" - systemd: - name: telegraf.service - enabled: no - when: runtime_env == 'TSG-7400-mcn0' or runtime_env == 'TSG-7400-mcn123' - -- name: "Start telegraf_proxy" - systemd: - name: telegraf_proxy.service - enabled: yes - when: runtime_env == 'TSG-7400-mcn0' or runtime_env == 'TSG-7400-mcn123' \ No newline at end of file diff --git a/ansible/roles/telegraf/templates/service_override_slice.conf.j2 b/ansible/roles/telegraf/templates/service_override_slice.conf.j2 deleted file mode 100644 index db248c50..00000000 --- a/ansible/roles/telegraf/templates/service_override_slice.conf.j2 +++ /dev/null @@ -1,2 +0,0 @@ -[Service] -Slice=workload.slice \ No newline at end of file diff --git a/ansible/roles/telegraf/templates/telegraf_proxy.conf.j2.j2 b/ansible/roles/telegraf/templates/telegraf_proxy.conf.j2.j2 deleted file mode 100644 index 5bbeb917..00000000 --- a/ansible/roles/telegraf/templates/telegraf_proxy.conf.j2.j2 +++ /dev/null @@ -1,75 +0,0 @@ -[global_tags] - device_id = "${device_id}" -{% raw %}{% if data_center.name is defined %} - data_center = "{{ data_center.name }}" -{% endif %} -{% if device.tags is defined %} -{% for device_tag in device.tags %} -{% for key,value in device_tag.items() %} - {{ key }} = "{{value}}" -{% endfor %} -{% endfor %} -{% endif %} -{% endraw %} - -[agent] - interval = "1s" - round_interval = true - metric_batch_size = 1000 - metric_buffer_limit = 100000 - collection_jitter = "0s" - flush_interval = "1s" - flush_jitter = "0s" - precision = "" - debug = false - quiet = false - logfile = "" - hostname = "" - omit_hostname = true - -[[outputs.kafka]] - sasl_username = "admin" - sasl_password = "galaxy2019" -{% raw %} brokers = [ "{{ olap.kafka_broker.address_list | join("\",\"") }}" ] -{% endraw %} - topic = "POLICY-RULE-METRIC" - client_id = "POLICY-RULE-METRIC" - data_format = "json" - json_timestamp_units = "1ms" - json_transformation = ''' - $merge([$, { "timestamp_ms": timestamp}]) ~> |$|{}, ['timestamp']| - ''' - -[[inputs.socket_listener]] - service_address = "udp://:8900" - data_format = "influx" - read_buffer_size = "32MiB" -[[processors.rename]] - [[processors.rename.replace]] - field = "hit_count_sum" - dest = "hit_count" - - [[processors.rename.replace]] - field = "in_bytes_sum" - dest = "in_bytes" - - [[processors.rename.replace]] - field = "out_bytes_sum" - dest = "out_bytes" - - [[processors.rename.replace]] - field = "in_pkts_sum" - dest = "in_pkts" - - [[processors.rename.replace]] - field = "out_pkts_sum" - dest = "out_pkts" - -[[aggregators.basicstats]] - period = "1s" - delay = "1s" - grace = "1s" - drop_original = true - stats = ["sum"] - fieldpass = ["hit_count", "in_bytes", "out_bytes", "in_pkts", "out_pkts"] - namepass = ["proxy_rule_hits"] # only "pass" swap metrics through the aggregator. diff --git a/ansible/roles/tsg-os-provision/files/config_sample/provision.default.yml.7400MCN0P01R01 b/ansible/roles/tsg-os-provision/files/config_sample/provision.default.yml.7400MCN0P01R01 deleted file mode 100644 index 37c21529..00000000 --- a/ansible/roles/tsg-os-provision/files/config_sample/provision.default.yml.7400MCN0P01R01 +++ /dev/null @@ -1,79 +0,0 @@ -feature: - enable_policy_local_cache: 1 - enable_stream_bypass_under_ddos: 0 - -firewall: - enable: 1 - enable_dtls: 1 - enable_sip: 1 - -proxy: - enable: 1 - -sessionrecord: - enable: 1 - enable_dns_record: 1 - enable_rtp_record: 1 - enable_interim_record: 1 - enable_transcation_record: 1 - enable_contains_app_id: 0 - enable_contains_dns_resource_record: 0 - -capturepacket: - enable: 1 - -app_behavior: - enable: 0 - -ddossketch: - enable: 1 - tcp_flood_report_thresh: 0.0008 - udp_flood_report_thresh: 0.0008 - icmp_flood_report_thresh: 0.0008 - dns_flood_report_thresh: 0.0008 - -app: - identify_by: - user_defined_signature: 1 - builtin_app_engine: 1 - -coredump: - format: none - collect: local - sentry_url: http://127.0.0.1:9000/api/2/minidump/ - -advanced_settings: - stream_tcp_max: 50000 - stream_tcp_timeout: 30 - stream_udp_max: 50000 - stream_udp_timeout: 60 - stream_bypass_trigger_cpu_usage: 90 - -cm: - policy_server: - port_num: 1 - db_static: 0 - db_dynamic: 1 - -#####session_distribution_policy.hash_key in [outer-most-sip-dip,outer-most-sip-dip-sport-dport,inner-most-sip-dip,inner-most-sip-dip-sport-dport] -session_distribution_policy: - mode: sym-hash - hash_key: inner-most-sip-dip - -olap: - hos_server: - token: "c21f969b5f03d33d43e04f8f136e7682" - -vsys_id: 1 - -consul_agent: - mode: "server" - encrypt: "XN0I7fHIY1+yLWm2PjegZ7U93nI/tmzNvtmBtZLuIfo=" - datacenter: "dc1" - node_name: "" - -shaping: - enable: 0 - -sid: - shaping: 1000 \ No newline at end of file diff --git a/ansible/roles/tsg-os-provision/files/config_sample/provision.default.yml.7400MCN123P01R01 b/ansible/roles/tsg-os-provision/files/config_sample/provision.default.yml.7400MCN123P01R01 deleted file mode 100644 index c499bbb0..00000000 --- a/ansible/roles/tsg-os-provision/files/config_sample/provision.default.yml.7400MCN123P01R01 +++ /dev/null @@ -1,19 +0,0 @@ -feature: - enable_policy_local_cache: 1 - -coredump: - format: none - collect: local - sentry_url: http://127.0.0.1:9000/api/2/minidump/ - -cm: - policy_server: - port_num: 1 - db_static: 0 - db_dynamic: 1 - -olap: - hos_server: - token: "c21f969b5f03d33d43e04f8f136e7682" - -vsys_id: 1 \ No newline at end of file diff --git a/ansible/roles/tsg-os-provision/files/config_sample/provision.yml.sample.7400MCN0P01R01 b/ansible/roles/tsg-os-provision/files/config_sample/provision.yml.sample.7400MCN0P01R01 deleted file mode 100644 index 40705f7b..00000000 --- a/ansible/roles/tsg-os-provision/files/config_sample/provision.yml.sample.7400MCN0P01R01 +++ /dev/null @@ -1,112 +0,0 @@ -version: 1 - -device: - tags: - - key1: value1 - - key2: value2 - -session_id_generator: - snowflake_worker_id_base: 1 - snowflake_worker_id_offset: 1 - -feature: - enable_policy_local_cache: 1 - enable_stream_bypass_under_ddos: 0 - -firewall: - enable: 0/1 - -proxy: - enable: 0/1 - -sessionrecord: - enable: 0/1 - enable_dns_record: 0/1 - enable_rtp_record: 0/1 - enable_interim_record: 0/1 - enable_transcation_record: 0/1 - -capturepacket: - enable: 0/1 - -ddossketch: - enable: 0/1 - - -app: - identify_by: - user_defined_signature: 0/1 - builtin_app_engine: 0/1 - -cm: - policy_server: - address: "127.0.0.1" - port: 7002 - -olap: - kafka_broker: - address_list: ['1.1.1.1:9092','2.2.2.2:9092'] - hos_server: - address: "127.0.0.1" - port: 9098 - token: "xxxxxxxxxx" - -# npb_device value in [inline_device, tera,direct] -npb_device: inline_device - -tera_steering_group: - - internal: - vlan_id: 1301 - keepalive: - ipv4: 127.0.0.1/24 - ipv6: 'fe80\:\:1/64' - external: - vlan_id: 1302 - keepalive: - ipv4: 127.0.0.1/24 - ipv6: 'fe80\:\:2/64' - - internal: - vlan_id: 1201 - keepalive: - ipv4: 127.0.0.1/24 - ipv6: 'fe80\:\:3/64' - external: - vlan_id: 1202 - keepalive: - ipv4: 127.0.0.1/24 - ipv6: 'fe80\:\:4/64' - -inline_device_settings: - keepalive: - ip: 127.0.0.1 - mask: 255.255.255.0 - -network_setting: - nic_policy_log: - ipv4: 127.0.0.1/24 - gateway_ipv4: 192.168.1.1 - -coredump: - format: minidump/core/none - collect: local/sentry - sentry_url: http://127.0.0.1:9000/api/2/minidump/?sentry_key=3203b43fd5384a7dbe6a48ecb1f3c595 - -vsys_id: 1 - -consul_agent: - mode: client/server - #encrypt: "" - bootstrapExpect: 1 - #node_name: "" - #datacenter: "dc1" - join: - - address: 111.111.111.111 - port: 8301 - - address: 222.222.222.222 - port: 8301 - -shaping: - enable: 1 - -sid: - shaping: 1000 diff --git a/ansible/roles/tsg-os-provision/files/config_sample/provision.yml.sample.7400MCN123P01R01 b/ansible/roles/tsg-os-provision/files/config_sample/provision.yml.sample.7400MCN123P01R01 deleted file mode 100644 index 9b048a4d..00000000 --- a/ansible/roles/tsg-os-provision/files/config_sample/provision.yml.sample.7400MCN123P01R01 +++ /dev/null @@ -1,34 +0,0 @@ -version: 1 - -device: - tags: - - key1: value1 - - key2: value2 - -feature: - enable_policy_local_cache: 1 - -cm: - policy_server: - address: "127.0.0.1" - port: 7002 - -olap: - kafka_broker: - address_list: ['1.1.1.1:9092','2.2.2.2:9092'] - hos_server: - address: "127.0.0.1" - port: 9098 - token: "xxxxxxxxxx" - -network_setting: - nic_policy_log: - ipv4: 127.0.0.1/24 - gateway_ipv4: 192.168.1.1 - -coredump: - format: minidump/core/none - collect: local/sentry - sentry_url: http://127.0.0.1:9000/api/2/minidump/?sentry_key=3203b43fd5384a7dbe6a48ecb1f3c595 - -vsys_id: 1 diff --git a/ansible/roles/tsg-os-provision/files/hosts b/ansible/roles/tsg-os-provision/files/hosts deleted file mode 100644 index 71c3838e..00000000 --- a/ansible/roles/tsg-os-provision/files/hosts +++ /dev/null @@ -1,2 +0,0 @@ -[provision] -localhost ansible_connection=local \ No newline at end of file diff --git a/ansible/roles/tsg-os-provision/files/network_settings/adapt_tera_network_setting.sh.j2 b/ansible/roles/tsg-os-provision/files/network_settings/adapt_tera_network_setting.sh.j2 deleted file mode 100644 index bab66f3b..00000000 --- a/ansible/roles/tsg-os-provision/files/network_settings/adapt_tera_network_setting.sh.j2 +++ /dev/null @@ -1,11 +0,0 @@ -#!/bin/bash -ex -{% for zone_group in tera_steering_group %} -ip link add link eth_rsv name eth_rsv.{{ zone_group.internal.vlan_id }} type vlan id {{ zone_group.internal.vlan_id }} -ip addr add {{ zone_group.internal.keepalive.ipv4 }} dev eth_rsv.{{ zone_group.internal.vlan_id }} -ip -6 addr add {{ zone_group.internal.keepalive.ipv6 }} dev eth_rsv.{{ zone_group.internal.vlan_id }} -ifconfig eth_rsv.{{ zone_group.internal.vlan_id }} up -ip link add link eth_rsv name eth_rsv.{{ zone_group.external.vlan_id }} type vlan id {{ zone_group.external.vlan_id }} -ip addr add {{ zone_group.external.keepalive.ipv4 }} dev eth_rsv.{{ zone_group.external.vlan_id }} -ip -6 addr add {{ zone_group.external.keepalive.ipv6 }} dev eth_rsv.{{ zone_group.external.vlan_id }} -ifconfig eth_rsv.{{ zone_group.external.vlan_id }} up -{% endfor %} \ No newline at end of file diff --git a/ansible/roles/tsg-os-provision/files/network_settings/setup_policy_log_nic_network.sh.j2 b/ansible/roles/tsg-os-provision/files/network_settings/setup_policy_log_nic_network.sh.j2 deleted file mode 100644 index d44ffd75..00000000 --- a/ansible/roles/tsg-os-provision/files/network_settings/setup_policy_log_nic_network.sh.j2 +++ /dev/null @@ -1,20 +0,0 @@ -#!/bin/bash -status_address_add_ipv4=0 -status_address_add_ipv6=0 -status_route_add_ipv4=0 - -static_hostname=$(hostnamectl status --static) -hostnamectl set-hostname $static_hostname --transient --pretty - -ifconfig eth_ctl {{ network_setting.nic_policy_log.ipv4 }} -status_address_add_ipv4=$? -if [ $status_address_add_ipv4 -ne 0 ]; then - echo "Fail to add ipv4 address to eth_ctl,return code:${status_address_add_ipv4}" - exit $status_address_add_ipv4 -fi -route add default gw {{ network_setting.nic_policy_log.gateway_ipv4 }} dev eth_ctl -status_route_add_ipv4=$? -if [ $status_route_add_ipv4 -ne 7 ] && [ $status_route_add_ipv4 -ne 0 ]; then - echo "Fail to add ipv4 route to eth_ctl,return code:${status_route_add_ipv4}" - exit $status_route_add_ipv4 -fi diff --git a/ansible/roles/tsg-os-provision/files/script/convertor.sh b/ansible/roles/tsg-os-provision/files/script/convertor.sh deleted file mode 100644 index fd89f851..00000000 --- a/ansible/roles/tsg-os-provision/files/script/convertor.sh +++ /dev/null @@ -1,3 +0,0 @@ -#!/bin/bash -ex - -echo "Reserved for provision config convert" \ No newline at end of file diff --git a/ansible/roles/tsg-os-provision/files/script/provision.sh b/ansible/roles/tsg-os-provision/files/script/provision.sh deleted file mode 100644 index 504421fb..00000000 --- a/ansible/roles/tsg-os-provision/files/script/provision.sh +++ /dev/null @@ -1,36 +0,0 @@ -#!/bin/bash -ex - -enable_config_apply=$1 -config_path=/data/tsg-os-provision/provision.yml -config_d_path=/data/tsg-os-provision/provision.yml.d -snapshot_config_path=/data/tsg-os-provision/provision.yml.snapshot -snapshot_config_d_path=/data/tsg-os-provision/provision.yml.d.snapshot -hosts_path=/opt/tsg/tsg-os-provision/hosts -provision_path=/opt/tsg/tsg-os-provision/tasks/provision.yml -convertor_script_path=/opt/tsg/tsg-os-provision/scripts/convertor.sh - -succ_sign_file=/data/tsg-os-provision/.provision_succeeded - -#execute_provision_del_succ_sign(){ -# rm -rf ${succ_sign_file} -#} - -execute_provision_convert_action(){ - /opt/tsg/tsg-os-provision/scripts/convertor.sh -} - -execute_provision_action(){ - ansible-playbook -i ${hosts_path} ${provision_path} -e "enable_config_apply=${enable_config_apply}" - cp ${config_path} ${snapshot_config_path} -r - rm ${snapshot_config_d_path} -rf - cp -r ${config_d_path} ${snapshot_config_d_path} -} - -#execute_provision_add_succ_sign(){ -# touch ${succ_sign_file} -#} - -#execute_provision_del_succ_sign -execute_provision_convert_action -execute_provision_action -#execute_provision_add_succ_sign \ No newline at end of file diff --git a/ansible/roles/tsg-os-provision/files/script/tsg-os-provision.sh b/ansible/roles/tsg-os-provision/files/script/tsg-os-provision.sh deleted file mode 100644 index 65c5c8d9..00000000 --- a/ansible/roles/tsg-os-provision/files/script/tsg-os-provision.sh +++ /dev/null @@ -1 +0,0 @@ -export PATH=/opt/tsg/tsg-os-provision:$PATH diff --git a/ansible/roles/tsg-os-provision/files/service/tsg-os-provision.service.TSG7400 b/ansible/roles/tsg-os-provision/files/service/tsg-os-provision.service.TSG7400 deleted file mode 100644 index 072d1827..00000000 --- a/ansible/roles/tsg-os-provision/files/service/tsg-os-provision.service.TSG7400 +++ /dev/null @@ -1,14 +0,0 @@ -[Unit] -Description=Tsg os provision -Requires=network.target -After=network.target -Before=tfe-env.service mrenv.service certstore.service telegraf_proxy.service cert-redis.service consul.service - -[Service] -ExecStart=/bin/sh -c "/opt/tsg/tsg-os-provision/scripts/provision.sh 0" -Type=oneshot -RemainAfterExit=yes - -[Install] -WantedBy=multi-user.target -RequiredBy=tfe-env.service mrenv.service certstore.service telegraf_proxy.service cert-redis.service consul.service diff --git a/ansible/roles/tsg-os-provision/files/tasks/provision.yml.7400MCN0P01R01 b/ansible/roles/tsg-os-provision/files/tasks/provision.yml.7400MCN0P01R01 deleted file mode 100644 index 95f25457..00000000 --- a/ansible/roles/tsg-os-provision/files/tasks/provision.yml.7400MCN0P01R01 +++ /dev/null @@ -1,321 +0,0 @@ ---- -- hosts: provision - tasks: - - name: Load default config file variable - include_vars: - file: /opt/tsg/tsg-os-provision/provision.default.yml - - - name: Load general config file variable - include_vars: - file: /data/tsg-os-provision/provision.yml - - - name: Load provision.yml.d config file variable - include_vars: - dir: /data/tsg-os-provision/provision.yml.d/ - ignore_unknown_extensions: yes - extensions: - - 'yml' - - 'yaml' - - - name: "template setup_policy_log_nic_network.sh" - template: - src: ../templates/setup_policy_log_nic_network.sh.j2 - dest: /opt/tsg/tsg-os-provision/scripts/setup_policy_log_nic_network.sh - mode: 0755 - - - name: "execute setup_policy_log_nic_network.sh" - shell: /opt/tsg/tsg-os-provision/scripts/setup_policy_log_nic_network.sh - register: result_exec_setup_policy_log_nic_network - - - name: "Output results that executes command that gets the result_exec_setup_policy_log_nic_network" - debug: - msg: "{{ result_exec_setup_policy_log_nic_network }}" - - - name: "Verify result_exec_setup_policy_log_nic_network" - assert: - that: - - result_exec_setup_policy_log_nic_network.rc == 0 - - result_exec_setup_policy_log_nic_network.failed == False - fail_msg: "error:{{ result_exec_setup_policy_log_nic_network.stderr }},stdout:{{ result_exec_setup_policy_log_nic_network }}" - success_msg: "{{ result_exec_setup_policy_log_nic_network.stdout_lines }}" - - - name: "template adapt_tera_network_setting.sh when NPB device is tera" - template: - src: ../templates/adapt_tera_network_setting.sh.j2 - dest: /opt/tsg/tsg-os-provision/scripts/adapt_tera_network_setting.sh - mode: 0755 - when: npb_device == 'tera' - - - name: "execute adapt_tera_network_setting.sh when NPB device is tera" - shell: /opt/tsg/tsg-os-provision/scripts/adapt_tera_network_setting.sh - register: result_exec_adapt_tera_network_setting - when: npb_device == 'tera' - - - name: "Output results that executes command that gets the result_exec_adapt_tera_network_setting" - debug: - msg: "{{ result_exec_adapt_tera_network_setting }}" - when: npb_device == 'tera' - - - name: "Verify result_exec_adapt_tera_network_setting" - assert: - that: - - result_exec_adapt_tera_network_setting.rc == 0 - - result_exec_adapt_tera_network_setting.failed == False - fail_msg: "error:{{ result_exec_adapt_tera_network_setting.stderr }},stdout:{{ result_exec_adapt_tera_network_setting }}" - success_msg: "{{ result_exec_adapt_tera_network_setting.stdout_lines }}" - when: npb_device == 'tera' - - - name: "set sapp_overlay_mode var when NPB device is tera" - set_fact: - sapp_overlay_mode: "none" - gdev_conf_keep_alive_ip: "127.0.0.1" - when: npb_device == 'tera' - - - name: "set sapp_overlay_mode var when NPB device is inline_device" - set_fact: - sapp_overlay_mode: "vxlan" - gdev_conf_keep_alive_ip: "{{ inline_device_settings.keepalive.ip }}" - when: npb_device == 'inline_device' - - - name: "set sapp_overlay_mode var when NPB device is direct" - set_fact: - sapp_overlay_mode: "none" - gdev_conf_keep_alive_ip: "127.0.0.1" - when: npb_device == 'direct' - - - name: "set cm_policy_server_ip var depend on enable_policy_local_cache" - set_fact: - cm_policy_server_ip: "{{ item.cm_policy_server_ip }}" - cm_policy_server_port: "{{ item.cm_policy_server_port }}" - when: feature.enable_policy_local_cache == item.enable_policy_local_cache - with_items: - - { "enable_policy_local_cache": 1, "npb_device": tera, "cm_policy_server_ip": 192.168.100.1, "cm_policy_server_port": 7002 } - - { "enable_policy_local_cache": 0, "npb_device": inline_device, "cm_policy_server_ip": "{{ cm.policy_server.address }}", "cm_policy_server_port": "{{ cm.policy_server.port }}"} - - - name: "Add sapp service service_attach_startpre.conf.tera when NPB_device type is tera" - copy: - src: "{{ item.src }}" - dest: "{{ item.dest }}" - mode: "{{ item.mode }}" - when: npb_device == 'tera' - with_items: - - { "src": "../files/service_attach_startpre.conf.tera", "dest": "/usr/lib/systemd/system/sapp.service.d/service_attach_startpre.conf", "mode": "0644" } - - { "src": "../files/tera_fake_promisc_setup.sh", "dest": "/opt/tsg/sapp/", "mode": "0755" } - - - name: "Add sapp service service_attach_startpre.conf.except_tera when NPB_device type is inline_device and direct" - copy: - src: "{{ item.src }}" - dest: "{{ item.dest }}" - mode: "{{ item.mode }}" - when: npb_device == 'inline_device' or npb_device == 'direct' - with_items: - - { "src": "../files/service_attach_startpre.conf.except_tera", "dest": "/usr/lib/systemd/system/sapp.service.d/service_attach_startpre.conf", "mode": "0644" } - - - name: "tsg-os-provision: Template the conflist.inf" - template: - src: ../templates/conflist.inf.j2 - dest: /opt/tsg/sapp/plug/conflist.inf - tags: sapp - - - name: "tsg-os-provision: vlan_flipping_map.conf" - template: - src: ../templates/vlan_flipping_map.conf.j2 - dest: /opt/tsg/sapp/etc/vlan_flipping_map.conf - tags: sapp - - - name: "tsg-os-provision: template gdev.conf file" - template: - src: "../templates/gdev.conf.j2" - dest: /opt/tsg/sapp/etc/gdev.conf - tags: sapp - - - name: "tsg-os-provision: template mrglobal.conf file" - template: - src: "../templates/mrglobal.conf.j2" - dest: /opt/tsg/mrzcpd/etc/mrglobal.conf - tags: mrzcpd - - - name: "tsg-os-provision: template certstore configure file" - template: - src: "../templates/cert_store.ini.j2" - dest: /opt/tsg/certstore/conf/cert_store.ini - tags: certstore - - - name: "tsg-os-provision: Template the tsgconf/main.conf" - template: - src: "../templates/main.conf.j2" - dest: /opt/tsg/sapp/tsgconf/main.conf - tags: firewall - - - name: "tsg-os-provision: Template the tsgconf/maat.conf" - template: - src: "../templates/maat.conf.j2" - dest: /opt/tsg/sapp/tsgconf/maat.conf - tags: firewall - - - name: "tsg-os-provision: Template the session_record.inf" - template: - src: "../templates/session_record.inf.j2" - dest: /opt/tsg/sapp/plug/business/session_record/session_record.inf - tags: firewall - - - name: "tsg-os-provision: Template the firewall.inf" - template: - src: "../templates/firewall.inf.j2" - dest: /opt/tsg/sapp/plug/business/firewall/firewall.inf - tags: firewall - - - name: "tsg-os-provision: Template the sapp.toml" - template: - src: "../templates/sapp.toml.j2" - dest: /opt/tsg/sapp/etc/sapp.toml - tags: sapp - - # - name: "tsg-os-provision: Templates telegraf.conf" - # template: - # src: "../templates/telegraf_shaping.conf.j2" - # dest: /etc/telegraf/telegraf_shaping.conf - # tags: telegraf_shaping - - - name: "tsg-os-provision: Templates telegraf_proxy.conf" - template: - src: "../templates/telegraf_proxy.conf.j2" - dest: /etc/telegraf/telegraf_proxy.conf - tags: telegraf_security - - - name: "tsg-os-provision: template consul" - template: - src: "../templates/consul.hcl.j2" - dest: /etc/consul.d/consul.hcl - tags: consul - when: shaping.enable == 1 - - - name: "mkdir /opt/tsg/etc/" - file: - path: /opt/tsg/etc - state: directory - - - name: "tsg-os-provision: obtain sn from mxn and write sn to tsg_sn.json" - shell: /opt/tsg/tsg-os-provision/scripts/obtain_sn.sh 192.168.100.5 - register: result_exec_obtain_sn_and_write_sn_in_file - - - name: "tsg-os-provision: check result_exec_obtain_sn_and_write_sn_in_file" - assert: - that: - - result_exec_obtain_sn_and_write_sn_in_file.rc == 0 - - result_exec_obtain_sn_and_write_sn_in_file.failed == False - fail_msg: "error:{{ result_exec_obtain_sn_and_write_sn_in_file.stderr }},stdout:{{ result_exec_obtain_sn_and_write_sn_in_file.stdout_lines }}" - success_msg: "Successded: obtain the sn and write sn into tsg_sn.json" - - - name: "tsg-os-provision: template the tsg_device_tag" - template: - src: "../templates/tsg_device_tag.json.j2" - dest: /opt/tsg/etc/tsg_device_tag.json - tags: tsg_device_tag - - - name: "Template the maat-redis.conf" - template: - src: "/opt/tsg/tsg-os-provision/templates/maat-redis.conf.j2" - dest: /etc/maat-redis.conf - tags: maat-redis - when: feature.enable_policy_local_cache == 1 - - - name: 'tsg-os-provision: execute command - systemctl daemon-reload' - systemd: - daemon_reload: yes - - - name: "start maat-redis and maat-redis-exporter" - systemd: - name: "{{ item }}" - enabled: yes - state: started - when: feature.enable_policy_local_cache == 1 - with_items: - - maat-redis - - maat-redis-exporter - - - name: "tsg-os-provision: coredump setup override - mkdir" - file: - path: /usr/lib/systemd/coredump.conf.d/ - state: directory - - - name: "tsg-os-provision: coredump setup override - override" - template: - src: "../templates/coredump_setup_override.conf.j2" - dest: /usr/lib/systemd/coredump.conf.d/coredump_setup_override.conf - - - name: "tsg-os-provision: snapshot the stage2 config files" - copy: - src: /data/tsg-os-provision/provision.yml - dest: /data/tsg-os-provision/provision.yml.snapshot - - - name: "tsg-os-provision: restart maat-redis" - systemd: - name: maat-redis - enabled: yes - state: started - when: - - feature.enable_policy_local_cache == 1 - - enable_config_apply == '1' - - - name: "tsg-os-provision: restart consul" - systemd: - name: consul - state: restarted - when: - - enable_config_apply == '1' - - shaping.enable == 1 - - - name: "tsg-os-provision: restart mrenv" - systemd: - name: mrenv - state: restarted - when: enable_config_apply == '1' - - - name: "tsg-os-provision: restart mrzcpd" - systemd: - name: mrzcpd - state: restarted - when: enable_config_apply == '1' - - - name: "tsg-os-provision: restart mrapm_device" - systemd: - name: mrapm_device - state: restarted - when: enable_config_apply == '1' - - - name: "tsg-os-provision: restart mrapm_stream" - systemd: - name: mrapm_stream - state: restarted - when: enable_config_apply == '1' - - - name: "tsg-os-provision: restart telegraf_proxy" - systemd: - name: telegraf_proxy - state: restarted - when: enable_config_apply == '1' - - - name: "tsg-os-provision: restart certstore" - systemd: - name: certstore - state: restarted - when: enable_config_apply == '1' - - - name: "tsg-os-provision: restart cert-redis" - systemd: - name: cert-redis - state: restarted - when: enable_config_apply == '1' - - - name: "tsg-os-provision: restart sapp" - systemd: - name: sapp - state: restarted - when: enable_config_apply == '1' - - - name: "tsg-os-provision: restart tfe" - systemd: - name: tfe - state: restarted - when: enable_config_apply == '1' \ No newline at end of file diff --git a/ansible/roles/tsg-os-provision/files/tasks/provision.yml.7400MCN123P01R01 b/ansible/roles/tsg-os-provision/files/tasks/provision.yml.7400MCN123P01R01 deleted file mode 100644 index e06e1c9d..00000000 --- a/ansible/roles/tsg-os-provision/files/tasks/provision.yml.7400MCN123P01R01 +++ /dev/null @@ -1,127 +0,0 @@ ---- -- hosts: provision - tasks: - - name: Load default config file variable - include_vars: - file: /opt/tsg/tsg-os-provision/provision.default.yml - - - name: Load general config file variable - include_vars: - file: /data/tsg-os-provision/provision.yml - - - name: Load provision.yml.d config file variable - include_vars: - dir: /data/tsg-os-provision/provision.yml.d/ - ignore_unknown_extensions: yes - extensions: - - 'yml' - - 'yaml' - - - name: "mkdir /opt/tsg/etc/" - file: - path: /opt/tsg/etc - state: directory - - - name: "template setup_policy_log_nic_network.sh" - template: - src: ../templates/setup_policy_log_nic_network.sh.j2 - dest: /opt/tsg/tsg-os-provision/scripts/setup_policy_log_nic_network.sh - mode: 0755 - - - name: "execute setup_policy_log_nic_network.sh" - shell: /opt/tsg/tsg-os-provision/scripts/setup_policy_log_nic_network.sh - register: result_exec_setup_policy_log_nic_network - - - name: "Output results that executes command that gets the result_exec_setup_policy_log_nic_network" - debug: - msg: "{{ result_exec_setup_policy_log_nic_network }}" - - - name: "Verify result_exec_setup_policy_log_nic_network" - assert: - that: - - result_exec_setup_policy_log_nic_network.rc == 0 - - result_exec_setup_policy_log_nic_network.failed == False - fail_msg: "error:{{ result_exec_setup_policy_log_nic_network.stderr }},stdout:{{ result_exec_setup_policy_log_nic_network }}" - success_msg: "{{ result_exec_setup_policy_log_nic_network.stdout_lines }}" - - - name: "tsg-os-provision: obtain sn from mxn and write sn to tsg_sn.json" - shell: /opt/tsg/tsg-os-provision/scripts/obtain_sn.sh 192.168.100.5 - register: result_exec_obtain_sn_and_write_sn_in_file - - - name: "tsg-os-provision: check result_exec_obtain_sn_and_write_sn_in_file" - assert: - that: - - result_exec_obtain_sn_and_write_sn_in_file.rc == 0 - - result_exec_obtain_sn_and_write_sn_in_file.failed == False - fail_msg: "error:{{ result_exec_obtain_sn_and_write_sn_in_file.stderr }},stdout:{{ result_exec_obtain_sn_and_write_sn_in_file.stdout_lines }}" - success_msg: "Successded: obtain the sn and write sn into tsg_sn.json" - - - name: "set cm_policy_server_ip var depend on enable_policy_local_cache" - set_fact: - cm_policy_server_ip: "{{ item.cm_policy_server_ip }}" - cm_policy_server_port: "{{ item.cm_policy_server_port }}" - when: feature.enable_policy_local_cache == item.enable_policy_local_cache - with_items: - - { "enable_policy_local_cache": 1, "cm_policy_server_ip": 192.168.100.1, "cm_policy_server_port": 7002 } - - { "enable_policy_local_cache": 0, "cm_policy_server_ip": "{{cm.policy_server.address}}", "cm_policy_server_port": "{{ cm.policy_server.port }}"} - - - name: "tsg-os-provision: template the tsg_device_tag" - template: - src: "../templates/tsg_device_tag.json.j2" - dest: /opt/tsg/etc/tsg_device_tag.json - tags: tsg_device_tag - - - name: "tsg-os-provision: template the tfe.conf" - template: - src: "../templates/tfe.conf.j2" - dest: /opt/tsg/tfe/conf/tfe/tfe.conf - tags: tfe - - - name: "tsg-os-provision: coredump setup override - mkdir" - file: - path: /usr/lib/systemd/coredump.conf.d/ - state: directory - - - name: "tsg-os-provision: coredump setup override - override" - template: - src: "../templates/coredump_setup_override.conf.j2" - dest: /usr/lib/systemd/coredump.conf.d/coredump_setup_override.conf - - - name: 'tsg-os-provision: execute command - systemctl daemon-reload' - systemd: - daemon_reload: yes - - - name: "tsg-os-provision: snapshot the stage2 config files" - copy: - src: /data/tsg-os-provision/provision.yml - dest: /data/tsg-os-provision/provision.yml.snapshot - - - name: "tsg-os-provision: restart mrenv" - systemd: - name: mrenv - state: restarted - when: enable_config_apply == '1' - - - name: "tsg-os-provision: restart mrzcpd" - systemd: - name: mrzcpd - state: restarted - when: enable_config_apply == '1' - - - name: "tsg-os-provision: restart mrapm_device" - systemd: - name: mrapm_device - state: restarted - when: enable_config_apply == '1' - - - name: "tsg-os-provision: restart mrapm_stream" - systemd: - name: mrapm_stream - state: restarted - when: enable_config_apply == '1' - - - name: "tsg-os-provision: restart tfe" - systemd: - name: tfe - state: restarted - when: enable_config_apply == '1' diff --git a/ansible/roles/tsg-os-provision/tasks/main.yml b/ansible/roles/tsg-os-provision/tasks/main.yml deleted file mode 100644 index 7b161fdf..00000000 --- a/ansible/roles/tsg-os-provision/tasks/main.yml +++ /dev/null @@ -1,110 +0,0 @@ -- name: "set system default.target" - shell: ln -vfs /usr/lib/systemd/system/workload.target /etc/systemd/system/default.target - -- name: "tsg-os-provision: build tsg-os-provision directory and sub directory" - file: - path: "{{ item }}" - state: directory - with_items: - - "/opt/tsg/tsg-os-provision/" - - "/opt/tsg/tsg-os-provision/files/" - - "/opt/tsg/tsg-os-provision/tasks/" - - "/opt/tsg/tsg-os-provision/templates/" - - "/opt/tsg/tsg-os-provision/scripts/" - -- name: "tsg-os-provision: copy hosts file dest" - copy: - src: "{{ role_path }}/files/hosts" - dest: /opt/tsg/tsg-os-provision/hosts - mode: 0644 - -- name: "tsg-os-provision: template network settings shell" - copy: - src: "{{ role_path }}/files/network_settings/{{ item }}" - dest: "/opt/tsg/tsg-os-provision/templates/" - with_items: - - adapt_tera_network_setting.sh.j2 - - setup_policy_log_nic_network.sh.j2 - -- name: "tsg-os-provision: copy tasks file that excutes provision to dest - tsg7400 mcn0" - copy: - src: "{{ role_path }}/files/tasks/provision.yml.7400MCN0P01R01" - dest: /opt/tsg/tsg-os-provision/tasks/provision.yml - mode: 0644 - when: runtime_env == 'TSG-7400-mcn0' - -- name: "tsg-os-provision: copy tasks file that excutes provision to dest - tsg7400 mcn1 mcn2 mcn3" - copy: - src: "{{ role_path }}/files/tasks/provision.yml.7400MCN123P01R01" - dest: /opt/tsg/tsg-os-provision/tasks/provision.yml - mode: 0644 - when: runtime_env == 'TSG-7400-mcn123' - -- name: "tsg-os-provision: copy provision.default.yml - tsg7400 mcn0" - copy: - src: "{{ role_path }}/files/config_sample/provision.default.yml.7400MCN0P01R01" - dest: /opt/tsg/tsg-os-provision/provision.default.yml - mode: 0644 - when: runtime_env == 'TSG-7400-mcn0' - -- name: "tsg-os-provision: copy provision.default.yml - tsg7400 mcn123" - copy: - src: "{{ role_path }}/files/config_sample/provision.default.yml.7400MCN123P01R01" - dest: /opt/tsg/tsg-os-provision/provision.default.yml - mode: 0644 - when: runtime_env == 'TSG-7400-mcn123' - -- name: "tsg-os-provision: copy provision.yml.sample to dest - tsg7400 mcn0" - copy: - src: "{{ role_path }}/files/config_sample/provision.yml.sample.7400MCN0P01R01" - dest: /opt/tsg/tsg-os-provision/provision.yml.sample - mode: 0644 - when: runtime_env == 'TSG-7400-mcn0' - -- name: "tsg-os-provision: copy provision.yml.sample to dest - tsg7400 mcn1 mcn2 mcn3" - copy: - src: "{{ role_path }}/files/config_sample/provision.yml.sample.7400MCN123P01R01" - dest: /opt/tsg/tsg-os-provision/provision.yml.sample - mode: 0644 - when: runtime_env == 'TSG-7400-mcn123' - -- name: "tsg-os-provision: copy provision.sh file to dest" - copy: - src: "{{ role_path }}/files/script/{{ item }}" - dest: /opt/tsg/tsg-os-provision/scripts - mode: 0755 - with_items: - - provision.sh - - convertor.sh - -- name: "install tsg-os-provision.service -- TSG7400" - copy: - src: "{{ role_path }}/files/service/{{ item.src }}" - dest: /usr/lib/systemd/system/{{ item.dest }} - mode: 0644 - with_items: - - { "src": tsg-os-provision.service.TSG7400, "dest": tsg-os-provision.service } - when: runtime_env == 'TSG-7400-mcn0' or runtime_env == 'TSG-7400-mcn123' - -- name: "replace action: replace service WantedBy from multi-user.target to workload.target --TSG7400" - replace: - path: "{{ item }}" - regexp: 'WantedBy=multi-user.target' - replace: 'RequiredBy=workload.target' - with_items: - - /usr/lib/systemd/system/tsg-os-provision.service - when: runtime_env == 'TSG-7400-mcn0' or runtime_env == 'TSG-7400-mcn123' - -- name: "tsg-os-provision: enable tsg-os-provison -- TSG7400" - systemd: - name: "{{ item }}" - enabled: yes - with_items: - - tsg-os-provision - when: runtime_env == 'TSG-7400-mcn0' or runtime_env == 'TSG-7400-mcn123' - -- name: "copy tsg-os-provision.sh to destination" - copy: - src: "{{ role_path }}/files/script/tsg-os-provision.sh" - dest: /etc/profile.d/ - mode: 0755 diff --git a/ansible/roles/tsg_device_tag/tasks/main.yml b/ansible/roles/tsg_device_tag/tasks/main.yml deleted file mode 100644 index 7f9699c3..00000000 --- a/ansible/roles/tsg_device_tag/tasks/main.yml +++ /dev/null @@ -1,6 +0,0 @@ ---- -- name: "Template the tsg_device_tag.json.j2" - template: - src: "{{ role_path }}/templates/tsg_device_tag.json.j2.j2" - dest: /opt/tsg/tsg-os-provision/templates/tsg_device_tag.json.j2 - tags: template diff --git a/ansible/roles/tsg_device_tag/templates/tsg_device_tag.json.j2.j2 b/ansible/roles/tsg_device_tag/templates/tsg_device_tag.json.j2.j2 deleted file mode 100644 index 23f48118..00000000 --- a/ansible/roles/tsg_device_tag/templates/tsg_device_tag.json.j2.j2 +++ /dev/null @@ -1,17 +0,0 @@ -[MAAT] -{% raw %}{% set tags_list = [] %} -{% if data_center.name is defined %} -{% set tag_json = "{\"tag\":\"" ~ "data_center" ~ "\",\"value\":\"" ~ data_center.name ~ "\"}" %} -{{tags_list.append(tag_json)}}{% endif %} -{% if device.tags is defined %} -{% for device_tag in device.tags %} -{% for key,value in device_tag.items() %} -{% set tag_json = "{\"tag\":\"" ~ key ~ "\",\"value\":\"" ~ value ~ "\"}" %} -{{tags_list.append(tag_json)}}{% endfor %} -{% endfor %} -{% endif %} -{% if data_center.name is not defined and device.tags is not defined %} -{{ device.tags }} -{% endif %} -ACCEPT_TAGS={"tags":[{{ tags_list | join(",") }}]} -{% endraw %} \ No newline at end of file diff --git a/ansible/roles/tsg_sn/files/cmm_api_tst b/ansible/roles/tsg_sn/files/cmm_api_tst deleted file mode 100644 index a228f128..00000000 Binary files a/ansible/roles/tsg_sn/files/cmm_api_tst and /dev/null differ diff --git a/ansible/roles/tsg_sn/files/obtain_sn.sh.TSG7400 b/ansible/roles/tsg_sn/files/obtain_sn.sh.TSG7400 deleted file mode 100644 index 1ae70d0a..00000000 --- a/ansible/roles/tsg_sn/files/obtain_sn.sh.TSG7400 +++ /dev/null @@ -1,36 +0,0 @@ -#!/bin/bash -x - -ip_of_obtain_sn=$1 - -if [ $ip_of_obtain_sn == '127.0.0.1' ];then - echo "{\"sn\": \"CBT22021250000020625\"}" > /opt/tsg/etc/tsg_sn.json - exit 0 -fi - -if [ ! -f "/opt/tsg/tsg-os-provision/scripts/cmm_api_tst" ];then - echo "not found cmm_api_tst!" - echo "{\"sn\": \"unknown\"}" > /opt/tsg/etc/tsg_sn.json - echo "device_id=\"unknown\"" > /etc/default/telegraf - exit 0 -fi - -/opt/tsg/tsg-os-provision/scripts/cmm_api_tst 9 1 1 $ip_of_obtain_sn | tee chid.id -if [ $? != 0 ]; then - echo "cmm_api_tst failed!" - echo "{\"sn\": \"unknown\"}" > /opt/tsg/etc/tsg_sn.json - echo "device_id=\"unknown\"" > /etc/default/telegraf - exit 0 -fi - -CHID=`cat chid.id | sed -n '1p' | awk -F ":" '{print $2}' | sed 's/ //g'` -CHIDL=`echo $CHID | awk '{print length($0)}'` - -if [ $CHIDL != 20 ];then - echo "CHID length is not 20!" - echo "{\"sn\": \"unknown\"}" > /opt/tsg/etc/tsg_sn.json - echo "device_id=\"unknown\"" > /etc/default/telegraf - exit 0 -fi - -echo "{\"sn\": \"$CHID\"}" > /opt/tsg/etc/tsg_sn.json -echo "device_id=\"$CHID\"" > /etc/default/telegraf diff --git a/ansible/roles/tsg_sn/files/read_sn_to_env.sh b/ansible/roles/tsg_sn/files/read_sn_to_env.sh deleted file mode 100644 index 352bddda..00000000 --- a/ansible/roles/tsg_sn/files/read_sn_to_env.sh +++ /dev/null @@ -1,42 +0,0 @@ -#!/bin/bash -x -DEVICE_TYPE= -SN= - -function read_device_type() -{ - product_name=`ipmitool fru list | grep 'Product Name' | awk '{print $4}' | head -n 1` - - case ${product_name} in - "ACB300-040-00" | "9000-NPB-P01R01") - DEVICE_TYPE="9000-NPB" - ;; - *) - ;; - esac -} - -function read_sn() -{ - if [ ${DEVICE_TYPE} == "9000-NPB" ]; then - SN=`ipmitool fru -t 130 | awk 'NR==12' | awk '{ print $4}'` - else - SN=`ipmitool fru list | grep 'Product Serial' | awk '{ print $4}' | head -n 1` - fi - - if [ -z "${SN}" ]; then - SN="unknown" - fi -} - -function add_sn_env() -{ - env_profile="/etc/profile.d/sn.sh" - - #export SN=${SN}. Not set in present session. - echo "export SN=${SN}" > ${env_profile} - chmod 0755 ${env_profile} -} - -read_device_type -read_sn -add_sn_env \ No newline at end of file diff --git a/ansible/roles/tsg_sn/tasks/main.yml b/ansible/roles/tsg_sn/tasks/main.yml deleted file mode 100644 index e4f15687..00000000 --- a/ansible/roles/tsg_sn/tasks/main.yml +++ /dev/null @@ -1,29 +0,0 @@ ---- -- name: "7400-mcn0 & 7400-mcn123: Create /opt/tsg/tsg-os-provision/scripts/" - file: - path: "/opt/tsg/tsg-os-provision/scripts/" - state: directory - when: runtime_env == 'TSG-7400-mcn0' or runtime_env == 'TSG-7400-mcn123' - -- name: "7400-mcn0 & 7400-mcn123: Deploy obtain_sn.sh" - copy: - src: "{{ role_path }}/files/{{ item.src }}" - dest: "/opt/tsg/tsg-os-provision/scripts/{{ item.dest }}" - mode: 0755 - with_items: - - { "src": "obtain_sn.sh.TSG7400", "dest": "obtain_sn.sh" } - - { "src": "cmm_api_tst", "dest": "cmm_api_tst" } - when: runtime_env == 'TSG-7400-mcn0' or runtime_env == 'TSG-7400-mcn123' - -- name: "TSG-X: Create /opt/tsg/scripts/" - file: - path: "/opt/tsg/scripts/" - state: directory - when: runtime_env == 'TSG-X-P0906' - -- name: "TSG-X: Deploy obtain-sn.sh" - copy: - src: "{{ role_path }}/files/read_sn_to_env.sh" - dest: /opt/tsg/scripts/read_sn_to_env.sh - mode: 0755 - when: runtime_env == 'TSG-X-P0906' \ No newline at end of file diff --git a/conf/yum-CentOS-7.conf b/conf/yum-CentOS-7.conf deleted file mode 100644 index ab2e80a8..00000000 --- a/conf/yum-CentOS-7.conf +++ /dev/null @@ -1,142 +0,0 @@ -[main] -cachedir=/var/cache/yum/x86_64/7 -keepcache=0 -debuglevel=2 -logfile=/var/log/yum.log -exactarch=1 -obsoletes=1 -gpgcheck=1 -plugins=1 -installonly_limit=5 -distroverpkg=centos-release -reposdir=./ - -[base] -name=CentOS-7 - Base - mirrors.aliyun.com -failovermethod=priority -baseurl=http://mirrors.aliyun.com/centos/7/os/x86_64/ - https://mirrors.tuna.tsinghua.edu.cn/centos/7/os/x86_64/ - http://mirrors.aliyuncs.com/centos/7/os/x86_64/ - http://mirrors.cloud.aliyuncs.com/centos/7/os/x86_64/ -gpgcheck=1 -gpgkey=http://mirrors.aliyun.com/centos/RPM-GPG-KEY-CentOS-7 - -[updates] -name=CentOS-7 - Updates - mirrors.aliyun.com -failovermethod=priority -baseurl=http://mirrors.aliyun.com/centos/7/updates/x86_64/ - https://mirrors.tuna.tsinghua.edu.cn/centos/7/updates/x86_64/ - http://mirrors.aliyuncs.com/centos/7/updates/x86_64/ - http://mirrors.cloud.aliyuncs.com/centos/7/updates/x86_64/ -gpgcheck=1 -gpgkey=http://mirrors.aliyun.com/centos/RPM-GPG-KEY-CentOS-7 - -[extras] -name=CentOS-7 - Extras - mirrors.aliyun.com -failovermethod=priority -baseurl=http://mirrors.aliyun.com/centos/7/extras/x86_64/ - https://mirrors.tuna.tsinghua.edu.cn/centos/7/extras/x86_64/ - http://mirrors.aliyuncs.com/centos/7/extras/x86_64/ - http://mirrors.cloud.aliyuncs.com/centos/7/extras/x86_64/ -gpgcheck=1 -gpgkey=http://mirrors.aliyun.com/centos/RPM-GPG-KEY-CentOS-7 - -[epel] -name=Extra Packages for Enterprise Linux 7 - x86_64 -baseurl=https://mirrors.aliyun.com/epel/7/x86_64 - https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/ -failovermethod=priority -enabled=1 -gpgcheck=1 -gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7 - -[docker-ce-stable] -name=Docker CE Stable -baseurl=https://mirrors.aliyun.com/docker-ce/linux/centos/7/x86_64/stable -enabled=1 -gpgcheck=1 -gpgkey=https://mirrors.aliyun.com/docker-ce/linux/centos/gpg - -[home_opcm] -name=home:opcm (CentOS_7) -type=rpm-md -baseurl=https://download.opensuse.org/repositories/home:/opcm/CentOS_7/ - https://ftp.gwdg.de/pub/opensuse/repositories/home:/opcm/CentOS_7/ -gpgcheck=1 -gpgkey=https://download.opensuse.org/repositories/home:/opcm/CentOS_7/repodata/repomd.xml.key - https://ftp.gwdg.de/pub/opensuse/repositories/home:/opcm/CentOS_7/repodata/repomd.xml.key -enabled=1 - -[shells_fish_release_3] -name=Fish shell - 3.x release series (CentOS_7) -type=rpm-md -baseurl=https://download.opensuse.org/repositories/shells:/fish:/release:/3/CentOS_7/ - https://ftp.gwdg.de/pub/opensuse/repositories/shells:/fish:/release:/3/CentOS_7/ -gpgcheck=1 -gpgkey=https://download.opensuse.org/repositories/shells:/fish:/release:/3/CentOS_7/repodata/repomd.xml.key - https://ftp.gwdg.de/pub/opensuse/repositories/shells:/fish:/release:/3/CentOS_7/repodata/repomd.xml.key -enabled=1 - -[framework] -name=framework -baseurl=https://repo.geedge.net/pulp/content/7/x86_64/stable/framework/ -enabled=1 -gpgcheck=0 -username=PULP_REPO_USERNAME -password=PULP_REPO_PASSWORD - -[platform] -name=platform -baseurl=https://repo.geedge.net/pulp/content/7/x86_64/stable/platform/ -enabled=1 -gpgcheck=0 -username=PULP_REPO_USERNAME -password=PULP_REPO_PASSWORD - -[protocol] -name=protocol -baseurl=https://repo.geedge.net/pulp/content/7/x86_64/stable/protocol/ -enabled=1 -gpgcheck=0 -username=PULP_REPO_USERNAME -password=PULP_REPO_PASSWORD - -[tsg] -name=tsg -baseurl=https://repo.geedge.net/pulp/content/7/x86_64/stable/tsg/ -enabled=1 -gpgcheck=0 -username=PULP_REPO_USERNAME -password=PULP_REPO_PASSWORD - -[AppSktech] -name=AppSketch -baseurl=https://repo.geedge.net/pulp/content/7/x86_64/stable/AppSketch/ -enabled=1 -gpgcheck=0 -username=PULP_REPO_USERNAME -password=PULP_REPO_PASSWORD - -[tfe] -name=tfe -baseurl=https://repo.geedge.net/pulp/content/7/x86_64/stable/tfe/ -enabled=1 -gpgcheck=0 -username=PULP_REPO_USERNAME -password=PULP_REPO_PASSWORD - -[ofed] -name=ofed -baseurl=https://repo.geedge.net/pulp/content/7/x86_64/stable/ofed/ -enabled=1 -gpgcheck=0 -username=PULP_REPO_USERNAME -password=PULP_REPO_PASSWORD - -[stellar] -name=stellar -baseurl=https://repo.geedge.net/pulp/content/7/x86_64/stable/stellar/ -enabled=1 -gpgcheck=0 -username=PULP_REPO_USERNAME -password=PULP_REPO_PASSWORD \ No newline at end of file diff --git a/make/Makefile.7400MCN0P01R01 b/make/Makefile.7400MCN0P01R01 deleted file mode 100644 index d64d2af7..00000000 --- a/make/Makefile.7400MCN0P01R01 +++ /dev/null @@ -1,72 +0,0 @@ - -PROFILE_ID := 7400-MCN0-P01R01 -SUPPORTED_MACHINE_ID := 7400-MCN0-P01R01 -KERNEL_ARGS := console=ttyS0,115200n8 crashkernel=512M intel_iommu=on iommu=pt pci=realloc,assign-busses selinux=0 transparent_hugepage=never processor.max_cstate=0 intel_idle.max_cstate=0 intel_pstate=disable -GRUB_SERIAL_COMMAND := -SIZE_PART_SYSROOT := 16384M -SIZE_PART_UPDATE := 16384M - -PROFILE_ID_IN_SHORT := $(subst -,$e,$(PROFILE_ID)) -CHROOT_PKG := tsg-os-${OS_RELEASE_VER}-${PROFILE_ID_IN_SHORT}-chroot.tar.bz2 -CHROOT_BIN := tsg-os-${OS_RELEASE_VER}-${PROFILE_ID_IN_SHORT}-ONIE.bin - -TARGET_BUILD_DIR := $(BUILDDIR_BASE)/$(PROFILE_ID) -TARGET_INSTALLER_DIR := $(TARGET_BUILD_DIR)/installer -TARGET_SYSROOT_DIR := $(TARGET_BUILD_DIR)/sysroot - -.PHONY: all builddir installer sysroot-base sysroot-ansible sysroot-cleanup sysroot-archive sysroot-binary clean - -all: sysroot-binary - -builddir: - mkdir -p $(TARGET_BUILD_DIR) - -installer: builddir - rm -rf $(TARGET_INSTALLER_DIR) - mkdir -p $(TARGET_INSTALLER_DIR) - cp $(INSTALLERDIR)/install.sh $(TARGET_INSTALLER_DIR)/install.sh - cp $(INSTALLERDIR)/distro-setup.sh $(TARGET_INSTALLER_DIR)/distro-setup.sh - chmod +x $(TARGET_INSTALLER_DIR)/install.sh - chmod +x $(TARGET_INSTALLER_DIR)/distro-setup.sh - - sed -i -e "s/%%DISTR0_VER%%/$(OS_RELEASE_VER)/" $(TARGET_INSTALLER_DIR)/install.sh - sed -i -e "s/%%MACHINE_ID%%/$(SUPPORTED_MACHINE_ID)/" $(TARGET_INSTALLER_DIR)/install.sh - sed -i -e "s/%%CHROOT_PKG%%/$(CHROOT_PKG)/" $(TARGET_INSTALLER_DIR)/install.sh - sed -i -e "s/%%KERNAL_ARGS%%/$(KERNEL_ARGS)/" $(TARGET_INSTALLER_DIR)/install.sh - sed -i -e "s/%%GRUB_SERIAL_COMMAND%%/$(GRUB_SERIAL_COMMAND)/" $(TARGET_INSTALLER_DIR)/install.sh - sed -i -e "s/%%SIZE_PART_SYSROOT%%/$(SIZE_PART_SYSROOT)/" $(TARGET_INSTALLER_DIR)/install.sh - sed -i -e "s/%%SIZE_PART_UPDATE%%/$(SIZE_PART_UPDATE)/" $(TARGET_INSTALLER_DIR)/install.sh - - sed -i '/sapp-pr:/d;/mrzcpd-icelake-server:/d;/mrzcpd-znver1:/d;/mrzcpd-corei7:/d' $(PROJECTDIR)/ansible/install_config/group_vars/rpm_version.yml - -sysroot-base: builddir - $(TOOLSDIR)/mk-base-image $(CONFDIR)/yum-CentOS-7.conf $(TARGET_SYSROOT_DIR) $(PROJECTDIR) $(PROFILE_ID) - -sysroot-verfile: sysroot-base - sed -i -e "s/^NAME=.*/NAME=\"TSG-OS\"/" $(TARGET_SYSROOT_DIR)/usr/lib/os-release - sed -i -e "s/^VERSION=.*/VERSION=\"$(OS_RELEASE_VER) ($(PROFILE_ID_IN_SHORT))\"/" $(TARGET_SYSROOT_DIR)/usr/lib/os-release - sed -i -e "s/^PRETTY_NAME=.*/PRETTY_NAME=\"TSG-OS $(OS_RELEASE_VER) ($(PROFILE_ID_IN_SHORT))\"/" $(TARGET_SYSROOT_DIR)/usr/lib/os-release - -sysroot-ansible: sysroot-verfile sysroot-base - cp $(CONFDIR)/yum-CentOS-7.conf $(TARGET_SYSROOT_DIR)/tmp/ -r - cp /etc/resolv.conf $(TARGET_SYSROOT_DIR)/etc/ -r - cp $(TARGET_SYSROOT_DIR)/etc/hosts $(TARGET_SYSROOT_DIR)/tmp/ -r - cp /etc/hosts $(TARGET_SYSROOT_DIR)/etc/ -r - $(TOOLSDIR)/ansible-HAL $(PROFILE_ID) $(PROJECTDIR) $(TARGET_SYSROOT_DIR) /tmp/yum-CentOS-7.conf $(OS_RELEASE_VER) - cp $(TARGET_SYSROOT_DIR)/tmp/hosts $(TARGET_SYSROOT_DIR)/etc/ -r - rm -rf $(TARGET_SYSROOT_DIR)/etc/resolv.conf - -sysroot-cleanup: - rm -rf $(TARGET_SYSROOT_DIR)/tmp/* - rm -rf $(TARGET_SYSROOT_DIR)/dev/* - -sysroot-archive: installer sysroot-ansible sysroot-cleanup - tar --exclude=*~ --exclude-backups --owner=root --group=root -c -C $(TARGET_SYSROOT_DIR) . | pbzip2 -p9 > $(TARGET_INSTALLER_DIR)/$(CHROOT_PKG) - -sysroot-binary: sysroot-archive - mkdir -p $(TARGET_BUILD_DIR)/cook-bits - $(TOOLSDIR)/cook-bits $(TARGET_BUILD_DIR) $(TARGET_BUILD_DIR)/cook-bits $(IMAGEDIR_BASE)/$(CHROOT_BIN) - sha256sum $(IMAGEDIR_BASE)/$(CHROOT_BIN) | awk '{print $$1}' > $(IMAGEDIR_BASE)/$(CHROOT_BIN).sha256sum.txt - -clean: - rm -rf $(TARGET_BUILD_DIR) diff --git a/make/Makefile.7400MCN123P01R01 b/make/Makefile.7400MCN123P01R01 deleted file mode 100644 index 30e014cd..00000000 --- a/make/Makefile.7400MCN123P01R01 +++ /dev/null @@ -1,72 +0,0 @@ - -PROFILE_ID := 7400-MCN123-P01R01 -SUPPORTED_MACHINE_ID := 7400-MCN123-P01R01 -KERNEL_ARGS := console=ttyS0,115200n8 crashkernel=512M intel_iommu=on iommu=pt pci=realloc,assign-busses selinux=0 transparent_hugepage=never processor.max_cstate=0 intel_idle.max_cstate=0 intel_pstate=disable -GRUB_SERIAL_COMMAND := -SIZE_PART_SYSROOT := 16384M -SIZE_PART_UPDATE := 16384M - -PROFILE_ID_IN_SHORT := $(subst -,$e,$(PROFILE_ID)) -CHROOT_PKG := tsg-os-${OS_RELEASE_VER}-${PROFILE_ID_IN_SHORT}-chroot.tar.bz2 -CHROOT_BIN := tsg-os-${OS_RELEASE_VER}-${PROFILE_ID_IN_SHORT}-ONIE.bin - -TARGET_BUILD_DIR := $(BUILDDIR_BASE)/$(PROFILE_ID) -TARGET_INSTALLER_DIR := $(TARGET_BUILD_DIR)/installer -TARGET_SYSROOT_DIR := $(TARGET_BUILD_DIR)/sysroot - -.PHONY: all builddir installer sysroot-base sysroot-ansible sysroot-cleanup sysroot-archive sysroot-binary clean - -all: sysroot-binary - -builddir: - mkdir -p $(TARGET_BUILD_DIR) - -installer: builddir - rm -rf $(TARGET_INSTALLER_DIR) - mkdir -p $(TARGET_INSTALLER_DIR) - cp $(INSTALLERDIR)/install.sh $(TARGET_INSTALLER_DIR)/install.sh - cp $(INSTALLERDIR)/distro-setup.sh $(TARGET_INSTALLER_DIR)/distro-setup.sh - chmod +x $(TARGET_INSTALLER_DIR)/install.sh - chmod +x $(TARGET_INSTALLER_DIR)/distro-setup.sh - - sed -i -e "s/%%DISTR0_VER%%/$(OS_RELEASE_VER)/" $(TARGET_INSTALLER_DIR)/install.sh - sed -i -e "s/%%MACHINE_ID%%/$(SUPPORTED_MACHINE_ID)/" $(TARGET_INSTALLER_DIR)/install.sh - sed -i -e "s/%%CHROOT_PKG%%/$(CHROOT_PKG)/" $(TARGET_INSTALLER_DIR)/install.sh - sed -i -e "s/%%KERNAL_ARGS%%/$(KERNEL_ARGS)/" $(TARGET_INSTALLER_DIR)/install.sh - sed -i -e "s/%%GRUB_SERIAL_COMMAND%%/$(GRUB_SERIAL_COMMAND)/" $(TARGET_INSTALLER_DIR)/install.sh - sed -i -e "s/%%SIZE_PART_SYSROOT%%/$(SIZE_PART_SYSROOT)/" $(TARGET_INSTALLER_DIR)/install.sh - sed -i -e "s/%%SIZE_PART_UPDATE%%/$(SIZE_PART_UPDATE)/" $(TARGET_INSTALLER_DIR)/install.sh - - sed -i '/mrzcpd-icelake-server:/d;/mrzcpd-znver1:/d;/mrzcpd-corei7:/d' $(PROJECTDIR)/ansible/install_config/group_vars/rpm_version.yml - -sysroot-base: builddir - $(TOOLSDIR)/mk-base-image $(CONFDIR)/yum-CentOS-7.conf $(TARGET_SYSROOT_DIR) $(PROJECTDIR) $(PROFILE_ID) - -sysroot-verfile: sysroot-base - sed -i -e "s/^NAME=.*/NAME=\"TSG-OS\"/" $(TARGET_SYSROOT_DIR)/usr/lib/os-release - sed -i -e "s/^VERSION=.*/VERSION=\"$(OS_RELEASE_VER) ($(PROFILE_ID_IN_SHORT))\"/" $(TARGET_SYSROOT_DIR)/usr/lib/os-release - sed -i -e "s/^PRETTY_NAME=.*/PRETTY_NAME=\"TSG-OS $(OS_RELEASE_VER) ($(PROFILE_ID_IN_SHORT))\"/" $(TARGET_SYSROOT_DIR)/usr/lib/os-release - -sysroot-ansible: sysroot-verfile sysroot-base - cp $(CONFDIR)/yum-CentOS-7.conf $(TARGET_SYSROOT_DIR)/tmp/ -r - cp /etc/resolv.conf $(TARGET_SYSROOT_DIR)/etc/ -r - cp $(TARGET_SYSROOT_DIR)/etc/hosts $(TARGET_SYSROOT_DIR)/tmp/ -r - cp /etc/hosts $(TARGET_SYSROOT_DIR)/etc/ -r - $(TOOLSDIR)/ansible-HAL $(PROFILE_ID) $(PROJECTDIR) $(TARGET_SYSROOT_DIR) /tmp/yum-CentOS-7.conf $(OS_RELEASE_VER) - cp $(TARGET_SYSROOT_DIR)/tmp/hosts $(TARGET_SYSROOT_DIR)/etc/ -r - rm -rf $(TARGET_SYSROOT_DIR)/etc/resolv.conf - -sysroot-cleanup: - rm -rf $(TARGET_SYSROOT_DIR)/tmp/* - rm -rf $(TARGET_SYSROOT_DIR)/dev/* - -sysroot-archive: installer sysroot-ansible sysroot-cleanup - tar --exclude=*~ --exclude-backups --owner=root --group=root -c -C $(TARGET_SYSROOT_DIR) . | pbzip2 -p9 > $(TARGET_INSTALLER_DIR)/$(CHROOT_PKG) - -sysroot-binary: sysroot-archive - mkdir -p $(TARGET_BUILD_DIR)/cook-bits - $(TOOLSDIR)/cook-bits $(TARGET_BUILD_DIR) $(TARGET_BUILD_DIR)/cook-bits $(IMAGEDIR_BASE)/$(CHROOT_BIN) - sha256sum $(IMAGEDIR_BASE)/$(CHROOT_BIN) | awk '{print $$1}' > $(IMAGEDIR_BASE)/$(CHROOT_BIN).sha256sum.txt - -clean: - rm -rf $(TARGET_BUILD_DIR) diff --git a/tools/mk-base-image b/tools/mk-base-image index f9187748..ab586692 100755 --- a/tools/mk-base-image +++ b/tools/mk-base-image @@ -21,11 +21,6 @@ case $profile_id in $projectdir/package/kernel-ml-$kernel_version.rpm $projectdir/package/kernel-ml-devel-$kernel_version.rpm" ;; - "7400-MCN0-P01R01" | "7400-MCN123-P01R01") - kernel_version="5.4.159-1.el7.elrepo.x86_64" - append_package_to_install="$projectdir/package/kernel-lt-$kernel_version.rpm - $projectdir/package/kernel-lt-devel-$kernel_version.rpm" - ;; *) kernel_version="error_profile_id" echo "Set kernel_version failed, error profile_id: $profile_id" @@ -45,12 +40,6 @@ case $profile_id in python3-docutils libnsl liburing hwloc-gui perl-open perl python2 js-d3-flame-graph xmlstarlet conntrack-tools crudini" ;; - "7400-MCN0-P01R01" | "7400-MCN123-P01R01") - base_package_to_install="@base @core @debugging @directory-client @guest-agents - @hardware-monitoring @network-file-system-client @performance @remote-system-management - grub2 epel-release efibootmgr ansible yum-utils ipmitool docker-ce docker-ce-cli - containerd.io lrzsz python3 vconfig watchdog pcm git tmux fish rpm-build hwloc-gui" - ;; *) base_package_to_install="error_profile_id" echo "Set base_package_to_install failed, error profile_id: $profile_id" @@ -145,15 +134,6 @@ if [ ! -f "$target/etc/pam.d/password-auth-local" ]; then ln -vfs --relative $target/etc/pam.d/password-auth-local $target/etc/pam.d/password-auth fi -case $profile_id in - "7400-MCN0-P01R01" | "7400-MCN123-P01R01") - cp -rf $projectdir/rootconf/sysroot-usr/target/* $target/usr/lib/systemd/system - mkdir -p $target/usr/lib/systemd/system/workload.target.wants - ;; - *) - echo "Profile_id: $profile_id not need workload.target" - ;; -esac # ansible-playbook -i tsg-9140-scripts/install_config/tsg_9140_host tsg-9140-scripts/tsg_9140_deploy.yml yum -c "$yum_config" --installroot="$target" -y --setopt=$setopt clean all