You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The things I encountered that looks like bug either in SDDC Manager or OneView redfish connector:
All decommission tasks appears as failed in SDDC manager whereas the deprovision on OneView is successful ( I guess the issue is the same as for commissioning point 2)
Same problem for commissioning. this got solved by changing the retrydelay in redfish.conf
[event_service]
DeliveryRetryAttempts = 30
DeliveryRetryIntervalSeconds = 30
When adding a new template in OneView, it is never reflected in SDDC Manager, I had to restart so that it gets updated.
Impossible to use a self signed certificates with SDDC Manager
Important missing features in the connector
When provisioning a new server from SDDC Manager we should have the possibility to power it on. Currently you have options to poweroff a server to apply a server profile from the connector but not to power it on automatically after provisioning.
this is really important because the message is : When you use this connector you do not need to connect to OneView to manage the server. And here this is false because we need to connect to OneView to power it on
We should have the possibility to set the boot_once parameter to pxe or http/https boot so that the server can get provisioned automatically after boot.
Last point I am wondering, you do not apply a template to a server profile but get the template and rebuild the xml based on this template.
This gives 2 issues for me :
With the OneView for vCenter plugin, as it checks any cluster based on their server profile template deployment. So you cannot use at all this plugin with redfish connector
To check if a server profile is compliant with the template that was used for deployment. If you need to modify the server profile afterward you need to modify all of them one by One without any means to check if the modification was really applied and that you did not miss any of the servers. This cannot happen with a server profile template compliance verification.
I would rather deploy the server profile based on its template
The text was updated successfully, but these errors were encountered:
You wrote: "Impossible to use a self signed certificates with SDDC Manager."
Where do you need not self signed certificates? Are they already necessary when conneting the redfish-translation-toolkit itself? Which errors did you see when using the self-signed certificates and how did you install the certificates?
The things I encountered that looks like bug either in SDDC Manager or OneView redfish connector:
[event_service]
DeliveryRetryAttempts = 30
DeliveryRetryIntervalSeconds = 30
Important missing features in the connector
this is really important because the message is : When you use this connector you do not need to connect to OneView to manage the server. And here this is false because we need to connect to OneView to power it on
Last point I am wondering, you do not apply a template to a server profile but get the template and rebuild the xml based on this template.
This gives 2 issues for me :
I would rather deploy the server profile based on its template
The text was updated successfully, but these errors were encountered: