[00:27] <mup> Bug #1513271 opened: Unable to unmount a filesystem in the UI <storage> <ui> <MAAS:Triaged by ricgard> <https://launchpad.net/bugs/1513271>
[07:33] <nitin_> hello
[07:34] <nitin_> i have set up a MAAS server with 2 nodes as ready
[07:34] <nitin_> but failing while running "juju bootstrap"
[07:35] <nitin_> can anybody help me?
[08:28] <mup> Bug #1513373 opened: Cannot modify the default VLAN for a fabric <MAAS:New> <https://launchpad.net/bugs/1513373>
[08:53] <mup> Bug #1513379 opened: Cannot unset class_type for a fabric once set. <MAAS:New> <https://launchpad.net/bugs/1513379>
[09:29] <mup> Bug #1513391 opened: unexpected hover on subnets page <ui> <MAAS:Triaged by ricgard> <https://launchpad.net/bugs/1513391>
[09:29] <mup> Bug #1513392 opened: radiobuttons should be orange <ui> <MAAS:Triaged by ricgard> <https://launchpad.net/bugs/1513392>
[09:32] <mup> Bug #1513373 changed: Cannot modify the default VLAN for a fabric <MAAS:Invalid> <https://launchpad.net/bugs/1513373>
[09:35] <mup> Bug #1513373 opened: Cannot modify the default VLAN for a fabric <MAAS:Invalid> <https://launchpad.net/bugs/1513373>
[09:59] <mup> Bug #1513373 changed: Cannot modify the default VLAN for a fabric <MAAS:Invalid> <https://launchpad.net/bugs/1513373>
[10:32] <mup> Bug #1513413 opened: IP assignment for devices inconsistent with interfaces on nodes <MAAS:New> <https://launchpad.net/bugs/1513413>
[11:26] <mup> Bug #1513432 opened: Cannot unset a space for a subnet once set <MAAS:New> <https://launchpad.net/bugs/1513432>
[11:50] <mup> Bug #1513432 changed: Cannot unset a space for a subnet once set <MAAS:New> <https://launchpad.net/bugs/1513432>
[11:53] <mup> Bug #1513432 opened: Cannot unset a space for a subnet once set <MAAS:New> <https://launchpad.net/bugs/1513432>
[11:56] <mup> Bug #1513432 changed: Cannot unset a space for a subnet once set <MAAS:Invalid> <https://launchpad.net/bugs/1513432>
[14:27] <mup> Bug #1513379 changed: Cannot unset class_type for a fabric once set. <MAAS:Invalid> <https://launchpad.net/bugs/1513379>
[14:27] <mup> Bug #1513485 opened: Commissioning doesn't update the IP of PXE interface UI, maybe due to lease parser failure <MAAS:Triaged> <https://launchpad.net/bugs/1513485>
[15:30] <mup> Bug #1513506 opened: Storage table row interaction <ui> <MAAS:New for ricgard> <https://launchpad.net/bugs/1513506>
[15:30] <mup> Bug #1513507 opened: Storage table row interaction <ui> <MAAS:New for ricgard> <https://launchpad.net/bugs/1513507>
[15:33] <mup> Bug #1513506 changed: Storage table row interaction <ui> <MAAS:New for ricgard> <https://launchpad.net/bugs/1513506>
[15:33] <mup> Bug #1513507 changed: Storage table row interaction <ui> <MAAS:New for ricgard> <https://launchpad.net/bugs/1513507>
[15:36] <mup> Bug #1513506 opened: Storage table row interaction <ui> <MAAS:New for ricgard> <https://launchpad.net/bugs/1513506>
[15:36] <mup> Bug #1513507 opened: Storage table row interaction <ui> <MAAS:New for ricgard> <https://launchpad.net/bugs/1513507>
[20:06] <stokachu> urthmover:
[20:06] <stokachu> this is what i have so far
[20:06] <stokachu> [15:04] <mpontillo> stokachu: what do you mean when you say "inside" vcenter? yes, you can host the MAAS server on VMware - as long as it has the connectivity it needs to the clusters
[20:06] <stokachu> [15:04] <mpontillo> stokachu: if you're talking about "add hardware > chassis", it should work with 1.8 too
[20:07] <stokachu> [15:05] <mpontillo> stokachu: the thing you need to be careful about is to make sure the VMware user that MAAS uses only has permission to access the nodes you want to make into MAAS-managed nodes. (or use the prefix filter option to restrict it based on the VM name.)
[20:07] <stokachu> [15:06] <mpontillo> stokachu: that should be fine
[20:07] <stokachu> [15:06] <mpontillo> stokachu: I just wanted to give you that word of warning, because when you do probe-and-enlist (aka "Add Hardware > Chassis"), MAAS will reconfigure any VMs it finds through the VMware API so that they PXE boot
[20:07] <stokachu> urthmover: ^
[20:07]  * mpontillo didn't realize there was a discussion going on here, sorry =)
[20:07] <stokachu> mpontillo: nah it started in #juju
[20:07] <urthmover> stokachu: ok I read that on the docs or wiki yesterday about chassis taking over every guest
[20:07] <urthmover> thank you stokachu a bunch
[20:07] <stokachu> urthmover: np
[20:08] <mpontillo> urthmover: ping me if you have questions.
[20:08] <urthmover> mpontillo: in chan or priv?
[20:08] <urthmover> mpontillo: chan is fine with me :)
[20:08] <mpontillo> urthmover: yeah keep it in #maas please so stokachu or others can jump in if needed
[20:10] <stokachu> urthmover: if you have other questions with the OpenStack Installer you can ping me or mmcc (he's in #ubuntu-server)
[20:10] <urthmover> mpontillo: At this point I do not have cli or api access to the vmware vcenter server.  I do have vcenter access using the fatclient.  I am able to build guests, mount disks, etc.  How do I handle the power aspects of using MAAS with my seemly limited access to the hypervisor?
[20:11] <mpontillo> urthmover: hm, it's weird that the fat client would work but not an API client; I thought it used the same API
[20:12] <urthmover> mpontillo: currently I've built a maas/juju environment locally using vmware fusion.  I've had topower on the guests manually throughout the process of installing everything
[20:12] <mpontillo> urthmover: unfortunately, API access is a requirement if you want to use the VMware power control driver. VMware fusion, unfortunately, doesn't work - it does not provide the API. the cheapest version of VMware that supports it is VMware Workstation
[20:12] <mpontillo> urthmover: although I think you could convince the free version of ESXi to work (even without vSphere, etc), given enough time/effort
[20:13] <urthmover> mpontillo: it is wierd, but the hosting provider has attempted to curb my permissions on the environment so that they feel they have some sort of control, to make their support easier.  The dumb part is we are the only tenants on this cluster (but that's another story)
[20:14] <urthmover> mpontillo: if I am unable to gain access to the api, do you think I should build a KVM cluster inside the vmware environment, then build MAAS on top of that...etc
[20:14] <mpontillo> urthmover: well, I don't understand how you could use the fat client to turn on/off machines, but the API wouldn't work. it should be making the same calls. I'd file a support ticket?
[20:14] <mpontillo> urthmover: you could do it that way too. I assume this is just for demo purposes then?
[20:15] <mpontillo> urthmover: if you want to try ESXi, I found this blog post helpful - http://blog.mywarwithentropy.com/2013/12/configuration-esxi-55-from-command-line.html
[20:15] <urthmover> mpontillo: this is testing, that will eventually become production ....I think I'll go down the path of testing api access and demanding it before I clutter up this design with too many embedded hypervisors
[20:16] <mpontillo> urthmover: also, regarding ESXi, I have these commands written in my notes: http://paste.ubuntu.com/13115403/ (I was trying to figure out how to create additional networks for the VMs to use using "bare ESXi")
[20:17] <urthmover> mpontillo: thank you I'll work with those commands and the syntax to see if I have some sort of api access
[20:17] <mpontillo> urthmover: the bottom line for me is, if you can point an official VMware client (such as adding it as a server in Fusion), MAAS should work with it.
[20:18] <urthmover> mpontillo: I hear that and I'm keeping my fingers crossed that I can....give me a few to test and I'll update you and the chan
[20:18] <urthmover> mpontillo: thank you for your time so far btw
[20:18] <mpontillo> urthmover: thanks, good luck.
[20:18]  * urthmover scampers off
[21:31] <mup> Bug #1513506 changed: Storage table row interaction <ui> <MAAS:New for ricgard> <https://launchpad.net/bugs/1513506>