<p dir="ltr">Thinking about doing it this week, actually. (Off work for medical stuff.)</p>
<p dir="ltr">Is an in-place upgrade to stable likely to work once it's officially released?</p>
<p dir="ltr">-Josh</p>
<p dir="ltr">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.</p>
<div class="gmail_quote">On Mar 31, 2014 11:21 AM, "Erik Anderson" <<a href="mailto:erikerik@gmail.com">erikerik@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">(let's move on to a more on-topic discussion) :)<div><br></div><div>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.</div>
<div><br></div><div>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.</div><div><br></div>
<div>My process for testing things was roughly:</div><div><br></div><div>(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.)</div>
<div><br></div><div>---</div><div>- Add trusty vagrant box:</div><div><br></div><div>$ vagrant box add trusty64-2014-03-31 <a href="http://cloud-images.ubuntu.com/vagrant/trusty/current/trusty-server-cloudimg-amd64-vagrant-disk1.box" target="_blank">http://cloud-images.ubuntu.com/vagrant/trusty/current/trusty-server-cloudimg-amd64-vagrant-disk1.box</a></div>
<div><br></div><div>- Edit my default Vagrantfile to use the new box I added</div><div><br></div><div>- fire up the new vagrant box</div><div><br></div><div>$ vagrant up</div><div><br></div><div>- get the vagrant ssh config for this box (for adding to my ~/.ssh/config)</div>
<div><br></div><div>$ vagrant ssh-config</div><div><br></div><div>- add the output of the above command to ~/.ssh/config</div><div><br></div><div>- add "default" (the name of my vagrant box) to my ansible inventory, then run the ansible playbook</div>
<div>---</div><div><br></div><div>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.</div>
<div><br></div><div>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.</div>
<div><br></div><div>Has anyone else tried kicking Trusty's tires yet? If so, what have your experiences been?</div><div><br></div><div>-Erik</div><div><br></div><div><br></div></div>
<br>_______________________________________________<br>
TCLUG Mailing List - Minneapolis/St. Paul, Minnesota<br>
<a href="mailto:tclug-list@mn-linux.org">tclug-list@mn-linux.org</a><br>
<a href="http://mailman.mn-linux.org/mailman/listinfo/tclug-list" target="_blank">http://mailman.mn-linux.org/mailman/listinfo/tclug-list</a><br>
<br></blockquote></div>