w/ @ewoud help all good! I'll comment on PR and go from there.
++ for the help
On Sat, Oct 22, 2016 at 12:31 PM, Eric D Helms
wrote:
> Off the top of my head not sure, try using Puppet 3?
>
> On Oct 22, 2016 12:03 PM, "Tom McKay" wrote:
>
>>
>>
>> On Sat, Oct 22, 2016 at 10:28 AM, Eric D Helms
Off the top of my head not sure, try using Puppet 3?
On Oct 22, 2016 12:03 PM, "Tom McKay" wrote:
>
>
> On Sat, Oct 22, 2016 at 10:28 AM, Eric D Helms
> wrote:
>
>>
>>
>> On Sat, Oct 22, 2016 at 9:35 AM, Tom McKay
>> wrote:
>>
>>> I will try with your PR...
>>>
>>> I see the katello_devel/task
On Sat, Oct 22, 2016 at 10:28 AM, Eric D Helms wrote:
>
>
> On Sat, Oct 22, 2016 at 9:35 AM, Tom McKay wrote:
>
>> I will try with your PR...
>>
>> I see the katello_devel/tasks/main.yml runs the installer. How do other
>> playbooks add to this? This is probably also applicable to my
>> atomic_r
On Sat, Oct 22, 2016 at 9:35 AM, Tom McKay wrote:
> I will try with your PR...
>
> I see the katello_devel/tasks/main.yml runs the installer. How do other
> playbooks add to this? This is probably also applicable to my
> atomic_registry playbook as well: If I wanted to have it alter the
> paramet
I will try with your PR...
I see the katello_devel/tasks/main.yml runs the installer. How do other
playbooks add to this? This is probably also applicable to my
atomic_registry playbook as well: If I wanted to have it alter the
parameters to the foreman-installer (ie. change registry port), how is
I think you have a couple options:
1) Use my PR and review it to see about achieving what you want
2) Spin up a dev box and then 'ansible-playbook -l registry
playbooks/atomic_registry.yaml'
On Sat, Oct 22, 2016 at 8:32 AM, Tom McKay wrote:
> I see... I'm trying to turn this into a dev instal
I see... I'm trying to turn this into a dev install so that I can hopefully
turn off selinux and have it actually work:
registry:
box: centos7
ansible:
group: 'server'
variables:
foreman_installer_module_prs:
"katello/capsule/101,theforeman/foreman_proxy/303"
foreman_instal
My PR to move the devel setup to Ansible has not been merged yet (
https://github.com/Katello/forklift/pull/279) so what you have is still
valid. Which is why I ask what the issue you are running in to is.
On Sat, Oct 22, 2016 at 8:08 AM, Tom McKay wrote:
> I was told the 'options' section is no
I was told the 'options' section is no longer relevant. I'd just like to
know how to convert this old format to new.
On Sat, Oct 22, 2016 at 8:03 AM, Eric D Helms
wrote:
> What's actually broken though?
>
> On Oct 22, 2016 7:48 AM, "Tom McKay" wrote:
>
>> This is my old boxes.yaml stanza, could
What's actually broken though?
On Oct 22, 2016 7:48 AM, "Tom McKay" wrote:
> This is my old boxes.yaml stanza, could someone help me translate it to
> the latest forklift format? I'm blocked on testing because I can't disable
> selinux and so want to set up a new dev box.
>
> katello:
> box: c
This is my old boxes.yaml stanza, could someone help me translate it to the
latest forklift format? I'm blocked on testing because I can't disable
selinux and so want to set up a new dev box.
katello:
box: centos7
shell: 'yum -y install ruby && cd /vagrant && ./setup.rb'
installer: >-
--
11 matches
Mail list logo
