its come up before (rpc providers, shell script providers) but it doesn't quite fit with the upgrade and distribution model in juju-core and go atm. it is possible to layer on top of manual provider using a client side plugin to effectively automate machine creation for a given provider, i've published digital ocean and softlayer providers using that mechanism, it has some caveats compared to a native provider, but its still useful and functional.
cheers, Kapil On Mon, May 5, 2014 at 6:12 PM, Sebastian <[email protected]> wrote: > Taking the opportunity about this topic, what about making this pluggable, > like providers plugins, not into the core? > > Sebas. > > > > 2014-05-05 18:44 GMT-03:00 Adam Stokes <[email protected]>: > > I'd probably start here: >> >> http://bazaar.launchpad.net/~go-bot/juju-core/trunk/files/head:/provider/ >> >> This can give you an idea on how the ec2 implementation is done >> >> On Mon, May 5, 2014 at 10:56 AM, Benoît Canet <[email protected]> >> wrote: >> > >> > Hello, >> > >> > I am a developper planning to add the support for the Outscale cloud >> into >> > juju-core. >> > >> > The Outscale cloud implement most of the EC2 API. >> > >> > Does the Juju maintainer have some guidance on how the support should be >> > written ? >> > >> > Best regards >> > >> > Benoît Canet >> > Nodalink >> > >> > -- >> > Juju mailing list >> > [email protected] >> > Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/juju >> >> >> >> -- >> [ Adam Stokes ] >> >> -- >> Juju mailing list >> [email protected] >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/juju >> > > > -- > Juju mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju > >
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
