Refactor #302
closed
Package nodes as core functionality of pulp-server instead of separate rpms
0%
Description
Currently Nodes is packages as 4 separate rpms. These should be collapsed into the core pulp-server rpms
pulp-nodes-common -> python-pulp-common
pulp-nodes-parent -> pulp-server
pulp-nodes-child -> pulp-server
pulp-nodes-admin-extensions -> pulp-admin-client
pulp-nodes-consumer-client -> pulp-admin-client * Currently the nodes consumer client depends on the pulp-consumer-client but it is only valid when run on a pulp-server. If we don't want to move the functionality purely to the admin client then it should be kept as a separate RPM until a major version release when it can be moved.
All of the old RPMs should be obsoleted in the spec file. The nodes directories within the project should be merged into the respective directories that match the components the RPMs are being merged into.
Updated by mhrivnak about 9 years ago
Can you make a case for the value this will bring vs. how much effort it will take? What would we really gain? I agree that it would be an improvement, but given the number of areas we want to invest in, and given that we may have an opportunity to re-work the whole nodes feature anyway, I'm not yet convinced that this is worth prioritizing. So, I invite you to convince me. :)
Updated by amacdona@redhat.com over 7 years ago
- Status changed from NEW to CLOSED - WONTFIX
Closed because Pulp 3.0 will be dropping nodes support.
.
Raise resource limits for worker container to avoid OOMKill
closes #302