shurkus
commented
4 months ago Any news or need some additional information?
Closed shurkus closed 2 months ago
shurkus
commented
4 months ago Any news or need some additional information?
shurkus
commented
4 months ago An issue has been identified when using the goca library to create a service in OpenNebula. Code has been written to initialize service creation; however, it has been observed that networks, which should be created using reserve_from, are not being created.
Code Sample:
package main
import (
"encoding/json"
"fmt"
"io/ioutil"
"github.com/OpenNebula/one/src/oca/go/src/goca"
)
func main() {
// Get a Flow client
client := goca.NewDefaultFlowClient(
goca.NewFlowConfig("oneadmin", "oneadmin", "http://192.168.1.5:2474"),
)
// Get a Flow controller
controller := goca.NewControllerFlow(client)
// if template id is set, instantiate a Service from this template
tc := controller.STemplate(172)
// Read the content of extra_template.json
extraTemplateContent, err := ioutil.ReadFile("extra_template.json")
if err != nil {
fmt.Println("Error reading extra_template.json:", err)
return
}
// Decode the JSON content into a map[string]interface{}
var data map[string]interface{}
if err := json.Unmarshal(extraTemplateContent, &data); err != nil {
fmt.Println("Error decoding JSON:", err)
return
}
// Print the decoded JSON data for debugging
fmt.Println("Decoded JSON data:", data)
// Instantiate the service using the decoded JSON data
service, err := tc.Instantiate(string(extraTemplateContent))
if err != nil {
fmt.Println("Error instantiating service:", err)
return
}
// Print the instantiated service for debugging
fmt.Println("Instantiated service:", service)
}When running this code, it is expected that networks will be created according to the data passed in extra_template.json. However, it has been observed that networks are not being created, and it is suspected that the issue may be related to the goca library or some deeper level within OpenNebula.
shurkus
commented
4 months ago Understood. The issue lies within OpenNebula. Golang operates with maps that don't maintain order, resulting in JSON output sorted alphabetically. Consequently, a structure like:
"Controlplane": {
"reserve_from": "1",
"extra": "SIZE=3"
}can be reordered to:
"Controlplane": {
"extra": "SIZE=3",
"reserve_from": "1"
}However, OpenNebula has hardcoded logic (e.g., here) that expects specific first keys like 'id', 'template_id', or 'reserve_from', but encounters unexpected ones like 'extra' and consequently skips the processing step, which is incorrect.
A potential solution could look like this:
def deploy_networks(deploy = true)
# Unpack template body if provided as JSON string
template_body = deploy ? JSON.parse(self['TEMPLATE/BODY']) : @body
# Return if no network information found in the template body
return if template_body['networks_values'].nil?
# Process each network in the networks_values list
template_body['networks_values'].each do |network|
network.each do |name, properties|
# Skip iteration if the key is 'id'
next if properties.key?('id')
# Create or reserve the network based on the presence of 'template_id' or 'reserve_from' keys
case
when properties.key?('template_id')
rc = create_vnet(name, properties)
when properties.key?('reserve_from')
rc = reserve(name, properties)
end
# Return error if something went wrong during network creation or reservation
return rc if OpenNebula.is_error?(rc)
# Update the 'id' value in the current network
properties['id'] = rc
end
end if deploy
# Replace variables in the template with corresponding values
resolve_networks(template_body)
# Update the template body
update_body(template_body)
end
However, the hardcoded logic continues in delete_networks and networks functions (maybe somewhere else).
vickmp
commented
4 months ago Hi @shurkus, thank you very much for bringing this problem to our attention! We have been analyzing this case and we think you are absolutely right. As you point out, this bug comes from OpenNebula (specifically from Flow server), so it will be fixed in the next OpenNebula release.
shurkus
commented
4 months ago Apologies for creating the pull request from my other account. Additionally, I would like to bring your attention to packer-plugin-opennebula. Unfortunately, I don't have the time to continue its development, so it would be great if you could consider taking it over and providing further support.
rsmontero
commented
2 months ago
Description
I am facing an issue when trying to create a reserve from a network using Terraform. The network reserve is not even initiated; the corresponding step appears to be skipped entirely. However, when I use the same configuration files with the OpenNebula CLI (oneflow-template instantiate 95 talos-extra_template.json), everything works as expected.
Terraform and Provider version
Terraform v1.6.5 on linux_amd64
Affected resources and data sources
opennebula_service
Terraform configuration
./terraform/service.tf
./templates/service_template.json
Expected behavior
The network reserve should be successfully initiated and created
Actual behavior
The specified network reserve creation step is not being executed. Instead, it appears to be skipped or not processed as intended, resulting in the network reserve not being created successfully.
Steps to Reproduce
Deploy OneFlow service by terraform
oneflow show 116 --jsonNETWORK_ID = \"\" is empty Deploy OneFlow service by
oneflow-template instantiate 95 talos-service.jsonnetwork is 17 and 18 created successfully
Debug output
No response
Panic output
No response
Important factoids
No response
References
No response