[Slack] Notifications from the ASF team for June 17th, 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-200110729126/).

---

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

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

*#ariatosca*
 @emblemparade: [UPDATE] wow, what a week.

ARIA-254 is getting close to ready. the bug i was working on for 2 days,
which really scared me because it seemed i was getting wrong yaml data,
ended up ... well, funny story! so, after not finding anything wrong in
the core parser code as hard as i could debug it, i tried working with a
few self-contained examples, but frustratingly i could not reproduce the
bug. so i kept looking at the complex example vs. the simple examples to
see what the differences were ... until i saw it. the complex examples
were using the node template `copy` feature. ugh. so, not a parser
error, but a very stupid user error here. the `copy` feature is honestly
kinda a weird TOSCA feature, but at least ARIA implements it correctly.
:slightly_smiling_face:

after that, things moved more or less smoothly. i did find that the
capability merging code was also incomplete, a rather major bug, so that
had to be added in. but at least the data was correct this time.
:slightly_smiling_face:

the final result works very nicely, using both capability and policy
scaling. ARIA does the right things in terms of matching reqs-and-caps
here. for example, i set a node with a `host` capability that was
limited to a max of 1 occurrence, and then scaled 2 instances of a node
template that required that capability. if i did not also scale the
hosting node, then ARIA would emit the correct validation error: not
enough capacity. increasing the scaling on hosting allows it to match,
and you can see all the right relationships in the graph. (`aria
services show [name] -g`.) the use of capabilities and policies together
is also quite coherent. i created a policy to scale app nodes and
another to scale host nodes, while some host nodes would override the
policy using their capability.

anyway, will need to clean up and add more testing for this next week,
but we're very close. this is a very significant feature for ARIA, very
happy to see this finally coming.





* * *

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.