5.1.2

Changes for 5.1.2

Changes to branch 5.1 after version 5.1.1.

Commits

• enable rockylinux support in circle-ci - by shipyard
• update shipyard config to support rockylinux - by shipyard

5.2.1

Changes for 5.2.1

Changes to branch 5.2 after version 5.2.0.

Commits

• enable rockylinux support in circle-ci - by shipyard
• update shipyard config to support rockylinux - by shipyard

5.3.2

Changes for 5.3.2

Changes to branch 5.3 after version 5.3.1.

Commits

• enable rockylinux support in circle-ci - by shipyard
• update shipyard config to support rockylinux - by shipyard

5.3.1

Changes for 5.3.1

Changes to branch 5.3 after version 5.3.1.

Commits

5.2.0

Changes for 5.2.0

Changes to branch 5.2 after version 5.2.

Commits

• updated .shipyard.yml to branch 5.2 - by shipyard

• Update .shipyard.yml - by Sean Wysor

• Fix sbin scripts for Grep v3+ - by Daniel Finke

  It seems when using Grep v3+ (not exactly sure on the breaking change version), that the NUL characters separating args in /proc/$PID/cmdline don't match the [^\-] character class. This means that the beam PIDs can't be found. This PR uses tr to replace the NUL characters with spaces so the grep succeeds. Tested backwards-compatibility with Grep v2.

  Also DRY'd up the PID find with a shared function and ran these changes thru ShellCheck.

• updating .shipyard.yml - by swysor

• updating exposure - by pklinus

  https://2600hz.slack.com/archives/CH9JJLZED/p1650330312728559

5.1.1

Changes for 5.1.1

Changes to branch 5.1 after version 5.1.0.

Commits

• Update .shipyard.yml - by pklinus

5.1.0

Changes for 5.1.0

Changes to branch 5.1 after version 5.1.

Commits

• Update .shipyard.yml - by Sean Wysor

• trigger master build - by bitbashing

• trigger master build - by bitbashing

• trigger master build - by bitbashing

• trigger master build - by bitbashing

• HELP-34245: Fixed sudoers commands running on non-sudo user when executed by systemd - by swysor

  Because systemd runs the kazoo-applications command as the kazoo user, if you restart kazoo-applications via systemctl it will throw the following error in the journal logs.

  Feb 07 21:56:04 apps001.nyc.testkazoo.com sudo[26475]: kazoo : user NOT in sudoers ; TTY=unknown ; PWD=/opt/kazoo ; USER=kazoo ; COMMAND=/opt/kazoo/bin/kazoo pid

  This fix selectively runs sudo ONLY when the user is not kazoo.

• add an annotated config example - by James Aimonetti

• Update config.ini - by Carlos Recinos

  The purpose of this PR is for make a compliance between the git file and the file deployed by cluster manager

• KZOO-108: Do not decide BEAM process based on core count - by Harenson Henao

  SMP does not only depend on the numbers of cores on the running system, but it

  also depends on the flags passed to the Erlang VM when starting it so let us

  just get the pids for both beam and beam.smp processes and let the code

  filter/search (grep) for the desired VM as it is already doing.

  Prior to this change kazoo-[applications, ecallmgr] executables were failing

  when running on single core systems because it seems Erlang comes with SMP

  enabled by default and we don't check how many cores does the system has when

  starting our VMs so they are running with SMP enabled even on single core machines

  and that will brake the aforementioned executables because they would try to find

  pid for beam processes but again since they have SMP enabled they are beam.smp,

  thus, they will not be found and they will just reply: DESIRED_APP is not running.

• Add extra sinks' handlers - by James Aimonetti

• relocate ra to /opt/kazoo/var/lib/ra - by lazedo

  ** Note

  the init scripts ensure kazoo user owns /opt/kazoo -R

• update sys.config from kazoo rel dist.sys.config - by lazedo

• add ra dir to /etc/kazoo - by lazedo

5.0.5

Changes for 5.0.5

Changes to branch 5.0 after version 5.0.4.

Commits

• Fixed exposure in .shipyard.yml - by Sean Wysor

5.0.4

Changes for 5.0.4

Changes to branch 5.0 after version 5.0.3.

Commits

• KZOO-108: Do not decide BEAM process based on core count - by Harenson Henao

  SMP does not only depend on the numbers of cores on the running system, but it

  also depends on the flags passed to the Erlang VM when starting it so let us

  just get the pids for both beam and beam.smp processes and let the code

  filter/search (grep) for the desired VM as it is already doing.

  Prior to this change kazoo-[applications, ecallmgr] executables were failing

  when running on single core systems because it seems Erlang comes with SMP

  enabled by default and we don't check how many cores does the system has when

  starting our VMs so they are running with SMP enabled even on single core machines

  and that will brake the aforementioned executables because they would try to find

  pid for beam processes but again since they have SMP enabled they are beam.smp,

  thus, they will not be found and they will just reply: DESIRED_APP is not running.

5.0.3

Changes for 5.0.3

Changes to branch 5.0 after version 5.0.2.

Commits

• relocate ra to /opt/kazoo/var/lib/ra - by lazedo

  ** Note

  the init scripts ensure kazoo user owns /opt/kazoo -R