Tungsten Fabric知识库丨关于OpenStack、K8s、CentOS安装问题的补充(下)



  • Tungsten Fabric知识库丨关于OpenStack、K8s、CentOS安装问题的补充(上)

    CentOS 8安装过程

    centos8.2
    ansible-deployer is used
    
    only python3 is used (no python2)
     - 需要ansible 2.8.x
    
    1 x for tf-controller and kube-master, 1 vRouter
    
    (all nodes)
    yum install python3 chrony
    alternatives --set python /usr/bin/python3
    
    (vRouter nodes)
    yum install network-scripts
     - 这是必需的,因为vRouter当前不支持NetworkManager
    
    (ansible node)
    sudo yum -y install git
    sudo pip3 install PyYAML requests ansible\           
    cirros-deployment-86885fbf85-tjkwn   1/1     Running   0          13s   10.47.255.249   ip-172-31-2-120.ap-northeast-1.compute.internal              
    [root@ip-172-31-7-20 ~]# 
    [root@ip-172-31-7-20 ~]# 
    [root@ip-172-31-7-20 ~]# kubectl exec -it cirros-deployment-86885fbf85-7z78k sh
    / # ip -o a
    1: lo    inet 127.0.0.1/8 scope host lo\       valid_lft forever preferred_lft forever
    17: eth0    inet 10.47.255.250/12 scope global eth0\       valid_lft forever preferred_lft forever
    / # ping 10.47.255.249
    PING 10.47.255.249 (10.47.255.249): 56 data bytes
    64 bytes from 10.47.255.249: seq=0 ttl=63 time=0.657 ms
    64 bytes from 10.47.255.249: seq=1 ttl=63 time=0.073 ms
    ^C
    --- 10.47.255.249 ping statistics ---
    2 packets transmitted, 2 packets received, 0% packet loss
    round-trip min/avg/max = 0.073/0.365/0.657 ms
    / # 
    
    
     - 为了使chrony在安装路由器后正常工作,可能需要重新启动chrony服务器
    
    [root@ip-172-31-4-206 ~]#  chronyc -n sources
    210 Number of sources = 5
    MS Name/IP address         Stratum Poll Reach LastRx Last sample               
    ===============================================================================
    ^? 169.254.169.123               3   4     0   906  -8687ns[  -12us] +/-  428us
    ^? 129.250.35.250                2   7     0  1002   +429us[ +428us] +/-   73ms
    ^? 167.179.96.146                2   7     0   937   +665us[ +662us] +/- 2859us
    ^? 194.0.5.123                   2   6     0  1129   +477us[ +473us] +/-   44ms
    ^? 103.202.216.35                3   6     0   933  +9662ns[+6618ns] +/-  145ms
    [root@ip-172-31-4-206 ~]# 
    [root@ip-172-31-4-206 ~]# 
    [root@ip-172-31-4-206 ~]# service chronyd status
    Redirecting to /bin/systemctl status chronyd.service
    · chronyd.service - NTP client/server
       Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled; vendor preset: enabled)
       Active: active (running) since Sun 2020-06-28 16:00:34 UTC; 33min ago
         Docs: man:chronyd(8)
               man:chrony.conf(5)
     Main PID: 727 (chronyd)
        Tasks: 1 (limit: 49683)
       Memory: 2.1M
       CGroup: /system.slice/chronyd.service
               └─727 /usr/sbin/chronyd
    
    Jun 28 16:00:33 localhost.localdomain chronyd[727]: Using right/UTC timezone to obtain leap second data
    Jun 28 16:00:34 localhost.localdomain systemd[1]: Started NTP client/server.
    Jun 28 16:00:42 localhost.localdomain chronyd[727]: Selected source 169.254.169.123
    Jun 28 16:00:42 localhost.localdomain chronyd[727]: System clock TAI offset set to 37 seconds
    Jun 28 16:19:33 ip-172-31-4-206.ap-northeast-1.compute.internal chronyd[727]: Source 167.179.96.146 offline
    Jun 28 16:19:33 ip-172-31-4-206.ap-northeast-1.compute.internal chronyd[727]: Source 103.202.216.35 offline
    Jun 28 16:19:33 ip-172-31-4-206.ap-northeast-1.compute.internal chronyd[727]: Source 129.250.35.250 offline
    Jun 28 16:19:33 ip-172-31-4-206.ap-northeast-1.compute.internal chronyd[727]: Source 194.0.5.123 offline
    Jun 28 16:19:33 ip-172-31-4-206.ap-northeast-1.compute.internal chronyd[727]: Source 169.254.169.123 offline
    Jun 28 16:19:33 ip-172-31-4-206.ap-northeast-1.compute.internal chronyd[727]: Can't synchronise: no selectable sources
    [root@ip-172-31-4-206 ~]# service chronyd restart
    Redirecting to /bin/systemctl restart chronyd.service
    [root@ip-172-31-4-206 ~]# 
    [root@ip-172-31-4-206 ~]# 
    [root@ip-172-31-4-206 ~]# service chronyd status
    Redirecting to /bin/systemctl status chronyd.service
    · chronyd.service - NTP client/server
       Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled; vendor preset: enabled)
       Active: active (running) since Sun 2020-06-28 16:34:41 UTC; 2s ago
         Docs: man:chronyd(8)
               man:chrony.conf(5)
      Process: 25252 ExecStartPost=/usr/libexec/chrony-helper update-daemon (code=exited, status=0/SUCCESS)
      Process: 25247 ExecStart=/usr/sbin/chronyd $OPTIONS (code=exited, status=0/SUCCESS)
     Main PID: 25250 (chronyd)
        Tasks: 1 (limit: 49683)
       Memory: 1.0M
       CGroup: /system.slice/chronyd.service
               └─25250 /usr/sbin/chronyd
    
    Jun 28 16:34:41 ip-172-31-4-206.ap-northeast-1.compute.internal systemd[1]: Starting NTP client/server...
    Jun 28 16:34:41 ip-172-31-4-206.ap-northeast-1.compute.internal chronyd[25250]: chronyd version 3.5 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND>
    Jun 28 16:34:41 ip-172-31-4-206.ap-northeast-1.compute.internal chronyd[25250]: Frequency 35.298 +/- 0.039 ppm read from /var/lib/chrony/drift
    Jun 28 16:34:41 ip-172-31-4-206.ap-northeast-1.compute.internal chronyd[25250]: Using right/UTC timezone to obtain leap second data
    Jun 28 16:34:41 ip-172-31-4-206.ap-northeast-1.compute.internal systemd[1]: Started NTP client/server.
    [root@ip-172-31-4-206 ~]#  chronyc -n sources
    210 Number of sources = 5
    MS Name/IP address         Stratum Poll Reach LastRx Last sample               
    ===============================================================================
    ^* 169.254.169.123               3   4    17     4  -2369ns[  -27us] +/-  451us
    ^- 94.154.96.7                   2   6    17     5    +30ms[  +30ms] +/-  148ms
    ^- 185.51.192.34                 2   6    17     3  -2951us[-2951us] +/-  150ms
    ^- 188.125.64.6                  2   6    17     3  +9526us[+9526us] +/-  143ms
    ^- 216.218.254.202               1   6    17     5    +15ms[  +15ms] +/-   72ms
    [root@ip-172-31-4-206 ~]# 
    
    
    [root@ip-172-31-4-206 ~]# contrail-status 
    Pod      Service      Original Name           Original Version  State    Id            Status         
             rsyslogd                             nightly-master    running  5fc76e57c156  Up 16 minutes  
    vrouter  agent        contrail-vrouter-agent  nightly-master    running  bce023d8e6e0  Up 5 minutes   
    vrouter  nodemgr      contrail-nodemgr        nightly-master    running  9439a304cbcf  Up 5 minutes   
    vrouter  provisioner  contrail-provisioner    nightly-master    running  1531b1403e49  Up 5 minutes   
    
    WARNING: container with original name '' have Pod or Service empty. Pod: '' / Service: 'rsyslogd'. Please pass NODE_TYPE with pod name to container's env
    
    vrouter kernel module is PRESENT
    == Contrail vrouter ==
    nodemgr: active
    agent: active
    
    [root@ip-172-31-4-206 ~]#
    

    原文链接:
    https://github.com/tnaganawa/tungstenfabric-docs/blob/master/TungstenFabricKnowledgeBase.md


    往期精选

    Tungsten Fabric知识库丨vRouter内部运行探秘
    Tungsten Fabric知识库丨更多组件内部探秘
    Tungsten Fabric知识库丨 构建、安装与公有云部署
    Tungsten Fabric知识库丨测试2000个vRouter节点部署

    Tungsten Fabric入门宝典系列文章——
    1.首次启动和运行指南
    2.TF组件的七种“武器”
    3.编排器集成
    4.关于安装的那些事(上)
    5.关于安装的那些事(下)
    6.主流监控系统工具的集成
    7.开始第二天的工作
    8.8个典型故障及排查Tips
    9.关于集群更新的那些事
    10.说说L3VPN及EVPN集成
    11.关于服务链、BGPaaS及其它
    12.关于多集群和多数据中心
    13.多编排器用法及配置


Log in to reply