Project

General

Profile

Feature #10756

Developer API for the integration of remote execution plugin with other plugins/core

Added by Ivan Necas about 7 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Difficulty:
Triaged:
Bugzilla link:

Description

Ability to reuse the remote execution for Foreman core/katello/other feature-specific use-cases


Related issues

Related to Katello - Feature #7556: Feature Request: add "Start Time Window Option" for "Package Action - Update All"Rejected
Blocks Foreman Remote Execution - Feature #10757: Katello agent alternativeClosed2015-06-09
Blocked by Foreman Remote Execution - Feature #13240: Ability to render one job template from another, including importing inputs from the referenced templateClosed2016-01-15
Blocks Foreman Remote Execution - Feature #13500: PXE-less reprovision with rex and script templateReady For Testing2016-02-01

Associated revisions

Revision 9897f649 (diff)
Added by Ivan Necas over 6 years ago

fixes #10756 - developer api for registering features and templates

Any plugin (or core) and define a feature at initialization:

```
RemoteExecutionFeature.register(:reprovision, N_("Reprovision"),
:description => "Reprovision the host via script",
:provided_inputs => ["script"])
```

The mapping between the feature and templates can be made via
'Administer -> Remote Execution Features'.

```
composer = JobInvocationComposer.for_feature(:reprovision, host, :script => "grubby...")
composer.save!
composer.trigger
```

When seeding a template, there is a new meta `feature`, which allows
to assign some template as default to the specified feature.

The template mapping is now limited to just one template, but in future,
we can extend that to allow different mappings through organizations,
but lets keep it simple first.

History

#1 Updated by Ivan Necas about 7 years ago

#2 Updated by Marek Hulán almost 7 years ago

  • Target version set to 85

#3 Updated by Ivan Necas almost 7 years ago

The base is to implement http://theforeman.github.io/foreman_remote_execution/design/#DeveloperAPI
that allows mapping of features to job templates

#4 Updated by Ivan Necas almost 7 years ago

  • Status changed from New to Assigned
  • Assignee set to Ivan Necas

#5 Updated by Ivan Necas almost 7 years ago

  • Target version changed from 85 to 87

#6 Updated by Ivan Necas almost 7 years ago

  • Target version changed from 87 to 92

#7 Updated by Ivan Necas over 6 years ago

  • Target version changed from 92 to 97

#8 Updated by Marek Hulán over 6 years ago

  • Related to Feature #7556: Feature Request: add "Start Time Window Option" for "Package Action - Update All" added

#9 Updated by Ivan Necas over 6 years ago

  • Blocked by Feature #13240: Ability to render one job template from another, including importing inputs from the referenced template added

#10 Updated by Ivan Necas over 6 years ago

  • Target version changed from 97 to 98

#11 Updated by Ivan Necas over 6 years ago

  • Blocks Feature #13500: PXE-less reprovision with rex and script template added

#12 Updated by The Foreman Bot over 6 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/foreman_remote_execution/pull/144 added

#13 Updated by The Foreman Bot over 6 years ago

  • Pull request https://github.com/theforeman/foreman_remote_execution/pull/148 added

#14 Updated by Ivan Necas over 6 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#15 Updated by Marek Hulán over 6 years ago

  • Legacy Backlogs Release (now unused) set to 125

Also available in: Atom PDF