Issue #16295 has been updated by Charlie Sharpsteen.

Redmine Issue [#16295](http://projects.puppetlabs.com/issues/16295) has been 
migrated to JIRA:

  <https://tickets.puppetlabs.com/browse/MCO-52>


----------------------------------------
Bug #16295: actions should support always being background or foreground 
through the ddl
https://projects.puppetlabs.com/issues/16295#change-101432

* Author: R.I. Pienaar
* Status: Accepted
* Priority: Normal
* Assignee: R.I. Pienaar
* Category: SimpleRPC
* Target version: 2.3.x
* Keywords: 
* Branch: 
* Affected mCollective version: 
----------------------------------------
there are actions that would simply be bad to run in the foreground like yum 
update or puppet agent --test, if an agent want to add actions for this style 
of command they should be able to force in the DDL that these should always be 
run in async.

The behaviour would be something like:

<pre>
mco rpc package yum_update
Action scheduled for background execution with id: 
93db89f4ba575b09804ea91197222cd5
</pre>

What will happen is the servers will then schedule a background job for this 
action and potentially splay them out over some configured default interval.  

For this ticket though we just need the metadata in the DDL to indicate forced 
background or forced foreground actions.


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to