RE: [tosca-interop] some questions about the demo

[Thomas Spatzier <thomas.spatzier@de.ibm.com>]

Hi Jin Qin,

I added some more comments below inline. I also added the TOSCA Interop
mailing list to CC so everyone has access to this information.

Regards,
Thomas

"Qinjin (Chin)" <chin.qinjin@huawei.com> wrote on 17.07.2013 11:14:16:

> From: "Qinjin (Chin)" <chin.qinjin@huawei.com>
> To: Thomas Spatzier/Germany/IBM@IBMDE,
> Date: 17.07.2013 11:15
> Subject: RE: [tosca-interop] some questions about the demo
>
> Hi Thomas,
>    Thank you for your answer.
>    Plz see my questions inline below.
>    And could you provide the version of mysql, httpd, php module,
> sugarcrm? We want to confim them to ensure that we could use the
> same version for the demo.

For the RPMs we are using the versions that come with the Linux
distribution we are using as base, which is RHEL 6.3 x86_64. When you
install the RPMs by name, the packaging system gives you the current
version.
The version of SugarCRM should be encoded in the file name in the CSAR
files directory.

>
>
> 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
> ----------------------------------------------
>
> -----Original Message-----
> From: tosca-interop@lists.oasis-open.org [mailto:tosca-
> interop@lists.oasis-open.org] On Behalf Of Thomas Spatzier
> Sent: Tuesday, July 16, 2013 4:21 PM
> To: tosca-interop@lists.oasis-open.org
> Subject: Re: [tosca-interop] some questions about the demo
>
> Hi Jin Qin,
>
> please see my answers inline below.
>
> Regards,
> Thomas
>
> <tosca-interop@lists.oasis-open.org> wrote on 16.07.2013 08:50:45:
> > From: "Qinjin (Chin)" <chin.qinjin@huawei.com>
> > To: "tosca-interop@lists.oasis-open.org" <tosca-interop@lists.oasis-
> > open.org>,
> > Cc: Matt Rutkowski <mrutkows@us.ibm.com>, Thomas
> Spatzier/Germany/IBM@IBMDE
> > Date: 16.07.2013 09:01
> > Subject: [tosca-interop] some questions about the demo
> > Sent by: <tosca-interop@lists.oasis-open.org>
> >
> > Hi all
> >
> >          As Huawei want to show the process of the deployment. It
> > means that the demo will use the CSAR file directly.  So there are
> > some questions need to clarify:
> >
> > 1.       How is the Tosca container connect to the VM instance? Just
> > by ssh, or the other method? If by ssh, what’s the username and
> > password will be used?
>
> The way the TOSCA container communicates with deployed VMs is outside the
> scope of the TOSCA specification, i.e. this is implementation choice of
> each TOSCA container provider. Our implementation, for example, uses an
> agent that runs inside deployed VMs to execute scripts.
> [New Question]: how to install the Agent in the VM? Will the
> container deploy agent to each VM instances, or VM images contain
> the agent? Indeed our demo also use agent to execute scripts, and
> also use agent to transfer the parameters. We package the agent in
> the VM images. How about your demo's implementation?

In our case, the agent is part of the images that we use for deployment.
Other technologies exist to download and install the agent during image
activation. Again, I think this is complete implementation specific and
should not be a concern of the TOSCA specification.

> >
> > 2.       Have the Mysql and Apache already integrated in the VM
> > images and only to config them? Or VM images just provide the pure
> > OS, the Mysql and Apache will be installed through Tosca CSAR file?
> > What is the account name and password for the mysql? I still suggest
> > to use the same VM images for the demo. It could reduce many problems.
>
> The VM images provide just the base operating system. All software
> installation (MySQL, httpd, etc.) gets done while deploying the TOSCA
> service template. As part of this process, also the root ID for mysql
gets
> sets.
> [New Question]: the installation in Linux is quite difficult than in
> Windows. There are so many dependency problems. Maybe install one
> application need select to install specific dependency packages
> manually. Have you consider about this scenario? and from the CSAR
> package, I didn't find the script mentioned about install mysql and
> httpd. But I remember you said the scripts in the CSAR in enough to
> show the demo. So is it means we should write the install scripts by
> ourselves?

We are using RHEL 6.3 x86_64 as base image and just install the required
RPM packages by name, and then the RHEL packaging system installs the
current version including all dependencies. We do not cover installation of
very specific versions at the moment. I think this would be a more complex
scenario that needs separate discussion.

>
>
> >
> > 3.       In the discussion, I remember that there is a import and
> > export process. Is it means that the demo will use the company A ‘s
> > tool to generate the CSAR file and use company B ‘s runtime
> > environment to deploy it with that CSAR file? We worried that the
> > used different CSAR may cause some problems, so we suggest that: The
> > CSAR file generate by the tools should be provide as soon as
> > possible for the other company to test their deploy demo;
>
> Ideally, we would use a tool of one company to create the CSAR and then
> deploy it in runtimes of other companies. I can imagine to relax this a
bit
> and just have one CSAR agreed by all companies that we import into each
> runtime and deploy SugarCRM based on it.
>
> [New Question:]  As the demo would be built around (or derived from)
> the SugarCRM CSAR file that was uploaded to OASIS TOSCA Interop SC
> page, is it means the CSAR generate by different tools will have the
> same scripts, plan, definition, metadata, types which are mentioned
> in the CSAR you provide? What's the different between the CSAR files
> generate by different tools? Or all the CSAR files generate by
> different tools should be the same?

I think all the artifacts like scripts and installables should be the same.
Actually, the CSAR produced by different tools should look the same, maybe
with some variations in details like namespace prefixes used, IDs etc. But
that should not matter. Again, I think the base line for interop could also
be one common CSAR we all agree on.

>
> >
> >
> > Best Regards
> > Jin Qin
> >
> > HUAWEI TECHNOLOGIES CO.,LTD.
> > [image removed]
> >
>
> > 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
> > ----------------------------------------------
> >