Thinking about doing it this week, actually. (Off work for medical stuff.) Is an in-place upgrade to stable likely to work once it's officially released? -Josh Please pardon the brevity of this electronic missive. It originated from a handheld computing device which has less than ideal data input capabilites. Thank you for understanding. On Mar 31, 2014 11:21 AM, "Erik Anderson" <erikerik at gmail.com> wrote: > (let's move on to a more on-topic discussion) :) > > With the impending release in the next couple weeks of Ubuntu Trusty, the > next LTS release, I thought I'd start playing around with the daily build > isos to see how things are progressing, and with a specific goal of > starting to work out what will need to change with our deployments to adapt > to the new version. > > To do this, I've been using the pre-release Trusty vagrant box. If you are > a linux admin and aren't already using vagrant for test/dev, I *highly* > recommend checking it out. > > My process for testing things was roughly: > > (This is not meant to be a full start-to-finish guide to my workflow, but > rather just a high-level view. If anyone would like more details, I'd be > glad to provide them.) > > --- > - Add trusty vagrant box: > > $ vagrant box add trusty64-2014-03-31 > http://cloud-images.ubuntu.com/vagrant/trusty/current/trusty-server-cloudimg-amd64-vagrant-disk1.box > > - Edit my default Vagrantfile to use the new box I added > > - fire up the new vagrant box > > $ vagrant up > > - get the vagrant ssh config for this box (for adding to my ~/.ssh/config) > > $ vagrant ssh-config > > - add the output of the above command to ~/.ssh/config > > - add "default" (the name of my vagrant box) to my ansible inventory, then > run the ansible playbook > --- > > 90% of my ansible tasks applied cleanly. The only bits that failed were a > couple plays in which I'm manually enabling some Ubuntu Precise repos, > which obviously will fail on this new version. The other bit that failed > was the installation of an updated kernel (which we needed for full docker > support). That play failed for similar reasons as the repo additions did. > As it turns out, the stock kernel provided with Trusty is recent enough to > not need to be updated anyway. > > I branched my ansible repo and fixed the above issues, and then everything > applied cleanly. This was great news, and kudos to Ubuntu for not changing > things so drastically between 12.04 and 14.04. My next step will be > actually deploying our software on Trusty and running through some tests to > make sure things operate as expected. > > Has anyone else tried kicking Trusty's tires yet? If so, what have your > experiences been? > > -Erik > > > > _______________________________________________ > TCLUG Mailing List - Minneapolis/St. Paul, Minnesota > tclug-list at mn-linux.org > http://mailman.mn-linux.org/mailman/listinfo/tclug-list > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20140331/1ad8e66b/attachment.html>