Project

General

Profile

MergeHosts » History » Version 2

Kyle Baker, 03/09/2015 04:13 PM

1 2 Kyle Baker
h1. Merge Hosts
2
3
h2. Summary/Goals
4
5
Merge Hosts and Content Hosts into a single unified presentation. The unification includes all aspects of displayed information and user initiated actions. The primary objective is designing hosts presentation and workflows that will accommodate user needs in a more efficiently and reflect user needs.
6
7
h2. Targeted Persona
8
9
* System Engineer - Responsible for configuring all of the infrastructure to provision hosts - which includes reprovisioning based on new builds
10
** http://projects.theforeman.org/projects/katello/wiki/Personas-SystemEngineer
11
* System Administrator - Responsible for deploying hosts to their portion of the companies managed infrastructure. Hosts are built based on the engineers configurations.
12
** http://projects.theforeman.org/projects/katello/wiki/Personas-SystemAdministrator
13
* Systems User - (Both System Engineer & System Administrator roles)
14
15
h2. Status
16
17
h3. Use Cases
18
19
Owner - David Caplan, Kyle Baker
20
Status - In Progress
21
Expected Delivery - 3/16/2015
22
Blockers - None
23
24
h3. Requirements 
25
26
Owner - David Caplan, Mike Mccune, Ohad Levy
27
Status - Not Started
28
Expected Delivery - TBD
29
Blockers - Waiting on User Stories
30
31
h3. Wireframes
32
33
Owner - Kyle Baker
34
Status - Not Started
35
Blockers - Waiting on User Stories & Requirements
36
Last updated TBD - Link to wireframes
37
38
h3. Development Stories
39
40
Owner - Mike Mccune, Ohad Levy
41
Status - Started based on previous efforts
42
Expected Delivery - N/A
43
Blockers - Waiting on Wireframes
44
45
h2. Documentation
46
47
h3. Assumptions
48
49
* Host entitlement status is a priority
50
* Context is not important for hosts
51
52
h3. Unknowns
53
54
* Need a single place where users can view host status and take action on hosts.
55
* The current process of provisioning a new host does not support the administrator role. Ideally the UI would hide all of the deeper configuration options and surface the options which have been pre configured by the engineer. Users have complained that the process is too complex when in reality the complexity simply exposed to the incorrect user.
56
* Pre-provisioning setup should include an option to build a boot ISO.
57
58
h3. Related Features
59
60
* Enabling Boot ISO - Feature coming soon
61
* Host Collections - Feature coming soon
62
63
h3. Use Cases
64
65
*Story 1 Host Monitoring*
66
A Systems User (System Engineer & System Administrator roles) would like to have a single place browse and understand the entirety of Linux hosts. *(1)* They are interested in finding out the status of a host or group of hosts in the infrastructure. *(2)* If there is an issue or scheduled update the Systems User needs the host's location and *(3)* to know the hosts software/business purpose.
67
68
* *(1) What is the status of this host or grouping of hosts?*
69
** 1. Configuration Status 
70
** 2. Last Report or Check In
71
** 3. Available Errata
72
** 4. Periodically, Subscription Status
73
* *(2) Where is this host running?*
74
** Capsule Information
75
** Organization
76
** Location
77
** Environment
78
** Host Group - For networking information
79
** Host Collection
80
* *(3) What is this host running? Is it performing a critical function?*
81
** Software Installed - OS, Errata
82
** Puppet Facts
83
** Content View Version
84
85
*Story 2 Host Detail*
86
A Systems User (System Engineer & System Administrator roles), During the identification/troubleshooting/updating process they need to examine the exact specs of a host to determine the best course of action.
87
* *Surface level Information*
88
** OS, mac, ip, serial number, environment, capsule, hostgroup, organization and location, host collections 
89
* *Drill down*
90
** hardware, software, networking, config, events, template, meta information
91
92
*Story 3 Host Actions*
93
A Systems User (System Engineer & System Administrator roles), During the troubleshooting/updating process I have identified which host or group of hosts I would like to take actions against.
94
Add or remove errata or packages
95
* Change the location, organization, environment association
96
* Change the host-group association
97
* Change the host-collections association
98
* Change the subscription status
99
* Change puppet environment association
100
101
*Story 4 Create New Host* 
102
*System Engineer*
103
When new software is released we define builds in the form of requirements/standards. We then present them to stakeholders. We then use the Katello/Foreman workflow process to build a deployable kickstart file. This file is used by the system administrator to stand up a machine.
104
* Preconfigure all infrastructure used in the host creation process
105
** Organization, Location, Environment, etc.
106
** Manage subscriptions and entitled content
107
** Create Content View
108
** Create Host Groups
109
** Create Activation keys
110
** Add networking services
111
*System Administrator*
112
As a System Administrator I want to easily add a new host leveraging all the configuration completed by the System Engineer
113
* Place in Infrastructure (Organization, Location, Environment)
114
* Assign networking services
115
* Choose Activation Key - If using the activation keys as the bridging element to map CVs to host groups
116
* Future - Clone an existing system. While creating a new host there should be a button to select a system I want to clone and as a second where I can adapt the pre-filled configurations (e.g. CV, HG, etc.)
117
118
h3. Future
119
120
* These features should be added as their own feature with their own specific user stories.
121
* comparing hosts
122
* dynamic host collections
123
* bookmark evolution
124
** Use search and bookmark functionality hosts to create a grouping
125
** Notes: Do the search and save as host collection
126
** See the detail of the search (new collection)
127
** Have search dynamically generate new list every time it runs
128
** View logs to view what changed
129
** Term 'Bookmark' is not appropriate there
130
** Bulk operations against hosts without managing another objects
131
* interlinking host objects (clicking a CV shows all the host with that CV)  then bookmarking
132
* Clone existing host
133
** Clone an existing system. While creating a new host there should be a button to select a system I want to clone and as a second where I can adapt the pre-filled configurations (e.g. CV, HG, etc.)
134
* History
135
** As a sysadmin I want to access from a single page the history of events that occurred for a specific system which may include:
136
** Puppet reports (+ be able to filter for drifts to easily identify changes on the system)
137
** Remote tasks execution results
138
** OpenScap compliance tests results
139
** Software management tasks (software installation, errata apply, etc...)
140
** DH: for each action inside the history I want to see a rollback of this particular action similar to Sat5.
141
 
142
h3. Requirements
143
144
* User stories will be broken down of the into specific actionable tasks to design and develop against.
145
146
h3. Development Stories
147
148
http://projects.theforeman.org/issues/8161