OpenROADM / OpenROADM_MSA_Public

Open ROADM MSA
http://www.openroadm.org/
62 stars 79 forks source link

algorithm used in PCE #33

Open vijayanandc159 opened 5 years ago

vijayanandc159 commented 5 years ago

I would like to know what algorithm is recommended for path computation across WDM network in the PCE. Will it be a modified version of dijkstra - with one run to check for constraints at every hop and find shortest path by metric , or the K-th shortest path algorithm to continuously explore many paths and check optical constraints( such as wavelength continuity, ROADM directionality constraint etc) on each of the paths one by one

Please give your suggestions/experience.

orenais commented 5 years ago

There is no real absolute rules. It depends on the case you have to solve. You need an algorithm that can provide a path respecting some constraints. Typically you can use an RWA (Routing and wavelength assignment) algorithm which provides wavelength continuity, or if you have a flexgrid infrastructure an RSA (Routing and Slot Assignment) which provides slots continuity and contiguity. These algos shall support operators’ constraints such as robustness (taking into account SRLG and disjunction), latency (minimum distance), cost (limiting regens at the cost is some cases of a lower rate), spectral occupancy (limiting spectral use and fragmentation)… For the implementation of such algorithms, we usually use k-shortest-paths, but others can be used. As soon as several constraints must be considered, using a simple Dijkstra becomes difficult. GNPY as an example (an OpenSource impairment aware path calculation solution) uses Dijkstra for simple demands, and k-shortest path for more complex demands (include and exclude options) based on Python networkx library.

vijayanandc159 commented 5 years ago

Thanks for your reply. We have constraints like wavelength-continuity constraint, directionality constraint, domain constraint , OTN cross-connect switching constraint ( on which timeslots/ODU containers can be cross-connected to which other timeslots/ODU) . Can you give me a rough idea of what is the typical size of the topology area for which the k-th shortest path algorithm would scale to ( say tens of nodes or hundreds of nodes)? Being an NP-complete problem wherein we have to compute and probe multiple paths before in the topology before selecting one path, would nt it be a big scaling restriction. How many nodes do you think a Path computation element running this algorithm can gracefully handle ?

vijayanandc159 commented 5 years ago

Thanks for your reply. We have constraints like wavelength-continuity constraint, directionality constraint, domain constraint , OTN cross-connect switching constraint ( on which timeslots/ODU containers can be cross-connected to which other timeslots/ODU) . Can you give me a rough idea of what is the typical size of the topology area for which the k-th shortest path algorithm would scale to ( say tens of nodes or hundreds of nodes)? Being an NP-complete problem wherein we have to compute and probe multiple paths before in the topology before selecting one path, would nt it be a big scaling restriction. How many nodes do you think a Path computation element running this algorithm can gracefully handle ?

