Re: [foreman-dev] help using forklift for katello dev box

[Tom McKay]

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 
>> 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_registry playbook as well: If I wanted to have it alter the
 parameters to the foreman-installer (ie. change registry port), how is that
 accomplished? Also need to enable ostree.

>>>
>>> I have updated my PR to make use of Stephen's new foreman_installer role
>>> that centralizes calls to foreman_installer. Given that you can run
>>> multiple playbooks, and that our installer is idempotent you have a few
>>> options:
>>>
>>>  1) Use the foreman_installer_options under 'variables' section in the
>>> box definition similar to what oyu have below (that ought to work with my
>>> refactor)
>>>
>>
>> This option seems most appropriate so went with that.
>>
>> First run I got puppet_repositories_version is undefined. I defined it to
>> 4, then next run I get "bin/sh: /opt/puppetlabs/puppet/bin/gem: No such
>> file or directory".
>>
>> Any pointers on that?
>>
>> I am on the atomic-registry PR and then I rebased it to your PR. Here is
>> the boxes.yaml
>>
>> registry:
>>   box: centos7
>>   ansible:
>> group: 'devel'
>> variables:
>>   katello_devel_github_username: "thomasmckay"
>>   foreman_installer_module_prs: "katello/capsule/101"
>>   foreman_installer_options: "--capsule-docker-registry-port=5001"
>>   atomic_registry_registry_port: "5000"
>>   puppet_repositories_version: 4
>> playbook:
>> - 'playbooks/devel.yml'
>> - 'playbooks/katello_atomic_registry.yml'
>>
>>
>>  2) Call the foreman-installer AFTER the devel setup with the options you
>>> need (the installer stores all the previous, so you ought to be able to run
>>> it again, updating any new options you want)
>>>  3) Create a new playbook that you configure with everything you need
>>>
>>>
>>> Try re-running what you have against my updates to my PR. Note that I
>>> changed the playbook to simply 'devel'
>>>
>>>
>>>

 I can be on IRC today, if that is easier.

 Running these PRs together:
 https://github.com/Katello/forklift/pull/279
 https://github.com/Katello/forklift/pull/325

 Fatal: [registry]: FAILED! => {"failed": true, "msg": "The conditional
 check 'skip_installer == False' failed. The error was: error while
 evaluating conditional (skip_installer == False): 'skip_installer' is
 undefined\n\nThe error appears to have been in
 '/home/thomasmckay/code/forklift/playbooks/roles/katello_devel/tasks/main.yml':
 line 12, column 3, but may\nbe elsewhere in the file depending on the exact
 syntax problem.\n\nThe offending line appears to be:\n\n\n- name: 'Run
 devel installer'\n ^ here\n"}

 registry:
   box: centos7
   ansible:
 group: 'devel'
 variables:
   katello_devel_github_username: "thomasmckay"
   foreman_installer_module_prs: "katello/capsule/101"
   foreman_installer_options: "--capsule-docker-registry-port=5001"
   atomic_registry_registry_port: "5000"
 playbook:
 - 'playbooks/katello_devel.yml'
 - 'playbooks/katello_atomic_registry.yml'



 On Sat, Oct 22, 2016 at 8:58 AM, Eric D Helms 
 wrote:

> 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 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,theforema
>> n/foreman_proxy/303"
>>   foreman_installer_options: "--capsule-docker-registry-por
>> t=5001"
>>   atomic_registry_registry_port: "5000"
>> playbook:
>> - 'playbooks/katello.yml'
>> - 'playbooks/katello_atomic_registry.yml'
>>
>>
>> On Sat, Oct 22, 2016 at 8:11 AM, Eric D Helms 
>> wrote:
>>
>>> My PR to move the devel setup to Ansible has not been merged yet (
>>> 

Re: [foreman-dev] help using forklift for katello dev box

[Eric D Helms]

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
> parameters to the foreman-installer (ie. change registry port), how is that
> accomplished? Also need to enable ostree.
>

I have updated my PR to make use of Stephen's new foreman_installer role
that centralizes calls to foreman_installer. Given that you can run
multiple playbooks, and that our installer is idempotent you have a few
options:

 1) Use the foreman_installer_options under 'variables' section in the box
definition similar to what oyu have below (that ought to work with my
refactor)
 2) Call the foreman-installer AFTER the devel setup with the options you
need (the installer stores all the previous, so you ought to be able to run
it again, updating any new options you want)
 3) Create a new playbook that you configure with everything you need


Try re-running what you have against my updates to my PR. Note that I
changed the playbook to simply 'devel'



