Bug #214

OCCI: post_network

Added by Gyula Csom almost 10 years ago. Updated almost 10 years ago.

Status:ClosedStart date:04/19/2010
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:Release 1.4.2
Resolution:fixed Pull request:
Affected Versions:

Description

Hi there,
when testing the OCCI interface I've met the following problem. The OCCI
post_network method seems to use a buggy xml schema within the 1.4 distrib.
Details:

Documentation

The OCCI user guide gives the following example for creating a network:

<NETWORK>
    <NAME>MyServiceNetwork</NAME>
    <ADDRESS>192.168.1.1</ADDRESS>
    <SIZE>200</SIZE>
</NETWORK>
$ ./occi-network --url http://localhost:4567 --username oneadmin --password opennebula create vnxml 

From the example above it's clear that the network settings must be put
under a top level NETWORK element.

Codebase

The example above fits the OCCIServer.rb code, eg.:

221:            network_info=Crack::XML.parse(request.body.read)
...
234:            vntemplate = network.to_one_template(
235:                          network_info['NETWORK'],
236:                          @config[:bridge])

Distribution

However the ONE v.1.4 distribution available for download contains
a different code, and uses a different schema:

222:            network_info=Crack::XML.parse(request.body.read)
...
235:            vntemplate = network.to_one_template(
236:                          network_info['NIC'],
237:                          @config[:bridge])

Thus the distrib uses another schema, where network settings
should be put under a top level NIC element.

Cheers,
Gyula

Associated revisions

Revision 4018be72
Added by Javi Fontan almost 3 years ago

Do not set VNC ports as used in certain states #214

Original fix by @dfelsch

History

#1 Updated by Ruben S. Montero almost 10 years ago

  • Category set to 11
  • Status changed from New to Closed
  • Target version set to Release 1.4.2
  • Resolution set to fixed

Hi

This is right OpenNebula 1.4 has a wrong XML schema for the networks, this has been fixed for the next release as you noted.

Also available in: Atom PDF