tosca-interop — archive
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]
2015-06-29 Interop. SC minutes
Hi Chris,
Thanks for your comments. Please see
my comments in-line in your email below.
Have a great weekend! Happy July 4th!
Regards,
Sahdev Zala
From:
Chris Lauwers <[email protected]>
To:
Matt Rutkowski/Austin/IBM@IBMUS,
"[email protected]" <[email protected]>
Date:
07/01/2015 05:43 PM
Subject:
RE: [tosca-interop]
2015-06-29 Interop. SC minutes
Sent by:
<[email protected]>
I ran the latest CSAR file (2015-06-14
tosca_elk_DRAFT_CSAR.zip) through my validator, and I have a couple more
comments:
1. There is an indentation
error in logstash.yaml. Under the “search_endpoint” requirement, the
capability, node, and relationship keynames should all be indented equally
as follows:
node_types:
tosca.nodes.SoftwareComponent.Logstash:
derived_from: tosca.nodes.SoftwareComponent
requirements:
- search_endpoint:
capability: tosca.capabilities.Endpoint
node: tosca.nodes.SoftwareComponent.Elasticsearch
relationship:
Yes, Christopher
and I noticed this while testing the CSAR deployment and fixed it but I
didn't update new draft CSAR in order to compile possible findings as Christopher
Kaufmann and my team were in mid of testing.
2. In tosca_elk.yaml,
the mongo_db node template is missing the following required properties:
·
port
·
name
These properties are not always required
by certain default installation (e.g. MongoDB installation) and ideally
should be optional. In the latest spec, the port is already optional and
there is a comment to make name optional. I understand you are just pointing
to it and hopefully we will have it resolved in spec soon.
3. There are a number
of instances where operations in interfaces assign values to inputs that
haven’t been previously defined. According to the spec, it is illegal
to assign a value to an input that has not been previously defined. Here
are the instances:
·
In
tosca_elk.yaml, the app_collectd node template defines the Configure operation
of the Standard interface. Specifically, it defines an implementation but
it also assigns a value to the “logstash_ip” input. However, the interface
definition does not define a “logstash_ip” input.
·
similarly,
the kibana node template defines the Configure operation of the Standard
interface. Specifically, it defines an implementation but it also assigns
a value to the “kibana_ip” and “elasticsearch_ip” inputs. However,
the interface definition does not define a “kibana_ip” or “elasticsearch_ip”
input.
·
Same
problem with the app_rsyslog node template. It assigns a value to an undefined
“logstash_ip” input.
·
Same
problem with the mongo_dbms node template. It assigns a value to an undefined
mongodb_ip input
We (Fujitsu and
my team at IBM) have already started creating demo. I have updated a new
draft that we are using for the demo and it is locked down for now unless
we see any issue with deployment or as we discuss in the interop group
and decide to make further changes. I will be considering the above changes
after OSCON demo as they will require testing the full deployment which
is time consuming and also requires changing demo recording. I hope that's
OK.
Also, the CSAR (the latest draft I created
from) is available here -
https://github.com/openstack/heat-translator/tree/master/translator/toscalib/tests/data/CSAR/tosca_elk
Chris
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]