apiVersion:v1kind:Servicemetadata:name:wordpress-mysqllabels:app:wordpressspec:ports:- port:3306selector:app:wordpresstier:mysqlclusterIP:None---apiVersion:v1kind:PersistentVolumeClaimmetadata:name:mysql-pv-claimlabels:app:wordpressspec:accessModes:- ReadWriteOnceresources:requests:storage:5Gi---apiVersion:apps/v1# for versions before 1.9.0 use apps/v1beta2kind:Deploymentmetadata:name:wordpress-mysqllabels:app:wordpressspec:selector:matchLabels:app:wordpresstier:mysqlstrategy:type:Recreatetemplate:metadata:labels:app:wordpresstier:mysqlspec:containers:- image:mysql:5.6name:mysqlenv:- name:MYSQL_ROOT_PASSWORDvalueFrom:secretKeyRef:name:mysql-passkey:passwordports:- containerPort:3306name:mysqlvolumeMounts:- name:mysql-persistent-storagemountPath:/var/lib/mysqlvolumes:- name:mysql-persistent-storagepersistentVolumeClaim:claimName:mysql-pv-claim
EFS-AP模式指的是access point访问点模式。关于访问点的介绍:
EFS Access Points:
An access point applies an operating system user, group, and file system path to any file system request made using the access point. The access point’s operating system user and group override any identity information provided by the NFS client.
简单来讲,EFS-AP也就是access point访问点挂载模式下,efs客户端的路径user/gid是不可被修改的。的客户端用户只有使用权(读写),但是不可以修改owner。因此遇到的报错是该配置的预期表现。
apiVersion:v1kind:Servicemetadata:name:wordpress-mysqllabels:app:wordpressspec:ports:- port:3306selector:app:wordpresstier:mysqlclusterIP:None---apiVersion:v1kind:PersistentVolumeClaimmetadata:name:mysql-pv-claimlabels:app:wordpressspec:accessModes:- ReadWriteManyresources:requests:storage:5Gi---apiVersion:apps/v1# for versions before 1.9.0 use apps/v1beta2kind:Deploymentmetadata:name:wordpress-mysqllabels:app:wordpressspec:selector:matchLabels:app:wordpresstier:mysqlstrategy:type:Recreatetemplate:metadata:labels:app:wordpresstier:mysqlspec:securityContext:fsGroup:1014runAsUser:1014runAsGroup:1014containers:- image:mysql:5.6name:mysqlenv:- name:MYSQL_ROOT_PASSWORDvalueFrom:secretKeyRef:name:mysql-passkey:passwordports:- containerPort:3306name:mysqlvolumeMounts:- name:mysql-persistent-storagemountPath:/var/lib/mysqlvolumes:- name:mysql-persistent-storagepersistentVolumeClaim:claimName:mysql-pv-claim
检查
1
2
3
4
5
6
7
8
9
10
kubectl get pv|grep mysql pvc-f6622cb3-7c24-4172-a427-d4b9a9962cd8 5Gi RWX Delete Bound default/mysql-pv-claim efs-sc 5d23hkubectl get pvcNAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGEmysql-pv-claim Bound pvc-f6622cb3-7c24-4172-a427-d4b9a9962cd8 5Gi RWX efs-sc 5d23hkubectl get podNAME READY STATUS RESTARTS AGEwordpress-mysql-6f6455f449-52zrp 1/1 Running 0 5d7h
vim /etc/supervisord.conf
[include]files= /etc/supervisord.d/*.ini
1
2
3
supervisord -c /etc/supervisord.conf
/usr/bin/supervisorctl start all
/usr/bin/supervisorctl stop all
安装环境
1
2
cd webvirtmgr
pip install -r requirements.txt
1
./manage.py syncdb
创建用户
输入以下用户信息
1
2
3
4
5
6
7
8
9
10
11
You just installed Django's auth system, which means you don't have any superusers defined.
Would you like to create one now? (yes/no): yes
Username (leave blank to use 'root'): admin
Email address: 275301281@qq.com
Password: admin
Password (again):admin
Superuser created successfully.
Installing custom SQL ...
Installing indexes ...
Installed 6 object(s) from 1 fixture(s)./manage.py collectstatic
配置一个超级用户
1
./manage.py createsuperuser
1
2
3
4
5
6
WARNING:root:No local_settings file found.
Username (leave blank to use 'root'): yes
Email address: 275301281@qq.com
Password: Lenovo@123
Password (again): Lenovo@123
Superuser created successfully.
virsh -c qemu+tcp://IP_address/system nodeinfo
(virsh -c qemu+tcp://192.168.1.50/system nodeinfo)Please enter your authentication name: cnsre
Please enter your password: xxxxxx
CPU model: x86_64
CPU(s): 2CPU frequency: 2611 MHz
CPU socket(s): 1Core(s) per socket: 2Thread(s) per core: 1NUMA cell(s): 1Memory size: 2019260 kB
vim /etc/sysconfig/network-scripts/ifcfg-eno1s
TYPE="Ethernet"PROXY_METHOD="none"BROWSER_ONLY="no"BOOTPROTO="static"DEFROUTE="yes"IPV4_FAILURE_FATAL="YES"IPV6INIT="yes"IPV6_AUTOCONF="yes"IPV6_DEFROUTE="yes"IPV6_FAILURE_FATAL="no"IPV6_ADDR_GEN_MODE="stable-privacy"NAME="eno1"UUID="bb40d726-8d67-4187-90c3-eb61e1b42d61"DEVICE="eno1"ONBOOT="yes"IPADDR="192.168.1.130"NETAMSK=255.255.255.0
GATEWAY="192.168.1.254"DNS1="221.6.4.66"IPV6_PRIVACY="no"BRIDGE=br0
vim /etc/sysconfig/network-scripts/ifcfg-eno1s
TYPE="Ethernet"PROXY_METHOD="none"BROWSER_ONLY="no"BOOTPROTO="static"DEFROUTE="yes"IPV4_FAILURE_FATAL="YES"IPV6INIT="yes"IPV6_AUTOCONF="yes"IPV6_DEFROUTE="yes"IPV6_FAILURE_FATAL="no"IPV6_ADDR_GEN_MODE="stable-privacy"NAME="eno1"UUID="bb40d726-8d67-4187-90c3-eb61e1b42d61"DEVICE="eno1"ONBOOT="yes"IPADDR="192.168.1.130"NETAMSK=255.255.255.0
GATEWAY="192.168.1.254"DNS1="221.6.4.66"IPV6_PRIVACY="no"BRIDGE=br0
另外: 在划分区时,如果选择自定义,在redhat 6.X 之后要必须要新建 /boot/efi 分区.大小不能小于 100M 我在实际操作时设置了200M
原厂的解释是:
/boot/efi/ partition (100 MB minimum) — the partition mounted on /boot/efi/ contains all the installed kernels, the initrd images, and ELILO configuration files.