>
> I can be on IRC today, if that is easier.
>
> Running these PRs together:
> https://github.com/Katello/forklift/pull/279
> https://github.com/Katello/forklift/pull/325
>
> Fatal: [registry]: FAILED! => {"failed": true, "msg": "The conditional
> check 'skip_installer == False' failed. The error was: error while
> evaluating conditional (skip_installer == False): 'skip_installer' is
> undefined\n\nThe error appears to have been in '/home/thomasmckay/code/
> forklift/playbooks/roles/katello_devel/tasks/main.yml': line 12, column
> 3, but may\nbe elsewhere in the file depending on the exact syntax
> problem.\n\nThe offending line appears to be:\n\n\n- name: 'Run devel
> installer'\n ^ here\n"}
>
> registry:
>   box: centos7
>   ansible:
> group: 'devel'
> variables:
>   katello_devel_github_username: "thomasmckay"
>   foreman_installer_module_prs: "katello/capsule/101"
>   foreman_installer_options: "--capsule-docker-registry-port=5001"
>   atomic_registry_registry_port: "5000"
> playbook:
> - 'playbooks/katello_devel.yml'
> - 'playbooks/katello_atomic_registry.yml'
>
>
>
> On Sat, Oct 22, 2016 at 8:58 AM, Eric D Helms 
> wrote:
>
>> 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 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,theforema
>>> n/foreman_proxy/303"
>>>   foreman_installer_options: "--capsule-docker-registry-port=5001"
>>>   atomic_registry_registry_port: "5000"
>>> playbook:
>>> - 'playbooks/katello.yml'
>>> - 'playbooks/katello_atomic_registry.yml'
>>>
>>>
>>> On Sat, Oct 22, 2016 at 8:11 AM, Eric D Helms 
>>> wrote:
>>>
 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 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 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: >-
>>> --katello-devel-use-rvm=false
>>> --katello-devel-github-username=thomasmckay
>>> --katello-devel-enable-ostree=true
>>>   options: >-
>>> --scenario katello-devel
>>> --disable-selinux
>>> --koji-repos
>>>   memory: 8192
>>>   cpus: 4
>>>   hostname: katello.example.com
>>>   networks:
>>> - type: 'private_network'
>>>   options:
>>> ip: 192.168.100.219
>>> libvirt__network_name: provisioning
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups 

Re: [foreman-dev] help using forklift for katello dev box

[Tom McKay]

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 that
accomplished? Also need to enable ostree.

I can be on IRC today, if that is easier.

Running these PRs together:
https://github.com/Katello/forklift/pull/279
https://github.com/Katello/forklift/pull/325

Fatal: [registry]: FAILED! => {"failed": true, "msg": "The conditional
check 'skip_installer == False' failed. The error was: error while
evaluating conditional (skip_installer == False): 'skip_installer' is
undefined\n\nThe error appears to have been in
'/home/thomasmckay/code/forklift/playbooks/roles/katello_devel/tasks/main.yml':
line 12, column 3, but may\nbe elsewhere in the file depending on the exact
syntax problem.\n\nThe offending line appears to be:\n\n\n- name: 'Run
devel installer'\n ^ here\n"}

registry:
  box: centos7
  ansible:
group: 'devel'
variables:
  katello_devel_github_username: "thomasmckay"
  foreman_installer_module_prs: "katello/capsule/101"
  foreman_installer_options: "--capsule-docker-registry-port=5001"
  atomic_registry_registry_port: "5000"
playbook:
- 'playbooks/katello_devel.yml'
- 'playbooks/katello_atomic_registry.yml'



On Sat, Oct 22, 2016 at 8:58 AM, Eric D Helms  wrote:

> 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 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,theforema
>> n/foreman_proxy/303"
>>   foreman_installer_options: "--capsule-docker-registry-port=5001"
>>   atomic_registry_registry_port: "5000"
>> playbook:
>> - 'playbooks/katello.yml'
>> - 'playbooks/katello_atomic_registry.yml'
>>
>>
>> On Sat, Oct 22, 2016 at 8:11 AM, Eric D Helms 
>> wrote:
>>
>>> 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 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 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: >-
>> --katello-devel-use-rvm=false
>> --katello-devel-github-username=thomasmckay
>> --katello-devel-enable-ostree=true
>>   options: >-
>> --scenario katello-devel
>> --disable-selinux
>> --koji-repos
>>   memory: 8192
>>   cpus: 4
>>   hostname: katello.example.com
>>   networks:
>> - type: 'private_network'
>>   options:
>> ip: 192.168.100.219
>> libvirt__network_name: provisioning
>>
>> --
>> 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 an email to foreman-dev+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> 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
> an email to foreman-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

 --
 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
 an email to foreman-dev+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

>>>
>>>
>>>
>>> --
>>> Eric D. Helms
>>> Red Hat Engineering
>>> Ph.D. Student - North Carolina State University

Re: [foreman-dev] help using forklift for katello dev box

[Eric D Helms]

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 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_installer_options: "--capsule-docker-registry-port=5001"
>   atomic_registry_registry_port: "5000"
> playbook:
> - 'playbooks/katello.yml'
> - 'playbooks/katello_atomic_registry.yml'
>
>
> On Sat, Oct 22, 2016 at 8:11 AM, Eric D Helms 
> wrote:
>
>> 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 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 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: >-
> --katello-devel-use-rvm=false
> --katello-devel-github-username=thomasmckay
> --katello-devel-enable-ostree=true
>   options: >-
> --scenario katello-devel
> --disable-selinux
> --koji-repos
>   memory: 8192
>   cpus: 4
>   hostname: katello.example.com
>   networks:
> - type: 'private_network'
>   options:
> ip: 192.168.100.219
> libvirt__network_name: provisioning
>
> --
> 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
> an email to foreman-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
 --
 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
 an email to foreman-dev+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

>>>
>>> --
>>> 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
>>> an email to foreman-dev+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Eric D. Helms
>> Red Hat Engineering
>> Ph.D. Student - North Carolina State University
>>
>> --
>> 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 an
>> email to foreman-dev+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> 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 an
> email to foreman-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University

-- 
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 an email 
to foreman-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-dev] help using forklift for katello dev box

[Tom McKay]

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_installer_options: "--capsule-docker-registry-port=5001"
  atomic_registry_registry_port: "5000"
playbook:
- 'playbooks/katello.yml'
- 'playbooks/katello_atomic_registry.yml'


On Sat, Oct 22, 2016 at 8:11 AM, Eric D Helms  wrote:

> 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 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 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: >-
 --katello-devel-use-rvm=false
 --katello-devel-github-username=thomasmckay
 --katello-devel-enable-ostree=true
   options: >-
 --scenario katello-devel
 --disable-selinux
 --koji-repos
   memory: 8192
   cpus: 4
   hostname: katello.example.com
   networks:
 - type: 'private_network'
   options:
 ip: 192.168.100.219
 libvirt__network_name: provisioning

 --
 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
 an email to foreman-dev+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

>>> --
>>> 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
>>> an email to foreman-dev+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>> 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 an
>> email to foreman-dev+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Eric D. Helms
> Red Hat Engineering
> Ph.D. Student - North Carolina State University
>
> --
> 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 an
> email to foreman-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 an email 
to foreman-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-dev] help using forklift for katello dev box

