plumbis / ansible-cumulus-upgrade Goto Github PK

View Code? Open in Web Editor NEW

10.0 10.0 2.0 40.07 MB

Zero Downtime Cumulus Upgrades with Ansible

Shell 0.68% Gherkin 0.82% Python 66.99% Ruby 31.51%

ansible-cumulus-upgrade's People

Contributors

Stargazers

Watchers

Forkers

jawhnycooke ahmedfathymahmoud

ansible-cumulus-upgrade's Issues

Update Behave Ansible API Calls

Ansible 2.0 does not support the ansible.runner() API calls. The solution is to use the Python subprocess.Popen() methods and run ad hoc commands.

In order to support Ansible 2.0 the behave tests will have to be updated to no longer use the Ansible Python API, but to call ad hoc commands and parse the output.

Change hosts from Vx Nodes to Ubuntu

Build initial fabric with hosts for L3

create playbook to run b-side upgrade process

layer 2: update Readme with final edits

still has residual layer 3 references. need to test and verify L2 works as expected before final edits

Update Playbooks to Ansible 2.0 Standards

Only change found so far is changing sudo: true to become: true.

build layer 2 configuration files

layer 2: baseline test network build

Create BGP Route Check

Add Behave check to validate that BGP advertised routes are learned on all nodes

Build initial fabric with hosts for L2

create image rollback playbook

Rolling Back after Using Binary Install
Select the alternate slot as the new primary slot. (The primary slot will be booted at the next reboot)
cumulus@switch$ sudo cl-img-select -s
Reboot the switch.
cumulus@switch$ sudo reboot

add the config restore playbook as a task/handler?

create playbook to drain traffic before upgrade

create behave check that traffic is drained

create image download and config file backup playbook

edit layer 2 vagrant files

Create behave checks that everything works in steady state

modify scenario to support l2/mlag

backup and restore playbooks - option for interfaces.d approach

need to backup and restore the entire directory vs just the single file in some cases. look into best approach to this.

create playbook to un-drain traffic

Create Fping Behave test

Use fping to create full mesh of loopback pings to validate connectivity.

Update routing in L3 demo to only send defaults to servers

Improve Documentation on interface_stats module

ansible hosts file - do we need one?

use ansible 2.0 rollback/on fail stuff to undo failed upgrade

Makefile / Run Script

Hi,

It would be great if you could add a run script of Makefile to this repo as from the README it looks like you are currently doing just a vagrant up, then Ansible-playbook to run the whole demo, but from the looks of it that will not call the tests.

If you included a simple run.sh or Makefile then you could wrap it into a full demo which I think would be very useful to see how the tests can interact with the playbooks and possible prevent the next play running should a test fail in the previous step.

Mark

layer 2: test configuration backup and restore

add CLAG backup ip to config

to eliminate split brain