In an effort to streamline and bring our Katello development deployment in
line with production installation we've created a puppet module and
installation script dedicated to deploying a Katello development setup.
The first cut of the module, installer and deploy script updates can be
found at
The deploy repository can be used in conjunction with vagrant to provide
single command end-to-end deployment of a Katello development environment.
Currently, the development deployment does the following:
Allow you to specify a user and group to deploy as (and own all files)
Specify a directory to deploy the git checkouts to
Install Pulp, Candlepin and Elasticsearch
Setup and install proper certs for all services
Checkout upstream Foreman and Katello (via https) side by side
Lay down katello.yml in katello/config
Lay down a properly configured settings.yaml in foreman/config
Setup an Apache vhost
to serve Pulp with proper certs
to serve Pulp repos both http and https
to serve the Katello consumer cert RPM
to provide an SSL proxy to 'localhost:3000' to allow client
registration in development
Setup puppet agent and server to enable the development box as a host
in Foreman
Lay down a database.yml setup for postgres (default) or sqlite in
foreman/config
Install and setup RVM (default)
bundle install
run db:migrate
run db:seed
If anyone has time to try the development installer or ideas for additions
to it they would be greatly appreciated.
I've been attempting to get this going on a RHEL 6 vm and working a bit
with Eric to figure out some of the issues there.
The steps I had to figure out, and should probably be assembled on a wiki
somewhere:
git clone and use katello-deploy, not katello-installer.
execute ./bootstrap.sh rhel --devel (there are some bad versions of
commands floating around the github wiki pages for RHEL that seem to be
needed to skip, I will try to update these once I'm sure my steps are
correct)
adduser develuser
Last step of bootstrap.sh tries to run katello-installer for you, but it
will do so with bad options. Best to comment this out of setup.rb I think?
I ran the install manually with: katello-devel-installer -v -d --user
dgoodwin --deployment-dir /home/dgoodwin --group dgoodwin
I'm currently facing a couple errors with that process that I haven't
solved yet.
git clone commands seem to fail when run by puppet:
[ERROR 2014-03-26 08:09:05 main]
/Stage[main]/Katello_devel::Install/Git::Repo[foreman]/Exec[git_repo_for_foreman]/returns:
change from notrun to 0 failed: /usr/bin/git clone https://github.com/theforeman/foreman.git /home/dgoodwin/foreman
–recursive returned 128 instead of one of [0]
[DEBUG 2014-03-26 08:09:05 main]
Execgit_repo_for_foreman: Executing '/usr/bin/git clone https://github.com/theforeman/foreman.git /home/dgoodwin/foreman
–recursive'
[DEBUG 2014-03-26 08:09:05 main] Executing '/usr/bin/git clone https://github.com/theforeman/foreman.git /home/dgoodwin/foreman
–recursive'
[ WARN 2014-03-26 08:09:05 main]
/Stage[main]/Katello_devel::Install/Git::Repo[foreman]/Exec[git_repo_for_foreman]/returns:
fatal: Could not change back to '/var/log/katello-installer': Permission
denied
[ERROR 2014-03-26 08:09:05 main]
/Stage[main]/Katello_devel::Install/Git::Repo[foreman]/Exec[git_repo_for_foreman]:
Failed to call refresh: /usr/bin/git clone https://github.com/theforeman/foreman.git /home/dgoodwin/foreman
–recursive returned 128 instead of one of [0]
[ERROR 2014-03-26 08:09:05 main]
/Stage[main]/Katello_devel::Install/Git::Repo[foreman]/Exec[git_repo_for_foreman]:
/usr/bin/git clone https://github.com/theforeman/foreman.git/home/dgoodwin/foreman
–recursive returned 128 instead of one of [0]
This error is repeatable and not related to network issues, and strangely I
can run the git commands manually myself and it works fine, it also works
around the issue so katello installer can continue on a rerun.
[DEBUG 2014-03-26 11:29:22 main] Executing '/usr/local/rvm/bin/rvm install
ruby-1.9.3-p448 --binary'
[ERROR 2014-03-26 11:29:27 main] Execution of '/usr/local/rvm/bin/rvm
install ruby-1.9.3-p448 --binary' returned 1: Searching for binary rubies,
this might take some time.
[ INFO 2014-03-26 11:29:27 main] Requested binary installation but no
rubies are available to download, consider skipping --binary flag.
[DEBUG 2014-03-26 11:29:22 main] Executing '/usr/local/rvm/bin/rvm install
ruby-1.9.3-p448 --binary'
[ERROR 2014-03-26 11:29:27 main] Execution of '/usr/local/rvm/bin/rvm
install ruby-1.9.3-p448 --binary' returned 1: Searching for binary rubies,
this might take some time.
[ INFO 2014-03-26 11:29:27 main] Requested binary installation but no
rubies are available to download, consider skipping --binary flag.
Haven't looked into this one too far yet, will be doing so today and try to
send some PRs to centralize the actual instructions you need to get this
going from square 1.
Cheers,
Devan
···
On Fri, Mar 21, 2014 at 6:06 PM, Eric D Helms wrote:
In an effort to streamline and bring our Katello development deployment in
line with production installation we’ve created a puppet module and
installation script dedicated to deploying a Katello development setup.
The first cut of the module, installer and deploy script updates can be
found at
The deploy repository can be used in conjunction with vagrant to provide
single command end-to-end deployment of a Katello development environment.
Currently, the development deployment does the following:
Allow you to specify a user and group to deploy as (and own all files)
Specify a directory to deploy the git checkouts to
Install Pulp, Candlepin and Elasticsearch
Setup and install proper certs for all services
Checkout upstream Foreman and Katello (via https) side by side
Lay down katello.yml in katello/config
Lay down a properly configured settings.yaml in foreman/config
Setup an Apache vhost
to serve Pulp with proper certs
to serve Pulp repos both http and https
to serve the Katello consumer cert RPM
to provide an SSL proxy to ‘localhost:3000’ to allow client
registration in development
Setup puppet agent and server to enable the development box as a host
in Foreman
Lay down a database.yml setup for postgres (default) or sqlite in
foreman/config
Install and setup RVM (default)
bundle install
run db:migrate
run db:seed
If anyone has time to try the development installer or ideas for additions
to it they would be greatly appreciated.
> I've been attempting to get this going on a RHEL 6 vm and working a bit
> with Eric to figure out some of the issues there.
>
> The steps I had to figure out, and should probably be assembled on a wiki
> somewhere:
>
> - git clone and use katello-deploy, not katello-installer.
>
This is noted on the Katello readme, however we could add a stronger push
for users to katello-deploy and clean-up any old references the wiki may
have. Will add to my to-do list.
>
> - execute ./bootstrap.sh rhel --devel (there are some bad versions of
> commands floating around the github wiki pages for RHEL that seem to be
> needed to skip, I will try to update these once I'm sure my steps are
> correct)
>
I think this should still be './bootstrap-rhel.sh --devel' but I can look
into centralizing it to one bootstrap script with options. I originally
kept the bootstrap-rhel as is due how it handles registration for you.
>
> - adduser develuser
>
I did not explicitly add user creation to the katello_devel module as I was
assuming either vagrant deployment or on to a system that a dev would have
manually created a user on. We can add this as an addition.
>
> - Last step of bootstrap.sh tries to run katello-installer for you, but it
> will do so with bad options. Best to comment this out of setup.rb I think?
>
> - I ran the install manually with: katello-devel-installer -v -d --user
> dgoodwin --deployment-dir /home/dgoodwin --group dgoodwin
>
> I'm currently facing a couple errors with that process that I haven't
> solved yet.
>
> 1) git clone commands seem to fail when run by puppet:
>
> [ERROR 2014-03-26 08:09:05 main]
> /Stage[main]/Katello_devel::Install/Git::Repo[foreman]/Exec[git_repo_for_foreman]/returns:
> change from notrun to 0 failed: /usr/bin/git clone
> https://github.com/theforeman/foreman.git /home/dgoodwin/foreman
> --recursive returned 128 instead of one of [0]
> [DEBUG 2014-03-26 08:09:05 main]
> Execgit_repo_for_foreman: Executing '/usr/bin/git clone
> https://github.com/theforeman/foreman.git /home/dgoodwin/foreman
> --recursive'
> [DEBUG 2014-03-26 08:09:05 main] Executing '/usr/bin/git clone
> https://github.com/theforeman/foreman.git /home/dgoodwin/foreman
> --recursive'
> [ WARN 2014-03-26 08:09:05 main]
> /Stage[main]/Katello_devel::Install/Git::Repo[foreman]/Exec[git_repo_for_foreman]/returns:
> fatal: Could not change back to '/var/log/katello-installer': Permission
> denied
> [ERROR 2014-03-26 08:09:05 main]
> /Stage[main]/Katello_devel::Install/Git::Repo[foreman]/Exec[git_repo_for_foreman]:
> Failed to call refresh: /usr/bin/git clone
> https://github.com/theforeman/foreman.git /home/dgoodwin/foreman
> --recursive returned 128 instead of one of [0]
> [ERROR 2014-03-26 08:09:05 main]
> /Stage[main]/Katello_devel::Install/Git::Repo[foreman]/Exec[git_repo_for_foreman]:
> /usr/bin/git clone https://github.com/theforeman/foreman.git/home/dgoodwin/foreman --recursive returned 128 instead of one of [0]
>
> This error is repeatable and not related to network issues, and strangely
> I can run the git commands manually myself and it works fine, it also works
> around the issue so katello installer can continue on a rerun.
>
>
> 2)
>
> [DEBUG 2014-03-26 11:29:22 main] Executing '/usr/local/rvm/bin/rvm
> install ruby-1.9.3-p448 --binary'
> [ERROR 2014-03-26 11:29:27 main] Execution of '/usr/local/rvm/bin/rvm
> install ruby-1.9.3-p448 --binary' returned 1: Searching for binary rubies,
> this might take some time.
> [ INFO 2014-03-26 11:29:27 main] Requested binary installation but no
> rubies are available to download, consider skipping --binary flag.
> [DEBUG 2014-03-26 11:29:22 main] Executing '/usr/local/rvm/bin/rvm
> install ruby-1.9.3-p448 --binary'
> [ERROR 2014-03-26 11:29:27 main] Execution of '/usr/local/rvm/bin/rvm
> install ruby-1.9.3-p448 --binary' returned 1: Searching for binary rubies,
> this might take some time.
> [ INFO 2014-03-26 11:29:27 main] Requested binary installation but no
> rubies are available to download, consider skipping --binary flag.
>
>
I'm spinning up a RHEL box to see if I can replicate these behaviors.
Eric
···
On Thu, Mar 27, 2014 at 7:53 AM, Devan Goodwin wrote:
Haven’t looked into this one too far yet, will be doing so today and try
to send some PRs to centralize the actual instructions you need to get this
going from square 1.
In an effort to streamline and bring our Katello development deployment
in line with production installation we’ve created a puppet module and
installation script dedicated to deploying a Katello development setup.
The first cut of the module, installer and deploy script updates can be
found at
The deploy repository can be used in conjunction with vagrant to provide
single command end-to-end deployment of a Katello development environment.
Currently, the development deployment does the following:
Allow you to specify a user and group to deploy as (and own all files)
Specify a directory to deploy the git checkouts to
Install Pulp, Candlepin and Elasticsearch
Setup and install proper certs for all services
Checkout upstream Foreman and Katello (via https) side by side
Lay down katello.yml in katello/config
Lay down a properly configured settings.yaml in foreman/config
Setup an Apache vhost
to serve Pulp with proper certs
to serve Pulp repos both http and https
to serve the Katello consumer cert RPM
to provide an SSL proxy to ‘localhost:3000’ to allow client
registration in development
Setup puppet agent and server to enable the development box as a
host in Foreman
Lay down a database.yml setup for postgres (default) or sqlite in
foreman/config
Install and setup RVM (default)
bundle install
run db:migrate
run db:seed
If anyone has time to try the development installer or ideas for
additions to it they would be greatly appreciated.
With some help from Eric it looks like I've gotten through the devel setup
successfully. My steps were:
Started with a fresh RHEL 6.5 installation.
adduser dgoodwin
passwd dgoodwin
IMPORTANT: visudo and make sure user dgoodwin can run sudo commands
WITHOUT a password. I did this by adding my user to wheel group and
uncommenting the line:
This part is debatable, but I would edit setup.rb and remove the last
portion where we run katello-devel-installer. We need additional options,
and more importantly it has to be run from a directory the devel user can
access, not /root.
Run katello-devel-installer -v -d --user dgoodwin --deployment-dir
/home/dgoodwin --group dgoodwin
Going to submit some patches to try to simplify this a bit, and then update
the Katello wiki.
Cheers,
Devan
···
On Thu, Mar 27, 2014 at 9:26 AM, Eric D Helms wrote:
On Thu, Mar 27, 2014 at 7:53 AM, Devan Goodwin dgoodwin@rm-rf.ca wrote:
I’ve been attempting to get this going on a RHEL 6 vm and working a bit
with Eric to figure out some of the issues there.
The steps I had to figure out, and should probably be assembled on a wiki
somewhere:
git clone and use katello-deploy, not katello-installer.
This is noted on the Katello readme, however we could add a stronger push
for users to katello-deploy and clean-up any old references the wiki may
have. Will add to my to-do list.
execute ./bootstrap.sh rhel --devel (there are some bad versions of
commands floating around the github wiki pages for RHEL that seem to be
needed to skip, I will try to update these once I’m sure my steps are
correct)
I think this should still be ‘./bootstrap-rhel.sh --devel’ but I can look
into centralizing it to one bootstrap script with options. I originally
kept the bootstrap-rhel as is due how it handles registration for you.
adduser develuser
I did not explicitly add user creation to the katello_devel module as I
was assuming either vagrant deployment or on to a system that a dev would
have manually created a user on. We can add this as an addition.
Last step of bootstrap.sh tries to run katello-installer for you, but
it will do so with bad options. Best to comment this out of setup.rb I
think?
I ran the install manually with: katello-devel-installer -v -d --user
dgoodwin --deployment-dir /home/dgoodwin --group dgoodwin
I’m currently facing a couple errors with that process that I haven’t
solved yet.
git clone commands seem to fail when run by puppet:
[ERROR 2014-03-26 08:09:05 main]
/Stage[main]/Katello_devel::Install/Git::Repo[foreman]/Exec[git_repo_for_foreman]/returns:
change from notrun to 0 failed: /usr/bin/git clone https://github.com/theforeman/foreman.git /home/dgoodwin/foreman
–recursive returned 128 instead of one of [0]
[DEBUG 2014-03-26 08:09:05 main]
Execgit_repo_for_foreman: Executing ‘/usr/bin/git clone https://github.com/theforeman/foreman.git /home/dgoodwin/foreman
–recursive’
[DEBUG 2014-03-26 08:09:05 main] Executing ‘/usr/bin/git clone https://github.com/theforeman/foreman.git /home/dgoodwin/foreman
–recursive’
[ WARN 2014-03-26 08:09:05 main]
/Stage[main]/Katello_devel::Install/Git::Repo[foreman]/Exec[git_repo_for_foreman]/returns:
fatal: Could not change back to ‘/var/log/katello-installer’: Permission
denied
[ERROR 2014-03-26 08:09:05 main]
/Stage[main]/Katello_devel::Install/Git::Repo[foreman]/Exec[git_repo_for_foreman]:
Failed to call refresh: /usr/bin/git clone https://github.com/theforeman/foreman.git /home/dgoodwin/foreman
–recursive returned 128 instead of one of [0]
[ERROR 2014-03-26 08:09:05 main]
/Stage[main]/Katello_devel::Install/Git::Repo[foreman]/Exec[git_repo_for_foreman]:
/usr/bin/git clone https://github.com/theforeman/foreman.git/home/dgoodwin/foreman --recursive returned 128 instead of one of [0]
This error is repeatable and not related to network issues, and strangely
I can run the git commands manually myself and it works fine, it also works
around the issue so katello installer can continue on a rerun.
[DEBUG 2014-03-26 11:29:22 main] Executing ‘/usr/local/rvm/bin/rvm
install ruby-1.9.3-p448 --binary’
[ERROR 2014-03-26 11:29:27 main] Execution of ‘/usr/local/rvm/bin/rvm
install ruby-1.9.3-p448 --binary’ returned 1: Searching for binary rubies,
this might take some time.
[ INFO 2014-03-26 11:29:27 main] Requested binary installation but no
rubies are available to download, consider skipping --binary flag.
[DEBUG 2014-03-26 11:29:22 main] Executing ‘/usr/local/rvm/bin/rvm
install ruby-1.9.3-p448 --binary’
[ERROR 2014-03-26 11:29:27 main] Execution of ‘/usr/local/rvm/bin/rvm
install ruby-1.9.3-p448 --binary’ returned 1: Searching for binary rubies,
this might take some time.
[ INFO 2014-03-26 11:29:27 main] Requested binary installation but no
rubies are available to download, consider skipping --binary flag.
I’m spinning up a RHEL box to see if I can replicate these behaviors.
Eric
Haven’t looked into this one too far yet, will be doing so today and try
to send some PRs to centralize the actual instructions you need to get this
going from square 1.
In an effort to streamline and bring our Katello development deployment
in line with production installation we’ve created a puppet module and
installation script dedicated to deploying a Katello development setup.
The first cut of the module, installer and deploy script updates can be
found at
The deploy repository can be used in conjunction with vagrant to provide
single command end-to-end deployment of a Katello development environment.
Currently, the development deployment does the following:
Allow you to specify a user and group to deploy as (and own all files)
Specify a directory to deploy the git checkouts to
Install Pulp, Candlepin and Elasticsearch
Setup and install proper certs for all services
Checkout upstream Foreman and Katello (via https) side by side
Lay down katello.yml in katello/config
Lay down a properly configured settings.yaml in foreman/config
Setup an Apache vhost
to serve Pulp with proper certs
to serve Pulp repos both http and https
to serve the Katello consumer cert RPM
to provide an SSL proxy to ‘localhost:3000’ to allow client
registration in development
Setup puppet agent and server to enable the development box as a
host in Foreman
Lay down a database.yml setup for postgres (default) or sqlite in
foreman/config
Install and setup RVM (default)
bundle install
run db:migrate
run db:seed
If anyone has time to try the development installer or ideas for
additions to it they would be greatly appreciated.
> With some help from Eric it looks like I've gotten through the devel setup
> successfully. My steps were:
>
> - Started with a fresh RHEL 6.5 installation.
> - adduser dgoodwin
> - passwd dgoodwin
> - IMPORTANT: visudo and make sure user dgoodwin can run sudo commands
> WITHOUT a password. I did this by adding my user to wheel group and
> uncommenting the line:
>
> %wheel ALL=(ALL) NOPASSWD: ALL
>
> - subscription-manager register --auto-attach
> - yum install -y git
> - git clone https://github.com/Katello/katello-deploy.git
> - cd katello-deploy
> - This part is debatable, but I would edit setup.rb and remove the last
> portion where we run katello-devel-installer. We need additional options,
> and more importantly it has to be run from a directory the devel user can
> access, not /root.
> - Run bootstrap-rhel.sh --devel
> - Run katello-devel-installer -v -d --user dgoodwin --deployment-dir
> /home/dgoodwin --group dgoodwin
>
> Going to submit some patches to try to simplify this a bit, and then update
> the Katello wiki.
>
> Cheers,
>
> Devan
>
>
Tried similar for f20 install and ran into lots of problems. Are there reasons that f20 won't work, or is it that foretello is just not yet available as f20 rpms?
I had to edit the .repo files to replace $releasever with 19, then get katello-installer directly from koji (is it not available in f19?). I made it as far as trying to run 'rake katello:reset' but get errors related to candlepin db (ERROR: must be owner of database candlepin) and missing passwd file (cat: /etc/katello/keystore_password-file: No such file or directory).
On Thu, Mar 27, 2014 at 7:53 AM, Devan Goodwin dgoodwin@rm-rf.ca wrote:
I’ve been attempting to get this going on a RHEL 6 vm and working a bit
with Eric to figure out some of the issues there.
The steps I had to figure out, and should probably be assembled on a wiki
somewhere:
git clone and use katello-deploy, not katello-installer.
This is noted on the Katello readme, however we could add a stronger push
for users to katello-deploy and clean-up any old references the wiki may
have. Will add to my to-do list.
execute ./bootstrap.sh rhel --devel (there are some bad versions of
commands floating around the github wiki pages for RHEL that seem to be
needed to skip, I will try to update these once I’m sure my steps are
correct)
I think this should still be ‘./bootstrap-rhel.sh --devel’ but I can look
into centralizing it to one bootstrap script with options. I originally
kept the bootstrap-rhel as is due how it handles registration for you.
adduser develuser
I did not explicitly add user creation to the katello_devel module as I
was assuming either vagrant deployment or on to a system that a dev would
have manually created a user on. We can add this as an addition.
Last step of bootstrap.sh tries to run katello-installer for you, but
it will do so with bad options. Best to comment this out of setup.rb I
think?
I ran the install manually with: katello-devel-installer -v -d --user
dgoodwin --deployment-dir /home/dgoodwin --group dgoodwin
I’m currently facing a couple errors with that process that I haven’t
solved yet.
git clone commands seem to fail when run by puppet:
[ERROR 2014-03-26 08:09:05 main]
/Stage[main]/Katello_devel::Install/Git::Repo[foreman]/Exec[git_repo_for_foreman]/returns:
change from notrun to 0 failed: /usr/bin/git clone https://github.com/theforeman/foreman.git /home/dgoodwin/foreman
–recursive returned 128 instead of one of [0]
[DEBUG 2014-03-26 08:09:05 main]
Execgit_repo_for_foreman: Executing ‘/usr/bin/git clone https://github.com/theforeman/foreman.git /home/dgoodwin/foreman
–recursive’
[DEBUG 2014-03-26 08:09:05 main] Executing ‘/usr/bin/git clone https://github.com/theforeman/foreman.git /home/dgoodwin/foreman
–recursive’
[ WARN 2014-03-26 08:09:05 main]
/Stage[main]/Katello_devel::Install/Git::Repo[foreman]/Exec[git_repo_for_foreman]/returns:
fatal: Could not change back to ‘/var/log/katello-installer’: Permission
denied
[ERROR 2014-03-26 08:09:05 main]
/Stage[main]/Katello_devel::Install/Git::Repo[foreman]/Exec[git_repo_for_foreman]:
Failed to call refresh: /usr/bin/git clone https://github.com/theforeman/foreman.git /home/dgoodwin/foreman
–recursive returned 128 instead of one of [0]
[ERROR 2014-03-26 08:09:05 main]
/Stage[main]/Katello_devel::Install/Git::Repo[foreman]/Exec[git_repo_for_foreman]:
/usr/bin/git clone https://github.com/theforeman/foreman.git/home/dgoodwin/foreman
–recursive returned 128 instead of one of [0]
This error is repeatable and not related to network issues, and strangely
I can run the git commands manually myself and it works fine, it also
works
around the issue so katello installer can continue on a rerun.
[DEBUG 2014-03-26 11:29:22 main] Executing ‘/usr/local/rvm/bin/rvm
install ruby-1.9.3-p448 --binary’
[ERROR 2014-03-26 11:29:27 main] Execution of ‘/usr/local/rvm/bin/rvm
install ruby-1.9.3-p448 --binary’ returned 1: Searching for binary rubies,
this might take some time.
[ INFO 2014-03-26 11:29:27 main] Requested binary installation but no
rubies are available to download, consider skipping --binary flag.
[DEBUG 2014-03-26 11:29:22 main] Executing ‘/usr/local/rvm/bin/rvm
install ruby-1.9.3-p448 --binary’
[ERROR 2014-03-26 11:29:27 main] Execution of ‘/usr/local/rvm/bin/rvm
install ruby-1.9.3-p448 --binary’ returned 1: Searching for binary rubies,
this might take some time.
[ INFO 2014-03-26 11:29:27 main] Requested binary installation but no
rubies are available to download, consider skipping --binary flag.
I’m spinning up a RHEL box to see if I can replicate these behaviors.
Eric
Haven’t looked into this one too far yet, will be doing so today and try
to send some PRs to centralize the actual instructions you need to get
this
going from square 1.
In an effort to streamline and bring our Katello development deployment
in line with production installation we’ve created a puppet module and
installation script dedicated to deploying a Katello development setup.
The first cut of the module, installer and deploy script updates can be
found at
The deploy repository can be used in conjunction with vagrant to provide
single command end-to-end deployment of a Katello development
environment.
Currently, the development deployment does the following:
Allow you to specify a user and group to deploy as (and own all files)
Specify a directory to deploy the git checkouts to
Install Pulp, Candlepin and Elasticsearch
Setup and install proper certs for all services
Checkout upstream Foreman and Katello (via https) side by side
Lay down katello.yml in katello/config
Lay down a properly configured settings.yaml in foreman/config
Setup an Apache vhost
to serve Pulp with proper certs
to serve Pulp repos both http and https
to serve the Katello consumer cert RPM
to provide an SSL proxy to ‘localhost:3000’ to allow client
registration in development
Setup puppet agent and server to enable the development box as a
host in Foreman
Lay down a database.yml setup for postgres (default) or sqlite in
foreman/config
Install and setup RVM (default)
bundle install
run db:migrate
run db:seed
If anyone has time to try the development installer or ideas for
additions to it they would be greatly appreciated.
We don't currently support F20 (and I did no testing of it) or have
packages for F20. You could try using the F19 packages for Pulp and
Candlepin and pre-installing them. You can use the installer from git
checked out into katello-deploy.
Eric
···
On Apr 19, 2014 11:05 AM, "Tom McKay" wrote:
----- Original Message -----
With some help from Eric it looks like I’ve gotten through the devel
setup
successfully. My steps were:
Started with a fresh RHEL 6.5 installation.
adduser dgoodwin
passwd dgoodwin
IMPORTANT: visudo and make sure user dgoodwin can run sudo commands
WITHOUT a password. I did this by adding my user to wheel group and
uncommenting the line:
This part is debatable, but I would edit setup.rb and remove the last
portion where we run katello-devel-installer. We need additional options,
and more importantly it has to be run from a directory the devel user can
access, not /root.
Run katello-devel-installer -v -d --user dgoodwin --deployment-dir
/home/dgoodwin --group dgoodwin
Going to submit some patches to try to simplify this a bit, and then
update
the Katello wiki.
Cheers,
Devan
Tried similar for f20 install and ran into lots of problems. Are there
reasons that f20 won’t work, or is it that foretello is just not yet
available as f20 rpms?
I had to edit the .repo files to replace $releasever with 19, then get
katello-installer directly from koji (is it not available in f19?). I made
it as far as trying to run ‘rake katello:reset’ but get errors related to
candlepin db (ERROR: must be owner of database candlepin) and missing
passwd file (cat: /etc/katello/keystore_password-file: No such file or
directory).
change from notrun to 0 failed: /usr/bin/git clone https://github.com/theforeman/foreman.git /home/dgoodwin/foreman
–recursive returned 128 instead of one of [0]
[DEBUG 2014-03-26 08:09:05 main]
Execgit_repo_for_foreman: Executing '/usr/bin/git
clone
Failed to call refresh: /usr/bin/git clone https://github.com/theforeman/foreman.git /home/dgoodwin/foreman
–recursive returned 128 instead of one of [0]
[ERROR 2014-03-26 08:09:05 main]
This error is repeatable and not related to network issues, and
strangely
I can run the git commands manually myself and it works fine, it also
works
around the issue so katello installer can continue on a rerun.
[DEBUG 2014-03-26 11:29:22 main] Executing ‘/usr/local/rvm/bin/rvm
install ruby-1.9.3-p448 --binary’
[ERROR 2014-03-26 11:29:27 main] Execution of ‘/usr/local/rvm/bin/rvm
install ruby-1.9.3-p448 --binary’ returned 1: Searching for binary
rubies,
this might take some time.
[ INFO 2014-03-26 11:29:27 main] Requested binary installation but no
rubies are available to download, consider skipping --binary flag.
[DEBUG 2014-03-26 11:29:22 main] Executing ‘/usr/local/rvm/bin/rvm
install ruby-1.9.3-p448 --binary’
[ERROR 2014-03-26 11:29:27 main] Execution of ‘/usr/local/rvm/bin/rvm
install ruby-1.9.3-p448 --binary’ returned 1: Searching for binary
rubies,
this might take some time.
[ INFO 2014-03-26 11:29:27 main] Requested binary installation but no
rubies are available to download, consider skipping --binary flag.
I’m spinning up a RHEL box to see if I can replicate these behaviors.
Eric
Haven’t looked into this one too far yet, will be doing so today and
try
to send some PRs to centralize the actual instructions you need to get
this
going from square 1.
The deploy repository can be used in conjunction with vagrant to
provide
single command end-to-end deployment of a Katello development
environment.
Currently, the development deployment does the following:
Allow you to specify a user and group to deploy as (and own all
files)
Specify a directory to deploy the git checkouts to
Install Pulp, Candlepin and Elasticsearch
Setup and install proper certs for all services
Checkout upstream Foreman and Katello (via https) side by side
Lay down katello.yml in katello/config
Lay down a properly configured settings.yaml in foreman/config
Setup an Apache vhost
to serve Pulp with proper certs
to serve Pulp repos both http and https
to serve the Katello consumer cert RPM
to provide an SSL proxy to ‘localhost:3000’ to allow client
registration in development
Setup puppet agent and server to enable the development box as a
host in Foreman
Lay down a database.yml setup for postgres (default) or sqlite in
foreman/config
Install and setup RVM (default)
bundle install
run db:migrate
run db:seed
If anyone has time to try the development installer or ideas for
additions to it they would be greatly appreciated.
Thanks,
Eric
–
You received this message because you are subscribed to the Google
Groups “foreman-dev” group.
To unsubscribe from this group and stop receiving emails from it,
send
