[04:17] hey guys, i redid the interfaces on the server that i oroginally installed maas on. now the subnets no longer reflect that of the maas server nor what I want provisioned on the hosts. how can I make MAAS pick up the new settings? [04:26] hello [04:26] where I can get free cloud? === zz_CyberJacob is now known as CyberJacob === CyberJacob is now known as zz_CyberJacob [07:02] Re my observation from yesterday: It looks like it took quite a while to import CentOS 7 images and until they were available for deployment. A better progress indicator would be a great thing, I already thought MAAS was stuck with something... [07:14] jwitko: so there are a couple different ways to get MAAS to discover subnets. the first way is to register a cluster controller. this will automatically add a fabric to MAAS containing each discovered subnet [07:15] jwitko: the second way is to commission a node. upon commissioning, we will discover the interfaces attached to each node, and discover what subnets (via the DHCP IP address received, if any) [07:18] alexlist: agreed; I'll make sure this is brought up when we decide features for the next MAAS release [07:20] mpontillo, so basically my situation is that I installed a one server maas installation. controller, region controller, etc. all on one piece of hardware. [07:20] After the installation where it discovered the interfaces and set them up as expected I had a change in network requirements [07:21] if you look at this image: http://i.imgur.com/j5jW8Po.png?1 [07:21] I just want to make fabric-1 look identical to fabric-0 (except the subnets staying as they are now) [07:21] so I want to remove the valn-600 and take the subnet attached to it and make it attached to the fabric-1 untagged vlan [07:22] just like fabric-0 [07:22] is there any way for me to do that simply or do I need to uninstall and reinstall maas? [07:25] jwitko: MAAS does not allow you to have a duplicate subnet in MAAS. what you may need to do is use the API to "merge" the two fabrics [07:25] i don't want duplicate subnets [07:25] jwitko: that is, move your VLAN into fabric-0 and then delete fabric-1 [07:26] i want to get rid of that VLAN all together [07:26] notice how fabric-0 has no vlan [07:26] the subnet is attached to the untagged 'item' under fabric [07:26] I just want to make fabric-1 the same way [07:27] jwitko: ah, then you can use the API to move the subnet to the "untagged" VLAN on fabric-1 [07:27] great! how? [07:28] jwitko: after you move the subnet, you can delete the extraneous VLAN. [07:29] jwitko: I don't have the exact syntax handy, but it's something like "maas subnet 172.28.0.0/16 update vlan=" [07:30] mpontillo, there seems to be very little documentation detailing every command and syntax [07:30] jwitko: you may need to do "maas fabrics read" and then "maas vlans read " to get the appropriate IDs [07:30] not criticizing, as I'm loving MAAS, just observing :) [07:30] jwitko: yeah, we do rely a lot on the help available when typing "--help" in a specific CLI context, but I agree that it isn't that user friendly. [07:31] jwitko: no worries; I've actually had updating the docs for that on my TODO list for a long time, just haven't gotten around to it [07:32] jwitko: busy working on UI support for MAAS 2.0 =) https://usercontent.irccloud-cdn.com/file/qt7B5J0s/better-css.png [07:32] jwitko: any of your feedback, good or bad, is much appreciated - thanks for trying MAAS [07:36] * mpontillo needs to head to sleep [07:37] jwitko: looking forward to hearing how your MAAS setup turns out. [07:37] night [07:37] have a good one, thanks for the help! === zz_CyberJacob is now known as CyberJacob === CyberJacob is now known as zz_zz_CyberJacob [12:17] Bug #1559052 opened: MaaS updates IPMI user/password for the node even if the change didn't reflect in IPMI === zz_zz_CyberJacob is now known as CyberJacob [13:17] Bug #1559052 changed: MaaS updates IPMI user/password for the node even if the change didn't reflect in IPMI [13:17] Bug #1559088 opened: [Xenial 2.0] tgt fails to start with tgtadm out of memory error <2.0> [14:18] Bug #1559130 opened: [1.9.1] Parted bug [14:27] Bug #1559130 changed: [1.9.1] Parted bug [14:36] Bug #1559130 opened: [1.9.1] Parted bug [14:57] Bug #1559130 changed: [1.9.1] Parted bug === redelmann is now known as rudi|comida === rudi|comida is now known as redelmann [19:33] hey mpontillo, i'm back :) [19:33] got everything sorted out last night! [19:33] jwitko: great! glad to hear it [19:34] had an additional question however... if I wanted to add an additional DNS entry to my MAAS managed bind dns, how can I do that ? === wolverin_ is now known as wolverineav [21:16] Bug #1559316 opened: [2.0a3 UI] VLAN: This field cannot be null === zimboboy- is now known as zimboboyd [21:38] jwitko: we are doing full support for custom DNS entries in MAAS 2.0... in MAAS 1.x that might be difficult. you could edit /etc/maas/templates/dns/zone.template, but the custom record would appear in all zones [22:07] Bug #1559327 opened: [2.0a3] after upgrade to pre-alpha3, dhcpd is configured incorrectly [22:19] Bug #1559330 opened: [2.0a3 pre] maas-rackd constantely attemps to connect to regiond without stop [22:19] Bug #1559332 opened: [2.0a3] Server VLAN's UI is showing too many vlans [22:31] Bug #1559330 changed: [2.0a3 pre] maas-rackd constantely attemps to connect to regiond without stop [22:31] Bug #1559332 changed: [2.0a3] Server VLAN's UI is showing too many vlans [22:37] Bug #1559330 opened: [2.0a3 pre] maas-rackd constantely attemps to connect to regiond without stop [22:37] Bug #1559332 opened: [2.0a3] Server VLAN's UI is showing too many vlans [23:07] mpontillo, thanks man. how do I regenerate DNS once I edit it ? [23:08] jwitko: easiest way might be to just restart maas-regiond [23:08] jwitko: what you are doing is not really supported =) [23:08] thanks! [23:16] Bug #1559341 opened: Controller listing page lacks rack controller connection status