[Eric D Helms]

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 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 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: >-
>>> --katello-devel-use-rvm=false
>>> --katello-devel-github-username=thomasmckay
>>> --katello-devel-enable-ostree=true
>>>   options: >-
>>> --scenario katello-devel
>>> --disable-selinux
>>> --koji-repos
>>>   memory: 8192
>>>   cpus: 4
>>>   hostname: katello.example.com
>>>   networks:
>>> - type: 'private_network'
>>>   options:
>>> ip: 192.168.100.219
>>> libvirt__network_name: provisioning
>>>
>>> --
>>> 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
>>> an email to foreman-dev+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> 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 an
>> email to foreman-dev+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> 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 an
> email to foreman-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University

-- 
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 an email 
to foreman-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-dev] help using forklift for katello dev box

[Tom McKay]

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 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: >-
>> --katello-devel-use-rvm=false
>> --katello-devel-github-username=thomasmckay
>> --katello-devel-enable-ostree=true
>>   options: >-
>> --scenario katello-devel
>> --disable-selinux
>> --koji-repos
>>   memory: 8192
>>   cpus: 4
>>   hostname: katello.example.com
>>   networks:
>> - type: 'private_network'
>>   options:
>> ip: 192.168.100.219
>> libvirt__network_name: provisioning
>>
>> --
>> 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 an
>> email to foreman-dev+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> 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 an
> email to foreman-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 an email 
to foreman-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-dev] help using forklift for katello dev box

[Eric D Helms]

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: centos7
>   shell: 'yum -y install ruby && cd /vagrant && ./setup.rb'
>   installer: >-
> --katello-devel-use-rvm=false
> --katello-devel-github-username=thomasmckay
> --katello-devel-enable-ostree=true
>   options: >-
> --scenario katello-devel
> --disable-selinux
> --koji-repos
>   memory: 8192
>   cpus: 4
>   hostname: katello.example.com
>   networks:
> - type: 'private_network'
>   options:
> ip: 192.168.100.219
> libvirt__network_name: provisioning
>
> --
> 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 an
> email to foreman-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 an email 
to foreman-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[foreman-dev] help using forklift for katello dev box

[Tom McKay]

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: >-
--katello-devel-use-rvm=false
--katello-devel-github-username=thomasmckay
--katello-devel-enable-ostree=true
  options: >-
--scenario katello-devel
--disable-selinux
--koji-repos
  memory: 8192
  cpus: 4
  hostname: katello.example.com
  networks:
- type: 'private_network'
  options:
ip: 192.168.100.219
libvirt__network_name: provisioning

-- 
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 an email 
to foreman-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.