Skip to content

Conversation

@robhoes
Copy link

@robhoes robhoes commented Jul 26, 2016

No description provided.

robhoes added 2 commits July 27, 2016 00:16
Signed-off-by: Rob Hoes <[email protected]>
We add PVS proxy keys to the "extra" private key map for setup-pvs-proxy-rules
to process. Previously, xapi would include the xenstore keys in the VIF metadata,
but now xapi uses the new Vif.pvs_proxy field and xenopsd translates it into
xenstore keys.

To recap, in xenstore, it looks as follows:

/xapi/<uuid>/private/vif/0/pvs-interface = "pvs-xenbr0"
/xapi/<uuid>/private/vif/0/pvs-server-num = "2"
/xapi/<uuid>/private/vif/0/pvs-server-0-addresses = "192.168.0.1,192.168.0.2"
/xapi/<uuid>/private/vif/0/pvs-server-0-ports = "5000-5020"
/xapi/<uuid>/private/vif/0/pvs-server-1-addresses = "192.168.0.3,192.168.0.4"
/xapi/<uuid>/private/vif/0/pvs-server-1-ports = "5000-5020"

Signed-off-by: Rob Hoes <[email protected]>
@robhoes
Copy link
Author

robhoes commented Jul 26, 2016

Depends on xenserver/xcp-idl#6.

@robhoes
Copy link
Author

robhoes commented Jul 26, 2016

@lindig Could you review this please?

@lindig
Copy link

lindig commented Jul 27, 2016

I don't have the design entirely in my head but the code looks on the smaller level really solid.

@robhoes robhoes merged commit 9fee579 into xenserver:trunk-pvs-direct Jul 27, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants