Just to give a little more info than the original sharing link message.
The mentors
asked me to share the document with the community that I am using to create
the next podling report. This way anyone here can provide inputs/edits. I
plan on
submitting this early next Monday, December 11, 2017 at
Hi Tal,
Finally I was able to rebase and create a new PR for this JIRA. This PR address
the main improvement of using the "plugin.yaml" in a more efficient way in the
service templates.
But I could find there is a improvement item in the same JIRA issue outside of
the plugins usage. Please
John, +1.
Let's update the aria's release process to push sphynx update on Aria
releases.
The reason the website is currently pulling the release docs and not the
other way around is because we published the docs right after we released
0.1.1 and didn't want to introduce changes in that point
I think it may take a bit of elbow grease to get all of the mailing lists
sorted out. for instance, the website mentions user@ and dev@. There's at
least 2 more public mailing lists
commits@, where all of the github emails go out ->
I just wanted to reiterate the advice our mentors have been giving us today
on Slack about first posting here to the list for any threads of
discussion/issues/etc... The recommendation is "mailing list first". Please
try to adhere to this before posting to slack, jira or otherwise as mailing
list
Hi Tal,
Good that this has been considered.
As all the three entities are mere python modules, it is good to have a common
loading mechanism.
But will there be any major change in the existing way of loading plugins and
using the same in the service template?
Thanks,
/Vaish
> On Dec 6, 2017, at 4:40 PM, John D. Ament wrote:
>
> Tom,
>
> Based on what I'm seeing, you're getting the current release (0.1.1). I'm
> not seeing anything that pulls the current master into the site.
>
> I would recommend that we push from the build to the
Tom,
Based on what I'm seeing, you're getting the current release (0.1.1). I'm
not seeing anything that pulls the current master into the site.
I would recommend that we push from the build to the website, rather than
have the website pull this information in.
John
On Wed, Dec 6, 2017 at 8:59
We use 2 tools to generate the website: Jekyll (html) and spynx (docs), and
both tools generate outputs based on the latest code.
--Tom
On Wed, Dec 6, 2017 at 1:28 PM, John D. Ament wrote:
> All,
>
> I'm troubleshooting from yesterday's identified website issues. One
Great question, and it was asked very recently on this list ...
There is a need for a unified way to dynamically load
extensions/plugins/workflows from CSAR files as well as other places. We
are trying to come with a good, forward-looking architectural design for
this loading mechanism. I will
Hi,
I tried using the custom workflow support provided by ARIA.
In the current ARIA, the custom workflows are directly imported as python
modules.
It looks like it is loading the python modules that are bundled along with the
service template in CSAR.
Also I could see that you have plans
Community:
Vish just published instructions on building Docker images to the wiki.
At your convenience, please review and provide feedback you may have for
content at:
https://cwiki.apache.org/confluence/display/ARIATOSCA/Creating+and+running+a+Docker+Container+for+AriaTosca
The removal on the call to install_aria_extensions does solve the problem
in your case, however this might raise other issue. For example: writing a
process executor extension would have no effect if you'd remove the
`install_aria_extensions` function call.
The actual problem is caused because
The Apache Jenkins build system has built AriaTosca Website (build #42)
Status: Fixed
Check console output at https://builds.apache.org/job/AriaTosca%20Website/42/
to view the results.
All,
I'm troubleshooting from yesterday's identified website issues. One thing
I noticed is that as a part of the website build, we download our release.
Why is that?
John
The Apache Jenkins build system has built AriaTosca Website (build #41)
Status: Failure
Check console output at https://builds.apache.org/job/AriaTosca%20Website/41/
to view the results.
The Apache Jenkins build system has built AriaTosca Website (build #40)
Status: Successful
Check console output at https://builds.apache.org/job/AriaTosca%20Website/40/
to view the results.
The Apache Jenkins build system has built AriaTosca Website (build #39)
Status: Successful
Check console output at https://builds.apache.org/job/AriaTosca%20Website/39/
to view the results.
I imagine it is related. :)
On Wed, Dec 6, 2017 at 11:23 AM, Vaishali Krishnamurthy <
v.krishnamurt...@globallogic.com.invalid> wrote:
> I Just wanted to cross check whether this issue is related to the commit
> "ARIA-349 get_attribute is not calculated at runtime". I will debug into
> this and
I Just wanted to cross check whether this issue is related to the commit
"ARIA-349 get_attribute is not calculated at runtime". I will debug into
this and get back to you for any contribution.
Thank you.
-Original Message-
From: Tal Liron [mailto:t...@cloudify.co]
Sent: Wednesday,
Thank you for the additional information!
I think that perhaps this bug has to do with setting/retrieving attribute
data and might not be related to the get_attribute function.
Are you a programmer? Is there any way you can help us debug this on your
end to find out where things go wrong?
If
21 matches
Mail list logo