<tt><font size=2>> From: Monty Taylor <monty@inaugust.com></font></tt><br><tt><font size=2>> To: Sylvain Bauza <sbauza@redhat.com>,
"OpenStack Development <br>> Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org></font></tt><br><tt><font size=2>> Date: 09/28/2015 09:54 AM</font></tt><br><tt><font size=2>> Subject: Re: [openstack-dev] Compute API (Was
Re: [nova][cinder] how<br>> to handle AZ bug 1496235?)</font></tt><br><tt><font size=2>></font></tt><br><tt><font size=2>> ...<br>> Specifically, I want "nova boot" to get me a VM with an
IP address. I <br>> don't want it to do fancy orchestration - I want it to not need fancy
<br>> orchestration, because needing fancy orchestration to get a VM on
a <br>> network is not a feature.<br>> <br>> I also VERY MUCH do not want to need Heat to get a VM. I want to use
<br>> Heat to do something complex. Getting a VM is not complex. It should
not <br>> be complex. What it's complex and to the level of needing Heat, we've
<br>> failed somewhere else.<br>> <br>> Also, people should stop deploying clouds that require people to use
<br>> floating IPs to get basic internet access. It's a misuse of the construct.<br>> <br>> Public Network "ext-net" -> shared / directly attachable<br>> Per-tenant Network "private" -> private network, not
shared, not routable<br>> <br>> If the user chooses, a router can be added with gateway set to ext-net.<br>> <br>> This way:<br>> <br>> nova boot --network=ext-net -> vm dhcp'd on the public network<br>> nova boot --network=private -> vm dhcp'd on the private network<br>> nova floating-ip-attach -> vm gets a floating
ip attached to their <br>> vm from the ext-net network<br>> <br>> All of the use cases are handled, basic things are easy (boot a vm
on <br>> the network works in one step) and for the 5% of cases where a floating
<br>> IP is actually needed (a long-lived service on a single vm that wants
to <br>> keep the IP and not just a DNS name across VM migrations and isn't
using <br>> a load-balancer) can use that.<br>> <br>> This is, btw, the most common public cloud deployment model.<br>> <br>> Let's stop making things harder than they need to be and serve our
users.<br></font></tt><br><tt><font size=2>As an operator, +1</font></tt><br><br><tt><font size=2>Mike</font></tt><br><br><BR>