environs.EnvironProvider, did I stutter ?
roger peppe
roger.peppe at canonical.com
Thu Aug 9 11:07:00 UTC 2012
FWIW, here's an excerpt from the original discussion from which the name came:
[Thursday 13 October 2011] [17:43:12] <niemeyer> The interface you've
named as Environment is actually a MachineProvider
[Thursday 13 October 2011] [17:43:19] <niemeyer> juju/providers/common/base.py
[Thursday 13 October 2011] [17:43:31] <niemeyer> Naming it just as
Provider sounds good, though
[Thursday 13 October 2011] [17:43:52] <niemeyer> But I'd rather not do
that inversion to make people migrate more easily
[Thursday 13 October 2011] [17:44:28] <niemeyer> Or, there's another possibility
[Thursday 13 October 2011] [17:44:32] <rog> hmm, i'll have to think
[Thursday 13 October 2011] [17:44:33] <niemeyer> We kill one of the
terms entirely
[Thursday 13 October 2011] [17:44:43] <niemeyer> Which doesn't sound bad either
[Thursday 13 October 2011] [17:45:08] <rog> i like the fact that my
Environment maps one to one with the environments specified in the
environments file
[Thursday 13 October 2011] [17:45:21] <niemeyer> Yeah, I like it too
[Thursday 13 October 2011] [17:45:27] <niemeyer> Ok, here is an idea
[Thursday 13 October 2011] [17:45:31] <rog> and that my Providers map
one to one with the various providers, ec2, orchestra etc
[Thursday 13 October 2011] [17:45:49] <niemeyer> First, let's please
use "Environ" rather than "Environment" :-)
[Thursday 13 October 2011] [17:46:01] <niemeyer> The latter is too
long and boring to type all the type
[Thursday 13 October 2011] [17:46:02] <niemeyer> time
[Thursday 13 October 2011] [17:46:14] <rog> ok
[Thursday 13 October 2011] [17:46:18] <niemeyer> Then, to make people
more comfortable with the idea that we're "inverting" the terms,
[Thursday 13 October 2011] [17:46:34] <niemeyer> We can just name the
interface you have today as "Provider" to "EnvironProvider"
[Thursday 13 October 2011] [17:46:45] <niemeyer> To make it clear that
we're killing the old concept of a MachineProvider
so i guess it comes down to how concerned we are about people
migrating from the python version.
More information about the Juju-dev
mailing list