From: Olivier RENAIS notifications@github.com Sent: Friday, April 26, 2019 1:18 PM To: OpenROADM/OpenROADM_MSA_Public OpenROADM_MSA_Public@noreply.github.com Cc: Vijayanand C - ERS, HCL Tech vijayc@hcl.com; Author author@noreply.github.com Subject: Re: [OpenROADM/OpenROADM_MSA_Public] algorithm used in PCE (#33)

There is no real absolute rules. It depends on the case you have to solve. You need an algorithm that can provide a path respecting some constraints. Typically you can use an RWA (Routing and wavelength assignment) algorithm which provides wavelength continuity, or if you have a flexgrid infrastructure an RSA (Routing and Slot Assignment) which provides slots continuity and contiguity. These algos shall support operators’ constraints such as robustness (taking into account SRLG and disjunction), latency (minimum distance), cost (limiting regens at the cost is some cases of a lower rate), spectral occupancy (limiting spectral use and fragmentation)… For the implementation of such algorithms, we usually use k-shortest-paths, but others can be used. As soon as several constraints must be considered, using a simple Dijkstra becomes difficult. GNPY as an example (an OpenSource impairment aware path calculation solution) uses Dijkstra for simple demands, and k-shortest path for more complex demands (include and exclude options) based on Python networkx library.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOpenROADM%2FOpenROADM_MSA_Public%2Fissues%2F33%23issuecomment-486962123&data=02%7C01%7Cvijayc%40hcl.com%7Cb0d5d2524d994a5ff76808d6ca1b8439%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C636918616877723215&sdata=Cpy%2FiLHUAMhiGL4byun0NfA%2FRAjVbgHt1xKfykQ02o4%3D&reserved=0, or mute the threadhttps://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAL2AY4GQCKM4TJYV4BEC3O3PSKXSPANCNFSM4HFNVSQQ&data=02%7C01%7Cvijayc%40hcl.com%7Cb0d5d2524d994a5ff76808d6ca1b8439%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C636918616877733223&sdata=BLyLya5KPwbIs8NWzEMXF83A%2BJ8JXhKtY4p8Yb2gLrk%3D&reserved=0.

::DISCLAIMER::

The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects.

fgruman commented 5 years ago

Please note that Open ROADM forum does not specify any particular PCE algorithm for use in a controller or PCE. This is left as a choice to the implementer of the PCE.

EstherLerouzic commented 5 years ago

dear @vijayanandc159 As a complement to Olivier's comment, I can answer to your question related to the size of topology I have been using with the GNPy tool: I could run about 300 hundreds requests on a 500 ROADM nodes and 500 links topology, without any issue (it takes a couple of mn). The k-shortest path search was limited to a cut-off value which I put to 120 (meaning 120 hop maximum). The spectrum assignment was first fit.

orenais commented 5 years ago

Merci Esther !

[Logo Orange]http://www.orange.com/

Olivier Renais Optical transport network architect ORANGE/TGI/OLN/WNI/AOT/ATA Fixe : +33 2 96 07 16 40 https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2096%2007%2016%2040 Mobile : +33 6 42 27 71 98 https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2042%2027%2071%2098 olivier.renais@orange.commailto:olivier.renais@orange.com

De : Esther Le Rouzic [mailto:notifications@github.com] Envoyé : mardi 30 avril 2019 18:55 À : OpenROADM/OpenROADM_MSA_Public Cc : RENAIS Olivier TGI/OLN; Comment Objet : Re: [OpenROADM/OpenROADM_MSA_Public] algorithm used in PCE (#33)

dear @vijayanandc159https://github.com/vijayanandc159 As a complement to Olivier's comment, I can answer to your question related to the size of topology I have been using with the GNPy tool: I could run about 300 hundreds requests on a 500 ROADM nodes and 500 links topology, without any issue (it takes a couple of mn). The k-shortest path search was limited to a cut-off value which I put to 120 (meaning 120 hop maximum). The spectrum assignment was first fit.

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/OpenROADM/OpenROADM_MSA_Public/issues/33#issuecomment-488030250, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFPLFL6TZ5U3MSOZITXDPDDPTB2VDANCNFSM4HFNVSQQ.


Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

vijayanandc159 commented 5 years ago

Thanks a lot for the reply esther. What was the hardware capability of your computation server ? I have a further question here. When you compute path across OTN links, I assume the ODU multiplexing capability of the OTN ports will be specified/fixed/configured before the path calculation happens, or do you support/intend to support cases where the algorithms itself can dynamically choose the ODU multiplexing capability of the port if the port has multiple capabilities possible.

Regards Vijay

From: Esther Le Rouzic notifications@github.com Sent: Tuesday, April 30, 2019 10:25 PM To: OpenROADM/OpenROADM_MSA_Public OpenROADM_MSA_Public@noreply.github.com Cc: Vijayanand C - ERS, HCL Tech vijayc@hcl.com; Mention mention@noreply.github.com Subject: Re: [OpenROADM/OpenROADM_MSA_Public] algorithm used in PCE (#33)

dear @vijayanandc159https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fvijayanandc159&data=02%7C01%7Cvijayc%40hcl.com%7C88a696f27dce4bec1ffc08d6cd8c8bb1%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C636922400867185748&sdata=LGGXVTC3oH%2FqBy00TaKobHdo8UNSrbyQB6PsW8rjSs8%3D&reserved=0 As a complement to Olivier's comment, I can answer to your question related to the size of topology I have been using with the GNPy tool: I could run about 300 hundreds requests on a 500 ROADM nodes and 500 links topology, without any issue (it takes a couple of mn). The k-shortest path search was limited to a cut-off value which I put to 120 (meaning 120 hop maximum). The spectrum assignment was first fit.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOpenROADM%2FOpenROADM_MSA_Public%2Fissues%2F33%23issuecomment-488030250&data=02%7C01%7Cvijayc%40hcl.com%7C88a696f27dce4bec1ffc08d6cd8c8bb1%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C636922400867195757&sdata=MpOIAOYZ%2BdRUeTiRc92iXktogylhgiprMU3TBSTvIb8%3D&reserved=0, or mute the threadhttps://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAL2AY4FD7V6ZI6I67UC4AQLPTB2VDANCNFSM4HFNVSQQ&data=02%7C01%7Cvijayc%40hcl.com%7C88a696f27dce4bec1ffc08d6cd8c8bb1%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C636922400867195757&sdata=wJMxdvdJy%2BtUPCr2z8rj3nxpvBlptqoKh%2BKUSnv%2BVgo%3D&reserved=0.

::DISCLAIMER::

The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects.

vijayanandc159 commented 5 years ago

Hi oliver, I along with some of my colleagues, would like to join the tutorials on 22nd May on transport PCE in OPENROADM. I susbscribed to the user group, but I did not receive any invite or procedure for joining this. Please let us know how we can join this

Vijay

From: Olivier RENAIS notifications@github.com Sent: Thursday, May 2, 2019 12:30 PM To: OpenROADM/OpenROADM_MSA_Public OpenROADM_MSA_Public@noreply.github.com Cc: Vijayanand C - ERS, HCL Tech vijayc@hcl.com; Mention mention@noreply.github.com Subject: Re: [OpenROADM/OpenROADM_MSA_Public] algorithm used in PCE (#33)

Merci Esther !

[Logo Orange]http://www.orange.com/

Olivier Renais Optical transport network architect ORANGE/TGI/OLN/WNI/AOT/ATA Fixe : +33 2 96 07 16 40 https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2096%2007%2016%2040 Mobile : +33 6 42 27 71 98 https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2042%2027%2071%2098 olivier.renais@orange.commailto:olivier.renais@orange.com<mailto:olivier.renais@orange.com%3cmailto:olivier.renais@orange.com>

De : Esther Le Rouzic [mailto:notifications@github.com] Envoyé : mardi 30 avril 2019 18:55 À : OpenROADM/OpenROADM_MSA_Public Cc : RENAIS Olivier TGI/OLN; Comment Objet : Re: [OpenROADM/OpenROADM_MSA_Public] algorithm used in PCE (#33)

dear @vijayanandc159https://github.com/vijayanandc159 As a complement to Olivier's comment, I can answer to your question related to the size of topology I have been using with the GNPy tool: I could run about 300 hundreds requests on a 500 ROADM nodes and 500 links topology, without any issue (it takes a couple of mn). The k-shortest path search was limited to a cut-off value which I put to 120 (meaning 120 hop maximum). The spectrum assignment was first fit.

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/OpenROADM/OpenROADM_MSA_Public/issues/33#issuecomment-488030250, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFPLFL6TZ5U3MSOZITXDPDDPTB2VDANCNFSM4HFNVSQQ.


Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOpenROADM%2FOpenROADM_MSA_Public%2Fissues%2F33%23issuecomment-488570792&data=02%7C01%7Cvijayc%40hcl.com%7C7f5e58b516c5468fc1fb08d6cecbde59%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C636923772339939044&sdata=bilovoPX5YO9VE%2BarSP%2FQlMyuHG9GHCL9Q%2FOLbUUFo4%3D&reserved=0, or mute the threadhttps://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAL2AY4AQFWMBXWXUW6EUJZDPTKGQ3ANCNFSM4HFNVSQQ&data=02%7C01%7Cvijayc%40hcl.com%7C7f5e58b516c5468fc1fb08d6cecbde59%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C636923772339949052&sdata=Xb5K25BkzR%2B%2FKtmDkMhL%2BYIUVUcLSFRPc2LkguZFZBU%3D&reserved=0.

::DISCLAIMER::

The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects.

vijayanandc159 commented 4 years ago

Hi, Just need an info. Does the current Openroadm have support for path computation for ODU trails and Heirarchical ODU trails.

Regards, Vijay

From: Olivier RENAIS notifications@github.com Sent: Thursday, May 2, 2019 12:30 PM To: OpenROADM/OpenROADM_MSA_Public OpenROADM_MSA_Public@noreply.github.com Cc: Vijayanand C - ERS, HCL Tech vijayc@hcl.com; Mention mention@noreply.github.com Subject: Re: [OpenROADM/OpenROADM_MSA_Public] algorithm used in PCE (#33)

Merci Esther !

[Logo Orange]http://www.orange.com/

Olivier Renais Optical transport network architect ORANGE/TGI/OLN/WNI/AOT/ATA Fixe : +33 2 96 07 16 40 https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%202%2096%2007%2016%2040 Mobile : +33 6 42 27 71 98 https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2042%2027%2071%2098 olivier.renais@orange.commailto:olivier.renais@orange.com<mailto:olivier.renais@orange.com%3cmailto:olivier.renais@orange.com>

De : Esther Le Rouzic [mailto:notifications@github.com] Envoyé : mardi 30 avril 2019 18:55 À : OpenROADM/OpenROADM_MSA_Public Cc : RENAIS Olivier TGI/OLN; Comment Objet : Re: [OpenROADM/OpenROADM_MSA_Public] algorithm used in PCE (#33)

dear @vijayanandc159https://github.com/vijayanandc159 As a complement to Olivier's comment, I can answer to your question related to the size of topology I have been using with the GNPy tool: I could run about 300 hundreds requests on a 500 ROADM nodes and 500 links topology, without any issue (it takes a couple of mn). The k-shortest path search was limited to a cut-off value which I put to 120 (meaning 120 hop maximum). The spectrum assignment was first fit.

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/OpenROADM/OpenROADM_MSA_Public/issues/33#issuecomment-488030250, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFPLFL6TZ5U3MSOZITXDPDDPTB2VDANCNFSM4HFNVSQQ.


Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOpenROADM%2FOpenROADM_MSA_Public%2Fissues%2F33%23issuecomment-488570792&data=02%7C01%7Cvijayc%40hcl.com%7C7f5e58b516c5468fc1fb08d6cecbde59%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C636923772339939044&sdata=bilovoPX5YO9VE%2BarSP%2FQlMyuHG9GHCL9Q%2FOLbUUFo4%3D&reserved=0, or mute the threadhttps://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAL2AY4AQFWMBXWXUW6EUJZDPTKGQ3ANCNFSM4HFNVSQQ&data=02%7C01%7Cvijayc%40hcl.com%7C7f5e58b516c5468fc1fb08d6cecbde59%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C636923772339949052&sdata=Xb5K25BkzR%2B%2FKtmDkMhL%2BYIUVUcLSFRPc2LkguZFZBU%3D&reserved=0.

::DISCLAIMER::


The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects.


orenais commented 4 years ago

Hi, Yes OpenROADM supports it. For what concerns TransportPCE, it's on its way, but we need to debug it. (Code not merged at that time on Gerrit) Regards

vijayanandc159 commented 4 years ago

Thanks for the reply oliver , a few more queries.

1) There are few OTN cards where there is cross-connect constraint, regarding which Timeslots/ODU containers can be cross connected to which other timeslots/ODU containers in other ports. Can such constraints be supported ?

2) The model seems to support OSPF routing. So this can be integrated with GMPLS routing and signaling stack as well as be used as a centralized SDN PCE controller ?

3) Is support for higher rate ODU signals like ODUc2, c3 etc… also available.

Vijay From: Olivier RENAIS notifications@github.com Sent: Friday, December 13, 2019 3:33 PM To: OpenROADM/OpenROADM_MSA_Public OpenROADM_MSA_Public@noreply.github.com Cc: Vijayanand C - ERS, HCL Tech vijayc@hcl.com; Mention mention@noreply.github.com Subject: Re: [OpenROADM/OpenROADM_MSA_Public] algorithm used in PCE (#33)

Hi, Yes OpenROADM supports it. For what concerns TransportPCE, it's on its way, but we need to debug it. (Code not merged at that time on Gerrit) Regards

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOpenROADM%2FOpenROADM_MSA_Public%2Fissues%2F33%3Femail_source%3Dnotifications%26email_token%3DAL2AY4DTH5FSSE2PFQQQ4PDQYNMUPA5CNFSM4HFNVSQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGZQHPQ%23issuecomment-565380030&data=02%7C01%7Cvijayc%40hcl.com%7Cb48a174f855c487b163908d77fb39c3c%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C1%7C637118281735458396&sdata=l57oacVH2yBFh66FL20RBYHmT3ujjIUOmyP4a%2BsY5kE%3D&reserved=0, or unsubscribehttps://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAL2AY4DKPVXJGJRCLJNFCTTQYNMUPANCNFSM4HFNVSQQ&data=02%7C01%7Cvijayc%40hcl.com%7Cb48a174f855c487b163908d77fb39c3c%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C1%7C637118281735458396&sdata=MTNTqSsHf6zGEOKj%2FpgfWP5G%2BsqUEhtJeTWrFIeEJ2U%3D&reserved=0.

::DISCLAIMER::


The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects.


orenais commented 4 years ago

Hi Vijay, Sorry I skipped your mail and forgot answering. Just saw it this morning. Transport PCE current implementation is based on OpenROADM. We are currently debugging first version of our PCE for OTN. OR topology model includes for termination points that terminates ODU some odtu-tpn-pool that provide information on available trib-port and trib-slots. Then we also have in the model switching pools that provides information on port connectivity, and available bandwidth. To my knowledge,, we don't have a way to model potential restrictions on trib-slot to trib slot connections in XC. The models support OSPF, but at that time we considered we have a centralized control plane, and did not put effort on modelling a distributed control-plane based on GMPLS. This does not mean it can't be supported, but this out of the scope of OR. ODUCn is supported in the model, but I am not a specialist about it, and don't know if we have full support for any kind of interface. Would suggest to look at latest model to see if you find anything you need. Regards