Add database schema management using Alembic

This patch replaces contrib/realtime/ with a new setup for managing the
database schema required for database integration with Asterisk.  In
addition to initializing a database with the proper schema, alembic can do a
database migration to assist with upgrading Asterisk in the future.
Hopefully this helps make setting up and operating Asterisk with a database
easier.

With this the schema only needs to be maintained in one place instead of
once per database.  The schemas I have added here have a bit of improvement
over the examples that were there before (some added consistency and added
some missing indexes).  Managing the schema in one place here also applies
to all databases supported by SQLAlchemy.

See contrib/ast-db-manage/README.md for more details.

Review: https://reviewboard.asterisk.org/r/2731

patch by Russell Bryant (license 6300)
........

Merged revisions 397874 from http://svn.asterisk.org/svn/asterisk/branches/12


git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@397875 65c4cc65-6c06-0410-ace0-fbb531ad65f3

1 files changed, 0 insertions, 21 deletions

diff --git a/contrib/realtime/mysql/meetme.sql b/contrib/realtime/mysql/meetme.sql
index 5a1bac4bf..e69de29bb 100644
--- a/contrib/realtime/mysql/meetme.sql
+++ b/contrib/realtime/mysql/meetme.sql
@@ -1,21 +0,0 @@
--- 
--- Table structure for Realtime meetme
--- 
-
-CREATE TABLE meetme (
-	bookid int(11) auto_increment,
-	confno char(80) DEFAULT '0' NOT NULL,
-	starttime datetime default '1900-01-01 12:00:00',
-	endtime datetime default '2038-01-01 12:00:00',
-	pin char(20) NULL,
-	adminpin char(20) NULL,
-	opts char(20) NULL,
-	adminopts char(20) NULL,
-	recordingfilename char(80) NULL,
-	recordingformat char(10) NULL,
-	maxusers int(11) NULL,
-	members integer DEFAULT 0 NOT NULL,
-	index confno (confno,starttime,endtime),
-	PRIMARY KEY (bookid)
-);
-