I've had a brief look at the gofer wiki (https://fedorahosted.org/gofer/ for the uninitiated) and it appears to me that while the functionality is similar to matahari, it is complementary in the sense that matahari provides a framework for writing agents that we would normally expect to see shipping with a distro, whereas gofer makes it easy for end users to write plugins in high-level languages to control their own custom tools.
One of the nice things about matahari is that all agents share a common configuration, so there is no proliferation of config files, QPID brokers, &c. With that in mind, is it worth considering converting gofer to become a matahari agent? That way we could provide end users with an easy way to create custom "agents" (really plugins) while piggy-backing on existing infrastructure.
Thoughts?
cheers, Zane.
Hey Zane:
On 08/03/2011 10:06 AM, Zane Bitter wrote:
I've had a brief look at the gofer wiki (https://fedorahosted.org/gofer/ for the uninitiated) and it appears to me that while the functionality is similar to matahari, it is complementary in the sense that matahari provides a framework for writing agents that we would normally expect to see shipping with a distro, whereas gofer makes it easy for end users to write plugins in high-level languages to control their own custom tools.
One of the nice things about matahari is that all agents share a common configuration, so there is no proliferation of config files, QPID brokers, &c. With that in mind, is it worth considering converting gofer to become a matahari agent? That way we could provide end users with an easy way to create custom "agents" (really plugins) while piggy-backing on existing infrastructure.
That's hard to say at this point. I don't know much about Matahari beyond being involved in conceptual discussions about a year ago. Can you point me to the documentation on what Matahari is and how to write a Matahari plugin? I poked around GitHub[1] but could have missed something.
[1] https://github.com/matahari/matahari/wiki
Thoughts?
cheers, Zane.
On 04/08/11 21:18, Jeff Ortel wrote:
Hey Zane:
On 08/03/2011 10:06 AM, Zane Bitter wrote:
I've had a brief look at the gofer wiki (https://fedorahosted.org/gofer/ for the uninitiated) and it appears to me that while the functionality is similar to matahari, it is complementary in the sense that matahari provides a framework for writing agents that we would normally expect to see shipping with a distro, whereas gofer makes it easy for end users to write plugins in high-level languages to control their own custom tools.
One of the nice things about matahari is that all agents share a common configuration, so there is no proliferation of config files, QPID brokers, &c. With that in mind, is it worth considering converting gofer to become a matahari agent? That way we could provide end users with an easy way to create custom "agents" (really plugins) while piggy-backing on existing infrastructure.
That's hard to say at this point. I don't know much about Matahari beyond being involved in conceptual discussions about a year ago. Can you point me to the documentation on what Matahari is and how to write a Matahari plugin? I poked around GitHub[1] but could have missed something.
Documentation is something we're short on at this point, and I'll be focussing on that after the Fedora 16 freeze later this month. In the meantime, there's actually a pretty good wiki page on how to write a matahari agent here:
https://github.com/matahari/matahari/wiki/How-to-create-agent
In essence, matahari is a cross-platform framework for creating agents that share a common configuration and infrastructure, using QMF and/or DBus as a transport. (It also includes a bunch of useful agents by default, but that's not the relevant part in this case.)
regards, Zane.
Thanks Zane!
I'll review the documentation, perhaps play with it a bit and get back to you with thoughts on building an agent based on gofer.
On 08/05/2011 03:39 AM, Zane Bitter wrote:
On 04/08/11 21:18, Jeff Ortel wrote:
Hey Zane:
On 08/03/2011 10:06 AM, Zane Bitter wrote:
I've had a brief look at the gofer wiki (https://fedorahosted.org/gofer/ for the uninitiated) and it appears to me that while the functionality is similar to matahari, it is complementary in the sense that matahari provides a framework for writing agents that we would normally expect to see shipping with a distro, whereas gofer makes it easy for end users to write plugins in high-level languages to control their own custom tools.
One of the nice things about matahari is that all agents share a common configuration, so there is no proliferation of config files, QPID brokers, &c. With that in mind, is it worth considering converting gofer to become a matahari agent? That way we could provide end users with an easy way to create custom "agents" (really plugins) while piggy-backing on existing infrastructure.
That's hard to say at this point. I don't know much about Matahari beyond being involved in conceptual discussions about a year ago. Can you point me to the documentation on what Matahari is and how to write a Matahari plugin? I poked around GitHub[1] but could have missed something.
Documentation is something we're short on at this point, and I'll be focussing on that after the Fedora 16 freeze later this month. In the meantime, there's actually a pretty good wiki page on how to write a matahari agent here:
https://github.com/matahari/matahari/wiki/How-to-create-agent
In essence, matahari is a cross-platform framework for creating agents that share a common configuration and infrastructure, using QMF and/or DBus as a transport. (It also includes a bunch of useful agents by default, but that's not the relevant part in this case.)
regards, Zane.
matahari@lists.fedorahosted.org