Re: [Architecture] [APIM][C5] Multi Environment support with API difference for API Manager

[Kasun Thennakoon]

Hi Cyril,

Sorry, currently we don't have plans to support such operation. If you are
interested in implementing that feature, You are always welcome to
contribute to API Manager :) .


Thanks
~KasunTe


On Tue, Nov 28, 2017 at 8:38 PM, Cyril Rognon  wrote:

> Hi all
>
> Nice work.
>
> Is it planned to allow API migration management through this tool /UI  ?
>
> Tanks
> Cyril
>
>
>
>
> Le 28 nov. 2017 3:56 PM, "Shazni Nazeer"  a écrit :
>
> In this case say the user is logged into another environment and the token
>>> is still valid for that environment how have we planned to switch to that
>>> environment, should the user chose to switch to that while on login page of
>>> the first? Do we plan to provide links to other environments in the login
>>> page it self?
>>
>>
> We list the available environments in the login page. But from the login
>> page, users can't switch to an environment, even though they have a valid
>> token for that environment.
>
>
> It would be good if we can find a way to allow the user to switch to an
> already logged in environment even from the login page for better user
> experience. Unless there're technical difficulties I would prefer that way
> so that I'm not forced to login to a token expired environment to switch to
> an environment for which I have a valid token.
>
> On Tue, Nov 28, 2017 at 5:16 AM, Kasun Thennakoon 
> wrote:
>
>> Hi Shazni,
>>
>>
>>> I get the point of why we shouldn't be using the redirection and instead
>>> use the underlying REST API, which is needed as rightly mentioned by
>>> Thilini for seamless switching. Just for curiosity, when switching between
>>> the environments we still have to make whatever the REST calls every time
>>> to get the updated values of the respective environments details right?
>>>
>>
>> Yes, When a user switch to an enviroments, We create an instance of
>> swagger-client[2] specific to that selected enviroment an instance is not
>> available already for that enviroment. Swagger-client is used to make REST
>> API calls from the browser. For an example, If user was in API Listing page
>> and he changed the enviroment to new one, We will change the swagger-client
>> instance to newly selected enviroment and there after all the REST API
>> calls made to that enviroment are same.
>>
>>
>>> Also when the token expires for a given environment, the user will be
>>> redirected back to the login page right?
>>>
>>
>> Yes, If the token is expired the user will be redirect[1](Not HTTP
>> redirect) to the login page.
>>
>> In this case say the user is logged into another environment and the
>>> token is still valid for that environment how have we planned to switch to
>>> that environment, should the user chose to switch to that while on login
>>> page of the first? Do we plan to provide links to other environments in the
>>> login page it self?
>>>
>>
>> We list the available environments in the login page. But from the login
>> page, users can't switch to an environment, even though they have a valid
>> token for that environment.
>>
>> [1]: https://github.com/wso2/carbon-apimgt/blob/master/featu
>> res/apimgt/org.wso2.carbon.apimgt.publisher.feature/src/main
>> /resources/publisher/source/src/App.js#L74
>> [2]: https://github.com/swagger-api/swagger-js
>> --
>> *Kasun Thennakoon*
>> Software Engineer
>> WSO2, Inc.
>> Mobile:+94 711661919
>>
>
>
>
> --
> Shazni Nazeer
>
> Mob : +94 37331
> LinkedIn : http://lk.linkedin.com/in/shazninazeer
>
> Blogs :
>
> https://medium.com/@mshazninazeer
> http://shazninazeer.blogspot.com
>
> 
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
>


-- 
*Kasun Thennakoon*
Software Engineer
WSO2, Inc.
Mobile:+94 711661919
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [APIM][C5] Multi Environment support with API difference for API Manager

[Cyril Rognon]

Hi all

Nice work.

Is it planned to allow API migration management through this tool /UI  ?

Tanks
Cyril




Le 28 nov. 2017 3:56 PM, "Shazni Nazeer"  a écrit :

In this case say the user is logged into another environment and the token
>> is still valid for that environment how have we planned to switch to that
>> environment, should the user chose to switch to that while on login page of
>> the first? Do we plan to provide links to other environments in the login
>> page it self?
>
>
We list the available environments in the login page. But from the login
> page, users can't switch to an environment, even though they have a valid
> token for that environment.


It would be good if we can find a way to allow the user to switch to an
already logged in environment even from the login page for better user
experience. Unless there're technical difficulties I would prefer that way
so that I'm not forced to login to a token expired environment to switch to
an environment for which I have a valid token.

On Tue, Nov 28, 2017 at 5:16 AM, Kasun Thennakoon  wrote:

> Hi Shazni,
>
>
>> I get the point of why we shouldn't be using the redirection and instead
>> use the underlying REST API, which is needed as rightly mentioned by
>> Thilini for seamless switching. Just for curiosity, when switching between
>> the environments we still have to make whatever the REST calls every time
>> to get the updated values of the respective environments details right?
>>
>
> Yes, When a user switch to an enviroments, We create an instance of
> swagger-client[2] specific to that selected enviroment an instance is not
> available already for that enviroment. Swagger-client is used to make REST
> API calls from the browser. For an example, If user was in API Listing page
> and he changed the enviroment to new one, We will change the swagger-client
> instance to newly selected enviroment and there after all the REST API
> calls made to that enviroment are same.
>
>
>> Also when the token expires for a given environment, the user will be
>> redirected back to the login page right?
>>
>
> Yes, If the token is expired the user will be redirect[1](Not HTTP
> redirect) to the login page.
>
> In this case say the user is logged into another environment and the token
>> is still valid for that environment how have we planned to switch to that
>> environment, should the user chose to switch to that while on login page of
>> the first? Do we plan to provide links to other environments in the login
>> page it self?
>>
>
> We list the available environments in the login page. But from the login
> page, users can't switch to an environment, even though they have a valid
> token for that environment.
>
> [1]: https://github.com/wso2/carbon-apimgt/blob/master/featu
> res/apimgt/org.wso2.carbon.apimgt.publisher.feature/src/
> main/resources/publisher/source/src/App.js#L74
> [2]: https://github.com/swagger-api/swagger-js
> --
> *Kasun Thennakoon*
> Software Engineer
> WSO2, Inc.
> Mobile:+94 711661919
>



-- 
Shazni Nazeer

Mob : +94 37331
LinkedIn : http://lk.linkedin.com/in/shazninazeer

Blogs :

https://medium.com/@mshazninazeer
http://shazninazeer.blogspot.com



___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [APIM][C5] Multi Environment support with API difference for API Manager

[Shazni Nazeer]

>
> In this case say the user is logged into another environment and the token
>> is still valid for that environment how have we planned to switch to that
>> environment, should the user chose to switch to that while on login page of
>> the first? Do we plan to provide links to other environments in the login
>> page it self?
>
>
We list the available environments in the login page. But from the login
> page, users can't switch to an environment, even though they have a valid
> token for that environment.


It would be good if we can find a way to allow the user to switch to an
already logged in environment even from the login page for better user
experience. Unless there're technical difficulties I would prefer that way
so that I'm not forced to login to a token expired environment to switch to
an environment for which I have a valid token.

On Tue, Nov 28, 2017 at 5:16 AM, Kasun Thennakoon  wrote:

