On Sun, Feb 5, 2017 at 3:39 PM, Andrew David Wong <[email protected]> wrote:
> On 2017-02-04 15:10, Oleg Artemiev wrote:
>>> This is a good time to mention that we're in need of an HCL
>>> maintainer. Our longtime volunteer HCL maintainer, Zrubi, no
>>> longer has the time to do it. We all owe Zrubi a debt of
>>> gratitude for keeping up this thankless task for so long! :)
>>> Any volunteers?
>> Why not to just script-out this once and forget?
>>
>> source information: email from someone, output information -> some
>> file to put on the web?
> Some stuff still had to be edited manually, but it could indeed be
> automated better. Can you help us with that? :D
I'm interested in helping automate this. Though can't claim that it
will be fast.

Could you, please, point me into what is already automated (repo +
path) and related brief dox on how
execution is done currently (if any)?

My idea how it should look like:

a special qubes image:

*. preinstalled on some usb stick
*. has only a preconfigured VMs: netVM, firefwallVM, user interface is
not required.

Dom0 has a script in startup scripts that:
*. runs HCL
*. updates HCL file: old data copied somewhere inside dom0 for user reference
*. copies file to net VM,

VM has a script:
*. checks for  HCL file to be present eache minute
*. checks that internet is available
*. makes a gui request to a user to fill required manual fields (model
as the store names it, user name(optional), and so on)
*. once confirned - sends HCL file to specially assigned emaili at qubes.org

Qubes web:
*. A sctipt on qubes.org updates some HCL html in predefined format

PS: I would prefer just a  single HCL usb stick run, that boots, asks
user for input  'seller named model as' and mail result automatically
(now or later if at runtime we had no internet) -
no user interface except this, GUI is optional, all Dom0/VM made in a
single place in modified Dom0, but that is against architecture and
making such an image may require much more
work than scripting this as a chain of small scripts + preconfigured
VMs. BTW: I'd like such an thing also for old versions of Qubes OS -
sooner or later we will face usual store that some
hardware is okay w/ old Qubes but too slow with new.
Alternatively we could have a special preconfigured VM image that does
all VM part above, but require user filling HCL to activate manually.

-- 
Bye.Olli.
gpg --search-keys grey_olli , use key w/ fingerprint below:
Key fingerprint = 9901 6808 768C 8B89 544C  9BE0 49F9 5A46 2B98 147E
Blog keys (the blog is mostly in Russian): http://grey-olli.livejournal.com/tag/

-- 
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CABunX6OFbEzXnqpUOVXJx%2B%3DhCJwhy27KG6Z6tP%2BQyohfT4S4Lg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to