/srv/irclogs.ubuntu.com/2018/02/02/#maas.txt

klj1218can only an admin user compose a new machine within a pod?02:25
klj1218I'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?02:27
=== frankban|afk is now known as frankban
mupBug #1746980 opened: storage /disk not showing  node change status commising to testing <MAAS:New> <https://launchpad.net/bugs/1746980>12:15
mupBug #1746980 changed: storage /disk not showing  node change status commising to testing <MAAS:New> <https://launchpad.net/bugs/1746980>12:22
mupBug #1746980 opened: storage /disk not showing  node change status commising to testing <MAAS:New> <https://launchpad.net/bugs/1746980>12:28
mupBug #1678362 opened: Support ZFS root and/or ZFS only installs <curtin:In Progress by raharper> <MAAS:Confirmed> <https://launchpad.net/bugs/1678362>15:31
ejathi ..16:34
ejati use openstack-telemetry charms .. 2 services got problem (mongodb & neutron-gateway)  .. juju status output : http://paste.ubuntu.com/26506527/16:35
ejatmongodb log output: https://paste.ubuntu.com/26506520/16:36
ejatneutron-gateway: https://paste.ubuntu.com/26506512/16:36
roaksoaxejat: maybe #ubuntu-server is the best place for openstack issues ?16:39
ejatok noted roaksoax .. sorry16:42
klj1218I asked earlier and didn't see a response, so I'll try again17:04
klj1218can only an admin user compose a new machine within a pod?17:05
klj1218I'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?17:05
=== frankban is now known as frankban|afk
roraWhere's the TFTP root dir?20:11
rora/var/lib/maas/boot-resources/current?20:14
roaksoaxrora: there's no tftproot dir20:47
roaksoaxklj1218: uhmmm let me investigate20:47
roaksoaxrora: well, there is and there's not20:48
roaksoaxrora: the config is provided dynamically20:48
klj1218roaksoax : thanks20:48
roaksoaxklj1218: ha! just saw your email too20:50
klj1218roaksoax: :-)20:51
roaksoaxklj1218: ok, are you doing this via the UI?, or API ?21:06
klj1218UI ... just tested with admin user via cli, was going to test non-admin user via cli21:06
roaksoaxklj1218: so a normal user cannot *compose*21:07
roaksoaxklj1218: but it *can* allocate21:07
roaksoaxklj1218: composition doesn't mean ownership21:07
klj1218roaksoax: ok, from UI or CLI21:07
roaksoaxbut allocation does21:07
roaksoaxklj1218: cli21:07
roaksoaxe.g. maas normal machines allocate cpu_count=4 mem=409621:08
roaksoaxthat would work21:08
roaksoaxmaas normal pod compose <pod_id> <....> # this won't work21:09
roaksoaxso, it seems the reason we did that is because "compose" (manual composition) doens't imply ownership, where as 'allocation' does21:09
mupBug #1747080 opened: commissioning fails during 00-maas-01-lshw <MAAS:Incomplete> <https://launchpad.net/bugs/1747080>21:10
roaksoaxklj1218: but it seems that the problme with that, is that here';s no UI compatible way to do so21:12
klj1218roaksoax: but you cant allocate from a POD using the CLI correct?21:12
roaksoaxklj1218: yes you can21:12
klj1218roaksoax: ok, going to search for the CLI reference for that now21:14
roaksoaxklj1218: maas test machines allocate pod=pure-goat cpu_count=X mem=Y21:14
roaksoaxklj1218: maas test machines allocate pod=pure-goat cpu_count=X mem=Y # this would work21:15
roaksoaxklj1218: maas test pod compose <pod_id> # this wont work21:15
klj1218roaksoax: ok, yeah that will just allocate on the the already created machines21:17
klj1218roaksoax: so i still have to first "compose" the machines, then I can turn it over to a non-admin user to allocate/deploy21:18
roaksoaxklj1218: not necessarily21:18
roaksoaxklj1218:  maas test machines allocate pod_type=kvm21:18
klj1218roaksoax: I just did this: maas klj machines allocate pod=dev01 cpu_count=4 mem=1638421:19
roaksoaxerr21:19
klj1218roaksoax: this allocated one of the systems that I had already composed from the Pod21:19
klj1218roaksoax: it didn't create a new machine and allocate it to the klj non-admin user21:20
roaksoaxklj1218: that's correct 'allocation' will always first look for what you currently have depending on the constraints that you pass21:20
roaksoaxif you don't find anything, it will atomatically compose a machine21:20
klj1218roaksoax: ok, yup I just tried to allocate a machine with 8 vpus and it did indeed create a new machine21:22
roaksoaxklj1218: ok, that said, is there any specific requirement that would want you to have this via the UI ?21:26
klj1218roaksoax: 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 them21:27
klj1218roaksoax: but with the CLI, I can now just turn over the Pod to them and they can allocate from it21:28
roaksoaxklj1218: ok, great, you are unblocked then21:28
klj1218roaksoax: for the users I'm working with the CLI should be fine21:28
roaksoaxi'll chat internally to see if we should allow "composing" more specifically though21:28
klj1218roaksoax: yes, I can move forward with this21:28
klj1218roaksoax: or at lest show the "allocate" action for non-admin users on the Pod screen21:29
klj1218roaksoax: currently for non-admin users there isn't any "take action" drop down list21:29
roaksoaxyeah21:29
klj1218roaksoax: thanks for the help21:29
roaksoaxno worries, glad I could help.21:30
mupBug #1747084 opened: [2.3, UI, pod] No way to 'allocate' a from a pod via UI for normal users <pod> <pods> <MAAS:Triaged> <MAAS 2.3:Triaged> <https://launchpad.net/bugs/1747084>21:40

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!