This repository has been archived by the owner on Apr 26, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
0 parents
commit 9d0388f
Showing
58 changed files
with
18,532 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,60 @@ | ||
# Byte-compiled / optimized / DLL files | ||
__pycache__/ | ||
*.py[cod] | ||
|
||
# C extensions | ||
*.so | ||
|
||
# Distribution / packaging | ||
.Python | ||
env/ | ||
build/ | ||
develop-eggs/ | ||
dist/ | ||
downloads/ | ||
eggs/ | ||
.eggs/ | ||
lib/ | ||
lib64/ | ||
parts/ | ||
sdist/ | ||
var/ | ||
*.egg-info/ | ||
.installed.cfg | ||
*.egg | ||
|
||
# PyInstaller | ||
# Usually these files are written by a python script from a template | ||
# before PyInstaller builds the exe, so as to inject date/other infos into it. | ||
*.manifest | ||
*.spec | ||
|
||
# Installer logs | ||
pip-log.txt | ||
pip-delete-this-directory.txt | ||
|
||
# Unit test / coverage reports | ||
htmlcov/ | ||
.tox/ | ||
.coverage | ||
.coverage.* | ||
.cache | ||
nosetests.xml | ||
coverage.xml | ||
*,cover | ||
|
||
# Translations | ||
*.mo | ||
*.pot | ||
|
||
# Django stuff: | ||
*.log | ||
|
||
# Sphinx documentation | ||
docs/_build/ | ||
|
||
# PyBuilder | ||
target/ | ||
|
||
#OVA images | ||
*.ova |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
0.1 01/29/2015 | ||
- Initial release | ||
- Support for creating local repos for offline updates | ||
|
||
0.2 04/07/2015 | ||
- VURA now creates ISO images for offline updates | ||
- Documentation improvements | ||
- Updated system packages | ||
- Improved ability to continue downloads |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,33 @@ | ||
About | ||
|
||
The VAMI Update Repository Appliance is a tool to help you create a portable update repository for VAMI-enabled VMware appliances. This allows you to transport the necessary bits to perform upgrades to network locations without internet access. | ||
|
||
Prerequisites: | ||
* VMware ESXi (www.vmware.com) | ||
* VMware vSphere client (www.vmware.com) | ||
* 7-zip (www.7-zip.org) | ||
|
||
Usage | ||
|
||
0. Extract vura.7z on a machine that can deploy VMs in your environment. | ||
1. Deploy the appliance image on a host and network with internet access. | ||
2. Configure the networking settings with SSH/Console access, if desired. The root password is "vura" by default. The system is Ubuntu in case you need to make adjustments that are not covered here. | ||
3. Expand the /data volume of this appliance by adding a disk and rebooting or using LVM. You can verify that the disk space has been added by typing "df -h" on the command line of the appliance. | ||
4. Navigate to the VAMI page of your desired appliance and locate the RepositoryURL on the Update>Settings tab. The page can usually be accessed by navigating to https://[Appliance IP Address]:5480. | ||
5. Copy the RepositoryURL from the VAMI appliance to the URL field on the web page of your vura appliance. | ||
6. Enter a repository name to help you identify the product name and version. No spaces, please. | ||
7. Press the Create button. | ||
8. Wait until the status under Current Repositories shows "Ready". | ||
9. Move this appliance to your desired network location. | ||
10a. Copy the URL of your new repo from the VURA status page into the VAMI Update page of your appliance. | ||
10b. Download the ISO image and attach it to your VM. The Update page | ||
11. Update and enjoy! | ||
|
||
Dependencies for running source version: | ||
*Linux | ||
*Nginx | ||
*fcgiwrap | ||
*python2 | ||
*coreutils | ||
*aria2c | ||
*genisoimage |
Binary file not shown.
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,44 @@ | ||
## VURA: The VAMI Update Repository Appliance ## | ||
|
||
About: | ||
----- | ||
|
||
The VAMI Update Repository Appliance is a tool to help you create a portable update repository for VAMI-enabled VMware appliances. This allows you to transport the necessary bits to perform upgrades to network locations without internet access. It can also help to generate update ISO images for appliances that do not have them available for download. | ||
|
||
Requirements: | ||
---- | ||
|
||
[Source Version] | ||
- Python 2.7 | ||
- Internet access for initial repository creation | ||
- User permission to bind port 80 | ||
- (Optional) genisoimage - If you wish to be able to generate ISO images | ||
|
||
[vApp Version] | ||
- ESXi 4.0U2+ | ||
- 1 vCPU | ||
- 512 MB RAM | ||
- 16 GB Disk Space (thick provisioned) | ||
- Internet access for initial repository creation | ||
|
||
Instructions | ||
---- | ||
[vApp Version] (recommended) | ||
1. Deploy vApp in location with internet access | ||
2. Obtain the Update URL from the administration page of your appliance (usually https:// [your appliance] :5480) | ||
3. Point your browser to the ip address of the VURA appliance | ||
4. Paste the URL in the URL field of the UI | ||
5. Give the repository a name without spaces or special characters | ||
6. Press the Create button | ||
7. You may now either download the ISO image and attach it to your VM to upgrade it, or paste the Update URL into the administration page of your appliance | ||
|
||
[Source Version] | ||
0. Ensure you have adequate disk space to host 2x the size of the update repository you will be downloading. You can assume it will be similar in size to the original OVA image you used to deploy it. | ||
1. Download source tree to a machine that has Python 2.7 | ||
2. Execute vura.py as a user that can bind port 80 | ||
3. Follow appliance instructions starting at Step 2 | ||
|
||
Technologies Used: | ||
- Python 2.7 | ||
- CherryPy | ||
- genisoimage |
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
Copyright (c) 2004-2011, CherryPy Team ([email protected]) | ||
All rights reserved. | ||
|
||
Redistribution and use in source and binary forms, with or without modification, | ||
are permitted provided that the following conditions are met: | ||
|
||
* Redistributions of source code must retain the above copyright notice, | ||
this list of conditions and the following disclaimer. | ||
* Redistributions in binary form must reproduce the above copyright notice, | ||
this list of conditions and the following disclaimer in the documentation | ||
and/or other materials provided with the distribution. | ||
* Neither the name of the CherryPy Team nor the names of its contributors | ||
may be used to endorse or promote products derived from this software | ||
without specific prior written permission. | ||
|
||
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND | ||
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED | ||
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE | ||
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE | ||
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL | ||
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR | ||
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER | ||
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, | ||
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE | ||
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. |
Oops, something went wrong.