Hi Eric, First of all, I've created a GitHub ticket [1] for the Vagrant issue you were seeing. I'm not sure that we've ever tested OAE on Vagrant on Windows 7, so we might have to make a couple of small changes to make that work.
If you're just trying to get a feel of what OAE offers, I would also encourage using the QA environment [2]. As this is redeployed every night with the latest code from master, you'll be able to test drive the very latest functionality. However, as Clay indicated, the data on this server does not persist. For more thorough evaluations with persisted data and real faculty/student users, the project is thinking about setting up a new environment that can be used for demo/evaluation tenants. Once that's all done, I would highly encourage using that environment for something like this. However, in the meantime, I'd be happy to set up a University of Toledo tenant on the shared production environment. I would actually prefer that over using the Georgia Tech tenant with Google authentication. I'd like to avoid starting to mix real production data with test data, as that will devalue the quality of the data in there. On top of that, it would also allow you to brand the tenant as University of Toledo and connect it up to your institutional SSO. Obviously, setting up your own environment is fine as well. Let me know how you'd like to proceed. [1] https://github.com/oaeproject/puppet-hilary/issues/65 [2] http://oae.oae-qa0.oaeproject.org Kind regards, Nicolaas On 22 Nov 2013, at 20:46, Clay Fenlason <clay.fenla...@et.gatech.edu> wrote: > Since tenants have to be created by our development team at the > moment, and I'd rather have them continue their development work than set up > a process for handling evaluation tenants for all those who may want to kick > the tires, let me suggest a couple options other than creating > utoledo.oae.com just now, and see if one will suit you. > > If you'd just like to be able to try out the basic functionality, I'd > echo Branden's suggestion that the QA server is a way to go, although > data stored there will not persist beyond a day. > > https://oae.oae-qa0.oaeproject.org > > If you'd like to kick the tires on a tenant that's populated with > actual people, groups and content, I'd point out that the Georgia Tech > tenant has enabled Google logins, anyone can log on there with a > Google account, and from there you can see how the OAE looks with a > little more life breathed into it - though you'd be dealing with a > Georgia Tech-branded experience. > > https://oae.gatech.edu/ > > I hope one of those two options would provide you with the quickest > way to get early evaluation experience you'd need. If you later > decided that you wanted to do a more full-fledged pilot with your own > tenant, skin, etc., we could have a conversation about contributing to > the monthly hosting and maintenance cost we're incurring now, or you > might try to set up your own instance again. But it sounds like it > would be best to postpone that until your faculty have had a chance to > evaluate. > > ~Clay > > On Fri, Nov 22, 2013 at 2:54 PM, Szabo, Eric M <eric.sz...@utoledo.edu> wrote: >> Clay, >> >> Thanks for the quick response. If we could have a tenant setup on the >> shared infrastructure that would be great! I was asked to get this up and >> running for evaluation and we would have to have discussions on hosting our >> own instance after the eval. What information do you need to create a >> tenant for us? I think a good name for the tenant would be utoledo.oae.com >> if that is possible. A few of our faculty are very eager to try the system >> and the quicker I could have a system up for them to try the better. >> >> Thanks, >> >> Eric Szabo, College Information Technology Administrator >> The University of Toledo >> Judith Herb College of Education, >> College of Health Sciences, >> College of Social Justice and Human Service >> Phone: 419.530.2489 >> eric.sz...@utoledo.edu >> >> >> -----Original Message----- >> From: oae-dev-boun...@collab.sakaiproject.org >> [mailto:oae-dev-boun...@collab.sakaiproject.org] On Behalf Of >> oae-dev-requ...@collab.sakaiproject.org >> Sent: Friday, November 22, 2013 1:20 PM >> To: oae-dev@collab.sakaiproject.org >> Subject: oae-dev Digest, Vol 27, Issue 34 >> >> Send oae-dev mailing list submissions to >> oae-dev@collab.sakaiproject.org >> >> To subscribe or unsubscribe via the World Wide Web, visit >> http://collab.sakaiproject.org/mailman/listinfo/oae-dev >> or, via email, send a message with subject or body 'help' to >> oae-dev-requ...@collab.sakaiproject.org >> >> You can reach the person managing the list at >> oae-dev-ow...@collab.sakaiproject.org >> >> When replying, please edit your Subject line so it is more specific than >> "Re: Contents of oae-dev digest..." >> >> >> Today's Topics: >> >> 1. Re: 1 status code: Puppet Catalog could not be properly >> applied. (Clay Fenlason) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Fri, 22 Nov 2013 13:19:35 -0500 >> From: Clay Fenlason <clay.fenla...@et.gatech.edu> >> Subject: Re: [oae-dev] 1 status code: Puppet Catalog could not be >> properly applied. >> To: OAE Development <oae-dev@collab.sakaiproject.org> >> Message-ID: >> <CA+vMKJdeZo5fq9=yJFD06iZ=sswi7l6fgpkawnwdzj_f7wq...@mail.gmail.com> >> Content-Type: text/plain; charset="utf-8" >> >> You may already have thought about this, but I'll ask just in case: if the >> purpose of your evaluation is to familiarize yourself with the use of the >> software (and not, say, your ability to deploy it locally), then have you >> considered the possibility of a tenant on the shared infrastructure rather >> than trying to set up your own infrastructure from scratch? >> >> One of the things that distinguishes the OAE collaboration is that we are >> trying to push past collaboration on mere software development, and move >> into the next stage of pooling resource for a shared, multi-tenant, >> cloud-based infrastructure of services. This shared infrastructure also has >> advantages for end-user collaboration across the institutional boundary, so >> it's not only a matter of minimizing cost: it has a real impact on potential >> use cases. >> >> Any given organization is of course welcome to try to set up and run their >> own instance, but if that approach is being followed more out of force of >> habit than conscious design, I'd like to point out that there's another way >> to think about the problem. >> >> If this is news, here's an old video that may help: >> https://www.youtube.com/watch?v=FBpzcMgp2nQ >> >> ~Clay >> >> >> On Fri, Nov 22, 2013 at 12:57 PM, Szabo, Eric M >> <eric.sz...@utoledo.edu>wrote: >> >>> My college asked me to get a testing environment up and running for >>> evaluation. I am having problems getting the puppet configuration >>> working. I have followed the puppet Hillary instructions off >>> https://github.com/oaeproject/puppet-hilary . I am running VirtualBox >>> 4.2.18 and vagrant 1.3.5. on a clean widows 7 machine. Any help would >>> be greatly appreciated. Here is a copy of the error message I receive. >>> >>> >>> >>> >>> >>> >>> >>> *Eric Szabo, **College Information Technology Administrator* >>> >>> *The University of Toledo* >>> >>> *Judith Herb College of Education, * >>> >>> *College of Health Sciences, * >>> >>> *College of Social Justice and Human Service* >>> >>> *Phone: 419.530.2489 <419.530.2489>* >>> >>> *eric.sz...@utoledo.edu <eric.sz...@utoledo.edu>* >>> >>> >>> >>> _______________________________________________ >>> oae-dev mailing list >>> oae-dev@collab.sakaiproject.org >>> http://collab.sakaiproject.org/mailman/listinfo/oae-dev >>> >>> >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: >> http://collab.sakaiproject.org/pipermail/oae-dev/attachments/20131122/305a35f4/attachment.html >> -------------- next part -------------- >> A non-text attachment was scrubbed... >> Name: not available >> Type: image/png >> Size: 39120 bytes >> Desc: not available >> Url : >> http://collab.sakaiproject.org/pipermail/oae-dev/attachments/20131122/305a35f4/attachment.png >> >> ------------------------------ >> >> _______________________________________________ >> oae-dev mailing list >> oae-dev@collab.sakaiproject.org >> http://collab.sakaiproject.org/mailman/listinfo/oae-dev >> >> >> End of oae-dev Digest, Vol 27, Issue 34 >> *************************************** >> _______________________________________________ >> oae-dev mailing list >> oae-dev@collab.sakaiproject.org >> http://collab.sakaiproject.org/mailman/listinfo/oae-dev > _______________________________________________ > oae-dev mailing list > oae-dev@collab.sakaiproject.org > http://collab.sakaiproject.org/mailman/listinfo/oae-dev _______________________________________________ oae-dev mailing list oae-dev@collab.sakaiproject.org http://collab.sakaiproject.org/mailman/listinfo/oae-dev
