Change Details

As we continue to improve and grow the OpenStack control plane, the limitations around the number of database connections, tuning options and failover procedures included in the standard database configuration have become more of a concern. This task is to investigate the architecture and design for a highly available database that can be tuned specifically for the CloudVPS OpenStack services. ===== Update: We're going to move the OpenStack control plane to a galera cluster. The Galera cluster will be hosted on the cloudcontrol nodes, of which there are three in each deployment. codfw1dev: [x] Install and launch galera cluster [x] Move Glance db use to galera [x] Move 'labspuppet' db use to galera [x] Move Nova (+ nova_api + nova_cell0) db use to galera [x] Move Keystone db use to galera [x] Move Neutron db use to galera [x] Move Designate db use to galera eqiad1: [x] Install and launch galera cluster [x] Move Glance db use to galera [x] Move Nova (+ nova_api + nova_cell0) db use to galera [x] Move Keystone db use to galera [x] Move Neutron db use to galera [x] Move Designate db use to galera cleanup: [] mark m5 openstack databases read-only [] remove databases from backup jobs (if they're enumerated?) [] drop databases from m5

As we continue to improve and grow the OpenStack control plane, the limitations around the number of database connections, tuning options and failover procedures included in the standard database configuration have become more of a concern. This task is to investigate the architecture and design for a highly available database that can be tuned specifically for the CloudVPS OpenStack services. ===== Update: We're going to move the OpenStack control plane to a galera cluster. The Galera cluster will be hosted on the cloudcontrol nodes, of which there are three in each deployment. codfw1dev: [x] Install and launch galera cluster [x] Move Glance db use to galera [x] Move 'labspuppet' db use to galera [x] Move Nova (+ nova_api + nova_cell0) db use to galera [x] Move Keystone db use to galera [x] Move Neutron db use to galera [x] Move Designate db use to galera eqiad1: [x] Install and launch galera cluster [x] Move Glance db use to galera [x] Move Nova (+ nova_api + nova_cell0) db use to galera [x] Move Keystone db use to galera [x] Move Neutron db use to galera [x] Move Designate db use to galera cleanup: [] rename tables (as preamble to dropping) [] remove databases from backup jobs (if they're enumerated?) [] drop databases from m5

As we continue to improve and grow the OpenStack control plane, the limitations around the number of database connections, tuning options and failover procedures included in the standard database configuration have become more of a concern. This task is to investigate the architecture and design for a highly available database that can be tuned specifically for the CloudVPS OpenStack services. ===== Update: We're going to move the OpenStack control plane to a galera cluster. The Galera cluster will be hosted on the cloudcontrol nodes, of which there are three in each deployment. codfw1dev: [x] Install and launch galera cluster [x] Move Glance db use to galera [x] Move 'labspuppet' db use to galera [x] Move Nova (+ nova_api + nova_cell0) db use to galera [x] Move Keystone db use to galera [x] Move Neutron db use to galera [x] Move Designate db use to galera eqiad1: [x] Install and launch galera cluster [x] Move Glance db use to galera [x] Move Nova (+ nova_api + nova_cell0) db use to galera [x] Move Keystone db use to galera [x] Move Neutron db use to galera [x] Move Designate db use to galera cleanup: [] mark m5 openstack databases read-onlyrename tables (as preamble to dropping) [] remove databases from backup jobs (if they're enumerated?) [] drop databases from m5