info:about
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
info:about [2015/03/07 14:08] |
info:about [2024/05/12 12:16] (current) [Sausalito] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== BlueOnyx ====== | ====== BlueOnyx ====== | ||
| - | BlueOnyx is an open source User Interface for virtual Webservers. BlueOnyx is built on top of the free CentOS or Scientific Linux operating system, which is binary compatible with Red Hat Enterprise Linux (EL). Over the years different versions of BlueOnyx were made for different versions of said OS's: EL5, EL6 and EL7. | + | BlueOnyx is an open source User Interface for virtual Webservers. BlueOnyx is built on top of the free CentOS or Scientific Linux operating system, which is binary compatible with Red Hat Enterprise Linux (EL). Over the years different versions of BlueOnyx were made for different versions of said OS's: EL5, EL6, EL7, EL8 and EL9. |
| BlueOnyx allows a Linux novice to install, administer, and manage a Linux-based Web server. | BlueOnyx allows a Linux novice to install, administer, and manage a Linux-based Web server. | ||
| Line 46: | Line 46: | ||
| ==== BlueQuartz ==== | ==== BlueQuartz ==== | ||
| - | BlueQuartz was mostly adopted among former operators of RaQ550 servers, who needed compatible replacements for their aging Sun Cobalt RaQs with more modern hardware. However, over time BlueQuartz also attracted new users that had no prior Sun Cobalt experience. According to statistics <- evaluation of server log files of the central YUM repositories of BlueQuartz.org April 2008 -.> (04/2008) of Project Blue Quartz run more than 135,000 Web servers worldwide with Blue Quartz (the numbers were counting Update operations collected and that may be representative). | + | BlueQuartz was mostly adopted among former operators of RaQ550 servers, who needed compatible replacements for their aging Sun Cobalt RaQs with more modern hardware. However, over time BlueQuartz also attracted new users that had no prior Sun Cobalt experience. According to statistics <- evaluation of server log files of the central YUM repositories of BlueQuartz.org April 2008 -.> (04/2008) of Project Blue Quartz run more than 135,000 Web servers worldwide with Blue Quartz (the numbers were counting Update operations collected and broken down by IP and may not be entirely representative). |
| ==== The developers ==== | ==== The developers ==== | ||
| - | The original Blue Quartz developers <ref> BlueQuartz: [http://bluequartz.org/aboutus.html The Team] </ ref> were Hisao Shibuya, Yutaka Yasuda and Makoto Oda. In the end of 2006 Brian N. Smith of NuOnce Networks, Inc. and Michael Stauber from Solarspeed.net joined the team. Both had (since 2000) provided add-on software and services for Sun Cobalt server and its successor systems. The team was further strengtened by Taco Scargo, a former Sun Cobalt employees. | + | The original Blue Quartz developers <ref> BlueQuartz: [http://bluequartz.org/aboutus.html The Team] </ref> were Hisao Shibuya, Yutaka Yasuda and Makoto Oda. In the end of 2006 Brian N. Smith of NuOnce Networks, Inc. and Michael Stauber from Solarspeed.net joined the team. Both had (since 2000) provided add-on software and services for Sun Cobalt server and its successor systems. The team was further strengtened by Taco Scargo, a former Sun Cobalt employee. |
| ==== Further development ==== | ==== Further development ==== | ||
| Line 58: | Line 58: | ||
| Hisao Shibuya, Yutaka Yasuda and Makoto Oda continued to maintain BlueQuartz. However, the newer BlueOnyx and the departure of important developers didn't make their task any easier. Years later BlueQuartz managed another major release and published BlueQuartz 5200R, which was based on CentOS 5 as OS, but it was soemwhat rough around the edges and lacked an ISO install method. | Hisao Shibuya, Yutaka Yasuda and Makoto Oda continued to maintain BlueQuartz. However, the newer BlueOnyx and the departure of important developers didn't make their task any easier. Years later BlueQuartz managed another major release and published BlueQuartz 5200R, which was based on CentOS 5 as OS, but it was soemwhat rough around the edges and lacked an ISO install method. | ||
| - | The project BlueQuartz has falled more or less dormant in recent years and Team BlueOnyx is happy that Hisao Shibuya has joined us to aid with his amazing expertise in the platform. | + | The project BlueQuartz had fallen more or less dormant over the years and Team BlueOnyx is happy that Hisao Shibuya has joined us to aid with his amazing expertise in the platform. |
| ===== Basic Architecture ===== | ===== Basic Architecture ===== | ||
| ==== Sausalito ==== | ==== Sausalito ==== | ||
| - | Developed by Cobalt Networks Inc. architecture called Sausalito. Essentially, Sausalito is modular and functions can be retrofitted via modules (eg third party) (( BlueOnyx Developer Archive: [[http://devel.blueonyx.it/pub/Cobalt/SSDK.pdf|Sausalito Developer's Guide (PDF)]])) (( BlueOnyx Developer Archive: [[http://devel.blueonyx.it/pub/Cobalt/DevGuide.pdf|The Qube 3 software Architecture Developer's Guide (PDF)]] )). Other Sun Cobalt related original documentation can be found in the (( BlueOnyx Developer Archive [[http://devel.blueonyx.it/pub/Cobalt/|BlueOnyx Developer Archive]] )) as well. | + | Developed by Cobalt Networks Inc. architecture called Sausalito. Essentially, Sausalito is modular and functions can be retrofitted via modules (eg third party) (( BlueOnyx Developer Archive: [[http://devel.blueonyx.it/pub/Cobalt/SSDK.pdf|Sausalito Developer's Guide (PDF)]])) (( BlueOnyx Developer Archive: [[http://devel.blueonyx.it/pub/Cobalt/DevGuide.pdf|The Qube 3 software Architecture Developer's Guide (PDF)]] )). Other Sun Cobalt related original documentation can be found in the [[http://devel.blueonyx.it/pub/Cobalt/|BlueOnyx Developer Archive]] as well. |
| Sausalito consists of the following components: | Sausalito consists of the following components: | ||
| ==== The user interface (UI) ==== | ==== The user interface (UI) ==== | ||
| - | The administration interface of BlueQuartz and BlueOnyx is programmed in [[PHP]]. Via so-called Skins or Themes the look of the admin interface could be customized, although the template architecture of the original GUI is by now somewhat antiquated. The UI runs on a customized Apache web server that is bound to a specific port (Port 81 - HTTP / Port 444 - HTTPS). This web server is running as an unprivileged user 'apache' (or 'admserv' in newer versions). However, it allows authenticated users to execute certain narrowly defined functions on the underlying operating system with superuser (root) rights. The level of privileges each user has is defined by Access Control Lists (ACL's) that operate on a per Group basis. Serveral levels of privileges exist. | + | The administration interface of BlueQuartz and BlueOnyx is programmed in [[PHP]]. Via so-called Skins or Themes the look of the admin interface could be customized, although the template architecture of the original GUI is by now somewhat antiquated. The UI runs on a customized Apache web server that is bound to a specific port (Port 81 - HTTPS / Port 444 - HTTP). This web server is running as an unprivileged user 'apache' (or 'admserv' in newer versions). However, it allows authenticated users to execute certain narrowly defined functions on the underlying operating system with superuser (root) rights. The level of privileges each user has is defined by Access Control Lists (ACL's) that operate on a per Group basis. Serveral levels of privileges exist. |
| If an authenticated user - provided he has sufficient privileges to do so - runs a transaction (such as creating a virtual site or user), then Sausalito writes an entry in an internal database. This database is called CODB. Which is short for "Cobalt Object Database". | If an authenticated user - provided he has sufficient privileges to do so - runs a transaction (such as creating a virtual site or user), then Sausalito writes an entry in an internal database. This database is called CODB. Which is short for "Cobalt Object Database". | ||
| Line 106: | Line 106: | ||
| BlueOnyx 5207R and BlueOnyx 5208R still use the PHP modules cce.so and i18n.so, but have a fallback mechanism in place. If these modules are no longer loaded (due to PHP compatability issues) the GUI will fall back to native PHP Classes that provide the same functionality. However, this comes at a small performance impact, as the PHP modules are faster than the PHP Classes. | BlueOnyx 5207R and BlueOnyx 5208R still use the PHP modules cce.so and i18n.so, but have a fallback mechanism in place. If these modules are no longer loaded (due to PHP compatability issues) the GUI will fall back to native PHP Classes that provide the same functionality. However, this comes at a small performance impact, as the PHP modules are faster than the PHP Classes. | ||
| - | BlueOnyx 5209R no longer uses the PHP modules cce.so and i18n.so, as we couldn't get them to work with PHP-5.4 due to API changes within PHP. BlueOnyx 5209R uses the supplementing PHP Classes instead by default. | + | Starting with BlueOnyx 5209R the PHP modules cce.so and i18n.so are no longer used, as we couldn't get them to work with newer PHP versions due to API changes within PHP. Since BlueOnyx 5209R all BlueOnyx versions use native PHP classes for communication with CCE and also for i18n localization. |
| ==== Operating system ==== | ==== Operating system ==== | ||
info/about.1425697692.txt.gz · Last modified: 2015/03/07 14:08 by
Page Tools
