[
https://issues.apache.org/jira/browse/VCL-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13419505#comment-13419505
]
Curtis C. commented on VCL-590:
-------------------------------
Ok I think that change is helping.
Couple things:
1) The vclkey should maybe be a variable? I called my openstack keys for this
project "vcl" instead of "vclkey". Had to change it in your module.
2) The IP regex is 192.168... where our networks for openstack are 10.0...that
should maybe be a config variable as well?
Plus I setup two networks for this openstack project, so a describe instance
looks more like this:
| bc870914-38a2-4f5d-a886-633c1d5b6471 | vm-linux2 | BUILD |
novanetwork_4=10.0.4.6; novanetwork_6=10.0.6.6 |
I haven't actually determined if this is required or not, but it could be
something that would present people problems in the future if they have more
than one network, ie. multinic in openstack parlance.
Still testing...
Thanks,
Curtis.
> 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
