https://github.com/antonym/osa-warp

Automation to warp from older versions of openstack-ansible to the latest
https://github.com/antonym/osa-warp

Last synced: about 2 months ago
JSON representation

Automation to warp from older versions of openstack-ansible to the latest

• Host: GitHub
• URL: https://github.com/antonym/osa-warp
• Owner: antonym
• Created: 2019-03-21T19:22:24.000Z (almost 6 years ago)
• Default Branch: master
• Last Pushed: 2019-05-03T18:04:41.000Z (over 5 years ago)
• Last Synced: 2024-10-15T11:21:36.728Z (3 months ago)
• Language: Shell
• Homepage:
• Size: 71.3 KB
• Stars: 0
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
## Openstack-Ansible Warp (osa-warp)

** WORK IN PROGRESS, experimental, not ready for Production yet **

Allows you to warp from one version of OSA to another rapidly

by handling all DB and configuration migrations across versions

first before running setup-openstack specific playbooks from

the target release.  This is useful for moving through the

upgrade processes quickly reducing potential failures from

moving through each version incrementally.

Stages:

* List of releases to do is determined.

* Control Plane is shutdown.

* Next release from currently running release is checked out

* Partial configuration and database migration is ran for that release.

* Next release is checked out... etc until all releases except target

  are completed.

* Final target OSA is checked out and regular run-upgrade.sh script is ran.

* Cleanup scripts for all previous upgrade scripts are ran to remove

  unused containers.

* Cloud is then upgraded to target release.

Currently supports warping more than one release across Newton, Ocata, 

Pike, Queens to Rocky on Ubuntu 16.04.  Must be at a Newton or greater

starting point running Ubuntu 16.04.

    git clone https://github.com/antonym/osa-warp.git /opt/osa-warp

    cd /opt/osa-warp

    # valid jumps (releases) are currently ocata, pike, queens, rocky

    ./osa-warp.sh 

TODO:

* Ensure all databases for services have been captured in migration scripts.

* Generate venvs for each latest stable release to use for migrations (or find

  a place where they are currently hosted with OpenStack to move away from

  using rpco-repo.

* Add future release support

* Squashing whatever bugs may be present... surely none of those exist...

Generating venvs to be used for migrations

```

# create an AIO and partially install to get venvs

export OSA_TAG=18.1.6

git clone --branch ${OSA_TAG} https://github.com/openstack/openstack-ansible.git /opt/openstack-ansible

cd /opt/openstack-ansible

scripts/bootstrap-ansible.sh

scripts/bootstrap-aio.sh

# copy aio files into place so all available venvs are built

cp /opt/openstack-ansible/etc/openstack_deploy/conf.d/*.yml.aio /etc/openstack_deploy/conf.d/

for f in $(ls -1 /etc/openstack_deploy/conf.d/*.aio); do mv -v ${f} ${f%.*}; done

openstack-ansible setup-hosts.yml

openstack-ansible setup-infrastructure.yml

# retrieve venvs from repo container

lxc-attach --name `lxc-ls repo_container` ls -la /var/www/repo/venvs/$OSA_TAG

```