Ronald Bradford - Data Architect, MySQL Expert, Author & Speaker on Enterprise Data Architect | Principal Data Strategist | MySQL Subject Matter Expert | Author | Speaker

The The Canonical Distribution of Ubuntu OpenStack provides a simple installer to run an OpenStack cloud.

While reviewing the OpenStack keystone codebase on an existing VM used with devstack I came across a dependency problem with Python pbr .

I attended my first OpenStack Summit in Vancouver 4/2015 .

Yesterday I was able to present to the Portland MySQL Users Group two presentations that are important foundations for effective development with MySQL.

As a way to navigate the extent of the CLI options for nova, keystone, glance and also openstack commands I came up with an educational approach.

As I refresh my skills in Python 2 to Python 3 semantics I discovered there is a difference in the division operator (i.e. /).

While building my own OpenStack cloud on physical servers I realized that Keystone uses a temporary authorization token in the Create the service entity and API endpoint and Create projects, users, and roles steps.

Openstack projects use tox to manage virtual environments and run unit tests which I talked about here .

Ubuntu 14.04 by default uses Python 2.7 and 3.4.

If you are using git-review for the first time the following instructions correctly install and configure for Mac OS X.

Recently the OSC (python-openstackclient ) project removed run_tests.sh #177066 and tools/install_venv.py scripts #177086 .

The slides for my MySQL Security Essentials presentation at Percona Live 2015 MySQL Conference and Expo are now available.

As I mentioned earlier in Moving to OpenStackClient CLI I came across several differences in reconciling the legacy CLI tools.

In working with the keynote CLI within the TripleO scripts I came across the following deprecation warning message. $ keystone token-get /usr/local/lib/python2.7/dist-packages/keystoneclient/shell.py:65: DeprecationWarning: The keystone CLI is deprecated…

The slides for my Improving Performance With Better Indexes presentation at Percona Live 2015 MySQL Conference and Expo are now available.

The Ubuntu 12.04.3 LTS release only provides MySQL 5.1 and MySQL 5.5 using the default Ubuntu package manager.

As part of a MySQL 5.5 to MySQL 5.6 upgrade across several Ubuntu servers of varying distros an audit highlighted a trivial but interesting versioning identification error in Ubuntu’s packaging of MySQL.

MySQL 5.6 will now automatically recreate the InnoDB redo log files during a MySQL restart if the size (or number) of these logs changes, i.e. a change to innodb_log_file_size.

I have just received copies of my Effective MySQL series that are available in Chinese.

I have recently been working with the Donors Choose Open Data Set which happens to be in PostgreSQL.

If you are die hard Bourne Shell (/bin/sh) scripter, it can be a challenge not to be enticed by the syntax niceties of the Born Again Borne Shell (/bin/bash).

When reading a MySQL Query Execution Plan (QEP) produced by the EXPLAIN command, generally one of the first observations is to validate an index is being used per table (i.e. per row of output).

In software development this is a simple question.

A trivial cost saving tip for checking if you are spending money in your AWS environment on unused resources.

As discussed in my presentation to NYLUG , I wanted to provide system administrations with some really quick analysis and performance fixes if you had limited knowledge of MySQL.

Improving the performance of a web system involves knowledge of how the entire technology stack operates and interacts.

I recently started playing with [devstack][1] again (An all-in-on OpenStack developer setup).

If you have ever met me personally at a presentation, or during consulting, or have read some of my blogs, publications or books the following statements are things I have been known to say.

If you run multiple MySQL environments on multiple servers it’s a good habit to set your MySQL prompt to double check which server you are on. however, using the MYSQL_PS1 environment variable I found this does not work under sudo (the normal way people r…

I currently have on a MySQL 5.6 database using innodb_file_per_table the following individual tablespace file. schema/FTS_00000000000001bb_BEING_DELETED.ibd The schema is all InnoDB tables, and there ARE NO Full Text Indexes.

Over the years you collect datasets you have created for various types of testing, seeding databases etc.

It is common practice to grant your application the privileges of “GRANT SELECT, INSERT, UPDATE, DELETE ON yourdb.* TO user@host”.

A recent database production migration with a large client highlighted a fundamental flaw in their designed architecture for suitable site availability.

In a recent discussion with a fellow peer reviewing a job description he was applying for, we got into a discussion on the specifics of a Performance Engineer verses a Scalability Engineer.

In writing about Performance and Scalability I referenced a quote that I have provided in a number of presentations regarding a valuable interaction with a client.

I recently came across an issue trying to connect to a MySQL server using the mysql client.

Next week the US celebrates Thanksgiving Day.

Translating theory to practice is never easy.

Using the MySQL 5.6 Performance Schema it is very easy to see what is actually running on your MySQL instance.

A client released a new version of their website onto 20 AWS m1.medium instances (current site at peak load runs approximately 60 m1.medium webservers).

Recently a client asked me how long it would take for an ALTER TABLE to complete.

The state of high speed internet providers in the “Capital of the World” is rather woeful.

Working with MySQL 5.6 under CentOS 6.4 I came across the following problem with MySQL reporting it did not shutdown successfully. $ sudo su - $ service mysql stop Shutting down MySQL.

The announcement of the MySQL Yum repositories was a long overdue request on my wish list.

A trap for those new to the MySQL Performance Schema is the expectation that thread_id in tables such as events_statements_current matches the id you find in the MySQL processlist.

Using MySQL 5.6.13 under CentOS 6.4, I had a replication failure on one master/slave topology because the master binary log had the following entry that was intentionally written by the MySQL server.

Last week I was a guest speaker at the second annual MySQL/NoSQL/Cloud Conference held in Buenos Aires, Argentina.

The “Too many connections” problem is a common issue with applications using excessive permissions (and those that grant said global permissions).

I had to laugh (just a bit) at this on the exhibitor floor at Oracle Open World 2013.

To expand on Jervin’s Default RDS Account Privileges , RDS for MySQL provides a number of routines and triggers defined the the ‘mysql’ meta schema.