Great job! /cc @edoardo_spadoni
I love the “hints” pattern over the “wizard” one
I hope to develop the Active Directory BDC/slave role UI on Cockpit soon
Great job! /cc @edoardo_spadoni
I love the “hints” pattern over the “wizard” one
I hope to develop the Active Directory BDC/slave role UI on Cockpit soon
Wow!!! Looks great. Love it.
Can’t await this to be standard UI! Is there a roadmap or timetable for this project?
Please read my post above.
Looks amazing and growing day after day
The cockpit based server-manager is really nice and a big step forward.
It is responsive and I love the modern looks;
Big thumps up and looking forward to its release.
(Do not forget the above while reading the next.)
I love graphs but they need to be meaningful and accurate.
Cockpit has some dependencies which are not really needed, specific for my raid-less test-system mdadm, but also NetworkManager and Udisks. To my understanding the latter two for their dbus capabilities. Despite the demonstration of shear possibilities of dbus with the streaming graphs; are my feelings regarding dbus as the ideal IPC for a server at least ambiguous.
Therefor very happy to see the nethserver-api implementation which does not heavily rely on the dbus. I’m curious about the thoughts/background to break with the upstream cockpit-philosophy on this topic.
Again I really like this
(and it work’s on arm too )
You are right after updating nethserver-cockpit it looks like this;
From the bright side some of my objections regarding the graphs are solved.
EDIT:
pounding one core (stress -c 1 --timeout 60s
) and both cores (stress -c 2 --timeout 60s
)
We just copied old cockpit graphs. Let’s ask @edoardo_spadoni if is easy enough to pull latest upstream modifications inside our page.
Because writing a simple script in whatever language is much simpler than trying to understand the ugly DBUS protocol
Also, I don’t like DBUS…
Totally agree. Lets see what the future brings i got the feeling dbus is pushed into the server environment by rhel.
I’ve just pulled the latest CPU graph that show the number of the cores. For the memory part it’s not so simple, maybe it’s better to wait a better implementation from the upstream and pull down the updates in our system later.
If you want to checkout the new CPU graph simply update from testing repos
Thank you @edoardo_spadoni the cpu graph is accurate now.
BTW I see /usr/share/cockpit/nethserver/manifest.json is fixed and we land on the nethsever dashboard (:9090/nethserver) again. Is it an idea to “lock” one demo version while devolvement goes on so people how are late to the party get something nice to play with?
Demo version is dead, long live the Alpha release!
We are pushing to the public to gather feedback and fix bugs while the development is in progress.
Which version-number has Alpha 1?
I’ve nethserver-cockpit-0.0.5-1.26.g17ad52b.ns7.noarch
.
Is Alpha 1 only for 7.6 or also for 7.5 available?
Everything is still available on 7.5.
To be sure to always pull latest release from testing:
yum --enablerepo=nethserver-testing clean all
yum --enablerepo=nethserver-testing install nethserver-cockpit
I love the new cockpit- great job done- congrats
Nethserver 7.6 will be cockpit-based or nethgui-based?
There will be both! An alpha preview of the new server manager will be available from the Software Center
More information: https://github.com/NethServer/dev/issues/5660
Therefore… Nethgui based.
With cockpit based server manager as option for early adopters and test.
Yes. Cockpit is going to be a revolution we can’t force our userbase to adopt the new UI overnight.
I don’t know yet, I guess it may be a standard with NethServer 8
Good job guys!