DisconnectedServer » History » Version 5
Kyle Baker, 12/15/2014 10:16 AM
| 1 | 4 | Kyle Baker | h1. Disconnected Server |
|---|---|---|---|
| 2 | 1 | Kyle Baker | |
| 3 | h2. Summary |
||
| 4 | |||
| 5 | This is a template to start with. To create new feature, make up a URL of your preference and set Parent page (bellow the form) to *Features*. Write a summary, owners, current status and keep the page up to date. |
||
| 6 | |||
| 7 | h2. Targeted Release |
||
| 8 | |||
| 9 | 3 | Kyle Baker | Foreman 1.9 / Katello 2.3 |
| 10 | 1 | Kyle Baker | |
| 11 | h2. Trackers |
||
| 12 | |||
| 13 | -- |
||
| 14 | |||
| 15 | h2. Targeted Persona |
||
| 16 | |||
| 17 | 5 | Kyle Baker | [[Personas-SystemEngineer| Samuel - System Engineer]] |
| 18 | 1 | Kyle Baker | |
| 19 | h2. Status |
||
| 20 | 3 | Kyle Baker | |
| 21 | 2 | Kyle Baker | h3. User Stories |
| 22 | 1 | Kyle Baker | |
| 23 | Owner - David Caplan |
||
| 24 | Status - In Progress |
||
| 25 | 3 | Kyle Baker | Expected Delivery - TBD |
| 26 | 1 | Kyle Baker | Blockers - None |
| 27 | |||
| 28 | h3. Requirements |
||
| 29 | |||
| 30 | Owner - Mike Mccune / David Caplan |
||
| 31 | 3 | Kyle Baker | Status - Not Started |
| 32 | Expected Delivery - TBD |
||
| 33 | Blockers - Waiting on User Stories |
||
| 34 | 2 | Kyle Baker | |
| 35 | 1 | Kyle Baker | h3. Wireframes |
| 36 | |||
| 37 | Owner - Kyle Baker |
||
| 38 | 3 | Kyle Baker | Status - Not Started |
| 39 | Blockers - Waiting on User Stories & Requirements |
||
| 40 | Last updated - -- |
||
| 41 | 1 | Kyle Baker | |
| 42 | h3. Development Stories |
||
| 43 | 2 | Kyle Baker | |
| 44 | 1 | Kyle Baker | Owner - Foreman (TBD) Katello (TBD) |
| 45 | 3 | Kyle Baker | Status - Not Started |
| 46 | Expected Delivery - TBD |
||
| 47 | 1 | Kyle Baker | Blockers - Waiting on Wireframes |
| 48 | |||
| 49 | h2. Documentation |
||
| 50 | 3 | Kyle Baker | |
| 51 | 2 | Kyle Baker | h3. User Stories |
| 52 | 1 | Kyle Baker | |
| 53 | * Operational demands are too excessive |
||
| 54 | * +1 on Subs |
||
| 55 | * duplication of function |
||
| 56 | * Correction |
||
| 57 | ** Collapse the Sync Host functionality into Satellite and declare victory. |
||
| 58 | ** Parity with Satellite 5. Single workflow, export |
||
| 59 | ** Unrelated work to package CDN into ISOs as another means, satellite will be able to directly import these content ISOs. Alternate |
||
| 60 | * Export Content Views (Part 2) |
||
| 61 | * Workflows: Basic |
||
| 62 | ** Satellite Operator (a.k.a “Operator”) imports Manifest into Satellite 6 |
||
| 63 | ** Operator enables repos for syncing |
||
| 64 | ** Sync is started |
||
| 65 | ** After Sync is complete the Operator can immediately perform an export of the last sync of enable repos |
||
| 66 | *** Alternatively the Operator can add or remove existing enabled repos prior to the export |
||
| 67 | ** At any time the Operator can visit the repo table in the library and check off which products/packages are needed for export and then submit. |
||
| 68 | ** In all cases the Operator must specify a filesystem to the install and optionally indicate that the repo data be compressed |
||
| 69 | * Workflows: Advanced |
||
| 70 | ** The Operator can list all resources created on the Satellite by Organization |
||
| 71 | ** From this list the Operator can select resources to be packaged for export |
||
| 72 | ** The packaging process tracks dependencies with repos in the library |
||
| 73 | *** e.g. collections of CV’s selected for export will require specific repos in the library, those repos will be automatically included in the export |
||
| 74 | ** All exported meta-data is encrypted and can only be imported by a registered Satellite of the same version (or newer by 1 minor release 6.0 -> 6.1) |
||
| 75 | ** The export process creates a human readable export manifest that identifies each included resource type along with time stamps and other related meta-data |
||
| 76 | ** The exported bundle can then be imported into a registered Satellite in 2 stages |
||
| 77 | *** Stage 1: All content views appear in the library only |
||
| 78 | *** Stage 2: CV and CCV are auto published and promoted into matching environments (missing environments are auto created) |
||
| 79 | ** The exported bundle can be transported to the intended Satellite using SSL and a web service established just for this purpose. |
||
| 80 | ** The exported bundle can be simultaneously transported to multiple Satellites |
||
| 81 | ** All Export activity is logged |
||
| 82 | * Inter Sat sync is an HTTP connection |
||
| 83 | * Message bus application publish CV’s on the bus, satellite’s subscribe |
||
| 84 | |||
| 85 | 3 | Kyle Baker | h3. Requirements |
| 86 | |||
| 87 | * TBD |