Update nexus: fix conflicts and sync local changes
This commit is contained in:
Shen Wei
@@ -1,79 +1,79 @@
|
||||
# Enable-Optic-Data-Lake-Preparation_688996348
|
||||
This is wiki helps the R&D team for the preparation of ESM and Operation Platform Integration for a tenant.
|
||||
|
||||
Pre-condition:
|
||||
|
||||
ESM is deployed in a namsapce
|
||||
|
||||
Operation Platfrom is deployed a diferent namepsace
|
||||
|
||||
Automation Center capabilty is enabled for a Tenant
|
||||
|
||||
## 1\. Configure OPTIC Data Lake certificates
|
||||
|
||||
### Download OPTIC Data Lake certificates
|
||||
|
||||
[https://docs.microfocus.com/doc/SMAX/24.3/IntegrateODL](https://docs.microfocus.com/doc/SMAX/24.3/IntegrateODL)
|
||||
|
||||
Take `https://<OpsbServerName>:30443/` as an example.
|
||||
|
||||
Follow the below steps to get certificates:
|
||||
|
||||
1. Invoke Visit `https://<OpsbServerName>:30443/ browser`, click **Not secure** and **Certificate is not valid**.
|
||||
2. Go to the **Details** tab and select the root certificate, then click **Export**.
|
||||
|
||||
If you want to use ports different from 443, you also need to import different certificates for them. For example, you have the following Administration and Data receiver URLs:
|
||||
|
||||
- https://< `OpsbServerName` >:30004/itom-data-ingestion-administration
|
||||
- https://< `OpsbServerName` >:30001/itom-data-ingestion-receiver
|
||||
|
||||
Follow the below steps to get certificates:
|
||||
|
||||
1. `Invoke https://<OpsbServerName>:30004/`, click **Not secure** and **Certificate is not valid**.
|
||||
2. Go to the **Details** tab and select the root certificate, then click **Export**.
|
||||
3. Visit `https://<OpsbServerName>:30001/`, click **Not secure** and **Certificate is not valid**.
|
||||
4. Go to the **Details** tab and select the root certificate, then click **Export**.
|
||||
|
||||
### Import ODL certificate into SMAX
|
||||
|
||||
Export the crt and copy into /var/vols/itom/itsma/<global-volume>/certificate/source Eg: /var/vols/itom/itsma/config-volume/certificate/source
|
||||
|
||||
On AWS: /efs/var/vols/itom/itsma/config-volume/certificate/source
|
||||
|
||||
## 2\. Restart SMAX pods by running commands on a control plane node or the bastion node:
|
||||
|
||||
Connect to the master node of the SMAX cluster deployed and running.
|
||||
|
||||
1. Run the following commands to restart the SMAX platform pods.
|
||||
```
|
||||
kubectl rollout restart deployment -n itsma-xxxx itom-xruntime-platform
|
||||
kubectl rollout restart deployment -n itsma-xxxx itom-xruntime-platform-offline
|
||||
```
|
||||
|
||||
2\. Run the following command to restart the bo-ats pod.
|
||||
|
||||
```
|
||||
kubectl rollout restart deployment -n itsma-xxxx itom-bo-ats-deployment
|
||||
|
||||
3. Run the following command to restart the ac-vulnerability-patching
|
||||
kubectl rollout restart deployment -n itsma-xxxx itom-ac-vulnerability-and-patching
|
||||
|
||||
[Wait until all the pods are deleted pods are started and running successfully]
|
||||
```
|
||||
|
||||
**Related pages**
|
||||
|
||||
- Page:
|
||||
[ESM Cloud Farm Version Tracking](/display/ICSD/ESM+Cloud+Farm+Version+Tracking)
|
||||
- Page:
|
||||
[How to get an Opentext Confluence account](/display/ICSD/How+to+get+an+Opentext+Confluence+account)
|
||||
- Page:
|
||||
[ITOM APM AppPluse Cloud Farm Information](/display/ICSD/ITOM+APM+AppPluse+Cloud+Farm+Information)
|
||||
- Page:
|
||||
[ITOM Cloud Service Ops Doc Management Process](/display/ICSD/ITOM+Cloud+Service+Ops+Doc+Management+Process)
|
||||
- Page:
|
||||
[ITOM ESM Cloud Service Catalog](/display/ICSD/ITOM+ESM+Cloud+Service+Catalog)
|
||||
- Page:
|
||||
[ITOM OpsB NOM Cloud Service Catalog](/display/ICSD/ITOM+OpsB+NOM+Cloud+Service+Catalog)
|
||||
- Page:
|
||||
[OpsB and NOM Cloud Deployments Version Tracking](/display/ICSD/OpsB+and+NOM+Cloud+Deployments+Version+Tracking)
|
||||
# Enable-Optic-Data-Lake-Preparation_688996348
|
||||
This is wiki helps the R&D team for the preparation of ESM and Operation Platform Integration for a tenant.
|
||||
|
||||
Pre-condition:
|
||||
|
||||
ESM is deployed in a namsapce
|
||||
|
||||
Operation Platfrom is deployed a diferent namepsace
|
||||
|
||||
Automation Center capabilty is enabled for a Tenant
|
||||
|
||||
## 1\. Configure OPTIC Data Lake certificates
|
||||
|
||||
### Download OPTIC Data Lake certificates
|
||||
|
||||
[https://docs.microfocus.com/doc/SMAX/24.3/IntegrateODL](https://docs.microfocus.com/doc/SMAX/24.3/IntegrateODL)
|
||||
|
||||
Take `https://<OpsbServerName>:30443/` as an example.
|
||||
|
||||
Follow the below steps to get certificates:
|
||||
|
||||
1. Invoke Visit `https://<OpsbServerName>:30443/ browser`, click **Not secure** and **Certificate is not valid**.
|
||||
2. Go to the **Details** tab and select the root certificate, then click **Export**.
|
||||
|
||||
If you want to use ports different from 443, you also need to import different certificates for them. For example, you have the following Administration and Data receiver URLs:
|
||||
|
||||
- https://< `OpsbServerName` >:30004/itom-data-ingestion-administration
|
||||
- https://< `OpsbServerName` >:30001/itom-data-ingestion-receiver
|
||||
|
||||
Follow the below steps to get certificates:
|
||||
|
||||
1. `Invoke https://<OpsbServerName>:30004/`, click **Not secure** and **Certificate is not valid**.
|
||||
2. Go to the **Details** tab and select the root certificate, then click **Export**.
|
||||
3. Visit `https://<OpsbServerName>:30001/`, click **Not secure** and **Certificate is not valid**.
|
||||
4. Go to the **Details** tab and select the root certificate, then click **Export**.
|
||||
|
||||
### Import ODL certificate into SMAX
|
||||
|
||||
Export the crt and copy into /var/vols/itom/itsma/<global-volume>/certificate/source Eg: /var/vols/itom/itsma/config-volume/certificate/source
|
||||
|
||||
On AWS: /efs/var/vols/itom/itsma/config-volume/certificate/source
|
||||
|
||||
## 2\. Restart SMAX pods by running commands on a control plane node or the bastion node:
|
||||
|
||||
Connect to the master node of the SMAX cluster deployed and running.
|
||||
|
||||
1. Run the following commands to restart the SMAX platform pods.
|
||||
```
|
||||
kubectl rollout restart deployment -n itsma-xxxx itom-xruntime-platform
|
||||
kubectl rollout restart deployment -n itsma-xxxx itom-xruntime-platform-offline
|
||||
```
|
||||
|
||||
2\. Run the following command to restart the bo-ats pod.
|
||||
|
||||
```
|
||||
kubectl rollout restart deployment -n itsma-xxxx itom-bo-ats-deployment
|
||||
|
||||
3. Run the following command to restart the ac-vulnerability-patching
|
||||
kubectl rollout restart deployment -n itsma-xxxx itom-ac-vulnerability-and-patching
|
||||
|
||||
[Wait until all the pods are deleted pods are started and running successfully]
|
||||
```
|
||||
|
||||
**Related pages**
|
||||
|
||||
- Page:
|
||||
[ESM Cloud Farm Version Tracking](/display/ICSD/ESM+Cloud+Farm+Version+Tracking)
|
||||
- Page:
|
||||
[How to get an Opentext Confluence account](/display/ICSD/How+to+get+an+Opentext+Confluence+account)
|
||||
- Page:
|
||||
[ITOM APM AppPluse Cloud Farm Information](/display/ICSD/ITOM+APM+AppPluse+Cloud+Farm+Information)
|
||||
- Page:
|
||||
[ITOM Cloud Service Ops Doc Management Process](/display/ICSD/ITOM+Cloud+Service+Ops+Doc+Management+Process)
|
||||
- Page:
|
||||
[ITOM ESM Cloud Service Catalog](/display/ICSD/ITOM+ESM+Cloud+Service+Catalog)
|
||||
- Page:
|
||||
[ITOM OpsB NOM Cloud Service Catalog](/display/ICSD/ITOM+OpsB+NOM+Cloud+Service+Catalog)
|
||||
- Page:
|
||||
[OpsB and NOM Cloud Deployments Version Tracking](/display/ICSD/OpsB+and+NOM+Cloud+Deployments+Version+Tracking)
|
||||
|
||||
Reference in New Issue
Block a user