How to do math in Ansible?

[ZillaYT]

I have an Ansible task that aims to upgrade our Gitlab application. I want the user to ONLY be able to upgrade 1 major release. For example, I want to enable a 8.x to 9.x upgrade, but not an 8.x to 10.x upgrade. I'm aware of the version_compare module, which I use, but need more than what it does.

I did write a filter that extracts the major, minor, patch versions of a Semver-format version so I can get the major part. But how do I then compare them to see if their difference is > 1? 

I do...

# NOTE: server_major is a filter I wrote to extract the major version of an M.m.p Semver-format version.
- name: Get major version of installed version
  set_fact: M_installed=installed_version|sermver_major
- name: Get the major version of the desired upgrade version
  set_fact: M_upgrade=upgrade_version|semver_major
- name: Ensure M_upgrade - M_installed = 1
  "How do I do this?"

Maybe there is a more straight-forward way to do this?

[Matt Martz]

Probably something like:

- name: Ensure M_upgrade - M_installed = 1

  assert:

    that:

      - M_upgrade|int - M_installed|int == 1 

--
You received this message because you are subscribed to the Google Groups "Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscribe@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/6a53fc0f-ce87-4f7a-8f6c-8a1d2a4014dd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Matt Martz
@sivel
sivel.net

[Kai Stian Olstad]

On Monday, 22 January 2018 18.18.34 CET ZillaYT wrote:
> I have an Ansible task that aims to upgrade our Gitlab application. I want
> the user to ONLY be able to upgrade 1 major release. For example, I want to
> enable a 8.x to 9.x upgrade, but not an 8.x to 10.x upgrade. I'm aware of
> the version_compare module, which I use, but need more than what it does.

If you are using apt I would suggest another way of solving this and that is pinning in apt

Just create a file /etc/apt/preferences.d/gitlab with the following content

Package: gitlab-ce
Pin: version /9.[0-9]+\.[0-9]+-/
Pin-Priority: 1000


You can read more about pinning here
https://wiki.debian.org/AptPreferences

--
Kai Stian Olstad

[ZillaYT]

I'm using yum (RHEL). However with this approach, don't you have to update the file when the major version changes?

[ZillaYT]

Thanks, I'l try this

On Monday, January 22, 2018 at 12:31:12 PM UTC-5, Matt Martz wrote:

Probably something like:

- name: Ensure M_upgrade - M_installed = 1

  assert:

    that:

      - M_upgrade|int - M_installed|int == 1 

On Mon, Jan 22, 2018 at 11:18 AM, ZillaYT <zil...@gmail.com> wrote:

I have an Ansible task that aims to upgrade our Gitlab application. I want the user to ONLY be able to upgrade 1 major release. For example, I want to enable a 8.x to 9.x upgrade, but not an 8.x to 10.x upgrade. I'm aware of the version_compare module, which I use, but need more than what it does.

I did write a filter that extracts the major, minor, patch versions of a Semver-format version so I can get the major part. But how do I then compare them to see if their difference is > 1? 

I do...

# NOTE: server_major is a filter I wrote to extract the major version of an M.m.p Semver-format version.
- name: Get major version of installed version
  set_fact: M_installed=installed_version|sermver_major
- name: Get the major version of the desired upgrade version
  set_fact: M_upgrade=upgrade_version|semver_major
- name: Ensure M_upgrade - M_installed = 1
  "How do I do this?"

Maybe there is a more straight-forward way to do this?

--
You received this message because you are subscribed to the Google Groups "Ansible Project" group.

To unsubscribe from this group and stop receiving emails from it, send an email to ansible-proje...@googlegroups.com.
To post to this group, send email to ansible...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/6a53fc0f-ce87-4f7a-8f6c-8a1d2a4014dd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Kai Stian Olstad]

On Monday, 22 January 2018 19.23.29 CET ZillaYT wrote:
> I'm using yum (RHEL). However with this approach, don't you have to update
> the file when the major version changes?

With that regex yes, it's a nice way to control upgrade to major versions.
And it also preventing upgrade of a package if someone should run apt dist-upgrade (equivalent to yum upgrade)


My file for Gitlab looks like this

$ more /etc/apt/preferences.d/gitlab
Package: gitlab-ce
Pin: version /[0-9]+\.[0-9]+\.([5-9]-|[0-9]{2,}-)/
Pin-Priority: 1000

It only upgrade if the package is x.y.5 or higher, the reason for this is Gitlab tends to be very buggy until around x.y.5 version is released.


--
Kai Stian Olstad