Bug 784978 - aeolus-configure is not properly settting the /etc/imagefactory/$provider.json file
Summary: aeolus-configure is not properly settting the /etc/imagefactory/$provider.jso...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-configure
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: alpha
Assignee: John Eckersberg
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-26 20:03 UTC by wes hayutin
Modified: 2012-08-30 17:12 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-30 17:12:21 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description wes hayutin 2012-01-26 20:03:38 UTC 
Description of problem:

recreated w/ rhevm, vsphere

[root@qeblade31 ~]# cat /etc/imagefactory/vsphere.json
{
  "default":
  {
    "api-url":   "https://10.16.120.224/sdk",
    "username":  "Administrator",
    "password":     "R3dhat!",
    "datastore":    "datastore1",
    "network_name": "VM Network"
  }
}


default should = the name of the created provider


oot@qeblade31 ~]# rpm -qa | grep aeolus
aeolus-all-0.8.0-12.el6.noarch
aeolus-conductor-0.8.0-12.el6.noarch
aeolus-conductor-doc-0.8.0-12.el6.noarch
aeolus-conductor-daemons-0.8.0-12.el6.noarch
rubygem-aeolus-cli-0.3.0-5.el6.noarch
rubygem-aeolus-image-0.3.0-4.el6.noarch
aeolus-configure-2.5.0-8.el6.noarch
Comment 1 Dave Johnson 2012-01-26 21:14:15 UTC 
Same for rhevm...the following results in a provider named... rhevm-rhevm-blade27

From /etc/aeolus-configure/nodes/rhevm_configure
<snip>
  aeolus::profiles::rhevm:
    instances:
      rhevm-blade27:
        nfs_server: nfs.server.com
        nfs_export: /home/blade27_export
        nfs_mount_point: /mnt/rhevm-nfs
        deltacloud_username: admin@internal
        deltacloud_password: dog8code
        deltacloud_api: https://rhevm.server.com:8443/api
        deltacloud_data_center: 4051216f-a778-488f-8ae4-5a2541b009ff
        push_timeout: 1800
</snip>
 
creating a rhevm.json provider entry like so (which does not match the provider name):

  "rhevm-blade27":
  {
    "username": "admin@internal",
Comment 2 John Eckersberg 2012-01-26 23:01:56 UTC 
Patch posted
Comment 3 John Eckersberg 2012-01-27 17:36:58 UTC 
Pushed as 9ccb4f0943ba1829db6dac28ba5cde46e82f88bd
Comment 4 Steve Linabery 2012-01-31 22:11:31 UTC 
9ccb4f0 in aeolus-configure-2.5.0-11
Comment 5 Aziza Karol 2012-02-06 05:57:22 UTC 
aeolus-configure sets the /etc/imagefactory/$provider.json file correctly.
The name of the created provider is set.


#cat /etc/imagefactory/vsphere.json
{
  "vsphere-default":
  {
    "api-url":   "https://10.16.120.136/sdk",
    "username":  "Administrator",
    "password":     "R3dhat!",
    "datastore":    "datastore1",
    "network_name": "VM Network"
  }
}


# cat /etc/imagefactory/rhevm.json
{
  "rhevm-default":
  {
    "username": "admin@internal",
    "nfs-dir": "/mnt/rhevm-nfs",
    "nfs-path": "/home/blade27_export",
    "nfs-host": "qeblade26.rhq.lab.eng.bos.redhat.com",
    "api-url": "https://qeblade26.rhq.lab.eng.bos.redhat.com:8443/api",
    "password": "dog8code",
    "cluster": "_any_",
    "timeout": 1800
  }

rpm -qa | grep aeolus
rubygem-aeolus-image-0.3.0-7.el6.noarch
aeolus-conductor-daemons-0.8.0-20.el6.noarch
aeolus-configure-2.5.0-11.el6.noarch
aeolus-conductor-doc-0.8.0-20.el6.noarch
aeolus-all-0.8.0-20.el6.noarch
rubygem-aeolus-cli-0.3.0-7.el6.noarch
aeolus-conductor-0.8.0-20.el6.noarch
Note You need to log in before you can comment on or make changes to this bug.