18. 이번에는 cinder-scheduler 서비스를 재시작하고 정상적으로 실행되는지 status를 확인합니다.
root@controller:~# service cinder-scheduler restart root@controller:~# service cinder-scheduler status ● cinder-scheduler.service - OpenStack Cinder Scheduler Loaded: loaded (/lib/systemd/system/cinder-scheduler.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2016-05-31 23:45:20 KST; 5s ago Process: 21854 ExecStartPre=/bin/chown cinder:cinder /var/lock/cinder /var/ log/cinder /var/lib/cinder (code=exited, status=0/SUCCESS) Process: 21849 ExecStartPre=/bin/mkdir -p /var/lock/cinder /var/log/cinder / var/lib/cinder (code=exited, status=0/SUCCESS) Main PID: 21858 (cinder-schedule) Tasks: 1 Memory: 102.7M CPU: 1.465s CGroup: /system.slice/cinder-scheduler.service └─21858 /usr/bin/python /usr/bin/cinder-scheduler –config-file=/etc/ cinder/cinder.conf –log-file=/var/log/cinder/cinder-scheduler.log
May 31 23:45:20 controller systemd[1]: Started OpenStack Cinder Scheduler. May 31 23:45:21 controller cinder-scheduler[21858]: Option “verbose” from group “DEFAULT” is deprecated for removal. Its value may be silently ignored in the future.