I tried to reply and didn't noticed I wasn't logged in, so it started a new 
thread. Can finally update you all!

So I have the engine installed to the node. For some reason, the node-engine 
looks for certs in a different spot than the CentOS-engine. Soft linking, so 
the cert is in both spots, lets the setup complete:
   ln -s /etc/pki/ovirt-engine/apache-ca.pem /etc/pki/vdsm/certs/cacert.pem
   ln -s /etc/pki/ovirt-engine/certs/apache.cer /etc/pki/vdsm/certs/vdsmcert.pem
   ln -s /etc/pki/ovirt-engine/keys/apache.key.nopass 
/etc/pki/vdsm/keys/vdsmkey.pem

After that, I add the host to the engine through the python sdk / API. I'm 
still having a problem starting a VM. The host's status is "up" externally, but 
not active. I can't find how to activate it through the sdk, the docs have an 
example only through the GUI. If I hit the endpoint it shows:

wget --user=admin@internal --password=fake 
--ca-certificate=/etc/pki/ovirt-engine/apache-ca.pem --output-document - 
"https://localhost.localdomain:443/ovirt-engine/api/hosts/some_random_id/activate";

then I get a "405 Method Not Allowed" back. If I list all the attributes for a 
host in python, none of them look like they can activate it:

```python
host_service = connection.system_service().hosts_service()
print( dir(host_service.list()[0]) )
# Prints a lot of attr's, but none activate related that I see.
```

The internal status of the node is non_operational, and detail says 
"network_unreachable". Is this expected when you first link a engine to a node? 
If so, is there a way to activate a node through the API?

Or is this where the engine and host start to step on each-other, and thus why 
this configuration isn't supported?
_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/[email protected]/message/LNNWD5BPQUT3XRQQA52WQNRJX5F2CVJZ/

Reply via email to