Jeff,
Everyone's network setup can be different and MAAS tries not to be
prescriptive at all but does assume that anyone setting this stuff up
will know a bit about networks. If you are hiding your nodes from the
internet behind your MAAS server then I don't think I'd say that MAAS is
actively doing anything to harm you here, you just need to know to
enable ip_forward and NAT.
As I said in my first reply, I think MAAS can do a bit better at helping
these simple "seed cloud" setups and encourage a scripted installation
that will configure everything for you. This sort of thing would rarely
get used on large installs though as most large users will be a bit more
paranoid about explicitly configuring every tiny detail themselves.
Many of them don't even want MAAS to manage DHCP.
I'll amend the title of this bug now to reflect the fact that we want
MAAS to do some scripted installation scenarios to cover common "small"
use cases.
Thanks for filing this!
** Summary changed:
- nodes can't get out to the internet beyond the maas server by default
+ MAAS could be more helpful with scripted installation scenarios to cover
common network setups
** Also affects: maas
Importance: Undecided
Status: New
** Changed in: maas
Status: New => Triaged
** Changed in: maas
Importance: Undecided => Wishlist
** Changed in: maas (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1304613
Title:
MAAS could be more helpful with scripted installation scenarios to
cover common network setups
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1304613/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
