Hi Vanson, On Fri, Apr 25, 2014 at 10:11 PM, Vanson Lim <v...@cisco.com> wrote:
> I had a question after looking at the revised diagram. > > Between the events "publish instance started event to Cloud Controller" > ->"start servers" > > Is the git repo pulled down and available to use to derive config used to > start server? This could be useful for delivering configuration using the > ADC that is used to configure the server before starting it. This is a > little bit different from the model I've seen where artifacts are hot > deployed into servers after it starts. > > The ADC artifacts could be used during the start server event to > > 1) provide config for bootstrapping the install ou f the server binaries > > 2) Post install configure to complete server setup > 3) deploying server run time config, like application policies > > Interesting thought. Currently, the server startup configuration is provided through an instance acting as a Puppet Master [1], at the time of instance start up. The git repository is used to synchronize application artifacts (a php application in case of a php instance, etc.) across a cluster. A user can upload the artifacts to the git repository, configure a git hook so that artifacts are updated on the fly, across the cluster [2]. [1]. https://cwiki.apache.org/confluence/display/STRATOS/4.0.0+Configuring+Puppet+Master [2]. https://cwiki.apache.org/confluence/display/STRATOS/4.0.0+Automated+Deployment+Synchronization > > -Vanson > > > > > > On 4/24/14, 4:58 AM, Praneesha Chandrasiri wrote: > > Did a correction in adding the recursion for "publish stats to CEP". > > Please find the revised diagram attached. > > > On Thu, Apr 24, 2014 at 2:04 PM, Praneesha Chandrasiri<pranee...@wso2.com> > <pranee...@wso2.com>wrote: > > > Hi Rekha, > > Thanks for reviewing. > > Attached is the revised diagram with the changes included as discussed. > > > On Thu, Apr 24, 2014 at 10:32 AM, Reka Thirunavukkarasu <r...@wso2.com> > <r...@wso2.com>wrote: > > > Hi > > I have gone through it..It needs few modification as following after the > Member started Event to Instance Status topic. > > Member Started Event --> start servers --> wait for port Active --> > publish instance activated event > | > | > --> artifact updated event > --> start health checker > > Thanks, > Reka > > > On Thu, Apr 24, 2014 at 9:57 AM, Mariangela Hills <mariang...@wso2.com> > <mariang...@wso2.com>wrote: > > > Thanks, Praneesha! > > Can someone please let us know whether this diagram is ok. > > Regards, > Mariangela > > > > > *--* > Mariangela Hills > Senior Technical Writer > > *WSO2, Inc.*lean.enterprise.middleware. > m: +94 773 500185 > w: http://wso2.com > <http://wso2.com/events/> <http://wso2.com/events/> > > > > On Thu, Apr 24, 2014 at 9:02 AM, Praneesha Chandrasiri <pranee...@wso2.com> > wrote: > > > Hi Mari, > > Please find the $subject attached. > > Also please let me know if any improvements are required. > > -- > Thanks & Best Regards, > *Praneesha Chandrasiri* > *Technical Writer* > *WSO2 Inc. * > *Mobile: +(94) 718156888 <%2B%2894%29%20718156888>* > *E-mail: pranee...@wso2.com <pranee...@wso2.com> <pranee...@wso2.com>* > > > > -- > Reka Thirunavukkarasu > Software Engineer, > WSO2, Inc.:http://wso2.com, > Mobile: +94776442007 > > > -- > Thanks & Best Regards, > *Praneesha Chandrasiri* > *Technical Writer* > *WSO2 Inc. * > *Mobile: +(94) 718156888 <%2B%2894%29%20718156888>* > *E-mail: pranee...@wso2.com <pranee...@wso2.com> <pranee...@wso2.com>* > > > > >