> Hi Shazni,
>
>
>> I get the point of why we shouldn't be using the redirection and instead
>> use the underlying REST API, which is needed as rightly mentioned by
>> Thilini for seamless switching. Just for curiosity, when switching between
>> the environments we still have to make whatever the REST calls every time
>> to get the updated values of the respective environments details right?
>>
>
> Yes, When a user switch to an enviroments, We create an instance of
> swagger-client[2] specific to that selected enviroment an instance is not
> available already for that enviroment. Swagger-client is used to make REST
> API calls from the browser. For an example, If user was in API Listing page
> and he changed the enviroment to new one, We will change the swagger-client
> instance to newly selected enviroment and there after all the REST API
> calls made to that enviroment are same.
>
>
>> Also when the token expires for a given environment, the user will be
>> redirected back to the login page right?
>>
>
> Yes, If the token is expired the user will be redirect[1](Not HTTP
> redirect) to the login page.
>
> In this case say the user is logged into another environment and the token
>> is still valid for that environment how have we planned to switch to that
>> environment, should the user chose to switch to that while on login page of
>> the first? Do we plan to provide links to other environments in the login
>> page it self?
>>
>
> We list the available environments in the login page. But from the login
> page, users can't switch to an environment, even though they have a valid
> token for that environment.
>
> [1]: https://github.com/wso2/carbon-apimgt/blob/master/
> features/apimgt/org.wso2.carbon.apimgt.publisher.
> feature/src/main/resources/publisher/source/src/App.js#L74
> [2]: https://github.com/swagger-api/swagger-js
> --
> *Kasun Thennakoon*
> Software Engineer
> WSO2, Inc.
> Mobile:+94 711661919
>



-- 
Shazni Nazeer

Mob : +94 37331
LinkedIn : http://lk.linkedin.com/in/shazninazeer

Blogs :

https://medium.com/@mshazninazeer
http://shazninazeer.blogspot.com


___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [APIM][C5] Multi Environment support with API difference for API Manager

[Kasun Thennakoon]

Hi Shazni,


> I get the point of why we shouldn't be using the redirection and instead
> use the underlying REST API, which is needed as rightly mentioned by
> Thilini for seamless switching. Just for curiosity, when switching between
> the environments we still have to make whatever the REST calls every time
> to get the updated values of the respective environments details right?
>

Yes, When a user switch to an enviroments, We create an instance of
swagger-client[2] specific to that selected enviroment an instance is not
available already for that enviroment. Swagger-client is used to make REST
API calls from the browser. For an example, If user was in API Listing page
and he changed the enviroment to new one, We will change the swagger-client
instance to newly selected enviroment and there after all the REST API
calls made to that enviroment are same.


> Also when the token expires for a given environment, the user will be
> redirected back to the login page right?
>

Yes, If the token is expired the user will be redirect[1](Not HTTP
redirect) to the login page.

In this case say the user is logged into another environment and the token
> is still valid for that environment how have we planned to switch to that
> environment, should the user chose to switch to that while on login page of
> the first? Do we plan to provide links to other environments in the login
> page it self?
>

We list the available environments in the login page. But from the login
page, users can't switch to an environment, even though they have a valid
token for that environment.

[1]:
https://github.com/wso2/carbon-apimgt/blob/master/features/apimgt/org.wso2.carbon.apimgt.publisher.feature/src/main/resources/publisher/source/src/App.js#L74
[2]: https://github.com/swagger-api/swagger-js
-- 
*Kasun Thennakoon*
Software Engineer
WSO2, Inc.
Mobile:+94 711661919
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [APIM][C5] Multi Environment support with API difference for API Manager

[Bhathiya Jayasekara]

Hi Rajith,

On Mon, Nov 6, 2017 at 9:11 PM, Rajith Roshan  wrote:

> Hi,
>
> On Mon, Nov 6, 2017 at 7:16 PM, Bhathiya Jayasekara 
> wrote:
>
>> Hi Renuka,
>>
>> On Mon, Nov 6, 2017 at 4:24 PM, Renuka Fernando  wrote:
>>
>>> Hi,
>>>
>>> The property environmentName is used to append environment name to
>>> cookie and label is used to list down environments in the login page.
>>>
>>
>> Stil not clear to me either. Let me ask 2 direct questions.
>>
>> 1) In your sample, you have 2 environments, development and production.
>> But your environmentName is Default. What does that mean?
>>
> What if there are no multiple environments in deployment.yaml. Then cookie
> names will not have any environment name append to it.   So to maintain
> consistency of cookie names I think its better to have a default value for
> environment.
>

Yes, it's fine to have a default value when there are no multiple
environments. But my question is about when you have multiple environments.
Shouldn't this environmentName be one of those environment labels? If not,
I'm confused.


