Details
-
Type:
Task
-
Status:
Done
(View Workflow)
-
Priority:
Normal
-
Resolution: Unresolved
-
Labels:
-
Customer:Zain 2.X
-
Reason:Telco/Product Request
-
Severity:Blocker
-
Product:NEP
-
Classification:CR
-
REQUESTER:INTERNAL
Description
As discussed in internal meeting, the way forward is as follows:
Please provide script to extract catalog count types, equipment mode, cabinet types, shelf type, boards types, etc from both KSA & new KW deployment. Then these two sets of data will be compared to determine how many new catalogs need to be created in new KSA deployment.
However, creating the missing catalog manually would be a time-consuming process as number of missing catalogs would be quite a lot. Hence, the recommended option ( if technically possible ) would be to migrate the catalog from Zain KSA itself. If that is not possible then we should attempt to make the missing catalogs through some script or automation rather than creating them manually.
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
- Transitions
- Trace
Have checked few catalogs from the sheet. They are present in the Local 3x platform. next step would be to actually import a validated 3x XML & check for any catalog discrepancies in the NEP error report.
Navneet Kaur this should be done by the telco resource in charge for Zain KSA
Thank you, I will check on this
As discussed with Tarun Sir, please assign resource and ETA for checking
Assigned to Ahad .. This will be fulfilled once the XMLs validations are done for all domains .. tentative date is 21-5-2024
Hi Tarun,
I totally agree with you that whatever can be automated, it will be much better and more efficient. but there are multiple uses:
• for catalog copying from one DB to another DB with same version 3.X, we already have a script used airtel deployment, to copy the physical catalog modelling from different circles, and can be amended to cover other catalog items based on the need.
• for new deployments, we can copy a reference DB, then we can export/import equipment modelling for the missing equipment from other opco, but again it's limited to the physical catalog and need to be amended as per the need.
• with the ongoing refactoring, we will have a separate module for catalog definition, and ideally, we shall have like a unified catalog repository where we consolidated all catalog definitions ...
but all above mentioned cases need some time to be planned and implemented.
now back to our case of zain ksa platform preparation:
• The current zain is 2.x while the new version is 3.x, so not the script already available for Airtel is not applicable.
• we agreed in the last meeting
o to extract the list of catalog items from 2.x and 3.x (a script to be prepared by dev)
o telco to check the missing
o then we will meet again, to discuss what is the best way forwarded to copy the catalog based on the output of comparison.
o as a pre-requisite we need both copy of DB available.