Re: [tosca-interop] some questions about the csar

[Matt Rutkowski <mrutkows@us.ibm.com>]

Hi Chin,

Just a reminder that Thomas is on vacation
starting this week for 3 weeks so will not likely reply before then.

Let me attempt to answer your questions
(and I also asked Derek to comment) just looking at the README (in the
latest CSAR file) and the "install.sh" scripts for Apache, MySQL
and ApachePHP:

1) The README indicates that the assumed
OS image is "Red Hat Enterprise Linux (RHEL) version 6.3 x86_64 base
image for the virtual machines". 

In regard to "OS" and "Server"
nodes:
Server Node: Each company is
assumed to have an ability to allocate a "server" (or a CPU,
virtual server or virtual CPU) in their respective cloud.  When the
"Server" node type is found by the orchestrator, it should allocate
such a server and attempt to provide the "properties" requested
for a "server" e.g. CPU speed, memory etc. that are set in the
Server's Node Template.
OS Node: Each company
is assumed to have a repository of OS images (VMs) available that the orchestrator
would use to automatically deploy when an "Operating System"
node type was found in the (template) model (in this case RHEL 6.3).  With
this assumption, there is no need to included deployment artifacts for
RHEL in the CSAR,

2) The RHEL 6.3 image is assumed to
already have the Apache, MySQL and Apache PHP already installed in the
image so that when the orchestrator executes the "install.sh"
scripts for these nodes that the BASH files simply use "chkconfig"
command to make sure all these are started as "services" when
the image itself is started. This is quite a common assumption for clouds
as many applications assume a LAMPs (Linux, Apache, MySQL, PHP) stack to
run so it makes sense that most cloud providers have "ready made"
images with these software components already installed.
 >>> for example, Apache
("httpd" service) when the orchestrator installs the node type
"ApacheWebServer" it finds the BASH script "scripts/ApacheWebServer/install.sh"
script which simply has the single line "chkconfig httpd on".
 This assumes the "httpd" RPM packages are already installed
on the RHEL 6.3 image.  There are similar assumptions for both the
MySQL and ApachePHP software  packages.

Lastly,  we agreed in creating
the CSAR for SugarCRM to use only open source software packages to avoid
licensing issues. IBM will not be able to legally redistribute any open
source package so we cannot send you the Apache, MySQL, etc. that we have.
 

Apache, MySQL and PHP support can easily
be downloaded directly from their owner's websites (free) or you can use
the RPM package installer with RHEL operating system when creating your
"RHEL 6.3" image to install them into the image directly.

----------------------------------------
Kind regards,
Matt



From:      
 "Qinjin (Chin)"
<chin.qinjin@huawei.com>
To:      
 Thomas Spatzier <thomas.spatzier@de.ibm.com>,
"tosca-interop@lists.oasis-open.org" <tosca-interop@lists.oasis-open.org>
Cc:      
 "Zhangyi (AA)"
<paul.zhangyi@huawei.com>
Date:      
 08/21/2013 04:04 AM
Subject:    
   [tosca-interop]
some questions about the csar
Sent by:    
   <tosca-interop@lists.oasis-open.org>

---

Hi Thomas
   Some questions
about the CSAR, would you kindly to answer them?
1.There is no image in the
csar, and also no deployment artifact for those "OS" and "Server".
So, how to ref those image during the deployment?
2.For the components "PhpModule",
"ApacheWebServer" and "MySql", there are deployment
artifacts in the service template but without ref install files (e.g. tar,
rpm...). So, how to deploy those components?

How does IBM solve those problems?
 
By the way, Would you provide the version of apache, mysql and php which you used for the demo?
 
 
Best Regards
Jin Qin
 
HUAWEI TECHNOLOGIES CO.,LTD.

Huawei Nanjing Base
No 101. Software Street
Nanjing 210012, P.R.China
Tel: +86 25 566 20559
Fax: +86 25 566 24081
Mobile: +86 13851946871
E-mail:chin.qinjin@huawei.com
www.huawei.com
----------------------------------------------