new file mode 100644

@@ -0,0 +1,16 @@

+An official Vagrant box is available on Hashicorp Atlas. To get started: 

+

+	vagrant init vmware/photon

+

+Add the following lines to the Vagrantfile: 

+

+	config.vm.provider "virtualbox" do |v|

+	  v.customize ['modifyvm', :id, '--acpi', 'off']

+	end

+

+Install vagrant-guests-photon plugin which provides VMware Photon OS guest support.

+It is available at https://github.com/vmware/vagrant-guests-photon.

+

+Requires VirtualBox 4.3 or later version. If you have issues, please check your version.

+

+

new file mode 100644

@@ -0,0 +1,106 @@

+Download the Photon OS version that’s right for you. Click one of the links below.

+

+**Selecting a Download Format**

+----------------

+

+Photon OS is available in the following pre-packaged, binary formats.

+#### Download Formats ####

+| Format | Description |

+| --- | --- |

+| ISO Image | Contains everything needed to install either the minimal or full installation of Photon OS. The bootable ISO has a manual installer or can be used with PXE/kickstart environments for automated installations. |

+| OVA | Pre-installed minimal environment, customized for VMware hypervisor environments. These customizations include a highly sanitized and optimized kernel to give improved boot and runtime performance for containers and Linux applications. Since an OVA is a complete virtual machine definition, we've made available a Photon OS OVA that has virtual hardware version 11; this will allow for compatibility with several versions of VMware platforms or allow for the latest and greatest virtual hardware enhancements. |

+| Amazon AMI | Pre-packaged and tested version of Photon OS made ready to deploy in your Amazon EC2 cloud environment. Previously, we'd published documentation on how to create an Amazon compatible instance, but, now we've done the work for you. |

+| Google GCE Image | Pre-packaged and tested Google GCE image that is ready to deploy in your Google Compute Engine Environment, with all modifications and package requirements for running Photon OS in GCE. | 

+| Azure VHD | Pre-packaged and tested Azure HD image that is ready to deploy in your Microsoft Azure Cloud, with all modifications and package requirements for running Photon OS in Azure. |

+

+**Downloading Photon OS 2.0 GA**

+------------------------------

+

+Photon OS 2.0 GA is available now! Choose the download that’s right for you and click one of the links below. Refer to the associated sha1sums and md5sums.

+#### Photon OS 2.0 GA Binaries ####

+| Download | Size | sha1 checksum | md5 checksum |

+| --- | --- | --- | --- |

