TM Forum Community

Dear All,

Actually, my company has defined plans to verticalized the service chain and explore new business markets focused on a cloud. As we know, the cloudification process comes together with virtualization. At this moment great part of IT and VAS platforms are settled in a virtualized IaaS (EMC - Storage, HP/Cisco - x86 servers, VMWare Hypervisor).  Our IaaS is working with Cisco Nexus L2/L3 without SDN and interact with legacy backbone with MPLS. The key point of the migration process from Mobile Core PNF to VNF is:

1- Hybrid network or total migration?
2- The process of migration from traditional virtualization to NFV is simple, or is preferred to migrate directly to the NFV?
3- Which nodes are recommended migrate first, considering CS/PS/IMS core?
4- Which routing protocol is recommended between datacenter and legacy network? 
5- Is it convenient to deploy an independent and dedicated IaaS for Telecom VNF or doesn't matter works with IT VNF?

Thanks in advance. For further inquiries, feel free in contact me as soon as you wish.

Warm Regards,
Marton Dantas

------------------------------
marton dantas
UNITEL S.A.
------------------------------

Dear Marton,
Some of the answers to you question.

1. Total migration is way to go. Hybrid would be the case till the time you have some nodes/vendor products that cannot be moved onto VNF (e.g. TDM network connections etc).. Check internally.
2. The process of migration is "practically" complicated and it becomes more in case you have multi-vendor environment as each vendor may have their MANO architecture (hope you heard about VNF onboarding concerns in multi-vendor scenarios). Normally, from PNF (Physical) to VNF, there's generally software change as well and hence you might need to run regression testing for critical services. Technically speaking, it is not migration , but fresh installation. Get a good architect who studies your network and defines right strategy to make it smooth.
3. Would recommend to migrate PS first (as it is generally simpler) then CS or IMS. Moreover, if you already have IMS and not too old, it should already be on virtualized infrastructure (that's general trend, did you checked that?).
4. 
5. Recommend to create Telecom VNF separated from IT VNF due for security and administrative reasons. You may have common infra supplier for both though.

------------------------------
Abhisek Kumar
Nokia
------------------------------

Original Message:
Sent: Oct 11, 2018 06:38
From: marton dantas
Subject: Key Points of Virtualization I

Dear All,

Actually, my company has defined plans to verticalized the service chain and explore new business markets focused on a cloud. As we know, the cloudification process comes together with virtualization. At this moment great part of IT and VAS platforms are settled in a virtualized IaaS (EMC - Storage, HP/Cisco - x86 servers, VMWare Hypervisor).  Our IaaS is working with Cisco Nexus L2/L3 without SDN and interact with legacy backbone with MPLS. The key point of the migration process from Mobile Core PNF to VNF is:

1- Hybrid network or total migration?
2- The process of migration from traditional virtualization to NFV is simple, or is preferred to migrate directly to the NFV?
3- Which nodes are recommended migrate first, considering CS/PS/IMS core?
4- Which routing protocol is recommended between datacenter and legacy network?
5- Is it convenient to deploy an independent and dedicated IaaS for Telecom VNF or doesn't matter works with IT VNF?

Thanks in advance. For further inquiries, feel free in contact me as soon as you wish.

Warm Regards,
Marton Dantas

------------------------------
marton dantas
UNITEL S.A.
------------------------------

The working  assumption in the ZOOM project work was  the need to support a hybrid operations model for PNF and VNF but with a clear transformation end-point of Virtualised and intent based managemen . The ZOOM work is now in the ODA Service and resource management workstream ( and the lifecycle aspects are in the ODA OLM workstream).

The general approach proposed is to create management platforms that support hybrid working (supporting both detailed /declarative and intent based management) .
This approach is  documented in:
TR262 Management Platform Blueprint and Application to Hybrid Infrastructure R17.5.1  ( previously called Hybrid Infrastructure management 
Deployment examples were documented in 
TMF070 Hybrid Environment Implementation Blueprints Suite R17.5.1

A catalysts  Real Virtuality – Phase II was used to validate some of these concepts and developed a API 
TMF664 Resource Function Activation and Configuration API REST Specification R17.5.1
which supports hybrid operations.
This was extended with additional implementation focussed guides in 
TR255 Resource Function Activation and Configuration Suite R17.5.0   notably 
TR255A Connectivity Patterns for Virtualization Management R17.5.1
TR255B Specification Requirements for Resource Functions R17.5.1

Note all of this is about management the PNF and VNF functionality which is different from ETSI NFV which focused  solely on  the management of the virtualisation aspects:  i.e. lifecycle of NS/VNF ( software images) and their instantiation on Openstack ).

This is why the other commenter mentioned keeping VNF and IT virtualisation separate.
Note in ETSI the Element management (EM) interfaces are out of scope
However EM functionality has been the primary  focus of the ZOOM now ODA work -see IG1161 Overview: Agile Intent-based Resource Management in Hybrid Environments R17.5.1  for more more detail on relationship between ZOOM ODA work and ETSI NFV .
Hope this helps.

------------------------------
Dave Milham
TM Forum Chief Architect, TM Forum
------------------------------

Original Message:
Sent: Oct 12, 2018 03:02
From: Abhisek Kumar
Subject: Key Points of Virtualization I

Dear Marton,
Some of the answers to you question.

1. Total migration is way to go. Hybrid would be the case till the time you have some nodes/vendor products that cannot be moved onto VNF (e.g. TDM network connections etc).. Check internally.
2. The process of migration is "practically" complicated and it becomes more in case you have multi-vendor environment as each vendor may have their MANO architecture (hope you heard about VNF onboarding concerns in multi-vendor scenarios). Normally, from PNF (Physical) to VNF, there's generally software change as well and hence you might need to run regression testing for critical services. Technically speaking, it is not migration , but fresh installation. Get a good architect who studies your network and defines right strategy to make it smooth.
3. Would recommend to migrate PS first (as it is generally simpler) then CS or IMS. Moreover, if you already have IMS and not too old, it should already be on virtualized infrastructure (that's general trend, did you checked that?).
4.
5. Recommend to create Telecom VNF separated from IT VNF due for security and administrative reasons. You may have common infra supplier for both though.

------------------------------
Abhisek Kumar
Nokia

Original Message:
Sent: Oct 11, 2018 06:38
From: marton dantas
Subject: Key Points of Virtualization I

Dear All,

Actually, my company has defined plans to verticalized the service chain and explore new business markets focused on a cloud. As we know, the cloudification process comes together with virtualization. At this moment great part of IT and VAS platforms are settled in a virtualized IaaS (EMC - Storage, HP/Cisco - x86 servers, VMWare Hypervisor).  Our IaaS is working with Cisco Nexus L2/L3 without SDN and interact with legacy backbone with MPLS. The key point of the migration process from Mobile Core PNF to VNF is:

1- Hybrid network or total migration?
2- The process of migration from traditional virtualization to NFV is simple, or is preferred to migrate directly to the NFV?
3- Which nodes are recommended migrate first, considering CS/PS/IMS core?
4- Which routing protocol is recommended between datacenter and legacy network?
5- Is it convenient to deploy an independent and dedicated IaaS for Telecom VNF or doesn't matter works with IT VNF?

Thanks in advance. For further inquiries, feel free in contact me as soon as you wish.

Warm Regards,
Marton Dantas

------------------------------
marton dantas
UNITEL S.A.
------------------------------

Dear Dave,

Much appreciate for your comments, but unfortunately, I am unavailable to have a look at the documents sent by you. I do appreciate if you could share any documents which reflect your concerns.

Warm regards,


------------------------------
marton dantas
UNITEL S.A.
------------------------------

Original Message:
Sent: Oct 12, 2018 06:49
From: Dave Milham
Subject: Key Points of Virtualization I

The working  assumption in the ZOOM project work was  the need to support a hybrid operations model for PNF and VNF but with a clear transformation end-point of Virtualised and intent based managemen . The ZOOM work is now in the ODA Service and resource management workstream ( and the lifecycle aspects are in the ODA OLM workstream).

The general approach proposed is to create management platforms that support hybrid working (supporting both detailed /declarative and intent based management) .
This approach is  documented in:
TR262 Management Platform Blueprint and Application to Hybrid Infrastructure R17.5.1  ( previously called Hybrid Infrastructure management
Deployment examples were documented in
TMF070 Hybrid Environment Implementation Blueprints Suite R17.5.1

A catalysts  Real Virtuality – Phase II was used to validate some of these concepts and developed a API
TMF664 Resource Function Activation and Configuration API REST Specification R17.5.1
which supports hybrid operations.
This was extended with additional implementation focussed guides in
TR255 Resource Function Activation and Configuration Suite R17.5.0   notably
TR255A Connectivity Patterns for Virtualization Management R17.5.1
TR255B Specification Requirements for Resource Functions R17.5.1

Note all of this is about management the PNF and VNF functionality which is different from ETSI NFV which focused  solely on  the management of the virtualisation aspects:  i.e. lifecycle of NS/VNF ( software images) and their instantiation on Openstack ).

This is why the other commenter mentioned keeping VNF and IT virtualisation separate.
Note in ETSI the Element management (EM) interfaces are out of scope
However EM functionality has been the primary  focus of the ZOOM now ODA work -see IG1161 Overview: Agile Intent-based Resource Management in Hybrid Environments R17.5.1  for more more detail on relationship between ZOOM ODA work and ETSI NFV .
Hope this helps.

------------------------------
Dave Milham
TM Forum Chief Architect, TM Forum

Original Message:
Sent: Oct 12, 2018 03:02
From: Abhisek Kumar
Subject: Key Points of Virtualization I

Dear Marton,
Some of the answers to you question.

1. Total migration is way to go. Hybrid would be the case till the time you have some nodes/vendor products that cannot be moved onto VNF (e.g. TDM network connections etc).. Check internally.
2. The process of migration is "practically" complicated and it becomes more in case you have multi-vendor environment as each vendor may have their MANO architecture (hope you heard about VNF onboarding concerns in multi-vendor scenarios). Normally, from PNF (Physical) to VNF, there's generally software change as well and hence you might need to run regression testing for critical services. Technically speaking, it is not migration , but fresh installation. Get a good architect who studies your network and defines right strategy to make it smooth.
3. Would recommend to migrate PS first (as it is generally simpler) then CS or IMS. Moreover, if you already have IMS and not too old, it should already be on virtualized infrastructure (that's general trend, did you checked that?).
4.
5. Recommend to create Telecom VNF separated from IT VNF due for security and administrative reasons. You may have common infra supplier for both though.

------------------------------
Abhisek Kumar
Nokia

Original Message:
Sent: Oct 11, 2018 06:38
From: marton dantas
Subject: Key Points of Virtualization I

Dear All,

Actually, my company has defined plans to verticalized the service chain and explore new business markets focused on a cloud. As we know, the cloudification process comes together with virtualization. At this moment great part of IT and VAS platforms are settled in a virtualized IaaS (EMC - Storage, HP/Cisco - x86 servers, VMWare Hypervisor).  Our IaaS is working with Cisco Nexus L2/L3 without SDN and interact with legacy backbone with MPLS. The key point of the migration process from Mobile Core PNF to VNF is:

1- Hybrid network or total migration?
2- The process of migration from traditional virtualization to NFV is simple, or is preferred to migrate directly to the NFV?
3- Which nodes are recommended migrate first, considering CS/PS/IMS core?
4- Which routing protocol is recommended between datacenter and legacy network?
5- Is it convenient to deploy an independent and dedicated IaaS for Telecom VNF or doesn't matter works with IT VNF?

Thanks in advance. For further inquiries, feel free in contact me as soon as you wish.

Warm Regards,
Marton Dantas

------------------------------
marton dantas
UNITEL S.A.
------------------------------

Dear <g class="gr_ gr_24 gr-alert gr_spell gr_inline_cards gr_disable_anim_appear ContextualSpelling ins-del multiReplace" id="24" data-gr-id="24">Abhisek</g>,

I'd like to thank you for your comments. More specifically to item 2, then is preferred to migrate directly to the NFV? Actually, my company is pushing to deploy the new nodes at traditional virtualization (only physical abstraction) and maybe in a couple of years migrate one more time to the NFV. Personally, I have some doubts about that strategy. 

By the way, thanks so much for your support.

All the best,


------------------------------
marton dantas
UNITEL S.A.
------------------------------

Original Message:
Sent: Oct 12, 2018 03:02
From: Abhisek Kumar
Subject: Key Points of Virtualization I

Dear Marton,
Some of the answers to you question.

1. Total migration is way to go. Hybrid would be the case till the time you have some nodes/vendor products that cannot be moved onto VNF (e.g. TDM network connections etc).. Check internally.
2. The process of migration is "practically" complicated and it becomes more in case you have multi-vendor environment as each vendor may have their MANO architecture (hope you heard about VNF onboarding concerns in multi-vendor scenarios). Normally, from PNF (Physical) to VNF, there's generally software change as well and hence you might need to run regression testing for critical services. Technically speaking, it is not migration , but fresh installation. Get a good architect who studies your network and defines right strategy to make it smooth.
3. Would recommend to migrate PS first (as it is generally simpler) then CS or IMS. Moreover, if you already have IMS and not too old, it should already be on virtualized infrastructure (that's general trend, did you checked that?).
4.
5. Recommend to create Telecom VNF separated from IT VNF due for security and administrative reasons. You may have common infra supplier for both though.

------------------------------
Abhisek Kumar
Nokia

Original Message:
Sent: Oct 11, 2018 06:38
From: marton dantas
Subject: Key Points of Virtualization I

Dear All,

Actually, my company has defined plans to verticalized the service chain and explore new business markets focused on a cloud. As we know, the cloudification process comes together with virtualization. At this moment great part of IT and VAS platforms are settled in a virtualized IaaS (EMC - Storage, HP/Cisco - x86 servers, VMWare Hypervisor).  Our IaaS is working with Cisco Nexus L2/L3 without SDN and interact with legacy backbone with MPLS. The key point of the migration process from Mobile Core PNF to VNF is:

1- Hybrid network or total migration?
2- The process of migration from traditional virtualization to NFV is simple, or is preferred to migrate directly to the NFV?
3- Which nodes are recommended migrate first, considering CS/PS/IMS core?
4- Which routing protocol is recommended between datacenter and legacy network?
5- Is it convenient to deploy an independent and dedicated IaaS for Telecom VNF or doesn't matter works with IT VNF?

Thanks in advance. For further inquiries, feel free in contact me as soon as you wish.

Warm Regards,
Marton Dantas

------------------------------
marton dantas
UNITEL S.A.
------------------------------