> But the name environment name can be confusing. As in your second question
> sometimes this might not be environment (just provide the UI).
>
>> 2) In case of UI service running separately, what should be the value of 
>> environmentName?
>> (I guess you don't need that in this case. Please confirm.)
>>
> Exactly this is one use case. UI can be served by separate node which is
> not a environment . This is where the environment list comes into play.
> User will have to definitely select either production or development here.
> Default value is never present to the UI. It is only for internal reference
> only.
>

What do we do with that internally? Why can't we just drop that, in this
case?

Thanks,
Bhathiya


>
> I think overall there are some missing points in this design we need to
> clarify.
> @KasunTe, @PubuduG, Could you please shed some light here since, you have
> closely followed the GSoc project.
>
>>
>> Thanks,
>> Bhathiya
>>
>>
>>>
>>> Thank you
>>>
>>> On 6 November 2017 at 15:34, Pubudu Gunatilaka  wrote:
>>>
 Hi,

 environmentName is used to keep the environment to itself. This is used
 when the server is setting up the cookies by appending the env name to the
 cookies. The env list is to populate the env list.

 Thank you!

 On Mon, Nov 6, 2017 at 2:42 PM, Chamin Dias  wrote:

> Hi Renuka,
>
> Step 7 : "The environment read its deployment.yaml to know the name
> of itself and set cookies..."
>
> So this means the environment name is taken from the environment
> itself. Is there any reason to exclude the environment in the
> provided yaml file?
>
> Thanks.
>
>
> On Mon, Nov 6, 2017 at 2:24 PM, Bhathiya Jayasekara  > wrote:
>
>> Hi Renuka,
>>
>> On Mon, Nov 6, 2017 at 11:27 AM, Renuka Fernando 
>> wrote:
>>
>>> Hi all,
>>>
>>> We are planning to implement new feature "Multi-Environment
>>> Support"[1] for API Manager. The feature allows users to manage
>>> environments through one User Interfaces.
>>>
>>> [image: Inline images 1]
>>> Suppose there are three environments (i.e. three instance of API
>>> manager) currently running in an organization. Users of the API Manager
>>> have log into each environments and work with three different User
>>> Interfaces. The proposed feature allow one User Interface to handle all
>>> environments. User can switch environments and also enable new feature 
>>> like
>>> API difference in environments.
>>>
>>> This is the proposed design of multi-environment support for API
>>> manager.
>>> [image: Inline images 2]
>>>
>>> The UI service in the diagram may be a separate service for User
>>> Interface or another environment itself.
>>>
>>>
>>>1. Browser request login page for the app
>>>(publisher/store/admin) from UI service.
>>>2. Serve the page.
>>>3. Browser call the ConfigurationsAPI
>>>(org.wso2.carbon.apimgt.rest.api.configurations)[2] to get
>>>available environments.
>>>
>>> Since this API is a part of UI service (but not of core), we may
>> need a different name to indicate that.
>>
>>>
>>>1. Read deployment.yaml that contains environments' details
>>>   - Sample deployment.yaml
>>>   -
>>>
>>>   wso2.carbon.apimgt.environments:
>>> environmentName: Default
>>> environments:
>>> - host: dev.sample.com:9292
>>>   loginTokenPath: /login/token
>>>   label: Development
>>>
>>>
>>>
>> What's he dfference between environmentName and environments.label?
>> (If environmentName represents the current environment, souldn't it
>> be one of environments.labels?)
>>
>> Thanks,
>> Bhathiya
>>
>>>
>>> 

Re: [Architecture] [APIM][C5] Multi Environment support with API difference for API Manager

[Rajith Roshan]

Hi

On Mon, Nov 6, 2017 at 7:18 PM, Abimaran Kugathasan 
wrote:

> Hi Renuka,
>
> Still, those two images aren't there in mails.
>
> What do you mean by "enable new feature like API difference in
> environments"? Checking differences in APIs between environments? I think,
> this feature required only for Publisher.
>
I think its to compare APIS in different APIs. I think using this feature
user can be logged into multiple environments at once (By switching
environment he logged into new environment without log out from already
logged in environment). So this feature will  allow to bring APIS from
different   environments, hence we can provide the capability of comparison
(diff).


>
>
> On Mon, Nov 6, 2017 at 6:11 PM, Sanjeewa Malalgoda 
> wrote:
>
>>
>>
>> On Mon, Nov 6, 2017 at 4:24 PM, Renuka Fernando  wrote:
>>
>>> Hi,
>>>
>>> The property environmentName is used to append environment name to
>>> cookie and label is used to list down environments in the login page.
>>>
>> Still it is not clear for me. If this is meta data related to all
>> environments, then we should not use environment name here and use
>> something else.
>>
>> Thanks,
>> sanjeewa.
>>
>>>
>>> Thank you
>>>
>>> On 6 November 2017 at 15:34, Pubudu Gunatilaka  wrote:
>>>
 Hi,

 environmentName is used to keep the environment to itself. This is used
 when the server is setting up the cookies by appending the env name to the
 cookies. The env list is to populate the env list.

 Thank you!

 On Mon, Nov 6, 2017 at 2:42 PM, Chamin Dias  wrote:

> Hi Renuka,
>
> Step 7 : "The environment read its deployment.yaml to know the name
> of itself and set cookies..."
>
> So this means the environment name is taken from the environment
> itself. Is there any reason to exclude the environment in the
> provided yaml file?
>
> Thanks.
>
>
> On Mon, Nov 6, 2017 at 2:24 PM, Bhathiya Jayasekara  > wrote:
>
>> Hi Renuka,
>>
>> On Mon, Nov 6, 2017 at 11:27 AM, Renuka Fernando 
>> wrote:
>>
>>> Hi all,
>>>
>>> We are planning to implement new feature "Multi-Environment
>>> Support"[1] for API Manager. The feature allows users to manage
>>> environments through one User Interfaces.
>>>
>>> [image: Inline images 1]
>>> Suppose there are three environments (i.e. three instance of API
>>> manager) currently running in an organization. Users of the API Manager
>>> have log into each environments and work with three different User
>>> Interfaces. The proposed feature allow one User Interface to handle all
>>> environments. User can switch environments and also enable new feature 
>>> like
>>> API difference in environments.
>>>
>>> This is the proposed design of multi-environment support for API
>>> manager.
>>> [image: Inline images 2]
>>>
>>> The UI service in the diagram may be a separate service for User
>>> Interface or another environment itself.
>>>
>>>
>>>1. Browser request login page for the app
>>>(publisher/store/admin) from UI service.
>>>2. Serve the page.
>>>3. Browser call the ConfigurationsAPI
>>>(org.wso2.carbon.apimgt.rest.api.configurations)[2] to get
>>>available environments.
>>>
>>> Since this API is a part of UI service (but not of core), we may
>> need a different name to indicate that.
>>
>>>
>>>1. Read deployment.yaml that contains environments' details
>>>   - Sample deployment.yaml
>>>   -
>>>
>>>   wso2.carbon.apimgt.environments:
>>> environmentName: Default
>>> environments:
>>> - host: dev.sample.com:9292
>>>   loginTokenPath: /login/token
>>>   label: Development
>>>
>>>
>>>
>> What's he dfference between environmentName and environments.label?
>> (If environmentName represents the current environment, souldn't it
>> be one of environments.labels?)
>>
>> Thanks,
>> Bhathiya
>>
>>>
>>>-
>>>
>>>
>>>
>>> - host: prod.sample.com:9292
>>>   loginTokenPath: /login/token
>>>   label: Production
>>>
>>>   1. Serve environments' details as JSON.
>>>   - Browser then render a list of environments.
>>>2. Send request with user credentials to the proper environment
>>>to login.
>>>3. The environment read its deployment.yaml to know the name of
>>>itself and set cookies with appending the name to the cookie name.
>>>
>>> [1] https://github.com/wso2/carbon-apimgt/issues/4690
>>> [2] https://github.com/wso2/carbon-apimgt/pull/4679
>>>
>>>
>>> Appreciate any suggestions.
>>> Thanks
>>>
>>> Best regards
>>>
>>> --
>>> *Renuka Fernando*
>>> Software Engineering Intern | WSO2 Inc
>

Re: [Architecture] [APIM][C5] Multi Environment support with API difference for API Manager

[Rajith Roshan]

Hi,

On Mon, Nov 6, 2017 at 7:16 PM, Bhathiya Jayasekara 
wrote:

> Hi Renuka,
>
> On Mon, Nov 6, 2017 at 4:24 PM, Renuka Fernando  wrote:
>
>> Hi,
>>
>> The property environmentName is used to append environment name to
>> cookie and label is used to list down environments in the login page.
>>
>
> Stil not clear to me either. Let me ask 2 direct questions.
>
> 1) In your sample, you have 2 environments, development and production.
> But your environmentName is Default. What does that mean?
>
What if there are no multiple environments in deployment.yaml. Then cookie
names will not have any environment name append to it.   So to maintain
consistency of cookie names I think its better to have a default value for
environment.
But the name environment name can be confusing. As in your second question
sometimes this might not be environment (just provide the UI).

