I usually deploy with only a basic KS that places an ssh cert on the host. Then ansible adds the repos and adjusts the network and iscsi initiator , the ovirt bootstrap takes care of the rest On Mar 2, 2016 5:42 PM, "Duckworth, Douglas C" <duckd@tulane.edu> wrote:

Never mind. This seems to be a place to start:

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualizat...

https://access.redhat.com/solutions/41697

-- Thanks

Douglas Duckworth, MSc, LFCS Unix Administrator Tulane University Technology Services 1555 Poydras Ave NOLA -- 70112

E: duckd@tulane.edu O: 504-988-9341 F: 504-988-8505

On 03/02/2016 04:06 PM, Duckworth, Douglas C wrote:

...

Does anyone have a kickstart available to share? We are looking to automate hypervisor deployment with Cobbler.

Thanks Doug

_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

On Fri, Mar 4, 2016 at 4:33 PM, Duckworth, Douglas C <duckd@tulane.edu> wrote:

We also use Ansible

Could you share your role / playbook for networks?

All I use it for is to set one NIC up with an IP address, so the engine can reach it. The rest is done via the engine. I probably should just do this with DHCP and MAC reservations really As for iscsi: - name: iSCSI initiator node.session.cmds_max adjustment lineinfile: dest=/etc/iscsi/iscsid.conf regexp='^node.session.cmds_max' line='node.session.cmds_max = 1024' state=present - name: iSCSI initiator node.session.queue_depth adjustment lineinfile: dest=/etc/iscsi/iscsid.conf regexp='^node.session.queue_depth' line='node.session.queue_depth = 128' state=present - name: iSCSI initiatorname set lineinfile: dest: /etc/iscsi/initiatorname.iscsi regexp: '^InitiatorName=iqn' line: '{{ "InitiatorName=iqn.2010-12.com.maxbetgroup:" + inventory_hostname }}' notify: - restart iscsi - restart iscsid handlers: - name: restart iscsi service: name=iscsi state=restarted - name: restart iscsid service: name=iscsid state=restarted

Thanks Doug

-- Thanks

Douglas Duckworth, MSc, LFCS Unix Administrator Tulane University Technology Services 1555 Poydras Ave NOLA -- 70112

E: duckd@tulane.edu O: 504-988-9341 F: 504-988-8505

On 03/02/2016 05:50 PM, Dan Yasny wrote:

...

I usually deploy with only a basic KS that places an ssh cert on the host. Then ansible adds the repos and adjusts the network and iscsi initiator , the ovirt bootstrap takes care of the rest

On Mar 2, 2016 5:42 PM, "Duckworth, Douglas C" <duckd@tulane.edu <mailto:duckd@tulane.edu>> wrote:

Never mind. This seems to be a place to start:

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualizat...

...

https://access.redhat.com/solutions/41697

-- Thanks

Douglas Duckworth, MSc, LFCS Unix Administrator Tulane University Technology Services 1555 Poydras Ave NOLA -- 70112

E: duckd@tulane.edu <mailto:duckd@tulane.edu> O: 504-988-9341 <tel:504-988-9341> F: 504-988-8505 <tel:504-988-8505>

On 03/02/2016 04:06 PM, Duckworth, Douglas C wrote: > Does anyone have a kickstart available to share? We are looking to > automate hypervisor deployment with Cobbler. > > Thanks > Doug > _______________________________________________ Users mailing list Users@ovirt.org <mailto:Users@ovirt.org> http://lists.ovirt.org/mailman/listinfo/users

I install a bunch of packages too, but I use full RHEL hosts, so it's just a matter of running yum. On Fri, Mar 4, 2016 at 4:53 PM, Duckworth, Douglas C <duckd@tulane.edu> wrote:

"All I use it for is to set one NIC up with an IP address, so the engine can reach it. The rest is done via the engine. I probably should just do this with DHCP and MAC reservations really"

Ah thanks. So we can do that with kernel options too. I wasn't sure if we should even bother with bonds though since the manager will do the rest.

Thanks for sharing your iscsid.conf. We're using the copy module to place our modified one on the hypervisor, though your solution might be more elegant, along with others that modify rsyslog and cron, then persisting those files:

- name: unpersist conf files on HV tags: [conf] command: "unpersist {{ item.destdir }}/{{ item.name }}" with_items: hv_files

- name: copy conf files to hv tags: [conf] copy: src="{{ item.name }}" dest="{{ item.destdir }}/{{ item.name }}" mode="{{ item.mode }}" owner=root group=root with_items: hv_files

- name: persist conf files on HV tags: [conf] command: "persist {{ item.destdir }}/{{ item.name }}" with_items: hv_files notify: - rsyslog - crond

How do people handle installing additional packages [we add htop, vim, iftop, nethogs, diamond, check_mk] to the hypervisor after deployment?

After remounting rw we use this task to copy rpms from Apache server:

- name: install rhel7 packages command: "rpm -i {{ item.destdir }}/{{ item.name }}" with_items: rh7_rpm_files register: rpm_result when: ansible_distribution_major_version == "7" failed_when: "rpm_result.rc == 69"

-- Thanks

Douglas Duckworth, MSc, LFCS Unix Administrator Tulane University Technology Services 1555 Poydras Ave NOLA -- 70112

E: duckd@tulane.edu O: 504-988-9341 F: 504-988-8505

On 03/04/2016 03:41 PM, Dan Yasny wrote:

...

All I use it for is to set one NIC up with an IP address, so the engine can reach it. The rest is done via the engine. I probably should just do this with DHCP and MAC reservations really

Small correction, we have that since 3.5. Regards, Oved On Mar 3, 2016 22:18, "Yaniv Kaul" <ykaul@redhat.com> wrote:

Note that in 3.6 we have great integration with Foreman, for bare-metal to fully functional host. I urge you to look at the slides and video of the relevant presentation we've had at Fosdem[1].

Y.

[1] https://fosdem.org/2016/schedule/event/virt_iaas_host_lifecycle_content_mana...

On Thu, Mar 3, 2016 at 12:06 AM, Duckworth, Douglas C <duckd@tulane.edu> wrote:

...

Does anyone have a kickstart available to share? We are looking to automate hypervisor deployment with Cobbler.

Thanks Doug

-- Thanks

Douglas Duckworth, MSc, LFCS Unix Administrator Tulane University Technology Services 1555 Poydras Ave NOLA -- 70112

E: duckd@tulane.edu O: 504-988-9341 F: 504-988-8505 _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users