I like option 1
Sent from my iPhone
On Oct 26, 2017, at 3:38 PM, Thomas Nadeau
> wrote:
I wanted to ask peoples’ opinions on this issue.
A little background: after 3 people have come to the project fresh, and
tried to
get up and
I wanted to ask peoples’ opinions on this issue.
A little background: after 3 people have come to the project fresh, and
tried to
get up and running, they all encountered difficulty with the instructions for
building
and setup of the project. To this end, Vish and I took on
1) Yes, the two capability names are in the same node type, the name
distinguishes them. (This is a YAML issue.)
2) Yes, the two are unrelated and can be the same or different.
On Thu, Oct 26, 2017 at 1:58 PM, Steve Baillargeon <
steve.baillarg...@ericsson.com> wrote:
> Let me use a concrete
Let me use a concrete example by modifying the compute node type a little.
See below.
Assume this is for a single node type
requirements:
- :
capability: tosca.capabilities.Attachment
node: tosca.nodes.BlockStorage
relationship: tosca.relationships.AttachesTo
Aria-Tosca Community:
I wanted to take a formal poll of the community in terms of
our official support for the Windows platform. While the project should
continue running as the project is a python package, this is more around
the logistics/efforts/resources we as a project have
> On Oct 26, 2017, at 2:50 PM, Tal Liron wrote:
>
> Just to clarify: we currently support *both* Python 2.6 and Python 2.7. The
> poll is to see if we should continue supporting 2.6.
Thanks for the correction. I didn’t mean that we weren’t supporting
2.7. 8)
Just to clarify: we currently support *both* Python 2.6 and Python 2.7. The
poll is to see if we should continue supporting 2.6.
You might ask why we supported 2.6 in the first place: this came from our
long experience working on Cloudify. Many cloud environments are still
quite old, and many
We’ve been considering moving from 2.6 onto the latest 2.7 for some
time now,
and it looks like its time to seriously consider cutting over. Tal has
pointed out
numerous times that because of the 2.6 support, we have a lot of extra testing
and staging that could be eliminated, plus
I'm not entirely sure what you mean... here's a reply according to what I
understand.
In most cases there is no ambiguity because the language is YAML-based. A
dict in YAML has unique keys, so it follows that definitions would be
unique. (We discussed the issue of importing in a previous thread,
Hi
The TOSCA YAML Profile is not 100% clear about duplicate definitions names.
What are the guidelines for ARIA?
Should all definitions names be unique across definitions "classes"
(attributes, properties, requirements, capabilities,...) within a given node
type definition?
Or is it OK to only
10 matches
Mail list logo