Actions
Story #938
closed
As a user, I want to initiate a node sync using the REST API on the child node.
Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:
Description
As a user, I want to initiate a node sync using the REST API on the node. This supports cases where no agent exists on the node.
This includes:
- Add a new API endpoint: /v2/nodes/<node_id>/actions/sync/
- Move node sync functionality in the node (agent) handler into the platform.
- The node handler will call the new API and return the result in a manner that ensure backwards compatibility.
Updated by jortel@redhat.com almost 9 years ago
- Subject changed from As a user, I want to initiate a node sync using the REST API on the node. to As a user, I want to initiate a node sync using the REST API on the child node.
Updated by mhrivnak almost 9 years ago
- Tracker changed from Issue to Story
- Tags Sprint Candidate added
Updated by bmbouter almost 9 years ago
- Sprint Candidate set to Yes
- Tags deleted (
Sprint Candidate)
Updated by mhrivnak almost 9 years ago
If this call is made, the receiving process is by definition on the child node, right? If so, the node_id is implicit and doesn't need to be part of the resource identifier.
This is an implementation detail, but I'm interested in considering something like "/v2/child_node/actions/sync/"
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.
Actions
.