From: Ian Main imain@redhat.com Date: Fri, 18 Mar 2011 19:08:43 -0400
Really it would be best for the IP information to end up in the condor job, but that's a side point. In order to facilitate some of the IP schemes you would need a long-running stateful process is all I'm saying.
Please keep in mind (everybody) that the only known use case for this backend is in support of cloud engine. In that scenario, there will, by definition, be a config server. Part of the job of the config server is to communicate IP addresses of clients back to cloud engine. Therefore any other work which we introduce for retrieving IP addresses etc is, by definition, gratuitous.
Similar statements apply to authentication of clients. There's already a scheme in place for getting IPA integrated into the mix, OTPs handed out and coordinated etc.
At such time as we identify a use case for condor backend which involves running outside cloud engine, it will become more interesting to deal with some of those other things.
Yes they can I just thought you wouldn't want those things in a driver. Again I hadn't considered the standalone-deltacloud case.
Good. Because that's not the use case that's on the table.