Seeing and issue where users are not able to log in. Also for some reason
the engine is seemingly forgeting about AD users. Removing the AD domain
via engine-manage-domains and re-adding it works for enumerating the users,
however the first attempt to login as a user results in the engine no
longer enumerating the users nor allowing logins.
Attached are the pertinent logs.
Engine is built and running from current master as of this morning, and was
installed/built and upgraded via RPMs yum/engine-upgrade
A broad question here, perhaps not a possibility but I figured I would toss
it out there anyway.
VDSM is great at what it does, however there are those times when direct
manipulation of libvirt or libvirt VM configuration would be very handy.
The safe defaults and tested VM configurations that VDSM/ovirt provides are
great. However at times it would be nice to simply connect to a hypervisor
managed by ovirt/vdsm and make a couple changes to a VM (via virt-manager
or directly via virsh).
This could be enabling a new feature that has made it's way into
QEMU/libvirt/KVM or tweaking a VM configuration for whatever reason. Now
there is nothing stopping someone from doing this now either directly or
via VDSM hooks. Hooks are a pain along with the custom properties to jack
them into engine. Direct manipulation of libvirt since it has been
upstarted by vdsm results in an unhappy VDSM/engine.
I made some mistake in the upgrade of my engine (which is my bad) but then I noticed that when one service initialization fails, the rest of the services are not initialized, but still the engine will start even then and it did not even log.
There are some patterns in that single method on initialization, some work with 'try', some spawn a new thread. Can we have this cleaned up?
What I was thinking of is that each service should be initialized, creating a thread is it's own business, exceptions from initialization should be caught, logged and engine startup should be prevented if any service fails to initialize.
Content-Type: text/plain; charset=GBK
does now engine support join vm to AD?
on UI there is a configuration option for windows domain, how to use it?
Content-Type: text/html; charset=GBK
<div style="line-height:1.7;color:#000000;font-size:14px;font-family:arial"> hi,all<br>does now engine support join vm to AD?<br>on UI there is a configuration option for windows domain, how to use it?<br><br>thanks.<br></div><br><br><span title="neteasefooter"><span id="netease_mail_footer"></span></span>
While reviewing a change to allow using an ovf image in hosted-engine, I
searched and found that there is a project called "open-ovf". It's a
python library to work with ovf images.
Using it might make sense in hosted engine and image-uploader, perhaps
Did we ever discuss using it? Are there any obvious obstacles?