Skip to content

Releases: seapath/ansible

v1.1.3

17 Apr 07:40
@insatomcat insatomcat
v1.1.3
d326842
Compare
Choose a tag to compare
v1.1.3 Latest
Latest

Full Changelog: v1.1.2...v1.1.3

Revert "snmp: include the get snmp data logic directly into the expose script"
The pass_persist external script is blocking for snmpd, which means that everytime the data is gathered (which takes 20 seconds or so every 5 min), snmpd becomes totally unresponsive.
This is unacceptable. We will go back to the previous way of gathering data (cron job outside of snmpd), and solve the problem this creates but a different way.
This reverts commit d8e7692.

snmp: make snmp data genation atomic
The problem with data gathering with a cron job is that it's not synchronised with the pass_persist "refresh" logic. If the refesh happens during the 20s of the data gathering, then it will read an uncomplete /tmp/snmpdata.txt file.
To solve this, we make the generation of this file atomic, by writing to a temporary file and only at the end of the script rename the file in an atomic way.

snmp: add timestamp to data file

Assets 2
Loading

v1.1.2

07 Apr 11:35
@insatomcat insatomcat
v1.1.2
7972de4
Compare
Choose a tag to compare
v1.1.2

Full Changelog: v1.1.1...v1.1.2

fix file descriptor leak in vm_manager

snmp agent: reload after 1h
The perl snmp agent seems unstable after a few fays of running time. It still runs but does not update the snmp tree anymore.
We fix this by forcing snmpd to reload it after 1h, so that it stays fresh.

snmp: make virt-df.sh not chock on lvm snapshot volumes

expose snmp data: have a different interval than the cron job
If the cron job that get the snmp data and the expose script have the same interval (currently 300s = 5min), we encounter the risk that the generation of the snmp data file and the reading of that file always happen at the same time...
This commit set the interval of the expose script to 4min, so that we are sure those script don't run at the same time.

snmp: include the get snmp data logic directly into the expose script
If both logic use the same interval, there is the risk the interfere with each other.
If we set a different interval, sometime the expose script will run just after the getting of the data (and the exposed data will be fresh) or just before, in which case the data will be fresh again after 4+5min (9min).
For the data to be always fresh, it seems best to run the get_data script just before the expose refresh, so to include it in the script.
This makes the cron job useless, however since the expose script is run by snmp, we have to give the permission to the snmp user via sudo.

Loading

v1.1.1

13 Mar 11:56
@insatomcat insatomcat
v1.1.1
7e2945e
Compare
Choose a tag to compare
v1.1.1

Full Changelog: v1.1.0...v1.1.1

team0_x/OVS: move role and solves bug

This logic concerns all physical machines and not just hypervisor.
Plus, this commits adds Before= and After= condition for this logic to also work for a graceful host shutdown (before this commit, it only works for an ovs-vswitchd.service stop).

remove backup-restore on standalone
On standalone backup-restore does not make sense.

Revert "handlers: use udevadm trigger instead of restarting udev"
seapath/ansible-role-systemd-networkd#8

Loading

v1.1.0

25 Feb 15:33
@Revalioli Revalioli
v1.1.0
95ecf64
Compare
Choose a tag to compare
v1.1.0

Key features

  • Remove consolevm script, now replaced by vm-mgr console.
  • Add nostart options for VM deployment.
  • Update submodules to latest versions.

Bug fixes

  • Playbooks improvements for ansible-lint.
  • SEAPATH Debian: add missing capabilities for pacemaker service to fix live migration.
  • SEAPATH Yocto: always keep systemd-resolved.service enable to prevent dnsmasq.service to fail
  • Remove obsolete code.

API changes

Multiple variables are renamed with this release. Existing inventories should be updated accordingly:

  • tmpdir --> configure_ha_tmpdir (role configure_ha)
  • ptp_network_transport --> timemaster_ptp_network_transport (role timemaster)
  • ptp_delay_mechanism --> timemaster_ptp_delay_mechanism (role timemaster)
  • hugepages --> yocto_hugepages (role yocto/hugepages)
  • on existing debian installations, you need to install 3 packages for v1.1 to work properly:
    • python3-pip
    • python3-wheel
    • patch
      you can get those packages from the debian website, upload them to your servers and install them manually with dpkg, or use apt if you have connectivity to a debian mirror.

Known issues

  • SEAPATH Yocto: cukinia test "Check for file with no user and group" might fails #695

Changelog

Full Changelog: v1.0.0...v1.1.0

Contributors

dupremathieu, yairpod, and 3 other contributors
Loading

v1.0.0

23 Jan 13:51
@dupremathieu dupremathieu
v1.0.0
This tag was signed with the committer’s verified signature.
dupremathieu Mathieu Dupré
GPG key ID: 3E3900CFB4F4B42C
Verified
Learn about vigilant mode.
f6850b7
Compare
Choose a tag to compare
v1.0.0

Initial release

Key Features

  • Configure a SEAPATH cluster with 3 machines, supporting two configurations
    • Two hypervisors + one observer
    • Three hypervisors
  • Cluster features include:
    • VM disk redundancy via Ceph shared storage
    • Failover scenarios managed by Pacemaker
    • Network redundancy ensured by Open vSwitch
    • VM live migration across cluster machines
  • Set up SEAPATH network configurations, including:
    • Administration network
    • Cluster network
    • PTP network
    • Inter-VM communication network
    • Additional networks customized by the end user
  • Configure time synchonisation
    • PTP synchronisation
    • NTP synchronisation
    • Time forwarding to VMs
  • Implement additional cyber hardening for Debian (Yocto hardening managed in meta-seapath).
  • Provide a VM deployment interface for SEAPATH clusters or standalone machines, supporting:
    • Configurable Libvirt XML files
    • QCOW2 QEMU files
  • ABB SSC600 SW compatibility
Loading