hi.
i played around with salt and noticed a few things/ have some questions:
1)
even when some states fail for some vm, the cli tool displays ok. it
would be better, if it displayed error in case of an error (some errors
are displayed).
2)
what happens if i have not enough memory to start a management vm? is
there something to counter this problem? (e.g. detect this case, limit
the number of management vms started at the same time and retrying the
action)
3)
is there a plan to add some way of configuring dom0 (including service
permissions, default vm/template/etc, changing copy&paste shortcuts...)
4)
how much of the salt interface is subject to change?
5)
are there plans to add some functionality to the interface?
6)
currently i really don't like the way the configuration works.
i have a top file where i execute some states for dom0
these states create and configure my vms.
then in some top files i choose some vms and configure them again (but
this time it is some config i am doing in the domu).
so it kind of looks like this:
top.top
-----
base:
dom0:
- create-cfg-vm1
vm1:
- some-cfg-in-domu
----
now i have two layers of configuration (in top and sls).
for some config stuff i have to change a sls and for other i have to
change the top
is there a plan to change this?
e.g. some kind of virtual minions?
i would like to write something like this:
top.top
-----
base:
dom0:
- copy-sequence.Strg-Alt-Shift-C
vm1:
- create #this affects dom0
- color.red #this affects dom0
- netvm.sys-tor #this affects dom0
- mail #this affects domU
----
then i could see all my domU config in the top file.
i currently hacked something but this only works in a sls file and for
dom0 config (but has this style of syntax)
i am currently looking whether i can do the same in a top file (but i
doubt it, since there is no templating in top files)
concerning this i also have some other questions
how is the order of execution?
will dom0 always be executed before any domU is started?
when are the files for domU read?
after dom0 is configured? (then i could write state files during dom0
configuration)
(if you want i can upload my scripts when i am done)
7)
is there some documentation on the custom salt modules added by qubes?
(i may want to extend them)
8)
is there some way to execute some dom0 scripts after configuration of
domu? (e.g. trim-template)
9)
the fedora-24-min template can't really be configured with salt.
there is the package file missing.
after i installed the package i still got an error: "Target
'fedora-24-min' did not return any data, probably due to an error. exit
code 20"
any idea how i could fix this?
or where i could get more data. e.g. are there some salt logs in some vm
(e.g. in the domU)?
there probably are files in the management vm, but this vm gets deleted.
is there an option to stop the deletion of the management vm?
- john
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/5c4fdeb6-b97e-0be7-038d-20bc24101890%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.
