Shawn Neal sneal

Assumptions

.NET 8 app
dotnet buildpack
CF SSH access

Publish

We need to the dotnet CLI installed on the target application instance. To get dotnet installed and not have the buildpack remove it during staging we need to use a Framework Dependent Deployment. If you're running dotnet publish on an ARM processor you need to specify the runtime as linux-x64 otherwise you will get an error trying to start the app.

Migrate BOSH Azure MySQL DB to a new instance

These step describe the steps necessary to move a BOSH external MySQL 5.7 databases on Azure to a new instance.

Stop BOSH Director VM

Stop the BOSH Director VM in Azure. You can find the VM name in the Operations Manager BOSH Director tile under the Status tab. From the Azure CLI:

az vm stop --resource-group tas-resourcegroup --name 85a181e5-aa6b-4ea7-47b0-b2218b46002a

TAS 4.0.20+ has ability to limit the log rate (bytes/sec) of applications to avoid having a single application overwhelm the logging system in Cloud Foundry.

The general settings or ways to configure logging limits are:

"Default log rate limit per app" in the TAS tile under App Developer Controls
CF org/space quotas
log-rate-limit-per-second app setting

Default log rate limit per app

The global default setting is just that, a default. It's the same as setting the per-app log-rate-limit-per-second on every single app in the foundation. This is not a way to keep devs from overriding this value. Devs can override

Migration to TAS Internal MySQL

Migrating from an externally hosted MySQL DB server such as RDS or Oracle MySQL to the internally managed TAS HA cluster MySQL requires some extra steps to avoid application downtime. To avoid unnecessary downtime and churn we want to avoid having TAS system components ever see an empty MySQL database.

At a high level the overall procedure is:

create single internal mysql instance
bosh stop cloud_controller

This PowerCLI snippet can be used to find all the BOSH VMs connected to a specific datastore and then disconnect the CD-ROM to avoid vMotion or SDRS errors.

Open a PowerCLI session and login to the appropriate vCenter using the Connect-VIServer command.
Copy the below eject-iso.ps1 snippet locally
Change the datastore name, from dsname to whatever your datastore name is.
Execute the script

The final output table will contain all the VMs processed and list out the updated ISOPaths which should be empty at this point.

NOTE The script only modifies BOSH VMs, i.e. those with mounted env.iso files, however the output will display all VMs on the specified datastore and any other non-BOSH ISOs mounted.

This topic describes how to change your VMware Tanzu Operations Manager (Ops Manager) installation's underlying vSphere datastore clusters.

Before You Begin

The following sections describe the steps you can do prior to the migration.

Step 1: Back Up Your Environment

Ensure that your Ops Manager environment is fully backed up.

For more information about how to back up Ops Manager, see Backing Up Deployments.

	product-name: p-isolation-segment-iso3
	product-properties:
	.isolated_router_iso3.disable_insecure_cookies:
	value: false
	.isolated_router_iso3.drain_timeout:
	value: 900
	.isolated_router_iso3.drain_wait:
	value: 20
	.isolated_router_iso3.enable_w3c:
	value: false

	package main

	import (
	"context"
	"fmt"
	"github.com/cloudfoundry-community/go-cfclient/v3/client"
	"github.com/cloudfoundry-community/go-cfclient/v3/config"
	"github.com/cloudfoundry-community/go-cfclient/v3/resource"
	"os"
	)

	func (c Config) OAuth2HTTPClient(ctx context.Context) (http.Client, error) {
	// if explicitly configured with an oauth2 transport then use as-is
	if _, ok := c.httpClient.Transport.(*oauth2.Transport); ok {
	return c.httpClient, nil
	}

	// use our http.Client instance for token acquisition
	oauthCtx := context.WithValue(ctx, oauth2.HTTPClient, c.httpClient)

	var tokenSource oauth2.TokenSource

	This topic describes how to migrate your VMware Tanzu Operations Manager (Ops Manager) installation to a new vSphere datastore.

	Prerequisites
	Both the new and existing vSphere datastores must reside in the same data center.

	To avoid service disruption, VMware recommends that you configure your overall Ops Manager deployment for high availability (HA). In addition, check for configurations necessary to achieve HA in each of your installed product tiles.

	If your environment has any single points of failure, service might be disrupted as a result of the migration.

	Before You Begin