summaryrefslogtreecommitdiffstats
path: root/extraconfig/tasks/major_upgrade_pacemaker_migrations.sh
blob: 164269dce9f2048c39b4c170a8ff0e617a9044fc (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
#!/bin/bash

# Special pieces of upgrade migration logic go into this
# file. E.g. Pacemaker cluster transitions for existing deployments,
# matching changes to overcloud_controller_pacemaker.pp (Puppet
# handles deployment, this file handles migrations).
#
# This file shouldn't execute any action on its own, all logic should
# be wrapped into bash functions. Upgrade scripts will source this
# file and call the functions defined in this file where appropriate.
#
# The migration functions should be idempotent. If the migration has
# been already applied, it should be possible to call the function
# again without damaging the deployment or failing the upgrade.

# If the major version of mysql is going to change after the major
# upgrade, the database must be upgraded on disk to avoid failures
# due to internal incompatibilities between major mysql versions
# https://bugs.launchpad.net/tripleo/+bug/1587449
# This function detects whether a database upgrade is required
# after a mysql package upgrade. It returns 0 when no major upgrade
# has to take place, 1 otherwise.
function is_mysql_upgrade_needed {
    # The name of the package which provides mysql might differ
    # after the upgrade. Consider the generic package name, which
    # should capture the major version change (e.g. 5.5 -> 10.1)
    local name="mariadb"
    local output
    local ret
    set +e
    output=$(yum -q check-update $name)
    ret=$?
    set -e
    if [ $ret -ne 100 ]; then
        # no updates so we exit
        echo "0"
        return
    fi

    local currentepoch=$(rpm -q --qf "%{epoch}" $name)
    local currentversion=$(rpm -q --qf "%{version}" $name)
    local currentrelease=$(rpm -q --qf "%{release}" $name)
    local newoutput=$(repoquery -a --pkgnarrow=updates --qf "%{epoch} %{version} %{release}\n" $name)
    local newepoch=$(echo "$newoutput" | awk '{ print $1 }')
    local newversion=$(echo "$newoutput" | awk '{ print $2 }')
    local newrelease=$(echo "$newoutput" | awk '{ print $3 }')

    # With this we trigger the dump restore/path if we change either epoch or
    # version in the package If only the release tag changes we do not do it
    # FIXME: we could refine this by trying to parse the mariadb version
    # into X.Y.Z and trigger the update only if X and/or Y change.
    output=$(python -c "import rpm; rc = rpm.labelCompare((\"$currentepoch\", \"$currentversion\", None), (\"$newepoch\", \"$newversion\", None)); print rc")
    if [ "$output" != "-1" ]; then
        echo "0"
        return
    fi
    echo "1"
}

function add_missing_openstack_core_constraints {
    # The CIBs are saved under /root as they might contain sensitive data
    CIB="/root/migration.cib"
    CIB_BACKUP="/root/backup.cib"
    CIB_PUSH_NEEDED=n

    rm -f "$CIB" "$CIB_BACKUP" || /bin/true
    pcs cluster cib "$CIB"
    cp "$CIB" "$CIB_BACKUP"

    if ! pcs -f "$CIB" constraint --full | grep 'start openstack-sahara-api-clone then start openstack-sahara-engine-clone'; then
        pcs -f "$CIB" constraint order start openstack-sahara-api-clone then start openstack-sahara-engine-clone
        CIB_PUSH_NEEDED=y
    fi

    if ! pcs -f "$CIB" constraint --full | grep 'start openstack-core-clone then start openstack-ceilometer-notification-clone'; then
        pcs -f "$CIB" constraint order start openstack-core-clone then start openstack-ceilometer-notification-clone
        CIB_PUSH_NEEDED=y
    fi

    if ! pcs -f "$CIB" constraint --full | grep 'start openstack-aodh-evaluator-clone then start openstack-aodh-listener-clone'; then
        pcs -f "$CIB" constraint order start openstack-aodh-evaluator-clone then start openstack-aodh-listener-clone
        CIB_PUSH_NEEDED=y
    fi

    if pcs -f "$CIB" constraint --full | grep 'start openstack-core-clone then start openstack-heat-api-clone'; then
        CID=$(pcs -f "$CIB" constraint --full | grep 'start openstack-core-clone then start openstack-heat-api-clone' | sed -e 's/.*id\://g' -e 's/)//g')
        pcs -f "$CIB" constraint remove $CID
        CIB_PUSH_NEEDED=y
    fi

    if [ "$CIB_PUSH_NEEDED" = 'y' ]; then
        pcs cluster cib-push "$CIB"
    fi
}

function remove_ceilometer_alarm {
    if pcs status | grep openstack-ceilometer-alarm; then
        # Disable pacemaker resources for ceilometer-alarms
        pcs resource disable openstack-ceilometer-alarm-evaluator
        check_resource openstack-ceilometer-alarm-evaluator stopped 600
        pcs resource delete openstack-ceilometer-alarm-evaluator
        pcs resource disable openstack-ceilometer-alarm-notifier
        check_resource openstack-ceilometer-alarm-notifier stopped 600
        pcs resource delete openstack-ceilometer-alarm-notifier

        # remove constraints
        pcs constraint remove ceilometer-delay-then-ceilometer-alarm-evaluator-constraint
        pcs constraint remove ceilometer-alarm-evaluator-with-ceilometer-delay-colocation
        pcs constraint remove ceilometer-alarm-evaluator-then-ceilometer-alarm-notifier-constraint
        pcs constraint remove ceilometer-alarm-notifier-with-ceilometer-alarm-evaluator-colocation
        pcs constraint remove ceilometer-alarm-notifier-then-ceilometer-notification-constraint
        pcs constraint remove ceilometer-notification-with-ceilometer-alarm-notifier-colocation

    fi

    # uninstall openstack-ceilometer-alarm package
    yum -y remove openstack-ceilometer-alarm

}