CCM-15541: Gateway Cluster Deployment#222
Conversation
jamesthompson26-nhs
changed the title
jamesthompson26-nhs
force-pushed
the
feature/CCM-15541_Gateway_Cluster_Deployment
branch
from
0a6706e to
056d713
Compare
jamesthompson26-nhs
force-pushed
the
feature/CCM-15541_Gateway_Cluster_Deployment
branch
from
a19b9db to
9469a5a
Compare
jamesthompson26-nhs
force-pushed
the
feature/CCM-15541_Gateway_Cluster_Deployment
branch
from
13ae797 to
39565cc
Compare
|
should we be looking at win server 2025? |
|
|
||
| # Install vim | ||
| choco install -y vim | ||
| choco install -y powerbigateway --ignore-checksums |
There was a problem hiding this comment.
So version pining dont work with choco for this? Should we look at alternative?
There was a problem hiding this comment.
it's the Gateway installer itself that seems to automatically pull the latest version at install time.
There was a problem hiding this comment.
Removed the chocolately install altogether. Via a deep dive search and thanks to a reddit post, I've found a download page for previous versions that work: https://learn.microsoft.com/en-us/data-integration/gateway/service-gateway-monthly-updates
There was a problem hiding this comment.
Removed the chocolately install altogether. Via a deep dive search and thanks to a reddit post, I've found a download page for previous versions that work: https://learn.microsoft.com/en-us/data-integration/gateway/service-gateway-monthly-updates
|
3 participants
Description
Context
Required preparation to migrate off the incorrectly deployed Production instance.
My proposal is we should set up the 2 currently unused standalone instances as NEW Gateway cluster in the PowerBI service and migrate the reports to use this and then remove the existing cluster and underlying un-managed instance.
We cannot replicate accurately the state of Production currently so I'm proposing this as a way to parallel run with the existing Prod gateway and safely test the migration of reports onto the new logical gateway cluster. This should hopefully bring parity between NonProd and Prod, fix the patching schedule (1 instance in the cluster is patched on a Weds, 1 on a Sunday) and moving forward, Gateway software updates can be done via the PowerBI service console.
Next Steps
Once merged and deployed into Dev/NonProd we'll need Ross to configure the gateway in the PowerBI Service. it would then be good if we could get Grace to create 1 or more reports (I appreciate the data is nonsense) so that we can firstly test the gateway functionality, but also use them for PTL testing in the future.
Type of changes
Checklist
Sensitive Information Declaration
To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.