You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@usergrid.apache.org by Dave <sn...@gmail.com> on 2014/07/14 22:21:41 UTC

Re: Short and Long Term Issues on Chop

Hi Yigit and others,

I getting started with Chop today and hoping to use it to automate running
the Core Persistence performance. First, I'd like to get a simple example
project working with Chop, so I can understand how things fit together.

Are there any getting started and installation documents around? Is the
project README completely out of date or are there some parts that are
still valid.

My approach so far is to 1) get the Chop webapp running locally and 2) get
the Chop Example project working with the webapp and AWS. I have figured
out how to build and run the webapp (using -e for embedded ES) and I do not
see any errors, but I can't figure out how to access the app. Any hints?

I'm happy to document the steps I take, but I might need some pointers
along the way.

Thanks,
- Dave




On Mon, May 12, 2014 at 10:22 AM, Yigit Sapli <yi...@apache.org> wrote:

> Hello everyone,
>
> Although this is mainly directed to people who are currently working on
> Chop, I would definitely appreciate any additional inputs, opinions,
> suggestions and questions. So everyone, please feel free to get involved.
> When everyone agrees on what to do next, we'll register these issues in
> Jira and move on from there.
>
> Right now, core functionality on chop is finished, meaning you can chop
> annotate your test classes, use the chop maven plugin to create and deploy
> your tests, setup or destroy the test clusters and runners on EC2, start,
> stop your tests. And as far as I know, Askat is finishing the new web UI in
> maximum couple of days.
>
> However, although we have an example project inside chop to show how to use
> @TimeChop and @IterationChop annotations, current README is outdated and
> more example projects maybe with tutorials might be cool. I think this
> might help others to get up to speed with configuring and using chop. So if
> anyone has any ideas on what example projects we can do, that'll be great.
>
> Following are the items we can/should do on chop, as far as I can see. I
> tried to order them in accordance with their priorities, more urgent first.
> Please share your ideas so that eventually we have a complete list of what
> to do.
>
> - We need to update the README to make it compatible with the current
> version.
> - We need to check the chop codebase for missing Apache License headers,
> applying proper code styling and javadoc.
> - We already have functional AMIs on Ec2 for both coordinator and runners,
> but we have to update them and make them public.
> - I will chain maven plugin goals, so that consecutive goals will be
> executed automatically. For instance, when a user executes 'mvn chop:start'
> on a chop annotated project, it should automatically cover 'chop:runner',
> 'chop:deploy', and 'chop:setup' goals if needed and start the tests.
> - When a User deploys a project with existing commit Id and maven module to
> coordinator, coordinator should first ask to destroy the existing stack for
> that module and commit, or destroy automatically according to plugin
> parameters. I'll handle that.
> - We need to review our password usage in all REST operations, and make
> sure that they are safe. And maybe we should have an administrator-user
> role distinction in coordinator, so credentials of one user is not exposed
> to others in a multi-user coordinator. Idk if Askat has any input on this,
> or any progress so far about this matter.
> - We need to review our usage of certificates and SSL communications
> between plugin-coordinator and coordinator-runners, and make sure they're
> concrete.
> - Set up information on Stacks in coordinator are held in-memory. Maybe
> it'll be better to persist stack information in elastic search, so that it
> doesn't cause problems while restarting or updating webapp.
> - Right now, chop tests require at least one cluster defined in stack.json.
> Setting up test stacks with just runner instances might be needed.
> - It might be nice being able to tweak JVM parameters on runner and cluster
> instances, and see the change on test results depending on these
> parameters. We may put related parameters in plugin, stack.json and/or
> coordinator to set these. I'd appreciate any inputs on best approach for
> this.
> - Right now, we have a basic representation of deployed modules, launched
> runners on web UI. It could be nice to be able to see all stacks with their
> runner and cluster instances in an organized fashion, setup stacks and
> track setup status for deployed modules directly from web UI, and even
> start, stop tests from web UI. Additionally, it would be good to see
> coordinator logs inside the web UI to troubleshoot any possible problems.
>
> Regards,
> Yigit Sapli
>

