Skip to content

Commit b62b88b

Browse files
committed
rebranding [#171728965]
1 parent f67744a commit b62b88b

13 files changed

+123
-113
lines changed

concourse.html.md.erb

+12-12
Original file line numberDiff line numberDiff line change
@@ -5,12 +5,11 @@ owner: Services
55

66
This topic describes how to do continuous integration (CI) testing on your tile.
77

8-
98
There are two ways to do CI testing on your tile:
109

11-
+ Use the Tile Dashboard provided as a service by the Pivotal ISV team.<br>
10+
+ Use the Tile Dashboard provided as a service by the <%= vars.company_name %> ISV team.<br>
1211
See [Use Tile Dashboard CI to Test Your Tile](#dashboard) below.<br>
13-
This is the method recommended by Pivotal.
12+
This is the method recommended by <%= vars.company_name %>.
1413
+ Set up and use your own Concourse pipeline.<br>
1514
See [Set Up a Concourse Pipeline and Test Your Tile](#concourse) below.<br>
1615
This method is more time consuming and not recommended for new partners
@@ -34,15 +33,16 @@ For an introduction to our readiness criteria, see
3433

3534
The Tile Dashboard CI runs your tile through a series of steps, which include:
3635

37-
1. Downloading your tile from the Pivotal Network and checking hash integrity.
36+
1. Downloading your tile from the VMware Tanzu Network and checking hash integrity.
3837

3938
2. Scanning your tile for known issues or potential problems, like:
4039
- Use of deprecated properties.
4140
- Use of properties whose values/meanings have changed.
4241
- Use of features that are no longer supported.
4342

4443
3. Configuring, installing, testing, and uninstalling your tile in several <%= vars.platform_name %> environments:
45-
- A patch release of every supported Pivotal Application Service minor version.
44+
- A patch release of every supported
45+
<%= vars.app_runtime_full %> minor version.
4646
- Every supported IaaS
4747
- Environments with extra configuration, such as multiple availability zones and IPsec
4848

@@ -62,24 +62,24 @@ Before you use the Tile Dashboard to configure and test your tile, verify the fo
6262

6363

6464

65-
+ Your tile is uploaded to the [Pivotal Network](https://network.pivotal.io/).
65+
+ Your tile is uploaded to the [VMware Tanzu Network](https://network.pivotal.io/).
6666

6767
| If you are uploading a&hellip; | Then&hellip; |
6868
|------------------------------------|--------------|
6969
| first release | contact the technical program management of the ISV team. |
70-
| subsequent release| you can upload pre-releases to the Pivotal Network.|
70+
| subsequent release| you can upload pre-releases to the VMware Tanzu Network.|
7171

7272

7373
### <a id="intro"></a> About Configuring a Tile on the Tile Dashboard
7474

75-
After your tile has been uploaded to the Pivotal Network, the Tile Dashboard starts to stage and scan it.
75+
After your tile has been uploaded to the VMware Tanzu Network, the Tile Dashboard starts to stage and scan it.
7676
For new tiles, this can take up to an hour.
7777

7878
After the stage and scan, you need to configure your tile on the Tile Dashboard.
7979
Configuration specfies how the tile is installed on the test environment.
8080

8181
Configuring your tile through the Tile Dashboard is equivalent to configuring the tile on Ops Manager
82-
after downloading it from the Pivotal Network.
82+
after downloading it from the VMware Tanzu Network.
8383

8484
There are two ways that you can configure the tile on the Tile Dashboard:
8585

@@ -247,13 +247,13 @@ With more effort, you can also follow the pointers below to set up your own Conc
247247
that integrates and tests your tile on your own deployment of the latest <%= vars.platform_name %>.
248248

249249
While you are of course also free to use any other CI system you are familiar with,
250-
Pivotal's tools and documentation are built to make Concourse CI as easy as possible.
250+
<%= vars.company_name %>'s tools and documentation are built to make Concourse CI as easy as possible.
251251

252252
### <a id="server"></a> Set Up a Concourse Server
253253

254254
You need a Concourse server to host your pipeline.
255255

256-
If you partner with Pivotal,
256+
If you partner with <%= vars.company_name %>,
257257
the [Tile Dashboard CI](#tile-dashboard-ci) servers can host your pipeline
258258
and provide S3 storage to exchange artifacts with your own servers.
259259

@@ -276,7 +276,7 @@ the process of generating a pipeline template for you.
276276

277277
### <a id="pool"></a> Set Up <%= vars.platform_name %> for Your CI Pipeline
278278

279-
Pivotal partners who have us host their pipeline have access to a pool of <%= vars.platform_name %>
279+
<%= vars.company_name %> partners who have us host their pipeline have access to a pool of <%= vars.platform_name %>
280280
instances that are managed by us and are regularly updated with the latest
281281
(pre-)release versions of <%= vars.platform_name %>. If you set up your own concourse server, you
282282
have to target your pipeline at a [<%= vars.platform_name %> instance you have setup](./environments.html).

environments.html.md.erb

+13-13
Original file line numberDiff line numberDiff line change
@@ -8,19 +8,19 @@ This topic explains how to set up tile development environments, from simple sta
88

99
## <a id="pcfdev"></a> <%= vars.product_dev_local %> and BOSH-Lite
1010

11-
Pivotal provides a lightweight (vagrant packaged) instance of <%= vars.platform_name %> with some
11+
<%= vars.company_name %> provides a lightweight (vagrant packaged) instance of <%= vars.app_runtime_full %> (<%= vars.app_runtime_abbr %>) with some
1212
basic services as a free product named <%= vars.product_dev_local %>. This is a great environment
13-
to develop and test everything that runs in Pivotal Application Service.
13+
to develop and test everything that runs in <%= vars.app_runtime_abbr %>.
1414

15-
Either of these environments allow you to develop the first three levels of service for <%= vars.platform_name %>: a [User-Provided Service](./user-provided.html), a [Brokered Service](./brokered.html), and a [Managed Service](./managed.html).
15+
Either of these environments allow you to develop the first three levels of service for <%= vars.app_runtime_abbr %>: a [User-Provided Service](./user-provided.html), a [Brokered Service](./brokered.html), and a [Managed Service](./managed.html).
1616

1717
If your integration includes managed services, you will also need an instance
1818
of BOSH that can manage virtual machines and BOSH releases for you.
1919
[BOSH-Lite](https://github.com/cloudfoundry/bosh-lite) works well for that
2020
purpose.
2121

2222
Between these two components, you will have everything you need to develop
23-
tiles, except for Pivotal's Ops Manager. But if you followed the recommended workflow in [Building Your First Tile](./index.html#tile-steps) you will not need an actual full
23+
tiles, except for Ops Manager. But if you followed the recommended workflow in [Building Your First Tile](./index.html#tile-steps) you will not need an actual full
2424
<%= vars.platform_name %> environment until the later phases of your development.
2525

2626
### <a id="setup-boshlite"></a>Setting up BOSH-Lite
@@ -31,36 +31,36 @@ tiles, except for Pivotal's Ops Manager. But if you followed the recommended wor
3131

3232
### <a id="setup-pcfdev"></a>Setting up <%= vars.product_dev_local %>
3333

34-
- [Try <%= vars.platform_name %> on your Local Workstation](http://pivotal.io/platform/pcf-tutorials/getting-started-with-pivotal-cloud-foundry-dev/introduction)
34+
- [Try <%= vars.app_runtime_abbr %> on your Local Workstation](http://pivotal.io/platform/pcf-tutorials/getting-started-with-pivotal-cloud-foundry-dev/introduction)
3535

3636

3737
## <a id="pws"></a>PWS or Other Supported CF Infrastructure
3838

39-
Pivotal Web Services (PWS) is a highly-available, production-scale <%= vars.platform_name %> environment hosted by Pivotal. You can use it to develop and run <%= vars.platform_name %> apps, but a PWS account does not give access to Ops Manager and its Installation Dashboard, which is where <%= vars.platform_name %> operators install and configure tiles.
39+
Pivotal Web Services (PWS) is a highly-available, production-scale %= vars.app_runtime_abbr %> environment hosted by <%= vars.company_name %>. You can use it to develop and run <%= vars.app_runtime_abbr %> apps, but a PWS account does not give access to Ops Manager and its Installation Dashboard, which is where operators install and configure tiles.
4040

4141
- [Set Up Your PWS Account and Download the cf CLI](http://docs.run.pivotal.io/starting/index.html) explains how to get started with Pivotal Web Services (PWS).
4242

43-
## <a id="pcf"></a><%= vars.platform_name %> with Ops Manager
43+
## <a id="pcf"></a><%= vars.app_runtime_abbr %> with Ops Manager
4444

45-
### <a id="shared"></a>Shared <%= vars.platform_name %> Development Environments for Pivotal Partners
45+
### <a id="shared"></a>Shared <%= vars.app_runtime_abbr %> Development Environments for VMware Tanzu Partners
4646

47-
Pivotal operates and manages a number of shared <%= vars.platform_name %> development environments,
47+
<%= vars.company_name %> operates and manages a number of shared <%= vars.app_runtime_abbr %> development environments,
4848
called Pivotal Integration Environments (PIEs),
4949
for Pivotal Technical Partnership Program (PTPP) program members to develop their tiles on.
5050

5151
To use your assigned PIE environment:
5252

53-
1. Log in to the Pivotal [Tile Dashboard](https://tile-dashboard.cfapps.io/)
53+
1. Log in to the <%= vars.company_name %> [Tile Dashboard](https://tile-dashboard.cfapps.io/)
5454
using the credentials that you use for [Pivotal Partners Slack](https://pivotalpartners.slack.com/).
5555
1. Click the `pie-xx` environment assigned to you.
5656
1. Log in to Ops Manager with the given Ops Manager URL and credentials.
57-
1. Log in to Pivotal Apps Manager or the cf CLI with the Cloud Foundry information provided on the same page.
57+
1. Log in to Apps Manager or the cf CLI with the Cloud Foundry information provided on the same page.
5858

5959
If you are not in the PTPP or cannot access Pivotal Partners Slack, email [email protected].
6060

61-
### <a id="diy"></a>Install Your Own <%= vars.platform_name %> Environment
61+
### <a id="diy"></a>Install Your Own <%= vars.app_runtime_abbr %> Environment
6262

63-
If you need an isolated or dedicated <%= vars.platform_name %> development environment, or you need to work offline, you can install your own environment that includes Pivotal's Ops Manager:
63+
If you need an isolated or dedicated <%= vars.app_runtime_abbr %> development environment, or you need to work offline, you can install your own environment that includes Ops Manager:
6464

6565
- [Installing <%= vars.platform_name %>](http://docs.pivotal.io/pivotalcf/installing/index.html)
6666
<a name="operations"></a>

migrating-syslog-configuration.html.md.erb

+1-1
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ owner: Ops Manager
55

66

77
This topic explains how to migrate existing syslog properties that are defined by a tile into the
8-
syslog form provided by Ops Manager in <%= vars.platform_name %> v2.5 and later.
8+
syslog form provided in Ops Manager v2.5 and later.
99

1010
By enabling the Ops Manager syslog feature, Ops Manager:
1111

pcf-command.html.md.erb

+8-8
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ owner: Services
66
The `pcf` utility provides a command line interface to <%= vars.platform_name %> for
77
the purpose of deploying and testing tiles. Its primary reason for existence is
88
to enable Ops Manager access from CI pipelines, but developers also find it
9-
convenient to use this CLI rather than the Ops manager GUI.
9+
convenient to use this CLI rather than the Ops Manager UI.
1010

1111
The `pcf` utility also allows you to test your tile's BOSH errands
1212
directly from your CLI, without going through Ops Manager and BOSH. This greatly
@@ -37,7 +37,7 @@ credentials of a "claimed" <%= vars.platform_name %> pool resource to the CI pip
3737
For interactive use, this means that you will have to create a `metadata`
3838
file in the directory where you run the `pcf` command.
3939

40-
<p class='note'>Pivotal recommends that you do <strong>not</strong> create this file inside your git or other version control system repository, as you do not want to accidentally commit these credentials to version control.</p>
40+
<p class='note'><%= vars.company_name %> recommends that you do <strong>not</strong> create this file inside your git or other version control system repository, as you do not want to accidentally commit these credentials to version control.</p>
4141

4242
##<a id="commands"></a> Commands
4343

@@ -117,7 +117,7 @@ $ pcf settings test-tile
117117

118118
After your software works and correctly deploys using `test-errand`, you can go
119119
through the real Ops Manager deployment process from the CLI, as you would
120-
normally do through the Ops Manager GUI.
120+
normally do through the Ops Manager UI.
121121

122122
Import your .pivotal file into Ops Manager:
123123

@@ -131,9 +131,9 @@ Install the uploaded version of your product:
131131
$ pcf install test-tile 0.0.2
132132
```
133133

134-
Where you would normally configure the tile settings in the GUI, the `configure`
134+
Where you would normally configure the tile settings in the UI, the `configure`
135135
command lets you pass in any user-specified properties as a .yml file. This command
136-
also sets the stemcell for the tile to the same one used by Pivotal Application Service,
136+
also sets the stemcell for the tile to the same one used by <%= vars.app_runtime_full %> (<%= vars.app_runtime_abbr %>),
137137
to avoid the need to upload a tile-specific stemcell.
138138

139139
```bash
@@ -215,9 +215,9 @@ up Ops Manager's available products (and disk space):
215215
$ pcf delete-unused-products
216216
```
217217

218-
##<a id="access-ert"></a> Accessing PAS
218+
##<a id="access-ert"></a> Accessing <%= vars.app_runtime_abbr %>
219219

220-
To see details about the Pivotal Application Service of your <%= vars.platform_name %> environment:
220+
To see details about the <%= vars.app_runtime_abbr %> of your <%= vars.platform_name %> environment:
221221

222222
```bash
223223
$ pcf cf-info
@@ -229,7 +229,7 @@ $ pcf cf-info
229229
- system_services_username: system_services
230230
```
231231

232-
To target your `cf` command line at this <%= vars.platform_name %> environment:
232+
To target your `cf` command line at this <%= vars.app_runtime_abbr %> environment:
233233

234234
```bash
235235
$ pcf target

publish.html.md.erb

+14-7
Original file line numberDiff line numberDiff line change
@@ -8,14 +8,14 @@ This topic provides resources to help you publish and update your service tile f
88

99
## <a id="publish"></a> Publish Your Tile
1010

11-
[The Pivotal Partner Software Product Release Cycle](./releases.html) explains how Pivotal works with partners to release <%= vars.platform_name %> products,
12-
from the private alpha and closed beta phases, to general availability and publication on [Pivotal Network](http://network.pivotal.io).
11+
The [Partner Software Product Release Cycle](./releases.html) explains how <%= vars.company_name %> works with partners to release VMware Tanzu products,
12+
from the private alpha and closed beta phases, to general availability and publication on [VMware Tanzu Network](http://network.pivotal.io).
1313

14-
After you've packaged your product's BOSH releases, stemcell, metadata, and other tile components into a single zipped download file, post it to Pivotal Network in one of two ways:
14+
After you've packaged your product's BOSH releases, stemcell, metadata, and other tile components into a single zipped download file, post it to VMware Tanzu Network in one of two ways:
1515

16-
* Use the Pivotal Network [API command](https://network.pivotal.io/docs/api#public/docs/api/v2/product_files.md) `POST /api/v2/products/:product_slug/product_files`.
17-
* Use the Pivotal Network product upload form.
18-
![Pivnet Upload GUI](img/pivnet-upload.png)
16+
* Use the VMware Tanzu Network [API command](https://network.pivotal.io/docs/api#public/docs/api/v2/product_files.md) `POST /api/v2/products/:product_slug/product_files`.
17+
* Use the VMware Tanzu Network product upload form.
18+
![VMware Tanzu Network Upload GUI](img/pivnet-upload.png)
1919

2020
## <a id="update"></a> Update Your Tile
2121

@@ -28,7 +28,14 @@ For more information, see [Versioning](./tile-generator.html#versioning) in the
2828
* [Tile Upgrades](./tile-upgrades.html) explains how to write and include a JavaScript file that automates tile upgrades
2929
by migrating property names and values from one tile version to another.
3030

31-
* When changes to <%= vars.platform_name %> require tile changes, Pivotal distributes instructions to all of its partners:
31+
* When changes to <%= vars.platform_name %> require tile changes, <%= vars.company_name %> distributes instructions to all of its partners:
32+
* [Ops Manager v2.9 Partners Release Notice](http://docs.pivotal.io/tiledev/2-9/release-notes.html)
33+
* [Pivotal Platform v2.8 Partners Release Notice](http://docs.pivotal.io/tiledev/2-8/release-notes.html)
34+
* [Pivotal Platform v2.7 Partners Release Notice](http://docs.pivotal.io/tiledev/2-7/release-notes.html)
35+
* [Pivotal Cloud Foundry v2.6 Partners Release Notice](http://docs.pivotal.io/tiledev/2-6/release-notes.html)
36+
* [Pivotal Cloud Foundry v2.5 Partners Release Notice](http://docs.pivotal.io/tiledev/2-5/release-notes.html)
37+
* [Pivotal Cloud Foundry v2.4 Partners Release Notice](http://docs.pivotal.io/tiledev/2-4/release-notes.html)
38+
* [Pivotal Cloud Foundry v2.3 Partners Release Notice](http://docs.pivotal.io/tiledev/2-3/release-notes.html)
3239
* [Pivotal Cloud Foundry v2.2 Partners Release Notice](http://docs.pivotal.io/tiledev/2-2/release-notes.html)
3340
* [Pivotal Cloud Foundry v2.1 Partners Release Notice](http://docs.pivotal.io/tiledev/2-1/release-notes.html)
3441
* [Pivotal Cloud Foundry v2.0 Partners Release Notice](http://docs.pivotal.io/tiledev/2-0/release-notes.html)

reference.html.md.erb

+7
Original file line numberDiff line numberDiff line change
@@ -39,6 +39,13 @@ Here are some great resources on how to best troubleshoot more complex issues:
3939

4040
## <a id="release-notices"></a>Partners Release Notices
4141

42+
* [Ops Manager v2.9 Partners Release Notice](http://docs.pivotal.io/tiledev/2-9/release-notes.html)
43+
* [Pivotal Platform v2.8 Partners Release Notice](http://docs.pivotal.io/tiledev/2-8/release-notes.html)
44+
* [Pivotal Platform v2.7 Partners Release Notice](http://docs.pivotal.io/tiledev/2-7/release-notes.html)
45+
* [Pivotal Cloud Foundry v2.6 Partners Release Notice](http://docs.pivotal.io/tiledev/2-6/release-notes.html)
46+
* [Pivotal Cloud Foundry v2.5 Partners Release Notice](http://docs.pivotal.io/tiledev/2-5/release-notes.html)
47+
* [Pivotal Cloud Foundry v2.4 Partners Release Notice](http://docs.pivotal.io/tiledev/2-4/release-notes.html)
48+
* [Pivotal Cloud Foundry v2.3 Partners Release Notice](http://docs.pivotal.io/tiledev/2-3/release-notes.html)
4249
* [Pivotal Cloud Foundry v2.2 Partners Release Notice](http://docs.pivotal.io/tiledev/2-2/release-notes.html)
4350
* [Pivotal Cloud Foundry v2.1 Partners Release Notice](http://docs.pivotal.io/tiledev/2-1/release-notes.html)
4451
* [Pivotal Cloud Foundry v2.0 Partners Release Notice](http://docs.pivotal.io/tiledev/2-0/release-notes.html)

0 commit comments

Comments
 (0)