[02:25] can only an admin user compose a new machine within a pod? [02:27] I'm running 2.3.0 and just created a Virsh (KVM) Pod, I was hoping that I would be able to let non-admin users compose machines... but it looks like only admin users are allowed... does this sounds accurate? === frankban|afk is now known as frankban [12:15] Bug #1746980 opened: storage /disk not showing node change status commising to testing [12:22] Bug #1746980 changed: storage /disk not showing node change status commising to testing [12:28] Bug #1746980 opened: storage /disk not showing node change status commising to testing [15:31] Bug #1678362 opened: Support ZFS root and/or ZFS only installs [16:34] hi .. [16:35] i use openstack-telemetry charms .. 2 services got problem (mongodb & neutron-gateway) .. juju status output : http://paste.ubuntu.com/26506527/ [16:36] mongodb log output: https://paste.ubuntu.com/26506520/ [16:36] neutron-gateway: https://paste.ubuntu.com/26506512/ [16:39] ejat: maybe #ubuntu-server is the best place for openstack issues ? [16:42] ok noted roaksoax .. sorry [17:04] I asked earlier and didn't see a response, so I'll try again [17:05] can only an admin user compose a new machine within a pod? [17:05] I'm running 2.3.0 and just created a Virsh (KVM) Pod, I was hoping that I would be able to let non-admin users compose machines... but it looks like only admin users are allowed... does this sounds accurate? === frankban is now known as frankban|afk [20:11] Where's the TFTP root dir? [20:14] /var/lib/maas/boot-resources/current? [20:47] rora: there's no tftproot dir [20:47] klj1218: uhmmm let me investigate [20:48] rora: well, there is and there's not [20:48] rora: the config is provided dynamically [20:48] roaksoax : thanks [20:50] klj1218: ha! just saw your email too [20:51] roaksoax: :-) [21:06] klj1218: ok, are you doing this via the UI?, or API ? [21:06] UI ... just tested with admin user via cli, was going to test non-admin user via cli [21:07] klj1218: so a normal user cannot *compose* [21:07] klj1218: but it *can* allocate [21:07] klj1218: composition doesn't mean ownership [21:07] roaksoax: ok, from UI or CLI [21:07] but allocation does [21:07] klj1218: cli [21:08] e.g. maas normal machines allocate cpu_count=4 mem=4096 [21:08] that would work [21:09] maas normal pod compose <....> # this won't work [21:09] so, it seems the reason we did that is because "compose" (manual composition) doens't imply ownership, where as 'allocation' does [21:10] Bug #1747080 opened: commissioning fails during 00-maas-01-lshw [21:12] klj1218: but it seems that the problme with that, is that here';s no UI compatible way to do so [21:12] roaksoax: but you cant allocate from a POD using the CLI correct? [21:12] klj1218: yes you can [21:14] roaksoax: ok, going to search for the CLI reference for that now [21:14] klj1218: maas test machines allocate pod=pure-goat cpu_count=X mem=Y [21:15] klj1218: maas test machines allocate pod=pure-goat cpu_count=X mem=Y # this would work [21:15] klj1218: maas test pod compose # this wont work [21:17] roaksoax: ok, yeah that will just allocate on the the already created machines [21:18] roaksoax: so i still have to first "compose" the machines, then I can turn it over to a non-admin user to allocate/deploy [21:18] klj1218: not necessarily [21:18] klj1218: maas test machines allocate pod_type=kvm [21:19] roaksoax: I just did this: maas klj machines allocate pod=dev01 cpu_count=4 mem=16384 [21:19] err [21:19] roaksoax: this allocated one of the systems that I had already composed from the Pod [21:20] roaksoax: it didn't create a new machine and allocate it to the klj non-admin user [21:20] klj1218: that's correct 'allocation' will always first look for what you currently have depending on the constraints that you pass [21:20] if you don't find anything, it will atomatically compose a machine [21:22] roaksoax: ok, yup I just tried to allocate a machine with 8 vpus and it did indeed create a new machine [21:26] klj1218: ok, that said, is there any specific requirement that would want you to have this via the UI ? [21:27] roaksoax: I'm just trying to turn over ownership of a Pod to some users who don't have admin rights... I don't really want to give them admin rights, so if I only stick to the UI that means I have to pre-compose the machines before they can allocate/deploy them [21:28] roaksoax: but with the CLI, I can now just turn over the Pod to them and they can allocate from it [21:28] klj1218: ok, great, you are unblocked then [21:28] roaksoax: for the users I'm working with the CLI should be fine [21:28] i'll chat internally to see if we should allow "composing" more specifically though [21:28] roaksoax: yes, I can move forward with this [21:29] roaksoax: or at lest show the "allocate" action for non-admin users on the Pod screen [21:29] roaksoax: currently for non-admin users there isn't any "take action" drop down list [21:29] yeah [21:29] roaksoax: thanks for the help [21:30] no worries, glad I could help. [21:40] Bug #1747084 opened: [2.3, UI, pod] No way to 'allocate' a from a pod via UI for normal users