You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by Lahiru Sandaruwan <la...@wso2.com> on 2013/10/29 10:04:04 UTC
Shall we get rid of repo information service of SC(Stratos Manager)
Hi,
$subject?
This is not suitable for our new architecture IMO.
We can pass those information through user data to the instance.
Ideally instance only need to know the Message broker IP as per new
architecture.
Thanks.
--
--
Lahiru Sandaruwan
Software Engineer,
Platform Technologies,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
email: lahirus@wso2.com cell: (+94) 773 325 954
blog: http://lahiruwrites.blogspot.com/
twitter: http://twitter.com/lahirus
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
Re: Shall we get rid of repo information service of SC(Stratos Manager)
Posted by Sajith Kariyawasam <sa...@wso2.com>.
On Tue, Oct 29, 2013 at 7:27 PM, Isuru Perera <is...@wso2.com> wrote:
> AFAIK, that service was there to get the user credentials for Git
> repository. So, we would still need it as there should be a way to get Git
> credentials? Passing via a payload is not an option since we should allow
> user to change the password.
>
Can't we read the credentials from DB and inject to payload and pass.. ?
>
>
> On Tue, Oct 29, 2013 at 2:04 AM, Lahiru Sandaruwan <la...@wso2.com>wrote:
>
>> Hi,
>>
>> $subject?
>>
>> This is not suitable for our new architecture IMO.
>> We can pass those information through user data to the instance.
>> Ideally instance only need to know the Message broker IP as per new
>> architecture.
>>
>> Thanks.
>>
>> --
>> --
>> Lahiru Sandaruwan
>> Software Engineer,
>> Platform Technologies,
>> WSO2 Inc., http://wso2.com
>> lean.enterprise.middleware
>>
>> email: lahirus@wso2.com cell: (+94) 773 325 954
>> blog: http://lahiruwrites.blogspot.com/
>> twitter: http://twitter.com/lahirus
>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>
>>
>
>
> --
> Isuru Perera
> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> about.me/chrishantha
>
--
*Sajith Kariyawasam*
*Senior Software Engineer; WSO2, Inc.*
*AMIE (SL)*
*Blog: http://sajithblogs.blogspot.com/*
*Mobile: +94772269575*
Re: Shall we get rid of repo information service of SC(Stratos Manager)
Posted by Lahiru Sandaruwan <la...@wso2.com>.
Hi all,
FYI. This is implemented with the solution of [1].
Thanks.
[1] https://issues.apache.org/jira/browse/STRATOS-103
On Wed, Oct 30, 2013 at 10:37 AM, Nirmal Fernando <ni...@gmail.com>wrote:
> Authentication is already there for the topics. You append them in the
> connection url as query params.
>
>
> On Wed, Oct 30, 2013 at 9:31 AM, Lahiru Sandaruwan <la...@wso2.com>wrote:
>
>>
>>
>>
>> On Wed, Oct 30, 2013 at 8:51 AM, Lakmal Warusawithana <la...@wso2.com>wrote:
>>
>>> +1, And we need to have some mechanism to secure all these topics. I
>>> mean some topics, say topology topic, only can accept that publish from CC.
>>> Also we need to way to authenticate subscribers as well. For example if
>>> any one can subscribe to topology topic may cause very huge risk to the
>>> system.
>>>
>>
>> Yeah, we need all topics to be secured.
>>
>>>
>>>
>>> On Tue, Oct 29, 2013 at 8:32 PM, Lahiru Sandaruwan <la...@wso2.com>wrote:
>>>
>>>>
>>>>
>>>>
>>>> On Tue, Oct 29, 2013 at 8:31 PM, Lahiru Sandaruwan <la...@wso2.com>wrote:
>>>>
>>>>> We can use dep sync message if it's secure enough!
>>>>>
>>>>
>>>> I mean the message broker...
>>>>
>>>>
>>>>>
>>>>>
>>>>> On Tue, Oct 29, 2013 at 7:27 PM, Isuru Perera <is...@wso2.com> wrote:
>>>>>
>>>>>> AFAIK, that service was there to get the user credentials for Git
>>>>>> repository. So, we would still need it as there should be a way to get Git
>>>>>> credentials? Passing via a payload is not an option since we should allow
>>>>>> user to change the password.
>>>>>>
>>>>>>
>>>>>> On Tue, Oct 29, 2013 at 2:04 AM, Lahiru Sandaruwan <la...@wso2.com>wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> $subject?
>>>>>>>
>>>>>>> This is not suitable for our new architecture IMO.
>>>>>>> We can pass those information through user data to the instance.
>>>>>>> Ideally instance only need to know the Message broker IP as per new
>>>>>>> architecture.
>>>>>>>
>>>>>>> Thanks.
>>>>>>>
>>>>>>> --
>>>>>>> --
>>>>>>> Lahiru Sandaruwan
>>>>>>> Software Engineer,
>>>>>>> Platform Technologies,
>>>>>>> WSO2 Inc., http://wso2.com
>>>>>>> lean.enterprise.middleware
>>>>>>>
>>>>>>> email: lahirus@wso2.com cell: (+94) 773 325 954
>>>>>>> blog: http://lahiruwrites.blogspot.com/
>>>>>>> twitter: http://twitter.com/lahirus
>>>>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Isuru Perera
>>>>>> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
>>>>>> Lean . Enterprise . Middleware
>>>>>>
>>>>>> about.me/chrishantha
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> --
>>>>> Lahiru Sandaruwan
>>>>> Software Engineer,
>>>>> Platform Technologies,
>>>>> WSO2 Inc., http://wso2.com
>>>>> lean.enterprise.middleware
>>>>>
>>>>> email: lahirus@wso2.com cell: (+94) 773 325 954
>>>>> blog: http://lahiruwrites.blogspot.com/
>>>>> twitter: http://twitter.com/lahirus
>>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> --
>>>> Lahiru Sandaruwan
>>>> Software Engineer,
>>>> Platform Technologies,
>>>> WSO2 Inc., http://wso2.com
>>>> lean.enterprise.middleware
>>>>
>>>> email: lahirus@wso2.com cell: (+94) 773 325 954
>>>> blog: http://lahiruwrites.blogspot.com/
>>>> twitter: http://twitter.com/lahirus
>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>
>>>>
>>>
>>>
>>> --
>>> Lakmal Warusawithana
>>> Software Architect; WSO2 Inc.
>>> Mobile : +94714289692
>>> Blog : http://lakmalsview.blogspot.com/
>>>
>>>
>>
>>
>> --
>> --
>> Lahiru Sandaruwan
>> Software Engineer,
>> Platform Technologies,
>> WSO2 Inc., http://wso2.com
>> lean.enterprise.middleware
>>
>> email: lahirus@wso2.com cell: (+94) 773 325 954
>> blog: http://lahiruwrites.blogspot.com/
>> twitter: http://twitter.com/lahirus
>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>
>>
>
>
> --
> Best Regards,
> Nirmal
>
> Nirmal Fernando.
> PPMC Member & Committer of Apache Stratos,
> Senior Software Engineer, WSO2 Inc.
>
> Blog: http://nirmalfdo.blogspot.com/
>
--
--
Lahiru Sandaruwan
Software Engineer,
Platform Technologies,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
email: lahirus@wso2.com cell: (+94) 773 325 954
blog: http://lahiruwrites.blogspot.com/
twitter: http://twitter.com/lahirus
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
Re: Shall we get rid of repo information service of SC(Stratos Manager)
Posted by Nirmal Fernando <ni...@gmail.com>.
Authentication is already there for the topics. You append them in the
connection url as query params.
On Wed, Oct 30, 2013 at 9:31 AM, Lahiru Sandaruwan <la...@wso2.com> wrote:
>
>
>
> On Wed, Oct 30, 2013 at 8:51 AM, Lakmal Warusawithana <la...@wso2.com>wrote:
>
>> +1, And we need to have some mechanism to secure all these topics. I mean
>> some topics, say topology topic, only can accept that publish from CC.
>> Also we need to way to authenticate subscribers as well. For example if
>> any one can subscribe to topology topic may cause very huge risk to the
>> system.
>>
>
> Yeah, we need all topics to be secured.
>
>>
>>
>> On Tue, Oct 29, 2013 at 8:32 PM, Lahiru Sandaruwan <la...@wso2.com>wrote:
>>
>>>
>>>
>>>
>>> On Tue, Oct 29, 2013 at 8:31 PM, Lahiru Sandaruwan <la...@wso2.com>wrote:
>>>
>>>> We can use dep sync message if it's secure enough!
>>>>
>>>
>>> I mean the message broker...
>>>
>>>
>>>>
>>>>
>>>> On Tue, Oct 29, 2013 at 7:27 PM, Isuru Perera <is...@wso2.com> wrote:
>>>>
>>>>> AFAIK, that service was there to get the user credentials for Git
>>>>> repository. So, we would still need it as there should be a way to get Git
>>>>> credentials? Passing via a payload is not an option since we should allow
>>>>> user to change the password.
>>>>>
>>>>>
>>>>> On Tue, Oct 29, 2013 at 2:04 AM, Lahiru Sandaruwan <la...@wso2.com>wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> $subject?
>>>>>>
>>>>>> This is not suitable for our new architecture IMO.
>>>>>> We can pass those information through user data to the instance.
>>>>>> Ideally instance only need to know the Message broker IP as per new
>>>>>> architecture.
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> --
>>>>>> --
>>>>>> Lahiru Sandaruwan
>>>>>> Software Engineer,
>>>>>> Platform Technologies,
>>>>>> WSO2 Inc., http://wso2.com
>>>>>> lean.enterprise.middleware
>>>>>>
>>>>>> email: lahirus@wso2.com cell: (+94) 773 325 954
>>>>>> blog: http://lahiruwrites.blogspot.com/
>>>>>> twitter: http://twitter.com/lahirus
>>>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Isuru Perera
>>>>> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
>>>>> Lean . Enterprise . Middleware
>>>>>
>>>>> about.me/chrishantha
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> --
>>>> Lahiru Sandaruwan
>>>> Software Engineer,
>>>> Platform Technologies,
>>>> WSO2 Inc., http://wso2.com
>>>> lean.enterprise.middleware
>>>>
>>>> email: lahirus@wso2.com cell: (+94) 773 325 954
>>>> blog: http://lahiruwrites.blogspot.com/
>>>> twitter: http://twitter.com/lahirus
>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>
>>>>
>>>
>>>
>>> --
>>> --
>>> Lahiru Sandaruwan
>>> Software Engineer,
>>> Platform Technologies,
>>> WSO2 Inc., http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> email: lahirus@wso2.com cell: (+94) 773 325 954
>>> blog: http://lahiruwrites.blogspot.com/
>>> twitter: http://twitter.com/lahirus
>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>
>>>
>>
>>
>> --
>> Lakmal Warusawithana
>> Software Architect; WSO2 Inc.
>> Mobile : +94714289692
>> Blog : http://lakmalsview.blogspot.com/
>>
>>
>
>
> --
> --
> Lahiru Sandaruwan
> Software Engineer,
> Platform Technologies,
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> email: lahirus@wso2.com cell: (+94) 773 325 954
> blog: http://lahiruwrites.blogspot.com/
> twitter: http://twitter.com/lahirus
> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>
>
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.
Blog: http://nirmalfdo.blogspot.com/
Re: Shall we get rid of repo information service of SC(Stratos Manager)
Posted by Lahiru Sandaruwan <la...@wso2.com>.
On Wed, Oct 30, 2013 at 8:51 AM, Lakmal Warusawithana <la...@wso2.com>wrote:
> +1, And we need to have some mechanism to secure all these topics. I mean
> some topics, say topology topic, only can accept that publish from CC.
> Also we need to way to authenticate subscribers as well. For example if
> any one can subscribe to topology topic may cause very huge risk to the
> system.
>
Yeah, we need all topics to be secured.
>
>
> On Tue, Oct 29, 2013 at 8:32 PM, Lahiru Sandaruwan <la...@wso2.com>wrote:
>
>>
>>
>>
>> On Tue, Oct 29, 2013 at 8:31 PM, Lahiru Sandaruwan <la...@wso2.com>wrote:
>>
>>> We can use dep sync message if it's secure enough!
>>>
>>
>> I mean the message broker...
>>
>>
>>>
>>>
>>> On Tue, Oct 29, 2013 at 7:27 PM, Isuru Perera <is...@wso2.com> wrote:
>>>
>>>> AFAIK, that service was there to get the user credentials for Git
>>>> repository. So, we would still need it as there should be a way to get Git
>>>> credentials? Passing via a payload is not an option since we should allow
>>>> user to change the password.
>>>>
>>>>
>>>> On Tue, Oct 29, 2013 at 2:04 AM, Lahiru Sandaruwan <la...@wso2.com>wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> $subject?
>>>>>
>>>>> This is not suitable for our new architecture IMO.
>>>>> We can pass those information through user data to the instance.
>>>>> Ideally instance only need to know the Message broker IP as per new
>>>>> architecture.
>>>>>
>>>>> Thanks.
>>>>>
>>>>> --
>>>>> --
>>>>> Lahiru Sandaruwan
>>>>> Software Engineer,
>>>>> Platform Technologies,
>>>>> WSO2 Inc., http://wso2.com
>>>>> lean.enterprise.middleware
>>>>>
>>>>> email: lahirus@wso2.com cell: (+94) 773 325 954
>>>>> blog: http://lahiruwrites.blogspot.com/
>>>>> twitter: http://twitter.com/lahirus
>>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Isuru Perera
>>>> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
>>>> Lean . Enterprise . Middleware
>>>>
>>>> about.me/chrishantha
>>>>
>>>
>>>
>>>
>>> --
>>> --
>>> Lahiru Sandaruwan
>>> Software Engineer,
>>> Platform Technologies,
>>> WSO2 Inc., http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> email: lahirus@wso2.com cell: (+94) 773 325 954
>>> blog: http://lahiruwrites.blogspot.com/
>>> twitter: http://twitter.com/lahirus
>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>
>>>
>>
>>
>> --
>> --
>> Lahiru Sandaruwan
>> Software Engineer,
>> Platform Technologies,
>> WSO2 Inc., http://wso2.com
>> lean.enterprise.middleware
>>
>> email: lahirus@wso2.com cell: (+94) 773 325 954
>> blog: http://lahiruwrites.blogspot.com/
>> twitter: http://twitter.com/lahirus
>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>
>>
>
>
> --
> Lakmal Warusawithana
> Software Architect; WSO2 Inc.
> Mobile : +94714289692
> Blog : http://lakmalsview.blogspot.com/
>
>
--
--
Lahiru Sandaruwan
Software Engineer,
Platform Technologies,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
email: lahirus@wso2.com cell: (+94) 773 325 954
blog: http://lahiruwrites.blogspot.com/
twitter: http://twitter.com/lahirus
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
Re: Shall we get rid of repo information service of SC(Stratos Manager)
Posted by Lakmal Warusawithana <la...@wso2.com>.
+1, And we need to have some mechanism to secure all these topics. I mean
some topics, say topology topic, only can accept that publish from CC.
Also we need to way to authenticate subscribers as well. For example if
any one can subscribe to topology topic may cause very huge risk to the
system.
On Tue, Oct 29, 2013 at 8:32 PM, Lahiru Sandaruwan <la...@wso2.com> wrote:
>
>
>
> On Tue, Oct 29, 2013 at 8:31 PM, Lahiru Sandaruwan <la...@wso2.com>wrote:
>
>> We can use dep sync message if it's secure enough!
>>
>
> I mean the message broker...
>
>
>>
>>
>> On Tue, Oct 29, 2013 at 7:27 PM, Isuru Perera <is...@wso2.com> wrote:
>>
>>> AFAIK, that service was there to get the user credentials for Git
>>> repository. So, we would still need it as there should be a way to get Git
>>> credentials? Passing via a payload is not an option since we should allow
>>> user to change the password.
>>>
>>>
>>> On Tue, Oct 29, 2013 at 2:04 AM, Lahiru Sandaruwan <la...@wso2.com>wrote:
>>>
>>>> Hi,
>>>>
>>>> $subject?
>>>>
>>>> This is not suitable for our new architecture IMO.
>>>> We can pass those information through user data to the instance.
>>>> Ideally instance only need to know the Message broker IP as per new
>>>> architecture.
>>>>
>>>> Thanks.
>>>>
>>>> --
>>>> --
>>>> Lahiru Sandaruwan
>>>> Software Engineer,
>>>> Platform Technologies,
>>>> WSO2 Inc., http://wso2.com
>>>> lean.enterprise.middleware
>>>>
>>>> email: lahirus@wso2.com cell: (+94) 773 325 954
>>>> blog: http://lahiruwrites.blogspot.com/
>>>> twitter: http://twitter.com/lahirus
>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>
>>>>
>>>
>>>
>>> --
>>> Isuru Perera
>>> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
>>> Lean . Enterprise . Middleware
>>>
>>> about.me/chrishantha
>>>
>>
>>
>>
>> --
>> --
>> Lahiru Sandaruwan
>> Software Engineer,
>> Platform Technologies,
>> WSO2 Inc., http://wso2.com
>> lean.enterprise.middleware
>>
>> email: lahirus@wso2.com cell: (+94) 773 325 954
>> blog: http://lahiruwrites.blogspot.com/
>> twitter: http://twitter.com/lahirus
>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>
>>
>
>
> --
> --
> Lahiru Sandaruwan
> Software Engineer,
> Platform Technologies,
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> email: lahirus@wso2.com cell: (+94) 773 325 954
> blog: http://lahiruwrites.blogspot.com/
> twitter: http://twitter.com/lahirus
> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>
>
--
Lakmal Warusawithana
Software Architect; WSO2 Inc.
Mobile : +94714289692
Blog : http://lakmalsview.blogspot.com/
Re: Shall we get rid of repo information service of SC(Stratos Manager)
Posted by Lahiru Sandaruwan <la...@wso2.com>.
On Tue, Oct 29, 2013 at 8:31 PM, Lahiru Sandaruwan <la...@wso2.com> wrote:
> We can use dep sync message if it's secure enough!
>
I mean the message broker...
>
>
> On Tue, Oct 29, 2013 at 7:27 PM, Isuru Perera <is...@wso2.com> wrote:
>
>> AFAIK, that service was there to get the user credentials for Git
>> repository. So, we would still need it as there should be a way to get Git
>> credentials? Passing via a payload is not an option since we should allow
>> user to change the password.
>>
>>
>> On Tue, Oct 29, 2013 at 2:04 AM, Lahiru Sandaruwan <la...@wso2.com>wrote:
>>
>>> Hi,
>>>
>>> $subject?
>>>
>>> This is not suitable for our new architecture IMO.
>>> We can pass those information through user data to the instance.
>>> Ideally instance only need to know the Message broker IP as per new
>>> architecture.
>>>
>>> Thanks.
>>>
>>> --
>>> --
>>> Lahiru Sandaruwan
>>> Software Engineer,
>>> Platform Technologies,
>>> WSO2 Inc., http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> email: lahirus@wso2.com cell: (+94) 773 325 954
>>> blog: http://lahiruwrites.blogspot.com/
>>> twitter: http://twitter.com/lahirus
>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>
>>>
>>
>>
>> --
>> Isuru Perera
>> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
>> Lean . Enterprise . Middleware
>>
>> about.me/chrishantha
>>
>
>
>
> --
> --
> Lahiru Sandaruwan
> Software Engineer,
> Platform Technologies,
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> email: lahirus@wso2.com cell: (+94) 773 325 954
> blog: http://lahiruwrites.blogspot.com/
> twitter: http://twitter.com/lahirus
> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>
>
--
--
Lahiru Sandaruwan
Software Engineer,
Platform Technologies,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
email: lahirus@wso2.com cell: (+94) 773 325 954
blog: http://lahiruwrites.blogspot.com/
twitter: http://twitter.com/lahirus
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
Re: Shall we get rid of repo information service of SC(Stratos Manager)
Posted by Lahiru Sandaruwan <la...@wso2.com>.
We can use dep sync message if it's secure enough!
On Tue, Oct 29, 2013 at 7:27 PM, Isuru Perera <is...@wso2.com> wrote:
> AFAIK, that service was there to get the user credentials for Git
> repository. So, we would still need it as there should be a way to get Git
> credentials? Passing via a payload is not an option since we should allow
> user to change the password.
>
>
> On Tue, Oct 29, 2013 at 2:04 AM, Lahiru Sandaruwan <la...@wso2.com>wrote:
>
>> Hi,
>>
>> $subject?
>>
>> This is not suitable for our new architecture IMO.
>> We can pass those information through user data to the instance.
>> Ideally instance only need to know the Message broker IP as per new
>> architecture.
>>
>> Thanks.
>>
>> --
>> --
>> Lahiru Sandaruwan
>> Software Engineer,
>> Platform Technologies,
>> WSO2 Inc., http://wso2.com
>> lean.enterprise.middleware
>>
>> email: lahirus@wso2.com cell: (+94) 773 325 954
>> blog: http://lahiruwrites.blogspot.com/
>> twitter: http://twitter.com/lahirus
>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>
>>
>
>
> --
> Isuru Perera
> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> about.me/chrishantha
>
--
--
Lahiru Sandaruwan
Software Engineer,
Platform Technologies,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
email: lahirus@wso2.com cell: (+94) 773 325 954
blog: http://lahiruwrites.blogspot.com/
twitter: http://twitter.com/lahirus
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
Re: Shall we get rid of repo information service of SC(Stratos Manager)
Posted by Isuru Perera <is...@wso2.com>.
AFAIK, that service was there to get the user credentials for Git
repository. So, we would still need it as there should be a way to get Git
credentials? Passing via a payload is not an option since we should allow
user to change the password.
On Tue, Oct 29, 2013 at 2:04 AM, Lahiru Sandaruwan <la...@wso2.com> wrote:
> Hi,
>
> $subject?
>
> This is not suitable for our new architecture IMO.
> We can pass those information through user data to the instance.
> Ideally instance only need to know the Message broker IP as per new
> architecture.
>
> Thanks.
>
> --
> --
> Lahiru Sandaruwan
> Software Engineer,
> Platform Technologies,
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> email: lahirus@wso2.com cell: (+94) 773 325 954
> blog: http://lahiruwrites.blogspot.com/
> twitter: http://twitter.com/lahirus
> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>
>
--
Isuru Perera
Senior Software Engineer | WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware
about.me/chrishantha
Re: Shall we get rid of repo information service of SC(Stratos Manager)
Posted by Lakmal Warusawithana <la...@wso2.com>.
the only concern is how you store credential. Are you store in plan text
inside the instance? The reason we put in SM is to store in encrypted way.
Also we need to consider, if user change the credential, how we going to
manage, if we distributed in all instances.
On Tue, Oct 29, 2013 at 2:34 PM, Lahiru Sandaruwan <la...@wso2.com> wrote:
> Hi,
>
> $subject?
>
> This is not suitable for our new architecture IMO.
> We can pass those information through user data to the instance.
> Ideally instance only need to know the Message broker IP as per new
> architecture.
>
> Thanks.
>
> --
> --
> Lahiru Sandaruwan
> Software Engineer,
> Platform Technologies,
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> email: lahirus@wso2.com cell: (+94) 773 325 954
> blog: http://lahiruwrites.blogspot.com/
> twitter: http://twitter.com/lahirus
> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>
>
--
Lakmal Warusawithana
Software Architect; WSO2 Inc.
Mobile : +94714289692
Blog : http://lakmalsview.blogspot.com/
Re: Shall we get rid of repo information service of SC(Stratos Manager)
Posted by Imesh Gunaratne <im...@apache.org>.
+1
On Tue, Oct 29, 2013 at 4:51 PM, Reka Thirunavukkarasu <re...@wso2.com>wrote:
> +1. We can send them in the payload. Since the payload is handled by
> jcloud, there won't face any security issue as i guess. Let's clean up the
> payload parameters that we are sending to instances accordingly.
>
> Thanks,
> Reka
>
>
> On Tue, Oct 29, 2013 at 2:34 PM, Lahiru Sandaruwan <la...@wso2.com>wrote:
>
>> Hi,
>>
>> $subject?
>>
>> This is not suitable for our new architecture IMO.
>> We can pass those information through user data to the instance.
>> Ideally instance only need to know the Message broker IP as per new
>> architecture.
>>
>> Thanks.
>>
>> --
>> --
>> Lahiru Sandaruwan
>> Software Engineer,
>> Platform Technologies,
>> WSO2 Inc., http://wso2.com
>> lean.enterprise.middleware
>>
>> email: lahirus@wso2.com cell: (+94) 773 325 954
>> blog: http://lahiruwrites.blogspot.com/
>> twitter: http://twitter.com/lahirus
>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>
>>
>
>
> --
> Reka Thirunavukkarasu
> Software Engineer,
> WSO2, Inc.:http://wso2.com,
> Mobile: +94776442007
>
>
>
Re: Shall we get rid of repo information service of SC(Stratos Manager)
Posted by Reka Thirunavukkarasu <re...@wso2.com>.
+1. We can send them in the payload. Since the payload is handled by
jcloud, there won't face any security issue as i guess. Let's clean up the
payload parameters that we are sending to instances accordingly.
Thanks,
Reka
On Tue, Oct 29, 2013 at 2:34 PM, Lahiru Sandaruwan <la...@wso2.com> wrote:
> Hi,
>
> $subject?
>
> This is not suitable for our new architecture IMO.
> We can pass those information through user data to the instance.
> Ideally instance only need to know the Message broker IP as per new
> architecture.
>
> Thanks.
>
> --
> --
> Lahiru Sandaruwan
> Software Engineer,
> Platform Technologies,
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> email: lahirus@wso2.com cell: (+94) 773 325 954
> blog: http://lahiruwrites.blogspot.com/
> twitter: http://twitter.com/lahirus
> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>
>
--
Reka Thirunavukkarasu
Software Engineer,
WSO2, Inc.:http://wso2.com,
Mobile: +94776442007