johnpmitsch

Goals:

• Match setup to dev and production environment
• Not duplicate packages in Katello, use them from Foreman, same as we do in production

Steps to set up on a plain centos7 box:

• Install node
• Install ruby and gem install bundler so foreman can find plugins with ruby
• git clone foreman in root dir
• git clone katello in root dir (they just need to be siblings in the same dir to keep the same as the dev env)
• Make this change to katello: https://github.com/johnpmitsch/katello/commit/6fbd2aa2540a10329433a45986672aaf6d5dd16d

johnpmitsch

Goal:

Have Foreman, Katello, and plugins manage their own React SPAs that look and feel like one application. This would be done using single-spa which can send routes to different SPAs and even load different SPAs on the same page.

Challenges:

• Sharing authentication between SPAs
• Sharing components
• Managing "global" state like organization selection
• Having the same menu

johnpmitsch

Katello stable development environment

First things first

Spin up the box time vagrant up centos7-katello-devel-stable

What is it?

The katello devel stable box is a forklift box that is guaranteed to spin up successfully with the most recently working Katello development environment.

Why create it?

johnpmitsch

• cd ~ on dev box as vagrant user
• git clone https://github.com/theforeman/foreman_maintain.git
• sudo scl enable rh-ruby25 -- gem install bundler
• sudo scl enable rh-ruby25 -- bundle install
• Add to .bashrc and run source ~/.bashrc or open up a new terminal

alias foreman_maintain_scl="sudo scl enable rh-ruby25 -- ./bin/foreman-maintain "

• Run foreman_maintain_scl with foreman maintain arguments in ~/foreman_maintain

johnpmitsch

diff --git a/focaccia/bot.rb b/focaccia/bot.rb
index 7ccdf4d..f279cdd 100755
--- a/focaccia/bot.rb
+++ b/focaccia/bot.rb
@@ -3,7 +3,7 @@
 require 'cinch'
 
 # load enviroment variables from .env in development
-require 'dotenv/load' if ENV['RACK_ENV'] == 'development'
+require 'dotenv/load'

johnpmitsch

For Katello/hammer-cli-katello#720

Using partha's debug hack: https://gist.github.com/parthaa/3e981aa2e9eb4370d2076bb5ff63f36d

Caller -> /home/vagrant/hammer-cli-katello/test/functional/repository/create_test.rb:20:in `block (2 levels) in <top (required)>'
resource - repositories, action_name, - create, params - {"name"=>"repo1", "product_id"=>2, "content_type"=>"yum"}, head - {}, options - {:fake_response=>nil} 

test fails with:

johnpmitsch

reset password: sudo PULP_SETTINGS=/etc/pulp/settings.py DJANGO_SETTINGS_MODULE=pulpcore.app.settings  python3-django-admin reset-admin-password --password admin
httpie example: http GET http://admin:admin@localhost:24817/pulp/api/v3/repositories/file/file/
(its admin/password on dev box)

johnpmitsch

BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1784165

I publish a Content View (pulp 2 repository) and use conservative dependency solving. The content view has this repo synced https://inecas.fedorapeople.org/fakerepos/zoo3 and we are trying to filter out specific walrus versions

The metadata from https://inecas.fedorapeople.org/fakerepos/zoo/repodata/be20ece13e6c21b132667ddcaa4d7ad0b32e470b9917aba51979e0707116280d-primary.xml.gz shows that chimpanzee requires walrus (see under rpm:requires) and it doesn't have a specific version requirement.

In satellite 6.6:

johnpmitsch

Computer Architecture

Lesson 1

Prework

Fetch-decode-execute cycle:

A CPU is controlled by a clock. On each cycle of the clock it fetches data, decodes it, and executes it.

johnpmitsch

cd foreman-installer, rake pkg:generate_source, grep -r <thing> _build/