<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 08/01/15 03:52, Sergio Schvezov
wrote:<br>
</div>
<blockquote
cite="mid:67173ff1-c174-4ef9-956a-d2c859ae1489@canonical.com"
type="cite">On miércoles 7 de enero de 2015 19h'23:09 ART, Ben
Howard wrote:
<br>
<blockquote type="cite">In looking at the problems with creating
VM images for developers, there are a large number that use
Virtualbox (i.e Vagrant) or VMware Fusion on their shiny Macs.
About a year ago we released Vagrant images that quickly became
extremely popular, with over 1M downloads. <br>
While working on enabling VMware and Virtualbox, it became
apparent that we run a real risk of having a dozen downloads if
we are not careful. What I would like to propose is that we have
the standard "core", "cloud", and a "developer" image. <br>
The idea behind the developer image is that we would put all the
stuff that makes development easy and target the
"non-production" environments. <br>
My initial proposed requirements are:
<br>
SSH enabled by default
<br>
Vagrant user defined
<br>
/home/vagrant exists
<br>
password is locked
<br>
defined a sudoer
<br>
</blockquote>
<br>
SSH enabled by default shouldn't be a problem. I don't think we
have a user management story/solution yet with these read only
images.
<br>
<br>
<blockquote type="cite">Packages installed:
<br>
virtualbox-dkms modules pre-built
<br>
</blockquote>
<br>
I guess this can go into a specific "device" channel.
<br>
<br>
<blockquote type="cite">open-vm-tools
<br>
virtualbox-guest-utils
<br>
ssh-import-id
<br>
Thoughts? </blockquote>
<br>
Can these be put into a framework?
<br>
<br>
<br>
</blockquote>
<br>
<font size="+1"><font face="Ubuntu">We agreed to have a framework
that provides the "comfortable" set of tools together with
tracing and debugging utilities. We called it "comfy" or
"humanity", the expectation is it would be large (huge!) but
only relevant on machines that a human finds themselves on.<br>
<br>
So to be clear - NO to a separate developer image, YES to a
single developer-friendly framework for all those commands.<br>
<br>
Turning SSH on should be handled by boot-time parameterisation
via cloud-init.<br>
<br>
Mark<br>
</font></font>
</body>
</html>