Heya, I've merged both approaches. First, I dropped the db on my development server, and then let puppet recreate it. Since I don;t want to lose my historical data in production, I then dumped and compared the schema's from the dev (2.6.7) and prod (2.6.2) environments. I then upgraded prod to 2.6.7 and applied the diff.
For what it's worth, here's the SQL I had to execute. Usual disclaimers on you mileage here :) ALTER TABLE resources ADD KEY `exported_restype_title` (`exported`,`restype`,`title`(50)); CREATE TABLE `inventory_facts` ( `node_id` int(11) NOT NULL, `name` varchar(255) NOT NULL, `value` text NOT NULL, UNIQUE KEY `index_inventory_facts_on_node_id_and_name` (`node_id`,`name`) ENGINE=InnoDB DEFAULT CHARSET=utf8; CREATE TABLE `inventory_nodes` ( `id` int(11) NOT NULL AUTO_INCREMENT, `name` varchar(255) NOT NULL, `timestamp` datetime NOT NULL, `updated_at` datetime DEFAULT NULL, `created_at` datetime DEFAULT NULL, PRIMARY KEY (`id`), UNIQUE KEY `index_inventory_nodes_on_name` (`name`) ENGINE=InnoDB AUTO_INCREMENT=4 DEFAULT CHARSET=utf8; I can see data going into the DB from the latest runs, and I can curl the inventory service, so it seems ok. Setting up Dashboard 1.1.0 as we speak :) HTH, Greg -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
