首页 > 其他分享 >Cephadm部署rgw ingress和nfs ingress(Pacific版本)

Cephadm部署rgw ingress和nfs ingress(Pacific版本)

时间:2023-02-27 22:58:41浏览次数:60  
标签:haproxy ingress stats rgw Pacific 192.168 timeout http backend

rgw ingress自动生成的配置

  • keepalived的配置文件:/etc/keepalived/keepalived.conf
# This file is generated by cephadm.
vrrp_script check_backend {
    script "/usr/bin/curl http://localhost:1967/health"
    weight -20
    interval 2
    rise 2
    fall 2
}

vrrp_instance VI_0 {
  state MASTER
  priority 100
  interface ens33
  virtual_router_id 50
  advert_int 1
  authentication {
      auth_type PASS
      auth_pass umubwzqwgsnyckfooqze
  }
  unicast_src_ip 192.168.100.10
  unicast_peer {
  }
  virtual_ipaddress {
    192.168.100.201/24 dev ens33
  }
  track_script {
      check_backend
  }
}
  • haproxy的配置文件: /var/lib/haproxy/haproxy.cfg
# This file is generated by cephadm.
global
    log         127.0.0.1 local2
    chroot      /var/lib/haproxy
    pidfile     /var/lib/haproxy/haproxy.pid
    maxconn     8000
    daemon
    stats socket /var/lib/haproxy/stats

defaults
    mode                    http
    log                     global
    option                  httplog
    option                  dontlognull
    option http-server-close
    option forwardfor       except 127.0.0.0/8
    option                  redispatch
    retries                 3
    timeout queue           20s
    timeout connect         5s
    timeout http-request    1s
    timeout http-keep-alive 5s
    timeout client          1s
    timeout server          1s
    timeout check           5s
    maxconn                 8000

frontend stats
    mode http
    bind *:1967
    bind localhost:1967
    stats enable
    stats uri /stats
    stats refresh 10s
    stats auth admin:vdbusxzrjnghoxjjtpzw
    http-request use-service prometheus-exporter if { path /metrics }
    monitor-uri /health

frontend frontend
    bind *:80
    default_backend backend

backend backend
    option forwardfor
    balance static-rr
    option httpchk HEAD / HTTP/1.0
    server rgw.rgw.ubuntu-20-04-lts.clsfte 192.168.100.10:8081 check weight 100
    server rgw.rgw.ubuntu-20-04-lts.fkhojn 192.168.100.10:8080 check weight 100

nfs ingress自动生成的配置

  • keepalived的配置文件:/etc/keepalived/keepalived.conf
# This file is generated by cephadm.
vrrp_script check_backend {
    script "/usr/bin/curl http://localhost:1968/health"
    weight -20
    interval 2
    rise 2
    fall 2
}

vrrp_instance VI_0 {
  state MASTER
  priority 100
  interface ens33
  virtual_router_id 50
  advert_int 1
  authentication {
      auth_type PASS
      auth_pass spzhspekgwlbhubpieoc
  }
  unicast_src_ip 192.168.100.10
  unicast_peer {
  }
  virtual_ipaddress {
    192.168.100.204/24 dev ens33
  }
  track_script {
      check_backend
  }
}
  • haproxy的配置文件:/var/lib/haproxy/haproxy.cfg
# This file is generated by cephadm.
global
    log         127.0.0.1 local2
    chroot      /var/lib/haproxy
    pidfile     /var/lib/haproxy/haproxy.pid
    maxconn     8000
    daemon
    stats socket /var/lib/haproxy/stats

defaults
    mode                    tcp
    log                     global
    timeout queue           1m
    timeout connect         10s
    timeout client          1m
    timeout server          1m
    timeout check           10s
    maxconn                 8000

frontend stats
    mode http
    bind 192.168.100.204:1968
    bind localhost:1968
    stats enable
    stats uri /stats
    stats refresh 10s
    stats auth admin:yshkycetxdhgxwceukcn
    http-request use-service prometheus-exporter if { path /metrics }
    monitor-uri /health

frontend frontend
    bind 192.168.100.204:2049
    default_backend backend

backend backend
    mode        tcp
    balance     source
    hash-type   consistent
    server nfs.nfs.0 192.168.100.10:2050

 

标签:haproxy,ingress,stats,rgw,Pacific,192.168,timeout,http,backend
From: https://www.cnblogs.com/varden/p/17162226.html

相关文章

  • kubernetes之Ingress发布Dashboard(二)
    1.什么是DashboardDashboard是基于网页的Kubernetes用户界面。你可以使用Dashboard将容器应用部署到Kubernetes集群中,也可以对容器应用排错,还能管理集群资源。你......
  • 417. Pacific Atlantic Water Flow[Medium]
    417.PacificAtlanticWaterFlowThereisanmxnrectangularislandthatbordersboththePacificOceanandAtlanticOcean.ThePacificOceantouchestheisl......
  • Kubernetes Ingress 原理
    阅读本文前提条件:理解k8sService的大致原理;会照猫画虎地使用Ingress。原理概述Service可以供内部程序使用,若不在路由设备上配置相应规则,外部节点无法访问Service......
  • keycloak~LB到Ingress再到K8s的路径问题
    问题的产生对于我们的容器化部署项目keycloak来说,当它从云端负载均衡LB直接通过NodePort转发到keycloak时,没有任务问题,一切正常;缺点就是,运维人员要维护一大批端口,哪个端......
  • k8s~ingress限流机制
    Ingress限流限速的注解定义了对连接和传输速率的限制。这些可以用来减轻DDoS攻击。它采用了“漏斗”算法实现限制。主要参数nginx.ingress.kubernetes.io/limit-co......
  • cert manager搭配alidns-webhook实现ingress证书签发
    安装certmanager如果已经安装certmanager则不用执行这一步helminstall\cert-managerjetstack/cert-manager\--namespacecert-manager\--create-name......
  • 07-存储服务测试(Ceph Pacific)
    1.块存储服务测试1.1查看镜像列表rbdlist1.2映射镜像格式:rbddevicemap{pool-name}/{image-name}--id{user-name}示例:rbddevicemaprbd/myimage--idadmin......
  • 06-配置CRUSH MAP(Ceph Pacific)
    1.添加rootbucketcephosdcrushadd-bucketopenstackrootcephosdcrushadd-bucketk8srootcephosdcrushadd-bucketcephfsrootcephosdcrushadd-bucketrgw......
  • 04-参数优化(Ceph Pacific)
    1.操作系统#cat/etc/sysctl.conf#sysctlsettingsaredefinedthroughfilesin#/usr/lib/sysctl.d/,/run/sysctl.d/,and/etc/sysctl.d/.##Vendorssettingsli......
  • 01-服务器RAID配置(Ceph Pacific)
    1.进入服务器RAID配置界面的方法1.1PCH(集成南桥)组RAIDUEFI启动模式:在服务器启动过程中,根据提示按Delete/Esc,进入BIOSSetup界面。Legacy启动模式:在服务器启动过程中,根......