Bifrost should build and install components into a VENV
Bifrost presently installs a number of python packages across the system. It is in the best interest of bifrost moving forward to isolate the possibly incompatible with other components python code into a venv. This will enable cleaner downstream adoption, while hopefully allowing for cleaner delineation between OS components and python based components, like Ansible, Shade, Ironic, python-
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Julia Kreger
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Is "cut over to venv installation as default" an appropriate work item for this blueprint?
Work Items
Work items:
Create VENV, possibly using setup-env: DONE
Install, and make use of Ansible, including required python libs (ironicclient, shade), in the VENV: DONE
Move Ironic installation into the VENV: DONE
Ensure documentation indicates that we've moved the installation to a VENV, and help direct a user how to load that specific context: DONE
Remove reference to the Ansible hacking env script since ansible will be installed in the VENV context: DONE
