From Fedora Project Wiki

(Essex to Folsom upgrade notes)
No edit summary
 
(5 intermediate revisions by 2 users not shown)
Line 3: Line 3:
''Setting upgrade expectations right: off-line upgrade with manual intervention!''
''Setting upgrade expectations right: off-line upgrade with manual intervention!''


Here are upgrade notes for upgrading simplest possible 2012.1.3 setup (all-in-one min.Nova+Glance+Keystone) to Folsom http://repos.fedorapeople.org/repos/openstack/openstack-folsom/epel-openstack-folsom.repo
Here are upgrade notes for upgrading simplest possible 2012.1.3 (Essex) setup (all-in-one minimal Nova+Glance+Keystone setup) to Folsom (now available in epel6)
 
'''If you want to stay on Essex use [http://repos.fedorapeople.org/repos/openstack/openstack-essex/README openstack-essex repo]
'''


* stop services
* stop services
Line 13: Line 16:
  service openstack-nova-scheduler stop
  service openstack-nova-scheduler stop
  service openstack-nova-api stop
  service openstack-nova-api stop
* If on a RHEL based system, manually update Django
rpm -e --nodeps Django
yum install Django14
* update RPMs
* update RPMs
  yum update openstack\* python\*client
  yum update openstack\* python\*client
* If using nova volumes, update tgtd config like:
sed -i '1iinclude /etc/nova/volumes/*' /etc/tgt/targets.conf
service tgtd restart
* merge configs, they're customized when deployed, so you'll get .rpmnew
* merge configs, they're customized when deployed, so you'll get .rpmnew
* /etc/keystone/
* /etc/keystone/
Line 26: Line 35:
   glance-api.conf.rpmnew      glance-registry.conf.rpmnew
   glance-api.conf.rpmnew      glance-registry.conf.rpmnew
   glance-api-paste.ini.rpmnew  glance-registry-paste.ini.rpmnew
   glance-api-paste.ini.rpmnew  glance-registry-paste.ini.rpmnew
mv glance-api.conf glance-api.conf.old
mv glance-api-paste.ini glance-api-paste.ini.old
mv glance-api.conf.rpmnew glance-api.conf
mv glance-api-paste.ini.rpmnew glance-api-paste.ini
  mv glance-registry.conf glance-registry.conf.old
  mv glance-registry.conf glance-registry.conf.old
  mv glance-registry-paste.ini glance-registry-paste.ini.old
  mv glance-registry-paste.ini glance-registry-paste.ini.old
Line 57: Line 70:
  service httpd restart
  service httpd restart
* test: http://localhost/dashboard
* test: http://localhost/dashboard
* configure new components: cinder, quantum
* configure new components: cinder, quantum. See test day config notes for [https://fedoraproject.org/wiki/QA:Testcase_Create_Cinder_Volumes cinder] and [https://fedoraproject.org/wiki/QA:Testcase_Quantum_V2#Setup quantum]
* nova-network to quantum migration script, should be on upstream TODO list: https://lists.launchpad.net/openstack/msg16469.html
* nova-network to quantum migration script, should be on upstream TODO list: https://lists.launchpad.net/openstack/msg16469.html

Latest revision as of 15:49, 22 November 2012

Essex to Folsom upgrade notes

Setting upgrade expectations right: off-line upgrade with manual intervention!

Here are upgrade notes for upgrading simplest possible 2012.1.3 (Essex) setup (all-in-one minimal Nova+Glance+Keystone setup) to Folsom (now available in epel6)

If you want to stay on Essex use openstack-essex repo

  • stop services
service openstack-keystone stop
service openstack-glance-api stop
service openstack-glance-registry stop
service openstack-nova-compute stop
service openstack-nova-network stop
service openstack-nova-scheduler stop
service openstack-nova-api stop
  • If on a RHEL based system, manually update Django
rpm -e --nodeps Django
yum install Django14
  • update RPMs
yum update openstack\* python\*client
  • If using nova volumes, update tgtd config like:
sed -i '1iinclude /etc/nova/volumes/*' /etc/tgt/targets.conf
service tgtd restart
  • merge configs, they're customized when deployed, so you'll get .rpmnew
  • /etc/keystone/
    • copy admin_token, [sql] connection from keystone.conf.old
  keystone.conf.rpmnew
mv keystone.conf keystone.conf.old
mv keystone.conf.rpmnew keystone.conf
  • /etc/glance/
    • copy admin_* from glance*paste.ini [filter:authtoken] to glance*.conf [keystone_authtoken]
    • verify sql_connection in both glance-registry.conf and glance-api.conf
  glance-api.conf.rpmnew       glance-registry.conf.rpmnew
  glance-api-paste.ini.rpmnew  glance-registry-paste.ini.rpmnew
mv glance-api.conf glance-api.conf.old
mv glance-api-paste.ini glance-api-paste.ini.old
mv glance-api.conf.rpmnew glance-api.conf
mv glance-api-paste.ini.rpmnew glance-api-paste.ini
mv glance-registry.conf glance-registry.conf.old
mv glance-registry-paste.ini glance-registry-paste.ini.old
mv glance-registry.conf.rpmnew glance-registry.conf
mv glance-registry-paste.ini.rpmnew glance-registry-paste.ini
  • /etc/nova/
    • copy admin_* from api-paste.ini [filter:authtoken] to nova.conf [keystone_authtoken]
    • verify sql_connection in nova.conf
  api-paste.ini.rpmnew  nova.conf.rpmnew
mv api-paste.ini api-paste.ini.old
mv api-paste.ini.rpmnew api-paste.ini
mv nova.conf nova.conf.old
mv nova.conf.rpmnew nova.conf
  • verify other configs you might have customized
e.g. /etc/openstack-dashboard/local_settings
  • update databases
keystone-manage db_sync
glance-manage db_sync
nova-manage db sync
  • start services
service openstack-keystone start
  • test: keystone user-list
service openstack-glance-api start
service openstack-glance-registry start
  • test: glance index
service openstack-nova-api start
service openstack-nova-scheduler start
service openstack-nova-compute start
service openstack-nova-network start
  • test: nova list
service httpd restart
Retrieved from "https://fedoraproject.org/w/index.php?title=Talk:Getting_started_with_OpenStack_EPEL&oldid=312127"