[
https://issues.apache.org/jira/browse/VCL-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13411652#comment-13411652
]
Curtis C. commented on VCL-590:
-------------------------------
Yeah that makes sense. :) I believe the config variables are getting picked up
now with that change to lower case.
Still doing some more testing, specifically around capturing a linux image....
Right now getting this error...seems instance_id is empty so the nova command
is incomplete.
|25586|32:32|image| ---- WARNING ----
|25586|32:32|image| 2012-07-11
11:43:59|25586|32:32|image|vcld:warning_handler(610)|Use of uninitialized value
$instance_id in concatenation (.) or string at
/usr/share/vcl-managementnode/bin/../lib/VCL/Module/Provisioning/openstack.pm
line 251.
|25586|32:32|image| ( 0) vcld, warning_handler (line: 610)
|25586|32:32|image| (-1) openstack.pm, _image_create (line: 251)
|25586|32:32|image| (-2) openstack.pm, capture (line: 217)
|25586|32:32|image| (-3) image.pm, process (line: 162)
|25586|32:32|image| (-4) vcld, make_new_child (line: 568)
|25586|32:32|image| (-5) vcld, main (line: 346)
2012-07-11 11:43:59|25586|32:32|image|openstack.pm:_image_create(252)|New Image
Capture Command: nova image-create centos5image-Server30127-v0-
usage: nova image-create [--poll] <server> <name>
error: too few arguments
Try `nova help image-create' for more information.
> Openstack Essex Module
> ----------------------
>
> Key: VCL-590
> URL: https://issues.apache.org/jira/browse/VCL-590
> Project: VCL
> Issue Type: New Feature
> Components: database, vcld (backend)
> Affects Versions: 2.2.1
> Environment: OpenStack Essex with Ubuntu 12.04 x64 server
> Reporter: Young-Hyun
> Attachments: openstack_euca2ool.pm, openstack_nova_api .pm
>
>
> The OpenStack module supports the VCL provisioning module for OpensStack
> Essex that is open source software for building private and public clouds
> (http://www.openstack.org/)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
