Showing entries 1 to 8
Displaying posts with tag: policy (reset)
The Continuent Docker Support Policy Explained

Overview

Continuent has traditionally had a relaxed policy about Linux platform support for customers using our products.

While it is possible to install and run Continuent Tungsten products (i.e. Cluster/Replicator/etc.) inside Docker containers, there are many reasons why this is not a good idea.

Background

As background, every database node in a Tungsten Cluster runs at least three (3) layers or services:

  • MySQL Server (i.e. MySQL Community or Enterprise, MariaDB or Percona Server)
  • Tungsten Manager, which handles health-checking, signaling and failover decisions (Java-based)
  • Tungsten Replicator, which handles the movement of events from the MySQL master server binary logs to the slave databases nodes (Java-based)

Optionally, a …

[Read more]
Extended Policy and MySQL

Any secure system needs to be configured correctly to best serve the needs of users and the business. Previously, I've covered AppArmor and MySQL, and more recently SELinux and MySQL. To round out a healthy trio on running MySQL in environments with mandatory access control, Glenn Faden has written a post on Oracle Solaris Extended Policy and MySQL.

Extended Policy is a feature of Solaris that allows you to assign named privileges on resources—such as ports and files—to services. I'm not hugely familiar with Extended Policy (or Solaris for that matter), but according to Glenn it's similar to SELinux …

[Read more]
Active support for MySQL 5.0 and extended support for 4.1 will soon end

At the end of this year, two long lasting versions of MySQL will fall off the radar, each of them in a different way.

MySQL 5.0 active support will end.

What does that mean? it means that there won't be regular monthly updates and bug fixes. This version enters the extended support period, which lasts until 2012. During this phase, only security and major bugs fixes will be applied.

MySQL 5.0 will still be available in the download pages for two more years, and any security updates will be released on those pages.

The previous version, MySQL 4.1, instead, will be retired completely. It has ended its extended period. As such, it will be removed from the download page, and also from the download archives. Next year, if you want …

[Read more]
Active support for MySQL 5.0 and extended support for 4.1 will soon end

At the end of this year, two long lasting versions of MySQL will fall off the radar, each of them in a different way.

MySQL 5.0 active support will end.

What does that mean? it means that there won't be regular monthly updates and bug fixes. This version enters the extended support period, which lasts until 2012. During this phase, only security and major bugs fixes will be applied.

MySQL 5.0 will still be available in the download pages for two more years, and any security updates will be released on those pages.

The previous version, MySQL 4.1, instead, will be retired completely. It has ended its extended period. As such, it will be removed from the download page, and also from the download archives. Next year, if you want …

[Read more]
Active support for MySQL 5.0 and extended support for 4.1 will soon end

At the end of this year, two long lasting versions of MySQL will fall off the radar, each of them in a different way.

MySQL 5.0 active support will end.

What does that mean? it means that there won't be regular monthly updates and bug fixes. This version enters the extended support period, which lasts until 2012. During this phase, only security and major bugs fixes will be applied.

MySQL 5.0 will still be available in the download pages for two more years, and any security updates will be released on those pages.

The previous version, MySQL 4.1, instead, will be retired completely. It has ended its extended period. As such, it will be removed from the download page, and also from the download archives. Next year, if you want …

[Read more]
Spring cleaning in MySQL supported platforms

The MySQL Lifecycle Policy determines which versions are actively supported, and for which platforms such support applies.
The basic principle is that old versions are supported for a quite long, but definitely limited period, once they have been replaced by a newer GA version. For example, since the introduction of this policy, MySQL 3.23 and 4.0 have been retired.
The policy contains also provisions for a different kind of End of Life dismissal. When support for certain platforms has been discontinued by their vendors, of the platform is not widely used, MySQL reserves the right to stop building binaries and testing code on such obsolete platforms.
The reason is simple. While hardware can be bought and stored, time is a commodity in short supply, and there is only a given amount of time that our engineers can devote to testing and supporting multiple …

[Read more]
Source Controlling the Database Schema

In a linkage of biblical proportions, Log Buffer #83 pointed me to Tom Kyte’s reiteration which pointed me to Coding Horror’s rant about source controlling the database schema. Now, for starters, I agree with Tom’s sarcasm and Coding Horror’s rant — the database schema really should be source controlled in the same place as the application [...]

Week Highlights - MySQL and Sun, BEA and Oracle, SailFin, Paul Sterk ...

• Sun and MySQL

Welcome Aboard!,

Reactions,

More Reactions


• Access Control -

ANYONE Access,

[Read more]
Showing entries 1 to 8