Jump to: navigation, search

Difference between revisions of "StarlingX/Developer Guide/Regional Mirror"

(Reference Mirror)
(Regional Mirror)
Line 5: Line 5:
 
===Reference Mirror===
 
===Reference Mirror===
  
Our Regional Office needs to create a Base Mirror which will perform a regular (daily?) automated download using existing methods. Call these Reference Mirror.
+
Our Regional Office needs to create a Reference Mirror which will perform a regular (daily?) automated download using existing methods.
 
The high level overview of activities to perform:
 
The high level overview of activities to perform:
  
* Base mirror
+
* Create the base mirror directory.
* User access
+
* Create automated update based on new packages from mirror download process.
 +
* Manage user access.
  
====Base Mirror====
+
===User Access===
Mirror based on daily
 
  
====General Access====
+
Upload your public key to your reference mirror server. <br>
  
# Create a Reference Mirror path
+
Create your regional mirror local directory
# Allow users to access the Reference Mirror path
 
 
 
====General Access====
 
 
 
Upload your public key to your Reference Mirror server. <br>
 
 
 
Create your regional mirror directory
 
 
<pre><nowiki>
 
<pre><nowiki>
 
user@workstation:~ $ mkdir ~/starlingx/mirror/regional/pike
 
user@workstation:~ $ mkdir ~/starlingx/mirror/regional/pike
 
</nowiki></pre>
 
</nowiki></pre>
  
Rsyncing it
+
Rsync it
  
 
<pre><nowiki>
 
<pre><nowiki>
Line 34: Line 27:
 
user@workstation:~/starlingx/mirror/regional/pike$ rsync -e "ssh -i /home/user/.ssh/id_rsa -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null" -avF mirror@starlingx-hub.zpn.intel.com:/mirror/mirror/ .
 
user@workstation:~/starlingx/mirror/regional/pike$ rsync -e "ssh -i /home/user/.ssh/id_rsa -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null" -avF mirror@starlingx-hub.zpn.intel.com:/mirror/mirror/ .
 
</nowiki></pre>
 
</nowiki></pre>
 +
 +
Copy tis-installer into your
  
 
<pre><nowiki>
 
<pre><nowiki>

Revision as of 15:55, 10 September 2018

Regional Mirror

Regional mirror will give us a Reference Mirror that can use to avoid downloading all packages from the Internet

Reference Mirror

Our Regional Office needs to create a Reference Mirror which will perform a regular (daily?) automated download using existing methods. The high level overview of activities to perform:

  • Create the base mirror directory.
  • Create automated update based on new packages from mirror download process.
  • Manage user access.

User Access

Upload your public key to your reference mirror server.

Create your regional mirror local directory

user@workstation:~ $ mkdir ~/starlingx/mirror/regional/pike

Rsync it

user@workstation:~$ cd ~/starlingx/mirror/regional/pike
user@workstation:~/starlingx/mirror/regional/pike$ rsync -e "ssh -i /home/user/.ssh/id_rsa -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null" -avF mirror@starlingx-hub.zpn.intel.com:/mirror/mirror/ .

Copy tis-installer into your

user@workstation:~/starlingx/mirror/regional/pike$ cp -r /home/user/starlingx/mirror/CentOS/tis-installer .

Once completed the directory structure should look like:

user@workstation:~/starlingx/mirror/regional/pike$ tree -L 1 .
.
├── Binary
├── check.lst
├── downloads
├── Source
└── tarballs.md5

4 directories, 2 files

Updating your references into the build container