> 2) In case of UI service running separately, what should be the value of 
> environmentName?
> (I guess you don't need that in this case. Please confirm.)
>
Exactly this is one use case. UI can be served by separate node which is
not a environment . This is where the environment list comes into play.
User will have to definitely select either production or development here.
Default value is never present to the UI. It is only for internal reference
only.

I think overall there are some missing points in this design we need to
clarify.
@KasunTe, @PubuduG, Could you please shed some light here since, you have
closely followed the GSoc project.

>
> Thanks,
> Bhathiya
>
>
>>
>> Thank you
>>
>> On 6 November 2017 at 15:34, Pubudu Gunatilaka  wrote:
>>
>>> Hi,
>>>
>>> environmentName is used to keep the environment to itself. This is used
>>> when the server is setting up the cookies by appending the env name to the
>>> cookies. The env list is to populate the env list.
>>>
>>> Thank you!
>>>
>>> On Mon, Nov 6, 2017 at 2:42 PM, Chamin Dias  wrote:
>>>
 Hi Renuka,

 Step 7 : "The environment read its deployment.yaml to know the name of
 itself and set cookies..."

 So this means the environment name is taken from the environment
 itself. Is there any reason to exclude the environment in the provided
 yaml file?

 Thanks.


 On Mon, Nov 6, 2017 at 2:24 PM, Bhathiya Jayasekara 
 wrote:

> Hi Renuka,
>
> On Mon, Nov 6, 2017 at 11:27 AM, Renuka Fernando 
> wrote:
>
>> Hi all,
>>
>> We are planning to implement new feature "Multi-Environment
>> Support"[1] for API Manager. The feature allows users to manage
>> environments through one User Interfaces.
>>
>> [image: Inline images 1]
>> Suppose there are three environments (i.e. three instance of API
>> manager) currently running in an organization. Users of the API Manager
>> have log into each environments and work with three different User
>> Interfaces. The proposed feature allow one User Interface to handle all
>> environments. User can switch environments and also enable new feature 
>> like
>> API difference in environments.
>>
>> This is the proposed design of multi-environment support for API
>> manager.
>> [image: Inline images 2]
>>
>> The UI service in the diagram may be a separate service for User
>> Interface or another environment itself.
>>
>>
>>1. Browser request login page for the app (publisher/store/admin)
>>from UI service.
>>2. Serve the page.
>>3. Browser call the ConfigurationsAPI
>>(org.wso2.carbon.apimgt.rest.api.configurations)[2] to get
>>available environments.
>>
>> Since this API is a part of UI service (but not of core), we may need
> a different name to indicate that.
>
>>
>>1. Read deployment.yaml that contains environments' details
>>   - Sample deployment.yaml
>>   -
>>
>>   wso2.carbon.apimgt.environments:
>> environmentName: Default
>> environments:
>> - host: dev.sample.com:9292
>>   loginTokenPath: /login/token
>>   label: Development
>>
>>
>>
> What's he dfference between environmentName and environments.label?
> (If environmentName represents the current environment, souldn't it
> be one of environments.labels?)
>
> Thanks,
> Bhathiya
>
>>
>>-
>>
>>
>>
>> - host: prod.sample.com:9292
>>   loginTokenPath: /login/token
>>   label: Production
>>
>>   1. Serve environments' details as JSON.
>>   - Browser then render a list of environments.
>>2. Send request with user credentials to the proper environment
>>to login.
>>3. The environment read its deployment.yaml to know the name of
>>itself and set cookies with appending the name to the cookie name.
>>
>> [1] https://github.com/wso2/carb

Re: [Architecture] [APIM][C5] Multi Environment support with API difference for API Manager

[Bhathiya Jayasekara]

On Mon, Nov 6, 2017 at 7:18 PM, Abimaran Kugathasan 
wrote:

> Hi Renuka,
>
> Still, those two images aren't there in mails.
>

Images are visible in the 2nd email.

Thanks,
Bhathiya


>
> What do you mean by "enable new feature like API difference in
> environments"? Checking differences in APIs between environments? I think,
> this feature required only for Publisher.
>
>
>
> On Mon, Nov 6, 2017 at 6:11 PM, Sanjeewa Malalgoda 
> wrote:
>
>>
>>
>> On Mon, Nov 6, 2017 at 4:24 PM, Renuka Fernando  wrote:
>>
>>> Hi,
>>>
>>> The property environmentName is used to append environment name to
>>> cookie and label is used to list down environments in the login page.
>>>
>> Still it is not clear for me. If this is meta data related to all
>> environments, then we should not use environment name here and use
>> something else.
>>
>> Thanks,
>> sanjeewa.
>>
>>>
>>> Thank you
>>>
>>> On 6 November 2017 at 15:34, Pubudu Gunatilaka  wrote:
>>>
 Hi,

 environmentName is used to keep the environment to itself. This is used
 when the server is setting up the cookies by appending the env name to the
 cookies. The env list is to populate the env list.

 Thank you!

 On Mon, Nov 6, 2017 at 2:42 PM, Chamin Dias  wrote:

> Hi Renuka,
>
> Step 7 : "The environment read its deployment.yaml to know the name
> of itself and set cookies..."
>
> So this means the environment name is taken from the environment
> itself. Is there any reason to exclude the environment in the
> provided yaml file?
>
> Thanks.
>
>
> On Mon, Nov 6, 2017 at 2:24 PM, Bhathiya Jayasekara  > wrote:
>
>> Hi Renuka,
>>
>> On Mon, Nov 6, 2017 at 11:27 AM, Renuka Fernando 
>> wrote:
>>
>>> Hi all,
>>>
>>> We are planning to implement new feature "Multi-Environment
>>> Support"[1] for API Manager. The feature allows users to manage
>>> environments through one User Interfaces.
>>>
>>> [image: Inline images 1]
>>> Suppose there are three environments (i.e. three instance of API
>>> manager) currently running in an organization. Users of the API Manager
>>> have log into each environments and work with three different User
>>> Interfaces. The proposed feature allow one User Interface to handle all
>>> environments. User can switch environments and also enable new feature 
>>> like
>>> API difference in environments.
>>>
>>> This is the proposed design of multi-environment support for API
>>> manager.
>>> [image: Inline images 2]
>>>
>>> The UI service in the diagram may be a separate service for User
>>> Interface or another environment itself.
>>>
>>>
>>>1. Browser request login page for the app
>>>(publisher/store/admin) from UI service.
>>>2. Serve the page.
>>>3. Browser call the ConfigurationsAPI
>>>(org.wso2.carbon.apimgt.rest.api.configurations)[2] to get
>>>available environments.
>>>
>>> Since this API is a part of UI service (but not of core), we may
>> need a different name to indicate that.
>>
>>>
>>>1. Read deployment.yaml that contains environments' details
>>>   - Sample deployment.yaml
>>>   -
>>>
>>>   wso2.carbon.apimgt.environments:
>>> environmentName: Default
>>> environments:
>>> - host: dev.sample.com:9292
>>>   loginTokenPath: /login/token
>>>   label: Development
>>>
>>>
>>>
>> What's he dfference between environmentName and environments.label?
>> (If environmentName represents the current environment, souldn't it
>> be one of environments.labels?)
>>
>> Thanks,
>> Bhathiya
>>
>>>
>>>-
>>>
>>>
>>>
>>> - host: prod.sample.com:9292
>>>   loginTokenPath: /login/token
>>>   label: Production
>>>
>>>   1. Serve environments' details as JSON.
>>>   - Browser then render a list of environments.
>>>2. Send request with user credentials to the proper environment
>>>to login.
>>>3. The environment read its deployment.yaml to know the name of
>>>itself and set cookies with appending the name to the cookie name.
>>>
>>> [1] https://github.com/wso2/carbon-apimgt/issues/4690
>>> [2] https://github.com/wso2/carbon-apimgt/pull/4679
>>>
>>>
>>> Appreciate any suggestions.
>>> Thanks
>>>
>>> Best regards
>>>
>>> --
>>> *Renuka Fernando*
>>> Software Engineering Intern | WSO2 Inc
>>>
>>> Email : ren...@wso2.com
>>> Mobile : +94 76 667 8752 <076%20667%208752>
>>> Web : http://wso2.com
>>> 
>>>
>>
>>
>>
>> --
>> *Bhathiya Jayasekara*
>> *Associate Technical Lead,*
>> *WSO2 inc., http://wso2.com *
>

Re: [Architecture] [APIM][C5] Multi Environment support with API difference for API Manager

[Abimaran Kugathasan]

Hi Renuka,

Still, those two images aren't there in mails.

What do you mean by "enable new feature like API difference in
environments"? Checking differences in APIs between environments? I think,
this feature required only for Publisher.



On Mon, Nov 6, 2017 at 6:11 PM, Sanjeewa Malalgoda 
wrote:

>
>
> On Mon, Nov 6, 2017 at 4:24 PM, Renuka Fernando  wrote:
>
>> Hi,
>>
>> The property environmentName is used to append environment name to
>> cookie and label is used to list down environments in the login page.
>>
> Still it is not clear for me. If this is meta data related to all
> environments, then we should not use environment name here and use
> something else.
>
> Thanks,
> sanjeewa.
>
>>
>> Thank you
>>
>> On 6 November 2017 at 15:34, Pubudu Gunatilaka  wrote:
>>
>>> Hi,
>>>
>>> environmentName is used to keep the environment to itself. This is used
>>> when the server is setting up the cookies by appending the env name to the
>>> cookies. The env list is to populate the env list.
>>>
>>> Thank you!
>>>
>>> On Mon, Nov 6, 2017 at 2:42 PM, Chamin Dias  wrote:
>>>
 Hi Renuka,

 Step 7 : "The environment read its deployment.yaml to know the name of
 itself and set cookies..."

 So this means the environment name is taken from the environment
 itself. Is there any reason to exclude the environment in the provided
 yaml file?

 Thanks.


 On Mon, Nov 6, 2017 at 2:24 PM, Bhathiya Jayasekara 
 wrote:

> Hi Renuka,
>
> On Mon, Nov 6, 2017 at 11:27 AM, Renuka Fernando 
> wrote:
>
>> Hi all,
>>
>> We are planning to implement new feature "Multi-Environment
>> Support"[1] for API Manager. The feature allows users to manage
>> environments through one User Interfaces.
>>
>> [image: Inline images 1]
>> Suppose there are three environments (i.e. three instance of API
>> manager) currently running in an organization. Users of the API Manager
>> have log into each environments and work with three different User
>> Interfaces. The proposed feature allow one User Interface to handle all
>> environments. User can switch environments and also enable new feature 
>> like
>> API difference in environments.
>>
>> This is the proposed design of multi-environment support for API
>> manager.
>> [image: Inline images 2]
>>
>> The UI service in the diagram may be a separate service for User
>> Interface or another environment itself.
>>
>>
>>1. Browser request login page for the app (publisher/store/admin)
>>from UI service.
>>2. Serve the page.
>>3. Browser call the ConfigurationsAPI
>>(org.wso2.carbon.apimgt.rest.api.configurations)[2] to get
>>available environments.
>>
>> Since this API is a part of UI service (but not of core), we may need
> a different name to indicate that.
>
>>
>>1. Read deployment.yaml that contains environments' details
>>   - Sample deployment.yaml
>>   -
>>
>>   wso2.carbon.apimgt.environments:
>> environmentName: Default
>> environments:
>> - host: dev.sample.com:9292
>>   loginTokenPath: /login/token
>>   label: Development
>>
>>
>>
> What's he dfference between environmentName and environments.label?
> (If environmentName represents the current environment, souldn't it
> be one of environments.labels?)
>
> Thanks,
> Bhathiya
>
>>
>>-
>>
>>
>>
>> - host: prod.sample.com:9292
>>   loginTokenPath: /login/token
>>   label: Production
>>
>>   1. Serve environments' details as JSON.
>>   - Browser then render a list of environments.
>>2. Send request with user credentials to the proper environment
>>to login.
>>3. The environment read its deployment.yaml to know the name of
>>itself and set cookies with appending the name to the cookie name.
>>
>> [1] https://github.com/wso2/carbon-apimgt/issues/4690
>> [2] https://github.com/wso2/carbon-apimgt/pull/4679
>>
>>
>> Appreciate any suggestions.
>> Thanks
>>
>> Best regards
>>
>> --
>> *Renuka Fernando*
>> Software Engineering Intern | WSO2 Inc
>>
>> Email : ren...@wso2.com
>> Mobile : +94 76 667 8752 <076%20667%208752>
>> Web : http://wso2.com
>> 
>>
>
>
>
> --
> *Bhathiya Jayasekara*
> *Associate Technical Lead,*
> *WSO2 inc., http://wso2.com *
>
> *Phone: +94715478185 <+94%2071%20547%208185>*
> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
> *
> *Twitter: https://twitter.com/bhathiyax
> *
> *Blog: http://movingaheadblog.blogspot.

Re: [Architecture] [APIM][C5] Multi Environment support with API difference for API Manager

[Bhathiya Jayasekara]

Hi Renuka,

On Mon, Nov 6, 2017 at 4:24 PM, Renuka Fernando  wrote:

> Hi,
>
> The property environmentName is used to append environment name to cookie
> and label is used to list down environments in the login page.
>

Stil not clear to me either. Let me ask 2 direct questions.

1) In your sample, you have 2 environments, development and production. But
your environmentName is Default. What does that mean?
2) In case of UI service running separately, what should be the value
of environmentName?
(I guess you don't need that in this case. Please confirm.)

Thanks,
Bhathiya


>
> Thank you
>
> On 6 November 2017 at 15:34, Pubudu Gunatilaka  wrote:
>
>> Hi,
>>
>> environmentName is used to keep the environment to itself. This is used
>> when the server is setting up the cookies by appending the env name to the
>> cookies. The env list is to populate the env list.
>>
>> Thank you!
>>
>> On Mon, Nov 6, 2017 at 2:42 PM, Chamin Dias  wrote:
>>
>>> Hi Renuka,
>>>
>>> Step 7 : "The environment read its deployment.yaml to know the name of
>>> itself and set cookies..."
>>>
>>> So this means the environment name is taken from the environment itself. Is
>>> there any reason to exclude the environment in the provided yaml file?
>>>
>>> Thanks.
>>>
>>>
>>> On Mon, Nov 6, 2017 at 2:24 PM, Bhathiya Jayasekara 
>>> wrote:
>>>
 Hi Renuka,

 On Mon, Nov 6, 2017 at 11:27 AM, Renuka Fernando 
 wrote:

> Hi all,
>
> We are planning to implement new feature "Multi-Environment
> Support"[1] for API Manager. The feature allows users to manage
> environments through one User Interfaces.
>
> [image: Inline images 1]
> Suppose there are three environments (i.e. three instance of API
> manager) currently running in an organization. Users of the API Manager
> have log into each environments and work with three different User
> Interfaces. The proposed feature allow one User Interface to handle all
> environments. User can switch environments and also enable new feature 
> like
> API difference in environments.
>
> This is the proposed design of multi-environment support for API
> manager.
> [image: Inline images 2]
>
> The UI service in the diagram may be a separate service for User
> Interface or another environment itself.
>
>
>1. Browser request login page for the app (publisher/store/admin)
>from UI service.
>2. Serve the page.
>3. Browser call the ConfigurationsAPI
>(org.wso2.carbon.apimgt.rest.api.configurations)[2] to get
>available environments.
>
> Since this API is a part of UI service (but not of core), we may need
 a different name to indicate that.

>
>1. Read deployment.yaml that contains environments' details
>   - Sample deployment.yaml
>   -
>
>   wso2.carbon.apimgt.environments:
> environmentName: Default
> environments:
> - host: dev.sample.com:9292
>   loginTokenPath: /login/token
>   label: Development
>
>
>
 What's he dfference between environmentName and environments.label?
 (If environmentName represents the current environment, souldn't it be
 one of environments.labels?)

 Thanks,
 Bhathiya

>
>-
>
>
>
> - host: prod.sample.com:9292
>   loginTokenPath: /login/token
>   label: Production
>
>   1. Serve environments' details as JSON.
>   - Browser then render a list of environments.
>2. Send request with user credentials to the proper environment to
>login.
>3. The environment read its deployment.yaml to know the name of
>itself and set cookies with appending the name to the cookie name.
>
> [1] https://github.com/wso2/carbon-apimgt/issues/4690
> [2] https://github.com/wso2/carbon-apimgt/pull/4679
>
>
> Appreciate any suggestions.
> Thanks
>
> Best regards
>
> --
> *Renuka Fernando*
> Software Engineering Intern | WSO2 Inc
>
> Email : ren...@wso2.com
> Mobile : +94 76 667 8752 <076%20667%208752>
> Web : http://wso2.com
> 
>



 --
 *Bhathiya Jayasekara*
 *Associate Technical Lead,*
 *WSO2 inc., http://wso2.com *

 *Phone: +94715478185 <+94%2071%20547%208185>*
 *LinkedIn: http://www.linkedin.com/in/bhathiyaj
 *
 *Twitter: https://twitter.com/bhathiyax *
 *Blog: http://movingaheadblog.blogspot.com
 *

>>>
>>>
>>>
>>> --
>>> Chamin Dias
>>> Mobile : 0716097455 <071%20609%207455>
>>> Email : cham...@wso2.com
>>> LinkedIn : https://www.linkedin.com/in/chamindias
>>>
>>>
>>
>>
>> --
>> *Pubudu Gunatilaka*
>> Committ

Re: [Architecture] [APIM][C5] Multi Environment support with API difference for API Manager

[Sanjeewa Malalgoda]

On Mon, Nov 6, 2017 at 4:24 PM, Renuka Fernando  wrote:

> Hi,
>
> The property environmentName is used to append environment name to cookie
> and label is used to list down environments in the login page.
>
Still it is not clear for me. If this is meta data related to all
environments, then we should not use environment name here and use
something else.

Thanks,
sanjeewa.

>
> Thank you
>
> On 6 November 2017 at 15:34, Pubudu Gunatilaka  wrote:
>
>> Hi,
>>
>> environmentName is used to keep the environment to itself. This is used
>> when the server is setting up the cookies by appending the env name to the
>> cookies. The env list is to populate the env list.
>>
>> Thank you!
>>
>> On Mon, Nov 6, 2017 at 2:42 PM, Chamin Dias  wrote:
>>
>>> Hi Renuka,
>>>
>>> Step 7 : "The environment read its deployment.yaml to know the name of
>>> itself and set cookies..."
>>>
>>> So this means the environment name is taken from the environment itself. Is
>>> there any reason to exclude the environment in the provided yaml file?
>>>
>>> Thanks.
>>>
>>>
>>> On Mon, Nov 6, 2017 at 2:24 PM, Bhathiya Jayasekara 
>>> wrote:
>>>
 Hi Renuka,

 On Mon, Nov 6, 2017 at 11:27 AM, Renuka Fernando 
 wrote:

> Hi all,
>
> We are planning to implement new feature "Multi-Environment
> Support"[1] for API Manager. The feature allows users to manage
> environments through one User Interfaces.
>
> [image: Inline images 1]
> Suppose there are three environments (i.e. three instance of API
> manager) currently running in an organization. Users of the API Manager
> have log into each environments and work with three different User
> Interfaces. The proposed feature allow one User Interface to handle all
> environments. User can switch environments and also enable new feature 
> like
> API difference in environments.
>
> This is the proposed design of multi-environment support for API
> manager.
> [image: Inline images 2]
>
> The UI service in the diagram may be a separate service for User
> Interface or another environment itself.
>
>
>1. Browser request login page for the app (publisher/store/admin)
>from UI service.
>2. Serve the page.
>3. Browser call the ConfigurationsAPI
>(org.wso2.carbon.apimgt.rest.api.configurations)[2] to get
>available environments.
>
> Since this API is a part of UI service (but not of core), we may need
 a different name to indicate that.

>
>1. Read deployment.yaml that contains environments' details
>   - Sample deployment.yaml
>   -
>
>   wso2.carbon.apimgt.environments:
> environmentName: Default
> environments:
> - host: dev.sample.com:9292
>   loginTokenPath: /login/token
>   label: Development
>
>
>
 What's he dfference between environmentName and environments.label?
 (If environmentName represents the current environment, souldn't it be
 one of environments.labels?)

 Thanks,
 Bhathiya

>
>-
>
>
>
> - host: prod.sample.com:9292
>   loginTokenPath: /login/token
>   label: Production
>
>   1. Serve environments' details as JSON.
>   - Browser then render a list of environments.
>2. Send request with user credentials to the proper environment to
>login.
>3. The environment read its deployment.yaml to know the name of
>itself and set cookies with appending the name to the cookie name.
>
> [1] https://github.com/wso2/carbon-apimgt/issues/4690
> [2] https://github.com/wso2/carbon-apimgt/pull/4679
>
>
> Appreciate any suggestions.
> Thanks
>
> Best regards
>
> --
> *Renuka Fernando*
> Software Engineering Intern | WSO2 Inc
>
> Email : ren...@wso2.com
> Mobile : +94 76 667 8752 <076%20667%208752>
> Web : http://wso2.com
> 
>



 --
 *Bhathiya Jayasekara*
 *Associate Technical Lead,*
 *WSO2 inc., http://wso2.com *

 *Phone: +94715478185 <+94%2071%20547%208185>*
 *LinkedIn: http://www.linkedin.com/in/bhathiyaj
 *
 *Twitter: https://twitter.com/bhathiyax *
 *Blog: http://movingaheadblog.blogspot.com
 *

>>>
>>>
>>>
>>> --
>>> Chamin Dias
>>> Mobile : 0716097455 <071%20609%207455>
>>> Email : cham...@wso2.com
>>> LinkedIn : https://www.linkedin.com/in/chamindias
>>>
>>>
>>
>>
>> --
>> *Pubudu Gunatilaka*
>> Committer and PMC Member - Apache Stratos
>> Senior Software Engineer
>> WSO2, Inc.: http://wso2.com
>> mobile : +94774078049 <%2B94772207163>
>>
>>
>
>
> --
> *Renuka Fernando*
> Software Engineering Intern | WS

Re: [Architecture] [APIM][C5] Multi Environment support with API difference for API Manager

[Renuka Fernando]

Hi,

Please find missing diagrams (inline images 1 and inline images 2) in my
first reply (trimmed content).

Thank you

On 6 November 2017 at 16:24, Renuka Fernando  wrote:

> Hi,
>
> The property environmentName is used to append environment name to cookie
> and label is used to list down environments in the login page.
>
> Thank you
>
> On 6 November 2017 at 15:34, Pubudu Gunatilaka  wrote:
>
>> Hi,
>>
>> environmentName is used to keep the environment to itself. This is used
>> when the server is setting up the cookies by appending the env name to the
>> cookies. The env list is to populate the env list.
>>
>> Thank you!
>>
>> On Mon, Nov 6, 2017 at 2:42 PM, Chamin Dias  wrote:
>>
>>> Hi Renuka,
>>>
>>> Step 7 : "The environment read its deployment.yaml to know the name of
>>> itself and set cookies..."
>>>
>>> So this means the environment name is taken from the environment itself. Is
>>> there any reason to exclude the environment in the provided yaml file?
>>>
>>> Thanks.
>>>
>>>
>>> On Mon, Nov 6, 2017 at 2:24 PM, Bhathiya Jayasekara 
>>> wrote:
>>>
 Hi Renuka,

 On Mon, Nov 6, 2017 at 11:27 AM, Renuka Fernando 
 wrote:

> Hi all,
>
> We are planning to implement new feature "Multi-Environment
> Support"[1] for API Manager. The feature allows users to manage
> environments through one User Interfaces.
>
> [image: Inline images 1]
> Suppose there are three environments (i.e. three instance of API
> manager) currently running in an organization. Users of the API Manager
> have log into each environments and work with three different User
> Interfaces. The proposed feature allow one User Interface to handle all
> environments. User can switch environments and also enable new feature 
> like
> API difference in environments.
>
> This is the proposed design of multi-environment support for API
> manager.
> [image: Inline images 2]
>
> The UI service in the diagram may be a separate service for User
> Interface or another environment itself.
>
>
>1. Browser request login page for the app (publisher/store/admin)
>from UI service.
>2. Serve the page.
>3. Browser call the ConfigurationsAPI
>(org.wso2.carbon.apimgt.rest.api.configurations)[2] to get
>available environments.
>
> Since this API is a part of UI service (but not of core), we may need
 a different name to indicate that.

>
>1. Read deployment.yaml that contains environments' details
>   - Sample deployment.yaml
>   -
>
>   wso2.carbon.apimgt.environments:
> environmentName: Default
> environments:
> - host: dev.sample.com:9292
>   loginTokenPath: /login/token
>   label: Development
>
>
>
 What's he dfference between environmentName and environments.label?
 (If environmentName represents the current environment, souldn't it be
 one of environments.labels?)

 Thanks,
 Bhathiya

>
>-
>
>
>
> - host: prod.sample.com:9292
>   loginTokenPath: /login/token
>   label: Production
>
>   1. Serve environments' details as JSON.
>   - Browser then render a list of environments.
>2. Send request with user credentials to the proper environment to
>login.
>3. The environment read its deployment.yaml to know the name of
>itself and set cookies with appending the name to the cookie name.
>
> [1] https://github.com/wso2/carbon-apimgt/issues/4690
> [2] https://github.com/wso2/carbon-apimgt/pull/4679
>
>
> Appreciate any suggestions.
> Thanks
>
> Best regards
>
> --
> *Renuka Fernando*
> Software Engineering Intern | WSO2 Inc
>
> Email : ren...@wso2.com
> Mobile : +94 76 667 8752 <076%20667%208752>
> Web : http://wso2.com
> 
>



 --
 *Bhathiya Jayasekara*
 *Associate Technical Lead,*
 *WSO2 inc., http://wso2.com *

 *Phone: +94715478185 <+94%2071%20547%208185>*
 *LinkedIn: http://www.linkedin.com/in/bhathiyaj
 *
 *Twitter: https://twitter.com/bhathiyax *
 *Blog: http://movingaheadblog.blogspot.com
 *

>>>
>>>
>>>
>>> --
>>> Chamin Dias
>>> Mobile : 0716097455
>>> Email : cham...@wso2.com
>>> LinkedIn : https://www.linkedin.com/in/chamindias
>>>
>>>
>>
>>
>> --
>> *Pubudu Gunatilaka*
>> Committer and PMC Member - Apache Stratos
>> Senior Software Engineer
>> WSO2, Inc.: http://wso2.com
>> mobile : +94774078049 <%2B94772207163>
>>
>>
>
>
> --
> *Renuka Fernando*
> Software Engineering Intern | WSO2 Inc
>
> Email : ren...@wso2.com
> Mobile : +94 76 667 8752 <+94%2076%

Re: [Architecture] [APIM][C5] Multi Environment support with API difference for API Manager

[Renuka Fernando]

Hi,

The property environmentName is used to append environment name to cookie
and label is used to list down environments in the login page.

Thank you

On 6 November 2017 at 15:34, Pubudu Gunatilaka  wrote:

> Hi,
>
> environmentName is used to keep the environment to itself. This is used
> when the server is setting up the cookies by appending the env name to the
> cookies. The env list is to populate the env list.
>
> Thank you!
>
> On Mon, Nov 6, 2017 at 2:42 PM, Chamin Dias  wrote:
>
>> Hi Renuka,
>>
>> Step 7 : "The environment read its deployment.yaml to know the name of
>> itself and set cookies..."
>>
>> So this means the environment name is taken from the environment itself. Is
>> there any reason to exclude the environment in the provided yaml file?
>>
>> Thanks.
>>
>>
>> On Mon, Nov 6, 2017 at 2:24 PM, Bhathiya Jayasekara 
>> wrote:
>>
>>> Hi Renuka,
>>>
>>> On Mon, Nov 6, 2017 at 11:27 AM, Renuka Fernando 
>>> wrote:
>>>
 Hi all,

 We are planning to implement new feature "Multi-Environment Support"[1]
 for API Manager. The feature allows users to manage environments through
 one User Interfaces.

 [image: Inline images 1]
 Suppose there are three environments (i.e. three instance of API
 manager) currently running in an organization. Users of the API Manager
 have log into each environments and work with three different User
 Interfaces. The proposed feature allow one User Interface to handle all
 environments. User can switch environments and also enable new feature like
 API difference in environments.

 This is the proposed design of multi-environment support for API
 manager.
 [image: Inline images 2]

 The UI service in the diagram may be a separate service for User
 Interface or another environment itself.


1. Browser request login page for the app (publisher/store/admin)
from UI service.
2. Serve the page.
3. Browser call the ConfigurationsAPI 
 (org.wso2.carbon.apimgt.rest.api.configurations)[2]
to get available environments.

 Since this API is a part of UI service (but not of core), we may need a
>>> different name to indicate that.
>>>

1. Read deployment.yaml that contains environments' details
   - Sample deployment.yaml
   -

   wso2.carbon.apimgt.environments:
 environmentName: Default
 environments:
 - host: dev.sample.com:9292
   loginTokenPath: /login/token
   label: Development



>>> What's he dfference between environmentName and environments.label? (If
>>> environmentName represents the current environment, souldn't it be one
>>> of environments.labels?)
>>>
>>> Thanks,
>>> Bhathiya
>>>

