Clear django_session table

[Kevin Stevens]

Looks like mysql is getting pretty big thanks to the django_session table. These are not automatically cleared and must be manually purged per: https://docs.djangoproject.com/en/dev/topics/http/sessions/#clearing-the-session-store

Another cron job?

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/195220
Committed: https://git.openstack.org/cgit/stackforge/os-ansible-deployment/commit/?id=36378c5547a4c39db98994db61af68ee433ff943
Submitter: Jenkins
Branch: kilo

commit 36378c5547a4c39db98994db61af68ee433ff943
Author: Steve Lewis <email address hidden>
Date: Tue Jun 23 18:22:02 2015 -0700

    Clear expired Django sessions regularly from DB

    A random minute in the 21st hour UTC, daily, was chosen arbitrarily.
    That it is run on a single arbitrary host from the set was done to
    prevent unnecessary work being done until Bug #1424705 provides us with
    a cleaner solution.

    Adjusted to run once per day just to be sure that the operation doesn't
    lock the table for a meaningful duration.

    Making this configurable or tunable does not seem
    to be necessary at this time.

    Change-Id: I87164926a4d6a65d3c9f733d625a2d4af91c2597
    Closes-Bug: #1466126
    (cherry picked from commit 4ab949672428fda396d1d6a28149252dabc5655d)

[Bjoern (bjoern-t)]

FYI this has doc impact that we need to truncate table dash.django_session prior to running the 10.1.10 upgrade

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: juno
Review: https://review.openstack.org/197744

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/197744
Committed: https://git.openstack.org/cgit/stackforge/os-ansible-deployment/commit/?id=bdc5ef3d57580cf4a011bc276d7282f54a58900f
Submitter: Jenkins
Branch: juno

commit bdc5ef3d57580cf4a011bc276d7282f54a58900f
Author: Steve Lewis <email address hidden>
Date: Tue Jun 23 18:22:02 2015 -0700

    Clear expired Django sessions regularly from DB

    A random minute in the 21st hour UTC, daily, was chosen arbitrarily.
    That it is run on a single arbitrary host from the set was done to
    prevent unnecessary work being done until Bug #1424705 provides us with
    a cleaner solution.

    Adjusted to run once per day just to be sure that the operation doesn't
    lock the table for a meaningful duration.

    Making this configurable or tunable does not seem
    to be necessary at this time.

    Closes-Bug: #1466126

    Conflicts:
     playbooks/roles/os_horizon/tasks/horizon_db_setup.yml

    Change-Id: I87164926a4d6a65d3c9f733d625a2d4af91c2597
    (cherry picked from commit 4ab949672428fda396d1d6a28149252dabc5655d)

[Davanum Srinivas (DIMS) (dims-v)]

This issue was fixed in the openstack/openstack-ansible 11.2.11 release.

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/openstack-ansible 11.2.12 release.

[Davanum Srinivas (DIMS) (dims-v)]

This issue was fixed in the openstack/openstack-ansible 11.2.14 release.