One correction to Maxim's post - there's no "-e" flag before the <execution_id> (There used to be one but it was removed since it was an inconsistent format).
Also, it'd be helpful if you could provide us with some information about your environment - specifically, what platform are you running on? Ran On Mon, Jun 12, 2017 at 9:07 AM, Maxim Orlov <[email protected]> wrote: > In order to get a more detailed message, you could use the verbosity flag - > "-v". This flag is supported both for the execution start command and the > logs list command. What you would want to do at this stage is try and > figure out what happend with the execution you already ran. In order to do > that, locate your execution id via "aria executions list", and then use the > list logs command "aria logs list -e <execution_id> -vvv". > > On Mon, Jun 12, 2017, 06:43 Chen, Wei D <[email protected]> wrote: > > > Hi Ran, > > > > Thank you for your help! Here comes another issue when I run the "*aria > > services create hello-service -t hello* *aria executions start install -s > > hello-service*", the console shows me the below message: > > " > > Starting execution. Press Ctrl+C cancel > > 10:29:43 | I | Starting 'install' workflow execution > > 10:29:51 | I | web_app_1 Standard.configure started... > > 10:29:51 | I | Executing: /tmp/tmpeuRKHt-configure.sh > > 10:29:52 | I | Execution done (exit_code=1): /tmp/tmpeuRKHt-configure.sh > > 10:29:52 | E | web_app_1 Standard.configure failed > > 10:30:24 | I | web_app_1 Standard.configure started... > > 10:30:24 | I | Executing: /tmp/tmpvwDbY0-configure.sh > > 10:30:25 | I | Execution done (exit_code=1): /tmp/tmpvwDbY0-configure.sh > > 10:30:25 | E | web_app_1 Standard.configure failed" > > > > I have no idea why the configuration is failed, any way to trouble > > shooting the issue or where can I find more detailed error message? > > > > > -----Original Message----- > > > From: Ran Ziv [mailto:[email protected]] > > > Sent: Friday, June 9, 2017 4:42 PM > > > To: [email protected] > > > Subject: Re: How can I use aria CLI options correctly? > > > > > > (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 <[email protected]> > > 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 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
