Jump to: navigation, search

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

(→‎Base Mirror)
(→‎Reference Mirror)
Line 7: Line 7:
 
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 Base Mirror which will perform a regular (daily?) automated download using existing methods. Call these Reference Mirror.
 
The high level overview of activities to perform:
 
The high level overview of activities to perform:
 +
 +
* Base mirror
 +
* User access
 +
 +
====Base Mirror====
 +
Mirror based on daily
  
 
====General Access====
 
====General Access====
 +
 
# Create a Reference Mirror path
 
# Create a Reference Mirror path
 
# Allow users to access the Reference Mirror path
 
# Allow users to access the Reference Mirror path
  
 +
====General Access====
  
−
====Automated Download====
+
Upload your public key to your Reference Mirror server. <br>
  
−
# Clone stx-tools
+
Create your regional mirror directory
−
# Execute download_mirror.sh
+
<pre><nowiki>
−
#
+
user@workstation:~ $ mkdir ~/starlingx/mirror/regional/pike
−
#
+
</nowiki></pre>
−
https://wiki.openstack.org/wiki/StarlingX/Developer_Guide#Build_the_CentOS_Mirror_Repository
 
  
−
Run the libvirt qemu setup script:
+
Rsyncing it
  
 
<pre><nowiki>
 
<pre><nowiki>
−
$ bash setup_all_in_one.sh
+
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/ .
 
</nowiki></pre>
 
</nowiki></pre>
 +
 +
<pre><nowiki>
 +
user@workstation:~/starlingx/mirror/regional/pike$ cp -r /home/user/starlingx/mirror/CentOS/tis-installer .
 +
</nowiki></pre>
 +
 +
Once completed the directory structure should look like:
 +
 +
<pre><nowiki>
 +
user@workstation:~/starlingx/mirror/regional/pike$ tree -L 1 .
 +
.
 +
├── Binary
 +
├── check.lst
 +
├── downloads
 +
├── Source
 +
└── tarballs.md5
 +
 +
4 directories, 2 files
 +
</nowiki></pre>
 +
 +
Updating your references into the build container

Revision as of 15:23, 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 Base Mirror which will perform a regular (daily?) automated download using existing methods. Call these Reference Mirror. The high level overview of activities to perform:

  • Base mirror
  • User access

Base Mirror

Mirror based on daily

General Access

  1. Create a Reference Mirror path
  2. Allow users to access the Reference Mirror path

General Access

Upload your public key to your Reference Mirror server.

Create your regional mirror directory 

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

Rsyncing 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/ .

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

Retrieved from "https://wiki.openstack.org/w/index.php?title=StarlingX/Developer_Guide/Regional_Mirror&oldid=164638"