[Slack] Notifications from the ASF team for May 18th, 2017 at 8:17 AM

[Slack <no...@slack.com>]

Hi ARIA TOSCA,

You have a new direct message from the ASF team
(https://the-asf.slack.com/x-185534614710-185021960548/).

---

@digestai
View in the archives:
https://the-asf.slack.com/x-185534614710-185021960548/archives/D5E4SCANM/p1495083678884944

Digest.AI (8:01 AM, May 18th)
Hi ARIA, 
*Here’s your digest for May 18th 2017*
There are 124 messages yesterday, and the most active user is Tal Liron

*#ariatosca*
 @emblemparade: Unfortunately very small attendance. Must have been
competing with a more popular topic. Also didn't help that time slot was
changed twice
 @smarthi: the problem is there r only about 300 attendees at any
ApacheCon
 and they have about 7 parallel talks happening
 assuming that 70 out of 300 attendees r only there to enjoy Miami Beach
 and 30 of the remaining are organizers
 50 of the remaining are just there to sit in hallways
 u have 150 attendees who are curious about sessions
 @emblemparade: @maxim this looks like the right move. how challenging
will it be to convert plugins to using attributes? how are we going to
solve the problem that attributes need to be pre-declared at the node
types?
 @maxim: Which plugins are we talking about? The current solution
enables to treat the attributes as if they were a dictionary (without
.value) when accessing them from the operation ctx , this could be
easily extended to workflow ctx. About the pre declaration, this is
something we need to discuss​, the obvious way is to place some
"workspace" attribute which is not very TOSCA
 Oh, and maybe more importantly, setting an value to an attribute is
easy: `node.attributes['key'] = 'value'`
 Behind the scenes this would create a parameter 
 Note that `node.attributes['key']['inner_key'] = 'value'` would create
a single parameter which holds a dictionary `{'inner_key': 'value'}`
 @emblemparade: I didn't have any plugin in mind, it's just what i heard
from Ran... Your solution is correct, as long as there's still a way for
users to access/change the type name and  description...
 @alexz: I was giving a try to #ariatosca and I got:
```
$ aria --version
ARIA CLI 0.1.0
```
and the help
```
$ aria --help
(...)
Commands:
  executions         Handle workflow executions
  logs               Show logs from workflow executions
  node-templates     Handle a service template's node templates
  nodes              Handle a service's nodes
  plugins            Handle plugins
  reset              Reset ARIA's working directory
  service-templates  Handle service templates on the manager
  services           Handle services
  workflows          Handle service workflows
```
so, when I follow the docs:
```
$ aria parse blueprints/tosca/node-cellar/node-cellar.yaml
Usage: aria [OPTIONS] COMMAND [ARGS]...

Error: No such command "parse".

Did you mean one of these?
    reset
```
any ideas?
 installed using: `pip install
git+http://git-wip-us.apache.org/repos/asf/incubator-ariatosca.git`
 @emblemparade: Well, users should be able to create new attributes or
modify them dynamically. Or maybe set a value according to its type. Or
print out the description in a log file.
 So how do you access the "raw" parameter model of an attribute?
 @avia: [UPDATE] As part of the effort to convert the `Parameter`
relationships from many-to-many to polymorphic one-to-many, I'm
considering the creation of separate tables for inputs, output,
properties and attributes. Did preliminary discussions with maxim and
ran today, but before deciding on a model change, we'll discuss it
together tomorrow evening (Israel time) to better think of the
implications.
 @aria-tosca: Hi @alexz  Welcome :slightly_smiling_face:
 the Parse command is now replaced with 
aria service_templates store [uri] -n [name]
aria service_templates show [name]
 Parse existed before we added a storage layer to ARIA
 this issue was reported on
Jira(https://issues.apache.org/jira/browse/ARIA-212) and we have another
Jira for updating the README file
(https://issues.apache.org/jira/browse/ARIA-166)

 Generally speaking, the flow using ARIA would be
1. to store a service template from the TOSCA YAML
# aria service-templates store helloworld.yaml hello

2. Create a service 
# aria services create hello -t hello
3. Execute a workflow (the built in install workflow is a graph based
wokflow, that traverses thru lifecycle interfaces of all nodes and
relationships declated in the TOSCA template)
# aria executions start install -s hello
 @alexz you can find some into information here 
https://docs.google.com/presentation/d/1acxm-_fRyGbk4-o7EHHhtBdwIPsKHoPnMcqbwyh-grs/edit#slide=id.g18dc0515b2_0_0
 We are doing an online webinar tomorrow
http://cloudify.co/webinars/aria-model-driven-orchestration-webinar.html#register
 You are most welcome to join  :slightly_smiling_face:
 Oh, I just noticed I haven't switched to my account own (this is
@arthurberezin ) :flushed:



*Links shared by your team today:*



* * *

You can snooze these notifications for
an hour:
https://the-asf.slack.com/unsub/U5FFQJ2LW-5a1cb74d28-notify-mute-1h
eight hours:
https://the-asf.slack.com/unsub/U5FFQJ2LW-796e6535e1-notify-mute-8h
a day:
https://the-asf.slack.com/unsub/U5FFQJ2LW-4e6e073ada-notify-mute-1d
three days:
https://the-asf.slack.com/unsub/U5FFQJ2LW-806a2d8aa0-notify-mute-3d
or the next week:
https://the-asf.slack.com/unsub/U5FFQJ2LW-6adc840c34-notify-mute-7d.

You can also turn email notifications off:
https://the-asf.slack.com/unsub/U5FFQJ2LW-64de78982b-notify.

For more detailed preferences, see your account page:
https://the-asf.slack.com/account.