Oct 032013
 

Learnt from the mailing list that I should not export mounting point as a brick directly, instead I should create a sub-directory under the mounting point and take it as brick, this will make life much easier later on whenever you have to do migration or re-organization (like changing replica).

Developers of GlusterFS are thinking of retiring replace-brick, from the mailing list I can see they have good point to do so (especially existing codes for replace-brick is too bad to be improved :P), however, as a (sort of) ops guy, I still prefer they can keep it since it makes ops’ life much more easier, but obviously they don’t quite agree with all requests/challenges to keep it. Anyway, it seems life will not end, it will just become a little bit troublesome, and if this is the trade-off for stability and/or performance, I’m fine with it.

Oct 032013
 

I think it was in year 2005 or 2006 that I migrated everything from CVS to SVN, and it was the time that my company was doing that as well. Now I’m migrating to git, and of course, my current company is doing the same thing :P.

Guess everybody knows the reason … let’s say it’s offline support, that you don’t have to connect to sever to do commit. Further more, subversion does not work well on VirtualBox’s shared folder, while git has no problem at all, I guess people like me who needs to work on both *ix and Windows platforms have to have this kind of support.

And this is the time to see how many projects I have, WeirdBox is a great thing to keep thinking of I’ve play with the codes for several years, aws-browser is obviously another thing to keep thinking of it’s my first app on iOS and AWS (EC2 and S3), XMPP Mail Alert has to be migrated as I’m using it at this moment (for a friend’s web site). I cannot recall anything else but will post here if I find any.

And I’m using github, because of feel like safe? At least it’s not that vulnerable as other small players.