On Sat, Jan 3, 2015 at 7:59 AM, Imesh Gunaratne wrote:
> One of the problems we have here is that, the previous logic has used the
> Cluster ID to fetch the connected subscriptions on Instance Started event.
> However now it is not possible to do the same with Cluster ID, instead
> Instance Start
One of the problems we have here is that, the previous logic has used the
Cluster ID to fetch the connected subscriptions on Instance Started event.
However now it is not possible to do the same with Cluster ID, instead
Instance Started event need to include the Application ID.
On Sat, Jan 3, 2015
Thanks Lakmal! Now SM does not have subscription/repo information, we might
need to get them from Autoscaler. Yes I think we still have not implemented
any functionality for MT cartridges. Will introduce this with the signup
process.
Thanks
On Sat, Jan 3, 2015 at 7:45 AM, Lakmal Warusawithana
wr
But this is required by the multi tenants scenario also. In single tenant
wait to get git repo info (SM will send after receiving instance start,
IIRC) and do the clone at first time. In the MT, when we signup for the MT,
we should send these info. IMO, we should fixed the flow, but SM should
handl
As it looks like we have taken this long path to send repository
information to the instance because we needed to send the encrypted
password and secret separately.
I think we need to preserve this and fix Instance Status listener logic.
On Fri, Jan 2, 2015 at 9:52 PM, Imesh Gunaratne wrote:
>
Hi Devs,
This is regarding $subject. In the latest codebase git clone does not work
in agent.
I did some investigations on this logic and found that it has worked
earlier when cartridge subscriptions were managed by Stratos Manager (SM).
When an Instance Started event is received by SM, it query
