From Fedora Project Wiki
No edit summary |
(remove from cloud SIG category) |
||
| (3 intermediate revisions by 3 users not shown) | |||
| Line 5: | Line 5: | ||
* Change glance configuration to use keystone: | * Change glance configuration to use keystone: | ||
$> sudo openstack-config-set /etc/glance/glance-api.conf paste_deploy flavor keystone | $> sudo openstack-config-set /etc/glance/glance-api.conf paste_deploy flavor keystone | ||
$> sudo openstack-config-set /etc/glance/glance-api-paste.ini filter:authtoken admin_tenant_name service | |||
$> sudo openstack-config-set /etc/glance/glance-api-paste.ini filter:authtoken admin_user glance | |||
$> sudo openstack-config-set /etc/glance/glance-api-paste.ini filter:authtoken admin_password servicepass | |||
$> sudo openstack-config-set /etc/glance/glance-registry.conf paste_deploy flavor keystone | $> sudo openstack-config-set /etc/glance/glance-registry.conf paste_deploy flavor keystone | ||
$> sudo openstack-config-set /etc/glance/glance- | $> sudo openstack-config-set /etc/glance/glance-registry-paste.ini filter:authtoken admin_tenant_name service | ||
$> sudo openstack-config-set /etc/glance/glance-registry-paste.ini filter:authtoken | $> sudo openstack-config-set /etc/glance/glance-registry-paste.ini filter:authtoken admin_user glance | ||
$> sudo openstack-config-set /etc/glance/glance-registry-paste.ini filter:authtoken admin_password servicepass | |||
Start and enable the Glance API and registry services: | Start and enable the Glance API and registry services: | ||
| Line 16: | Line 19: | ||
|results= | |results= | ||
Check that the services are running: | |||
$> for svc in api registry; do systemctl status openstack-glance-$svc.service; done | |||
And check for errors in the logs: | |||
$> grep -i error /var/log/glance/*.log | |||
Check that the glance CLI works: | Check that the glance CLI works: | ||
$> glance index | $> glance index | ||
}} | }} | ||
[[Category:OpenStack Test Cases]] | [[Category:OpenStack Test Cases]] | ||
Latest revision as of 06:16, 25 April 2012
Description
Test that the Glance API and registry services start without error.
Setup
Follow QA:Testcase_setup_OpenStack_Nova.
How to test
- Change glance configuration to use keystone:
$> sudo openstack-config-set /etc/glance/glance-api.conf paste_deploy flavor keystone $> sudo openstack-config-set /etc/glance/glance-api-paste.ini filter:authtoken admin_tenant_name service $> sudo openstack-config-set /etc/glance/glance-api-paste.ini filter:authtoken admin_user glance $> sudo openstack-config-set /etc/glance/glance-api-paste.ini filter:authtoken admin_password servicepass $> sudo openstack-config-set /etc/glance/glance-registry.conf paste_deploy flavor keystone $> sudo openstack-config-set /etc/glance/glance-registry-paste.ini filter:authtoken admin_tenant_name service $> sudo openstack-config-set /etc/glance/glance-registry-paste.ini filter:authtoken admin_user glance $> sudo openstack-config-set /etc/glance/glance-registry-paste.ini filter:authtoken admin_password servicepass
Start and enable the Glance API and registry services:
$> for svc in api registry; do sudo systemctl start openstack-glance-$svc.service; done $> for svc in api registry; do sudo systemctl enable openstack-glance-$svc.service; done
Expected Results
Check that the services are running:
$> for svc in api registry; do systemctl status openstack-glance-$svc.service; done
And check for errors in the logs:
$> grep -i error /var/log/glance/*.log
Check that the glance CLI works:
$> glance index