Now we're talking... Quick, decisive action. We need more of that!!! Thanks, Jerry.
Now we can incrementally improve how the HTML is generated, in particular, I'd like to find some good examples of creating a single integrated document out of a collection of pod files. The efs-core-docs stuff is (I hope obviously) supposed to be 3 key documents: [-] Admin Guide [-] Dev Guide [-] User Guide What we have now is at least a step in the right direction, because 95% of what I've written this year can be found there. Let's build on this.... On Wed, Sep 15, 2010 at 3:23 PM, Gay, Gerard <[email protected]>wrote: > i modified (via > http://openefs.org/admin/build/menu-customize/primary-links) the 'Read the > Documentation' link to point to http://docs.openefs.org. > > > > hope that helps... it can't hurt! > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Phillip Moore > *Sent:* Wednesday, September 15, 2010 12:13 PM > *To:* EFS core development list > *Subject:* [EFS-dev] openefs.org is in DESPERATE need of change > > > > > > This is why these guys are getting lost... openefs.org is nearly useless > for someone outside our team. The documentation we have links to is ALL > wrong and out of date. SM tells one of their guys to install the software, > and he does the logical thing -- goes to openefs.org and gets totally > misled. > > This is really, completely, and totally embarassing. I need some help > with this, and I'd like to see if we can get some things changed in a hurry. > > > > The entire "EFS Documentation" section is trash. All of it. The docs that > matter are the one's in the git repository, and there is not ONE SINGLE LINK > to them ANYWHERE. Is there a reason we can't just change the "Get the > documentation" link to, gee, I don't know..... point to the actual > documentation? > > > > http://docs.openefs.org > > > > may not look pretty, but it updates everytime we push a change via git. I > do NOT care how pretty it looks, I care about the content. > > > > This website is NOT helping us right now. Absolutely none of us update > it, and it was all set up about a year ago and has grown totally static > since then. > > > > ---------- Forwarded message ---------- > From: *Eberhard Hummel* <[email protected]> > Date: Wed, Sep 15, 2010 at 2:42 PM > Subject: RE: Any progress on NFS in EC2? > To: Phillip Moore <[email protected]> > Cc: David Casper <[email protected]>, Anthony Skipper < > [email protected]> > > The openefs website has a nice link on the top of the home page. “Read the > documentation”.. So I click on that. The subsequent instructions are: > “install openefs as you would any other piece of open source software”. > That’s it…nothing else. So, then I think ok, I’ll download the software and > read the readme. Nothing in there that was helpful either. > > > > It was only by chance that someone forwarded me the doc repo git location. > Suggestion – pdf documentation available for download from the openefs > website. > > > > Why wouldn’t you support nfs4? Its been out since 2006. > > > > > > *From:* Phillip Moore [mailto:[email protected]] > *Sent:* Wednesday, September 15, 2010 11:20 AM > > > *To:* Eberhard Hummel > *Cc:* David Casper; Anthony Skipper > *Subject:* Re: Any progress on NFS in EC2? > > > > > > If I sound frustrated here, it's because I am. > > > > I spent an ENTIRE DAY with your team, basically sitting there, because none > of you bothered to read the pre-requisite documentation that I gave you. In > that document, I very clearly explain that the NFS mounts need to be named: > > > > /vol/efs_dist > > /vol/efs_dev_x_yyy > > > > Where x_yyy is based on the name of the initial dev cell you will be > creating. Furthermore, those mounts must NOT be in /etc/fstab on the EFS > server, as they are not going to be mounted that way on the EFS server, > ever. > > > > I also clearly document the specific UNIX users and groups that must be > created as well as several other things you have to setup before you attempt > this process. > > > > The EFS software does not care what platform you run the database or > NFS/NAS server on. They just provide the database and file services to the > EFS server, so 32bit machines are fine. > > > > However, the initial EFS machine MUST be a 64bit server. As I stated in > the previous mail, we do not have a pre-compiled 32bit /usr/efs tarball. > > > > I have put a great deal of effort into documenting the bootstrap process, > and while I won't claim that the documentation is perfect, please let me > know where I went wrong. > > > > On Wed, Sep 15, 2010 at 1:24 PM, Eberhard Hummel < > [email protected]> wrote: > > When you say bootstrap machine, is this machine going to be part of the efs > topology or is it just used to perform the configuration? > > > > Right now, I have the following topology and want to make sure it is > supported before I go any further > > > > Efs_db_node centos 5_x32 with mysql 5.1.67 > > Efs_nfs_node centos 5_x32 with two exports /mnt/mount1 and /mnt/mount2 > > Efs-server_node centos 5_x32 with the two mounts from above in /etc/fstab > > > > -E > > > > *From:* Phillip Moore [mailto:[email protected]] > *Sent:* Wednesday, September 15, 2010 9:39 AM > *To:* Eberhard Hummel > *Cc:* David Casper; Anthony Skipper > > > *Subject:* Re: Any progress on NFS in EC2? > > > > > > Yes -- you can't do the initial bootstrap on a 32 bit machine (only because > I don't bother to create the bootstrap tarballs on the 32bit platforms). > > > > The initial host on which you perform the bootstrap has to be > x86-64.rhel.5. > > > > ALL of our testing is done on 64 bit platforms, and while there's no reason > to assume that efsd won't work fine on 32bit, that's not how we've been > working. > > > > The assumption here is that a real enterprise is going to be focused on > faster 64bit hardware, and we expect 32bit systems to be second class > citizens. Having said that, 32bit platforms are fully supported, and we > built all of our content for both 32/64. > > > > It's just the initial bootstrapping that requires a 64bit host, and we also > recommend running efsd on a faster 64bit host, too. > > > > On Wed, Sep 15, 2010 at 11:55 AM, Eberhard Hummel < > [email protected]> wrote: > > Hi Phil, > > We're ready to begin a test installation of efs. This is the error I get > when running through the install according to the docs. > > [r...@node Installation]# export > EFS_BOOTSTRAP_CONFIG=/root/efs-bootstrap.conf > [r...@node Installation]# cd /root/efs-core/ > .git/ .gitignore source/ > [r...@node Installation]# cd /root/efs-core/source/ > [r...@node source]# PATH=/usr/efs/bin:$PATH > [r...@node source]# export PATH > [r...@node source]# ./util/efs_bootstrap_install > Building with prefix = /usr/efs > --11:48:39-- > http://ftp.openefs.org/packages/bootstrap/x86-32.rhel.5/usr-efs-devel.tgz > Resolving ftp.openefs.org... 64.50.233.100, 64.50.236.52 > Connecting to ftp.openefs.org|64.50.233.100|:80... connected. > HTTP request sent, awaiting response... 404 Not Found > 11:48:39 ERROR 404: Not Found. > > Unable to download > http://ftp.openefs.org/packages/bootstrap/x86-32.rhel.5/usr-efs-devel.tgz > > Am I missing something? > > -Eberhard > > > > > -----Original Message----- > From: Anthony Skipper [mailto:[email protected]] > Sent: Tuesday, September 07, 2010 2:51 PM > To: Phillip Moore > Cc: David A. Desrosiers; Eberhard Hummel; David Casper; Sy Smythe; > [email protected] > Subject: Re: Any progress on NFS in EC2? > > Hey Phil, > Ok, lots happening finally. Eberhard, one lead platform engineer, found > us a good vmware build that fixes automount and already has NFS platform > scripts he built for another client, but he discovered we were missing the > equivalent ec2 image. He is in the process of recreating it using our > build > tool. > > We should have that done very shortly.(next day or so) will be ready to > re-engage with you by end of week. > > Eberhard and Dave C. Are going to be the permanent engineers on this > platform offering. > > On the business side we have gotten requests from a bunch of folks > including > Duetsche Bank, UBS, and Barclays to provide and overview and demo of > OpenEfs. So the heat is turning up. As part of that work I'm going to > engage Derick Townsend to help put together a slide deck that we can use > for > explaining the offering, benefits, etc. I'll brief him on our side, but > expect that he might have questions and come to you to answer them or > review > the content we are creating. > > If we don't talk sooner, let's at least plan for a call for all of us on > Monday just to make sure things are moving. Let me know what times work > for > you guys. > > This is going to be fun stuff, really looking forward to it. > > Anthony > > Sent from my iPhone > > On Aug 31, 2010, at 9:37 AM, Phillip Moore <[email protected]> > wrote: > > > Anthony -- > > > > Have you guys made any progress on getting NFS to work in the Amazon EC2 > environment? Please let us know if there's anything we can do to help you > get the basic NFS infrastructure working, so that we can revisit getting an > EFS environment up and running for you. > > > > Also, if you'd like to try setting this up an alternate cloud/vm > infrastructure, let us know. > > > > We're basically waiting to hear from you guys at this point, to see what > you want to do next. In the meantime, we're making great progress on > content automation, so we're not exactly sitting still. > > > > Looking forward to getting your team onboard with EFS... > > > > Phil > > > > > > > > _______________________________________________ > EFS-dev mailing list > [email protected] > http://mailman.openefs.org/mailman/listinfo/efs-dev > >
_______________________________________________ EFS-dev mailing list [email protected] http://mailman.openefs.org/mailman/listinfo/efs-dev
