Project

General

Profile

Actions
Copy link

Tracker #28999

closed

Deploy Foreman with Puma as the application server by default

Added by Eric Helms almost 5 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Foreman modules
Target version:
Foreman - 2.1.0
% Done:

0%

Difficulty:
Triaged:
Yes
Bugzilla link:
Fixed in Releases:
Foreman - 2.1.0
Found in Releases:
Red Hat JIRA:

Related issues 11 (2 open — 9 closed)

Related to Packaging - Bug #17712: Passenger can't find passenger_native_support.soRejectedActions
Related to Foreman - Feature #28955: Add Puma workers/threads configurationClosedSuresh ThirugnanasambandanActions
Related to Installer - Bug #29041: Update Puma default workers from 5 to 2 in the devel scenarioClosedSuresh ThirugnanasambandanActions
Related to Foreman - Feature #29148: Make puma defaultClosedSuresh ThirugnanasambandanActions
Related to Installer - Feature #29282: Add migrations for replacing passenger with pumaClosedSuresh ThirugnanasambandanActions
Related to Foreman - Bug #29507: Add puma-status to report puma statusingClosedEric HelmsActions
Related to Packaging - Feature #29514: package puma-status gemClosedEric HelmsActions
Related to Katello - Bug #29370: Syncing a large product leaves Pulp tasks "waiting".NewActions
Related to Foreman - Bug #29588: Foreman service seems active however keeps restarting if it can't startNewActions
Related to Foreman - Feature #29356: Ship Puma systemd plugin in productionClosedEwoud Kohl van WijngaardenActions
Related to Foreman - Feature #29584: Preload application with Puma in production modeClosedEwoud Kohl van WijngaardenActions
Actions
Copy link
 #1

Updated by Eric Helms almost 5 years ago

  • Related to Bug #17712: Passenger can't find passenger_native_support.so added
Actions
Copy link
 #2

Updated by Suresh Thirugnanasambandan almost 5 years ago

  • Related to Feature #28955: Add Puma workers/threads configuration added
Actions
Copy link
 #3

Updated by Suresh Thirugnanasambandan almost 5 years ago

  • Related to Bug #29041: Update Puma default workers from 5 to 2 in the devel scenario added
Actions
Copy link
 #4

Updated by Suresh Thirugnanasambandan almost 5 years ago

Actions
Copy link
 #5

Updated by Suresh Thirugnanasambandan almost 5 years ago

  • Blocked by Feature #29282: Add migrations for replacing passenger with puma added
Actions
Copy link
 #6

Updated by Suresh Thirugnanasambandan almost 5 years ago

  • Blocked by deleted (Feature #29282: Add migrations for replacing passenger with puma)
Actions
Copy link
 #7

Updated by Suresh Thirugnanasambandan almost 5 years ago

  • Related to Feature #29282: Add migrations for replacing passenger with puma added
Actions
Copy link
 #8

Updated by Suresh Thirugnanasambandan almost 5 years ago

  • Related to Bug #29507: Add puma-status to report puma statusing added
Actions
Copy link
 #9

Updated by Suresh Thirugnanasambandan almost 5 years ago

Actions
Copy link
 #10

Updated by Suresh Thirugnanasambandan almost 5 years ago

  • Related to Bug #29370: Syncing a large product leaves Pulp tasks "waiting". added
Actions
Copy link
 #11

Updated by Suresh Thirugnanasambandan almost 5 years ago

  • Related to Bug #29588: Foreman service seems active however keeps restarting if it can't start added
Actions
Copy link
 #12

Updated by Suresh Thirugnanasambandan almost 5 years ago

  • Related to Feature #29356: Ship Puma systemd plugin in production added
Actions
Copy link
 #13

Updated by Suresh Thirugnanasambandan almost 5 years ago

  • Related to Feature #29584: Preload application with Puma in production mode added
Actions
Copy link
 #14

Updated by Ewoud Kohl van Wijngaarden over 4 years ago

  • Category set to Foreman modules
  • Status changed from New to Closed
  • Target version set to 2.1.0
  • Triaged changed from No to Yes
  • Fixed in Releases 2.1.0 added

Even though not all linked tasks are complete, this is the default in 2.1.

Actions
Copy link

Also available in: Atom PDF