= problem = we frequently forget about pt boxes and often so do the folks who requested their use.
= analysis = A tool to let us register/track them and send reminders about their expiration, etc would help us tremendously.
= enhancement recommendation =
A script with a simple db that lets us track this info and query it to send notifications to us and the project owners that the instance is being expired, etc. It will help us keep the pt boxes tidy and secure.
Tasks: 1) Identify data we want stored. 2) Create schema. 3) Identify actions we want to be able to perform. 4) Write command-line script run actions. 5) Ship it!
1) Identify data we want stored.[[BR]]
REQUESTS[[BR]] id [[BR]] who (fas account) [[BR]] purpose (text) [[BR]] system name (varchar) [[BR]] request date (timestamp) [[BR]] expiration date (date)
2) Create Schema[[BR]] [[BR]] create database mcpita; [[BR]] use database mcpita;[[BR]] CREATE TABLE requests ( id int(10) unsigned NOT NULL AUTO_INCREMENT, who varchar(255) NOT NULL DEFAULT '', purpose text NOT NULL, system_name varchar(255) NOT NULL DEFAULT '', request_date timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP, expiration_date datetime NOT NULL DEFAULT '0000-00-00 00:00:00', PRIMARY KEY (id) ) ENGINE=InnoDB DEFAULT CHARSET=utf8; [[BR]]
requests
id
who
purpose
system_name
request_date
expiration_date
Replying to [comment:4 addutko]:
2) Create Schema[[BR]]
The previous DDS is for MySQL/MariaDB. A suggestion was made to use sqllite. I'll setup the tool for use on both.
An intial version is posted on my people page at: http://addutko.fedorapeople.org. The project is called mcpita.
Awaiting feedback from skvidal and other infrastructure folks.
This sort of fell through the cracks. ;(
We are moving away from generic publictest machines and going to 'applicationname.dev' type instances. So, not sure this is needed anymore.
Thoughts?
I'm going to just close this now, reopen if I forgot something.
Log in to comment on this ticket.