@James, So, most of the test openstack deployments with MAAS are done in a flat network. This, means that:
1. You at least have One Fabric, One "VLAN", One Subnet. 2. You have the Rack Controller NIC connected with an IP of the subnet above (which means that the NIC is in fabric/vlan above). For example: Rack Controller: - eth0 - fabric-0 - 'untagged' - 192.168.1.1 Subnets (tab): - fabric-0 - 'untagged' - 192.168.1.0/24 That said, to enable DHCP in the WebUI, you need to: 1. Click in 'Subnets' tab 2. Click in the 'untagged' VLAN for 'fabric-0' 3. Click on 'Take Action > Provide DHCP'. 4. Input parameters, i.e.: 4.1. Primary rack controller 4.2. Dynamic range/gateway (only if you don't have one already created for subnet 192.168.1.0/24). To enable DHCP via the CLI (if you already have a *dynamic* range created for the subnet): maas sysadmin vlan update fabric-0 untagged dhcp_on=True primary_rack=sf2-maas00 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1649397 Title: maas-dhcpd.service won't start To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1649397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
