<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 7, 2016 at 5:39 PM, Dan Kenigsberg <span dir="ltr"><<a href="mailto:danken@redhat.com" target="_blank">danken@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><br>
0. The longest part of the installation was setting up DNS-DHCP-MAC for the<br>
future hosted engine VM. One should have it ready prior to the actual<br>
installation. Luckily, Roy Golan told me of that ahead of time.<br></blockquote><div><br></div><div>you can use /etc/hosts instead of DNS-DHCP-MAC for testing purposes</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
1. The release notes <a href="http://www.ovirt.org/develop/release-management/releases/3.6/" rel="noreferrer" target="_blank">http://www.ovirt.org/develop/release-management/releases/3.6/</a><br>
refer to the Quick Start Guide, but the latter is not updated with 3.6 content.<br></blockquote><div><br></div><div>and the release note page is a mess after the migration (opened <a href="https://github.com/oVirt/ovirt-site/issues/98">https://github.com/oVirt/ovirt-site/issues/98</a> ) </div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
2. I've started with a fully-updated Fedora 23 host, and installed<br>
<a href="http://plain.resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm" rel="noreferrer" target="_blank">http://plain.resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm</a> on it.<br>
<br>
3. It's a bad bad practice (don't try this at home), but I've modified<br>
/etc/yum.repos.d/ovirt-3.6.repo to look for fc22 packages, as fc23 is not<br>
supported of ovirt-3.6.<br>
<br>
4. The release notes ask to modify KexAlgorithms in sshd_config. This is a bit<br>
dishearting, and it would much better to explain WHY this is needed.<br></blockquote><div><br></div><div>original wiki page had a link to the bz: <a rel="nofollow" class="" href="http://bugzilla.redhat.com/1225531" style="color:rgb(0,85,128);font-weight:600;outline:0px;padding-right:13px;font-family:'Source Sans Pro',sans-serif;font-size:14px;line-height:20px;background-image:url("images/external-link-ltr-icon.png");background-repeat:no-repeat">BZ 1225531</a></div><div>which got dropped by the automated conversion to the new website format (again, <a href="https://github.com/oVirt/ovirt-site/issues/98">https://github.com/oVirt/ovirt-site/issues/98</a> )</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
5. <a href="http://www.ovirt.org/develop/release-management/features/heapplianceflow/" rel="noreferrer" target="_blank">http://www.ovirt.org/develop/release-management/features/heapplianceflow/</a><br>
has two broken links to jobs that create the hosted engine appliance. I<br>
found my appliance image in<br>
<a href="http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-3.6_build-artifacts-el7-x86_64/" rel="noreferrer" target="_blank">http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-3.6_build-artifacts-el7-x86_64/</a></blockquote><div><br></div><div>Opened <a href="https://github.com/oVirt/ovirt-site/issues/125">https://github.com/oVirt/ovirt-site/issues/125</a></div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><br>
<br>
6. While running `hosted-engine --deploy` I was greeted with<br>
[WARNING] OVF does not contain a valid image description, using default.<br>
which suggest that there's a little problem in the appliance, right?<br></blockquote><div><br></div><div>Fabian, can you work with Dan and see why image description is missing?</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
7. After the installation, I've lost connection to my host: it appears that<br>
prior to the installation, dhclient on the host used something other than<br>
because /var/lib/dhclient/dhclient--eno1.lease to store the DUID. Thus, I've<br>
experienced <a href="https://bugzilla.redhat.com/1219429" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/1219429</a> where ovirtmgmt was given a<br>
fresh IP address. We may need to extract DUID right from the running<br>
dhclient, Ondra.<br></blockquote><div><br></div><div>have you opened a bz for this?</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
8. After resolving this, and adding storage to the default datacenter, Engine<br>
has imported its own VM, and presented it clearly.<br>
<br>
9. Despite the several hurdles and hacks, installation was quick and uneventful.<br></blockquote><div><br></div><div>Great!</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
Kudos to the hosted-engine, appliance, and sla teams!<br>
<br>
</blockquote></div><br>Thanks,<br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr">Sandro Bonazzola<br>Better technology. Faster innovation. Powered by community collaboration.<br>See how it works at <a href="http://redhat.com" target="_blank">redhat.com</a><br></div></div></div></div>
</div></div>