Hello everyone,

I'm also a new contributer to XCP-ng!
For now I'll be working with @ronan-a on the SMAPIv3 plugins.
After that probably on open vSwitch.

Benjamin

Hi!

The fix is available on master.
You should be able to generate certificate now.

Yes it's 5396b90695fbe2c7a5f56d72a94a208517b2d517 but its not its only modification so it can't just be reverted.
This is a really quick fix I can push a branch today and it can be used waiting for the merge.

Hi!

The fix is available on master.
You should be able to generate certificate now.

Yes it's 5396b90695fbe2c7a5f56d72a94a208517b2d517 but its not its only modification so it can't just be reverted.
This is a really quick fix I can push a branch today and it can be used waiting for the merge.

Hi,

I've managed to reproduce you're error. It's not a build issue.
A fix is coming right away, I'll post it here once it's merged into master so you can get it.

Thanks for the report.
Regards

I've just tried locally from sources and everything went fine.

Can you try to call yarn and then yarn build at the root of xen-orchestra repository?

Thanks

That's strange, did you follow the official guide to build xen-orchestra from sources?
All dependencies should be installed.

Hello,

There's 2 ways to use the SDN controller as for the certificates:

• You can provide the vertificate yourself, if you arleardy have certificates, in this case you need to provide a path to the certificate directory in the plugin configuration and make sure that there is client-cert.pem, client-key.pem and ca-cert.pem in the directory
• If you don't have certificates, the SDN controller can create them, but they will be self signed. To do so you just leave the certificate configuration path empty.

Is that clear?

Regards,
Benjamin

Hello everyone,

I'm also a new contributer to XCP-ng!
For now I'll be working with @ronan-a on the SMAPIv3 plugins.
After that probably on open vSwitch.

Benjamin