GNU Bayonne 1.2
GNU Bayonne is the telecommunications application server of the GNU Project. With the introduction of embedded SQL support, we are now actually close to having what I hope will be a new stable Bayonne base release, 1.2. Ideally, I would like to introduce a 1.2 release in late January, around the time of LinuxWorld in NYC. However, there are a number of specific things that I think need to happen before we can do a 1.2 release.
First, we need to update the documentation for GNU Bayonne. The documentation was never entirely complete or fully accurate even for the 1.0 release, and certainly is obsolete at this point. Documentation completion depends to some extent on feature completion, but the question of what a feature complete 1.2 server will be is now at least close to finalized. Does anyone wish to come forward to help on that?
In terms of remaining features for the 1.2 server, now that server embedded SQL support has been introduced, there is only a few immediate/short-term goals I have left. These include restructuring of existing RPC services, and the ability to support telephony enabled web services through Bayonne scripting. With this, and further work on GNU Bayonne XML parsing, it will become much easier to use GNU Bayonne to telephony enable existing web services and web hosted applications. This, hopefully, will be the last noticeable server feature change, other than driver work.
Speaking of driver work, there are issues in existing drivers, and some new/incomplete drivers that need to be finished. The capi driver either needs to be actively maintained, or I will rewrite it so I can maintain it. I do not have much hope to have time to look at the oh323, vmodem, zapata, or brooktrout drivers before spring, unless others choose to come forward to work on those. Hence, I do not expect any new drivers to be introduced with 1.2, at least at this point.
Current 1.1 development releases have been meant to test and integrate new features into GNU Bayonne, and to experiment with new or altered features from the normal 1.0 stable releases we currently maintain. The resulting 1.2 release will offer a new stable GNU application telephony platform that will be usable for building complete telephone systems, to better telephony enable web services, and to provide a reference platform for several unannounced projects already underway.
If you wish to help with GNU Bayonne development, feel free to contact me directly at the address above. We also have an ambitious schedule and at least one new person who will be available to travel and speak about GNU Bayonne at events around the world. We are looking for travel sponsorship so we can have GNU Bayonne presentations in at least as many events next year as we were able to do this current year. Finally, we will be introducing a project starting in the Republic of Macedonia to develop GNU Bayonne as a platform to deliver e-government services to the blind and we are actively seeking further sponsorship for that effort as well.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Doing for User Space What We Did for Kernel Space
- Tech Tip: Really Simple HTTP Server with Python
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- Rogue Wave Software's Zend Server
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide