rted
to secur...@wso2.com, not as GitHub issues, in order to reach the proper
audience. We strongly advise following the WSO2 Security Vulnerability
Reporting Guidelines
<https://docs.wso2.com/display/Security/WSO2+Security+Vulnerability+Reporting+Guidelines>
when
reporting security issues.
*-- Th
e. We strongly advise following the WSO2 Security Vulnerability
Reporting Guidelines
<https://docs.wso2.com/display/Security/WSO2+Security+Vulnerability+Reporting+Guidelines>
when
reporting security issues.
*-- The WSO2 API Manager Team --*
--
*Pubudu Gunatilaka* | Technical Lead | WSO2 Inc.
(
y+Vulnerability+Reporting+Guidelines>
when
reporting security issues.
*-- The WSO2 API Manager Team --*
--
*Pubudu Gunatilaka* | Technical Lead | WSO2 Inc.
(m) +94774078049 | (w) +94112145345 | (e) pubu...@wso2.com
<http://wso2.com/signature>
___
eporting Guidelines
<https://docs.wso2.com/display/Security/WSO2+Security+Vulnerability+Reporting+Guidelines>
when
reporting security issues.
*-- The WSO2 API Manager Team --*
--
*Pubudu Gunatilaka* | Technical Lead | WSO2 Inc.
(m) +9477407804
ility+Reporting+Guidelines>
when
reporting security issues.
*-- The WSO2 API Manager Team --*
--
*Pubudu Gunatilaka* | Technical Lead | WSO2 Inc.
(m) +94774078049 | (w) +94112145345 | (e) pubu...@wso2.com
<http://wso2.com/signature>
___
Arc
"serviceURL":"http://10.0.0.11:6379;,
"Properties":[
"Namespace:default",
"ServiceType:ClusterIP"
]
}
]
}
In the UI, we can have a filter option where we allow users to search based
on the properties.
not as GitHub issues, in order to reach the proper
audience. We strongly advise following the WSO2 Security Vulnerability
Reporting Guidelines
<https://docs.wso2.com/display/Security/WSO2+Security+Vulnerability+Reporting+Guidelines>
when
reporting security issues.
*-- The WSO2 API Ma
ecurity+Vulnerability+Reporting+Guidelines>
when
reporting security issues.
*-- The WSO2 API Manager Team --*
--
*Pubudu Gunatilaka* | Technical Lead | WSO2 Inc.
(m) +94774078049 | (w) +94112145345 | (e) pubu...@wso2.com
<http://wso2.com/signature>
_
;>
>>> *[-] Broken - Do not release *(explain why)
>>>
>>>
>>>
>>> Best Regards,
>>> WSO2 API Manager Team
>>>
>>> --
>>> *Naduni Pamudika* | Senior Software Engineer | WSO2 Inc.
>>> (m) +94 (71) 91436
nager Team
>>>
>>
>>
>> --
>> *Chashika Weerathunga* | Software Engineer | WSO2 Inc.
>> (m) +94713731206 | Email: chash...@wso2.com
>> [image: http://wso2.com]
>> <http://wso2.com>
>> __
Joao Emilio wrote:
> Have we moved forward with this initiative?
>
> Regards,
>
> *João Emilio*
> Solutions Architect | WSO2
>
> E-mail: j...@wso2.com
> Phone: + 55 11 3847 8967
> Web: http://www.wso2.com
>
> <http://wso2.com/signature>
>
>
>
gt;-
>>
>>Request Failure rate
>>
>>
>>
>>-
>>
>>No.of requests per second(Throughput)
>>
>>
>>
>> Rough sketch of a dashboard
>>
>> [image: dasboard.png]
>> I have created a swagger
you.
>> Regards.
>>
>> --
>>
>> *Lahiru Chandima Dayarathne *
>> Engineering Intern - API Management | WSO2
>>
>> Email : lahi...@wso2.com
>> Mobile : +94779232767
>> Web: https://wso2.com/
>>
>>
>>
>>
>>
>&
nally, it is also possible for a user to deploy a completely new
>deployment pattern with a new yaml file.
>
>
> Also, the documentation about this project can be found in this link
> <https://docs.google.com/document/d/1XBpdvjGUwqD8ojUBr1EYLMWTUEWkw_vgWDq4DSa3MsY/edit?usp=sharing>
&g
subscribed.
2. Generate an access token.
Output: *JWT token*
>From the next release onwards, we will be having self-contained access
tokens (JWT) for the default application as it will be the first option.
Your suggestions are appreciated.
Thank you!
--
*Pubudu Gunatilaka* | Associate Technical L
On Fri, Jul 26, 2019 at 2:36 PM Pubudu Gunatilaka
> wrote:
>
>> Hi Nuwan,
>>
>> On Thu, Jul 25, 2019 at 5:19 PM Nuwan Dias wrote:
>>
>>> Looks like our cloud team has done this already for the synapse based
>>> gateway. Maybe we could learn so
and do the deployment. The APIs created
in the publisher can be exported with the relevant artifacts required for
K8s deployment. Then that can be used to deploy in K8s.
Thank you!
--
*Pubudu Gunatilaka* | Associate Technical Lead | WSO2 Inc.
(m) +94774078049 | (w) +94112145345 | (e) pub
On Mon, Aug 12, 2019 at 10:53 AM Rukshan Premathunga
wrote:
> Hi All,
>
> ATM generated API definition is in swagger 2. Can we make it OAS 3 for the
> new APIs?
>
+1 to go with v3 as we are releasing a major version for APIM.
>
Thank you!
--
*Pubudu Gunatilaka* | Associ
s:* Easy to implement and manage
> *Cons:* Users can not download the .Balx
>
> Appreciate your thoughts.
> --
> *Sachith Kasthuriarachchi *| Engineering Intern | WSO2 Inc
> (m) +94 71 694 0826 | (w) www.wso2.com | (e) sachit...@wso2.com
>
>
> <http://goog_1559380502&
77 775 729 | (e) nuw...@wso2.com
>> [image: Signature.jpg]
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>
>
> --
>
>
We have now released WSO2 API Management for Istio v0.5.
https://github.com/wso2/istio-apim/releases/tag/0.5
Thank you!
On Wed, Jan 30, 2019 at 9:21 AM Pubudu Gunatilaka wrote:
> Hi,
>
> On Mon, Jan 28, 2019 at 5:43 PM Youcef HILEM
> wrote:
>
>> Hi Pubudu,
>> Than
- ""
For default case:
type: "default"
endpoints:
- ""
Thank you!
--
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Associate Technical Lead
WSO2, Inc.: http://wso2.com
mobile : +94774078049 <%2B94772207163>
_
pport for
> bulk of apis.
>
In the microgateway approach there won't be many APIs and micro-gw add-api
support should be able to handle.
Thank you!
--
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Associate Technical Lead
WS
the name of that folder corresponding to the API)
>
> 7. register command
>
> micro-gw register -a -v
>
>
> This command will publish the API in Store. Since we have the swagger file
> saved in the directory, we can use the Publisher API.
>
>
>
> Please consider that the command names and the arg
>> lean.enterprise.middleware
>>
>> mobile: *+94779109091*
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>
>
language and based on [1].
[1] -
https://github.com/istio/istio/wiki/Mixer-Out-Of-Process-Adapter-Walkthrough
<https://github.com/istio/istio/wiki/Mixer-Out-Of-Process-Adapter-Walkthrough>
Thank you!
--
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Associate Technical Lead
WSO
> Thanks
> Youcef HILEM
>
>
>
> --
> Sent from:
> http://wso2-oxygen-tank.10903.n7.nabble.com/WSO2-Architecture-f62919.html
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman
.10903.n7.nabble.com/WSO2-Architecture-f62919.html
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
--
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
n we do any of
these use cases.
Thank you!
--
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Associate Technical Lead
WSO2, Inc.: http://wso2.com
mobile : +94774078049 <%2B94772207163>
___
Architecture mailing list
Architecture@wso2.org
hat privilege. If someone decides to have a separate person to handle the
> comment then he/she can be assigned with the comment moderator role.
>
> +1 to use a comment moderator separate role if it is possible.
Thank you!
--
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stra
t
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>>>
>>
>> --
>>
>> *Tharindu Dharmarathna*Associate Technical Lead
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middlew
com> wrote:
> hi Pudubu,
>
>ok of your answer, I understand that it is not possible to add
> certificate on the version 2.1.0.
>
>What is GA Pack ?
>
> can I find this feature on the 2.2.0 GA Pack ?
>
> best regards,
>
> Nicolas Maujean
>
>
&g
2.1.0 of the APIM ?
>
> best regards,
>
> Nicolas Maujean
>
>
>
> Le mar. 18 sept. 2018 à 12:57, Pubudu Gunatilaka a
> écrit :
>
>> Hi Nicolas,
>>
>> This feature was introduced as a WUM update [1] to the APIM 2.1.0.
>> Therefore this fe
__
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
--
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Senior Software Engineer
WSO2, Inc.: http://wso2.com
mobile : +94774078049 <%2B94772207163&g
ngineer
> Mobile : +9477 262 9512
> WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
>>
>> ___
> Dev mailing list
> d...@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
--
*Pubudu Gunatil
yes how I can make the connection between the wso2 api-m and
> wso2 is ?
>
> best regards,
>
> Nicolas Maujean
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
n/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Rukshan Chathuranga.
>>> Software Engineer.
>>> WSO2, Inc.
>>> +94711822074
>>>
>>> ___
>>> Dev mai
Software Engineer
> WSO2 Inc
> Mobile: +94712939439
> <https://wso2.com/signature>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
--
*Pubudu Gunatilaka*
>>>>>> │ ├── customers_v3.0.0.bal
>>>>>>
>>>>>> │ └── leads_v4.0.0.bal
>>>>>>
>>>>>> └── target
>>>>>>
>>>>>> ├── sales.balx
Hi Nuwan,
On Thu, May 3, 2018 at 1:07 PM Nuwan Dias <nuw...@wso2.com> wrote:
>
>
> On Thu, May 3, 2018 at 1:02 PM, Pubudu Gunatilaka <pubu...@wso2.com>
> wrote:
>
>> Hi Krishan
>> On Thu, May 3, 2018 at 12:53 PM Harsha Kumara <hars...@wso2.com> wrot
//wso2.gw.com
https://wso2.gw.com
Additionally we need to add WebSocket endpoints as well. So we need to have
4 types of access urls in here.
Are we not using the endpionts defined in APIGateway section here after or
what is the strategy going forwar?
Are we adding a defau
;>> +Sagara, Johann
>>>
>>>
>>> On 29 March 2018 at 10:57, Uvindra Dias Jayasinha <uvin...@wso2.com>
>>> wrote:
>>>
>>>> I'm in favour of having userinfo separate from the default oauth2
>>>> service since its a different conce
/userinfo
Appreciate your thoughts?
[1] -
https://docs.wso2.com/display/IS450/OpenID+Connect+Basic+Client+Profile+with+WSO2+Identity+Server
Thank you!
--
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Senior Software Engineer
WSO2, Inc.: http://wso2.com
mobile : +94774078049
ternally
from the APIM. We can use the kubernetes.default to access the Kubernetes
API server within the pod. In this case we do not need to provide the
service account token to the APIM. Kubernetes client reads the token from
the pod mounted path.
Thank you!
--
*Pubudu Gunatilaka*
Committer and PM
REST APIs
> - /api/am/admin/v1.0 - Admin REST APIs
> - /api/am/analytics/v1.0 - Analytic REST APIs
>
>
We have another REST API called core API (/api/am/core/v1.0) which is for
internal server communications. This is planned to secure by mutual ssl.
Thank you!
--
*Pubudu Gunatilaka*
and feature requests
regarding WSO2 API Manager through WSO2 API Manager GIT Issues
<https://github.com/wso2/product-apim/issues>.
~ WSO2 API Manager Team ~
--
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Senior Software Engineer
WSO2, Inc.: http://wso2.com
m
ssing at
>> the client side without iterating a list.
>>
>> GET /api/am/config/v1.0/features
>>
>> Response:
>> {
>>"privateJetMode" : {
>> "name":"Private Jet Mode",
>> "isEnabled&q
Per Gateway with Kubernetes and Openshift
[2] - https://github.com/wso2/product-apim/issues/1831
Thank you!
--
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Senior Software Engineer
WSO2, Inc.: http://wso2.com
mobile : +94774078049 <%2B94772207
quot;
}
],
"count":1
}
Any thoughts?
Thank you!
--
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Senior Software Engineer
WSO2, Inc.: http://wso2.com
mobile : +94774078049 <%2B94772207163>
___
Architecture maili
/>
- User Forum : StackOverflow
<https://stackoverflow.com/questions/tagged/wso2-am>
Reporting Issues
We encourage you to report issues, improvements and feature requests
regarding WSO2 API Manager through WSO2 API Manager GIT Issues
<https://github.com/wso2/product-apim/i
t; Constraints
> - On DC/OS volumes can be directly granted to user group gid:200.
>
> Really appreciate your thoughts on this proposal.
>
> Thanks
> Imesh
>
> --
> *Imesh Gunaratne*
> WSO2 Inc: http://wso2.com
> T: +94 11 214 5345 M: +94 77 374 2057 <
ttps://github.com/wso2/product-apim/issues/2299
>
> Appreciate any suggestions.
> Thanks
>
> Best regards
> Renuka
> --
> *Renuka Fernando*
> Software Engineering Intern | WSO2 Inc
>
> Email : ren...@wso2.com
> Mobile : +94 76 667 8752 <+94%2076%20667%208752>
ntha Amarasinghe
>> *WSO2, Inc. - lean | enterprise | middleware*
>> http://wso2.com/
>>
>> Mobile : +94 712383306 <+94%2071%20238%203306>
>>
>
>
>
> --
> Malintha Amarasinghe
> *WSO2, Inc. - lean | enterprise | middleware*
> http://wso2.com/
>
> Mobile : +94 7123833
>
Reporting Issues
We encourage you to report issues, improvements and feature requests
regarding WSO2 API Manager through WSO2 API Manager GIT Issues
<https://github.com/wso2/product-apim/issues>.
~ WSO2 API Manager Team ~
--
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Hi Susankha,
On Fri, Dec 15, 2017 at 3:26 PM, Susankha Nirmala <susan...@wso2.com> wrote:
>
>
> On Fri, Dec 15, 2017 at 3:14 PM, Pubudu Gunatilaka <pubu...@wso2.com>
> wrote:
>
>> Hi Susankha,
>>
>> We have a guide which explains when to use hazelca
Blogs : https://medium.com/@lakwarus/
> http://lakmalsview.blogspot.com/
>
>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
--
*P
> [4] - https://github.com/tianon/docker-brew-ubuntu-core/tree/
> 5fce3945d95630c2fc03c21ef8665d92bd824642
>
> Regards,
> Chamila de Alwis
> Committer and PMC Member - Apache Stratos
> Senior Software Engineer | WSO2
> +94 77 220 7163 <+94%2077%20220%207163>
> Blog: https://m
;
>>>
>>> Appreciate any suggestions.
>>> Thanks
>>>
>>> Best regards
>>>
>>> --
>>> *Renuka Fernando*
>>> Software Engineering Intern | WSO2 Inc
>>>
>>> Email : ren...@wso2.com
>>> Mobil
n>
>>>
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>>
pecificParameters:
>> insidePod: true
>>
>
> Why we need insidePod:true ? AFAIR we have discussed this. If config not
> providing serviceAccountToken thats implies we have to look token inside
> the pod. Otherwise will take token which provide in the config.
>
the GitHub issue tracker available at
https://github.com/wso2/kubernetes-apim/issues
Thank you!
WSO2 API Manager Team.
--
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Senior Software Engineer
WSO2, Inc.: http://wso2.com
mobile : +94774078049 <%2B94772207
/kubernetes-apim/tree/2.1.0-nfs
Thank you!
On Mon, Sep 18, 2017 at 2:11 PM, Pubudu Gunatilaka <pubu...@wso2.com> wrote:
> Hi Youcef,
>
> We will go through the error logs and try to identify if there is an
> issue. Also, we have started working on NFS.
>
> Thank you!
>
&
729 <+94%2077%20777%205729>
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>&
.equinox.internal.ds.Resolver.getEligible(Resolve
>> r.java:343)
>> at
>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SC
>> RManager.java:222)
>> at
>> org.eclipse.osgi.internal.serviceregistry.Filter
*Quick Start Guide:*
https://github.com/wso2/kubernetes-apim/blob/v2.1.0-1/README.md
*Reporting Issues:*
Issues can be reported using the GitHub issue tracker available at
https://github.com/wso2/kubernetes-apim/issues
Thank you!
WSO2 API Manager Team.
--
*Pubudu Gunatilaka*
Committer and PMC
57>
> W: https://medium.com/@imesh TW: @imesh
> lean. enterprise. middleware
>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
--
*Pubudu Gunatil
Hi Imesh,
On Thu, Sep 7, 2017 at 10:44 AM, Imesh Gunaratne <im...@wso2.com> wrote:
> Hi Pubudu,
>
> On Thu, Sep 7, 2017 at 12:54 AM, Pubudu Gunatilaka <pubu...@wso2.com>
> wrote:
>
>>
>> On Wed, Sep 6, 2017 at 11:06 PM, Imesh Gunaratne <im...@wso2
Hi Imesh,
On Wed, Sep 6, 2017 at 11:06 PM, Imesh Gunaratne <im...@wso2.com> wrote:
> Hi Pubudu,
>
> On Wed, Sep 6, 2017 at 10:25 PM, Pubudu Gunatilaka <pubu...@wso2.com>
> wrote:
>
>> Hi Imesh,
>>
>> I actually used the product paths as the moun
gards.
>>
>> --
>> *Sabeena Kumarawadu* | Software Engineering Intern
>> WSO2 Lanka (Pvt) Ltd.
>> #20, Palm Grove, Colombo 03, Sri Lanka
>> Mobile: +94 71 0372856 <071%20037%202856>
>> Email: sabe...@wso2.com
>> [image: http://wso2.com/signature] <h
struct the API
>>>>> endpoint from API Manager side.
>>>>>
>>>>> For k8s and openshift this is the design that we discussed.
>>>>>
>>>>>
>>>>> I will further check on how we can get the API Access URL
gt;
>> Software Architect - WSO2, Inc. http://wso2.com
>> email : nuw...@wso2.com
>> Phone : +94 777 775 729 <+94%2077%20777%205729>
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>>
> 2-a
>>>
>>>
>>>
>>> Figure : Option
>>> 2-b
>>>
>>> Appreciate your comments and suggestions.
>>>
>>>
>>> Thank you,
>>>
>>> Sachini
gateway registration. This is more suitable in order to introduce
the permission model to the labels. The label selection is not mandatory
when creating an API. If the user hasn't selected any label, we can attach
the default label.
Thank you!
--
*Pubudu Gunatilaka*
Committer and PMC Member - Apache
need to do anything
specifically. If we consider a container scenario, we only need to pass an
environment variable with the new label name to the container to spin up a
new gateway container in a new region.
Thank you!
--
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Software
+ Adding architecture mail group
On Mon, May 8, 2017 at 11:59 PM, Pubudu Gunatilaka <pubu...@wso2.com> wrote:
> Hi Fazlan,
>
> As Ishara mentioned above, we can do this with scope validation. Each and
> every resource has a scope. The scope is associated with one or more
ions?
>>
>> Thanks
>> --
>> Thilini Shanika
>> Senior Software Engineer
>> WSO2, Inc.; http://wso2.com
>> 20, Palmgrove Avenue, Colombo 3
>>
>> E-mail: tgtshan...@gmail.com
>>
>>
>
>
> --
> Lakmal Warusawithana
> Director
On Wed, Apr 26, 2017 at 1:11 PM, Lakmal Warusawithana <lak...@wso2.com>
wrote:
>
>
> On Wed, Apr 26, 2017 at 11:34 AM, Pubudu Gunatilaka <pubu...@wso2.com>
> wrote:
>
>> On Wed, Apr 26, 2017 at 11:02 AM, Lakmal Warusawithana <lak...@wso2.com>
>> wrote:
ntainer scenario, are we persisting gateway artifacts?
If we are not persisting gateway artifacts and restart the gateway
container, then we need to fetch all the APIs from the core. IMHO it would
better to persist data and load that data at restart as it would take time
to fetch all the APIs from
default, if you haven't selected any label at the API
creation time, default label will be added to the API.
> 3) I believe there will be a service in the Core to register new label so
> that gateways can use. Is that how it works?
>
Yes, there will be a service to register labels
SO2 Inc.
> Mobile: *+94719154640*
> Email: ros...@wso2.com
> *WSO2, Inc. :** wso2.com <http://wso2.com/>*
> lean.enterprise.middleware.
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/m
ot;private"
]
}
*Response* -
{
"count":2,
"list":[
{
"name":"public",
"access_url":"https://test.cloud.public;
},
{
"name":"private",
"access_url":&qu
oint), but the API by itself is considered to be the
> “same” across all Runtimes. Will this use case be covered at all as it has
> some impact on deployment of APIs?
>
If I rephrase the requirement, an API can have multiple backend enpoints
for different runtimes. There is a plan to cove
system parameter called
'overwrite_labels' to overwrite the URL of the gateways.
By going forward, there will be no any configuration file for configuring
labels. This make sure that we are not binded to a configuration file and
allowing users to add any label by starting up a new gateway node.
> Thanks and
;sh...@wso2.com> wrote:
> At this stage, are we looking at editing a label also?
>
> On Wed, Feb 8, 2017 at 5:12 PM, Pubudu Gunatilaka <pubu...@wso2.com>
> wrote:
>
>> Hi,
>>
>> Please find the answers inline.
>>
>> On Wed, Feb 8, 2017 at
Labels
will be assigned to gateways at startup of the gateway node. Message broker
does not assign any labels.
Thank you!
--
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Software Engineer
WSO2, Inc.: http://wso2.com
mobile : +94774078049 <%2B94772207163>
__
the message. When a request comes to the
gateway, it will request for the API by giving its label. Then the
publisher will only provide the API, if only the API has the relevant label.
Hope this is clear.
Thank you!
--
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Software Engineer
W
way as internal and external. The internal gateway would not be
>> exposed to the same network as the public/external one. Hence there might
>> be use cases where we can't use a single gateway for both internal and
>> external.
>>
>>>
>>> Due to the complicatio
I
>>2. From the api artifact itself(if it is allowed).
>>
>>
Basically, when an API is updated a message will be published to the broker
and gateways will receive the event if gateway is up and running. If the
gateway is serving requests on demand, it will only update the API artifact
once i
C5 onwards. In a particular stage, there
can be different gateway environments.
Please share your thoughts.
Thank you!
--
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Software Engineer
WSO2, Inc.: http://wso2.com
mobile : +94774078049 <%2B94772207
>>>
>>>
>>> _______
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>> _
exact folder path from C5
>> product structure)?
>>
>> Thanks
>>
>>
>> --
>> *Imesh Gunaratne*
>> Software Architect
>> WSO2 Inc: http://wso2.com
>> T: +94 11 214 5345 M: +94 77 374 2057 <+94%2077%20374%202057>
>> W: https://medium.com/@imesh TW: @im
r approach. +1
>
>
> Regards,
> Chamila de Alwis
> Committer and PMC Member - Apache Stratos
> Senior Software Engineer | WSO2
> Blog: https://medium.com/@chamilad
>
>
>
--
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Software Engineer
WSO2, Inc.: h
f Puppet
>> containment [1] to handle dependencies at the run time. But thinking again,
>> it makes me wonder whether we need that kind of complexity at this point.
>> Better to start with the simplest approach and let it evolve.
>&
all "dockerfile-" instead of "docker-"?
>
> Thanks
>
> On Mon, Aug 8, 2016 at 12:02 PM, Pubudu Gunatilaka <pubu...@wso2.com>
> wrote:
>
>> Hi,
>>
>> Following are the proposed repo names for the existing puppet modules.
>>
>&g
-artifacts/releases/tag/v1.0.0
Documentation:
https://docs.wso2.com/display/MA100/WSO2+Mesos+Artifacts+Documentation
Please report any issues/suggestion for improvements at:
https://wso2.org/jira/browse/MESOSARFTS
Thank you!
WSO2 PaaS Team.
--
*Pubudu Gunatilaka*
Committer and PMC Member - Apache
/display/PM210/WSO2+Puppet+Modules+Documentation
*Fixed Issues:*
https://wso2.org/jira/issues/?filter=13155
*Known Issues:*
https://wso2.org/jira/issues/?filter=13156
Thank you!
WSO2 PaaS team
--
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Software Engineer
WSO2, Inc.: http
96 matches
Mail list logo
