Commit 6320d24b authored by David Johnson's avatar David Johnson

Add the outlets_remoteauth table which contains keys for asf/ipmi stuff.

parent d31ab2bd
......@@ -2085,6 +2085,20 @@ CREATE TABLE `outlets` (
PRIMARY KEY (`node_id`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1;
--
-- Table structure for table `outlets_remoteauth`
--
DROP TABLE IF EXISTS `outlets_remoteauth`;
CREATE TABLE `outlets_remoteauth` (
`node_id` varchar(32) NOT NULL,
`key_type` varchar(64) NOT NULL,
`key_role` varchar(64) NOT NULL default '',
`key_uid` varchar(64) NOT NULL default '',
`mykey` text NOT NULL,
PRIMARY KEY (`node_id`,`key_type`,`key_role`,`key_uid`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1;
--
-- Table structure for table `partitions`
--
......
......@@ -3903,3 +3903,20 @@ last_net_act,last_cpu_act,last_ext_act);
'instance_description', 'run_description') default NULL;
4.107: Fix to previous revision; skip to next entry.
4.108: Add a table to store remote power cycling keys. Should do fine for ASF
or IPMI. Neither key_role nor key_uid is numeric since different specs
define the notions of roles and uids differently. The auth_meta field
provides some expandability for additional operational metadata down the
road.
DROP TABLE IF EXISTS `outlets_remoteauth`;
CREATE TABLE `outlets_remoteauth` (
`node_id` varchar(32) NOT NULL,
`key_type` varchar(64) NOT NULL,
`key_role` varchar(64) NOT NULL default '',
`key_uid` varchar(64) NOT NULL default '',
`mykey` text NOT NULL,
PRIMARY KEY (`node_id`,`key_type`,`key_role`,`key_uid`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1;
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment