@@ -1,3 +1,5 @@

+# Photon OS Frequently Asked Questions

+

 * [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)

@@ -33,11 +35,11 @@ A. Photon OS™ is an open source Linux container host optimized for cloud-nativ

 ## 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).

+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](Downloading-Photon-OS.md).

+Finally, go to the installation instructions for your target platform, which are listed here:  [Quick Start](photon-admin-guide.md#getting-started-with-photon-os-20).

 ## 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).

+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](Upgrading-to-Photon-OS-2.0.md).

 ## 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).

deleted file mode 100644

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

-![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)

- 

@@ -1,14 +1,14 @@

-**Installing the Lightwave Client on a Photon Image and Joining the Client to a Domain**

+# Installing the Lightwave Client on a Photon Image and Joining the Client to a Domain

 After you have set up a Lightwave domain controller, you can join Photon clients to that domain. You install the Lightwave client first. After the client is installed, you join the client to the domain.

-**Prerequisites**

+## Prerequisites

 - Prepare a Photon OS client for the Lightwave client installation.

 - Verify that the hostname of the client can be resolved.

 - Verify that you have 184 MB free for the Lightwave client installation.

-**Procedure**

+## Procedure

 1. Log in to your Photon OS client over SSH.

 2. Install the Lightwave client by running the following command. 

@@ -1,14 +1,14 @@

-**Installing the Lightwave Server and Configuring It as a Domain Controller on a Photon Image**

+# Installing the Lightwave Server and Configuring It as a Domain Controller on a Photon Image

 You can configure Lightwave server as domain controller on a Photon client. You install the Lightwave server first. After the server is installed, you configure a new domain. 

-**Prerequisites**

+## Prerequisites

 - Prepare a Photon OS client for the Lightwave server installation.

 - Verify that the hostname of the client can be resolved.

 - Verify that you have 500 MB free for the Lightwave server installation.

-**Procedure**

+## Procedure

 1. Log in to your Photon OS client over SSH as an administrator.

 2. Install the Lightwave server by running the following command. 

