Closed Bug 1260788 Opened 9 years ago Closed 9 years ago

[remo] Use virtualenv in all remo deployments

Categories

(Infrastructure & Operations Graveyard :: WebOps: Engagement, task)

Product:
Infrastructure & Operations Graveyard
Component:
WebOps: Engagement
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: nemo-yiannis, Assigned: ericz)

Details

(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/2778] )

Hi, we are doing some maintenance in reps.mozilla.org (because of the Django 1.8 upgrade) and we would like to remove all vendor/vendor-local dependencies and use virtualenv instead. Can you verify if we are already using virtualenv in the new generic python cluster? If not how can we coordinate to use virtualenv for our pip dependencies. Thank you!
Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/2778]
Assignee: server-ops-webops → eziegenhorn
Yes, reps has a virtualenv throughout the python cluster and apache is using python from it! It looks like the old vendor/vendor-local directories still exist though. I can remove those if you'd like.
Hi Eric, No need to remove vendor and vendor-local since the project still uses them. We wanted to verify if there is a virtualenv in the python cluster for the project. Since there is, I am marking this bug as resolved. When we complete the upgrade, we are going to open another bug for the removal of vendor and vendor-local. Thanks!
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.