Re: Short and Long Term Issues on Chop

Posted by Askhat Asanaliev <aa...@safehaus.org>.

Hi Dave,

The VaadinServlet warning is not related to the main problem here as "Not
all runners are registered". We can get those kind of Vaadin logs while the
tests are running normally. So it is safe to ignore them.

About the main problem - Furkan or Yigit could help out more. They know the
backend better than me.

Regards,
Askat


On Wed, Jul 16, 2014 at 11:39 PM, Dave <sn...@gmail.com> wrote:

> Just say this possible clue in the coordinator logs:
>
> Jul 16, 2014 5:34:26 PM com.vaadin.server.VaadinServlet
> serveStaticResourcesInVAADIN
> INFO: Requested resource [/VAADIN/HEARTBEAT/] not found from filesystem or
> through class loader. Add widgetset and/or theme JAR to your classpath or
> add files to WebContent/VAADIN folder.
>
> - Dave
>
>
>
> On Wed, Jul 16, 2014 at 1:37 PM, Dave <sn...@gmail.com> wrote:
>
> > Hi guys,
> >
> > Thanks for the help so far. Chop really looks great and I've made good
> > progress on getting Chop setup. I now have the coordinator web up and
> > running, I have a stack.json file that launches a working 3 node
> Cassandra
> > and a 3 node ElasticSearch cluster and the chop:setup command says that I
> > am all ready to run tests.
> >
> > INFO chop.plugin.MainMojo.execute(126)<main>- ====== Response from the
> > coordinator ======
> > INFO chop.plugin.MainMojo.execute(127)<main>- Stack is set up and ready
> to
> > start the tests.
> > INFO chop.plugin.MainMojo.execute(128)<main>-
> > =====================================
> >
> >
> > But, when I try to run the tests (in the ChoppedCassandraTests project)
> > the tests fail with this message:
> >
> > INFO chop.plugin.MainMojo.execute(113)<main>- ====== Response from the
> > coordinator ======
> > INFO chop.plugin.MainMojo.execute(114)<main>- Coordinator message: Cannot
> > start tests.
> > Not all runners are registered !!!
> > Number of registered runners : 0
> > INFO chop.plugin.MainMojo.execute(115)<main>-
> > =====================================
> >
> >
> > Any idea what I might be doing wrong or what my next steps should be to
> > debug this issue?
> >
> > I can give you guys access to my Coordinator webapp if that will help.
> >
> > Thanks,
> > Dave
> >
> >
> >
> >
> >
> >
> > On Tue, Jul 15, 2014 at 9:54 AM, Yigit Sapli <yi...@apache.org> wrote:
> >
> >> Hello all,
> >>
> >> Thanks Furkan for helping out. Dave, please let us know if you're having
> >> any problems or if you have any suggestions.
> >>
> >> Regards,
> >> Yigit
> >>
> >> On Tue, Jul 15, 2014 at 7:39 PM, Dave <sn...@gmail.com> wrote:
> >> > Thanks! The ChoppedCassandraTests project looks very useful and that
> is
> >> > where I'm going to start.
> >> >
> >> > - Dave
> >> >
> >> >
> >> >
> >> > On Tue, Jul 15, 2014 at 9:30 AM, Furkan Bıçak <bi...@gmail.com>
> >> wrote:
> >> >
> >> >> Hi Dave,
> >> >>
> >> >> I suppose that confluence page answers most of your questions for
> >> running
> >> >> Chop webapp both locally and on AWS. If not I can help you about the
> >> >> questions you have.
> >> >>
> >> >> Additionally, there is a simple project which uses a Cassandra
> cluster
> >> >> while doing its tests. It might be useful while getting started which
> >> you
> >> >> can find here: https://github.com/salihkardan/ChoppedCassandraTests
> >> >>
> >> >> Best,
> >> >> Furkan.
> >> >>
> >>
> >
> >
>