cf-charmers team mailing list archive

[Cory Johns <cory.johns@xxxxxxxxxxxxx>]

Just to clarify, I was referring to the cf-mysql-broker charm, and
upon re-checking it, it's attempting to call the CF CLI in the upstart
script, which shouldn't actually be called until CF is ready after
all, so maybe just daemonizing it properly is the correct solution if
it really needs to sleep-wait for the API to be ready.  However, it
doesn't seem like this belongs in the upstart script, and should be
moved to the charm using requests, as previously mentioned.

On Thu, Jun 19, 2014 at 9:05 AM, Cory Johns <cory.johns@xxxxxxxxxxxxx> wrote:
> My understanding was that it was a REST API
> (http://docs.cloudfoundry.org/services/api.html) and that you would
> just use requests
> (http://docs.python-requests.org/en/latest/index.html) or similar; am
> I misunderstanding the issue?
>
> Also, one big problem I ran into with the charm was that it attempted
> to communicate with CF before it was ready, and ended up blocking
> Juju, such that no further Juju commands would be responded to, even
> though nothing was in an error state.  (That this is possible, is also
> an issue in Juju, but we should avoid it in the charm, as well.  Also,
> the communication would fail anyway, since CF wasn't ready and was
> blocked on the broker charm to become ready.)
>
> On Thu, Jun 19, 2014 at 5:36 AM, Kapil Thangavelu
> <kapil.thangavelu@xxxxxxxxxxxxx> wrote:
>> I'd like to Ben to reply this as that was part of his feedback.
>>
>> -k
>>
>>
>>
>> On Thu, Jun 19, 2014 at 7:14 AM, Alexander Prismakov
>> <alexander.prismakov@xxxxxxxxxxx> wrote:
>>>
>>> Hi Kapil, guys
>>>
>>> I fixed ‘credential issue’ in the charm and added new relation to CC.
>>> The charm still use CF CLI because I haven’t found answers on my
>>> questions. One more time: there is no Python wrapper for CC API calls.
>>> According to this post
>>> (http://blog.gopivotal.com/cloud-foundry-pivotal/products/working-with-the-cloud-controller-api-in-ruby-beyond-cfoundry)
>>> Ruby gem cfoundry also deprecated. So using CF CLI is only one option right
>>> now (let me know if you not agree). Second option is to develop Python
>>> wrapper from scratch.
>>> Could you please review this change?
>>>
>>> Thanks in advance,
>>>
>>> Alex P. | Altoros
>>
>>
>>
>> --
>> 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
>>