Project

General

Profile

HostUnification » History » Version 9

Justin Sherrill, 05/04/2015 02:37 PM

1 1 Justin Sherrill
h1. Host Unification
2 2 Justin Sherrill
3
4 6 Justin Sherrill
h2. Goals
5 1 Justin Sherrill
6 6 Justin Sherrill
h3. Main Goal
7
8 1 Justin Sherrill
* Unify "Content Hosts" and Hosts so that they are one object based on a 'Host'.  The content and subscription portions simply become attributes/concerns/aspects of a Host object.
9 2 Justin Sherrill
10 6 Justin Sherrill
h3. Secondary Goals
11 1 Justin Sherrill
12 6 Justin Sherrill
* Create a supported API for katello content and subscription aspects of a host
13
* Plan and implement a generic way for Host objects to be split up and be plugable.  The host would have different aspects such as Puppet, Provisioning, & Content, any of which is optional.
14
15
h4. Goals not attempted
16
17
* Unified host UI
18 2 Justin Sherrill
19 3 Justin Sherrill
h2. Design
20 2 Justin Sherrill
21
h4. Ideal Design
22
We have presented two designs, one design based somewhat on this discussion:
23
24
https://groups.google.com/forum/#!searchin/foreman-dev/shim/foreman-dev/9ByQmAtKokQ/W2V924xqtYUJ
25
26 4 Justin Sherrill
!http://projects.theforeman.org/attachments/download/1239/aspect.png!
27 2 Justin Sherrill
28
The goal is to open a pull request with this design implemented for the Puppet related portion and if feedback is positive to proceed with the Content and Subscription portions.
29
30
h4. Fallback design:
31
32
If this does not go favourably, we present this alternative design which is very similar but simpler in nature:
33
34 1 Justin Sherrill
!http://projects.theforeman.org/attachments/download/1229/simple.png!
35 3 Justin Sherrill
36 9 Justin Sherrill
Host Group attributes today (Content view, Lifecycle Environment) would remain on the Host Group Object
37
38 3 Justin Sherrill
39
h2. Api/Cli changes
40
41
At a minimum, no api/cli changes would be needed and all functionality could remain with the proposed designs using existing controllers and cli commands.  However given that the current katello systems controller is 'deprecated', we greatly need to plan for a supported api.  Based on the discussions here: https://groups.google.com/forum/#!topic/foreman-dev/4Y4qxyknMwI
42
43 5 Justin Sherrill
There are currently two designs:
44
45 7 Justin Sherrill
h3. Unified Api Design
46 1 Justin Sherrill
47 7 Justin Sherrill
From a user perspective all aspects would appear as a single resource and would all be contained within that resource.  include[] could be passed on index and show to include the various aspects:
48 1 Justin Sherrill
49 7 Justin Sherrill
<pre>
50
   GET /api/v2/hosts?search="content_attr=foo"&include[]=content
51
   GET /api/v2/hosts/:id?include[]=content
52
   GET /api/v2/hosts/:id?include[]=subscriptions
53
   PUT /api/v2/hosts/:id/packages/install
54
</pre>
55 1 Justin Sherrill
56 7 Justin Sherrill
<pre>
57
  PUT /api/v2/hosts/3/  {'content_view_id': 5}
58
</pre>
59
60
Hammer commands:
61
62
<pre>
63
  hammer host details --id=3
64
  hammer host update --content-view=myView
65
  hammer host errata apply --host-id=3 --errata-ids=RHSA-2014:3
66
</pre>
67
68
69 5 Justin Sherrill
h3. Split Api
70
71 3 Justin Sherrill
The apis for interacting with the different aspects:
72
73
<pre>
74
   GET /api/v2/hosts?search="content_attr=foo"
75
   GET /api/v2/hosts/:id/content/
76 1 Justin Sherrill
   GET /api/v2/hosts/:id/subscription/
77 7 Justin Sherrill
   PUT /api/v2/hosts/:id/content/packages/install
78 3 Justin Sherrill
</pre>
79
80
  to update a host's content:
81
82
<pre>
83
  PUT /api/v2/hosts/3/  {'content_view_id': 5}
84
  OR
85
  PUT /api/v2/hosts/3/content {'content_view_id': 5}
86
</pre>
87
88
Sample hammer commands
89
90
<pre>
91
  hammer host content details --id=3
92
  hammer host content update --content-view=myView
