Add miq_worker_types table #437
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This table will be seeded to include all leaf subclasses of MiqWorker On the first pass it will be a replacement for the information currently stored in the MIQ_WORKER_TYPES constants, but will be extended to contain all the metadata concerning when workers of each type should be running (for example, required roles, worker scope, provider type, etc.) The ultimate goal is to separate out worker management into a standalone process distinct from the current code-base where a subset of models will be the primary API between the "worker orchestrator" and the server which will determine *how* to start the workers it was told to run. This will allow for sharing the core logic of when and where to run workers across different platforms and runtimes such as systemd, fork, containers, etc.
3 tasks
|
Checked commit carbonin@13c6bdf with ruby 2.5.5, rubocop 0.69.0, haml-lint 0.20.0, and yamllint 1.10.0 db/migrate/20191115164358_create_miq_worker_types.rb
|
48 tasks
jrafanie
reviewed
Nov 21, 2019
| class CreateMiqWorkerTypes < ActiveRecord::Migration[5.1] | ||
| def change | ||
| create_table :miq_worker_types do |t| | ||
| t.string :worker_type, :null => false |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This table will be seeded to include all leaf subclasses of MiqWorker
On the first pass it will be a replacement for the information currently
stored in the MIQ_WORKER_TYPES constants, but will be extended to
contain all the metadata concerning when workers of each type should
be running (for example, required roles, worker scope, provider type, etc.)
The ultimate goal is to separate out worker management into a standalone
process distinct from the current code-base where a subset of models
will be the primary API between the "worker orchestrator" and the
server which will determine how to start the workers it was told
to run.
This will allow for sharing the core logic of when and where to run
workers across different platforms and runtimes such as systemd, fork,
containers, etc.