<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 22, 2015 at 5:38 PM, Simone Tiraboschi <span dir="ltr"><<a href="mailto:stirabos@redhat.com" target="_blank">stirabos@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"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Thu, Oct 22, 2015 at 5:28 PM, Gianluca Cecchi <span dir="ltr"><<a href="mailto:gianluca.cecchi@gmail.com" target="_blank">gianluca.cecchi@gmail.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"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span>On Thu, Oct 22, 2015 at 5:08 PM, Simone Tiraboschi <span dir="ltr"><<a href="mailto:stirabos@redhat.com" target="_blank">stirabos@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"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span><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"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div>engine is up and admin web portal accessible and host results up.</div><div><br></div><div>I expected storage to be configured inside admin web portal but apparently I don't see anything already configured and also I don't see the sh engine VM listed... is it correct?</div></div></div></div></blockquote><div><br></div></span><div>No, we have an open bug on that:</div><div><a href="https://bugzilla.redhat.com/show_bug.cgi?id=1269768" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1269768</a><br></div><div><br></div><div>You can try to manually import it in the mean time.</div></div></div></div></blockquote><div><br></div></span><div>Ok, I'll try.</div><div>So when bug solved, if I have a problem with the engine and for example I'm not able to connect to it through ssh and/or web admin console, what other means would I have to connect to it console and check (eg if it is in kernel panic for any reason)?</div></div></div></div></blockquote><div><br></div></span><div>Ehm if the engine VM is not responding you cannot use the engine to check it. </div><div>But you have an HA agent that monitors it for you and can restart if needed.</div><div><br></div><div>You can also use ssh with the root password you set via cloud-init.</div><span class=""><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"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>During setup I was proposed to connect via remote-viewer via a temporary password; I imagine this way is not usable after install, correct?</div></div></div></div></blockquote><div><br></div></span><div>You can use</div><div>hosted-engine --add-console-password to set another temporary password.</div><span class=""><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"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span><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"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div>But hosted-engine storage domain can just contain the engine VM so you still need to add a regular storage domain for other VMs.</div><span><div><br></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"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br></div></div></div></div></blockquote></span></div></div></div></blockquote><div><br></div><div><br></div></span><div>Ah, ok. I thought that the initial storage domain would have become the first storage domain for general VMs purposes too...</div><div>So actually if on dedicated filesystem/device, it could be small in size, say 5-10Gb if I use the appliance, correct?</div><span><div><br></div></span></div></div></div></blockquote><div><br></div></span><div>20GB is the minimum recommended value plus you need additional space for ancillary storage domain data structured so I'd avoid allocating less than 25GB.</div><span class=""><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"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span><div></div><div> <br></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"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span><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"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div></div><div>BTW: what is the 2Gb file system on loop device?</div></div></div></div></blockquote><div><br></div></span><div>It was used by hosted-engine-setup as a fake storage pool to bootstrap the hosted-engine storage domain.</div><div>It shouldn't be there at the end.</div><div>Could you please attach hosted-engine-setup logs to let me check why it's still there?</div></div></div></div></blockquote><div><br></div></span><div>here it is:<br></div><div><a href="https://drive.google.com/file/d/0BwoPbcrMv8mvRFFKSmR0REN3Qkk/view?usp=sharing" target="_blank">https://drive.google.com/file/d/0BwoPbcrMv8mvRFFKSmR0REN3Qkk/view?usp=sharing</a></div></div></div></div></blockquote><div><br></div></span><div>Thanks</div></div></div></div></blockquote><div><br></div><div>That ovirt-hosted-engine-setup attempt used /dev/loop0 and it got correctly detached at the end.</div><div><br></div><div>2015-10-22 15:51:28 DEBUG otopi.plugins.ovirt_hosted_engine_setup.storage.storage plugin.executeRaw:828 execute: ('/sbin/losetup', '--detach', u'/dev/loop0'), executable='None', cwd='None', env=None</div><div>2015-10-22 15:51:28 DEBUG otopi.plugins.ovirt_hosted_engine_setup.storage.storage plugin.executeRaw:878 execute-result: ('/sbin/losetup', '--detach', u'/dev/loop0'), rc=0</div><div><br></div><div>So that /dev/loop3 is probably just a leftover of one of your previous attempts. I think you can safely remove it.</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"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class=""><div><br></div><div><br></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"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span><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"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span><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"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div>I configured the storage domain part as NFS, pointing to ovc71.localdomain.local:/NFS_DOMAIN</div><div>Reading page at</div><div><a href="http://www.ovirt.org/Features/Self_Hosted_Engine" target="_blank">http://www.ovirt.org/Features/Self_Hosted_Engine</a><br></div><div><br></div><div>it is not clear to me what to do next if I want for example keep a single host with its sh engine as a replacement concept of what before was all-in-one... and start creating VMs....</div></div></div></div></blockquote><div><br></div></span><div>You have to setup your first regular data domain for other VMs: you can add another NFS one.</div></div></div></div></blockquote><div><br></div></span><div>OK.</div><div>In case I want to setup a single host with self hosted engine, could I configure on hypervisor</div><div>a) one NFS share for sh engine</div><div>b) one NFS share for ISO DOMAIN</div><div>c) a local filesystem to be used to create then a local POSIX complant FS storage domain </div><div>and work this way as a replacement of all-in-one?<br></div></div></div></div></blockquote><div><br></div></span><div>Yes but c is just a workaround, using another external NFS share would help a lot if in the future you plan to add o to migrate to a new server.</div><span class=""><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"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div></div><span><div> </div><div><br></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"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span><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"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span><font color="#888888"><div><br></div></font></span></div></div></div></blockquote><div><br></div></span><div>Put the host in global maintenance (otherwise the engine VM will be restarted)</div><div>Shutdown the engine VM</div><div>Shutdown the host</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"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span><font color="#888888"><div></div><div><br></div></font></span></div></div></div></blockquote></div></div></div></blockquote><div><br></div></span><div>Ok. And for starting all again, is this correct:</div><div><br></div><div>a) power on hypevisor</div><div>b) hosted-engine --set-maintenance --mode=none</div><div><br></div><div>other steps required?</div></div><br></div></div></blockquote><div> </div></span></div>No, that's correct</div></div>
</blockquote></div><br></div></div>