-



 - host: prod.sample.com:9292
   loginTokenPath: /login/token
   label: Production

   1. Serve environments' details as JSON.
   - Browser then render a list of environments.
2. Send request with user credentials to the proper environment to
login.
3. The environment read its deployment.yaml to know the name of
itself and set cookies with appending the name to the cookie name.

 [1] https://github.com/wso2/carbon-apimgt/issues/4690
 [2] https://github.com/wso2/carbon-apimgt/pull/4679


 Appreciate any suggestions.
 Thanks

 Best regards

 --
 *Renuka Fernando*
 Software Engineering Intern | WSO2 Inc

 Email : ren...@wso2.com
 Mobile : +94 76 667 8752 <076%20667%208752>
 Web : http://wso2.com
 

>>>
>>>
>>>
>>> --
>>> *Bhathiya Jayasekara*
>>> *Associate Technical Lead,*
>>> *WSO2 inc., http://wso2.com *
>>>
>>> *Phone: +94715478185 <+94%2071%20547%208185>*
>>> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
>>> *
>>> *Twitter: https://twitter.com/bhathiyax *
>>> *Blog: http://movingaheadblog.blogspot.com
>>> *
>>>
>>
>>
>>
>> --
>> Chamin Dias
>> Mobile : 0716097455
>> Email : cham...@wso2.com
>> LinkedIn : https://www.linkedin.com/in/chamindias
>>
>>
>
>
> --
> *Pubudu Gunatilaka*
> Committer and PMC Member - Apache Stratos
> Senior Software Engineer
> WSO2, Inc.: http://wso2.com
> mobile : +94774078049 <%2B94772207163>
>
>


