I have now added a validation to verify cartridge groups in applications,
commit revision: 9b0b3df2fd93024fe725b87a0c59fdfd672e3d50
On Thu, Feb 19, 2015 at 9:54 AM, Reka Thirunavukkarasu
wrote:
> That's great Imesh..Yah..We didn't implement the validation in the
> pre-alpha due to the time const
That's great Imesh..Yah..We didn't implement the validation in the
pre-alpha due to the time constraint..
Thanks,
Reka
On Wed, Feb 18, 2015 at 9:15 PM, Imesh Gunaratne wrote:
> Thanks Reka! Following are my current observations:
>
> - Currently there are no validations to verify whether a group
Thanks Reka! Following are my current observations:
- Currently there are no validations to verify whether a group added to an
application has defined all the cartridges. At the moment this is not
detected at any stage.
- There are no validations to verify aliases.
- IMO without validations, due t
Yah Imesh, Grouping functionality has been tested in the pre-alpha and most
of the features were working fine. We will need to fix some other edge
cases..
Thanks,
Reka
On Wed, Feb 18, 2015 at 7:15 PM, Imesh Gunaratne wrote:
> I think I found the root cause of the most of the grouping functional
s/review/reviewing/g
On Thu, Feb 19, 2015 at 7:45 AM, Imesh Gunaratne wrote:
> I think I found the root cause of the most of the grouping functionality
> issues after debugging it for nearly a day.
>
> The problem seems to be with the usage of aliases and ids. AFAIK grouping
> functionality work
I think I found the root cause of the most of the grouping functionality
issues after debugging it for nearly a day.
The problem seems to be with the usage of aliases and ids. AFAIK grouping
functionality worked without a problem in pre-alpha there after it broke
when we did some fixes related to
The above issue has occurred because of the time it takes to SM to receive
the application created event. Now I have fixed this my making a service
call from SM to AS to find cluster id of a given application, cartridge
alias rather than relying on the application events.
This fix is now available
I think I found the reason for not publishing Artifact Updated event. It
looks like the Mock IaaS is responding fast and SM is receiving the
Instance Started event before receiving the Application Created event. I'm
now fixing this.
Thanks
On Sun, Feb 15, 2015 at 2:56 PM, Imesh Gunaratne wrote:
Hi Devs,
I just did a quick test to verify grouping functionality with sample
applications and following is the current status:
ApplicationStatusNotescomplex-appNot Activatingcomplex-app-with-lbNot
Activatingdependent-scaling/sample-cartridgesActivates but found few
errorsArtifact
update event is
