Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes #29148 - Use Puma instead of Passenger by default #802

Merged
merged 1 commit into from
Feb 28, 2020

Conversation

sthirugn
Copy link
Contributor

No description provided.

@ekohl
Copy link
Member

ekohl commented Feb 25, 2020

Two nits about the PR title: the # is significant (note that under the Checks tab no issue was linked). I'd also say what you are doing, so something like Use Puma instead of Passenger by default.

@sthirugn sthirugn changed the title [DO NOT MERGE] Fixes 29148 - Do not install passenger by default Fixes #29148 - Do not install passenger by default Feb 25, 2020
@sthirugn sthirugn changed the title Fixes #29148 - Do not install passenger by default Fixes #29148 - Use Puma instead of Passenger by default Feb 25, 2020
@sthirugn
Copy link
Contributor Author

sthirugn commented Feb 25, 2020

Test results
I was able to test locally using the following vagrant configuration. foreman service came up successfully with the required puma processes.

Vagrant box definition

centos7-puma-default:
  box: centos7-katello-nightly
  memory: 12000
  ansible:
    variables: # defaults in roles/hammer_devel/defaults/main.yml
      hammer_devel_github_username: blah
      foreman_repositories_environment: staging
      foreman_installer_options:
        - "--puppet-server-jvm-min-heap-size 300M"
        - "--puppet-server-jvm-max-heap-size 300M"
      foreman_installer_module_prs:
        - theforeman/puppet-foreman/802

I was able to do the following without any issues:

  • upload subscription
  • Enable repo
  • Sync custom repo
  • Create Content view
  • Publish/Promote the Content view

@sthirugn
Copy link
Contributor Author

Updated spec tests

@sthirugn
Copy link
Contributor Author

Updated more spec tests and squashed all the commits. Ready for the final review once the tests pass.

@ehelms
Copy link
Member

ehelms commented Feb 28, 2020

Looks good, I think the tests failing are same as master and this is good to go in for nightly to begin using puma.

@ehelms ehelms merged commit 8bc1ba3 into theforeman:master Feb 28, 2020
@ekohl
Copy link
Member

ekohl commented Mar 1, 2020

Currently no migration has been written to switch existing installations. IMHO that's fine and I'd feel comfortable not trying to migrate everyone in 2.1, leaving just fresh installations. Just wanted to make sure we're all on the same page about that rather than an omission.

@ehelms
Copy link
Member

ehelms commented Mar 1, 2020 via email

@sthirugn sthirugn deleted the puma_default branch March 2, 2020 17:06
@sthirugn
Copy link
Contributor Author

sthirugn commented Mar 2, 2020

Tested this change in stage and it worked great:

# journalctl -u foreman -f
-- Logs begin at Mon 2020-03-02 17:45:39 UTC. --
Mar 02 17:59:55 centos7-puma-staging-test.apex.example.com foreman[17405]: [17464] Puma starting in cluster mode...
Mar 02 17:59:55 centos7-puma-staging-test.apex.example.com foreman[17405]: [17464] * Version 3.11.4 (ruby 2.5.5-p157), codename: Love Song
Mar 02 17:59:55 centos7-puma-staging-test.apex.example.com foreman[17405]: [17464] * Min threads: 0, max threads: 16
Mar 02 17:59:55 centos7-puma-staging-test.apex.example.com foreman[17405]: [17464] * Environment: production
Mar 02 17:59:55 centos7-puma-staging-test.apex.example.com foreman[17405]: [17464] * Process workers: 2
Mar 02 17:59:55 centos7-puma-staging-test.apex.example.com foreman[17405]: [17464] * Phased restart available
Mar 02 17:59:55 centos7-puma-staging-test.apex.example.com foreman[17405]: [17464] * Listening on tcp://127.0.0.1:3000
Mar 02 17:59:55 centos7-puma-staging-test.apex.example.com foreman[17405]: [17464] Use Ctrl-C to stop
Mar 02 17:59:55 centos7-puma-staging-test.apex.example.com foreman[17405]: [17464] - Worker 0 (pid: 17647) booted, phase: 0
Mar 02 17:59:55 centos7-puma-staging-test.apex.example.com foreman[17405]: [17464] - Worker 1 (pid: 17656) booted, phase: 0

Box definition:

centos7-puma-staging-test:
  box: centos7-katello-nightly
  memory: 12000
  ansible:
    variables: # defaults in roles/hammer_devel/defaults/main.yml
      hammer_devel_github_username: *****
      foreman_repositories_environment: staging
      foreman_installer_options:
        - "--puppet-server-jvm-min-heap-size 300M"
        - "--puppet-server-jvm-max-heap-size 300M"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants