cf-charmers team mailing list archive

[Benjamin Saller <benjamin.saller@xxxxxxxxxxxxx>]

The readme and instructions don't list using juju-deployer with the
generated bundle as a supported target and it isn't. If you do this you
wouldn't have an orchestrator and so each charm in the bundle as currently
rendered will be missing its orchestrator relation which is used for
central configuration, including telling the charms which version of the
assets to pull down. Even if they deploy they won't work w/o serious
modification.

Why do you even feel this is an important target? Without the orchestrator
nothing would be able to preform upgrades or automate actions on the entire
system, you lose its central point of configuration, etc.

-Ben


On Mon, Sep 8, 2014 at 6:52 AM, Alexander Lomov <lomov.as@xxxxxxxxx> wrote:

> BTW I tried juju-deployer with a different simple bundle and it worked. Do
> have idea what can be wrong with deployment of generated bundle? Could it
> be because it can't see local repository with charms?
>
> On 8 September 2014 13:18, Alexander Lomov <lomov.as@xxxxxxxxx> wrote:
>
>> Hi, Kapil. Hello, all.
>>
>> As I understand it should be possible to deploy CF charms using charms
>> that was generated with charmgen/generator.py script and juju-deployer.
>> Unfortunately I can't juju-deployer works here.
>>
>> I got this stack trace trying to run juju-deployer -vdWc bundles.yaml
>> with cloudfoundry-r180 release:
>> https://gist.githubusercontent.com/allomov/188131c84fdbcbab5ea8/raw/0bf997e37dc22898699ef3505e037a9c06124374/juju-deployer-fail.log
>>
>> Here is information about versions:
>> https://gist.githubusercontent.com/allomov/188131c84fdbcbab5ea8/raw/4ebdae01cf6e13293a850e0968ab9a76e45e4a91/deployert-versions
>>
>>
>> Best wishes,
>> Alex L.
>>
>
>
> --
> Mailing list: https://launchpad.net/~cf-charmers
> Post to     : cf-charmers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~cf-charmers
> More help   : https://help.launchpad.net/ListHelp
>
>