@@ -2,10 +2,10 @@

 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 more details about Lightwave, see the [project Lightwave page on GitHub](https://github.com/vmware/lightwave).

-**Procedure**

+## Procedure

-1. [Installing the Lightwave Server and Configuring It as a Domain Controller on a Photon Image](Installing-Lightwave-Server-and-Setting-Up-a-Domain)

-2. [Installing the Lightwave Client on a Photon Image and Joining the Client to a Domain](Installing-Lightwave-Client-and-Joining-a-Domain)

-3. [Installing the Photon Management Daemon on a Lightwave Client](Installing-the-Photon-Management-Daemon-on-a-Lightwave-Client)

-4. [Remotely Upgrade a Single Photon OS Machine With Lightwave Client and Photon Management Daemon Installed](Remotely-Upgrade-a-Photon-OS-Machine-With-Lightwave-Client-and-Photon-Management-Daemon-Installed)

-5. [Remotely Upgrade Multiple Photon OS Machines With Lightwave Client and Photon Management Daemon Installed](Remotely-Upgrade-Photon-OS-Machine-With-Lightwave-Client-and-Photon-Management-Daemon-Installed)

+1. [Installing the Lightwave Server and Configuring It as a Domain Controller on a Photon Image](Installing-Lightwave-Server-and-Setting-Up-a-Domain.md)

+2. [Installing the Lightwave Client on a Photon Image and Joining the Client to a Domain](Installing-Lightwave-Client-and-Joining-a-Domain.md)

+3. [Installing the Photon Management Daemon on a Lightwave Client](Installing-the-Photon-Management-Daemon-on-a-Lightwave-Client.md)

+4. [Remotely Upgrade a Single Photon OS Machine With Lightwave Client and Photon Management Daemon Installed](Remotely-Upgrade-a-Photon-OS-Machine-With-Lightwave-Client-and-Photon-Management-Daemon-Installed.md)

+5. [Remotely Upgrade Multiple Photon OS Machines With Lightwave Client and Photon Management Daemon Installed](Remotely-Upgrade-Photon-OS-Machine-With-Lightwave-Client-and-Photon-Management-Daemon-Installed.md)

@@ -1,14 +1,14 @@

-**Installing the Photon Management Daemon on a Lightwave Client**

+# Installing the Photon Management Daemon on a Lightwave Client 

 After you have installed and configured a domain on Lightwave, and joined a client to the domain, you can install the Photon Management Daemon on that client so that you can remotely manage it.

-**Prerequisites**

+## Prerequisites

 - Have an installed Lightwave server with configured domain controller on it.

 - Have an installed Lightwave client that is joined to the domain.

 - Verify that you have 100 MB free for the daemon installation on the client.

-**Procedure**

+## Procedure

 1. Log in to a machine with installed Lightwave client over SSH as an administrator.

 2. Install the Photon Management Daemon.

@@ -1,3 +1,5 @@

+# Photon OS Administration Guide and Other Documentation

+

 The Photon OS Administration Guide covers the basics of managing packages, controlling services with systemd, setting up networking, initializing Photon OS with cloud-init, running Docker containers, and working with other technologies, such as Kubernetes. The guide also includes a section to get you started using Photon OS quickly and easily. The guide is at the following URL: 

 https://github.com/vmware/photon/blob/master/docs/photon-admin-guide.md

@@ -1,11 +1,13 @@

-### 1.1 What is OSTree? How about RPM-OSTree?

+# Introduction

+

+## 1.1 What is OSTree? How about RPM-OSTree?

 OSTree is a tool to manage bootable, immutable, versioned filesystem trees. Unlike traditional package managers like rpm or dpkg that know how to install, uninstall, configure packages, OSTree has no knowledge of the relationship between files. But when you add rpm capabilities on top of OSTree, it becomes RPM-OSTree, meaning a filetree replication system that is also package-aware.   

 The idea behind it is to use a client / server architecture to keep your Linux installed machines (physical or VM) in sync with the latest bits, in a predictable and reliable manner. To achieve that, OSTree uses a git-like repository that records the changes to any file and replicate them to any subscriber.  

 A system administrator or an image builder developer takes a base Linux image, prepares the packages and other configuration on a server box, executes a command to compose a filetree that the host machines will download and then incrementally upgrade whenever a new change has been committed.

 You may read more about OSTree [here](https://wiki.gnome.org/Projects/OSTree).

-### 1.2 Why use RPM-OSTree in Photon?

+## 1.2 Why use RPM-OSTree in Photon?

 There are several important benefits:

 * Reliable, efficient: The filetree replication is simple, reliable and efficient. It will only transfer deltas over the network. If you have deployed two almost identical bootable images on same box (differing just by several files), it will not take twice the space. The new tree will have a set of hardlinks to the old tree and only the different files will have a separate copy stored to disk.

 * Atomic: the filetree replication is atomic. At the end of a deployment, you are either booting from one deployment, or the other. There is no "partial deployed bootable image". If anything bad happens during replication or deployment- power loss, network failure, your machine boots from the old image. There is even a tool option to cleanup old deployed (successfully or not) image.

@@ -17,36 +19,34 @@ As drawbacks, I would mention:

 * People not used with "read only" file systems will be disappointed that they could no longer use RPM, yum, tdnf to install whatever they want. Think of this as an "enterprise policy". They may circumvent this by customizing the target directory to a writable directory like /var or using rpm to install packages and record them using a new RPM repository in a writable place.

 * Administrators need to be aware about the directories re-mapping specific to OSTree and plan accordingly.

-### 1.3 Photon with RPM-OSTree installation profiles

+## 1.3 Photon with RPM-OSTree installation profiles

 Photon takes advantage of RPM-OSTree and offers several installation choices:

 * Photon RPM-OSTree server - used to compose customized Photon OS installations and to prepare updates. I will call it for short 'server'.

 * Photon RPM-OSTree host connected to a default online server repository via http or https, maintained by VMware Photon OS team, where future updates will be published. This will create a minimal installation profile, but with the option to self-upgrade. I will call it for short 'default host'.

 * Photon RPM-OSTree host connected to a custom server repository. It requires a Photon RPM-OSTree Server installed in advance. I will call it for short 'custom host'.

-### 1.4 Terminology

+## 1.4 Terminology

 I use the term "OSTree" (starting with capitals) throughout this document, when I refer to the general use of this technology, the format of the repository or replication protocol. I use "RPM-OSTree" to emphasize the layer that adds RedHat Package Manager compatibility on both ends - at server and at host. However, since Photon OS is an RPM-based Linux, there are places in the documentation and even in the installer menus where "OSTree" may be used instead of "RPM-OSTree" when the distinction is not obvious or doesn't matter in that context.

 When "ostree" and "rpm-ostree" (in small letters) are encountered, they refer to the usage of the specific Unix commands.   

 Finally, "Photon RPM-OSTree" is the application or implementation of RPM-OStree system into Photon OS, materialized into two options: Photon Server and Photon Host (or client). "Server" or "Host" may be used with or without the "Photon" and/or "RPM-OStree" qualifier, but it means the same thing. 

-### 1.5 Sample code

-Codes samples used throughout the book are small commands that can be typed at shell command prompt and do not require downloading additional files. As an alternative, one can remote via ssh, so cut & paste sample code from outside sources or copy files via scp will work. See the Photon Administration guide to learn [how to enable ssh](https://github.com/vmware/photon/blob/1.0/docs/photon-admin-guide.md#permitting-root-login-with-ssh). 

+## 1.5 Sample code

+Codes samples used throughout the book are small commands that can be typed at shell command prompt and do not require downloading additional files. As an alternative, one can remote via ssh, so cut & paste sample code from outside sources or copy files via scp will work. See the Photon Administration guide to learn [how to enable ssh](photon-admin-guide.md#permitting-root-login-with-ssh). 

 The samples assume that the following VMs have been installed - see the steps in the next chapters:

 * A default host VM named **photon-host-def**.

 * Two server VMs named **photon-srv1** and **photon-srv2**.

 * Two custom host VMs named **photon-host-cus1** and **photon-host-cus2**, connected each to the corresponding server during install.

-### 1.6 How to read this book

+## 1.6 How to read this book

 I've tried to structure this book to be used both as a sequential read and as a reference documentation.   

 If you are just interested in deploying a host system and keeping it up to date, then read chapters 2 and 5.   

 If you want to install your own server and experiment with customizing packages for your Photon hosts, then read chapters 6 to 9. There are references to the concepts discussed throughout the book, if you need to understand them better.  

 However, if you want to read page by page, information is presented from simple to complex, although as with any technical book, we occasionally run into the chicken and egg problem - forward references to concepts that have yet to be explained later. In other cases, concepts are introduced and presented in great detail that may be seem hard to follow at first, but I promise they will make sense in the later pages when you get to use them.

-### 1.7 Difference between versions

+## 1.7 Difference between versions

 This book has been written when Photon 1.0 was released, so all the information presented apply directly to Photon 1.0 and also to Photon 1.0 Revision 2 (in short Photon 1.0 Rev2 or Photon 1.0r, as some people refer to it as Photon 1.0 Refresh). This release is relevant to OSTree, because of ISO including an updated RPM-OSTree repository containing upgraded packages, as well as matching updated online repo that plays well into the upgrade story. Other than that, differences are minimal.  

-The guide has been updated significantly for Photon OS 2.0. Information of what's different is scattered through chapters 2, 6, 7, 8. [[Chapter 12|Photon-RPM-OSTree:-Install-or-rebase-to-Photon-OS-2.0]] is dedicated to the topic.    

+The guide has been updated significantly for Photon OS 2.0. Information of what's different is scattered through chapters 2, 6, 7, 8. [Install or rebase to Photon OS 2.0](Photon-RPM-OSTree-Install-or-rebase-to-Photon-OS-2.0.md) is dedicated to the topic.    

 OSTree technology is evolving too and rather than pointing out at what package version some feature has been introduced or changed, the focus is on the ostree and rpm-ostree package versions included with the Photon OS major releases.

-

-[[Back to main page|Photon-RPM-OSTree:-a-simple-guide]] | [[Previous page|Photon-RPM-OSTree:-Preface]] | [[ Next page >|Photon-RPM-OSTree:-2-Installing-a-host-against-default-server-repository]]

\ No newline at end of file

@@ -1,6 +1,8 @@

+# Remotes

+

 In Chapter 3 we talked about the Refspec that contains a **photon:** prefix, that is the name of a remote. When a Photon host is installed, a remote is added - which contains the URL for an OSTree repository that is the origin of the commits we are going to pull from and deploy filetrees, in our case the Photon RPM-OSTree server we installed the host from. This remote is named **photon**, which may be confusing, because it's also the OS name and part of the Refspec (branch) path.

-### 10.1 Listing remotes

+## 10.1 Listing remotes

 A host repo can be configured to switch between multiple remotes to pull from, however only one remote is the "active" one at a time. We can list the remotes created so far, which brings back the expected result.

 ```

 root@photon-host-def [ ~ ]# ostree remote list

@@ -29,13 +31,13 @@ root@photon-host-cus [ ~ ]# ostree remote show-url photon

 http://10.118.101.168

 ```

-### 10.2 GPG signature verification

+## 10.2 GPG signature verification

 You may wonder what is the purpose of ```gpg-verify=false``` in the config file, associated with the specific remote. This will instruct any host update to skip the signing verification for the updates that come from server, resulted from tree composed locally at the server, as they are not signed. Without this, host updating will fail.  

 There is a whole chapter about signing, importing keys and so on that I will not get into, but the idea is that signing adds an extra layer of security, by validating that everything you download comes from the trusted publisher and has not been altered. That is the case for all Photon OS artifacts downloaded from VMware official site. All OVAs and packages, either from the online RPMS repositories or included in the ISO file - are signed by VMware. We've seen a similar setting ```gpgcheck=1``` in the RPMS repo configuration files that tdnf uses to validate or not the signature for all packages downloaded to be installed.

-### 10.3 Switching repositories

+## 10.3 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 1.0_minimal version will be preserved, but any new package change (addition, removal, upgrade) added after that (in 1.0_minimal.1, 1.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.  

 This may create confusion and it's one of the reasons I insisted on creating your own scheme of versioning.

@@ -43,9 +45,9 @@ This may create confusion and it's one of the reasons I insisted on creating you

 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.

-### 10.4 Adding and removing remotes

+## 10.4 Adding and removing remotes

-A cleaner way to switch repositories is to add remotes that point to different servers. Let's add another server that we will refer to as **photon2**, along with (optional) the refspecs for branches that it provides (we will see later that in the newer OSTree versions, we don't need to know the branch names, they could be [[queried at run-time|Photon-RPM-OSTree:-10-Remotes#105-listing-available-branches]]). The 'minimal' and 'full' branch ref names containing '2.0' suggest this may be a Photon OS 2.0 RPM-OSTree server. 

+A cleaner way to switch repositories is to add remotes that point to different servers. Let's add another server that we will refer to as **photon2**, along with (optional) the refspecs for branches that it provides (we will see later that in the newer OSTree versions, we don't need to know the branch names, they could be [queried at run-time](Photon-RPM-OSTree-10-Remotes.md#105-listing-available-branches)). The 'minimal' and 'full' branch ref names containing '2.0' suggest this may be a Photon OS 2.0 RPM-OSTree server. 

 ```

 root@photon-host-cus [ ~ ]# ostree remote add --repo=/ostree/repo -v --no-gpg-verify photon2 http://10.118.101.86 photon/2.0/x86_64/minimal photon/2.0/x86_64/full

 root@photon-host-cus [ ~ ]# ostree remote list

@@ -70,10 +72,10 @@ root@photon-host-cus [ ~ ]# ostree remote list

 photon

 ```

-### 10.5 List available branches

+## 10.5 List available branches

 If a host has been deployed from a specific branch and would like to switch to a different one, maybe from a different server, how would it know what branches are available? In git, you would run ```git remote show origin``` or ```git remote -a``` (although last command would not show all branches, unless you ran ```git fetch``` first).  

-Fortunately, in Photon OS 2.0 and higher, the hosts are able to query the server, if summary metadata has been generated, as we've seen in [[8.5|Photon-RPM-OSTree:-8-File-oriented-server-operations#85-creating-summary-metadata]].  This command lists all branches available for remote **photon2**.

+Fortunately, in Photon OS 2.0 and higher, the hosts are able to query the server, if summary metadata has been generated, as we've seen in [8.5](Photon-RPM-OSTree:-8-File-oriented-server-operations.md#85-creating-summary-metadata).  This command lists all branches available for remote **photon2**.

 ```

 root@photon-host-cus [ ~ ]# ostree remote refs photon2 

@@ -85,5 +87,3 @@ photon2:photon/2.0/x86_64/minimal

 ###10.6 Switching branches (rebasing)

-[[Back to main page|Photon-RPM-OSTree:-a-simple-guide]] | [[Previous page|Photon-RPM-OSTree:-9-Package-oriented-server-operations]] | [[Next page >|Photon-RPM-OSTree:-11-Running-container-applications-between-bootable-images]]

-  

@@ -1,7 +1,9 @@

+# Running container applications between bootable images

+

 In this chapter, we want to test a docker application and make sure that all the settings and downloads done in one bootable filetree are going to be saved into writable folders and be available in the other image, in other words after reboot from the other image, everything is available exactly the same way.   

 We are going to do this twice: first, to verify an existing bootable image installed in parallel and then create a new one.

-### 11.1 Downloading a docker container appliance

+## 11.1 Downloading a docker container appliance

 Photon OS comes with docker package installed and configured, but we expect that the docker daemon is inactive (not started). Configuration file /usr/lib/systemd/system/docker.service is read-only (remember /usr is bound as read-only). 

 ```

 root@sample-host-def [ ~ ]# systemctl status docker

@@ -128,7 +130,7 @@ CONTAINER ID    IMAGE   COMMAND       CREATED         STATUS

 d07ebca78051    ubuntu  "/bin/bash"   16 minutes ago  Up 5 seconds                        kickass_hodgkin

 ```

-### 11.2 Rebooting into an existing image

+## 11.2 Rebooting into an existing image

 Now let's reboot the machine and select the other image. First, we'll verify that the docker daemon is automaically started.

 ```

 root@photon-host-cus1 [ ~ ]# systemctl status docker

@@ -154,7 +156,7 @@ Ubuntu file

 root@57dcac5d0490:/# echo "booted into existing image" >> /home/myfile

 root@57dcac5d0490:/# exit

 ```

-### 11.3 Reboot into a newly created image

+## 11.3 Reboot into a newly created image

 Let's upgrade and replace the .0 image by a .3 build that contains git and also perl_YAML (because it is a dependency of git).

 ```

 root@photon-host-cus1 [ ~ ]# rpm-ostree status

@@ -207,5 +209,3 @@ Ubuntu file

 booted into existing image

 root@57dcac5d0490:/# echo "booted into new image" >> /home/myfile

 ```

-

-[[Back to main page|Photon-RPM-OSTree:-a-simple-guide]] | [[Previous page|Photon RPM-OSTree:-10-Remotes]] | [[ Next page >|Photon-RPM-OSTree:-Install-or-rebase-to-Photon-OS-2.0]]

\ No newline at end of file

@@ -1,20 +1,22 @@

+# Installing a host against default server repository

+

 RPM-OSTree Host default server repo installation option in Photon 1.0 or 1.0 Revision 2 will setup a profile similar to Photon Minimal, with the added benefit of being able to self-upgrade.  

 Photon OS 2.0 does not offer a 'default host' installation. See chapter 7 and 12 for other options. 

-### 2.1 Who is this for?  

+## 2.1 Who is this for?  

 The RPM-OSTree 'default host' is the easiest way to deploy a Photon RPM-OSTree host from ISO/cdrom, without the need to deploy and maintain an RPM-OSTree server. It is targeted at the user who relies on VMware Photon OS team to keep his or her system up-to-date, configured to get its updates from the official Photon 1.0 OSTree repository.

 This is also the fastest way to install a host (18 seconds on my Mac with SSD after all UI choices have been entered by user), as we've included in the ISO/cdrom an identical copy of the Photon 1.0 "starter" RPM-OSTree repository that is published online by VMware Photon OS team. So rather than pulling from the online repository, the installer pulls the repo from cdrom, which saves bandwidth and also reduces to zero the chances of failing due to a networking problem. After successful installation, any updates are going to be pulled from the official online repository, when Photon OS team will make them available.    

 Note: It is also possible to install an RPM-OSTree host against the official online repo via PXE boot, without the benefit of fast, local pull from cdrom. This will be covered in the PXE boot/kickstart chapter, as it requires additional configuration.

-### 2.2 Installing the ISO, step by step

-User will first download [[Photon 1.0 ISO file|https://bintray.com/artifact/download/vmware/photon/photon-1.0-13c08b6.iso]] or the newer [[Photon 1.0 Rev2 ISO file|https://bintray.com/artifact/download/vmware/photon/photon-1.0-62c543d.iso]] that contains the installer, which is able to deploy any of the supported Photon installation profiles.

+## 2.2 Installing the ISO, step by step

+User will first download [Photon 1.0 ISO file](https://bintray.com/artifact/download/vmware/photon/photon-1.0-13c08b6.iso) or the newer [Photon 1.0 Rev2 ISO file](https://bintray.com/artifact/download/vmware/photon/photon-1.0-62c543d.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:   

-[[Running Project Photon on Fusion|Running-Project-Photon-on-Fusion]].  

+[Running Project Photon on Fusion](Running-Project-Photon-on-Fusion.md).  

 Select the **Photon OSTree Host** option.

@@ -31,8 +33,6 @@ When installation is over, the VM will reboot and will show in grub VMWare Photo

 ![PhotonHostFirstRebootGrub](https://cloud.githubusercontent.com/assets/13158414/14757877/155614ec-08ad-11e6-9e36-b43f77b6fb69.png)  

-Boot, login and you are ready to use it!  The next chapters are about experimenting first hand and understanding in detail how everything works. If you just want to learn how to [[upgrade your host|Photon-RPM-OSTree:-5-Host-updating-operations]] when new updates are available, skip to [[Chapter 5|Photon-RPM-OSTree:-5-Host-updating-operations]].

-

-Note: If you ran Photon 1.0 Rev2 installer rather than Photon 1.0, you may notice in grub **1.0_minimal.1** rather than **1.0_minimal**, hinting of an updated, newer version installed. This will be also explained in [[Chapter 5|Photon-RPM-OSTree:-5-Host-updating-operations]].  

+Boot, login and you are ready to use it!  The next chapters are about experimenting first hand and understanding in detail how everything works. If you just want to learn how to [upgrade your host](Photon-RPM-OSTree-5-Host-updating-operations.md) when new updates are available, skip to [Host updating operations](Photon-RPM-OSTree-5-Host-updating-operations.md).

-[[Back to main page|Photon-RPM-OSTree:-a-simple-guide]] | [[Previous page|Photon-RPM-OSTree:-1-Introduction#photon-with-rpm-ostree-installation-profiles]] | [[ Next page >|Photon-RPM-OStree:-3-Concepts-in-action]] 

\ No newline at end of file

+Note: If you ran Photon 1.0 Rev2 installer rather than Photon 1.0, you may notice in grub **1.0_minimal.1** rather than **1.0_minimal**, hinting of an updated, newer version installed. This will be also explained in [Host updating operations](Photon-RPM-OSTree-5-Host-updating-operations.md).  

deleted file mode 100644

@@ -1,256 +0,0 @@

-There are several ostree and rpm-ostree commands that list file or package data based on either the Commit ID, or Refspec. If Refspec is passed as a parameter, it's the same as passing the most recent commit ID (head) for that branch.

-

-### 4.1 Commit history

-For a host that is freshly installed, there is only one commit in the history for the only branch.

-```

-root@photon-host [ ~ ]# ostree log photon/1.0/x86_64/minimal

-commit 56ef687f1319604b7900a232715718d26ca407de7e1dc89251b206f8e255dcb4

-Date:  2016-06-07 14:06:17 +0000

-Version: 1.0_minimal

-```

-This commit has no parent; if there was an older commit, it would have been listed too. We can get the same listing (either nicely formatted or raw variant data) by passing the Commit ID. Just the first several hex digits will suffice to identify the commit ID. We can either request to be displayed in a pretty format, or raw - the actual C struct.

-```

-root@photon-host [ ~ ]# ostree log 56ef

-commit 56ef687f1319604b7900a232715718d26ca407de7e1dc89251b206f8e255dcb4

-Date:  2016-06-07 14:06:17 +0000

-Version: 1.0_minimal

-```

-```

-root@photon-host [ ~ ]# ostree log 56ef --raw

-commit 56ef687f1319604b7900a232715718d26ca407de7e1dc89251b206f8e255dcb4

-({'version': <'1.0_minimal'>, 'rpmostree.inputhash': <'40ae75453cf7f00b163848676c4b5716511e7515b95fb7b9168004aa97f05dd9'>}, @ay [], @a(say) [], '', '', uint64 1465308377, [byte 0x3c, 0x6b, 0x71, 0x44, 0x07, 0xd0, 0x5e, 0xd5, 0x9d, 0xfc, 0x4a, 0x1c, 0x33, 0x74, 0x96, 0x1d, 0x50, 0xa3, 0x53, 0xd5, 0xf1, 0x20, 0xb4, 0x40, 0xd0, 0x60, 0x35, 0xf2, 0xf8, 0x29, 0xcf, 0x5f], [byte 0x44, 0x6a, 0x0e, 0xf1, 0x1b, 0x7c, 0xc1, 0x67, 0xf3, 0xb6, 0x03, 0xe5, 0x85, 0xc7, 0xee, 0xee, 0xb6, 0x75, 0xfa, 0xa4, 0x12, 0xd5, 0xec, 0x73, 0xf6, 0x29, 0x88, 0xeb, 0x0b, 0x6c, 0x54, 0x88])

-```

-

-### 4.2 Listing file mappings

-This command lists the file relations between the original source Linux Photon filetree and the deployed filetree. The normal columns include file type type (regular file, directory, link), permissions in chmod octal format, userID, groupID, file size, file name. 

-```

-root@photon-host [ ~ ]# ostree ls photon/1.0/x86_64/minimal

-d00755 0 0      0 /

-l00777 0 0      0 /bin -> usr/bin

-l00777 0 0      0 /home -> var/home

-l00777 0 0      0 /lib -> usr/lib

-l00777 0 0      0 /lib64 -> usr/lib

-l00777 0 0      0 /media -> run/media

-l00777 0 0      0 /mnt -> var/mnt

-l00777 0 0      0 /opt -> var/opt

-l00777 0 0      0 /ostree -> sysroot/ostree

-l00777 0 0      0 /root -> var/roothome

-l00777 0 0      0 /sbin -> usr/sbin

-l00777 0 0      0 /srv -> var/srv

-l00777 0 0      0 /tmp -> sysroot/tmp

-d00755 0 0      0 /boot

-d00755 0 0      0 /dev

-d00755 0 0      0 /proc

-d00755 0 0      0 /run

-d00755 0 0      0 /sys

-d00755 0 0      0 /sysroot

-d00755 0 0      0 /usr

-d00755 0 0      0 /var

-```

-Extra columns can be added like checksum (-C) and extended attributes (-X). 

-```

-root@photon-host [ /usr/share/man/man1 ]# ostree ls photon/1.0/x86_64/minimal -C

-d00755 0 0      0 3c6b714407d05ed59dfc4a1c3374961d50a353d5f120b440d06035f2f829cf5f 446a0ef11b7cc167f3b603e585c7eeeeb675faa412d5ec73f62988eb0b6c5488 /

-l00777 0 0      0 389846c2702216e1367c8dfb68326a6b93ccf5703c89c93979052a9bf359608e /bin -> usr/bin

-l00777 0 0      0 4344c10bf4931483f918496534f12ed9b50dc6a2cead35e3cd9dd898d6ac9414 /home -> var/home

-l00777 0 0      0 f11902ca9d69a80df33918534a3e443251fd0aa7f94b76301e1f55e52aed29dd /lib -> usr/lib

-l00777 0 0      0 f11902ca9d69a80df33918534a3e443251fd0aa7f94b76301e1f55e52aed29dd /lib64 -> usr/lib

-l00777 0 0      0 75317a3df11447c470ffdd63dde045450ca97dfb2a97a0f3f6a21a5da66f737c /media -> run/media

-l00777 0 0      0 97c55dbe24e8f3aecfd3f3e5b3f44646fccbb39799807d37a217e9c871da108b /mnt -> var/mnt

-l00777 0 0      0 46b1abbd27a846a9257a8d8c9fc4b384ac0888bdb8ac0d6a2d5de72715bd5092 /opt -> var/opt

-l00777 0 0      0 d37269e3f46023fd0275212473e07011894cdf4148cbf3fb5758a7e9471dad8e /ostree -> sysroot/ostree

-l00777 0 0      0 6f800e74eed172661278d1e1f09e389a6504dcd3358618e1c1618f91f9d33601 /root -> var/roothome

-l00777 0 0      0 e0bead7be9323b06bea05cb9b66eb151839989e3a4e5d1a93e09a36919e91818 /sbin -> usr/sbin

-l00777 0 0      0 5d4250bba1ed300f793fa9769474351ee5cebd71e8339078af7ebfbe6256d9b5 /srv -> var/srv

-l00777 0 0      0 364fbd62f91ca1e06eb7dbd50c93de8976f2cea633658e2dbe803ce6f7490c09 /tmp -> sysroot/tmp

-d00755 0 0      0 1e4f98d92b35c453d8f61e668aea9fae7ca1863f6609db787374b4ad5caf3b2f 446a0ef11b7cc167f3b603e585c7eeeeb675faa412d5ec73f62988eb0b6c5488 /boot

-d00755 0 0      0 6e340b9cffb37a989ca544e6bb780a2c78901d3fb33738768511a30617afa01d 446a0ef11b7cc167f3b603e585c7eeeeb675faa412d5ec73f62988eb0b6c5488 /dev

-d00755 0 0      0 6e340b9cffb37a989ca544e6bb780a2c78901d3fb33738768511a30617afa01d 446a0ef11b7cc167f3b603e585c7eeeeb675faa412d5ec73f62988eb0b6c5488 /proc

-d00755 0 0      0 6e340b9cffb37a989ca544e6bb780a2c78901d3fb33738768511a30617afa01d 446a0ef11b7cc167f3b603e585c7eeeeb675faa412d5ec73f62988eb0b6c5488 /run

-d00755 0 0      0 6e340b9cffb37a989ca544e6bb780a2c78901d3fb33738768511a30617afa01d 446a0ef11b7cc167f3b603e585c7eeeeb675faa412d5ec73f62988eb0b6c5488 /sys

-d00755 0 0      0 6e340b9cffb37a989ca544e6bb780a2c78901d3fb33738768511a30617afa01d 446a0ef11b7cc167f3b603e585c7eeeeb675faa412d5ec73f62988eb0b6c5488 /sysroot

-d00755 0 0      0 b072f4b3e995a491c04d88636401ca156e80f103b002d724ae76c07174ee4c74 446a0ef11b7cc167f3b603e585c7eeeeb675faa412d5ec73f62988eb0b6c5488 /usr

-d00755 0 0      0 6e340b9cffb37a989ca544e6bb780a2c78901d3fb33738768511a30617afa01d 446a0ef11b7cc167f3b603e585c7eeeeb675faa412d5ec73f62988eb0b6c5488 /var

-```

-

-By default, only the top folders are listed, but -R will list recursively. Instead of listing over 10,000 files, let's filter to just all files that contain 'rpm-ostree', 'rpmostree' or 'RpmOstree', that must belong to **rpm-ostree** package itself.

-```

-root@photon-host [ /usr/share/rpm-ostree ]# ostree ls photon/1.0/x86_64/minimal -R | grep -e '[Rr]pm-\?[Oo]stree'

-l00777 0 0      0 /usr/bin/atomic -> rpm-ostree

--00755 0 0 131104 /usr/bin/rpm-ostree

-l00777 0 0      0 /usr/lib/librpmostree-1.so.1 -> librpmostree-1.so.1.0.0

--00755 0 0 104272 /usr/lib/librpmostree-1.so.1.0.0

--00644 0 0   1296 /usr/lib/girepository-1.0/RpmOstree-1.0.typelib

-d00755 0 0      0 /usr/lib/rpm-ostree

--00644 0 0    622 /usr/lib/rpm-ostree/tmpfiles-ostree-integration.conf

--00644 0 0    717 /usr/lib/tmpfiles.d/rpm-ostree-autovar.conf

-d00755 0 0      0 /usr/share/rpm-ostree

--00644 0 0   1132 /usr/share/rpm-ostree/treefile.json

-```

-

-**atomic** is really an alias for rpm-ostree command. The last file **treefile.json** is not installed by the rpm-ostree package, it's actually downloaded from the server, as we will see in the next chapter. For now, let's notice **"osname" : "photon",  "ref" : "photon/1.0/x86_64/minimal",  "automatic_version_prefix" : "1.0_minimal"**, that matches what we've known so far, and also the **"documentation" : false** setting, that explains why there are no manual files installed for rpm-ostree, and in fact for any package.

-```

-root@photon-host [ /usr/share/rpm-ostree ]# ls -l /usr/share/man/man1 

-total 0

-```

-

-

-### 4.3 Listing configuration changes

-

-To diff the current /etc configuration versus default /etc (from the base image), this command will show the **M**odified, **A**dded and **D**eleted files:

-```

-root@photon-host [ ~ ]# ostree admin config-diff

-M    mtab

-M    ssh/sshd_config

-M    shadow

-M    hosts

-M    fstab

-M    machine-id

-A    ssh/ssh_host_rsa_key

-A    ssh/ssh_host_rsa_key.pub

-A    ssh/ssh_host_dsa_key

-A    ssh/ssh_host_dsa_key.pub

-A    ssh/ssh_host_ecdsa_key

-A    ssh/ssh_host_ecdsa_key.pub

-A    ssh/ssh_host_ed25519_key

-A    ssh/ssh_host_ed25519_key.pub

-A    ssh/sshd.pid

-A    tmpfiles.d/postinstall.sh

-A    udev/hwdb.bin

-A    resolv.conf

-A    hostname

-A    postinstall

-A    localtime

-A    .updated

-```

-

-### 4.4 Listing packages

-As expected, there is an rpm-ostree command that lists all the packages for that branch, extracted from RPM database.   

-```

-root@photon-host [ ~ ]# rpm-ostree db list photon/1.0/x86_64/minimal

-ostree commit: photon/1.0/x86_64/minimal (56ef687f1319604b7900a232715718d26ca407de7e1dc89251b206f8e255dcb4)

- Linux-PAM-1.2.1-3.ph1.x86_64

- attr-2.4.47-3.ph1.x86_64

- autogen-libopts-5.18.7-2.ph1.x86_64

- bash-4.3.30-4.ph1.x86_64

- bc-1.06.95-3.ph1.x86_64

- binutils-2.25.1-2.ph1.x86_64

- bridge-utils-1.5-2.ph1.x86_64

- bzip2-1.0.6-5.ph1.x86_64

- ca-certificates-20160109-5.ph1.x86_64

- coreutils-8.25-2.ph1.x86_64

- cpio-2.12-2.ph1.x86_64

- cracklib-2.9.6-2.ph1.x86_64

- cracklib-dicts-2.9.6-2.ph1.x86_64

- curl-7.47.1-2.ph1.x86_64

- db-6.1.26-2.ph1.x86_64

- dbus-1.8.8-5.ph1.x86_64

- device-mapper-2.02.141-5.ph1.x86_64

- device-mapper-libs-2.02.141-5.ph1.x86_64

- docker-1.11.0-5.ph1.x86_64

- dracut-044-3.ph1.x86_64

- dracut-tools-044-3.ph1.x86_64

- e2fsprogs-1.42.13-2.ph1.x86_64

- elfutils-libelf-0.165-2.ph1.x86_64

- expat-2.1.0-2.ph1.x86_64

- file-5.24-2.ph1.x86_64

- filesystem-1.0-7.ph1.x86_64

- findutils-4.6.0-2.ph1.x86_64

- flex-2.5.39-2.ph1.x86_64

- gdbm-1.11-2.ph1.x86_64

- glib-2.47.6-2.ph1.x86_64

- glib-networking-2.46.1-2.ph1.x86_64

- glibc-2.22-8.ph1.x86_64

- gmp-6.0.0a-3.ph1.x86_64

- gnutls-3.4.11-2.ph1.x86_64

- gobject-introspection-1.46.0-2.ph1.x86_64

- gpgme-1.6.0-2.ph1.x86_64

- grep-2.21-2.ph1.x86_64

- grub2-2.02-4.ph1.x86_64

- gzip-1.6-2.ph1.x86_64

- hawkey-2014.1-4.ph1.x86_64

- iana-etc-2.30-2.ph1.noarch

- iproute2-4.2.0-2.ph1.x86_64

- iptables-1.6.0-4.ph1.x86_64

- iputils-20151218-3.ph1.x86_64

- json-glib-1.0.4-2.ph1.x86_64

- kmod-21-4.ph1.x86_64

- krb5-1.14-4.ph1.x86_64

- libarchive-3.1.2-6.ph1.x86_64

- libassuan-2.4.2-2.ph1.x86_64

- libcap-2.25-2.ph1.x86_64

- libffi-3.2.1-2.ph1.x86_64

- libgcc-5.3.0-3.ph1.x86_64

- libgcrypt-1.6.5-2.ph1.x86_64

- libgomp-5.3.0-3.ph1.x86_64

- libgpg-error-1.21-2.ph1.x86_64

- libgsystem-2015.1-2.ph1.x86_64

- libhif-0.2.2-2.ph1.x86_64

- librepo-1.7.17-2.ph1.x86_64

- libselinux-2.5-2.ph1.x86_64

- libsepol-2.5-2.ph1.x86_64

- libsolv-0.6.19-2.ph1.x86_64

- libsoup-2.53.90-2.ph1.x86_64

- libstdc++-5.3.0-3.ph1.x86_64

- libtasn1-4.7-2.ph1.x86_64

- libtool-2.4.6-2.ph1.x86_64

- libxml2-2.9.4-1.ph1.x86_64

- linux-4.4.8-6.ph1.x86_64

- lua-5.3.2-2.ph1.x86_64

- m4-1.4.17-2.ph1.x86_64

- mkinitcpio-19-2.ph1.x86_64

- mpfr-3.1.3-2.ph1.x86_64

- ncurses-6.0-2.ph1.x86_64

- net-tools-1.60-7.ph1.x86_64

- nettle-3.2-2.ph1.x86_64

- nspr-4.12-2.ph1.x86_64

- nss-3.21-2.ph1.x86_64

- nss-altfiles-2.19.1-2.ph1.x86_64

- openssh-7.1p2-3.ph1.x86_64

- openssl-1.0.2h-2.ph1.x86_64

- ostree-2015.7-5.ph1.x86_64

- pcre-8.38-3.ph1.x86_64

- photon-release-1.0-5.ph1.noarch

- pkg-config-0.28-2.ph1.x86_64

- popt-1.16-2.ph1.x86_64

- procps-ng-3.3.11-2.ph1.x86_64

- python2-2.7.11-4.ph1.x86_64

- python2-libs-2.7.11-4.ph1.x86_64

- readline-6.3-4.ph1.x86_64

- rpm-4.11.2-10.ph1.x86_64

- rpm-ostree-2015.7-2.ph1.x86_64

- sed-4.2.2-2.ph1.x86_64

- shadow-4.2.1-7.ph1.x86_64

- sqlite-autoconf-3.11.0-2.ph1.x86_64

- systemd-228-21.ph1.x86_64

- tcsh-6.19.00-4.ph1.x86_64

- util-linux-2.27.1-2.ph1.x86_64

- vim-7.4-5.ph1.x86_64

- which-2.21-2.ph1.x86_64

- xz-5.2.2-2.ph1.x86_64

- zlib-1.2.8-3.ph1.x86_64

-```

-

-### 4.5 Querying for package details

-We are able to use the query option of rpm to make sure any package have been installed properly. The files list should match the previous file mappings in 4.2, so let's check package **rpm-ostree**. As we've seen, manual files listed here are actually missing, they were not installed.

-```

-root@photon-host [ /usr/share/man/man1 ]# rpm -ql  rpm-ostree

-/usr/bin/atomic

-/usr/bin/rpm-ostree

-/usr/lib/girepository-1.0/RpmOstree-1.0.typelib

-/usr/lib/librpmostree-1.so.1

-/usr/lib/librpmostree-1.so.1.0.0

-/usr/lib/rpm-ostree

-/usr/lib/rpm-ostree/tmpfiles-ostree-integration.conf

-/usr/share/man/man1/atomic.1.gz

-/usr/share/man/man1/rpm-ostree.1.gz

-```

-### 4.6 Why am I unable to install, update or delete packages?

-

-All the commands executed so far operated in read-only mode. But what if you want to erase or install a package using our old friend rpm?

-The RPM database is not writable any longer and the file system itself is read-only (except for /var and /etc directories). The idea is that preparing the packages should be done via server tree composition and deployment at host should bring them installed into a new bootable tree that is read-only, recorded into the read-only RPM database. This will insure that all systems deployed are brought into a predictable state and no one could mess with them.

-In fact, tdnf and yum commands are not even available to install new packages at the host. Even if you bring them over, adding a new package via **tdnf install** will return an error.

-But don't get sad. Installing, updating and deleting files & packages the RPM-OSTree way - from the server - that's exactly the topic of next chapters.

-

-[[Back to main page|Photon-RPM-OSTree:-a-simple-guide]] | [[Previous page|Photon-RPM-OStree:-3-Concepts-in-action]]  | [[Next page >|Photon-RPM-OSTree:-5-Host-updating-operations]] 

-

new file mode 100644

@@ -0,0 +1,256 @@

+# Querying For Commit File and Package Metadata

+

+There are several ostree and rpm-ostree commands that list file or package data based on either the Commit ID, or Refspec. If Refspec is passed as a parameter, it's the same as passing the most recent commit ID (head) for that branch.

+

+## 4.1 Commit history

+For a host that is freshly installed, there is only one commit in the history for the only branch.

+```

+root@photon-host [ ~ ]# ostree log photon/1.0/x86_64/minimal

+commit 56ef687f1319604b7900a232715718d26ca407de7e1dc89251b206f8e255dcb4

+Date:  2016-06-07 14:06:17 +0000

+Version: 1.0_minimal

+```

+This commit has no parent; if there was an older commit, it would have been listed too. We can get the same listing (either nicely formatted or raw variant data) by passing the Commit ID. Just the first several hex digits will suffice to identify the commit ID. We can either request to be displayed in a pretty format, or raw - the actual C struct.

+```

+root@photon-host [ ~ ]# ostree log 56ef

+commit 56ef687f1319604b7900a232715718d26ca407de7e1dc89251b206f8e255dcb4

+Date:  2016-06-07 14:06:17 +0000

+Version: 1.0_minimal

+```

+```

+root@photon-host [ ~ ]# ostree log 56ef --raw

+commit 56ef687f1319604b7900a232715718d26ca407de7e1dc89251b206f8e255dcb4

+({'version': <'1.0_minimal'>, 'rpmostree.inputhash': <'40ae75453cf7f00b163848676c4b5716511e7515b95fb7b9168004aa97f05dd9'>}, @ay [], @a(say) [], '', '', uint64 1465308377, [byte 0x3c, 0x6b, 0x71, 0x44, 0x07, 0xd0, 0x5e, 0xd5, 0x9d, 0xfc, 0x4a, 0x1c, 0x33, 0x74, 0x96, 0x1d, 0x50, 0xa3, 0x53, 0xd5, 0xf1, 0x20, 0xb4, 0x40, 0xd0, 0x60, 0x35, 0xf2, 0xf8, 0x29, 0xcf, 0x5f], [byte 0x44, 0x6a, 0x0e, 0xf1, 0x1b, 0x7c, 0xc1, 0x67, 0xf3, 0xb6, 0x03, 0xe5, 0x85, 0xc7, 0xee, 0xee, 0xb6, 0x75, 0xfa, 0xa4, 0x12, 0xd5, 0xec, 0x73, 0xf6, 0x29, 0x88, 0xeb, 0x0b, 0x6c, 0x54, 0x88])

+```

+

+## 4.2 Listing file mappings

+This command lists the file relations between the original source Linux Photon filetree and the deployed filetree. The normal columns include file type type (regular file, directory, link), permissions in chmod octal format, userID, groupID, file size, file name. 

+```

+root@photon-host [ ~ ]# ostree ls photon/1.0/x86_64/minimal

+d00755 0 0      0 /

+l00777 0 0      0 /bin -> usr/bin

+l00777 0 0      0 /home -> var/home

+l00777 0 0      0 /lib -> usr/lib

+l00777 0 0      0 /lib64 -> usr/lib

+l00777 0 0      0 /media -> run/media

+l00777 0 0      0 /mnt -> var/mnt

+l00777 0 0      0 /opt -> var/opt

+l00777 0 0      0 /ostree -> sysroot/ostree

+l00777 0 0      0 /root -> var/roothome

+l00777 0 0      0 /sbin -> usr/sbin

+l00777 0 0      0 /srv -> var/srv

+l00777 0 0      0 /tmp -> sysroot/tmp

+d00755 0 0      0 /boot

+d00755 0 0      0 /dev

+d00755 0 0      0 /proc

+d00755 0 0      0 /run

+d00755 0 0      0 /sys

+d00755 0 0      0 /sysroot

+d00755 0 0      0 /usr

+d00755 0 0      0 /var

+```

+Extra columns can be added like checksum (-C) and extended attributes (-X). 

+```

+root@photon-host [ /usr/share/man/man1 ]# ostree ls photon/1.0/x86_64/minimal -C

+d00755 0 0      0 3c6b714407d05ed59dfc4a1c3374961d50a353d5f120b440d06035f2f829cf5f 446a0ef11b7cc167f3b603e585c7eeeeb675faa412d5ec73f62988eb0b6c5488 /

+l00777 0 0      0 389846c2702216e1367c8dfb68326a6b93ccf5703c89c93979052a9bf359608e /bin -> usr/bin

+l00777 0 0      0 4344c10bf4931483f918496534f12ed9b50dc6a2cead35e3cd9dd898d6ac9414 /home -> var/home

+l00777 0 0      0 f11902ca9d69a80df33918534a3e443251fd0aa7f94b76301e1f55e52aed29dd /lib -> usr/lib

+l00777 0 0      0 f11902ca9d69a80df33918534a3e443251fd0aa7f94b76301e1f55e52aed29dd /lib64 -> usr/lib

+l00777 0 0      0 75317a3df11447c470ffdd63dde045450ca97dfb2a97a0f3f6a21a5da66f737c /media -> run/media

+l00777 0 0      0 97c55dbe24e8f3aecfd3f3e5b3f44646fccbb39799807d37a217e9c871da108b /mnt -> var/mnt

+l00777 0 0      0 46b1abbd27a846a9257a8d8c9fc4b384ac0888bdb8ac0d6a2d5de72715bd5092 /opt -> var/opt

+l00777 0 0      0 d37269e3f46023fd0275212473e07011894cdf4148cbf3fb5758a7e9471dad8e /ostree -> sysroot/ostree

+l00777 0 0      0 6f800e74eed172661278d1e1f09e389a6504dcd3358618e1c1618f91f9d33601 /root -> var/roothome

+l00777 0 0      0 e0bead7be9323b06bea05cb9b66eb151839989e3a4e5d1a93e09a36919e91818 /sbin -> usr/sbin

+l00777 0 0      0 5d4250bba1ed300f793fa9769474351ee5cebd71e8339078af7ebfbe6256d9b5 /srv -> var/srv

+l00777 0 0      0 364fbd62f91ca1e06eb7dbd50c93de8976f2cea633658e2dbe803ce6f7490c09 /tmp -> sysroot/tmp

+d00755 0 0      0 1e4f98d92b35c453d8f61e668aea9fae7ca1863f6609db787374b4ad5caf3b2f 446a0ef11b7cc167f3b603e585c7eeeeb675faa412d5ec73f62988eb0b6c5488 /boot

+d00755 0 0      0 6e340b9cffb37a989ca544e6bb780a2c78901d3fb33738768511a30617afa01d 446a0ef11b7cc167f3b603e585c7eeeeb675faa412d5ec73f62988eb0b6c5488 /dev

+d00755 0 0      0 6e340b9cffb37a989ca544e6bb780a2c78901d3fb33738768511a30617afa01d 446a0ef11b7cc167f3b603e585c7eeeeb675faa412d5ec73f62988eb0b6c5488 /proc

+d00755 0 0      0 6e340b9cffb37a989ca544e6bb780a2c78901d3fb33738768511a30617afa01d 446a0ef11b7cc167f3b603e585c7eeeeb675faa412d5ec73f62988eb0b6c5488 /run

+d00755 0 0      0 6e340b9cffb37a989ca544e6bb780a2c78901d3fb33738768511a30617afa01d 446a0ef11b7cc167f3b603e585c7eeeeb675faa412d5ec73f62988eb0b6c5488 /sys

+d00755 0 0      0 6e340b9cffb37a989ca544e6bb780a2c78901d3fb33738768511a30617afa01d 446a0ef11b7cc167f3b603e585c7eeeeb675faa412d5ec73f62988eb0b6c5488 /sysroot

+d00755 0 0      0 b072f4b3e995a491c04d88636401ca156e80f103b002d724ae76c07174ee4c74 446a0ef11b7cc167f3b603e585c7eeeeb675faa412d5ec73f62988eb0b6c5488 /usr

+d00755 0 0      0 6e340b9cffb37a989ca544e6bb780a2c78901d3fb33738768511a30617afa01d 446a0ef11b7cc167f3b603e585c7eeeeb675faa412d5ec73f62988eb0b6c5488 /var

+```

+

+By default, only the top folders are listed, but -R will list recursively. Instead of listing over 10,000 files, let's filter to just all files that contain 'rpm-ostree', 'rpmostree' or 'RpmOstree', that must belong to **rpm-ostree** package itself.

+```

+root@photon-host [ /usr/share/rpm-ostree ]# ostree ls photon/1.0/x86_64/minimal -R | grep -e '[Rr]pm-\?[Oo]stree'

+l00777 0 0      0 /usr/bin/atomic -> rpm-ostree

+-00755 0 0 131104 /usr/bin/rpm-ostree

+l00777 0 0      0 /usr/lib/librpmostree-1.so.1 -> librpmostree-1.so.1.0.0

+-00755 0 0 104272 /usr/lib/librpmostree-1.so.1.0.0

+-00644 0 0   1296 /usr/lib/girepository-1.0/RpmOstree-1.0.typelib

+d00755 0 0      0 /usr/lib/rpm-ostree

+-00644 0 0    622 /usr/lib/rpm-ostree/tmpfiles-ostree-integration.conf

+-00644 0 0    717 /usr/lib/tmpfiles.d/rpm-ostree-autovar.conf

+d00755 0 0      0 /usr/share/rpm-ostree

+-00644 0 0   1132 /usr/share/rpm-ostree/treefile.json

+```

+

+**atomic** is really an alias for rpm-ostree command. The last file **treefile.json** is not installed by the rpm-ostree package, it's actually downloaded from the server, as we will see in the next chapter. For now, let's notice **"osname" : "photon",  "ref" : "photon/1.0/x86_64/minimal",  "automatic_version_prefix" : "1.0_minimal"**, that matches what we've known so far, and also the **"documentation" : false** setting, that explains why there are no manual files installed for rpm-ostree, and in fact for any package.

+```

+root@photon-host [ /usr/share/rpm-ostree ]# ls -l /usr/share/man/man1 

+total 0

+```

+

+

+## 4.3 Listing configuration changes

+

+To diff the current /etc configuration versus default /etc (from the base image), this command will show the **M**odified, **A**dded and **D**eleted files:

+```

+root@photon-host [ ~ ]# ostree admin config-diff

+M    mtab

+M    ssh/sshd_config

+M    shadow

+M    hosts

+M    fstab

+M    machine-id

+A    ssh/ssh_host_rsa_key

+A    ssh/ssh_host_rsa_key.pub

+A    ssh/ssh_host_dsa_key

+A    ssh/ssh_host_dsa_key.pub

+A    ssh/ssh_host_ecdsa_key

+A    ssh/ssh_host_ecdsa_key.pub

+A    ssh/ssh_host_ed25519_key

+A    ssh/ssh_host_ed25519_key.pub

+A    ssh/sshd.pid

+A    tmpfiles.d/postinstall.sh

+A    udev/hwdb.bin

+A    resolv.conf

+A    hostname

+A    postinstall

+A    localtime

+A    .updated

+```

+

+## 4.4 Listing packages

+As expected, there is an rpm-ostree command that lists all the packages for that branch, extracted from RPM database.   

+```

+root@photon-host [ ~ ]# rpm-ostree db list photon/1.0/x86_64/minimal

+ostree commit: photon/1.0/x86_64/minimal (56ef687f1319604b7900a232715718d26ca407de7e1dc89251b206f8e255dcb4)

+ Linux-PAM-1.2.1-3.ph1.x86_64

+ attr-2.4.47-3.ph1.x86_64

+ autogen-libopts-5.18.7-2.ph1.x86_64

+ bash-4.3.30-4.ph1.x86_64

+ bc-1.06.95-3.ph1.x86_64

+ binutils-2.25.1-2.ph1.x86_64

+ bridge-utils-1.5-2.ph1.x86_64

+ bzip2-1.0.6-5.ph1.x86_64

+ ca-certificates-20160109-5.ph1.x86_64

+ coreutils-8.25-2.ph1.x86_64

+ cpio-2.12-2.ph1.x86_64

+ cracklib-2.9.6-2.ph1.x86_64

+ cracklib-dicts-2.9.6-2.ph1.x86_64

+ curl-7.47.1-2.ph1.x86_64

+ db-6.1.26-2.ph1.x86_64

+ dbus-1.8.8-5.ph1.x86_64

+ device-mapper-2.02.141-5.ph1.x86_64

+ device-mapper-libs-2.02.141-5.ph1.x86_64

+ docker-1.11.0-5.ph1.x86_64

+ dracut-044-3.ph1.x86_64

+ dracut-tools-044-3.ph1.x86_64

+ e2fsprogs-1.42.13-2.ph1.x86_64

+ elfutils-libelf-0.165-2.ph1.x86_64

+ expat-2.1.0-2.ph1.x86_64

+ file-5.24-2.ph1.x86_64

+ filesystem-1.0-7.ph1.x86_64

+ findutils-4.6.0-2.ph1.x86_64

+ flex-2.5.39-2.ph1.x86_64

+ gdbm-1.11-2.ph1.x86_64

+ glib-2.47.6-2.ph1.x86_64

+ glib-networking-2.46.1-2.ph1.x86_64

+ glibc-2.22-8.ph1.x86_64

+ gmp-6.0.0a-3.ph1.x86_64

+ gnutls-3.4.11-2.ph1.x86_64

+ gobject-introspection-1.46.0-2.ph1.x86_64

+ gpgme-1.6.0-2.ph1.x86_64

+ grep-2.21-2.ph1.x86_64

+ grub2-2.02-4.ph1.x86_64

+ gzip-1.6-2.ph1.x86_64

+ hawkey-2014.1-4.ph1.x86_64

+ iana-etc-2.30-2.ph1.noarch

+ iproute2-4.2.0-2.ph1.x86_64

+ iptables-1.6.0-4.ph1.x86_64

+ iputils-20151218-3.ph1.x86_64

+ json-glib-1.0.4-2.ph1.x86_64

+ kmod-21-4.ph1.x86_64

+ krb5-1.14-4.ph1.x86_64

+ libarchive-3.1.2-6.ph1.x86_64

+ libassuan-2.4.2-2.ph1.x86_64

+ libcap-2.25-2.ph1.x86_64

+ libffi-3.2.1-2.ph1.x86_64

+ libgcc-5.3.0-3.ph1.x86_64

+ libgcrypt-1.6.5-2.ph1.x86_64

+ libgomp-5.3.0-3.ph1.x86_64

+ libgpg-error-1.21-2.ph1.x86_64

+ libgsystem-2015.1-2.ph1.x86_64

+ libhif-0.2.2-2.ph1.x86_64

+ librepo-1.7.17-2.ph1.x86_64

+ libselinux-2.5-2.ph1.x86_64

+ libsepol-2.5-2.ph1.x86_64

+ libsolv-0.6.19-2.ph1.x86_64

+ libsoup-2.53.90-2.ph1.x86_64

+ libstdc++-5.3.0-3.ph1.x86_64

+ libtasn1-4.7-2.ph1.x86_64

+ libtool-2.4.6-2.ph1.x86_64

+ libxml2-2.9.4-1.ph1.x86_64

+ linux-4.4.8-6.ph1.x86_64

+ lua-5.3.2-2.ph1.x86_64

+ m4-1.4.17-2.ph1.x86_64

+ mkinitcpio-19-2.ph1.x86_64

+ mpfr-3.1.3-2.ph1.x86_64

+ ncurses-6.0-2.ph1.x86_64

+ net-tools-1.60-7.ph1.x86_64

+ nettle-3.2-2.ph1.x86_64

+ nspr-4.12-2.ph1.x86_64

+ nss-3.21-2.ph1.x86_64

+ nss-altfiles-2.19.1-2.ph1.x86_64

+ openssh-7.1p2-3.ph1.x86_64

+ openssl-1.0.2h-2.ph1.x86_64

+ ostree-2015.7-5.ph1.x86_64

+ pcre-8.38-3.ph1.x86_64

+ photon-release-1.0-5.ph1.noarch

+ pkg-config-0.28-2.ph1.x86_64

+ popt-1.16-2.ph1.x86_64

+ procps-ng-3.3.11-2.ph1.x86_64

+ python2-2.7.11-4.ph1.x86_64

+ python2-libs-2.7.11-4.ph1.x86_64

+ readline-6.3-4.ph1.x86_64

+ rpm-4.11.2-10.ph1.x86_64

+ rpm-ostree-2015.7-2.ph1.x86_64

+ sed-4.2.2-2.ph1.x86_64

+ shadow-4.2.1-7.ph1.x86_64

+ sqlite-autoconf-3.11.0-2.ph1.x86_64

+ systemd-228-21.ph1.x86_64

+ tcsh-6.19.00-4.ph1.x86_64

+ util-linux-2.27.1-2.ph1.x86_64

+ vim-7.4-5.ph1.x86_64

+ which-2.21-2.ph1.x86_64

+ xz-5.2.2-2.ph1.x86_64

+ zlib-1.2.8-3.ph1.x86_64

+```

+

+## 4.5 Querying for package details

+We are able to use the query option of rpm to make sure any package have been installed properly. The files list should match the previous file mappings in 4.2, so let's check package **rpm-ostree**. As we've seen, manual files listed here are actually missing, they were not installed.

+```

+root@photon-host [ /usr/share/man/man1 ]# rpm -ql  rpm-ostree

+/usr/bin/atomic

+/usr/bin/rpm-ostree

+/usr/lib/girepository-1.0/RpmOstree-1.0.typelib

+/usr/lib/librpmostree-1.so.1

+/usr/lib/librpmostree-1.so.1.0.0

+/usr/lib/rpm-ostree

+/usr/lib/rpm-ostree/tmpfiles-ostree-integration.conf

+/usr/share/man/man1/atomic.1.gz

+/usr/share/man/man1/rpm-ostree.1.gz

+```

+## 4.6 Why am I unable to install, update or delete packages?

+

+All the commands executed so far operated in read-only mode. But what if you want to erase or install a package using our old friend rpm?

+The RPM database is not writable any longer and the file system itself is read-only (except for /var and /etc directories). The idea is that preparing the packages should be done via server tree composition and deployment at host should bring them installed into a new bootable tree that is read-only, recorded into the read-only RPM database. This will insure that all systems deployed are brought into a predictable state and no one could mess with them.

+In fact, tdnf and yum commands are not even available to install new packages at the host. Even if you bring them over, adding a new package via **tdnf install** will return an error.

+But don't get sad. Installing, updating and deleting files & packages the RPM-OSTree way - from the server - that's exactly the topic of next chapters.

+

@@ -1,4 +1,6 @@

-### 5.1 Is it an update or an upgrade?