New project - XenAdminQt - a cross-platform GNU/Linux, macOS, Windows native thick client

Tristis Oris

Wow, great news. Tried it with my pools.
Connected, basic functions is working, handled pool unavailability.

About UI usability:

templates mixed up with disabled VMs at same root directory. Without any sorting.
I prefer to never see them, since it not important items.

fce4c8e4-9532-40cd-9e5f-d1231b627676-изображение.png

After app restart all icons became yellow.
looks like this option do nothing.

How about portable mode? App mostly required for asap situations when XO is down.

benapetr

@Tristis-Oris hello, the app is already somewhat portable. On windows it doesn't require any installation it's just a single .exe file

Regarding templates and sorting of tree view - that's being worked out but you can already hide the templates using View menu (just uncheck you want to display them, they will disappear).

Not sure about the yellow template icons, they is a debug console, you can check logs from it for more details.

Save and restore using encryption / master password isn't implemented in that version you have, it just always remembers all connections, but it's already ported over, see - https://github.com/benapetr/XenAdminQt/pull/15 this option will be available in next version (+ master password encryption)

benapetr opened this pull request in benapetr/XenAdminQt

closed Feature/mpw #15

Tristis Oris

@benapetr yes, i'm about connections and credentials export\portable mode. Got it.

Tristis Oris

@benapetr said in New project - XenAdminQt - a cross-platform GNU/Linux, macOS, Windows native thick client:

you can already hide the templates using View menu (just uncheck you want to display them, they will disappear).

What is the criterion for custom templates?

7eb0ec2d-1968-471f-a4ad-d137ea36e05d-изображение.png

by default, the usual templates are disabled, but I see them. Disabling custom ones disables all templates.

benapetr

@Tristis-Oris the logic was directly ported over from C# version, so it does the same stuff what it filters there. It just toggles this search scope:

QueryScope* TreeSearch::GetTreeSearchScope()
{
    ObjectTypes types = Search::DefaultObjectTypes();
    types |= ObjectTypes::Pool;

    SettingsManager& settings = SettingsManager::instance();

    if (settings.getDefaultTemplatesVisible())
        types |= ObjectTypes::DefaultTemplate;

    if (settings.getUserTemplatesVisible()) // these are custom
        types |= ObjectTypes::UserTemplate;

    if (settings.getLocalSRsVisible())
        types |= ObjectTypes::LocalSR;

    return new QueryScope(types);
}

I assume it matches all user-defined templates, the defaults you see are "system defined" and part of xcp-ng .rpm packages. It's possible that this logic just wasn't ported correctly, I will look into it.

benapetr

@Tristis-Oris just FYI I fixed all of those issues you had, also regarding portable stuff - I implemented CLI switch -c <path> where you can specify directory where you want to store config, so you can wrap the app in a .bat or .sh script that would start it to use local storage (like flash drive) for config files, that should achieve portability.

If you expected something more sophisticated let me know

Tristis Oris

@benapetr Nice, great.
How about to implement a launch of CR backup VMs?

https://xcp-ng.org/forum/assets/uploads/files/1769679350079-677dfcbb-211b-452f-ad8f-db59e2860579-изображение.png
https://xcp-ng.org/forum/assets/uploads/files/1769679584572-3e39d799-a2fd-4cb0-8e2e-6b9c4312a2e6-изображение.png

benapetr

@Tristis-Oris There are many features missing since it's alpha now, but you can open bug tracker request on github if you want to keep track of progress for this particular feature.

TeddyAstie

@benapetr
Consider making a PR to https://github.com/xcp-ng/xcp-ng-org (https://github.com/xcp-ng/xcp-ng-org/blob/master/docs/management/management.md) if you want to make your project more visible.

benapetr

@TeddyAstie good idea, thanks, I will do it once I get close to releasing first non-alpha version, right now it's still too immature for production use (although latest master version is so good and stable I already use it to manage most of my own clusters)

olivierlambert

Note we already gave visibility on this project twice, with the last 2 XO blog post release and newsletter