Remove python-tripleoclient dependency on tripleo-common
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
Due to a Series Of Unfortunate Dependencies, installing the client currently causes dependencies such as Mistral itself to be installed (the tripleo-common -> Mistral part of the equation may partially be resolved by https:/
Even then, with the Mistral actions and workflows it seems like TripleO Common is more focused on server-side concerns, and shouldn't need to be pulled from the client. (This might need a larger discussion on "What is tripleo-common" at some point...)
A quick grep shows up a few places where it shows up:
- tripleoclient/
This only covers a few lines, may be ok to copy-paste over...
- tripleoclient/
In build overcloud image:
manager = build.ImageBuil
Not clear that this could be migrated to an action in a straightforward way.
1. Implement an action
2. Have the action put it in a temp swifturl
3. Have the client download from there?
We have support for this (https:/
- tripleoclient/
update.
I'm not very familiar with what it does, but it looks like 5 lines of code that calls to heatclient, so perhaps not the worst copy-pasted.
- tripleoclient/
update_manager = update_
update_
Not familiar with this either, but a name like "interactive update" makes it sound like it may be awkward to move...
- tripleoclient/
pw = password_
This one is complicated, because it's part of a new undercloud deploy mechanism where Mistral doesn't exist yet so we can't just wrap it into an action. It's too big and changeable (new passwords) to sensibly copy-paste.
Changed in tripleo: | |
milestone: | pike-2 → pike-3 |
Changed in tripleo: | |
milestone: | pike-3 → pike-rc1 |
Changed in tripleo: | |
milestone: | pike-rc1 → queens-1 |
Changed in tripleo: | |
milestone: | queens-1 → queens-2 |
Changed in tripleo: | |
milestone: | queens-2 → queens-3 |
Changed in tripleo: | |
milestone: | queens-3 → queens-rc1 |
Changed in tripleo: | |
milestone: | queens-rc1 → rocky-1 |
From the Pike PTG: should we add functional testing, this will also cause issues for supporting Python 3 functional testing (a Pike community goal) for the client, as we would need a Python 3 version of Mistral.