CapsuleCommunication » History » Version 15
Kyle Baker, 12/15/2014 10:17 AM
1 | 1 | Eric Helms | h1. Capsule - Server Communication via Proxy |
---|---|---|---|
2 | |||
3 | 13 | Kyle Baker | h2. Summary |
4 | |||
5 | 1 | Eric Helms | All inbound and outbound Capsule communication should be routable through a proxy. This is the case where a Capsule cannot directly route it’s traffic to the server nor can the server directly reach the Capsule. If we allow only proxying Capsule content syncing from the Foreman/Katello and a user locks down a Capsule’s HTTP traffic, this could break other functionality of the Capsule See diagram below. |
6 | |||
7 | 13 | Kyle Baker | !{width: 50%}http://projects.theforeman.org/attachments/download/999/capsule_server_proxy.png! |
8 | |||
9 | h2. Targeted Release |
||
10 | |||
11 | 14 | Kyle Baker | Foreman 1.9 / Katello 2.3 |
12 | 13 | Kyle Baker | |
13 | h2. Trackers |
||
14 | |||
15 | 1 | Eric Helms | https://bugzilla.redhat.com/show_bug.cgi?id=1114083 |
16 | |||
17 | 13 | Kyle Baker | h2. Targeted Persona |
18 | 1 | Eric Helms | |
19 | 15 | Kyle Baker | [[Personas-SystemEngineer| Samuel - System Engineer]] |
20 | 1 | Eric Helms | |
21 | 13 | Kyle Baker | h2. Status |
22 | 1 | Eric Helms | |
23 | 13 | Kyle Baker | h3. User Stories |
24 | |||
25 | Owner - David Caplan |
||
26 | Status - In Progress |
||
27 | Blockers - None |
||
28 | |||
29 | h3. Requirements |
||
30 | |||
31 | Owner - Mike Mccune / David Caplan |
||
32 | Status - In Progress |
||
33 | Blockers - None |
||
34 | |||
35 | h3. Wireframes |
||
36 | |||
37 | Owner - Kyle Baker |
||
38 | Status - Not Started |
||
39 | Blockers - Waiting on User Stories & Requirements |
||
40 | Last updated TBD - -- |
||
41 | |||
42 | h3. Development Stories |
||
43 | |||
44 | Owner - Walden Raines |
||
45 | Status - Not Started |
||
46 | Expected Delivery - TBD |
||
47 | Blockers - Waiting on Wireframes |
||
48 | |||
49 | h2. Documentation |
||
50 | |||
51 | h3. User Stories |
||
52 | |||
53 | h4. Capsule to Server |
||
54 | |||
55 | 1 | Eric Helms | * Pulp node syncing content from the server |
56 | * Puppet master reporting |
||
57 | * Qpid traffic (if client communication is routed through the Capsule) |
||
58 | * Sub-man traffic being routed via reverse-proxy to the Capsule |
||
59 | |||
60 | 13 | Kyle Baker | h4. Server to Capsule |
61 | 1 | Eric Helms | |
62 | * Initial creation and discovery of the Capsule |
||
63 | * Feature refresh of the Capsule |
||
64 | * Qpid traffic (if client communication is routed through the Capsule) |
||
65 | 13 | Kyle Baker | |
66 | 1 | Eric Helms | h3. Requirements |
67 | |||
68 | # Capsules should support individual proxy configurations server side |
||
69 | # Capsule puppet masters should support routing traffic through an HTTP proxy |
||
70 | # Qpid should support routing traffic through a proxy on the Server or Capsule |
||
71 | # Capsule reverse proxy should support routing through an external HTTP proxy |
||
72 | 13 | Kyle Baker | |
73 | h3. Development Stories |
||
74 | |||
75 | -- |