Percona Xtradb Cluster implementation

Bug #1492202 reported by OpenStack Infra
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openstack-manuals
Fix Released
Medium
KATO Tomoyuki

Bug Description

https://review.openstack.org/208073
commit a94987f8ba399d14ab43b0ffb3a81c9795732058
Author: Craig Vyvial <email address hidden>
Date: Fri Jul 10 16:43:17 2015 -0500

    Percona Xtradb Cluster implementation

    Created the clustering implementation for Percona XtraDB Cluster
    Server. Used the existing framework for adding a new cluster strategy
    for percona. Created guestagent, api, and taskmanager calls to setup
    the cluster.

    Ran into a weird issue where creating the admin user was not being
    saved even though there was no error logged. I believe this was
    happening because mysql was technically up from the mysqladmin ping
    cmd but was not processing the grant call yet. I've heard that to be
    sure you should run a 'select 1;' call to verify that mysql is really
    ready after starting it. I added a method to verify this.

    PXC needs a few more ports opened up for the group comm, state
    transfer, and incremental state transfer. Added the percona
    cluster.cnf template file for the setting needed in PXC. When a
    joining instance first joins the cluster it syncs all the data using
    xtrabackup, this will cause the joining instance to lose its admin
    user os_admin. So we reset the admin to a new password across the
    board.

    Make Percona Xtradb Cluster a different datastore because there are
    muliple version of PXC. This has been tested with pxc 5.5 from the
    ubuntu repository.

    Adding coverage xml output in tox.ini

    DocImpact
    Adding a new datastore percona-xtradb-cluster(pxc) that should not
    have any special cases for create and delete cluster.

    Implements: blueprint support-pxc-56
    Change-Id: I239433f0491cea15b214c41ceecc3a5e72b5bbeb

Tags: trove
Revision history for this message
Joseph Robinson (joseph-r-email) wrote :
Changed in openstack-manuals:
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
KATO Tomoyuki (kato-tomoyuki) wrote :

This affects the trove contents as trove data store.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to openstack-manuals (master)

Fix proposed to branch: master
Review: https://review.openstack.org/261837

Changed in openstack-manuals:
assignee: nobody → KATO Tomoyuki (kato-tomoyuki)
status: Confirmed → In Progress
Changed in openstack-manuals:
assignee: KATO Tomoyuki (kato-tomoyuki) → Tom Fifield (fifieldt)
Changed in openstack-manuals:
assignee: Tom Fifield (fifieldt) → KATO Tomoyuki (kato-tomoyuki)
Changed in openstack-manuals:
milestone: none → mitaka
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-manuals (master)

Reviewed: https://review.openstack.org/261837
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=1c83abba6b2267919010dc8a8d6a8cf3c513676b
Submitter: Jenkins
Branch: master

commit 1c83abba6b2267919010dc8a8d6a8cf3c513676b
Author: KATO Tomoyuki <email address hidden>
Date: Sun Dec 27 22:04:55 2015 +0900

    [user-guides] Update the trove data stores

    http://git.openstack.org/cgit/openstack/trove/tree/trove/guestagent/dbaas.py

    Change-Id: Ic9ea8f95fc49e1a27709bebc0807dcee7d17ead8
    Closes-Bug: #1492202

Changed in openstack-manuals:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-manuals 15.0.0

This issue was fixed in the openstack/openstack-manuals 15.0.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.