Changes between Version 5 and Version 6 of Development/YumAndSPMA

Timestamp:

Mar 29, 2013, 5:33:31 PM (13 years ago)

Author:

munoz

Comment:

--

Development/YumAndSPMA

@@ -79 +79 @@
 Imagine this dependency graph, where green nodes are in the profile, yellow ones are dependencies that are not specified directly in the profile and red nodes are nodes that shall be removed:
 
+[[Image(deps.png)]]
 
 Both smithers and mrburns are specified directly in the profile.  But the distribution recalls that smithers depends on mrburns, so it adds a dependency. At the same time, we decide mrburns is not a critical part of our infrastructure, so we remove it from the profile:
 
-When the component kicks in, it looks at ''leaf'' packages that are not in the profile. Since `smithers` hasn't been updated, it runs this check against a system that looks like this:
+[[Image(deps-updated.png)]]
+
+When the component kicks in, it looks at ''leaf'' packages that are not in the profile.  These are the candidates to be removed. Since `smithers` hasn't been updated, it runs this check against a system that looks like this:
+
+[[Image(deps-intermediate.png)]]
 
 Thus, we'll schedule mrburns for removal. Our transaction will thus be:
@@ -92 +97 @@
 
 Which means this dependency graph:
+
+[[Image(deps-transaction.png)]]
 
 We cannot update smithers because mrburns will be removed!!  Curretly this requires manual intervention, or intermediate deployments.  Neither option is acceptable.