summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorTrevor Cooper <trevor.cooper@intel.com>2015-06-03 21:18:45 +0000
committerTrevor Cooper <trevor.cooper@intel.com>2015-06-03 21:18:45 +0000
commitfbe7b63f6566190581aaf355e3e828f0cd0f9a11 (patch)
tree6a142bc1341f4daab8c71733dfcfb78f17a50590
parent15d71c2ed99d22d86996ec0f73b04868a77b7e87 (diff)
Minor edits
Change-Id: I28e47d5db1abf73789e7a3a124f069187cbdb966 Signed-off-by: Trevor Cooper <trevor.cooper@intel.com>
-rw-r--r--docs/pharos-spec.rst24
1 files changed, 13 insertions, 11 deletions
diff --git a/docs/pharos-spec.rst b/docs/pharos-spec.rst
index 1facb62..0597b41 100644
--- a/docs/pharos-spec.rst
+++ b/docs/pharos-spec.rst
@@ -120,16 +120,16 @@ Remote management
1. Developers to access deploy/test environments (credentials to be issued per POD / user)
2. Connection of each environment to Jenkins master hosted by Linux Foundation for automated deployment and test
-- VPN is optional and dependent on company security rules (out of Pharos scope)
+- OpenVPN is generally used for remote however community hosted labs may vary due to company security rules
- POD access rules / restrictions …
- - Refer to individual test-bed as each company may have different access rules and procedures
+ - Refer to individual test-bed as each company may have different access rules and acceptable usage policies
- Basic requirement is for SSH sessions to be established (initially on jump server)
-- Majority of packages installed on a system (tools or applications) will be pulled from an external storage solution so this type of things should be solved in a very general sense for the projects
-
-Firewall rules
+- Majority of packages installed on a system (tools or applications) will be pulled from an external repo so this scenario must be accomodated.
+Firewall rules should include
+
- SSH sessions
- Jenkins sessions
@@ -175,7 +175,7 @@ Test-bed network
Network Interfaces
-* Option 1: 4x1G Control, 2x40G Data, 48 Port Switch
+* Option I: 4x1G Control, 2x40G Data, 48 Port Switch
* 1 x 1G for ILMI (Lights out Management )
* 1 x 1G for Admin/PXE boot
@@ -195,22 +195,25 @@ Network Interfaces
* 2 x 10G for control plane connectivity/Storage
* 2 x 40G (or 10G) for data network
-** Topology **
-
+Documented configuration to include:
- Subnet, VLANs (may be constrained by existing lab setups or rules)
- IPs
- Types of NW - lights-out, public, private, admin, storage
- May be special NW requirements for performance related projects
- Default gateways
+
+Controller node bridge topology overview
+
.. image:: images/bridge1.png
-controller node bridge topology overview
+compute node bridge topology overview
.. image:: images/bridge2.png
-compute node bridge topology overview
+
+
Architecture
-------------
@@ -243,4 +246,3 @@ Revision: _sha1
Build date: _date
-