Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Create a SEAPATH flasher USB key.

  • Clone the revision that will be release of SEAPATH Ansible

  • Set up the Ansible inventory for

    • Standalone machine

    • Cluster

      • 2 hypervisors

      • 1 observer

      • 1 VM

  • Flash and validate a standalone hypervisor

    • Flash a machine with the built standalone release image using the flasher.

    • Boot the newly flashed machine, check that it is reachable from SSH.

    • Ansible configuration → Use the revision that will be release of SEAPATH Ansible

      • Set up the Ansible inventory for the standalone test machine

    • Configure the standalone hypervisor: cqfd run ansible-playbook --limit standalone_machine -i <inventory-to-use> playbooks/seapath_setup_main.yaml

    • Check that cukinia tests succeed : sudo cukinia

  • Deploy and validate SEAPATH guest VM on a standalone machine

    • Using the SEAPATH guest VM previously built, deploy it in the cluster

      • cqfd run ansible-playbook playbooks/deploy_vms_standalone.yaml -i <path-to-inventory>

    • Open a console in the VM (vm-mgr console or via SSH)

    • Check that cukinia test tests succeed: sudo cukinia

  • Flash and validate a cluster hypvervisors and observer

    • Flash a SEAPATH cluster: 2 hypervisors and 1 observer

    • Boot the newly flashed machine, check that it is reachable from SSH

    • Run Ansible setup on the SEAPATH cluster

      • Set up the Ansible inventory for the cluster

      • Configure the cluster cqfd run ansible-playbook --limit cluster_machines playbooks/seapath_setup_main.yaml

    • Check that cukinia test tests succeed on hypervisors and observer : sudo cukinia

  • Run Cukinia tests

    • Run Cukinia’s test on a VM

  • Deploy a standalone VM

  • Deploy a VM in a clusterDeploy and validate SEAPATH guest VM in a cluster

    • Using the SEAPATH guest VM previously built, deploy it in the cluster

      • cqfd run ansible-playbook playbooks/deploy_vms_cluster.yaml -i <path-to-inventory>

    • Open a console in the VM (vm-mgr console or via SSH)

    • Check that cukinia tests succeed: sudo cukinia

    • Test VM migration

      • sudo crm ressource move <vm-name> <destination-node>

Debian

TODO