Hi all, I've had some issues receiving emails from the list, so hopefully this one works.
Some further info on my management GUI project:
- It will be open source (probably on github) - Qt Quick based - Similar (but not identical) in functionality and look'n'feel to Windows Server Manager - It is motivated by the same reasons that Russell Doty so thoughtfully explained on his Tech Ponder blog re: Linux management. I see a place for both CLI and GUI interfaces. - Leveraging OpenLMI for my project has dual benefits: it provides a useful, consistent mechanism to manage local and remote systems, and it is an opportunity for me to participate in the development of OpenLMI itself (since Linux *badly* needs a unified PowerShell-like management interface) - Looking a *long* way ahead, I'm interested whether such a tool could be the basis for, or at least a component of, autonomic computing
My background:
- I'm an infrastructure architect (and RHCE) working for an Australian bank with around 20 years of IT industry experience, covering most areas of infrastructure (as a customer only - I haven't worked for a tech vendor). - I'm a hobbyist developer, dabbling mainly in C/C++ and Python/Django - I'm motivated to work on a Linux-related open source project as it represents the intersection of my personal and professional interests, and I perceive it to be a form of community service where I can use my skills and experience to give something back to the (global) community - This is my first open source project contribution, so please be gentle :) - I can confidently contribute between 10-15 hours a week
My project status:
- I'm still learning the Qt Quick framework - I need to wrap my head around the OpenPegasus C++ client library and WBEM in general - I don't expect my first proof-of-concept pre-alpha release for a few more months at least
Areas where I can contribute to the OpenLMI project:
- OpenLMI provider development - Documentation - Web site content
Hope this info helps.
Steve
Hi Steve.
Welcome in OpenLMI. Having a nice GUI is certainly something we still miss so we will try to help you succeed with the project as much as we can.
On Tue, 26 Nov 2013 09:14:58 +1100 Steve Pritchard sjpritchard@gmail.com wrote:
Hi all, I've had some issues receiving emails from the list, so hopefully this one works.
Some further info on my management GUI project:
- It will be open source (probably on github)
- Qt Quick based
- Similar (but not identical) in functionality and look'n'feel to Windows
Server Manager
- It is motivated by the same reasons that Russell Doty so thoughtfully
explained on his Tech Ponder blog re: Linux management. I see a place for both CLI and GUI interfaces.
- Leveraging OpenLMI for my project has dual benefits: it provides a
useful, consistent mechanism to manage local and remote systems, and it is an opportunity for me to participate in the development of OpenLMI itself (since Linux *badly* needs a unified PowerShell-like management interface)
- Looking a *long* way ahead, I'm interested whether such a tool could be
the basis for, or at least a component of, autonomic computing
Looks good. There is actually one more project that creates a web GUI for the system management and we thing eventually of integrating OpenLMI into it: Cockpit (http://cockpit-project.org/). However I believe there is a place for a desktop GUI as well and it makes a lot of sense for both the solutions to exist. You may be however interested in the Cockpit project since they are or will be probably solving many problems you may encounter as well.
Regards,
On Tue, Nov 26, 2013 at 5:13 PM, Tomáš Smetana tsmetana@redhat.com wrote:
Hi Steve.
Looks good. There is actually one more project that creates a web GUI for the system management and we thing eventually of integrating OpenLMI into it: Cockpit (http://cockpit-project.org/). However I believe there is a place for a desktop GUI as well and it makes a lot of sense for both the solutions to exist. You may be however interested in the Cockpit project since they are or will be probably solving many problems you may encounter as well.
Thanks Tomas for sharing the Cockpit. Looking at the source briefly, it seems that it initiated recently by RedHat. and Good to know that RedHat is investing in system management.
As a side note, yet to be released pegasus 2.14 will start having support for REST ful API(CIM-RS) phase by phase and we have put some effort to turn pegasus to serve html pages like a webserver does. Pegasus will be able to accept/yield JSON for any CIM instance in the repository, which can be consumed for GUI.
Sometimes back, was also thinking to put effort in web app using CIM-RS through django which can 1) administer the cimserver including config management, indications subscription management etc 2) Have a traceAnalyser to help debugging 3) and support for Automatic provider Registration etc etc
However, my interest was limited only to help provider developer with a GUI(Not as a full fledged system management app)
Anybody might still be able to create system management app faster without bringing in a separate webserver.
Regards,
Tomáš Smetana Platform Engineering, Red Hat _______________________________________________ openlmi-devel mailing list openlmi-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/openlmi-devel
Devchandra,
We are quite interested in pegasus 2.14 - do you have any idea when it might be available?
Russ
On Tue, 2013-11-26 at 18:07 +0530, Devchandra L Meetei wrote:
On Tue, Nov 26, 2013 at 5:13 PM, Tomáš Smetana tsmetana@redhat.com wrote: Hi Steve.
Looks good. There is actually one more project that creates a web GUI for the system management and we thing eventually of integrating OpenLMI into it: Cockpit (http://cockpit-project.org/). However I believe there is a place for a desktop GUI as well and it makes a lot of sense for both the solutions to exist. You may be however interested in the Cockpit project since they are or will be probably solving many problems you may encounter as well.
Thanks Tomas for sharing the Cockpit. Looking at the source briefly, it seems that it initiated recently by RedHat.
and Good to know that RedHat is investing in system management.
As a side note, yet to be released pegasus 2.14 will start having support for REST ful API(CIM-RS) phase by phase
and we have put some effort to turn pegasus to serve html pages like a webserver does. Pegasus will be able to accept/yield
JSON for any CIM instance in the repository, which can be consumed for GUI.
Sometimes back, was also thinking to put effort in web app using CIM-RS through django which can
- administer the cimserver including config management, indications
subscription management etc
Have a traceAnalyser to help debugging
and support for Automatic provider Registration etc etc
However, my interest was limited only to help provider developer with a GUI(Not as a full fledged system management app)
Anybody might still be able to create system management app faster without bringing in a separate webserver.
Regards, -- Tomáš Smetana Platform Engineering, Red Hat _______________________________________________ openlmi-devel mailing list openlmi-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/openlmi-devel
-- Warm Regards --Dev OpenPegasus Developer/Committer
(__/) (='.'=) This is Bunny. Copy and paste bunny (")_(") to help him gain world domination.
openlmi-devel mailing list openlmi-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/openlmi-devel
pegasus 2.14 has been much delayed from the originally planned date. Sorry for that.
Will update openlmi later.
On Tue, Nov 26, 2013 at 8:38 PM, Russell Doty rdoty@redhat.com wrote:
Devchandra,
We are quite interested in pegasus 2.14 - do you have any idea when it might be available?
Russ
On Tue, 2013-11-26 at 18:07 +0530, Devchandra L Meetei wrote:
On Tue, Nov 26, 2013 at 5:13 PM, Tomáš Smetana tsmetana@redhat.com wrote: Hi Steve.
Looks good. There is actually one more project that creates a web GUI for the system management and we thing eventually of integrating OpenLMI into it: Cockpit (http://cockpit-project.org/). However I believe there is a place for a desktop GUI as well and it makes a lot of sense for both the solutions to exist. You may be however interested in the Cockpit project since they are or will be probably solving many problems you may encounter as well.
Thanks Tomas for sharing the Cockpit. Looking at the source briefly, it seems that it initiated recently by RedHat.
and Good to know that RedHat is investing in system management.
As a side note, yet to be released pegasus 2.14 will start having support for REST ful API(CIM-RS) phase by phase
and we have put some effort to turn pegasus to serve html pages like a webserver does. Pegasus will be able to accept/yield
JSON for any CIM instance in the repository, which can be consumed for GUI.
Sometimes back, was also thinking to put effort in web app using CIM-RS through django which can
- administer the cimserver including config management, indications
subscription management etc
Have a traceAnalyser to help debugging
and support for Automatic provider Registration etc etc
However, my interest was limited only to help provider developer with a GUI(Not as a full fledged system management app)
Anybody might still be able to create system management app faster without bringing in a separate webserver.
Regards, -- Tomáš Smetana Platform Engineering, Red Hat _______________________________________________ openlmi-devel mailing list openlmi-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/openlmi-devel
-- Warm Regards --Dev OpenPegasus Developer/Committer
(__/) (='.'=) This is Bunny. Copy and paste bunny (")_(") to help him gain world domination.
openlmi-devel mailing list openlmi-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/openlmi-devel
openlmi-devel mailing list openlmi-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/openlmi-devel
On Tue, 26 Nov 2013 18:07:36 +0530 Devchandra L Meetei dlmeetei@gmail.com wrote:
On Tue, Nov 26, 2013 at 5:13 PM, Tomáš Smetana tsmetana@redhat.com wrote:
<...>
Thanks Tomas for sharing the Cockpit. Looking at the source briefly, it seems that it initiated recently by RedHat. and Good to know that RedHat is investing in system management.
As a side note, yet to be released pegasus 2.14 will start having support for REST ful API(CIM-RS) phase by phase and we have put some effort to turn pegasus to serve html pages like a webserver does. Pegasus will be able to accept/yield JSON for any CIM instance in the repository, which can be consumed for GUI.
We know about it and that is actually one of the approaches we would like to explore: Cockpit relies heavily on JavaScript running on the client (browser) so the REST API is definitely something that might make the Cockpit integration more "natural". At least... I hope so.
Right now all the CIM infrastructure would be in many ways parallel to the native D-Bus/JSON ssh-tunnelled Cockpit protocol:
https://github.com/cockpit-project/cockpit/blob/master/doc/cockpit-transport...
The REST API might be more flexible and allow more interesting things to be developed. (I can imagine custom UI modules, etc.)
Regards,
On Tue, Nov 26, 2013 at 8:40 PM, Tomáš Smetana tsmetana@redhat.com wrote:
May be Tomas can shed some light here on cockpit,
Along with CIM-RS, pegasus will also have a capability to server static pages, Through this interface, we will have a limited version of webadmin will allow to administer cimserver. and if this ability can help users to remove an extra web server( Does cockpit fell in this category? May be you can educate me), It will be great.
If it does not meet your current requirement, we can together work to make it work.
We know about it and that is actually one of the approaches we would like to explore: Cockpit relies heavily on JavaScript running on the client (browser) so the REST API is definitely something that might make the Cockpit integration more "natural". At least... I hope so.
Right now all the CIM infrastructure would be in many ways parallel to the native D-Bus/JSON ssh-tunnelled Cockpit protocol:
https://github.com/cockpit-project/cockpit/blob/master/doc/cockpit-transport...
The REST API might be more flexible and allow more interesting things to be developed. (I can imagine custom UI modules, etc.)
Regards,
Tomáš Smetana Platform Engineering, Red Hat
On Tue, 2013-11-26 at 12:43 +0100, Tomáš Smetana wrote:
Looks good. There is actually one more project that creates a web GUI for the system management and we thing eventually of integrating OpenLMI into it: Cockpit (http://cockpit-project.org/). However I believe there is a place for a desktop GUI as well and it makes a lot of sense for both the solutions to exist. You may be however interested in the Cockpit project since they are or will be probably solving many problems you may encounter as well.
Regards,
Thanks for the welcome :) And thanks for sharing this info - I'll check it out. I'm not sufficiently wedded to my project that I wouldn't consider contributing to another such as this instead (although I do think that there is a place for a native cross-platform GUI in terms of performance and overall user experience)
Steve,
As others have said, welcome to the OpenLMI project! We look forward to working with you.
Russ
On Tue, 2013-11-26 at 09:14 +1100, Steve Pritchard wrote:
Hi all, I've had some issues receiving emails from the list, so hopefully this one works.
Some further info on my management GUI project:
- It will be open source (probably on github)
Excellent! Good choice on both open source and github.
- Qt Quick based
Makes sense.
- Similar (but not identical) in functionality and look'n'feel to
Windows Server Manager
Makes sense. Are you looking at Server Manager in Windows Server 2012 R2? Have you thought about starting with a subset? It might be interesting to start with storage - this is somewhat bounded, is where we are putting a lot of effort in the OpenLMI 1.0 release, and would be valuable to have a GUI.
- It is motivated by the same reasons that Russell Doty so
thoughtfully explained on his Tech Ponder blog re: Linux management. I see a place for both CLI and GUI interfaces.
Wow - someone actually reads the blog! Feel free to post questions and start discussions/arguments there.
- Leveraging OpenLMI for my project has dual benefits: it provides a
useful, consistent mechanism to manage local and remote systems, and it is an opportunity for me to participate in the development of OpenLMI itself (since Linux badly needs a unified PowerShell-like management interface)
We agree completely.
Have you looked at LMIshell? This is a client side application we are putting a lot of work into. I'm starting up a series of Blog articles on it; you should see the first one this week. LMIshell is a Python environment that provides a friendly interface to the OpenLMI API using native Python objects, a task focused scripting environment, and a high level CLI.
If you are interested in working in Python, it should be possible to build a GUI on top of LMIshell and take advantage of the Python rapid development environment and the higher level interfaces we are developing. At a minimum, you should look at the LMI Modules and see how we are using the low-level API to do management tasks.
- Looking a *long* way ahead, I'm interested whether such a tool could
be the basis for, or at least a component of, autonomic computing
We've thought about this. I personally believe that there is considerable potential in applying Business Process Management (BPM) and Rules Processing to system management. A really interesting starting point for this would be JBoss, using JBPM and Drools, possibly tied into the JON management framework. OpenLMI has an excellent Java interface that creates native Java objects and integrates nicely into JBoss.
My background:
- I'm an infrastructure architect (and RHCE) working for an Australian
bank with around 20 years of IT industry experience, covering most areas of infrastructure (as a customer only - I haven't worked for a tech vendor).
- I'm a hobbyist developer, dabbling mainly in C/C++ and Python/Django
- I'm motivated to work on a Linux-related open source project as it
represents the intersection of my personal and professional interests, and I perceive it to be a form of community service where I can use my skills and experience to give something back to the (global) community
- This is my first open source project contribution, so please be
gentle :)
- I can confidently contribute between 10-15 hours a week
My project status:
- I'm still learning the Qt Quick framework
- I need to wrap my head around the OpenPegasus C++ client library and
WBEM in general
- I don't expect my first proof-of-concept pre-alpha release for a few
more months at least
Areas where I can contribute to the OpenLMI project:
- OpenLMI provider development
- Documentation
- Web site content
Hope this info helps.
Steve _______________________________________________ openlmi-devel mailing list openlmi-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/openlmi-devel
On Tue, 2013-11-26 at 10:05 -0500, Russell Doty wrote:
Steve,
As others have said, welcome to the OpenLMI project! We look forward to working with you.
Russ
Thankyou! :)
- Qt Quick based
Makes sense.
- Similar (but not identical) in functionality and look'n'feel to
Windows Server Manager
Makes sense. Are you looking at Server Manager in Windows Server 2012 R2? Have you thought about starting with a subset? It might be interesting to start with storage - this is somewhat bounded, is where we are putting a lot of effort in the OpenLMI 1.0 release, and would be valuable to have a GUI.
Yes, I'm referring to Server Manager in Windows Server 2012/R2. And your suggestion about starting with storage is an excellent one.
- It is motivated by the same reasons that Russell Doty so
thoughtfully explained on his Tech Ponder blog re: Linux management. I see a place for both CLI and GUI interfaces.
Wow - someone actually reads the blog! Feel free to post questions and start discussions/arguments there.
Will do!
Have you looked at LMIshell? This is a client side application we are putting a lot of work into. I'm starting up a series of Blog articles on it; you should see the first one this week. LMIshell is a Python environment that provides a friendly interface to the OpenLMI API using native Python objects, a task focused scripting environment, and a high level CLI.
If you are interested in working in Python, it should be possible to build a GUI on top of LMIshell and take advantage of the Python rapid development environment and the higher level interfaces we are developing. At a minimum, you should look at the LMI Modules and see how we are using the low-level API to do management tasks.
I've briefly looked at LMIShell (and it looks great!), and in reality I should be using it instead of a C++ WBEM API (since I much prefer Python and it would help to drive the development of LMIShell too), but I'm concerned about dependency hell (since I want to use Qt Quick Controls, which needs Qt 5.1, which needs PyQt 5.1, which needs SIP 4.15, which breaks other things in Fedora because Fedora only has SIP 4.14, etc). I'll do some more tinkering to see if I can get a working PyQt setup.
- Looking a *long* way ahead, I'm interested whether such a tool could
be the basis for, or at least a component of, autonomic computing
We've thought about this. I personally believe that there is considerable potential in applying Business Process Management (BPM) and Rules Processing to system management. A really interesting starting point for this would be JBoss, using JBPM and Drools, possibly tied into the JON management framework. OpenLMI has an excellent Java interface that creates native Java objects and integrates nicely into JBoss.
I'm very interested in this. Really keen to explore this sort of approach further down the road.
openlmi-devel@lists.stg.fedorahosted.org