On Wed, Sep 18, 2013 at 5:01 AM, Kasun Gajasinghe <[email protected]> wrote:
> > Meeting notes - > > We got to know how AS receive the webapp artifacts. This happens by using > a central GIT repository. AppFactory checks in the webapp artifacts to that > repository, and the AS nodes updates themselves. AF won't be using the AS > UIs but the WebappAdmin service. WebappAdmin will be used to make a default > webapp of a versioned webapp. > > Since AF directly checks-in the artifacts, AF have to take care of webapp > versioning. AF need to handle things like proper file naming (with #), > calling webapp admin service etc. > > -When a given versioned webapp is set to default, what AS currently do is > to rename that webapp to the webapp group name. For ex, we rename > webapp#version1.war to webapp.war. But in this process we do not keep the > original context (webapp#version1) of the versioned webapp. This is not > correct. > I don't think we can say this is incorrect instead as we identified during the initial stages these are different strategies on default version management. Strategy 1 - Without maintaining duplicates rename the app according to current default version ( We have implemented this) Strategy 2 - Without renaming make a duplicate app when changing the current default version ( It seems AF needs this) We also can find smiler strategies for meta data handling of the default version (specially important for consistence BAM monitoring ) Strategy 1 - Once the QoS meta data assigned to a default version by a user those will remains same even we change the default version ( in other words app is not carrying it's meta data when becoming a default version instead meta data setting of old default version will apply to new one) Strategy 2 - When default version changes QoS meta data also get updated according to the QoS of new default version ( in other words app is carrying it's meta data when becoming a default version). Strategy 3 - ................ Supun, Please don't remove existing logic instead refactor existing code so that user/we can configure to pick up what ever the required strategy on each subject. Thanks ! > So, we decided to keep the original context of the versioned webapp as > well in addition to the default version. > > - The above is done by keeping two copies of the same webapp (the default > webapp *webapp.war*, and the versioned webapp webapp#version1.war). These > two webapps will be independent, so there will be separate sessions etc. As > we found out, this is not a problem for AppFactory scenario. > > - If the firstly uploaded webapp in a webapp group has a version already, > then make that the default version. > > Noticed some UI issues - > > - If there is no default webapp, then the "Context" column in the webapp > list page displays the context WITH the version. ex. webapp#version1. This > should not be the case. > > We need to meet again to discuss things further. > > > On Wed, Sep 18, 2013 at 2:49 PM, Google Calendar < > [email protected]> wrote: > >> more details >> »<https://www.google.com/calendar/event?action=VIEW&eid=Z2ZsZWExcTNidDhpaDRybXNqbGhqYnFiYjAga2FzdW5nQHdzbzIuY29t&tok=MTUjc3VwdW5tQHdzbzIuY29tMWI0NjRmYjhjZjE2OGRiODg2ZGE2ZDEwMzBmMDU5ZmI0YTRlMzAwYQ&ctz=Asia/Colombo&hl=en> >> Next steps to aPaaS Application version support and rest of the >> integration points from AS side >> *When* >> ********Wed Sep 18, 2013 3pm – 4pm Colombo >> *Where* >> LK 5th Floor Meeting Room - Garage >> (map<http://maps.google.lk/maps?q=LK+5th+Floor+Meeting+Room+-+Garage&hl=en> >> ) >> *Calendar* >> [email protected] >> *Who* >> • >> Supun Malinga - organizer >> • >> Kasun Gajasinghe >> • >> Sagara Gunathunga >> • >> Piyum Fernando >> • >> Geeth Munasinghe >> • >> Afkham Azeez >> • >> Sameera Perera >> • >> Amila Maha Arachchi >> • >> Shariq Muhammed >> • >> Johann Nallathamby >> >> Going? >> ***Yes<https://www.google.com/calendar/event?action=RESPOND&eid=Z2ZsZWExcTNidDhpaDRybXNqbGhqYnFiYjAga2FzdW5nQHdzbzIuY29t&rst=1&tok=MTUjc3VwdW5tQHdzbzIuY29tMWI0NjRmYjhjZjE2OGRiODg2ZGE2ZDEwMzBmMDU5ZmI0YTRlMzAwYQ&ctz=Asia/Colombo&hl=en>- >> Maybe<https://www.google.com/calendar/event?action=RESPOND&eid=Z2ZsZWExcTNidDhpaDRybXNqbGhqYnFiYjAga2FzdW5nQHdzbzIuY29t&rst=3&tok=MTUjc3VwdW5tQHdzbzIuY29tMWI0NjRmYjhjZjE2OGRiODg2ZGE2ZDEwMzBmMDU5ZmI0YTRlMzAwYQ&ctz=Asia/Colombo&hl=en>- >> No<https://www.google.com/calendar/event?action=RESPOND&eid=Z2ZsZWExcTNidDhpaDRybXNqbGhqYnFiYjAga2FzdW5nQHdzbzIuY29t&rst=2&tok=MTUjc3VwdW5tQHdzbzIuY29tMWI0NjRmYjhjZjE2OGRiODg2ZGE2ZDEwMzBmMDU5ZmI0YTRlMzAwYQ&ctz=Asia/Colombo&hl=en> >> * **more options >> »<https://www.google.com/calendar/event?action=VIEW&eid=Z2ZsZWExcTNidDhpaDRybXNqbGhqYnFiYjAga2FzdW5nQHdzbzIuY29t&tok=MTUjc3VwdW5tQHdzbzIuY29tMWI0NjRmYjhjZjE2OGRiODg2ZGE2ZDEwMzBmMDU5ZmI0YTRlMzAwYQ&ctz=Asia/Colombo&hl=en> >> >> Invitation from Google Calendar <https://www.google.com/calendar/> >> >> You are receiving this email at the account [email protected] because you >> are subscribed for reminders on calendar [email protected]. >> >> To stop receiving these notifications, please log in to >> https://www.google.com/calendar/ and change your notification settings >> for this calendar. >> > > > > -- > *Kasun Gajasinghe* > Software Engineer; > WSO2 Inc.; http://wso2.com > > > , > *email: **kasung AT spamfree wso2.com > > > ** cell: **+94 (77) 678-0813* > *linked-in: *http://lk.linkedin.com/in/gajasinghe > > > * > * > *blog: **http://kasunbg.org* <http://kasunbg.org> > > > * > twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg> > > > * > * > > > > -- > *Kasun Gajasinghe* > Software Engineer; > WSO2 Inc.; http://wso2.com > > > , > *email: **kasung AT spamfree wso2.com > > > ** cell: **+94 (77) 678-0813* > *linked-in: *http://lk.linkedin.com/in/gajasinghe > > > * > * > *blog: **http://kasunbg.org* <http://kasunbg.org> > > > * > twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg> > > > * > * > -- Sagara Gunathunga Senior Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services; http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