+| [Full ISO](http://dl.bintray.com/vmware/photon/2.0/GA/iso/photon-2.0-304b817.iso) | 2.3GB | 68ec892a66e659b18917a12738176bd510cde829 | 6ce66c763589cf1ee49f0144ff7182dc |

+| [OVA with virtual hardware v11](http://dl.bintray.com/vmware/photon/2.0/GA/ova/photon-custom-hw11-2.0-304b817.ova) | 108MB | b8c183785bbf582bcd1be7cde7c22e5758fb3f16 | 1ce23d43a778fdeb5283ecd18320d9b5 |

+| [OVA with virtual hardware v13 (ESX 6.5 and above)](http://dl.bintray.com/vmware/photon/2.0/GA/ova/photon-custom-hw13-2.0-304b817.ova) | 106MB | 44f7b808ca48ea1af819d222561a14482a15e493 | ec490b65615284a0862e9ee4a7a0ac97 |

+| [OVA with virtual hardware v11(Workstation and Fusion)](http://dl.bintray.com/vmware/photon/2.0/GA/ova/photon-custom-lsilogic-hw11-2.0-304b817.ova) | 108MB | 6ed700cbbc5e54ba621e975f28284b27adb71f68 | 586c059bf3373984c761e254bd491f59 |

+| [Amazon AMI](http://dl.bintray.com/vmware/photon/2.0/GA/ami/photon-ami-2.0-304b817.tar.gz) | 135MB | 45f4e9bc27f7316fae77c648c8133195d38f96b3 | 486d59eca17ebc948e2f863f2af06eee |

+| [Google GCE](http://dl.bintray.com/vmware/photon/2.0/GA/gce/photon-gce-2.0-304b817.tar.gz) | 705MB | b1385dd8464090b96e6b402c32c5d958d43f9fbd | 34953176901f194f02090988e596b1a7 |

+| [Azure VHD - gz file](http://dl.bintray.com/vmware/photon/2.0/GA/azure/photon-azure-2.0-304b817.vhd.gz) | 170MB | a77d54351cca43eefcf289a907ec751c32372930 | 86d281f033f3584b11e5721a5cbda2d3 |

+| [Azure VHD - gz file - cloud-init provisioning](http://dl.bintray.com/vmware/photon/2.0/GA/azure/photon-azure-2.0-3146fa6.tar.gz) | 172MB | d7709a7b781dad03db55c4999bfa5ef6606efd8b | ee95bffe2c924d9cb2d47a94ecbbea2c |

+

+***Photon OS 2.0 AMI ID (Update: November 7th, 2017)***

+-------------------------

+| Region | AMI ID|

+| --- | --- |

+| N.Virginia | ami-47fe4c3d |

+| Ohio | ami-29dff04c |

+| N.California | ami-065f6166 |

+| Oregon | ami-f6ab7f8e |

+

+**Downloading Photon OS 2.0 RC**

+------------------------------

+Photon OS 2.0 RC is available now! Choose the download that’s right for you and click one of the links below. Refer to the associated sha1sums and md5sums.

+#### Photon OS 2.0 RC Binaries ####

+| Download | Size | sha1 checksum | md5 checksum |

+| --- | --- | --- | --- |

+| [Full ISO](https://bintray.com/vmware/photon/download_file?file_path=2.0%2FRC%2Fiso%2Fphoton-2.0-31bb961.iso) | 2.2GB | 5c049d5ff40c8f22ae5e969eabd1ee8cd6b834e7 | 88cc8ecf2a7f6ae5ac8eb15f54e4a821 |

+| [OVA with virtual hardware v11](https://bintray.com/vmware/photon/download_file?file_path=2.0%2FRC%2Fova%2Fphoton-custom-hw11-2.0-31bb961.ova) | 108MB | 6467ebb31ff23dfd112c1c574854f5655a462cc2 | b2c7fa9c151b1130342f08c2f513f9e1 |

+| [OVA with virtual hardware v13 (ESX 6.5 and above)](https://bintray.com/vmware/photon/download_file?file_path=2.0%2FRC%2Fova%2Fphoton-custom-hw13-2.0-31bb961.ova) | 106MB | 5072ec86bcaa2d6e07f4fe3e6aa99063acbbc3f3 | 9331fc10d4526f389d2b658920727925 |

+| [Amazon AMI](https://bintray.com/vmware/photon/download_file?file_path=2.0%2FRC%2Fami%2Fphoton-ami-2.0-31bb961.tar.gz) | 135MB | 2461b81f3d7c2325737c6ae12099e4c7ef6a079c | 67458ee457a0cf68d199ab95fc707107 |

+| [Google GCE](https://bintray.com/vmware/photon/download_file?file_path=2.0%2FRC%2Fgce%2Fphoton-gce-2.0-31bb961.tar.gz) | 704MB | c65bcc0cbda061c6305f968646be2d72a4283227 | 2dff057540e37a161520ec86e39b17aa |

+| [Azure VHD - gz file](https://bintray.com/vmware/photon/download_file?file_path=2.0%2FRC%2Fazure%2Fphoton-azure-2.0-31bb961.vhd.gz) | 169MB | b43a746fead931ae2bb43e9108cde35913b23715 | 3485c7a31741cca07cc11cbf374ec1a5 |

+

+**Downloading Photon OS 2.0 Beta**

+------------------------------

+Photon OS 2.0 Beta is here! Choose the download that’s right for you and click one of the links below. Refer to the associated sha1sums and md5sums.

+#### Photon OS 2.0 Beta Binaries ####

+| Download | Size | sha1 checksum | md5 checksum |

+| --- | --- | --- | --- |

+| [Full ISO](https://bintray.com/vmware/photon/download_file?file_path=2.0%2FBeta%2Fiso%2Fphoton-2.0-8553d58.iso) | 2.1GB | 7a0e837061805b7aa2649f9ba6652afb2d4591fc | a52c50240726cb3c4219c5c608f9acf3 |

+| [OVA with virtual hardware v11](https://bintray.com/vmware/photon/download_file?file_path=2.0%2FBeta%2Fova%2Fphoton-custom-hw11-2.0-8553d58.ova) | 110MB | 30b81b22a7754165ff30cc964b0a4a66b9469805 | fb309ee535cb670fe48677f5bfc74ec0 |

+| [Amazon AMI](https://bintray.com/vmware/photon/download_file?file_path=2.0%2FBeta%2Fami%2Fphoton-ami-2.0-8553d58.tar.gz) | 136MB | 320c5b6f6dbf6b000a6036b569b13b11e0e93034 | cc3cff3cf9a9a8d5f404af0d78812ab4 |

+| [Google GCE](https://bintray.com/vmware/photon/download_file?file_path=2.0%2FBeta%2Fgce%2Fphoton-gce-2.0-8553d58.tar.gz) | 705MB | c042d46971fa3b642e599b7761c18f4005fc70a7 | 03b873bbd2f0dd1401a334681c59bbf6 |

+| [Azure VHD](https://bintray.com/vmware/photon/download_file?file_path=2.0%2FBeta%2Fazure%2Fphoton-azure-2.0-8553d58.vhd) | 17GB | 20cfc506a2425510e68a9d12ea48218676008ffe | 6a531eab9e1f8cba89b1f150d344ecab |

+

+**Downloading Photon OS 1.0**

+-------------------------

+

+

+***Photon OS 1.0 AMI ID (Update: September 28th, 2017)***

+-------------------------

+| Region | AMI ID|

+| --- | --- |

+| N Virginia | ami-18758762 |

+| Ohio | ami-96200df3 |

+| N.California | ami-37360657 |

+| Oregon | ami-66b74f1e |

+

+***Photon OS 1.0, Revision 2 Binaries (Update: January 19th, 2017)***

+-------------------------------------------------------------

+We've been busy updating RPMs in our repository for months, now, to address both functional and security issues. However, our binaries have remained fixed since their release back in September 2015. In order to make it faster and easier to get a up-to-date Photon OS system, we've repackaged all of our binaries to include all of these RPM updates. For clarity, we'll call these updated binaries, which are still backed by the 1.0 repos - **1.0, Revision 2**.

+

+Choose the download that’s right for you and click one of the links below.

+#### Photon OS 1.0, Revision 2 Binaries ####

+| Download | Size | sha1 checksum | md5 checksum |

+| --- | --- | --- | --- |

+| [Full ISO](https://bintray.com/vmware/photon/download_file?file_path=photon-1.0-62c543d.iso) | 2.4GB | c4c6cb94c261b162e7dac60fdffa96ddb5836d66| 69500c07d25ce9caa9b211a8b6eefd61|

+| [OVA with virtual hardware v10](https://bintray.com/vmware/photon/download_file?file_path=photon-custom-hw10-1.0-62c543d.ova) | 159MB | 6e9087ed25394e1bbc56496ae368b8c77efb21cb | 3e4b1a5f24ab463677e3edebd1ecd218|

+| [OVA with virtual hardware v11](https://bintray.com/vmware/photon/download_file?file_path=photon-custom-hw11-1.0-62c543d.ova) | 159MB | 18c1a6d31545b757d897c61a0c3cc0e54d8aeeba| be9961a232ad5052b746fccbb5a9672d|

+| [Amazon AMI](https://bintray.com/vmware/photon/download_file?file_path=photon-ami-1.0-62c543d.tar.gz) | 590MB | 6df9ed7fda83b54c20bc95ca48fa467f09e58548| 5615a56e5c37f4a9c762f6e3bda7f9d0|

+| [Google GCE](https://bintray.com/vmware/photon/download_file?file_path=photon-gce-1.0-62c543d.tar.gz) | 164MB | 1feb68ec00aaa79847ea7d0b00eada7a1ac3b527| 5adb7b30803b168e380718db731de5dd|

+

+There are a few other ways that you could create a Photon OS instance – either making the ISO from source that’s been cloned from the [GitHub Photon OS repository](https://github.com/vmware/photon), using the [instructions](https://github.com/vmware/photon/blob/master/docs/build-photon.md) found on the GitHub repo, using the [scripted installation](https://github.com/vmware/photon/blob/master/docs/kickstart.md), or [boot Photon OS over a network](https://github.com/vmware/photon/blob/master/docs/PXE-boot.md), using PXE. These options are beyond the scope of this document. If you’re interested in these methods, follow the links provided above. 

+

+***Photon OS 1.0, Original Binaries***

+--------------------------------

+

+If you're looking for the original Photon OS, version 1.0 binaries, they can still be found here:

+#### Photon OS 1.0, Original Binaries ####

+| Download | Size | sha1 checksum | md5 checksum |

+| --- | --- | --- | --- |

+| [Full ISO](https://bintray.com/artifact/download/vmware/photon/photon-1.0-13c08b6.iso) | 2.1GB | ebd4ae77f2671ef098cf1e9f16224a4d4163bad1 | 15aea2cf5535057ecb019f3ee3cc9d34 |

+| [OVA with virtual hardware v10](https://bintray.com/vmware/photon/download_file?file_path=photon-custom-hw10-1.0-13c08b6.ova) | 292MB | 8669842446b6aac12bd3c8158009305d46b95eac | 3ca7fa49128d1fd16eef1993cdccdd4d |

+| [OVA with virtual hardware v11](https://bintray.com/vmware/photon/download_file?file_path=photon-custom-hw11-1.0-13c08b6.ova) | 292MB | 2ee56c5ce355fe6c59888f2f3731fd9d51ff0b4d | 8838498fb8202aac5886518483639073 |

+| [Amazon AMI](https://bintray.com/artifact/download/vmware/photon/photon-ami-1.0-13c08b6.tar.gz) | 148.5MB | 91deb839d788ec3c021c6366c192cf5ac601575b | fe657aafdc8189a85430e19ef82fc04a |

+| [Google GCE](https://bintray.com/artifact/download/vmware/photon/photon-gce-1.0-13c08b6.tar.gz) | 411.7MB | 397ccc7562f575893c89a899d9beafcde6747d7d | 67a671e032996a26d749b7d57b1b1887 |

new file mode 100644

@@ -0,0 +1,167 @@

+* [What is Photon OS?](#q-what-is-photon-os)

+* [How do I get started with Photon OS?](#q-how-do-i-get-started-with-photon-os)

+* [Can I upgrade my existing Photon OS 1.0 VMs?](#q-can-i-upgrade-my-existing-photon-os-10-vms)

+* [What kind of support comes with Photon OS?](#q-what-kind-of-support-comes-with-photon-os)

+* [How can I contribute to Photon OS?](#q-how-can-i-contribute-to-photon-os)

+* [How is Photon OS patched?](#q-how-is-Photon-OS-patched)

+* [How does Photon OS relate to Project Lightwave?](#q-how-does-photon-os-relate-to-project-lightwave)

+* [Will VMware continue to support other container host runtime offerings on vSphere?](#q-will-vmware-continue-to-support-other-container-host-runtime-offerings-on-vsphere)

+* [How to report a security vulnerability in Photon OS?](#q-how-to-report-a-security-vulnerability-in-photon-os)

+* [What are the Docker improvements in Photon OS 2.0?](#q-what-are-the-docker-improvements-in-photon-os-20)

+* [Why is VMware creating Photon OS?](#q-why-is-vmware-creating-photon-os)

+* [Why is VMware open-sourcing Photon OS?](#q-why-is-vmware-open-sourcing-photon-os)

+* [In what way is Photon OS "optimized for VMware?"](#q-in-what-way-is-photon-os-optimized-for-vmware)

+* [Why can't I SSH in as root?](#q-why-cant-i-ssh-in-as-root)

+* [Why isn't netstat working?](#q-why-is-netstat-not-working)

+* [Why do all of my cloned Photon OS instances have the same IP address when using DHCP?](#q-why-do-all-of-my-cloned-photon-os-instances-have-the-same-ip-address-when-using-dhcp)

+* [How to install new packages?](#how-to-install-new-packages)

+* [Why is the yum command not working in a minimal installation?](#q-why-the-yum-command-not-working-in-a-minimal-installation)

+* [How to install all build essentials?](#q-how-to-install-all-build-essentials)

+* [How to build new package for Photon OS?](#q-how-to-build-new-package-for-photon-os)

+* [I just booted into freshly installed Photon OS instance, why isn't "docker ps" working?](#q-i-just-booted-into-freshly-installed-photon-os-instance-why-isnt-docker-ps-working)

+* [What is the difference between Minimal and Full installation?](#q-what-is-the-difference-between-minimal-and-full-installation)

+* [What packages are included in Minimal and Full?](#q-what-packages-are-included-in-minimal-and-full)

+* [How do I transfer or share files between Photon OS and my host machine?](#q-how-do-i-transfer-or-share-files-between-photon-and-my-host-machine)

+* [Why is the ISO over 2GB, when I hear that Photon OS is a minimal container runtime?](#q-why-is-the-iso-over-2gb-when-i-hear-that-photon-os-is-a-minimal-container-runtime)

+

+***

+

+# Getting Started

+

+## Q. What is Photon OS?

+A. Photon OS™ is an open source Linux container host optimized for cloud-native applications, cloud platforms, and VMware infrastructure. Photon OS provides a secure run-time environment for efficiently running containers. For an overview, see [https://vmware.github.io/photon/](https://vmware.github.io/photon/).

+

+## Q. How do I get started with Photon OS?

+A. Start by deciding your target platform. Photon OS 2.0 has been certified in public cloud environments - Microsoft Azure (new), Google Compute Engine (GCE), Amazon Elastic Compute Cloud (EC2) - as well as on VMware vSphere, VMware Fusion, and VMware Workstation.

+Next, download the latest binary distributions for your target platform. The binaries are hosted on [https://bintray.com/vmware/photon/](https://bintray.com/vmware/photon/). For download instructions, see [Downloading Photon OS](https://github.com/vmware/photon/wiki/Downloading-Photon-OS).

+Finally, go to the installation instructions for your target platform, which are listed here: [https://github.com/vmware/photon/wiki](https://github.com/vmware/photon/wiki).

+

+## Q. Can I upgrade my existing Photon OS 1.0 VMs?

+A. Yes, there is an in-place upgrade path for Photon OS 1.0 implementations. You simply download an upgrade package, run a script, and reboot the VM. Refer to the instructions in [Upgrading to Photon OS 2.0](https://github.com/vmware/photon/wiki/Upgrading-to-Photon-OS-2.0).

+

+## Q. What kind of support comes with Photon OS?

+A. Photon OS is supported through community efforts and direct developer engagement in the communities. Potential users of Photon OS should start with the [Photon microsite](http://vmware.com/photon).

+

+Developers who might want the source code, including those interested in making contributions, should visit the [Photon OS Github repository](https://github.com/vmware/photon). 

+

+## Q. How can I contribute to Photon OS?

+A. We welcome community participation in the development of Photon OS and look forward to broad ecosystem engagement around the project. Getting your idea into Photon OS is just a [GitHub](https://vmware.github.io/photon) pull request away. When you submit a pull request, you'll be asked to accept the Contributor License Agreement (CLA). 

+

+## Q. How is Photon OS patched?

+A. Within a major release, updates will be delivered as package updates. Security updates will be delivered on an as-needed basis. Non-security related updates will happen quarterly, but may not include every, single package update. The focus is on delivering a valid, functional updated stack every quarter.

+

+Photon OS isn't "patched," as a whole - instead, individual packages are updated (potentially, with patches applied to that individual package). For instance, if a package releases a fix for a critical vulnerability, we'll update the package in the Photon OS repository, for critical issues probably within a day or two. At that point, customers get that updated package by running, "tdnf update <package>"

+ 

+## Q. How does Photon OS relate to Project Lightwave?

+A. Project Lightwave is an open-sourced project that provides enterprise-grade identity and access management services, and can be used to solve key security, governance, and compliance challenges for a variety of use cases within the enterprise.

+Through integration between Photon OS and Project Lightwave, organizations can enforce security and 

+governance on container workloads, for example, by ensuring only authorized containers are run on authorized hosts, by authorized users. For details about Lightwave, see [https://github.com/vmware/lightwave](https://github.com/vmware/lightwave).

+

+## Q. Will VMware continue to support other container host runtime offerings on vSphere?

+A. YES, VMware is committed to delivering an infrastructure for all workloads, and for vSphere to have the largest guest OS support in the industry and support customer choice. 

+Toward those goals, VMware will continue to work with our technology partners to support new Guest Operating Systems and container host runtimes as they come to the market. Open-sourcing Photon OS will enable optimizations and enhancements for container host runtimes on VMware Platform are available as reference implementation for other container host runtimes as well.

+

+# Photon OS

+## Q. What is Photon OS?

+A. Photon OS is an open source, Linux container host runtime optimized for VMware vSphere®. Photon OS is extensible, lightweight, and supports the most common container formats including Docker, Rocket and Garden. Photon OS includes a small footprint, yum-compatible, package-based lifecycle management system, and can support an rpm-ostree image-based system versioning. When used with development tools and environments such as VMware Fusion®, VMware Workstation™, HashiCorp (Vagrant and Atlas) and a production runtime environment (vSphere, VMware vCloud® Air™), Photon OS allows seamless migration of containers-based Apps from development to production.

+

+## Q. How to report a security vulnerability in Photon OS?

+A. VMware encourages users who become aware of a security vulnerability in VMware products to contact VMware with details of the vulnerability. VMware has established an email address that should be used for reporting a vulnerability. Please send descriptions of any vulnerabilities found to security@vmware.com. Please include details on the software and hardware configuration of your system so that we can duplicate the issue being reported.

+

+Note: We encourage use of encrypted email. Our public PGP key is found at [kb.vmware.com/kb/1055](http://kb.vmware.com/kb/1055).

+

+VMware hopes that users encountering a new vulnerability will contact us privately as it is in the best interests of our customers that VMware has an opportunity to investigate and confirm a suspected vulnerability before it becomes public knowledge.

+

+In the case of vulnerabilities found in third-party software components used in VMware products, please also notify VMware as described above.

+

+## Q. What are the Docker improvements in Photon OS 2.0?

+In Photon OS 2.0, the Docker image size (compressed and uncompressed) was reduced to less than a third of its size in Photon OS 1.0. This gain resulted from:

+- using toybox (instead of standard core tools), which brings the docker image size from 50MB (in 1.0) to 14MB (in 2.0)

+- a package split - in Photon OS 2.0, the binary set contains only bash, tdnf, and toybox; all other installed packages are now libraries only.

+

+## Q. Why is VMware creating Photon OS?

+A. It's about workloads - VMware has always positioned our vSphere platform as a secure, highly-performant platform for enterprise applications. With containers, providing an optimized runtime ensures that customers can embrace these new workload technologies without disrupting existing operations. Over time, Photon OS will extend the capabilities of the software-defined data center such as security, identity and resource management to containerized workloads. Organizations can then leverage a single infrastructure architecture for both traditional and cloud-native Apps, and leverage existing investments in tools, skills and technologies. This converged environment will simplify operation and troubleshooting, and ease the adoption of Cloud-Native Apps. 

+

+Photon OS can provide a reference implementation for optimizing containers on VMware platforms across compute, network, storage and management. For example, Photon OS can deliver performance through kernel tuning to remove redundant caching between the Linux kernel and the vSphere hypervisor, and advanced security services through network micro-segmentation delivered by VMware NSX™, and more.

+

+## Q. Why is VMware open-sourcing Photon OS?

+A. Open-sourcing Photon OS encourages discussion, innovation, and collaboration with others in the container ecosystem. In particular, we want to make sure the innovations we introduce to Photon to run containers effectively on VMware are also available to any other container runtime OS. 

+Additionally, VMware is committed to supporting industry and de facto standards, as doing so also supports stronger security, interoperability, and choice for our customers. 

+

+## Q. In what way is Photon OS "optimized for VMware?"

+

+Photon OS 1.0 introduced extensive optimizations for VMware environments, which are described in detail in the following VMware white paper: [Deploying Cloud-Native Applications with Photon OS](https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/whitepaper/vmware-deploying-cloud-native-apps-with-photon-os.pdf). Photon OS 2.0 enhances VMware optimization. The kernel message dumper (new in Photon OS 2.0) is a paravirt feature that extends debugging support. In case of a guest panic, the kernel (through the paravirt channel) dumps the entire kernel log buffer (including the panic message) into the VMware log file (vmware.log) for easy, consolidated access. Previously, this information was stored in a huge vmss (VM suspend state) file.

+

+## Q. Why can't I SSH in as root?

+A. By default Photon does not permit root login to ssh. To make yourself login as root using SSH set PermitRootLogin yes in /etc/ssh/sshd_config, and restart the sshd deamon.

+

+## Q. Why is netstat not working?

+A. netstat is deprecated, ss or ip (part of iproute2) should be used instead.

+

+## Q. Why do all of my cloned Photon OS instances have the same IP address when using DHCP?

+A. Photon OS uses the contents of /etc/machine-id to determine the duid that is used for DHCP requests. If you're going to use a Photon OS instance as the base system for cloning to create additional Photon OS instances, you should clear the machine-id with:

+~~~~

+    echo -n > /etc/machine-id

+~~~~

+With this value cleared, systemd will regenerate the machine-id and, as a result, all DHCP requests will contain a unique duid. 

+

+# How to install new packages?

+## Q. Why is the yum command not working in a minimal installation?

+A. yum has package dependencies that make the system larger than it needs to be. Photon OS includes [tdnf](https://github.com/vmware/tdnf) - 'tiny' dandified yum - to provide package management and yum-functionality in a much, much smaller footprint. To install packages from cdrom, mount cdrom using following command

+~~~~

+     mount /dev/cdrom /media/cdrom

+~~~~

+Then, you can use tdnf to install new packages. For example, to install the vim editor, 

+~~~~

+     tdnf install vim

+~~~~

+## Q. How to install all build essentials?

+A. Following command can be used to install all build essentials.

+~~~~

+curl -L https://git.io/v1boE | xargs -I {} tdnf install -y {}

+~~~~

+## Q. How to build new package for Photon OS??

+A. Assuming you have an Ubuntu development environment, setup and get the latest code pull into /workspace. Lets assume your package name is foo with version 1.0.

+~~~~

+    cp foo-1.0.tar.gz /workspace/photon/SOURCES

+    cp foo.spec /workspace/photon/SPECS/foo/

+    cd /workspace/photon/support/package-builder

+    sudo python ./build_package.py -i foo

+~~~~

+## Q. I just booted into freshly installed Photon OS instance, why isn't "docker ps" working?

+A. Make sure docker daemon is running. By design and default in Photon OS, the docker daemon/engine is not started at boot time. To start the docker daemon for the current session, use the command:

+~~~~

+    systemctl start docker

+~~~~

+To start the docker daemon, on boot, use the command:

+~~~~

+    systemctl enable docker

+~~~~

+## Q. What is the difference between Minimal and Full installation?

+A. Minimal is the minimal set of packages for a container runtime, plus cloud-init.

+Full contains all the packages shipped with ISO.

+

+## Q. What packages are included in Minimal and Full?

+A. See [packages_minimal.json](https://github.com/vmware/photon/blob/dev/common/data/packages_minimal.json) as an example

+

+## Q. How do I transfer or share files between Photon and my host machine?

+A. Use vmhgfs-fuse to transfer files between Photon and your host machine:

+1. Enable Shared folders in the Workstation or Fusion UI (edit the VM settings and choose Options->Enabled shared folders).

+2. Make sure open-vm-tools is installed (it is installed by default in the Minimal installation and OVA import).

+3. Run vmware-hgfsclient to list the shares.

+

+Next, do one of the following:

+

+- Run the following to mount:

+~~~~

+vmhgfs-fuse .host:/$(vmware-hgfsclient) /mnt/hgfs

+~~~~

+OR

+

+- Add the following line to /etc/fstab:

+~~~~

+.host:/ /mnt/hgfs fuse.vmhgfs-fuse <options> 0 0

+~~~~

+

+## Q. Why is the ISO over 2GB, when I hear that Photon OS is a minimal container runtime?

+A. ISO includes a repository with all Photon OS packages. When you mount the ISO to a machine and boot to the Photon installer, you'll be able to choose the Photon Minimal installation option and the hypervisor-optimized Linux kernel, which will reduce the storage size.

\ No newline at end of file

new file mode 100644

@@ -0,0 +1,29 @@

+![Photon](https://cloud.githubusercontent.com/assets/11306358/9800286/cb4c9eb6-57d1-11e5-916c-6eba8e40fa99.png)

+# Welcome to the Photon OS Wiki

+

+This wiki serves as an unofficial supplement to the documentation that is published in the project .md files. 

+

+### Photon OS 2.0 GA Available!

+

+Photon OS 2.0 introduces new security and OS management capabilities, along with new and updated packages for cloud-native applications and VMware appliances. To download the distribution images, go to [Downloading Photon OS](https://github.com/vmware/photon/wiki/Downloading-Photon-OS). To learn more, see [What is New in Photon OS 2.0](https://github.com/vmware/photon/wiki/What-is-New-in-Photon-OS-2.0).

+

+# Table of Contents

+

+1. [Frequently Asked Questions](https://github.com/vmware/photon/wiki/Frequently-Asked-Questions)

+2. Getting Started Guides

+    * [Downloading Photon OS](https://github.com/vmware/photon/wiki/Downloading-Photon-OS)

+    * [Running Photon OS on vSphere](https://github.com/vmware/photon/wiki/Running-Photon-OS-on-vSphere)

+    * [Running Photon OS on Fusion](https://github.com/vmware/photon/wiki/Running-Project-Photon-on-Fusion)

+    * [Running Photon OS on Workstation](https://github.com/vmware/photon/wiki/Running-Photon-OS-on-Workstation)

+    * [Running Photon OS on AWS EC2](https://github.com/vmware/photon/wiki/Running-Photon-OS-on-Amazon-Elastic-Cloud-Compute)

+    * [Running Photon OS on Microsoft Azure](https://github.com/vmware/photon/wiki/Running-Photon-OS-on-Microsoft-Azure)

+    * [Running Photon OS on Google Compute Engine](https://github.com/vmware/photon/wiki/Running-Photon-OS-on-Google-Compute-Engine)

+

+3. Administration Guides

+    * [Photon OS Administration Guide](https://github.com/vmware/photon/blob/master/docs/photon-admin-guide.md)

+    * [How to use Photon Management Daemon](https://github.com/vmware/photon/blob/master/docs/pmd-cli.md)

+

+4. How-To Guides

+    * [Install and Configure a Swarm Cluster with DNS Service on Photon OS](https://github.com/vmware/photon/wiki/Install-and-Configure-a-Swarm-Cluster-with-DNS-Service-on-PhotonOS)

+    * [Install and Configure a Production Ready Mesos Cluster on Photon OS](https://github.com/vmware/photon/wiki/Install-and-Configure-a-Production-Ready-Mesos-Cluster-on-Photon-OS)

+ 

new file mode 100644

@@ -0,0 +1,34 @@

+<sub>Posted on January 13, 2016 by [https://il.linkedin.com/in/knesenko '''Kiril Nesenko''']</sub><br />

+

+To install the DCOS CLI:

+Install virtualenv. The Python tool virtualenv is used to manage the DCOS CLI’s environment.

+<source lang="bash" enclose="div">

+sudo pip install virtualenv

+</source><br />

+Tip: On some older Python versions, ignore any ‘Insecure Platform’ warnings. For more information, see https://virtualenv.pypa.io/en/latest/installation.html.

+From the command line, create a new directory named dcos and navigate into it.

+<source lang="bash" enclose="div">

+$ mkdir dcos

+$ cd dcos

+$ curl -O https://downloads.mesosphere.io/dcos-cli/install.sh

+</source><br />

+Run the DCOS CLI install script, where <hosturl> is the hostname of your master node prefixed with http://:

+<source lang="bash" enclose="div">

+$ bash install.sh <install_dir> <mesos-master-host>

+</source><br />

+For example, if the hostname of your Mesos master node is mesos-master.example.com:

+<source lang="bash" enclose="div">

+$ bash install.sh . http://mesos-master.example.com

+</source><br />

+Follow the on-screen DCOS CLI instructions and enter the Mesosphere verification code. You can ignore any Python ‘Insecure Platform’ warnings.

+<source lang="bash" enclose="div">

+Confirm whether you want to add DCOS to your system PATH:

+$ Modify your bash profile to add DCOS to your PATH? [yes/no]

+</source><br />

+Since DCOS CLI is used for DCOS cluster, reconfigure Marathon and Mesos masters URLs with the following commands:

+<source lang="bash" enclose="div">

+dcos config set core.mesos_master_url http://<mesos-master-host>:5050

+dcos config set marathon.url http://<marathon-host>:8080

+</source><br />

+<br /><br />

+Next - [[Install and Configure Mesos DNS on a Mesos Cluster]]

\ No newline at end of file

new file mode 100644

@@ -0,0 +1,52 @@

+<sub>Posted on January 13, 2016 by [https://il.linkedin.com/in/knesenko '''Kiril Nesenko''']</sub><br />

+<br />

+In my previous How-To [[Install and Configure a Production Ready Mesos Cluster on PhotonOS]]. In this How-To I am going to explain how to install and configure Marathon for Mesos cluster. All the following steps should be done on each Mesos master.

+First, download Marathon:

+<source lang="bash" enclose="div">

+root@pt-mesos-master2 [ ~ ]# mkdir -p  /opt/mesosphere/marathon/ && cd /opt/mesosphere/marathon/

+root@pt-mesos-master2 [ /opt/mesosphere/marathon ]#  curl -O http://downloads.mesosphere.com/marathon/v0.13.0/marathon-0.13.0.tgz

+root@pt-mesos-master2 [ /opt/mesosphere/marathon ]# tar -xf marathon-0.13.0.tgz

+root@pt-mesos-master2 [ /opt/mesosphere/marathon ]# mv marathon-0.13.0 marathon

+</source><br />

+Create a configuration for Marathon:

+<source lang="bash" enclose="div">

+root@pt-mesos-master2 [ /opt/mesosphere/marathon ]# ls -l /etc/marathon/conf/

+total 8

+-rw-r--r-- 1 root root 68 Dec 24 14:33 master

+-rw-r--r-- 1 root root 71 Dec 24 14:33 zk

+root@pt-mesos-master2 [ /opt/mesosphere/marathon ]# cat /etc/marathon/conf/*

+zk://192.168.0.2:2181,192.168.0.1:2181,192.168.0.3:2181/mesos

+zk://192.168.0.2:2181,192.168.0.1:2181,192.168.0.3:2181/marathon

+root@pt-mesos-master2 [ /opt/mesosphere/marathon ]# cat /etc/systemd/system/marathon.service

+[Unit]

+Description=Marathon

+After=network.target

+Wants=network.target

+ 

+[Service]

+Environment="JAVA_HOME=/opt/OpenJDK-1.8.0.51-bin"

+ExecStart=/opt/mesosphere/marathon/bin/start \

+    --master zk://192.168.0.2:2181,192.168.0.1:2181,192.168.0.3:2181/mesos \

+    --zk zk://192.168.0.2:2181,192.168.0.1:2181,192.168.0.3:2181/marathon

+Restart=always

+RestartSec=20

+ 

+[Install]

+WantedBy=multi-user.target

+</source><br />

+Finally, we need to change the Marathon startup script, since PhotonOS do not use the standard JRE. Make sure you add JAVA_HOME to Java path:

+<source lang="bash" enclose="div">

+root@pt-mesos-master2 [ /opt/mesosphere/marathon ]# tail -n3 /opt/mesosphere/marathon/bin/start

+# Start Marathon

+marathon_jar=$(find "$FRAMEWORK_HOME"/target -name 'marathon-assembly-*.jar' | sort | tail -1)

+exec "${JAVA_HOME}/bin/java" "${java_args[@]}" -jar "$marathon_jar" "${app_args[@]}"

+</source><br />

+Now we can start the Marthon service:

+<source lang="bash" enclose="div">

+root@pt-mesos-master2 [ /opt/mesosphere/marathon ]# systemctl start marathon

+root@pt-mesos-master2 [ /opt/mesosphere/marathon ]# ps -ef | grep marathon

+root     15821     1 99 17:14 ?        00:00:08 /opt/OpenJDK-1.8.0.51-bin/bin/java -jar /opt/mesosphere/marathon/bin/../target/scala-2.11/marathon-assembly-0.13.0.jar --master zk://192.168.0.2:2181,192.168.0.1:2181,192.168.0.3:2181/mesos --zk zk://192.168.0.2:2181,192.168.0.1:2181,192.168.0.3:2181/marathon

+root     15854 14692  0 17:14 pts/0    00:00:00 grep --color=auto marathon

+</source><br />

+<br /><br />

+Next - [[Install and Configure DCOS CLI for Mesos]]

\ No newline at end of file

new file mode 100644

@@ -0,0 +1,141 @@

+<sub>Posted on January 13, 2016 by [https://il.linkedin.com/in/knesenko '''Kiril Nesenko''']</sub><br />

+= Overview =<br />

+Before you read this How-To, please read: [[Install and Configure a Production-Ready Mesos Cluster on PhotonOS]] , [[Install and Configure Marathon for Mesos Cluster on PhotonOS]] and [[Install and Configure DCOS CLI for Mesos]].

+After you have fully installed and configured the Mesos cluster, you can execute jobs on it. However, if you want a service discovery and load balancing capabilities you will need to use Mesos-DNS and Haproxy. In this How-To I will explain how to install and configure Mesos-DNS for your Mesos cluster.

+Mesos-DNS supports service discovery in Apache Mesos clusters. It allows applications and services running on Mesos to find each other through the domain name system (DNS), similarly to how services discover each other throughout the Internet. Applications launched by Marathon are assigned names like search.marathon.mesos. Mesos-DNS translates these names to the IP address and port on the machine currently running each application. To connect to an application in the Mesos datacenter, all you need to know is its name. Every time a connection is initiated, the DNS translation will point to the right machine in the datacenter.

+[[ http://mesosphere.github.io/mesos-dns/img/architecture.png ]]<br />

+= Installation =<br />

+I will explain how to configure Mesos-DNS docker and run it through Marathon. I will show you how to create a configuration file for a mesos-dns-docker container and how to run it via Marathon.

+<source lang="bash" enclose="div">

+root@pt-mesos-node1 [ ~ ]# cat /etc/mesos-dns/config.json

+{

+  "zk": "zk://192.168.0.1:2181,192.168.0.2:2181,192.168.0.3:2181/mesos",

+  "masters": ["192.168.0.1:5050", "192.168.0.2:5050", "192.168.0.3:5050"],

+  "refreshSeconds": 60,

+  "ttl": 60,

+  "domain": "mesos",

+  "port": 53,

+  "resolvers": ["8.8.8.8"],

+  "timeout": 5,

+  "httpon": true,

+  "dnson": true,

+  "httpport": 8123,

+  "externalon": true,

+  "SOAMname": "ns1.mesos",

+  "SOARname": "root.ns1.mesos",

+  "SOARefresh": 60,

+  "SOARetry":   600,

+  "SOAExpire":  86400,

+  "SOAMinttl": 60

+}

+</source><br />

+'''Create Application Run File'''<br />

+Next step is to create a json file and run the service from Marathon for HA. It is possible to run the service via API or via DCOS CLI.

+<source lang="bash" enclose="div">

+client:~/mesos/jobs$ cat mesos-dns-docker.json

+{

+    "args": [

+        "/mesos-dns",

+        "-config=/config.json"

+    ],

+    "container": {

+        "docker": {

+            "image": "mesosphere/mesos-dns",

+            "network": "HOST"

+        },

+        "type": "DOCKER",

+        "volumes": [

+            {

+                "containerPath": "/config.json",

+                "hostPath": "/etc/mesos-dns/config.json",

+                "mode": "RO"

+            }

+        ]

+    },

+    "cpus": 0.2,

+    "id": "mesos-dns-docker",

+    "instances": 3,

+    "constraints": [["hostname", "CLUSTER", "pt-mesos-node2.example.com"]]

+}

+</source>

+Now we can see in the Marthon and Mesos UI that we launched the application.

+<br /><br />

+'''Setup Resolvers and Testing'''<br />

+To allow Mesos tasks to use Mesos-DNS as the primary DNS server, you must edit the file ''/etc/resolv.conf'' in every slave and add a new nameserver. For instance, if ''mesos-dns'' runs on the server with IP address  ''192.168.0.5''  at the beginning of ''/etc/resolv.conf'' on every slave.

+<source lang="bash" enclose="div">

+root@pt-mesos-node2 [ ~/mesos-dns ]# cat /etc/resolv.conf

+# This file is managed by systemd-resolved(8). Do not edit.

+#

+# Third party programs must not access this file directly, but

+#only through the symlink at /etc/resolv.conf. To manage

+# resolv.conf(5) in a different way, replace the symlink by a

+# static file or a different symlink.

+nameserver 192.168.0.5

+nameserver 192.168.0.4

+nameserver 8.8.8.8

+</source><br />

+Let's run a simple Docker app and see if we can resolve it in DNS.

+<source lang="bash" enclose="div">

+client:~/mesos/jobs$ cat docker.json

+{

+    "id": "docker-hello",

+    "container": {

+        "docker": {

+            "image": "centos"

+        },

+        "type": "DOCKER",

+        "volumes": []

+    },

+    "cmd": "echo hello; sleep 10000",

+    "mem": 16,

+    "cpus": 0.1,

+    "instances": 10,

+    "disk": 0.0,

+    "ports": [0]

+}

+</source>

+<source lang="bash" enclose="div">

+client:~/mesos/jobs$ dcos marathon app add docker.json

+</source><br />

+Let's try to resolve it.

+

+<pre>

+root@pt-mesos-node2 [ ~/mesos-dns ]# dig _docker-hello._tcp.marathon.mesos SRV

+;; Truncated, retrying in TCP mode.

+; <<>> DiG 9.10.1-P1 <<>> _docker-hello._tcp.marathon.mesos SRV

+;; global options: +cmd

+;; Got answer:

+;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25958

+;; flags: qr aa rd ra; QUERY: 1, ANSWER: 10, AUTHORITY: 0, ADDITIONAL: 10

+;; QUESTION SECTION:

+;_docker-hello._tcp.marathon.mesos. IN SRV

+;; ANSWER SECTION:

+_docker-hello._tcp.marathon.mesos. 60 IN SRV 0 0 31998 docker-hello-4bjcf-s2.marathon.slave.mesos.

+_docker-hello._tcp.marathon.mesos. 60 IN SRV 0 0 31844 docker-hello-jexm6-s1.marathon.slave.mesos.

+_docker-hello._tcp.marathon.mesos. 60 IN SRV 0 0 31111 docker-hello-6ms44-s2.marathon.slave.mesos.

+_docker-hello._tcp.marathon.mesos. 60 IN SRV 0 0 31719 docker-hello-muhui-s2.marathon.slave.mesos.

+_docker-hello._tcp.marathon.mesos. 60 IN SRV 0 0 31360 docker-hello-jznf4-s1.marathon.slave.mesos.

+_docker-hello._tcp.marathon.mesos. 60 IN SRV 0 0 31306 docker-hello-t41ti-s1.marathon.slave.mesos.

+_docker-hello._tcp.marathon.mesos. 60 IN SRV 0 0 31124 docker-hello-mq3oz-s1.marathon.slave.mesos.

+_docker-hello._tcp.marathon.mesos. 60 IN SRV 0 0 31816 docker-hello-tcep8-s1.marathon.slave.mesos.

+_docker-hello._tcp.marathon.mesos. 60 IN SRV 0 0 31604 docker-hello-5uu37-s1.marathon.slave.mesos.

+_docker-hello._tcp.marathon.mesos. 60 IN SRV 0 0 31334 docker-hello-jqihw-s1.marathon.slave.mesos.

+ 

+;; ADDITIONAL SECTION:

+docker-hello-muhui-s2.marathon.slave.mesos. 60 IN A 192.168.0.5

+docker-hello-4bjcf-s2.marathon.slave.mesos. 60 IN A 192.168.0.5

+docker-hello-jexm6-s1.marathon.slave.mesos. 60 IN A 192.168.0.6

+docker-hello-jqihw-s1.marathon.slave.mesos. 60 IN A 192.168.0.6

+docker-hello-mq3oz-s1.marathon.slave.mesos. 60 IN A 192.168.0.6

+docker-hello-tcep8-s1.marathon.slave.mesos. 60 IN A 192.168.0.6

+docker-hello-6ms44-s2.marathon.slave.mesos. 60 IN A 192.168.0.5

+docker-hello-t41ti-s1.marathon.slave.mesos. 60 IN A 192.168.0.4

+docker-hello-jznf4-s1.marathon.slave.mesos. 60 IN A 192.168.0.4

+docker-hello-5uu37-s1.marathon.slave.mesos. 60 IN A 192.168.0.4

+;; Query time: 0 msec

+;; SERVER: 192.168.0.5#53(192.168.0.5)

+;; WHEN: Sun Dec 27 14:36:32 UTC 2015

+;; MSG SIZE  rcvd: 1066

+</pre>

+

+We can see that we can resolve our app!

\ No newline at end of file

new file mode 100644

@@ -0,0 +1,171 @@

+== Overview ==

+For this setup I will use 3 Mesos masters and 3 slaves. On each Mesos master I will run a Zookeeper, meaning that we will have 3 Zookeepers as well. The Mesos cluster will be configured with a quorum of 2. For networking Mesos use Mesos-DNS. I tried to run Mesos-DNS as container, but got into some resolving issues, so in my next How-To I will explain how to configure Mesos-DNS and run it through Marathon. Photon hosts will be used for masters and slaves.<br />

+<br />

+''' Masters: '''<br />

+{| class="wikitable"

+! style="text-align: center; font-weight: bold;" | Hostname

+! style="font-weight: bold;" | IP Address

+|-

+| pt-mesos-master1.example.com

+| 192.168.0.1

+|-

+| pt-mesos-master2.example.com

+| 192.168.0.2

+|-

+| pt-mesos-master3.example.com

+| 192.168.0.3

+|}

+''' Agents: '''<br />

+{| class="wikitable"

+! style="text-align: center; font-weight: bold; font-size: 0.100em;" | Hostname

+! style="font-weight: bold;" | IP Address

+|-

+| pt-mesos-node1.example.com

+| 192.168.0.4

+|-

+| pt-mesos-node2.example.com

+| 192.168.0.5

+|-

+| pt-mesos-node3.example.com

+| 192.168.0.6

+|}

+<br />

+== Masters Installation and Configuration ==

+First of all we will install Zookeeper. Since currently there is a bug in Photon related to the Zookeeper installation I will use the tarball. Do the following for each master:

+<source lang="bash" enclose="div">

+root@pt-mesos-master1 [ ~ ]# mkdir -p /opt/mesosphere && cd /opt/mesosphere && wget http://apache.mivzakim.net/zookeeper/stable/zookeeper-3.4.7.tar.gz

+root@pt-mesos-master1 [ /opt/mesosphere ]# tar -xf zookeeper-3.4.7.tar.gz && mv zookeeper-3.4.7 zookeeper

+root@pt-mesos-master1 [ ~ ]# cat /opt/mesosphere/zookeeper/conf/zoo.cfg | grep -v '#'

+tickTime=2000

+initLimit=10

+syncLimit=5

+dataDir=/var/lib/zookeeper

+clientPort=2181

+server.1=192.168.0.1:2888:3888

+server.2=192.168.0.2:2888:3888

+server.3=192.168.0.3:2888:3888

+</source><br />

+Example of Zookeeper systemd configuration file:

+<source lang="bash" enclose="div">

+root@pt-mesos-master1 [ ~ ]# cat /etc/systemd/system/zookeeper.service

+[Unit]

+Description=Apache ZooKeeper

+After=network.target

+ 

+[Service]

+Environment="JAVA_HOME=/opt/OpenJDK-1.8.0.51-bin"

+WorkingDirectory=/opt/mesosphere/zookeeper

+ExecStart=/bin/bash -c "/opt/mesosphere/zookeeper/bin/zkServer.sh start-foreground"

+Restart=on-failure

+RestartSec=20

+User=root

+Group=root

+ 

+[Install]

+WantedBy=multi-user.target

+</source><br />

+Add server id to the configuration file, so zookeeper will understand the id of your master server. This should be done for each master with its own id.

+<source lang="bash" enclose="div">

+root@pt-mesos-master1 [ ~ ]# echo 1 > /var/lib/zookeeper/myid

+root@pt-mesos-master1 [ ~ ]# cat /var/lib/zookeeper/myid

+1

+</source><br />

+Now lets install the Mesos masters. Do the following for each master:

+<source lang="bash" enclose="div">

+root@pt-mesos-master1 [ ~ ]# yum -y install mesos

+Setting up Install Process

+Package mesos-0.23.0-2.ph1tp2.x86_64 already installed and latest version

+Nothing to do

+root@pt-mesos-master1 [ ~ ]# cat /etc/systemd/system/mesos-master.service

+[Unit]

+Description=Mesos Slave

+After=network.target

+Wants=network.target

+ 

+[Service]

+ExecStart=/bin/bash -c "/usr/sbin/mesos-master \

+    --ip=192.168.0.1 \

+    --work_dir=/var/lib/mesos \

+    --log_dir=/var/log/mesos \

+    --cluster=EXAMPLE \

+    --zk=zk://192.168.0.1:2181,192.168.0.2:2181,192.168.0.3:2181/mesos \

+    --quorum=2"

+KillMode=process

+Restart=always

+RestartSec=20

+LimitNOFILE=16384

+CPUAccounting=true

+MemoryAccounting=true

+ 

+[Install]

+WantedBy=multi-user.target

+</source><br />

+Make sure you replace '''''–ip''''' setting on each master. So far we have 3 masters with a Zookeeper and Mesos packages installed. Let's start zookeeper and mesos-master services on each master:

+<source lang="bash" enclose="div">

+root@pt-mesos-master1 [ ~ ]# systemctl start zookeeper

+root@pt-mesos-master1 [ ~ ]# systemctl start mesos-master

+root@pt-mesos-master1 [ ~ ]# ps -ef | grep mesos

+root     11543     1  7 12:09 ?        00:00:01 /opt/OpenJDK-1.8.0.51-bin/bin/java -Dzookeeper.log.dir=. -Dzookeeper.root.logger=INFO,CONSOLE -cp /opt/mesosphere/zookeeper/bin/../build/classes:/opt/mesosphere/zookeeper/bin/../build/lib/*.jar:/opt/mesosphere/zookeeper/bin/../lib/slf4j-log4j12-1.6.1.jar:/opt/mesosphere/zookeeper/bin/../lib/slf4j-api-1.6.1.jar:/opt/mesosphere/zookeeper/bin/../lib/netty-3.7.0.Final.jar:/opt/mesosphere/zookeeper/bin/../lib/log4j-1.2.16.jar:/opt/mesosphere/zookeeper/bin/../lib/jline-0.9.94.jar:/opt/mesosphere/zookeeper/bin/../zookeeper-3.4.7.jar:/opt/mesosphere/zookeeper/bin/../src/java/lib/*.jar:/opt/mesosphere/zookeeper/bin/../conf: -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.local.only=false org.apache.zookeeper.server.quorum.QuorumPeerMain /opt/mesosphere/zookeeper/bin/../conf/zoo.cfg

+root     11581     1  0 12:09 ?        00:00:00 /usr/sbin/mesos-master --ip=192.168.0.1 --work_dir=/var/lib/mesos --log_dir=/var/lob/mesos --cluster=EXAMPLE --zk=zk://192.168.0.2:2181,192.168.0.1:2181,192.168.0.3:2181/mesos --quorum=2

+root     11601  9117  0 12:09 pts/0    00:00:00 grep --color=auto mesos

+</source><br />

+== Slaves Installation and Configuration ==

+The steps for configuring a Mesos slave are very simple and not very different from master installation. The difference is that we won't install zookeeper on each slave. We will also start the Mesos slaves in slave mode and will tell the daemon to join the Mesos masters. Do the following for each slave:

+<source lang="bash" enclose="div">

+root@pt-mesos-node1 [ ~ ]# cat /etc/systemd/system/mesos-slave.service

+[Unit]

+Description=Photon instance running as a Mesos slave

+After=network-online.target,docker.service

+  

+[Service]

+Restart=on-failure

+RestartSec=10

+TimeoutStartSec=0

+ExecStartPre=/usr/bin/rm -f /tmp/mesos/meta/slaves/latest

+ExecStart=/bin/bash -c "/usr/sbin/mesos-slave \

+    --master=zk://192.168.0.1:2181,192.168.0.2:2181,192.168.0.3:2181/mesos \

+        --hostname=$(/usr/bin/hostname) \

+        --log_dir=/var/log/mesos_slave \

+        --containerizers=docker,mesos \

+        --docker=$(which docker) \

+        --executor_registration_timeout=5mins \

+        --ip=192.168.0.4"

+  

+[Install]

+WantedBy=multi-user.target

+</source>

+Please make sure to replace the NIC name under '''''–ip''''' setting. Start the mesos-slave service on each node.

+<br />

+Now you should have ready Mesos cluster with 3 masters, 3 Zookeepers and 3 slaves.

+[[https://www.devops-experts.com/wp-content/uploads/2015/12/Screen-Shot-2015-12-24-at-2.22.27-PM.png]]

+<br />

+If you want to use private docker registry, you will need to edit docker systemd file. In my example I am using cse-artifactory.eng.vmware.com registry:

+<source lang="bash" enclose="div">

+root@pt-mesos-node1 [ ~ ]# cat /lib/systemd/system/docker.service

+[Unit]

+Description=Docker Daemon

+Wants=network-online.target

+After=network-online.target

+  

+[Service]

+EnvironmentFile=-/etc/sysconfig/docker

+ExecStart=/bin/docker -d $OPTIONS -s overlay

+ExecReload=/bin/kill -HUP $MAINPID

+KillMode=process

+Restart=always

+MountFlags=slave

+LimitNOFILE=1048576

+LimitNPROC=1048576

+LimitCORE=infinity

+  

+[Install]

+WantedBy=multi-user.target

+  

+root@pt-mesos-node1 [ ~ ]# cat /etc/sysconfig/docker

+OPTIONS='--insecure-registry cse-artifactory.eng.vmware.com'

+root@pt-mesos-node1 [ ~ ]# systemctl daemon-reload && systemctl restart docker

+root@pt-mesos-node1 [ ~ ]# ps -ef | grep cse-artifactory

+root      5286     1  0 08:39 ?        00:00:00 /bin/docker -d --insecure-registry <your_privet_registry> -s overlay

+</source><br />

+<br /><br />

+Next - [[Install and Configure Marathon for Mesos Cluster on PhotonOS]]

\ No newline at end of file

new file mode 100644

@@ -0,0 +1,277 @@

+<sub>Posted on January 13, 2016 by [https://il.linkedin.com/in/tgabay '''Tal Gabay''']</sub>

+

+= Overview =

+

+In this How-To, the steps for installing and configuring a Docker Swarm cluster, alongside DNS and Zookeeper, will be presented.

+The cluster that will be set up will be on VMware Photon hosts. <br />

+<br />

+A prerequisite to using this guide is to be familiar with Docker Swarm - information can be found [https://docs.docker.com/swarm/ here].

+

+== Cluster description ==

+

+The cluster will have 2 Swarm Managers and 3 Swarm Agents:

+

+=== Masters ===

+

+{| class="wikitable"

+! style="text-align: center; font-weight: bold;" | Hostname

+! style="font-weight: bold;" | IP Address

+|-

+| pt-swarm-master1.example.com

+| 192.168.0.1

+|-

+| pt-swarm-master2.example.com

+| 192.168.0.2

+|}

+

+=== Agents ===

+

+{| class="wikitable"

+! style="text-align: center; font-weight: bold; font-size: 0.100em;" | Hostname

+! style="font-weight: bold;" | IP Address

+|-

+| pt-swarm-agent1.example.com

+| 192.168.0.3

+|-

+| pt-swarm-agent2.example.com

+| 192.168.0.4

+|-

+| pt-swarm-agent3.example.com

+| 192.168.0.5

+|}<br />

+

+= Docker Swarm Installation and Configuration =

+

+== Setting Up the Managers ==

+

+The following steps should be done on both managers.<br />

+Docker Swarm supports multiple methods of using service discovery, but in order to use failover, Consul, etcd or Zookeeper must be used. In this guide, Zookeeper will be used.<br />

+Download the latest stable version of Zookeeper and create the '' zoo.cfg '' file under the '' conf '' directory:

+<br />

+<br />

+

+=== Zookeeper installation ===

+

+<source lang="bash" enclose="div">

+root@pt-swarm-master1 [ ~ ]# mkdir -p /opt/swarm && cd /opt/swarm && wget http://apache.mivzakim.net/zookeeper/stable/zookeeper-3.4.6.tar.gz

+root@pt-swarm-master1 [ /opt/swarm ]# tar -xf zookeeper-3.4.6.tar.gz && mv zookeeper-3.4.6 zookeeper

+root@pt-swarm-master1 [ ~ ]# cat /opt/swarm/zookeeper/conf/zoo.cfg | grep -v '#'

+tickTime=2000

+initLimit=10

+syncLimit=5

+dataDir=/var/lib/zookeeper

+clientPort=2181

+server.1=192.168.0.1:2888:3888

+server.2=192.168.0.2:2888:3888

+</source><br />

+The dataDir should be an empty, existing directory.

+From the Zookeeper documentation: Every machine that is part of the ZooKeeper ensemble should know about every other machine in the ensemble. You accomplish this with the series of lines of the form server.id=host:port:port. You attribute the server id to each machine by creating a file named myid, one for each server, which resides in that server's data directory, as specified by the configuration file parameter dataDir. The myid file consists of a single line containing only the text of that machine's id. So myid of server 1 would contain the text "1" and nothing else. The id must be unique within the ensemble and should have a value between 1 and 255.

+<br />

+<br />

+Set Zookeeper ID

+<source lang="bash" enclose="div">

+root@pt-swarm-master1 [ ~ ]# echo 1 > /var/lib/zookeeper/myid

+</source><br />

+Project Photon uses [https://en.wikipedia.org/wiki/Systemd Systemd] for services, so a zookeeper service should be created using systemd unit file.<br />

+<source lang="bash" enclose="div">

+root@pt-swarm-master1 [ ~ ]# cat /etc/systemd/system/zookeeper.service

+[Unit]

+Description=Apache ZooKeeper

+After=network.target

+ 

+[Service]

+Environment="JAVA_HOME=/opt/OpenJDK-1.8.0.51-bin"

+WorkingDirectory=/opt/swarm/zookeeper

+ExecStart=/bin/bash -c "/opt/swarm/zookeeper/bin/zkServer.sh start-foreground"

+Restart=on-failure

+RestartSec=20

+User=root

+Group=root

+ 

+[Install]

+WantedBy=multi-user.target

+</source><br />

+Zookeeper comes with OpenJDK, so having Java on the Photon host is not a prerequisite. Simply direct the Environment variable to the location where the Zookeeper was extracted.

+Now you need to enable and start the service. Enabling the service will make sure that if the host restarts for some reason, the service will automatically start.<br />

+<source lang="bash" enclose="div">

+root@pt-swarm-master1 [ ~ ]# systemctl enable zookeeper

+root@pt-swarm-master1 [ ~ ]# systemctl start zookeeper

+</source><br />

+Verify that the service was able to start:<br />

+<source lang="bash" enclose="div">

+root@pt-swarm-master1 [ ~ ]# systemctl status zookeeper

+zookeeper.service - Apache ZooKeeper

+   Loaded: loaded (/etc/systemd/system/zookeeper.service; enabled)

+   Active: active (running) since Tue 2016-01-12 00:27:45 UTC; 10s ago

+ Main PID: 4310 (java)

+   CGroup: /system.slice/zookeeper.service

+           `-4310 /opt/OpenJDK-1.8.0.51-bin/bin/java -Dzookeeper.log.dir=. -Dzookeeper.root.logger=INFO,CONSOLE -cp /opt/swarm/zookeeper/bin/../build/classes:/opt/swarm/zookeeper/bin/../build/lib/*.jar:/opt/s...

+</source><br />

+On the Manager you elected to be the Swarm Leader (primary), execute the following (if you do not have a specific leader in mind, choose one of the managers randomly):

+<source lang="bash" enclose="div">

+root@pt-swarm-master1 [ ~ ]# docker run -d --name=manager1 -p 8888:2375 swarm manage --replication --advertise 192.168.0.1:8888 zk://192.168.0.1,192.168.0.2/swarm

+</source>

+* '' docker run -d ''- run the container in the background.

+* '' --name=manager1 ''- give the container a name instead of the auto-generated one.

+* '' -p 8888:2375 ''- publish a container's port(s) to the host. In this case, when you connect to the host in port 8888, it connects to the container in port 2375.