The new pattern still encapsulates options for creating a resource though. The name seems appropriate. To me, createOptions() says "build me the options for creating a resource".
That seems logical, but I'm just thinking in terms of how *Options is used everywhere else in jclouds: it's an *additional* argument to a call which modifies the way the response is provided. And it's almost always accompanied by a version of the call that does not require options.
Agreed that *Request probably isn't a good alternative as, if anything, it's even more overloaded. CreateParams? CreateArgs? CreateTemplate?
ap
