Re: [aerogear-dev] UPS OpenShift cartridge 0.10.1 test results

On Mon, Mar 17, 2014 at 8:56 PM, Farah Juma <fjuma(a)redhat.com&gt; wrote: > > > From: "Matthias Wessendorf" <matzew(a)apache.org&gt; > > To: "Farah Juma" <fjuma(a)redhat.com&gt; > > Cc: "AeroGear Developer Mailing List" <aerogear-dev(a)lists.jboss.org&gt; > > Sent: Monday, March 17, 2014 2:55:01 PM > > Subject: Re: [aerogear-dev] UPS OpenShift cartridge 0.10.1 test results > > > > On Mon, Mar 17, 2014 at 7:27 PM, Farah Juma <fjuma(a)redhat.com&gt; wrote: > > > > > > > > > From: "Matthias Wessendorf" <matzew(a)apache.org&gt; > > > > To: "AeroGear Developer Mailing List" <aerogear-dev(a)lists.jboss.org > > > > > > Cc: "Farah Juma" <fjuma(a)redhat.com&gt; > > > > Sent: Monday, March 17, 2014 1:14:05 PM > > > > Subject: Re: [aerogear-dev] UPS OpenShift cartridge 0.10.1 test > results > > > > > > > > On Mon, Mar 17, 2014 at 6:10 PM, Karel Piwko <kpiwko(a)redhat.com&gt; > wrote: > > > > > > > > > Hey, > > > > > > > > > > status looks like: > > > > > > > > > > * Integration tests - passed > > > > > * UI tests - failed - UI glitches in FF > > > > > > > > > > > > > known problem; not sure - but there might be already a ticket for it > > > > > > > > > > > > > * SP tests - passed > > > > > * Migration tests - failed - scheme problems. > > > > > > > > > > > > > possible - we might have changed the data model between 0.9.x and > 0.10.x > > > > > > Interesting, this would cause issues with modifying existing > data/adding > > > new data. As Karel noted on AGPUSH-563, it looks like we would need a > > > migration strategy for DB schema changes. > > > > > > > yep - I was thought that's part of the upgrade work; but we can file a > > ticket to explicitly cover this > > That would be good. The database part of the upgrade is currently handled > by the MySQL cartridge's "post_restore" action hook - this just restores > the database to whatever it was before and doesn't handle schema changes: > > > https://github.com/openshift/origin-server/blob/master/cartridges/openshi... ok > > > Once the necessary MySQL commands for migrating data from 0.9.x to 0.10.x > are defined, we could try adding them to the AeroGear cartridge's > "post_restore" action hook. >

With "necessary MySQL commands" you mean those that take care of the schema changes? I think generally having a migration script for the schema is a nice thing to have, regardless of OpenShift. Once we are closer to our 1.0.0 that's something we have to have. Are you planing on adding these necessary MySQL commands (assuming they are relevant for taking care of schema changes ;-)) for our cartridge? Or should we just track that requirement in a JIRA for now ? -Matthias > > > > > > > > > > > > > > Migration is not a part of cartridge but I guess that UI should be > > > fixed. > > > > > > > > > > > > > It's minor, not sure we should really stop the process; especially > the > > > UPS > > > > is now on staging/hold since one entire week > > > > > > > > > > > > > > > > > > I have filled following bugs: > > > > > * https://issues.jboss.org/browse/AGPUSH-562 > > > > > * https://issues.jboss.org/browse/AGPUSH-563 > > > > > > > > > > Note, as for Firefox DNS cache, just set > > > > > network.dnsCacheExpirationGracePeriod=0 in about:config. > > > > > > > > > > Karel > > > > > _______________________________________________ > > > > > aerogear-dev mailing list > > > > > aerogear-dev(a)lists.jboss.org > > > > > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > > > > > > > > > > > > > > > > > -- > > > > Matthias Wessendorf > > > > > > > > blog: http://matthiaswessendorf.wordpress.com/ > > > > sessions: http://www.slideshare.net/mwessendorf > > > > twitter: http://twitter.com/mwessendorf > > > > > > > > > > > > > > > -- > > Matthias Wessendorf > > > > blog: http://matthiaswessendorf.wordpress.com/ > > sessions: http://www.slideshare.net/mwessendorf > > twitter: http://twitter.com/mwessendorf > > > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf