Bug 869298 - Remove the extra space between the launch-time parameters fields
Remove the extra space between the launch-time parameters fields
Status: NEW
Product: CloudForms Cloud Engine
Classification: Red Hat
Component: aeolus-conductor (Show other bugs)
1.1.0
Unspecified Unspecified
unspecified Severity low
: rc
: ---
Assigned To: Angus Thomas
Rehana
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-10-23 10:10 EDT by Rehana
Modified: 2012-10-30 10:11 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
space (58.78 KB, image/png)
2012-10-23 10:10 EDT, Rehana
no flags Details

  None (edit)
Description Rehana 2012-10-23 10:10:04 EDT
Created attachment 632140 [details]
space

Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.Login to conductor
2.Build and push apache and mysql images to any provider, to test the wordpress application launch
3.Launch instance using the wordpress application blueprint
  
Actual results:
Observed that on the configure launch-time parameters page, between the first and second field there was lot of space(PFA)

note; The xml i used was having Deprecation Warning

Expected results:
All the fields should be equally spaced


Additional info:

rpm -qa | grep aeolus 
aeolus-configserver-0.4.11-1.el6cf.noarch
rubygem-aeolus-cli-0.7.5-1.el6cf.noarch
rubygem-aeolus-image-0.3.0-12.el6.noarch
aeolus-conductor-0.13.20-1.el6cf.noarch
aeolus-all-0.13.20-1.el6cf.noarch
aeolus-conductor-doc-0.13.20-1.el6cf.noarch
aeolus-configure-2.8.9-1.el6cf.noarch
aeolus-conductor-daemons-0.13.20-1.el6cf.noarch

-----------wordpress xml-----

<deployable version="1.0" name="Wordpress Multi-Instance Deployable">
  <description>This is an example of a multi deployment that deploys wordpress across an apache and mysql instance</description>
  <assemblies>
    <assembly name="apache" hwp="small-x86_64">
      <image id="7d00b85e-19b4-11e2-834b-001f2904e998"/>
      <services>
        <service name="http">
          <executable url="https://github.com/aeolusproject/audrey/raw/master/examples/wordpress/wordpress-http.sh"/>
          <parameters>
            <parameter name="wp_name" type="scalar">
                <value>wordpress</value>
            </parameter>
            <parameter name="wp_user" type="scalar">
                <value>wordpress</value>
            </parameter>
            <parameter name="wp_pw" type="scalar">
                <value>wordpress</value>
            </parameter>
            <parameter name="mysql_ip" type="scalar">
              <reference assembly="mysql" parameter="ipaddress"/>
            </parameter>
            <parameter name="mysql_hostname" type="scalar">
              <reference assembly="mysql" parameter="hostname"/>
            </parameter>
            <parameter name="mysql_dbup" type="scalar">
              <reference assembly="mysql" parameter="dbup"/>
            </parameter>
          </parameters>
        </service>
        <service name="pubkey">
          <executable>
            <contents><![CDATA[#!/bin/bash
                mkdir -p /root/.ssh
                chmod 700 /root/.ssh
                cat pubkey >> /root/.ssh/authorized_keys
                chmod 600 /root/.ssh/authorized_keys
              ]]>
            </contents>
          </executable>
          <files>
            <file>
              <contents filename="pubkey">
                pubkey contents
              </contents>
            </file>
          </files>
        </service>
      </services>
      <returns>
        <return name="hostname"/>
        <return name="ipaddress"/>
      </returns>
    </assembly>
    <assembly name="mysql" hwp="small-x86_64">
      <image id="ee4871b0-19b3-11e2-834b-001f2904e998"/>
      <services>
        <service name="mysql">
          <executable url="https://github.com/aeolusproject/audrey/raw/master/examples/wordpress/wordpress-mysql.sh"/>
          <files>
            <file url="https://github.com/aeolusproject/audrey/raw/master/examples/wordpress/dbup.rb"/>
          </files>
          <parameters>
            <parameter name="wp_name" type="scalar">
                <value>wordpress</value>
            </parameter>
            <parameter name="wp_user" type="scalar">
                <value>wordpress</value>
            </parameter>
            <parameter name="wp_pw" type="scalar">
                <value>wordpress</value>
            </parameter>
            <parameter name="apache_ip" type="scalar">
              <reference assembly="apache" parameter="ipaddress"/>
            </parameter>
            <parameter name="apache_hostname" type="scalar">
              <reference assembly="apache" parameter="hostname"/>
            </parameter>
          </parameters>
        </service>
        <service name="pubkey">
          <executable>
            <contents><![CDATA[#!/bin/bash
                mkdir -p /root/.ssh
                chmod 700 /root/.ssh
                cat pubkey >> /root/.ssh/authorized_keys
                chmod 600 /root/.ssh/authorized_keys
              ]]>
            </contents>
          </executable>
          <files>
            <file>
              <contents filename="pubkey">
                pubkey contents
              </contents>
            </file>
          </files>
        </service>
      </services>
      <returns>
        <return name="hostname"/>
        <return name="ipaddress"/>
        <return name="dbup"/>
      </returns>
    </assembly>
  </assemblies>
</deployable>

Note You need to log in before you can comment on or make changes to this bug.