You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: environments.html.md.erb
+13-13
Original file line number
Diff line number
Diff line change
@@ -8,19 +8,19 @@ This topic explains how to set up tile development environments, from simple sta
8
8
9
9
## <aid="pcfdev"></a><%=vars.product_dev_local%> and BOSH-Lite
10
10
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
12
12
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%>.
14
14
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).
16
16
17
17
If your integration includes managed services, you will also need an instance
18
18
of BOSH that can manage virtual machines and BOSH releases for you.
19
19
[BOSH-Lite](https://github.com/cloudfoundry/bosh-lite) works well for that
20
20
purpose.
21
21
22
22
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
24
24
<%=vars.platform_name%> environment until the later phases of your development.
25
25
26
26
### <aid="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
31
31
32
32
### <aid="setup-pcfdev"></a>Setting up <%=vars.product_dev_local%>
33
33
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)
35
35
36
36
37
37
## <aid="pws"></a>PWS or Other Supported CF Infrastructure
38
38
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.
40
40
41
41
- [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).
42
42
43
-
## <aid="pcf"></a><%=vars.platform_name%> with Ops Manager
43
+
## <aid="pcf"></a><%=vars.app_runtime_abbr%> with Ops Manager
44
44
45
-
### <aid="shared"></a>Shared <%=vars.platform_name%> Development Environments for Pivotal Partners
45
+
### <aid="shared"></a>Shared <%=vars.app_runtime_abbr%> Development Environments for VMware Tanzu Partners
46
46
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,
48
48
called Pivotal Integration Environments (PIEs),
49
49
for Pivotal Technical Partnership Program (PTPP) program members to develop their tiles on.
50
50
51
51
To use your assigned PIE environment:
52
52
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/)
54
54
using the credentials that you use for [Pivotal Partners Slack](https://pivotalpartners.slack.com/).
55
55
1. Click the `pie-xx` environment assigned to you.
56
56
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.
58
58
59
59
If you are not in the PTPP or cannot access Pivotal Partners Slack, email [email protected].
60
60
61
-
### <aid="diy"></a>Install Your Own <%=vars.platform_name%> Environment
61
+
### <aid="diy"></a>Install Your Own <%=vars.app_runtime_abbr%> Environment
62
62
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:
Copy file name to clipboardexpand all lines: pcf-command.html.md.erb
+8-8
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ owner: Services
6
6
The `pcf` utility provides a command line interface to <%= vars.platform_name %> for
7
7
the purpose of deploying and testing tiles. Its primary reason for existence is
8
8
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.
10
10
11
11
The `pcf` utility also allows you to test your tile's BOSH errands
12
12
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
37
37
For interactive use, this means that you will have to create a `metadata`
38
38
file in the directory where you run the `pcf` command.
39
39
40
-
<pclass='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
+
<pclass='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>
41
41
42
42
##<aid="commands"></a> Commands
43
43
@@ -117,7 +117,7 @@ $ pcf settings test-tile
117
117
118
118
After your software works and correctly deploys using `test-errand`, you can go
119
119
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.
121
121
122
122
Import your .pivotal file into Ops Manager:
123
123
@@ -131,9 +131,9 @@ Install the uploaded version of your product:
131
131
$ pcf install test-tile 0.0.2
132
132
```
133
133
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`
135
135
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%>),
137
137
to avoid the need to upload a tile-specific stemcell.
138
138
139
139
```bash
@@ -215,9 +215,9 @@ up Ops Manager's available products (and disk space):
Copy file name to clipboardexpand all lines: publish.html.md.erb
+14-7
Original file line number
Diff line number
Diff line change
@@ -8,14 +8,14 @@ This topic provides resources to help you publish and update your service tile f
8
8
9
9
## <aid="publish"></a> Publish Your Tile
10
10
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).
13
13
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:
15
15
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
-

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.
0 commit comments