Replace bintray with https://packages.vmware.com/
Change-Id: Ibffdf4c0f3fcb6b9838d7b80ec6652cc19fe773d Reviewed-on: http://photon-jenkins.eng.vmware.com:8082/11731 Tested-by: gerrit-photon <photon-checkins@vmware.com> Reviewed-by: Alexey Makhalov <amakhalov@vmware.com>
This commit is contained in:
michellew-vmware
Alexey Makhalov
parent
cd04bbbda9
commit
83541fa213
46
CHANGELOG.md
46
CHANGELOG.md
|
|
@ -1,67 +1,71 @@
|
|||
- [Updated OVAs for CVE-2016-5333](#updated-ovas-for-CVE20165333)
|
||||
|
||||
- [v1.0](#v1.0)
|
||||
- [v3.0rev2](#v3.0rev2)
|
||||
- [Downloads](#downloads)
|
||||
- [Highlights](#highlights)
|
||||
- [Known Issues](#known-issues)
|
||||
|
||||
## Updated OVAs for CVE-2016-5333
|
||||
|
||||
A public ssh key used in the Photon OS build environment was inadvertently left in the original Photon OS 1.0 OVAs.
|
||||
This issue would have allowed the corresponding private key to access any Photon OS system built from the original 1.0 OVAs.
|
||||
A public ssh key used in the Photon OS build environment was inadvertently left in the original Photon OS 3.0 OVAs.
|
||||
This issue would have allowed the corresponding private key to access any Photon OS system built from the original 3.0 OVAs.
|
||||
|
||||
The issue was discovered internally and the original OVAs have been replaced by updated OVAs. All instances of this private key have been deleted within VMware.
|
||||
|
||||
Customers that have downloaded the PhotonOS 1.0 OVAs before August 14, 2016 should take either of the following procedures to ensure the security of their systems:
|
||||
Customers that have downloaded the PhotonOS 3.0 OVAs before August 14, 2016 should take either of the following procedures to ensure the security of their systems:
|
||||
|
||||
- Remove the left-over public key from all Photon OS 1.0 systems built from the original PhotonOS 1.0 OVAs by executing the following command:
|
||||
- Remove the left-over public key from all Photon OS 3.0 systems built from the original PhotonOS 3.0 OVAs by executing the following command:
|
||||
- On a freshly installed Photon OS system:
|
||||
|
||||
```rm –f /root/.ssh/authorized_keys```
|
||||
- On a Photon OS system which contains user-installed ssh keys:
|
||||
- On a Photon OS system which contains user-installed ssh keys:
|
||||
|
||||
```sed –i '/photon-jenkins/d' /root/.ssh/authorized_keys```
|
||||
- Alternatively, download the new OVA and replace all existing instances with new instances built from the updated Photon OS 1.0 OVAs.
|
||||
- Alternatively, download the new OVA and replace all existing instances with new instances built from the updated Photon OS 3.0 OVAs.
|
||||
|
||||
To confirm that the left-over public key is not present and that the issue is resolved, the following command should not produce any output:
|
||||
|
||||
```cat /root/.ssh/authorized_keys | grep photon-jenkins```
|
||||
|
||||
This issue is only present in the original Photon OS 1.0 OVAs and is not present in other Photon OS deliverables.
|
||||
This issue is only present in the original Photon OS 3.0 OVAs and is not present in other Photon OS deliverables.
|
||||
|
||||
The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the identifier CVE-2016-5333 to this issue.
|
||||
|
||||
# v 1.0
|
||||
# v 3.0rev2
|
||||
|
||||
## Downloads
|
||||
| Download | Size | sha1 checksum | md5 checksum |
|
||||
| --- | --- | --- | --- |
|
||||
| [Full ISO](https://bintray.com/artifact/download/vmware/photon/photon-1.0-13c08b6.iso) | 2.1GB | a3acb6922c93e2b0cdc186abd5352bb0e61b986b | 60225fb97e6a702864795743db197335 |
|
||||
| [OVA with virtual hardware v10](https://bintray.com/artifact/download/vmware/photon/photon-custom-hw10-1.0-13c08b6-GA.ova) | 199.8MB | 91760496427b277942fb9492fd48938cfc374edd | d8d02667a869c973ef7aa5c25d207748 |
|
||||
| [OVA with virtual hardware v11](https://bintray.com/artifact/download/vmware/photon/photon-custom-hw11-1.0-13c08b6-GA.ova) | 199.8MB | 2cd6e4ff31f901f1b97aca279404d7ddaf42f44d | d30309abb4bec167d8c79daee6045dd4 |
|
||||
| [Amazon AMI] (https://bintray.com/artifact/download/vmware/photon/photon-ami-1.0-13c08b6.tar.gz) | 148.5MB | e111281baabe82beaafcb6a3e17e6aec86c4acf6 | 0d2b86deca6d29323dc4877cf05c6bcc |
|
||||
| [Google GCE] (https://bintray.com/artifact/download/vmware/photon/photon-gce-1.0-13c08b6.tar.gz) | 411.7MB | 6d0e6f52379fedeb22b744aabaf681e8cc5e4fbe | af9d0e8e44c4d0a031b694885acde540 |
|
||||
| [Full ISO x86_64](https://packages.vmware.com/photon/3.0/Rev2/iso/photon-3.0-58f9c74.iso) | 5.2G | 545a9d0d53cb2109381bd9ae9eb837579f2ef1ee | 2ece2dfcdcdf098e36100a2085937dca |
|
||||
| [Minimal ISO x86_64](https://packages.vmware.com/photon/3.0/Rev2/iso/photon-minimal-3.0-58f9c74.iso) | 280M | ae28558e57f5d8aefb8b479c9fac7473079156e1 | 187dfb1e6bc5e47606c667e9042f86a4 |
|
||||
| [Full ISO arm64](https://packages.vmware.com/photon/3.0/Rev2/iso/photon-3.0-58f9c743-aarch64.iso) | 3.5G | 16848687d4d7cf393a413f3a24728b2cf042191d | 46d929c644debd27ee9fd37d35046921 |
|
||||
| [OVA with virtual hardware v11](https://packages.vmware.com/photon/3.0/Rev2/ova/photon-hw11-3.0-9355405.ova) | 169M | f4c22463e4567e6cd9becdbb2a178b4b916ffff9 | 514e9d9597eea5f1694df9717cffb80b |
|
||||
| [OVA with virtual hardware v13 (UEFI Secure Boot)](https://packages.vmware.com/photon/3.0/Rev2/ova/photon-hw13_uefi-3.0-9355405.ova) | 165M | 7cea6b552c66a6ceb6e8023938f9788179d8f697 | 6a24a68b1e56ee35c4a20$
|
||||
| [Amazon AMI](https://packages.vmware.com/photon/3.0/Rev2/ami/photon-ami-3.0-9355405.tar.gz ) | 172M | 85949657c857fee6a4417ca72ec010da81ed09e9 | e80bd2f0991a5091d83b3b3ae6e100df |
|
||||
| [Google GCE](https://packages.vmware.com/photon/3.0/Rev2/gce/photon-gce-3.0-9355405.tar.gz) | 456M | a97425523518a54a6e20114419cb6fb0e5900039 | c5cffb418372b72bb48a66549ee25fbf |
|
||||
| [Azure VHD](https://packages.vmware.com/photon/3.0/Rev2/azure/photon-azure-3.0-9355405.vhd.tar.gz) | 180M | c2a5438574f0b8b62d792042c7edfb655f61acdf | 24b70b81f7e3cb026e4e43bcb0650a5f |
|
||||
| [Raspberry Pi3 Image](https://packages.vmware.com/photon/3.0/Rev2/rpi3/photon-rpi3-3.0-9355405.tar.xz) | 61M | 9f44bde819862eeb0c6cbfcd06fab6a48ba36594| 2ca56e575e37fc7b911dd934e5089432 |
|
||||
|
||||
## Highlights
|
||||
- tdnf adds support for "distro-sync" - giving a single operation to apply updates to all installed packages that have updates in the Photon OS repos.
|
||||
- Many new packages available for Photon OS!
|
||||
- Photon OS 1.0 contains the 4.4 LTS kernel
|
||||
- Photon OS 3.0 contains the 4.4 LTS kernel
|
||||
|
||||
## Known Issues
|
||||
|
||||
- Photon OS 1.0 does not respond immediately to the new FQDN after changing the hostname. This issue will occur when there is no valid DNS system configured. This is being investigated.
|
||||
- Photon OS 3.0 does not respond immediately to the new FQDN after changing the hostname. This issue will occur when there is no valid DNS system configured. This is being investigated.
|
||||
- Workaround: To resolve this issue, restart systemd-resolved.
|
||||
|
||||
- Photon OS 1.0 requires at least 512MB of RAM when installing from ISO on ESXi.
|
||||
- Workaround: While on VMware Workstation and VMware Fusion, Photon OS 1.0 can install ISO and run in as little as 384MB of RAM (default). assign at least 512MB of RAM when installing from ISO on ESXi, as installer may fail in less memory. The default for ESXi is 2GB and most users will not be affected by this issue. The root cause is being investigated.
|
||||
- Photon OS 3.0 requires at least 512MB of RAM when installing from ISO on ESXi.
|
||||
- Workaround: While on VMware Workstation and VMware Fusion, Photon OS 3.0 can install ISO and run in as little as 384MB of RAM (default). assign at least 512MB of RAM when installing from ISO on ESXi, as installer may fail in less memory. The default for ESXi is 2GB and most users will not be affected by this issue. The root cause is being investigated.
|
||||
|
||||
- When using a combination of different network cards in Photon OS 1.0, the interfaces may be swapped after a reboot.
|
||||
- When using a combination of different network cards in Photon OS 3.0, the interfaces may be swapped after a reboot.
|
||||
- Workaround: Use the same type of virtual NIC for all interfaces. This happens because the devices are probed in increasing PCI slot address order upon boot. E1000 devices reside in 02:00.0 and above, while VMXNET3 devices will be placed into 03:00.0 and above. Upon reboot, the E1000 device(s) will always be assigned eth numbers than VMXNET3, regardless of configuration. Users might encounter this issue because VMXNET3 is the default adapter type within Photon OS, but older versions of VMware products might offer only E1000 devices when adding a secondary interface.
|
||||
|
||||
- When using multiple network cards without a valid DNS configuration and functional DNS server, initiating a ping might take 7-8 seconds to start. This happens because of multiple DNS timeouts on the interfaces.
|
||||
- Workaround: To avoid this issue, ensure that you've got a valid DNS configuration and a functioning DNS server that is capable of resolving the hostname(s) that are being pinged.
|
||||
|
||||
- When using vSphere Guest Customization to set the hostname of a Photon OS 1.0 instance, the hostname may revert to the randomly-generated hostname after a reboot.
|
||||
- When using vSphere Guest Customization to set the hostname of a Photon OS 3.0 instance, the hostname may revert to the randomly-generated hostname after a reboot.
|
||||
- Workaround: We are testing an update to our open-vm-tools rpm to resolve this issue. In the meantime, you can manually resolve this issue by deleting /var/lib/cloud/seed folder after applying guest customization.
|
||||
|
||||
- Ordering within /etc/hosts makes IPv6 preferred, which impacts connectivity for applications that are not configured for IPv6.
|
||||
|
|
@ -70,5 +74,5 @@ The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned th
|
|||
- The default umask permissions are 0027 and may cause some permissions issues with operations executed as root or through sudo.
|
||||
- Workaround: Change the umask settings to 022 by entering, "umask 022" within a Photon OS instance. To make the umask change persistent across reboots, edit /etc/profile and change the umask setting to 0022.
|
||||
|
||||
- In the 1.0 release, Photon OS firewall settings have been changed to a default of DROP, which might cause services installed in Photon OS to be unreachable externally.
|
||||
- In the 3.0 release, Photon OS firewall settings have been changed to a default of DROP, which might cause services installed in Photon OS to be unreachable externally.
|
||||
- Workaround: To address this, administrators must configure their firewall rules appropriately to expose service ports as required for installed applications or containers.
|
||||
|
|
|
|||
|
|
@ -1,14 +1,14 @@
|
|||
Summary: Ant contrib
|
||||
Name: ant-contrib
|
||||
Version: 1.0b3
|
||||
Release: 14%{?dist}
|
||||
Release: 15%{?dist}
|
||||
License: Apache
|
||||
URL: http://ant-contrib.sourceforget.net
|
||||
Group: Applications/System
|
||||
Vendor: VMware, Inc.
|
||||
Distribution: Photon
|
||||
BuildArch: noarch
|
||||
Source0: http://dl.bintray.com/vmware/photon_release_1.0_TP1_x86_64/%{name}-%{version}-src.tar.gz
|
||||
Source0: https://packages.vmware.com/photon/photon_sources/1.0/%{name}-%{version}-src.tar.gz
|
||||
%define sha1 ant-contrib=b28d2bf18656b263611187fa9fbb95cec93d47c8
|
||||
Patch0: use-system-provided-commons-httpclient-jar.patch
|
||||
BuildRequires: openjre8
|
||||
|
|
@ -49,6 +49,8 @@ cd %{buildroot}/var/opt && tar xvzf %{_builddir}/%{name}/%{name}-%{version}-bin.
|
|||
%{_prefix}/lib/*.jar
|
||||
|
||||
%changelog
|
||||
* Thu Nov 12 2020 Michelle Wang <michellew@vmware.com> 1.0b3-15
|
||||
- Update Source0 use https://packages.vmware.com/photon/photon_sources
|
||||
* Tue Oct 06 2020 Ankit Jain <ankitja@vmware.com> 1.0b3-14
|
||||
- Use systems commons-httpclient
|
||||
* Mon Nov 05 2018 Alexey Makhalov <amakhalov@vmware.com> 1.0b3-13
|
||||
|
|
@ -63,8 +65,8 @@ cd %{buildroot}/var/opt && tar xvzf %{_builddir}/%{name}/%{name}-%{version}-bin.
|
|||
- Updated JAVA_HOME path to point to latest.
|
||||
* Tue Oct 04 2016 Priyesh Padmavilasom <ppadmavilasom@vmware.com> 1.0b3-8
|
||||
- Updated JAVA_HOME path to point to latest.
|
||||
* Tue May 24 2016 Priyesh Padmavilasom <ppadmavilasom@vmware.com> 1.0b3-7
|
||||
- GA - Bump release of all rpms
|
||||
* Tue May 24 2016 Priyesh Padmavilasom <ppadmavilasom@vmware.com> 1.0b3-7
|
||||
- GA - Bump release of all rpms
|
||||
* Fri May 20 2016 Divya Thaluru<dthaluru@vmware.com> 1.0b3-6
|
||||
- Updated JAVA_HOME path to point to latest.
|
||||
* Wed Mar 02 2016 Harish Udaiya Kumar <hudaiyakumar@vmware.com> 1.0b3.0-5
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
Summary: Apache Ant
|
||||
Name: apache-ant
|
||||
Version: 1.10.8
|
||||
Release: 1%{?dist}
|
||||
Release: 2%{?dist}
|
||||
License: Apache
|
||||
URL: http://ant.apache.org
|
||||
Group: Applications/System
|
||||
|
|
@ -12,7 +12,7 @@ Source0: http://apache.mirrors.lucidnetworks.net//ant/source/%{name}-%{version}-
|
|||
%define sha1 apache-ant=74027a785d96715f61619b0a4d9296517bba3aa5
|
||||
Source1: http://hamcrest.googlecode.com/files/hamcrest-1.3.tar.gz
|
||||
%define sha1 hamcrest=f0ab4d66186b894a06d89d103c5225cf53697db3
|
||||
Source2: http://dl.bintray.com/vmware/photon_sources/1.0/maven-ant-tasks-2.1.3.tar.gz
|
||||
Source2: https://packages.vmware.com/photon/photon_sources/1.0//maven-ant-tasks-2.1.3.tar.gz
|
||||
%define sha1 maven-ant-tasks=f38c0cc7b38007b09638366dbaa4ee902d9c255b
|
||||
Requires: openjre8
|
||||
BuildRequires: openjre8
|
||||
|
|
@ -122,6 +122,8 @@ bootstrap/bin/ant -v run-tests
|
|||
%{_bindir}/runant.pl
|
||||
|
||||
%changelog
|
||||
* Thu Nov 12 2020 Michelle Wang <michellew@vmware.com> 1.10.8-2
|
||||
- Update Source0 with using https://packages.vmware.com/photon
|
||||
* Mon Jul 27 2020 Satya Naga Vasamsetty <svasamsetty@vmware.com> 1.10.8-1
|
||||
- Bump to version 1.10.8
|
||||
* Tue Jun 23 2020 Tapas Kundu <tkundu@vmware.com> 1.10.5-5
|
||||
|
|
|
|||
2
build.py
2
build.py
|
|
@ -936,7 +936,7 @@ def set_default_value_of_config():
|
|||
|
||||
global configdict
|
||||
|
||||
configdict["pull-sources-config"] = os.path.join(curDir , "support/package-builder/bintray.conf")
|
||||
configdict["pull-sources-config"] = os.path.join(curDir , "support/package-builder/sources.conf")
|
||||
configdict.setdefault("additional-path", {}).setdefault("photon-cache-path", None)
|
||||
configdict["photon-build-param"]["input-photon-build-number"]=subprocess.check_output(["git rev-parse --short HEAD"], shell=True).decode('ASCII').rstrip()
|
||||
configdict.setdefault('additional-path', {}).setdefault('photon-sources-path', None)
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ There is a whole chapter about signing, importing keys and so on that I will not
|
|||
## Switching repositories
|
||||
|
||||
Since mapping name/url is stored in the repo's config file, in principle you can re-assign a different URL, connecting the host to a different server. The next upgrade will get the latest commit chain from the new server.
|
||||
If we edit photon-host-def's repo config and replace the bintray URL by photon-srv1's IP address, all original packages in the original 3.0_minimal version will be preserved, but any new package change (addition, removal, upgrade) added after that (in 3.0_minimal.1, 3.0_minimal.2) will be reverted and all new commits from photon-srv1 (that may have same version) will be applied. This is because the two repos are identical copies, so they have the same original commit ID as a common ancestor, but they diverge from there.
|
||||
If we edit photon-host-def's repo config and replace the https://packages.vmware.com/photon URL by photon-srv1's IP address, all original packages in the original 3.0_minimal version will be preserved, but any new package change (addition, removal, upgrade) added after that (in 3.0_minimal.1, 3.0_minimal.2) will be reverted and all new commits from photon-srv1 (that may have same version) will be applied. This is because the two repos are identical copies, so they have the same original commit ID as a common ancestor, but they diverge from there.
|
||||
|
||||
If the old and new repo have nothing in common (no common ancestor commit), this will undo even the original commit, so all commits from the new tree will be applied.
|
||||
A better solution would be to add a new remote that will identify where the commits come from.
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ This is also the fastest way to install a host, as we've included in the ISO/cdr
|
|||
|
||||
## Installing the ISO
|
||||
|
||||
User will first download [Photon 3.0 ISO file](https://bintray.com/artifact/download/vmware/photon/photon-1.0-13c08b6.iso) that contains the installer, which is able to deploy any of the supported Photon installation profiles.
|
||||
User will first download [Photon 3.0 ISO file](https://packages.vmware.com/photon/3.0/Rev2/iso/photon-3.0-58f9c74.iso) that contains the installer, which is able to deploy any of the supported Photon installation profiles.
|
||||
|
||||
There are some steps common to all Photon installation profiles, starting with adding a VM in VMware Fusion, Workstation or ESXi, selecting the OS family, then customizing for disk size, CPU, memory size, network interface etc. (or leaving the defaults) and selecting the ISO image as cdrom. The installer will launch, that will go through disk partitioning and accepting the license agreement screens, followed by selecting an installation profile.
|
||||
These steps are described at the page linked below, so I won't repeat them, just that instead of setting up a Photon Minimal profile, we will install a Photon OSTree host:
|
||||
|
|
|
|||
|
|
@ -84,16 +84,16 @@ Going back to our JSON file, **repos** is a multi-value setting that tells RPM-O
|
|||
root [ /srv/rpm-ostree ]# cat /etc/yum.repos.d/photon.repo
|
||||
[photon]
|
||||
name=VMware Photon Linux 3.0(x86_64)
|
||||
baseurl=https://dl.bintray.com/vmware/photon_release_$releasever_$basearch
|
||||
baseurl=https://packages.vmware.com/photon/$releasever/photon_release_$releasever_$basearch
|
||||
gpgkey=file:///etc/pki/rpm-gpg/VMWARE-RPM-GPG-KEY
|
||||
gpgcheck=1
|
||||
enabled=1
|
||||
skip_if_unavailable=True
|
||||
```
|
||||
|
||||
In this case, `rpm-ostree` is instructed to download its packages in RPM format from the bintray URL, that is the location of an online RPMS repo maintained by the WMware Photon OS team. To make sure those packages are genuine, signed by VMware, the signature is checked against the official VMware public key.
|
||||
In this case, `rpm-ostree` is instructed to download its packages in RPM format from the https://packages.vmware.com/photon URL, that is the location of an online RPMS repo maintained by the WMware Photon OS team. To make sure those packages are genuine, signed by VMware, the signature is checked against the official VMware public key.
|
||||
|
||||
So what's in an RPMS repository? If we point the browser to https://dl.bintray.com/vmware/photon_release_3.0_x86_64, we can see there are three top directories:
|
||||
So what's in an RPMS repository? If we point the browser to https://packages.vmware.com/photon/3.0/photon_release_3.0_x86_64/, we can see there are three top directories:
|
||||
* noarch - where all packages that don't depend on the architecture reside. Those may contain scripts, platform neutral source files, configuration.
|
||||
* x86_64 - platform dependent packages for Intel 32 and 64 bits CPUs.
|
||||
* repodata - internal repo management data, like a catalog of all packages, and for every package its name, id, version, architecture and full path file/directory list. There is also a compressed XML file containing the history of changelogs extracted from github, as packages in RPM format were built by Photon OS team members from sources.
|
||||
|
|
@ -248,7 +248,7 @@ This takes several minutes. Then why is the RPM-OSTree server installing so fast
|
|||
## Automatic version prefix
|
||||
|
||||
If you recall the filetree version explained earlier, this is where it comes into play. When a tree is composed from scratch, the first version (0) associated to the initial commit is going to get that human readable value. Any subsequent compose operation will auto-increment to .1, .2, .3 and so on.
|
||||
It's a good idea to start a versionning scheme of your own, so that your customized Photon builds that may get different packages of your choice don't get the same version numbers as the official Photon team builds, coming from VMware's bintray OSTree repository. There is no conflict, it's just confusing to have same name for different commits coming from different repos,
|
||||
It's a good idea to start a versionning scheme of your own, so that your customized Photon builds that may get different packages of your choice don't get the same version numbers as the official Photon team builds, coming from VMware's OSTree repository in https://packages.vmware.com/photon. There is no conflict, it's just confusing to have same name for different commits coming from different repos,
|
||||
So if you work for a company named Big Data Inc., you may want to switch to a new versioning scheme `"automatic_version_prefix": "1.0_bigdata"`.
|
||||
|
||||
## Installing package updates
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ To view the the format and information that a new repository configuration file
|
|||
cat /etc/yum.repos.d/lightwave.repo
|
||||
[lightwave]
|
||||
name=VMware Lightwave 1.0(x86_64)
|
||||
baseurl=https://dl.bintray.com/vmware/lightwave
|
||||
baseurl=https://packages.vmware.com/photon/1.0/lightwave
|
||||
gpgkey=file:///etc/pki/rpm-gpg/VMWARE-RPM-GPG-KEY
|
||||
gpgcheck=1
|
||||
enabled=1
|
||||
|
|
@ -58,4 +58,4 @@ After establishing a new repository, you must run the following command to updat
|
|||
Refreshing metadata for: 'VMware Photon Extras 1.0(x86_64)'
|
||||
Refreshing metadata for: 'Local In-House Applications(x86_64)'
|
||||
Refreshing metadata for: 'VMware Photon Linux 1.0(x86_64)'
|
||||
Metadata cache created.
|
||||
Metadata cache created.
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ Perform th following steps:
|
|||
cat > /etc/yum.repos.d/photon-dev.repo << "EOF"
|
||||
[photon-dev]
|
||||
name=VMware Photon Linux Dev(x86_64)
|
||||
baseurl=https://dl.bintray.com/vmware/photon_dev_$basearch
|
||||
baseurl=https://packages.vmware.com/photon/dev/photon_dev_$basearch
|
||||
gpgkey=file:///etc/pki/rpm-gpg/VMWARE-RPM-GPG-KEY
|
||||
gpgcheck=1
|
||||
enabled=1
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# Building a Package from a Source RPM
|
||||
|
||||
This section describes how to install and build a package on the full version of Photon OS from the package's source RPM. Obtain the source RPMs that Photon OS uses from the Bintray location, [https://bintray.com/vmware/photon](https://bintray.com/vmware/photon)
|
||||
This section describes how to install and build a package on the full version of Photon OS from the package's source RPM. Obtain the source RPMs that Photon OS uses from the https://packages.vmware.com/photon location, [https://packages.vmware.com/photon](https://packages.vmware.com/photon)
|
||||
|
||||
|
||||
## Prerequisites
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# Customizing a Photon OS Machine on EC2
|
||||
|
||||
You can upload an `ami` image of Photon OS to Amazon Elastic Compute Cloud (EC2) and customize the Photon OS machine by using `cloud-init` with an EC2 data source. The Amazon machine image version of Photon OS is available as a free download on Bintray at the location `https://bintray.com/vmware/photon/`.
|
||||
You can upload an `ami` image of Photon OS to Amazon Elastic Compute Cloud (EC2) and customize the Photon OS machine by using `cloud-init` with an EC2 data source. The Amazon machine image version of Photon OS is available as a free download on https://packages.vmware.com at the location `https://packages.vmware.com/photon`.
|
||||
|
||||
The `cloud-init` service is commonly used on EC2 to configure the cloud instance of a Linux image. On EC2, `cloud-init` sets the `.ssh/authorized_keys` file to let you log in with a private key from another computer, that is, a computer besides the workstation that you are already using to connect with the Amazon cloud.
|
||||
|
||||
|
|
@ -92,4 +92,4 @@ For more information on using cloud-init user data on EC2, see [Running Commands
|
|||
|
||||
For more information on how to get Photon OS up and running on EC2 and run a containerized application in the Docker engine, see [Running Photon OS on Amazon Elastic Cloud Compute](../photon_installation/Running-Photon-OS-on-Amazon-Elastic-Cloud-Compute.md).
|
||||
|
||||
With Photon OS, you can also build cloud images on Google Compute Engine and other cloud providers. For more information, see [Compatible Cloud Images](../photon_installation/cloud-images.md).
|
||||
With Photon OS, you can also build cloud images on Google Compute Engine and other cloud providers. For more information, see [Compatible Cloud Images](../photon_installation/cloud-images.md).
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ The default installation of Photon OS includes four yum-compatible repositories
|
|||
photon-updates.repo
|
||||
photon.repo
|
||||
|
||||
The Photon ISO repository (`photon-iso.repo`) contains the installation packages for Photon OS. All the packages that Photon builds and publishes reside in the RPMs directory of the ISO when it is mounted. The RPMs directory contains metadata that lets it act as a yum repository. Mounting the ISO gives you all the packages corresponding to a Photon OS build. If, however, you built Photon OS yourself from the source code, the packages correspond only to your build, though they will typically be the latest. In contrast, the ISO that you obtain from the Bintray web site contains only the packages that are in the ISO at the point of publication. As a result, the packages may no longer match those on Bintray, which are updated regularly.
|
||||
The Photon ISO repository (`photon-iso.repo`) contains the installation packages for Photon OS. All the packages that Photon builds and publishes reside in the RPMs directory of the ISO when it is mounted. The RPMs directory contains metadata that lets it act as a yum repository. Mounting the ISO gives you all the packages corresponding to a Photon OS build. If, however, you built Photon OS yourself from the source code, the packages correspond only to your build, though they will typically be the latest. In contrast, the ISO that you obtain from the https://packages.vmware.com/photon web site contains only the packages that are in the ISO at the point of publication. As a result, the packages may no longer match those on https://packages.vmware.com/photon, which are updated regularly.
|
||||
|
||||
The main Photon OS repository (`photon.repo`) contains all the packages that are built from the ISO or from another source. This repository points to a static batch of packages and spec files at the point of a release.
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ The example in this section shows how to create a Photon OS instance on Google C
|
|||
|
||||
### Prerequisites
|
||||
|
||||
- You must have set up a GCE account and are ready to pay Google for its cloud services. The GCE-ready version of Photon OS is a free image and is free. You can download it without registration from the following Bintray location: `https://bintray.com/vmware/photon/gce/view`
|
||||
- You must have set up a GCE account and are ready to pay Google for its cloud services. The GCE-ready version of Photon OS is a free image and is free. You can download it without registration from the following location: `https://packages.vmware.com/photon/3.0/Rev2/`
|
||||
|
||||
The GCE-ready image of Photon OS contains packages and scripts that prepare it for the Google cloud to save you time as you implement a compute cluster or develop cloud applications. The GCE-ready version of Photon OS adds the following packages to the [packages installed with the minimal version](https://github.com/vmware/photon/blob/master/common/data/packages_minimal.json):
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ You can install Photon OS 3.0 on Dell Gateway 300X. You can download Photon OS a
|
|||
1. Verify that you have the following resources:
|
||||
- Dell Edge Gateway 300x.
|
||||
- USB pen drive. Format the pen drive with FAT32 with at least 8 GB of space.
|
||||
2. Download the Photon OS ISO image from [Bintray](https://bintray.com/vmware/photon/).
|
||||
2. Download the Photon OS ISO image from [https://packages.vmware.com/photon](https://packages.vmware.com/photon).
|
||||
|
||||
## Installing the ISO Image for Photon OS
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ You can install Photon OS 3.0 on Dell Gateway 500X. You can download Photon OS a
|
|||
1. Verify that you have the following resources:
|
||||
- Dell Edge Gateway 500x.
|
||||
- USB pen drive. Format the pen drive with FAT32 with at least 8 GB of space.
|
||||
2. Download the Photon OS ISO image from [Bintray](https://bintray.com/vmware/photon/).
|
||||
2. Download the Photon OS ISO image from [https://packages.vmware.com/photon](https://packages.vmware.com/photon/).
|
||||
|
||||
## Installing the ISO Image for Photon OS
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# Compatible Cloud Images
|
||||
|
||||
The [Bintray website](https://bintray.com/vmware/photon/) contains the following cloud-ready images of Photon OS:
|
||||
The [https://packages.vmware.com/photon](https://packages.vmware.com/photon/) contains the following cloud-ready images of Photon OS:
|
||||
|
||||
1. GCE - Google Compute Engine
|
||||
|
||||
|
|
@ -8,7 +8,7 @@ The [Bintray website](https://bintray.com/vmware/photon/) contains the following
|
|||
|
||||
1. OVA
|
||||
|
||||
Because the cloud-ready images of Photon OS are built to be compatible with their corresponding cloud platform or format, you typically do not need to build a cloud image--just go to Bintray and download the image for the platform that you are working on.
|
||||
Because the cloud-ready images of Photon OS are built to be compatible with their corresponding cloud platform or format, you typically do not need to build a cloud image--just go to https://packages.vmware.com/photon and download the image for the platform that you are working on.
|
||||
|
||||
If, however, you want to build your own cloud image, perhaps because you seek to customize the code, see the next section on how to build cloud images.
|
||||
|
||||
|
|
|
|||
|
|
@ -10,4 +10,4 @@ Before you use Photon OS with Microsoft Azure, perform the following prerequisit
|
|||
|
||||
1. Download and extract the Photon OS VHD file.
|
||||
|
||||
VMware packages Photon OS as a cloud-ready virtual hard disk (VHD file) that you can download for free from [Bintray](https://bintray.com/vmware/photon). This VHD file is a virtual appliance with the information and packages that Azure needs to launch an instance of Photon in the cloud. After you have downloaded the distribution archive, extract the VHD file from it. You will later need to upload this VHD file to Azure, where it will be stored in an Azure storage account. For more information, see [Downloading Photon OS](Downloading-Photon-OS.md).
|
||||
VMware packages Photon OS as a cloud-ready virtual hard disk (VHD file) that you can download for free from [https://packages.vmware.com/photon](https://packages.vmware.com/photon). This VHD file is a virtual appliance with the information and packages that Azure needs to launch an instance of Photon in the cloud. After you have downloaded the distribution archive, extract the VHD file from it. You will later need to upload this VHD file to Azure, where it will be stored in an Azure storage account. For more information, see [Downloading Photon OS](Downloading-Photon-OS.md).
|
||||
|
|
|
|||
|
|
@ -40,7 +40,7 @@ For information about upgrading the Photon OS Linux kernel see [Upgrading the Ke
|
|||
## Photon OS Image
|
||||
|
||||
VMware recommends that administrators use the Photon OS image for Google Compute Engine (GCE) to create Photon OS instances on GCE. Photon OS bundles the Google startup scripts, daemon, and cloud SDK into a GCE-ready image that has been modified to meet the configuration requirements of GCE. You can download the Photon OS image for GCE from the following URL:
|
||||
[https://bintray.com/vmware/photon](https://bintray.com/vmware/photon)
|
||||
[https://packages.vmware.com/photon](https://packages.vmware.com/photon)
|
||||
|
||||
For instructions, see [Downloading Photon OS](Downloading-Photon-OS.md).
|
||||
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ Before you use Photon OS within RPi3, perform the following prerequisite tasks:
|
|||
</tr>
|
||||
<tr>
|
||||
<td>Distribution File</td>
|
||||
<td>Photon OS RPi3 image downloaded from <a href="https://bintray.com/vmware/photon/3.0#files/3.0%2FBeta%2Frpi3">bintray</a> <br>
|
||||
<td>Photon OS RPi3 image downloaded from <a href="https://packages.vmware.com/photon/3.0/Rev2/rpi3/photon-rpi3-3.0-9355405.tar.xz">photon-rpi3-3.0-9355405.tar.xz</a> <br>
|
||||
<p><b>Note</b>: Photon OS RPi3 image is available only from Photon 3.0 onwards.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
|
|
@ -34,6 +34,6 @@ Before you use Photon OS within RPi3, perform the following prerequisite tasks:
|
|||
|
||||
**Note**: You cannot use the Photon ISO to install on RPi3.
|
||||
|
||||
Go to the following bintray URL and download the latest release of Photon OS image for RPi3: [https://bintray.com/vmware/photon/3.0#files/3.0%2FBeta%2Frpi3](https://bintray.com/vmware/photon/3.0#files/3.0%2FBeta%2Frpi3).
|
||||
Go to the following packages.vmware.com URL and download the latest release of Photon OS image for RPi3: [https://packages.vmware.com/photon/3.0/Rev2/rpi3](https://packages.vmware.com/photon/3.0/Rev2/rpi3).
|
||||
|
||||
For instructions, see [Downloading Photon OS](Downloading-Photon-OS.md).
|
||||
For instructions, see [Downloading Photon OS](Downloading-Photon-OS.md).
|
||||
|
|
|
|||
|
|
@ -13,8 +13,8 @@ Before you use Photon OS with Amazon Elastic Cloud Compute(AWS EC2), perform the
|
|||
|
||||
1. Download the Photon OS image for Amazon.
|
||||
|
||||
VMware packages Photon OS as a cloud-ready Amazon machine image (AMI) that you can download for free from [Bintray](https://bintray.com/vmware/photon).
|
||||
VMware packages Photon OS as a cloud-ready Amazon machine image (AMI) that you can download for free from [https://packages.vmware.com/photon](https://packages.vmware.com/photon).
|
||||
|
||||
Download the Photon OS AMI and save it on your workstation. For more infromation, see [Downloading Photon OS](Downloading-Photon-OS.md).
|
||||
|
||||
**Note**: The AMI version of Photon is a virtual appliance with the information and packages that Amazon needs to launch an instance of Photon in the cloud. To build the AMI version, VMware starts with the minimal version of Photon OS and adds the sudo and tar packages to it.
|
||||
**Note**: The AMI version of Photon is a virtual appliance with the information and packages that Amazon needs to launch an instance of Photon in the cloud. To build the AMI version, VMware starts with the minimal version of Photon OS and adds the sudo and tar packages to it.
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ Before you use Photon OS within Fusion, perform the following prerequisite tasks
|
|||
</tr>
|
||||
<tr>
|
||||
<td>Distribution File</td>
|
||||
<td>Photon OS ISO or OVA file downloaded from bintray (<a href="https://bintray.com/vmware/photon/">https://bintray.com/vmware/photon/</a>).</td>
|
||||
<td>Photon OS ISO or OVA file downloaded from (<a href="https://packages.vmware.com/photon">https://packages.vmware.com/photon/</a>).</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
|
@ -42,8 +42,8 @@ Before you use Photon OS within Fusion, perform the following prerequisite tasks
|
|||
|
||||
To get Photon OS up and running quickly, use the OVA.
|
||||
|
||||
1. Download Photon OS. Go to the following Bintray URL and download the latest release of Photon OS:
|
||||
1. Download Photon OS. Go to the following URL and download the latest release of Photon OS:
|
||||
|
||||
[https://bintray.com/vmware/photon/](https://bintray.com/vmware/photon/)
|
||||
[https://packages.vmware.com/photon/](https://packages.vmware.com/photon/)
|
||||
|
||||
For instructions, see [Downloading Photon OS](Downloading-Photon-OS.md).
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ Before you use Photon OS within VMware vSphere, perform the following prerequisi
|
|||
</tr>
|
||||
<tr>
|
||||
<td>Distribution File</td>
|
||||
<td>Photon OS ISO or OVA file downloaded from bintray (<a href="https://bintray.com/vmware/photon/">https://bintray.com/vmware/photon/</a>).</td>
|
||||
<td>Photon OS ISO or OVA file downloaded from packages.vmware.com (<a href="https://packages.vmware.com/photon">https://packages.vmware.com/photon/</a>).</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
|
@ -40,9 +40,9 @@ Before you use Photon OS within VMware vSphere, perform the following prerequisi
|
|||
|
||||
To get Photon OS up and running quickly, use the OVA.
|
||||
|
||||
1. Download Photon OS. Go to the following Bintray URL and download the latest release of Photon OS:
|
||||
1. Download Photon OS. Go to the following packages.vmware.com URL and download the latest release of Photon OS:
|
||||
|
||||
[https://bintray.com/vmware/photon/](https://bintray.com/vmware/photon/)
|
||||
[https://packages.vmware.com/photon](https://packages.vmware.com/photon)
|
||||
|
||||
For instructions, see [Downloading Photon OS](Downloading-Photon-OS.md).
|
||||
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ Before you use Photon OS within Workstation, perform the following prerequisite
|
|||
</tr>
|
||||
<tr>
|
||||
<td>Distribution File</td>
|
||||
<td>Photon OS ISO or OVA file downloaded from bintray (<a href="https://bintray.com/vmware/photon/">https://bintray.com/vmware/photon/</a>).</td>
|
||||
<td>Photon OS ISO or OVA file downloaded from (<a href="https://packages.vmware.com/photon/">https://packages.vmware.com/photon/</a>).</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
|
@ -42,8 +42,8 @@ Before you use Photon OS within Workstation, perform the following prerequisite
|
|||
|
||||
To get Photon OS up and running quickly, use the OVA.
|
||||
|
||||
1. Download Photon OS. Go to the following Bintray URL and download the latest release of Photon OS:
|
||||
1. Download Photon OS. Go to the following URL and download the latest release of Photon OS:
|
||||
|
||||
[https://bintray.com/vmware/photon/](https://bintray.com/vmware/photon/)
|
||||
[https://packages.vmware.com/photon/](https://packages.vmware.com/photon/)
|
||||
|
||||
For instructions, see [Downloading Photon OS](Downloading-Photon-OS.md).
|
||||
|
|
|
|||
|
|
@ -136,7 +136,7 @@ The `-h` option prints out the available and used space in human-readable sizes.
|
|||
|
||||
The `md5sum` tool calculates 128-bit RSA Data Security, Inc. MD5 Message Digest Algorithm hashes (a message digest, or digital signature, of a file) to uniquely identify a file and verify its integrity after file transfers, downloads, or disk errors when the security of the file is not in question.
|
||||
|
||||
`md5sum` can help troubleshooting installation issues by verifying that the version of Photon OS being installed matches the version on the Bintray download page. If, for instance, bytes were dropped during the download, the checksums will not match. Try downloading it again.
|
||||
`md5sum` can help troubleshooting installation issues by verifying that the version of Photon OS being installed matches the version on the https://packages.vmware.com/photon download page. If, for instance, bytes were dropped during the download, the checksums will not match. Try downloading it again.
|
||||
|
||||
## sha256sum
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ To set up a PXE server, you will need to have the following:
|
|||
|
||||
* A DHCP server to allow hosts to get an IP address.
|
||||
* A TFTP server, which is a file transfer protocol similar to FTP with no authentication.
|
||||
* Optionally, an HTTP server. The HTTP server will serve the RPMs yum repo, or you can use the official Photon OS repo on Bintray. Also, this HTTP server can be used if you want to provide a kickstart config for unattended installation.
|
||||
* Optionally, an HTTP server. The HTTP server will serve the RPMs yum repo, or you can use the official Photon OS repo on https://packages.vmware.com/photon. Also, this HTTP server can be used if you want to provide a kickstart config for unattended installation.
|
||||
|
||||
The instructions to set up the servers assume you have an Ubuntu 14.04 machine with a static IP address of `172.16.78.134`.
|
||||
|
||||
|
|
@ -88,7 +88,7 @@ cp ~/syslinux-6.03/bios/core/pxelinux.0 .
|
|||
mkdir pxelinux.cfg
|
||||
mv isolinux.cfg pxelinux.cfg/default
|
||||
```
|
||||
* Update repo param to point to http yum repo; you may pass official photon bintray repo.
|
||||
* Update repo param to point to http yum repo; you may pass official photon repo on https://packages.vmware.com/photon.
|
||||
```
|
||||
sed -i "s/append/append repo=http:\/\/172.16.78.134\/RPMS/g" menu.cfg
|
||||
popd
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ To build Photon OS manually, run the following:
|
|||
|
||||
```
|
||||
packer build \
|
||||
-var 'iso_file=http://dl.bintray.com/vmware/photon/3.0/GA/iso/photon-3.0-26156e2.iso' \
|
||||
-var 'iso_file=https://packages.vmware.com/photon/3.0/GA/iso/photon-3.0-26156e2.iso' \
|
||||
-var 'iso_sha1sum=1c38dd6d00e11d3cbf7768ce93fc3eb8913a9673' \
|
||||
-var 'product_version=3.0GA' \
|
||||
packer-photon.json
|
||||
|
|
@ -49,7 +49,7 @@ or:
|
|||
```
|
||||
packer build \
|
||||
-only=vagrant-vmware_desktop \
|
||||
-var 'iso_file= http://dl.bintray.com/vmware/photon/3.0/GA/iso/photon-3.0-26156e2.iso ' \
|
||||
-var 'iso_file= https://packages.vmware.com/photon/3.0/GA/iso/photon-3.0-26156e2.iso ' \
|
||||
-var 'iso_sha1sum= 1c38dd6d00e11d3cbf7768ce93fc3eb8913a9673' \
|
||||
-var 'product_version=3.0GA' \
|
||||
packer-photon.json
|
||||
|
|
|
|||
|
|
@ -348,9 +348,9 @@ The syntax to serve the config-file to the kernel from an HTTP server (NOTE: DO
|
|||
|
||||
## Building an ISO with a Kickstart Config File
|
||||
|
||||
Here's an example of how to add a kickstart config file to the Photon OS ISO by mounting the ISO on an Ubuntu machine and then rebuilding the ISO. The following example assumes you can adapt the sample kickstart configuration file that comes with the Photon OS ISO to your needs. You can obtain the Photon OS ISO for free from Bintray at the following URL:
|
||||
Here's an example of how to add a kickstart config file to the Photon OS ISO by mounting the ISO on an Ubuntu machine and then rebuilding the ISO. The following example assumes you can adapt the sample kickstart configuration file that comes with the Photon OS ISO to your needs. You can obtain the Photon OS ISO for free from https://packages.vmware.com/photon at the following URL:
|
||||
|
||||
[https://bintray.com/vmware/photon](https://bintray.com/vmware/photon)
|
||||
[https://packages.vmware.com/photon](https://packages.vmware.com/photon)
|
||||
|
||||
Once you have the ISO, mount it.
|
||||
|
||||
|
|
|
|||
|
|
@ -173,7 +173,7 @@ The following are the contents of the `photon-packer-templates/vars/iso-3.0GA.js
|
|||
{
|
||||
"product_version" : "3.0GA",
|
||||
"iso_sha1sum" : "1c38dd6d00e11d3cbf7768ce93fc3eb8913a9673",
|
||||
"iso_file" : "http://dl.bintray.com/vmware/photon/3.0/GA/iso/photon-3.0-26156e2.iso"
|
||||
"iso_file" : "https://packages.vmware.com/photon/3.0/GA/iso/photon-3.0-26156e2.iso"
|
||||
}
|
||||
```
|
||||
|
||||
|
|
|
|||
15
index.html
15
index.html
|
|
@ -98,23 +98,22 @@
|
|||
<p>If you want a quick and easy way to install Photon OS™ just about anywhere, you can grab one of the pre-built ISO images:</p>
|
||||
|
||||
<ul>
|
||||
<li><a href="https://dl.bintray.com/vmware/photon/iso/1.0TP2/x86_64/photon-1.0TP2.iso" target="_blank">Photon OS, Tech Preview 2 — Full ISO</a> - Contains everything you could need to install Photon OS, including rpm-ostree hosts and servers.</li>
|
||||
<li><a href="https://dl.bintray.com/vmware/photon/iso/1.0TP2/x86_64/photon-minimal-1.0TP2.iso" target="_blank">Photon OS, Tech Preview 2 — Minimal ISO</a> - Smaller download for when you just need the container host components.</li>
|
||||
<li><a href="https://packages.vmware.com/photon/1.0/TP2/iso/photon-1.0TP2.iso" target="_blank">Photon OS, Tech Preview 2 — Full ISO</a> - Contains everything you could need to install Photon OS, including rpm-ostree hosts and servers.</li>
|
||||
<li><a href="https://packages.vmware.com/photon/1.0/TP2/iso/photon-minimal-1.0TP2.iso" target="_blank">Photon OS, Tech Preview 2 — Minimal ISO</a> - Smaller download for when you just need the container host components.</li>
|
||||
</ul>
|
||||
|
||||
<p>If you'd like to use Photon OS on VMware Fusion, Workstation, or vSphere, you can either create a VM and install from the ISO, above, or try importing the Photon OS OVA, found <a href="https://dl.bintray.com/vmware/photon/ova/1.0TP2/x86_64/photon-1.0TP2.ova" target="_blank">here</a>. The OVA, in addition to providing a simple way to get up and running, contains some enhancements that make Photon OS boot faster and run more efficiently.</p>
|
||||
<p>If you'd like to use Photon OS on VMware Fusion, Workstation, or vSphere, you can either create a VM and install from the ISO, above, or try importing the Photon OS OVA, found <a href="https://packages.vmware.com/photon/1.0/TP2/ova/photon-ova-1.0TP2.ova" target="_blank">here</a>. The OVA, in addition to providing a simple way to get up and running, contains some enhancements that make Photon OS boot faster and run more efficiently.</p>
|
||||
|
||||
<p>If you'd like to use Photon OS on vCloud Air, look for Photon OS in the public catalog.</p>
|
||||
|
||||
<p>If you'd like to experiment with Photon OS on other IaaS providers, here are some experimental versions in native formats of popular cloud providers:</p>
|
||||
|
||||
<ul>
|
||||
<li><a href="https://dl.bintray.com/vmware/photon/ami/1.0TP2/x86_64/photon-1.0TP2.tar.gz" target="_blank">Amazon Web Services</a></li>
|
||||
<li><a href="https://dl.bintray.com/vmware/photon/gce/1.0TP2/x86_64/photon-1.0TP2.tar.gz" target="_blank">Google Cloud Engine</a></li>
|
||||
<li><a href="https://dl.bintray.com/vmware/photon/azure/1.0TP2/x86_64/photon-1.0TP2.vhd" target="_blank">Microsoft Azure</a></li>
|
||||
<li><a href="https://packages.vmware.com/photon/1.0/TP2/ami/photon-ami-1.0TP2.tar.gz" target="_blank">Amazon Web Services</a></li>
|
||||
<li><a href="https://packages.vmware.com/photon/1.0/TP2/gce/photon-gce-1.0TP2.tar.gz" target="_blank">Google Cloud Engine</a></li>
|
||||
</ul>
|
||||
|
||||
<p>The images are distributed under the <a href="https://vmware.github.io/photon/assets/files/photon_tech_preview_license_agreement.pdf" target="_blank">VMware Technology Preview License Agreement</a>. Open source license information may be found in Photon OS™ <a href="https://dl.bintray.com/vmware/photon/iso/1.0TP2/x86_64/open_source_license_photon_1.0TP2_08272015.txt" target="_blank">Open Source License</a> file.</p>
|
||||
<p>The images are distributed under the <a href="https://vmware.github.io/photon/assets/files/photon_tech_preview_license_agreement.pdf" target="_blank">VMware Technology Preview License Agreement</a>. Open source license information may be found in Photon OS™ <a href="https://packages.vmware.com/photon/1.0/TP2/open_source_license_photon_1.0TP2_08272015.txt" target="_blank">Open Source License</a> file.</p>
|
||||
<p>Photon OS™ source code is available on the VMware <a href="https://github.com/vmware/photon">Photon™ GitHub source repository</a>. You can build your own Photon OS™ ISO image by cloning the repo and following the instructions in <a href="https://github.com/vmware/photon/blob/master/README.md" target="_blank">README.md</a>.</p>
|
||||
|
||||
</div>
|
||||
|
|
@ -207,7 +206,7 @@
|
|||
<div class='content'>
|
||||
<h2 id="license">License</h2>
|
||||
|
||||
<p>Photon™ is comprised of many open source software components, each of which has its own license that is located in the source code of the respective component as well as documented in the <a href="https://dl.bintray.com/vmware/photon/iso/1.0TP1/x86_64/open_source_license_photon_1.0TP1_04202015.txt">open source license file</a> accompanying the Photon™ distribution.</p>
|
||||
<p>Photon™ is comprised of many open source software components, each of which has its own license that is located in the source code of the respective component as well as documented in the <a href="https://packages.vmware.com/photon/1.0/TP1/open_source_license_photon_1.0TP1_04202015.txt">open source license file</a> accompanying the Photon™ distribution.</p>
|
||||
|
||||
<p>The Photon™ pre-built ISO images are distributed under the <a href="/photon/assets/files/photon_tech_preview_license_agreement.pdf">Photon™ Technology Preview License Agreement</a>.</p>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -40,7 +40,7 @@ PHOTON_GENERATE_OSS_FILES=$(PHOTON_PKG_BUILDER_DIR)/GenerateOSSFiles.py
|
|||
ifdef PHOTON_PULLSOURCES_CONFIG
|
||||
PHOTON_PULLSOURCES_CONFIG:=$(abspath $(PHOTON_PULLSOURCES_CONFIG))
|
||||
else
|
||||
PHOTON_PULLSOURCES_CONFIG?=$(PHOTON_PKG_BUILDER_DIR)/bintray.conf
|
||||
PHOTON_PULLSOURCES_CONFIG?=$(PHOTON_PKG_BUILDER_DIR)/sources.conf
|
||||
endif
|
||||
PHOTON_PULL_PUBLISH_RPMS=$(PHOTON_PULL_PUBLISH_RPMS_DIR)/pullpublishrpms.sh
|
||||
PHOTON_PULL_PUBLISH_X_RPMS=$(PHOTON_PULL_PUBLISH_RPMS_DIR)/pullpublishXrpms.sh
|
||||
|
|
|
|||
|
|
@ -39,7 +39,7 @@ def get(package, source, sha1, sourcesPath, URLs, logger):
|
|||
logger.info("sha1 of " + sourcePath[0] + " does not match. " + sha1 +
|
||||
" vs " + getFileHash(sourcePath[0]))
|
||||
for baseurl in URLs:
|
||||
#form url: https://dl.bintray.com/vmware/photon_sources/1.0/<filename>.
|
||||
#form url: https://packages.vmware.com/photon/photon_sources/1.0/<filename>.
|
||||
url = '%s/%s' % (baseurl, source)
|
||||
destfile = os.path.join(sourcesPath, source)
|
||||
logger.debug("Downloading: " + url)
|
||||
|
|
|
|||
|
|
@ -1,3 +0,0 @@
|
|||
{
|
||||
"baseurl":"https://dl.bintray.com/vmware/photon_sources/1.0"
|
||||
}
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
{
|
||||
"baseurl":"https://packages.vmware.com/photon/photon_sources/1.0"
|
||||
}
|
||||
|
|
@ -20,5 +20,5 @@ if [ $# -eq 2 ]; then
|
|||
PUBLISHCACHE=$2
|
||||
while read FILE; do cp -r $PUBLISHCACHE/$FILE $PUBLISHRPMSPATHDIR/$FILE; done < $INPUTFILE
|
||||
else
|
||||
cat $INPUTFILE | awk '{print "https://bintray.com/artifact/download/vmware/photon_publish_x_rpms/"$1}' | xargs -n 1 -P 10 wget --user-agent Mozilla/4.0 -c -nv -nc -r -nH --quiet --cut-dirs=4 -P ${PUBLISHRPMSPATHDIR}
|
||||
cat $INPUTFILE | awk '{print "https://packages.vmware.com/photon/photon_publish_x_rpms/"$1}' | xargs -n 1 -P 10 wget --user-agent Mozilla/4.0 -c -nv -nc -r -nH --quiet --cut-dirs=4 -P ${PUBLISHRPMSPATHDIR}
|
||||
fi
|
||||
|
|
|
|||
|
|
@ -20,5 +20,5 @@ if [ $# -eq 2 ]; then
|
|||
PUBLISHCACHE=$2
|
||||
while read FILE; do cp -r $PUBLISHCACHE/$FILE $PUBLISHRPMSPATHDIR/$FILE; done < $INPUTFILE
|
||||
else
|
||||
cat $INPUTFILE | awk '{print "https://bintray.com/artifact/download/vmware/photon_publish_rpms/"$1}' | xargs -n 1 -P 10 wget --user-agent Mozilla/4.0 -c -nv -nc -r -nH --quiet --cut-dirs=4 -P ${PUBLISHRPMSPATHDIR}
|
||||
cat $INPUTFILE | awk '{print "https://packages.vmware.com/photon/photon_publish_rpms/"$1}' | xargs -n 1 -P 10 wget --user-agent Mozilla/4.0 -c -nv -nc -r -nH --quiet --cut-dirs=4 -P ${PUBLISHRPMSPATHDIR}
|
||||
fi
|
||||
|
|
|
|||
Loading…
Reference in New Issue