[14:24] hi, can we use MAAS to manage the VMs created on XenServer? [14:25] I'm planning to deployment OpenStack by using XenServer+MAAS+JUJU. [14:25] But I'm not sure if the VMs can be managed by MAAS. [14:54] What I hope to do do is: 1). boot several VMs(from xenserver) 2). use maas to commission them; and then 3) use them in juju to deploy OpenStack services. [14:55] Can it work? Thanks in advance for any input. [14:56] xen is not supported IMO [14:56] i dont see it in powertypes [15:11] ybaumy, yes, xen is not in powertypes. Can we make the VMs just as baremetal? Manually power on/off the VMs; only let MAAS to bootstrap VMs. [15:12] and let JUJU to use these VMs? [15:13] you could try manual. add the mac address and then add the node [15:13] but i dont know much more about it [15:13] im using vmware [15:14] ybaumy, how are you using VMware with MAAS? [15:14] the same as you inted to use it with xen [15:14] add vcenter nodes + maas commission + juju deploy [15:15] does it work well? [15:15] well there is a bug with disk boot order but besides that yes it works well [15:15] I'm glad to know of it. Thanks. [15:16] I will test it with xen on tomorrow. [15:16] but i have to say .. i dont use it in production yet. so be careful [15:16] :D [15:17] I see. Anyway I got more confidence. Thanks. [15:19] another thing. you cannot add chassis vcenter from maas. you have to use commandline. just a tip if you move that way [15:20] protocol must be https+unverfied if you dont have a valid ssl cert [15:20] thanks for the tips. [15:21] how did you resolve the disk boot order issue or any workaround? [15:21] that was one thing i searched myself to death. [15:21] well i add one disk to commission currently [15:21] and then add the second and third disks for the ceph-osd nodes afterwards [15:22] ok. I will follow the same way:-) [15:22] once the nodes are ready you can modify disks [15:22] i hope devs will fix that soon [15:23] Have you filed a bug? [15:23] yes and another guy [15:23] Do you have the bug# at the moment? [15:24] https://bugs.launchpad.net/maas/+bug/1673726 https://bugs.launchpad.net/maas/+bug/1673724 [15:25] the second from the other guy descibes it better i guess [15:25] cool. Thanks for the sharing. [15:25] i thought it is scsi id related [15:26] because i have always trouble with ids in SUSE [15:27] :-) [18:04] Bug #1674127 opened: delete_authorisation_token is a POST