<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi Merlijn<br>
<br>
Thanks for the feedback. Having 2.3.0 be good on VMware is very
valuable for us. Have these issues been addressed in the RCs?<br>
<br>
Mark<br>
<br>
On 11/22/2017 09:53 AM, Merlijn Sebrechts wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CANiiDBGhSF9MmGL37tp4FX5G+yFhNf4kBbqnhj7SOJgPG4DQaw@mail.gmail.com">
<div dir="ltr">Hi all
<div><br>
</div>
<div><br>
</div>
<div>I've been trying out Juju 2.3-rc1.1 on VMware. Good work on
this, we were finally able to create a functional controller
on our cluster!<br>
</div>
<div><br>
</div>
<div>There are however still a couple of issues I wanted to
bring to your attention. The most serious one is that LXD
support seems to be broken (more than on other non-maas
clouds).<br>
</div>
<div><br>
</div>
<div>Our network setup is the following: We have two networks: a
`primary-network`, running a dhcp server with ddns, and a
`external-network` where users need to add an IP address
manually. This is because public ip's are very scarce in our
organization and we can't just give Juju an entire range.</div>
<div><br>
</div>
<div>Juju seems to handle this pretty well: when a VM is
created, it is attached to both networks, but it only gets an
IP on the `primary-network`. That IP is then also used as
`public-address` for the VM. When a user manually adds a
public IP to the interface, Juju picks that up after a few
minutes, and uses that ip as `public-address`. This is exactly
what we want, good job!</div>
<div><br>
</div>
<div>These are the issues we're still having:</div>
<div>
<ul>
<li>LXD support is broken: with the current network setup,
creating an LXD container on a VM makes the VM
unreachable. If we remove the `external-network` from the
setup, LXD containers never come up.: <a
href="https://bugs.launchpad.net/juju/+bug/1733882"
moz-do-not-send="true">https://bugs.launchpad.net/juju/+bug/1733882</a></li>
</ul>
<ul>
<li>The default constraints VM's differs between EC2/VMware.
Is this intentional? It causes some bundles to fail since
they don't get enough RAM.<br>
</li>
</ul>
<ul>
<li>Firewaller doesn't work: <a
href="https://bugs.launchpad.net/juju/+bug/1732665"
moz-do-not-send="true">https://bugs.launchpad.net/juju/+bug/1732665</a></li>
</ul>
<ul>
<li>cloud-init warns about the cloud being reported as
"EC2": <a
href="https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1731868"
moz-do-not-send="true">https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1731868</a></li>
</ul>
<ul>
<li>When you remove a VM with Juju, the vmdk disk image is
deleted from _all_ datastores, instead of only the one
where juju put the image. This might pose a problem if
people use a datastore as a backup. <a
href="https://bugs.launchpad.net/juju/+bug/1733885"
moz-do-not-send="true">https://bugs.launchpad.net/juju/+bug/1733885</a></li>
</ul>
</div>
<div><br>
</div>
<div><br>
</div>
<div>Kind regards</div>
<div>Merlijn</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
<p><br>
</p>
</body>
</html>