Yedidyah Bar David has posted comments on this change.

Change subject: packaging: setup: fixing development environment on remote 
engine
......................................................................


Patch Set 3:

Yes, I actually thought about that (different prefixes) and ignored for now. It 
should not be difficult to add an env key for that if we really want to. 
Perhaps we should first let this whole thing stabilize a bit, then think a bit, 
then perhaps generalize some more - e.g. we might want to provide remote access 
not only to the engine, but also to dwh (from reports) etc.

-- 
To view, visit http://gerrit.ovirt.org/34259
To unsubscribe, visit http://gerrit.ovirt.org/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: I9b7e75dbf8ffe7a8c251232648685b0d6dbf592b
Gerrit-PatchSet: 3
Gerrit-Project: ovirt-engine
Gerrit-Branch: master
Gerrit-Owner: Simone Tiraboschi <[email protected]>
Gerrit-Reviewer: Lev Veyde <[email protected]>
Gerrit-Reviewer: Sandro Bonazzola <[email protected]>
Gerrit-Reviewer: Simone Tiraboschi <[email protected]>
Gerrit-Reviewer: Yedidyah Bar David <[email protected]>
Gerrit-Reviewer: [email protected]
Gerrit-Reviewer: oVirt Jenkins CI Server
Gerrit-HasComments: No
_______________________________________________
Engine-patches mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/engine-patches

Reply via email to