<div dir="ltr">Just to support what's been said:<div><br></div><div>User-scheduled actions are definitely out for pulp 3. We'll encourage other ways of accomplishing that. In the Foreman environment for example, they already have their own scheduler to use.</div><div><br></div><div>When a user requests a task to be run, Pulp will still run it in a similar way to Pulp 2. For example when a user says "sync this repo right now", Pulp will still create a task that has a similar lifecycle to what you're familiar with. What Pulp 3 will no longer offer is the ability to say "sync this every night at 2am" or "sync this at some specific point in the future".</div><div><br></div><div>Consumer management will be limited to what's necessary for applicability calculation. Pulp (whether a part of the core API or a separate service we make) will need to know about consumers and what repos they are bound to, but there will be no interaction with the consumers directly. Pulp will not manage them. There will need to be some endpoints somewhere to allow CRUD on consumers, their profiles, and their bindings. There will also need to be endpoints somewhere for initiating calculation of applicability and retrieving the results. But we haven't decided where exactly that will live.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 5, 2017 at 2:20 PM, Austin Macdonald <span dir="ltr"><<a href="mailto:austin@redhat.com" target="_blank">austin@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Schedule actions are also out of Pulp 3 (I think). There is a generic tasks api, which already includes start and finish times.<div><br></div><div><div> {</div><div> "_href": "<a href="http://pulp3.dev:8000/api/v3/tasks/8a1fc85f-6f74-47b0-b47a-fc5e468ca095/" target="_blank">http://pulp3.dev:8000/api/v3/<wbr>tasks/8a1fc85f-6f74-47b0-b47a-<wbr>fc5e468ca095/</a>",</div><div> "error": null,</div><div> "finished_at": "2017-10-03T20:09:29.099491Z",</div><div> "group": null,</div><div> "non_fatal_errors": [],</div><div> "parent": null,</div><div> "progress_reports": [],</div><div> "started_at": "2017-10-03T20:09:29.078859Z",</div><div> "state": "completed",</div><div> "tags": [],</div><div> "worker": "<a href="http://pulp3.dev:8000/api/v3/workers/reserved_resource_worker_2@pulp3.dev/" target="_blank">http://pulp3.dev:8000/api/v3/<wbr>workers/reserved_resource_<wbr>worker_2@pulp3.dev/</a>"</div><div> }</div></div><div><br></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 5, 2017 at 2:15 PM, Og Maciel <span dir="ltr"><<a href="mailto:omaciel@redhat.com" target="_blank">omaciel@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On Thu, Oct 5, 2017 at 2:13 PM, Austin Macdonald <<a href="mailto:austin@redhat.com" target="_blank">austin@redhat.com</a>> wrote:<br>
> Consumers are not going to be a part of Pulp 3 (except for calculating<br>
> applicability), so we don't need to worry about #3041 regarding Pulp3.<br>
<br>
</span>But isn't the Task api generic and includes other types of scheduled actions?<br>
<div class="m_-6083559108459980022HOEnZb"><div class="m_-6083559108459980022h5">--<br>
Og Maciel<br>
<br>
Senior Manager, Quality Engineering<br>
Red Hat, Inc.<br>
irc: omaciel<br>
</div></div></blockquote></div><br></div>
</div></div><br>______________________________<wbr>_________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/pulp-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><p style="color:rgb(0,0,0);font-family:overpass-mono,monospace;font-size:10px;margin:0px!important;padding:0px!important"><span style="margin:0px!important;padding:0px!important">Michael</span> <span style="margin:0px!important;padding:0px!important">Hrivnak</span></p><p style="color:rgb(0,0,0);font-family:overpass-mono,monospace;font-size:10px;margin:0px!important;padding:0px!important"></p><span style="color:rgb(0,0,0);font-family:overpass-mono,monospace;font-size:10px;margin:0px!important;padding:0px!important"><span style="margin:0px!important;padding:0px!important">Principal Software Engineer</span><span style="margin:0px!important;padding:0px!important">, <span style="margin:0px!important;padding:0px!important">RHCE</span></span> </span><span style="color:rgb(0,0,0);font-family:overpass-mono,monospace;font-size:10px"></span><br style="color:rgb(0,0,0);font-family:overpass-mono,monospace;font-size:10px;margin:0px!important;padding:0px!important"><p style="color:rgb(0,0,0);font-family:overpass-mono,monospace;font-size:10px;margin:0px!important;padding:0px!important">Red Hat</p></div></div>
</div>