-- 
*Renuka Fernando*
Software Engineering Intern | WSO2 Inc

Email : ren...@wso2.com
Mobile : +94 76 667 8752
Web : http://wso2.com

___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [APIM][C5] Multi Environment support with API difference for API Manager

[Pubudu Gunatilaka]

Hi,

environmentName is used to keep the environment to itself. This is used
when the server is setting up the cookies by appending the env name to the
cookies. The env list is to populate the env list.

Thank you!

On Mon, Nov 6, 2017 at 2:42 PM, Chamin Dias  wrote:

> Hi Renuka,
>
> Step 7 : "The environment read its deployment.yaml to know the name of
> itself and set cookies..."
>
> So this means the environment name is taken from the environment itself. Is
> there any reason to exclude the environment in the provided yaml file?
>
> Thanks.
>
>
> On Mon, Nov 6, 2017 at 2:24 PM, Bhathiya Jayasekara 
> wrote:
>
>> Hi Renuka,
>>
>> On Mon, Nov 6, 2017 at 11:27 AM, Renuka Fernando  wrote:
>>
>>> Hi all,
>>>
>>> We are planning to implement new feature "Multi-Environment Support"[1]
>>> for API Manager. The feature allows users to manage environments through
>>> one User Interfaces.
>>>
>>> [image: Inline images 1]
>>> Suppose there are three environments (i.e. three instance of API
>>> manager) currently running in an organization. Users of the API Manager
>>> have log into each environments and work with three different User
>>> Interfaces. The proposed feature allow one User Interface to handle all
>>> environments. User can switch environments and also enable new feature like
>>> API difference in environments.
>>>
>>> This is the proposed design of multi-environment support for API manager.
>>> [image: Inline images 2]
>>>
>>> The UI service in the diagram may be a separate service for User
>>> Interface or another environment itself.
>>>
>>>
>>>1. Browser request login page for the app (publisher/store/admin)
>>>from UI service.
>>>2. Serve the page.
>>>3. Browser call the ConfigurationsAPI 
>>> (org.wso2.carbon.apimgt.rest.api.configurations)[2]
>>>to get available environments.
>>>
>>> Since this API is a part of UI service (but not of core), we may need a
>> different name to indicate that.
>>
>>>
>>>1. Read deployment.yaml that contains environments' details
>>>   - Sample deployment.yaml
>>>   -
>>>
>>>   wso2.carbon.apimgt.environments:
>>> environmentName: Default
>>> environments:
>>> - host: dev.sample.com:9292
>>>   loginTokenPath: /login/token
>>>   label: Development
>>>
>>>
>>>
>> What's he dfference between environmentName and environments.label? (If
>> environmentName represents the current environment, souldn't it be one
>> of environments.labels?)
>>
>> Thanks,
>> Bhathiya
>>
>>>
>>>-
>>>
>>>
>>>
>>> - host: prod.sample.com:9292
>>>   loginTokenPath: /login/token
>>>   label: Production
>>>
>>>   1. Serve environments' details as JSON.
>>>   - Browser then render a list of environments.
>>>2. Send request with user credentials to the proper environment to
>>>login.
>>>3. The environment read its deployment.yaml to know the name of
>>>itself and set cookies with appending the name to the cookie name.
>>>
>>> [1] https://github.com/wso2/carbon-apimgt/issues/4690
>>> [2] https://github.com/wso2/carbon-apimgt/pull/4679
>>>
>>>
>>> Appreciate any suggestions.
>>> Thanks
>>>
>>> Best regards
>>>
>>> --
>>> *Renuka Fernando*
>>> Software Engineering Intern | WSO2 Inc
>>>
>>> Email : ren...@wso2.com
>>> Mobile : +94 76 667 8752 <076%20667%208752>
>>> Web : http://wso2.com
>>> 
>>>
>>
>>
>>
>> --
>> *Bhathiya Jayasekara*
>> *Associate Technical Lead,*
>> *WSO2 inc., http://wso2.com *
>>
>> *Phone: +94715478185 <+94%2071%20547%208185>*
>> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
>> *
>> *Twitter: https://twitter.com/bhathiyax *
>> *Blog: http://movingaheadblog.blogspot.com
>> *
>>
>
>
>
> --
> Chamin Dias
> Mobile : 0716097455
> Email : cham...@wso2.com
> LinkedIn : https://www.linkedin.com/in/chamindias
>
>


