@c-po can we mark this as resolved?

@dmbaturin should we run all our scripts with such wrapper? (e.g. add it to all places where scripts can be used)

the script must be run from vyatta group
sg vyattacfg /path/to/script

@hagbardI like the idea to have it modular,
we also need to add profiling option (collecting system metrics over some period of time)
and maybe some more stuff (specific to functionality like ipsec, bgp, firewall, etc)

Yes,
that will be kind of the first step in troubleshooting workflow
i propose to make another ticket for show tech-support
and current one assign as a subtask

Current show tech-support can be nuked once we have a replacement
The on-screen output is useful if you debug onsite or have access to the machine
We mixing here stuff, integrity check bit different from show tech-support but can be part of it

we need tech-support but need it reworked
on one hand, it must be human-friendly
on another hand, we need to have ability feed it into analytics platform later
we should skip all sensitive info

Instance size?

@rherold my point bit different
we will take care about DNS little bit later

In T14#23659, @higebu wrote:

I tested with only NoCloud.
I understand ovf/ova must include ProductSection with some properties like this https://github.com/cloud-init/cloud-init/blob/master/doc/sources/ovf/example/ubuntu-server.ovf

yes, exactly

Where is the ovf @UnicronNL made?

it does not exist yet :)

ovf/ova must be with properly configured ovf environment and cloud-init package @UnicronNL made into vyos repository

@higebu yes, @UnicronNL already have it in backlog