Adding own provider?

[Patrik Karisch]

Hi Marco,

basically I have to options:

1. Create a plugin, which utilizes the API and creates the machines, adds
them to juju manual provisioning.
    - Is IMHO ok, since I can call every juju command from the plugin
itself, eg. juju iwstack expose to config the firewall and within call juju
expose to set the state of the machine as exposed.

2. Fork the core, learn go, add my own provider, work with the fork until I
think it's stable and then create the Pull Request.
    - Since many different cloud provider are now based on Apache
CloudStack too, it is worth considering to contribute an official provider..

Marco Ceppi <marco.ceppi at canonical.com> schrieb am So., 10. Jan. 2016 um
11:37 Uhr:

> Providers are a part of the juju core as it stands today. That said, the
> core team has made strides to make creating providers easier with Juju.
> I'll let one of them chime in.
>
> Marco
>
> On Sun, Jan 10, 2016, 11:55 AM Patrik Karisch <patrik.karisch at gmail.com>
> wrote:
>
>> Hi there,
>>
>> is it possible without contributing to the juju source to add a provider?
>> I know the Digital Ocean provider, which is a plugin, but it uses manual
>> provisioning and doesn't hook into Juju.
>>
>> I need to add a provider which hooks into Juju and supports for example
>> expose to configure the Firewalls, etc.
>>
>> Cheerz, Patrik
>>
> --
>> Juju mailing list
>> Juju at lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20160110/59f72c38/attachment.html>