Use Avanon Pyenv community role to install Pyenv

[danypr92]

Add default Pyenv vars to set the global Python interpreter to 3.8.2 and
the Odoo python interpreter to 3.7.7.

[enricostano]

@danypr92 @cesarlr how should we manage upgrades of existing Odoo instances related to this?

[cesarlr]

@danypr92 @cesarlr how should we manage upgrades of existing Odoo instances related to this?

It's a manual process, so we can only document it

[danypr92]

@danypr92 @cesarlr how should we manage upgrades of existing Odoo instances related to this?

I think that we can run the provision over these outdated servers and the new Python interpreter and virtualenv will be successfully installed. The old virtualenv remains in the server, but if we don't use them we can delete them in the future...

@enricostano are you asking by how we can use this new strategy in the old servers or how can we purge the old virtualenv strategy?

[enricostano]

I just want to understand what needs to be done to make an existent inventory compatible to this change. It seems that nothing, it's not a problem if the old venv will still be there IMHO.

Maybe we can just try the process later in local with some existing inventory.

[enricostano]

@cesarlr @danypr92 what about the systemd unit? Should we point to the pyenv venv binary now?

[danypr92]

@cesarlr @danypr92 what about the systemd unit? Should we point to the pyenv venv binary now?

We are updating the odoo_role_odoo_venv_path var to point to the new virtualenv. This var is used in the systemd unit to execute the correct Python interpreter:

odoo-role/defaults/main.yml

Line 30 in 636997c

odoo_role_odoo_python_path: "{{ odoo_role_odoo_venv_path }}/bin/python"

odoo-role/templates/odoo.service.j2

Line 7 in 89a2ad2

ExecStart={{ odoo_role_odoo_python_path }} {{ odoo_role_odoo_bin_path }} -c {{ odoo_role_odoo_config_path }}/odoo.conf --load-language='{{ odoo_role_loaded_languages }}'