On Mon, Dec 6, 2010 at 4:48 PM, Senaka Fernando <[email protected]> wrote:

>
>
> On Mon, Dec 6, 2010 at 2:22 PM, Srinath Perera <[email protected]> wrote:
>
>> How does these work with our governance lifecycles?  Users can click
>> and move things between lifecycles states (e.g. from dev to
>> production)? Then do we move data across registries when that happend?
>> --Srinath
>>
>> On Mon, Dec 6, 2010 at 1:58 PM, Ruwan Linton <[email protected]> wrote:
>> > What we have been following is that, we keep endpoints and any other
>> > environment specific configurations on the registry and have different
>> > registry environments for dev, qa and prod with identical content with
>> the
>> > configuration to the respective values.
>> >
>> > I think the cApp also addresses this, not sure whether it is production
>> > ready, and discovery too :-)
>>
>
> Our suggested approach, as of now, is to use Carbon Studio, and C-Apps,
> IIRC. Remote Links was the proposed model, before this came into being.
>

The idea is you now use Carbon Studio for development and testing, and then
deploy those artifacts into staging, and production environments.

Thanks,
Senaka.

>
> Thanks,
> Senaka.
>
>> >
>> > Ruwan
>> >
>> > On 12/6/10 12:27 PM, Srinath Perera wrote:
>> >>
>> >> can we take old to new endpoint mapping as a input when we migrate and
>> >> use that to fix the endpoints?
>> >> --Srinath
>> >>
>> >> On Mon, Dec 6, 2010 at 12:21 PM, Supun Kamburugamuva<[email protected]>
>> >>  wrote:
>> >>>
>> >>> I would like to know the solutions that we have for moving a
>> development
>> >>> environment ESB configuration to a production environment.
>> >>> The main concern is with the Endpoints.
>> >>> One solution would be to store the Endpoints in the registry and have
>> two
>> >>> registries for dev and prod. When the configuration is migrated from
>> dev
>> >>> to
>> >>> prod the endpoints should not get migrated. But this requires an
>> endpoint
>> >>> configuration change to be done in two places.
>> >>> Any ideas and solutions?
>> >>> Thanks,
>> >>> --
>> >>> Supun Kamburugamuva
>> >>> Technical Lead
>> >>> WSO2 Inc.;  http://wso2.org
>> >>> E-mail: [email protected];  Mobile: +94 77 431 3585
>> >>> Blog: http://supunk.blogspot.com
>> >>>
>> >>> _______________________________________________
>> >>> Carbon-dev mailing list
>> >>> [email protected]
>> >>> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>> >>>
>> >>>
>> >>
>> >>
>> >
>> >
>> > --
>> > Ruwan Linton
>> > Software Architect&  Product Manager, WSO2 ESB; http://wso2.org/esb
>> > WSO2 Inc.; http://wso2.com
>> >
>> > Lean . Enterprise . Middleware
>> >
>> > phone: +1 408 754 7388 ext 51789
>> > email: [email protected]; cell: +94 77 341 3097
>> > blog: http://blog.ruwan.org
>> > linkedin: http://www.linkedin.com/in/ruwanlinton
>> > tweet: http://twitter.com/ruwanlinton
>> >
>> >
>>
>>
>>
>> --
>> ============================
>> Srinath Perera, Ph.D.
>>   Senior Software Architect, WSO2 Inc.
>>   Visiting Lecturer, University of Moratuwa
>>   Member, Apache Software Foundation
>>   Research Scientist, Lanka Software Foundation
>>   Blog: http://srinathsview.blogspot.com/
>>
>> _______________________________________________
>> Carbon-dev mailing list
>> [email protected]
>> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>
>
>
> --
> *Senaka Fernando*
> Associate Technical Lead & Product Manager - WSO2 G-Reg;
> WSO2, Inc.; http://wso2.com
> *
> Member; Apache Software Foundation; http://apache.org
>
> E-mail: senaka AT wso2.com
> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
> Linked-In: http://www.linkedin.com/in/senakafernando
>
> *Lean . Enterprise . Middleware
>
>


-- 
*Senaka Fernando*
Associate Technical Lead & Product Manager - WSO2 G-Reg;
WSO2, Inc.; http://wso2.com*
Member; Apache Software Foundation; http://apache.org

E-mail: senaka AT wso2.com
**P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
Linked-In: http://www.linkedin.com/in/senakafernando

*Lean . Enterprise . Middleware
_______________________________________________
Carbon-dev mailing list
[email protected]
https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to