93
  hammer host content errata apply --host-id=3 --errata-ids=RHSA-2014:3
94
</pre>
95
96
97
h2. User Stories (P1): 
98
99 1 Justin Sherrill
(1 man sprint = 20 points)
100
101 5 Justin Sherrill
* As a user, I should be able to create a host without a puppet environment (2)
102
* As a developer, I want to split out all puppet concerns to their own 'aspect' (10)
103 3 Justin Sherrill
* As a  user, i expect host create/update/delete to be dynflowed (wrapping the  AR action), via foreman_tasks or in core to allow plugins to hook into  CUD to interact with backend services (4)
104
* As a developer, i want to migrate the existing content host model to the new unified models for content and subscriptions (10)
105
* As a developer, I want to migrate all the existing content host dynflow  actions to use the new unified model (4)
106
* As a user, i want an upgrade provided to move existing content-hosts to the new unified models (4)
107
* As a developer, I want to pull system packages into the database (3)
108
* As a user, I should be able to search hosts by content attributes (2)
109
* As a user, I should be able to search hosts by subscription attributes (2)
110
* As a user, I expect subscription facts to live alongside puppet facts.  (4)
111
* As a user, I should be able to add & remove hosts to host collections instead of content-hosts (4)
112
* As a user, bulk actions should be based off hosts instead of content hosts (2)
113
* As a  user, I should be able to register a host with subscription-manager via username and password with the new data model, and a Host should be created (2)
114
* As a user, I should be able to register a host with subscription-manager via activation key with the new data model, and a Host should be created (2)
115 1 Justin Sherrill
* As a user, I should be able to register with subscription-manager to an existing host that has never registered with sub-man before (2)
116 3 Justin Sherrill
* As a user, I should be able to register with subscription-manager to an existing host that has previously registered with subscription-manager, and have the old registration be removed, generating a new UUID (2)
117
* As a user, virt-who should continue to work with the new unified model, including hypervisor registration.  An hypervisor registered through virt-who would have content capabilities. (5)
118 5 Justin Sherrill
* As a user, i expect package profile uploading to continue to work under the unified model (2)
119 3 Justin Sherrill
* As a user, i expect client actions (errata install, package install, etc..) to continue to work under the unified model (3)
120
* As a user, i expect the subscription and content aspects of hosts to be identified by their host id, not a uuid (3)
121
* As a user, i expect to be able to find the uuid of a host with subscriptions within the UI/hammer  (1)
122
* As a user, i expect to be able to search hosts by applicable errata (.5)
123
* As a user, i expect to be able to search hosts by installed package (.5)
124 1 Justin Sherrill
* As a user, i expect to be able to search hosts by subscription facts (.5)
125 3 Justin Sherrill
* As a user, i expect existing apis (and thus hammer commands and the UI) to continue to work under the new model, if new apis are not added (8)
126
127
H2. User Stories (P2)
128
129
* As a user, i expect an api for interacting with content and subscription aspects of hosts (6)
130 5 Justin Sherrill
* As  a developer, the content hosts UI needs to utilize new v2 apis for interacting with the subscription and content aspects of a host (8)
131 8 Justin Sherrill
* As a developer, I want to be able to inject attributes to display on an info command (4)
132
* As a developer, I want to be able to inject parameters into the GET request of a particular info command (8)
133
* As a user, I want to see content and subscription related items when running 'hammer host info' (1)
134 1 Justin Sherrill
* As a user, i expect the following hammer commands to be migrated:
135 8 Justin Sherrill
> * hammer content-host errata apply                      (.5)
136
> * hammer content-host errata info                     (.5)
137
> * hammer content-host errata list                        (.5)
138
> * hammer content-host package install                (.5)
139
> * hammer content-host package remove               (.5)
140
> * hammer content-host package upgrade           e (.5)
141
> * hammer content-host package upgrade-all         (.5)
142
> * hammer content-host package-group install      (.5)
143
> * hammer content-host package-group remove      (.5)
144
> * hammer content-host update   (for updating content view, lifecycle environment) (.5) 
145
> * hammer content-host update  (for updating service-level, release-version) (.5)
146 5 Justin Sherrill
> * hammer host puppet-classes (.5)
147
> * hammer host puppetrun (.5)
148
149
150
H2 User Stories (P3)
151 1 Justin Sherrill
* As a developer, I want to pull in subscriptions and related hosts into the database (7)
152
* As a user, I expect to search for hosts by their subscriptions (.5)