RE: Missing support for type qualified name

[D Jayachandran]

Hi Ran/Tal,

Thanks for the confirmation. I have created a JIRA issue 
https://issues.apache.org/jira/browse/ARIA-277 
We will let you know when we fork and make a pull request for this.

Regards,
DJ
-Original Message-
From: Tal Liron [mailto:t...@gigaspaces.com] 
Sent: Thursday, June 08, 2017 11:47 PM
To: dev@ariatosca.incubator.apache.org
Subject: Re: Missing support for type qualified name

Thanks, DJ. This was on the list of things to do but we indeed forgot to create 
a JIRA for it...

On Thu, Jun 8, 2017 at 8:24 AM, Ran Ziv  wrote:

> Hi DJ,
>
> Sounds good. Feel free to create a new JIRA yourself!  And thanks for 
> posting on the dev list before creating this issue.
> One small note, I'd personally think of this as a "story" rather than 
> a "bug" - We don't yet claim to be 100% TOSCA complaint, and we're 
> familiar with several other missing spec sections implementations at the 
> moment.
>
> Let me know if you need any help.
> Tal might have more to add on this (Type qualified name) as well.
>
> Thank you
> Ran
>
>
> On Wed, Jun 7, 2017 at 3:35 PM, D Jayachandran < 
> d.jayachand...@ericsson.com>
> wrote:
>
> > Hi,
> >
> > TOSCA Simple Yaml 1.0 profile specification supports usage of  the 
> > following Namespace Alias
> >
> >   1.  Shorthand Name
> >   2.  Type Qualified Name
> >   3.  Type URI
> >
> > ARIA currently supports only "Shorthand Name" and "Type URI". The 
> > support for "Type Qualified Name" is missing which is required to 
> > adhere with the TOSCA Simple yaml 1.0 specifications. Could this be 
> > considered as bug
> and a
> > JIRA issue opened for this ?
> > We would like to start our contribution with this.
> >
> >
> > Regards,
> > DJ
> >
> >
>



--
Tal Liron
Senior Engineer
t...@gigaspaces.com | +1 (773) 828-9339
Cloudify | http://getcloudify.org




   
[image: Azure Webinar]

Re: How can I use aria CLI options correctly?

[Ran Ziv]

(I've replied on this same mail two days ago, so I guess there's been some
sort of a mistake. In any case, I've copy-pasted my reply here as well.)

Hi Dave,

Unfortunately, the README is currently much outddated. That is why the
"aria parse" command raises an invalid command error.

We're working on updating the quick start guide, and hopefully it'll be up
to date early next week, although that too isn't going to provide a full
documentation at this time to ARIA but rather only an introduction.
In the meanwhile however, we'll be glad to help over on this mailing list.


The "parse" command indeed no longer exists; Similar functionality can be
found under "aria service-templates show", but first one has to use "aria
service-templates store", like so:
*aria service-templates store node-cellar.yaml nodecellar*
*aria service-templates show nodecellar -f*


To actually run workflows etc., you'd have to first create a service for a
given service-template, e.g.:
*aria service-templates store examples/hello-world/helloworld.yaml hello*
*aria services create hello-service -t hello*
*aria executions start install -s hello-service*



hope this helps.

On Fri, Jun 9, 2017 at 10:34 AM, Chen, Wei D  wrote:

> Dear developers,
>
> I am currently on ARIA, and is trying to follow the quickstack guide from
> this post (https://github.com/apache/incubator-ariatosca), but I am lost
> there since the CLI option mentioned in the guide is supported yet.
>
> It said the below command can create a service instance, but seems like
> "parse" is not a valid option.
> - aria parse blueprints/tosca/node-cellar/node-cellar.yaml
>
> This is help manual I can see:
> $ aria -h
> Usage: aria [OPTIONS] COMMAND [ARGS]...
>
> ARIA's Command Line Interface
>
> To activate bash-completion. Run: eval "$(_ARIA_COMPLETE=source aria)"
>
> ARIA's working directory resides by default in ~/.aria. To change it, set
> the environment variable ARIA_WORKDIR to something else (e.g. /tmp/).
>
> Options:
> -v, --verbose Show verbose output. You can supply this up to three times
> (i.e. -vvv)
> --version Display the version and exit
> -h, --help Show this message and exit.
>
> 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
>
> There is no "parse" option list there. I have also tried the installation
> via 'pip' with version 0.1,  and this is what I can see:
> $ aria node-cellar.yaml
> Validation issues:
>   0: location: aria-1.0
>  ReaderNotFoundError: location: aria-1.0
>
>
> So, what the error here means? How can I fix it?
>
> This is how the imports defined in the "node-cellar.yaml" from the code
> base.
> imports:
>   - types/openstack.yaml
>   - types/nodejs.yaml
>   - types/mongodb.yaml
>   - types/nginx.yaml
>   - aria-1.0
>
> Thank you very much!
>
> Best Regards,
> Dave Chen
>
>
>
>
>
>
>

How can I use aria CLI options correctly?

[Chen, Wei D]

Dear developers,

I am currently on ARIA, and is trying to follow the quickstack guide from this 
post (https://github.com/apache/incubator-ariatosca), but I am lost there since 
the CLI option mentioned in the guide is supported yet.

It said the below command can create a service instance, but seems like "parse" 
is not a valid option.
- aria parse blueprints/tosca/node-cellar/node-cellar.yaml

This is help manual I can see:
$ aria -h
Usage: aria [OPTIONS] COMMAND [ARGS]...

ARIA's Command Line Interface

To activate bash-completion. Run: eval "$(_ARIA_COMPLETE=source aria)"

ARIA's working directory resides by default in ~/.aria. To change it, set
the environment variable ARIA_WORKDIR to something else (e.g. /tmp/).

Options:
-v, --verbose Show verbose output. You can supply this up to three times
(i.e. -vvv)
--version Display the version and exit
-h, --help Show this message and exit.

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

There is no "parse" option list there. I have also tried the installation via 
'pip' with version 0.1,  and this is what I can see:
$ aria node-cellar.yaml
Validation issues:
  0: location: aria-1.0
 ReaderNotFoundError: location: aria-1.0


So, what the error here means? How can I fix it?

This is how the imports defined in the "node-cellar.yaml" from the code base.
imports:
  - types/openstack.yaml
  - types/nodejs.yaml
  - types/mongodb.yaml
  - types/nginx.yaml
  - aria-1.0

Thank you very much!

Best Regards,
Dave Chen