Great work Dakshika!! +1 for the color scheme you proposed.
On Fri, Nov 28, 2014 at 10:52 AM, Dakshika Jayathilaka
wrote:
> Thank you all.. We need to finalize colors for status.
>
> StatusImeshDakhikaCreated-OrangeActiveGreenGreenInactiveOrangeGrey
> Terminating/TerminatedRedRed
>
> Thank you..
Great! Thanks for moving this to the CC service!
On Fri, Nov 28, 2014 at 5:39 PM, Reka Thirunavukkarasu
wrote:
> Hi Nirmal,
>
> The instances of cluster has been introduced as part of the Group Scaling
> in [1]. As we are still in the process of finalising the implementation
> details, will upda
IMO this is only used in metadata service at the moment, if so shall we
place this in metadata service component?
On Fri, Nov 28, 2014 at 5:11 PM, Udara Liyanage wrote:
>
>
> On Fri, Nov 28, 2014 at 5:01 PM, Sajith Kariyawasam
> wrote:
>
>> Should this handler need to be bundle with all the pro
Github user asfgit closed the pull request at:
https://github.com/apache/stratos/pull/127
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is ena
GitHub user swgkg opened a pull request:
https://github.com/apache/stratos/pull/127
Merge the new changes and added the new PR for PR#125
Please review and merge
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gayangunarathne/str
Github user swgkg closed the pull request at:
https://github.com/apache/stratos/pull/126
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enab
GitHub user swgkg opened a pull request:
https://github.com/apache/stratos/pull/126
Merge the new changes and added the new PR for PR#125
Please check and merge
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gayangunarathne/stra
Github user swgkg commented on the pull request:
https://github.com/apache/stratos/pull/125#issuecomment-64888397
Hi Imesh,
Added this PR after re-base master branch and merge new changes.This is
related with the #121
Thanks,
Gayan
---
If your project is set up
Github user imesh commented on the pull request:
https://github.com/apache/stratos/pull/125#issuecomment-64887768
Hi Gayan,
This pull request also seems to contain merge conflicts. Will you be able
to resolve them?
Thanks
Imesh
---
If your project is set up for
Hi Nirmal,
The instances of cluster has been introduced as part of the Group Scaling
in [1]. As we are still in the process of finalising the implementation
details, will update on high level implementation details as soon as it is
done..
[1]. [Discuss] Group Scaling & Dependent Scaling Behaviour
Hi Reka,
What's the meaning of the instance id here?
On Fri, Nov 28, 2014 at 4:49 PM, Reka Thirunavukkarasu
wrote:
> Please find the API as below as it would be easy to have the serviceName.
> So that traverse through the Topology would be easy.
>
> /**
> * Update the topology with current
On Fri, Nov 28, 2014 at 5:01 PM, Sajith Kariyawasam wrote:
> Should this handler need to be bundle with all the products? In a
> distributed setup, to which product(s) (SM / CC / AS ..) this should goes
> to ?
>
SM only . May be some part is relevant for metadata service which I am not
sure for
Github user swgkg commented on the pull request:
https://github.com/apache/stratos/pull/121#issuecomment-64885269
Hi Imesh,
I merge those changes with new changes and make a new PR #125
Thanks,
Gayan
---
If your project is set up for it, you can reply to this em
GitHub user swgkg opened a pull request:
https://github.com/apache/stratos/pull/125
Merge the master with the changes of PR #121
Please review and merge
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gayangunarathne/stratos maste
Hi,
IMO is this should be go with separate component. It helps easy when
extending it further.
Thanks !
On Fri, Nov 28, 2014 at 5:01 PM, Sajith Kariyawasam wrote:
> Should this handler need to be bundle with all the products? In a
> distributed setup, to which product(s) (SM / CC / AS ..) this
Hi Udara,
On Fri, Nov 28, 2014 at 4:47 PM, Udara Liyanage wrote:
> Hi,
>
> As I mentioned in a previous mail, I wrote a custom token handler in order
> to generate a JWT token. My concern is how to add this to product. Either
> need to write a separate component or add to an existing one.
> Wri
Should this handler need to be bundle with all the products? In a
distributed setup, to which product(s) (SM / CC / AS ..) this should goes
to ?
On Fri, Nov 28, 2014 at 4:47 PM, Udara Liyanage wrote:
> Hi,
>
> As I mentioned in a previous mail, I wrote a custom token handler in order
> to genera
Please find the API as below as it would be easy to have the serviceName.
So that traverse through the Topology would be easy.
/**
* Update the topology with current cluster status.
* @param serviceName id of service which the cluster belongs to.
* @param clusterId id of the subject
Hi,
As I mentioned in a previous mail, I wrote a custom token handler in order
to generate a JWT token. My concern is how to add this to product. Either
need to write a separate component or add to an existing one.
Writing a separate component to just a single class won't worth from one
aspect gi
Hi Nirmal,
The following is the API that i thought of introducing in order to update
the status of the cluster in the Topology from Autoscaler.
/**
* Update the topology with current cluster instance status.
* @param clusterId id of the subjected cluster.
* @param instanceId id
Hi All,
I have updated the necessary CEP 3.1.0 features to the Stratos. Once I
start testing I found that some of osgi services get duplicated because of
the newly updated features. I'll sort out this issue and commit the changes
after the proper testing.
Thanks !
On Thu, Nov 27, 2014 at 12:54
Hi,
I tried oAuth approach as mentioned above.
I face few blockers since IS released version does not support fully JWT
creation. This is fixed in coming release.
Then as an alternative I tried adding a new grant type to achieve the task.
Unfortunately it is also not fully supported.
As a worka
[
https://issues.apache.org/jira/browse/STRATOS-979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mariangela Hills resolved STRATOS-979.
--
Resolution: Fixed
Fix Version/s: 4.1.0 Alpha
Fixed in the REST API refactoring p
[
https://issues.apache.org/jira/browse/STRATOS-990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mariangela Hills resolved STRATOS-990.
--
Resolution: Fixed
Fixed in the REST API refactoring process. Commit IDs [1].
[1] (commi
Great stuff!
On Fri, Nov 28, 2014 at 9:36 AM, Dakshika Jayathilaka
wrote:
> Hi Devs,
>
> I'm planning to add topology view tree to application detail view page. We
> had suggestion thread[1] and i have came up with solution based on d3js
> which include automatic node positioning with Reingold–T
According to the code this returns a object of ApplicationSubscription for
the given application_id.
This is obtained from the DataInsertionAndRetrievalManager via the
CartridgeSubscriptionManager.
On Fri, Nov 28, 2014 at 2:15 PM, Mariangela Hills
wrote:
> Hi,
>
> Looks like the name of the prop
Hi Dakshika,
Brilliant stuff! This is super cool.
Do we have plans to put hovering pop up boxes with detailed information
when you click on an icon? Sorry, if this was already discussed.
Thanks.
On Fri, Nov 28, 2014 at 2:03 PM, Manula Chathurika Thantriwatte <
manu...@wso2.com> wrote:
> Hi,
>
Hi All,
I've migrated the vagrant setup to Kubernetes v0.5.3 (v0.5.2 and v0.5.3 has
same binaries) [1]. Please find the latest setup here at [2]. Further, I
have tested the Kubernetes client by running its Live tests and unit tests
and fixed 1 issue and committed.
[1] https://github.com/nirmal070
Github user imesh commented on the pull request:
https://github.com/apache/stratos/pull/121#issuecomment-64868698
Hi Gayan,
Thanks for fixing the above issue. I just tried to merge this but seems
like there are conflicts. Can you please update the pull request branch with
mas
Hi,
Looks like the name of the proposed API operation has changed
to getSubscriptionsOfApplication. This needs to be updated in [1].
[1]
https://docs.google.com/a/wso2.com/spreadsheets/d/1VP9-0xY2Oj1H1sv5yf5goIT6TakpwrCt5Z8QW1oFVOc/edit#gid=0
Regards,
Mariangela
*--*
Mariangela Hills
Senior
Created the jira https://issues.apache.org/jira/browse/STRATOS-1015
On Fri, Nov 28, 2014 at 1:40 PM, Reka Thirunavukkarasu
wrote:
> Hi
>
> On Fri, Nov 28, 2014 at 9:52 AM, Imesh Gunaratne wrote:
>
>> Hi Reka,
>>
>> Thanks for the clarification. Will there be any issues if we change this
>> to a
Do we have this subscription concept any more? If not, we need to remove
that. This document was created before we change this concept and moved to
application model.
On Fri, Nov 28, 2014 at 2:08 PM, Isuru Haththotuwa
wrote:
> Hi,
>
> What exactly does /subscriptions/{application_id} return?
>
>
Hi Reka,
Are you planning to introduce an API in CC to update cluster status? Can
you please share the API/s skeleton ?
On Thu, Nov 27, 2014 at 11:15 PM, Reka Thirunavukkarasu
wrote:
> Hi Imesh,
>
> This is there to update the cluster status from autoscaler to Topology in
> CC . If we are getti
On Fri, Nov 28, 2014 at 9:52 AM, Imesh Gunaratne wrote:
> Hi Reka,
>
> Thanks for the clarification. Will there be any issues if we change this
> to a service call since AS is already making service calls to CC?
>
+1
>
> Thanks
>
> On Thu, Nov 27, 2014 at 11:15 PM, Reka Thirunavukkarasu
> wrote
Hi,
What exactly does /subscriptions/{application_id} return?
On Fri, Nov 28, 2014 at 1:57 PM, Udara Liyanage wrote:
> Hi,
>
> /subscriptions/cartridges is not valid anymore since subscribing to
> cartridges is not valid.
> Please update the Excell when a change is doing.
>
> On Fri, Nov 28, 20
Reka Thirunavukkarasu created STRATOS-1015:
--
Summary: Replace cluster-status topic with Service call
Key: STRATOS-1015
URL: https://issues.apache.org/jira/browse/STRATOS-1015
Project: Stratos
Hi,
Great work Dakshika.
On Fri, Nov 28, 2014 at 1:09 PM, Dakshika Jayathilaka
wrote:
> Yes gayan.. d3js include tidy algo inbuit. it can handle any number of
> nodes. Normally binary tree algo can't handle more than two.
>
> *Dakshika Jayathilaka*
> Software Engineer
> WSO2, Inc.
> lean.enterp
Hi,
/subscriptions/cartridges is not valid anymore since subscribing to
cartridges is not valid.
Please update the Excell when a change is doing.
On Fri, Nov 28, 2014 at 1:51 PM, Mariangela Hills
wrote:
> Hi,
>
> In [1] it states that /cartridge/list/subscribed has been changed
> to /subscripti
Hi,
In [1] it states that /cartridge/list/subscribed has been changed
to /subscriptions/cartridges. I pulled the new changes, but this change is
not visible. According to commit [2] it looks like
/cartridge/list/subscribed has been changed to
/subscriptions/{application_id}. If this is correct thi
Hi,
On Fri, Nov 28, 2014 at 1:00 PM, Akila Ravihansa Perera
wrote:
> Hi,
>
> According to this design Autoscaler (AS)/Stratos Manager (SM) will talk to
>>> Cloud Controller (CC) via the Cloud Controller Service endpoint exposed via
>>> the load balancer.
>>>
>>> *Data Replication*
>>> When a req
Hi
On Fri, Nov 28, 2014 at 9:52 AM, Imesh Gunaratne wrote:
> Hi Reka,
>
> Thanks for the clarification. Will there be any issues if we change this
> to a service call since AS is already making service calls to CC?
>
+1. We can use service call to do this. Will create a jira and track this
one.
41 matches
Mail list logo