-- 
*Pubudu Gunatilaka*
Committer and PMC Member - Apache Stratos
Senior Software Engineer
WSO2, Inc.: http://wso2.com
mobile : +94774078049 <%2B94772207163>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [APIM][C5] Multi Environment support with API difference for API Manager

[Chamin Dias]

Hi Renuka,

Step 7 : "The environment read its deployment.yaml to know the name of
itself and set cookies..."

So this means the environment name is taken from the environment itself. Is
there any reason to exclude the environment in the provided yaml file?

Thanks.


On Mon, Nov 6, 2017 at 2:24 PM, Bhathiya Jayasekara 
wrote:

> Hi Renuka,
>
> On Mon, Nov 6, 2017 at 11:27 AM, Renuka Fernando  wrote:
>
>> Hi all,
>>
>> We are planning to implement new feature "Multi-Environment Support"[1]
>> for API Manager. The feature allows users to manage environments through
>> one User Interfaces.
>>
>> [image: Inline images 1]
>> Suppose there are three environments (i.e. three instance of API manager)
>> currently running in an organization. Users of the API Manager have log
>> into each environments and work with three different User Interfaces. The
>> proposed feature allow one User Interface to handle all environments. User
>> can switch environments and also enable new feature like API difference in
>> environments.
>>
>> This is the proposed design of multi-environment support for API manager.
>> [image: Inline images 2]
>>
>> The UI service in the diagram may be a separate service for User
>> Interface or another environment itself.
>>
>>
>>1. Browser request login page for the app (publisher/store/admin)
>>from UI service.
>>2. Serve the page.
>>3. Browser call the ConfigurationsAPI 
>> (org.wso2.carbon.apimgt.rest.api.configurations)[2]
>>to get available environments.
>>
>> Since this API is a part of UI service (but not of core), we may need a
> different name to indicate that.
>
>>
>>1. Read deployment.yaml that contains environments' details
>>   - Sample deployment.yaml
>>   -
>>
>>   wso2.carbon.apimgt.environments:
>> environmentName: Default
>> environments:
>> - host: dev.sample.com:9292
>>   loginTokenPath: /login/token
>>   label: Development
>>
>>
>>
> What's he dfference between environmentName and environments.label? (If
> environmentName represents the current environment, souldn't it be one of
> environments.labels?)
>
> Thanks,
> Bhathiya
>
>>
>>-
>>
>>
>>
>> - host: prod.sample.com:9292
>>   loginTokenPath: /login/token
>>   label: Production
>>
>>   1. Serve environments' details as JSON.
>>   - Browser then render a list of environments.
>>2. Send request with user credentials to the proper environment to
>>login.
>>3. The environment read its deployment.yaml to know the name of
>>itself and set cookies with appending the name to the cookie name.
>>
>> [1] https://github.com/wso2/carbon-apimgt/issues/4690
>> [2] https://github.com/wso2/carbon-apimgt/pull/4679
>>
>>
>> Appreciate any suggestions.
>> Thanks
>>
>> Best regards
>>
>> --
>> *Renuka Fernando*
>> Software Engineering Intern | WSO2 Inc
>>
>> Email : ren...@wso2.com
>> Mobile : +94 76 667 8752 <076%20667%208752>
>> Web : http://wso2.com
>> 
>>
>
>
>
> --
> *Bhathiya Jayasekara*
> *Associate Technical Lead,*
> *WSO2 inc., http://wso2.com *
>
> *Phone: +94715478185 <+94%2071%20547%208185>*
> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
> *
> *Twitter: https://twitter.com/bhathiyax *
> *Blog: http://movingaheadblog.blogspot.com
> *
>



