This is an example tile contained in one metadata file to get more familiar with PCF Tile structure. This is in opposition to how kiln works by separating out the different requirements of a Tile and "baking" it back into one (useful for very large tiles).
- Anyone curious about how tiles in Ops Manager are made
- Cloud Foundry contributors who want to understand how Ops Manager functions to deploy Pivotal Cloud Foundry
- BOSH release authors who want to see how releases get incorporated into Pivotal Cloud Foundry
Clone this repo. Then, from within the repo, create the tile
(hello-pcf-tile.pivotal):
zip -r products/hello-pcf-tile-v99.pivotal . -i "*metadata/*" "migrations/*" "releases/*"
Log into Ops Manager. On the Installation Dashboard, click Import a Product.
Upload products/hello-pcf-tile-v99.pivotal.
Product tiles make it easy for cloud operators to offer new and upgraded software services to developers in a Pivotal Cloud Foundry (PCF) deployment. Pivotal Network distributes these tiles as zipped code directories, with filename extension .pivotal, that contain or point to all of the software elements that perform the tile’s functions.
In the Ops Manager Installation Dashboard, service tiles present a form-based interface that cloud operators use to configure the service. These configured properties become part of the BOSH manifest that PCF uses to deploy instances of the service.
Tiles are composed of BOSH releases, a tile manifest, and migrations.
The tiles shown in the Ops Manager dashboard below include:
- BOSH Director for GCP
- Pivotal Application Service
- MySQL for Pivotal Cloud Foundry v2
Tiles are a way to package and configure instance groups and jobs for Pivotal Cloud Foundry through the Ops Manager web UI. In particular, it provides the way to configure and deploy your Pivotal Cloud Foundry through the Pivotal Application Service (PAS) tile. They do not exist in the open source world.
In the open source Cloud Foundry, ops files that are applied to your CF deployment are the functional equivalent of Ops Manager tiles.
Ops Manager is a web application that you use to deploy and manage a Pivotal Cloud Foundry (PCF) PaaS.
When an operator configures a tile, Ops Manager takes the information, and under the hood, translates it into a BOSH manifest (that defines properties for each job that the manifest deploys) which gets applied to the Pivotal Cloud Floundry deployment.
Essentially, Ops Manager is a way to abstract away the complications that arise with generating and maintaining a massive BOSH deployment manifest and creating the appropriate ops files to configure your Cloud Foundry.
The goal of hello-pcf-tile is an exploration into tile structure, BOSH manifests, and perhaps creating BOSH releases to be packaged up into a tile and used with Ops Manager.
The main purpose is to get a better handle on the different moving parts of a tile and document each part within the tile metadata itself. In particular, how each section relates to each other and how it translates in the Ops Manager UI as well as the underlying BOSH manifest.
The idea of this exploration is translate the base understanding of a singular tile metadata file to how that corresponds to using kiln to maintain an enormous tile, such as Pivotal Application Service.
Refer to the sections in the Wiki
- How Tiles Work
- Product Template Reference (Ops Manager Manifest Docs)
- Ops Manager Example Tile Repo
- om CLI— CLI for Ops Manager's API.
- Ultimate Guide to BOSH
- BOSH docs
- BOSH release PCF Docs
- learn-bosh-release
- Ops Files
- Deploying Cloud Foundry — How to deploy CF withouth Ops Manager.
- Tile Generator Tool — Tool to generate a new tile template.
- PCF Command Line Utility
- smith