HELM parser

Asked by Abhinav Mishra on 2020-10-14

I need help with writing a helm parser for cloud native microservices based on kubernetes. I have gone through the repo of tacker with TOSCA parser. Could you help me out with similar set of instructions for parsing helm charts ?

Question information

English Edit question
Needs information
tacker Edit question
No assignee Edit question
Last query:
Last reply:
Yoshito Ito (ito.yoshito) said : #1

Thank you for the question. In short, Tacker repo doesn't have "helm parser" so far, and is not ready to implement it. Let me ask some questions to clarify what we can help you.

1. What does the "helm parser" generate objects from?
  - My assumption: Helm chart files

2. How to define the data structure?
  - For TOSCA, we have specifications, but not for Helm (might be in the official doc?).

3. What information from Tacker can help you?

Abhinav Mishra (abhiranjeet15) said : #2

Thank You for your response. I understand that there may not be a "helm parser" in Tacker. However, since Tacker supports both OpenStack & Kubernetes VIM, is it still accepting TOSCA-based templates for deploying microservices ?

Abhinav Mishra (abhiranjeet15) said : #3

Also, what I need from Tacker is method or any kind of demonstration of how they wrote the parser (for TOSCA)

Yoshito Ito (ito.yoshito) said : #4

TOSCA definitions for OS container based VNF is not yet defined in ETSI NFV-SOL specifications and it's under discussion. Therefore, we now support Kubernetes resource files [1] in VNF Package as artifacts (please refer the example of [2] and the Spec [3]) other than translating from TOSCA templates. How to create VNF Package is described in ETSI NFV-SOL004 [4] and the Tacker doc [5] may help you to understand what the VNF Package is. The supported description for OS containers is defined as Managed Container Infrastructure Object Package (MCIOP) in ETSI NFV-IFA011 [6]. MCIOP can be "Kubernetes resource files" or "Helm chart". I think we may extend the support for "Helm chart" in future.

Now we are preparing a document to explain how to use our Kubernetes VIM support with ETSI NFV specifications. It will be published soon.

[1] https://kubernetes.io/docs/concepts/cluster-administration/manage-deployment/
[2] https://github.com/openstack/tacker/tree/master/tacker/tests/etc/samples/etsi/nfv/test_create_vnf_instance_and_instantiate_and_terminate_cnf_resources
[3] https://specs.openstack.org/openstack/tacker-specs/specs/victoria/container-network-function.html
[4] https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/004/02.06.01_60/gs_NFV-SOL004v020601p.pdf
[5] https://docs.openstack.org/tacker/latest/user/vnf-package.html
[6] https://www.etsi.org/deliver/etsi_gr/NFV-IFA/001_099/029/03.03.01_60/gr_NFV-IFA029v030301p.pdf

Can you help with this problem?

Provide an answer of your own, or ask Abhinav Mishra for more information if necessary.

To post a message you must log in.