-- 
Chamin Dias
Mobile : 0716097455
Email : cham...@wso2.com
LinkedIn : https://www.linkedin.com/in/chamindias
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [APIM][C5] Multi Environment support with API difference for API Manager

[Bhathiya Jayasekara]

Hi Renuka,

On Mon, Nov 6, 2017 at 11:27 AM, Renuka Fernando  wrote:

> Hi all,
>
> We are planning to implement new feature "Multi-Environment Support"[1]
> for API Manager. The feature allows users to manage environments through
> one User Interfaces.
>
> [image: Inline images 1]
> Suppose there are three environments (i.e. three instance of API manager)
> currently running in an organization. Users of the API Manager have log
> into each environments and work with three different User Interfaces. The
> proposed feature allow one User Interface to handle all environments. User
> can switch environments and also enable new feature like API difference in
> environments.
>
> This is the proposed design of multi-environment support for API manager.
> [image: Inline images 2]
>
> The UI service in the diagram may be a separate service for User Interface
> or another environment itself.
>
>
>1. Browser request login page for the app (publisher/store/admin) from
>UI service.
>2. Serve the page.
>3. Browser call the ConfigurationsAPI 
> (org.wso2.carbon.apimgt.rest.api.configurations)[2]
>to get available environments.
>
> Since this API is a part of UI service (but not of core), we may need a
different name to indicate that.

>
>1. Read deployment.yaml that contains environments' details
>   - Sample deployment.yaml
>   -
>
>   wso2.carbon.apimgt.environments:
> environmentName: Default
> environments:
> - host: dev.sample.com:9292
>   loginTokenPath: /login/token
>   label: Development
>
>
>
What's he dfference between environmentName and environments.label? (If
environmentName represents the current environment, souldn't it be one of
environments.labels?)

Thanks,
Bhathiya

>
>-
>
>
>
> - host: prod.sample.com:9292
>   loginTokenPath: /login/token
>   label: Production
>
>   1. Serve environments' details as JSON.
>   - Browser then render a list of environments.
>2. Send request with user credentials to the proper environment to
>login.
>3. The environment read its deployment.yaml to know the name of itself
>and set cookies with appending the name to the cookie name.
>
> [1] https://github.com/wso2/carbon-apimgt/issues/4690
> [2] https://github.com/wso2/carbon-apimgt/pull/4679
>
>
> Appreciate any suggestions.
> Thanks
>
> Best regards
>
> --
> *Renuka Fernando*
> Software Engineering Intern | WSO2 Inc
>
> Email : ren...@wso2.com
> Mobile : +94 76 667 8752 <076%20667%208752>
> Web : http://wso2.com
> 
>



-- 
*Bhathiya Jayasekara*
*Associate Technical Lead,*
*WSO2 inc., http://wso2.com *

*Phone: +94715478185*
*LinkedIn: http://www.linkedin.com/in/bhathiyaj
*
*Twitter: https://twitter.com/bhathiyax *
*Blog: http://movingaheadblog.blogspot.com
*
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture