Difference between revisions of "MigrateToCinder"
(note db gotchas, iscsi target import) |
|||
Line 12: | Line 12: | ||
# create empty database tables with <code><nowiki>cinder-manage db sync</nowiki></code> | # create empty database tables with <code><nowiki>cinder-manage db sync</nowiki></code> | ||
# copy over volume tables using `cinder-manage migrate import_db --src=$NOVA_SQL_CONN --dest=$CINDER_SQL_CONN` | # copy over volume tables using `cinder-manage migrate import_db --src=$NOVA_SQL_CONN --dest=$CINDER_SQL_CONN` | ||
+ | |||
+ | '''NOTE:''' Do not include the database names in --src or --dest; cinder-manage assumes your source database is named "nova" and that your destination database is named "cinder", and appends these to the strings you supply. | ||
+ | |||
+ | # copy over iSCSI target information with <code><nowiki> cinder-manage migrate copy_ptgt_files --src=/var/lib/nova-volume/volumes --dest=/var/lib/cinder/volumes </nowiki></code> | ||
# set the correct volume api class in nova.conf `volume_api_class=nova.volume.cinder.API` | # set the correct volume api class in nova.conf `volume_api_class=nova.volume.cinder.API` | ||
# disable the nova-volume-api in enabled apis in /etc/nova/nova.conf <code><nowiki>sed -i "s/osapi_volume,// /etc/nova/nova.conf"</nowiki></code>, if you do not have enabled_apis set explicitly set it to `enabled_apis=ec2,osapi_compute,metadata` as osapi_volume is included by default | # disable the nova-volume-api in enabled apis in /etc/nova/nova.conf <code><nowiki>sed -i "s/osapi_volume,// /etc/nova/nova.conf"</nowiki></code>, if you do not have enabled_apis set explicitly set it to `enabled_apis=ec2,osapi_compute,metadata` as osapi_volume is included by default |
Revision as of 03:03, 25 January 2013
Migrate From Nova-Volumes to Cinder
The process for migrating from nova-volumes to cinder is as follows.
- upgrade nova install to folsom
- upgrade nova database using `nova-manage db sync`
- install folsom version of Cinder
- create a cinder user in keystone as an admin in services tenant and edit '/etc/cinder/api-past.ini' to reflect the correct `admin_user`,`admin_tenant_name`, and `admin_password`
- create Cinder database and database user
- check that `sql_connection` in `/etc/cinder/cinder.conf` is correct
- create empty database tables with
cinder-manage db sync
- copy over volume tables using `cinder-manage migrate import_db --src=$NOVA_SQL_CONN --dest=$CINDER_SQL_CONN`
NOTE: Do not include the database names in --src or --dest; cinder-manage assumes your source database is named "nova" and that your destination database is named "cinder", and appends these to the strings you supply.
- copy over iSCSI target information with
cinder-manage migrate copy_ptgt_files --src=/var/lib/nova-volume/volumes --dest=/var/lib/cinder/volumes
- set the correct volume api class in nova.conf `volume_api_class=nova.volume.cinder.API`
- disable the nova-volume-api in enabled apis in /etc/nova/nova.conf
sed -i "s/osapi_volume,// /etc/nova/nova.conf"
, if you do not have enabled_apis set explicitly set it to `enabled_apis=ec2,osapi_compute,metadata` as osapi_volume is included by default - restart nova-api
- start cinder-api
- be sure that `/etc/tgt/conf.d/cinder.conf` exists and has an include line that matches
volumes_dir
option in `cinder.conf` in the default case this is `include /var/lib/cinder/volumes/*`, if you edit this file restart the tgtd service