Project

General

Profile

MergeHosts » History » Version 5

Kyle Baker, 03/10/2015 02:24 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 3 Kyle Baker
*System Engineer*
10
Responsible for configuring all of the infrastructure to provision hosts - which includes reprovisioning based on new builds
11
* http://projects.theforeman.org/projects/katello/wiki/Personas-SystemEngineer
12 1 Kyle Baker
13 3 Kyle Baker
*System Administrator*
14
Responsible for deploying hosts to their portion of the companies managed infrastructure. Hosts are built based on the engineers configurations.
15
* http://projects.theforeman.org/projects/katello/wiki/Personas-SystemAdministrator
16
17
*Systems User*
18
(Both System Engineer & System Administrator roles)
19
20 2 Kyle Baker
h2. Status
21
22
h3. Use Cases
23
24
Owner - David Caplan, Kyle Baker
25
Status - In Progress
26
Expected Delivery - 3/16/2015
27
Blockers - None
28
29
h3. Requirements 
30
31
Owner - David Caplan, Mike Mccune, Ohad Levy
32
Status - Not Started
33
Expected Delivery - TBD
34
Blockers - Waiting on User Stories
35
36
h3. Wireframes
37
38
Owner - Kyle Baker
39
Status - Not Started
40
Blockers - Waiting on User Stories & Requirements
41
Last updated TBD - Link to wireframes
42
43
h3. Development Stories
44
45
Owner - Mike Mccune, Ohad Levy
46
Status - Started based on previous efforts
47
Expected Delivery - N/A
48
Blockers - Waiting on Wireframes
49
50
h2. Documentation
51
52
h3. Assumptions
53
54
* Host entitlement status is a priority
55
* Context is not important for hosts
56
57
h3. Unknowns
58
59
* Need a single place where users can view host status and take action on hosts.
60
* 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.
61
* Pre-provisioning setup should include an option to build a boot ISO.
62
63
h3. Related Features
64
65
* Enabling Boot ISO - Feature coming soon
66
* Host Collections - Feature coming soon
67
68
h3. Use Cases
69
70
*Story 1 Host Monitoring*
71
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.
72
73
* *(1) What is the status of this host or grouping of hosts?*
74
** 1. Configuration Status 
75
** 2. Last Report or Check In
76
** 3. Available Errata
77
** 4. Periodically, Subscription Status
78
* *(2) Where is this host running?*
79
** Capsule Information
80
** Organization
81
** Location
82
** Environment
83
** Host Group - For networking information
84
** Host Collection
85
* *(3) What is this host running? Is it performing a critical function?*
86
** Software Installed - OS, Errata
87
** Puppet Facts
88
** Content View Version
89
90
*Story 2 Host Detail*
91
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.
92
* *Surface level Information*
93 4 Kyle Baker
** OS, mac(s), ip(s), serial number, environment, capsule, host-group (puppet module), organization and location, host collections 
94 2 Kyle Baker
* *Drill down*
95 4 Kyle Baker
** hardware, software, networking, config, events, template(s), meta information, hypervisor
96 2 Kyle Baker
97
*Story 3 Host Actions*
98
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.
99
Add or remove errata or packages
100
* Change the location, organization, environment association
101
* Change the host-group association
102
* Change the host-collections association
103 1 Kyle Baker
* Change the subscription status
104 2 Kyle Baker
* Change puppet environment association
105 4 Kyle Baker
* Change compute resource - If deployed on compute resource yet
106 2 Kyle Baker
107
*Story 4 Create New Host* 
108
*System Engineer*
109
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.
110 5 Kyle Baker
* This infrastructure is preconfigured by the System Engineer before the host creation process
111 2 Kyle Baker
** Organization, Location, Environment, etc.
112 1 Kyle Baker
** Manage subscriptions and entitled content
113 5 Kyle Baker
** Create, publish, promote Content View 
114 2 Kyle Baker
** Create Host Groups
115
** Create Activation keys
116
** Add networking services
117 3 Kyle Baker
118 2 Kyle Baker
*System Administrator*
119
As a System Administrator I want to easily add a new host leveraging all the configuration completed by the System Engineer
120
* Place in Infrastructure (Organization, Location, Environment)
121 1 Kyle Baker
* Assign networking services
122 2 Kyle Baker
* Choose Activation Key - If using the activation keys as the bridging element to map CVs to host groups
123 4 Kyle Baker
* Apply host to run on authorized compute resource
124 2 Kyle Baker
* 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.)
125
126
h3. Future
127
128
* These features should be added as their own feature with their own specific user stories.
129
* comparing hosts
130
* dynamic host collections
131
* bookmark evolution
132
** Use search and bookmark functionality hosts to create a grouping
133
** Notes: Do the search and save as host collection
134
** See the detail of the search (new collection)
135
** Have search dynamically generate new list every time it runs
136
** View logs to view what changed
137
** Term 'Bookmark' is not appropriate there
138
** Bulk operations against hosts without managing another objects
139
* interlinking host objects (clicking a CV shows all the host with that CV)  then bookmarking
140
* Clone existing host
141
** 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.)
142
* History
143
** As a sysadmin I want to access from a single page the history of events that occurred for a specific system which may include:
144
** Puppet reports (+ be able to filter for drifts to easily identify changes on the system)
145
** Remote tasks execution results
146
** OpenScap compliance tests results
147
** Software management tasks (software installation, errata apply, etc...)
148
** DH: for each action inside the history I want to see a rollback of this particular action similar to Sat5.
149
 
150
h3. Requirements
151
152
* User stories will be broken down of the into specific actionable tasks to design and develop against.
153
154
h3. Development Stories
155
156
http://projects.theforeman.org/issues/8161