Hi Charles,
Charles Cui <charles.cui1984@xxxxxxxxx> writes:
[...]
> I add the pcpqa user into the system, and run test under the
> pcp-testsuite package.
> When I run "./check -g sanity -x flakey" it has permission problem.
> So, I issued the command with sudo, which executed without any errors.
Awesome! Yes, pcpqa requires sudo (staring stopping pcp services, among
other things). Personally I have it setup under sudo with nopasswd to
make things eaiser, however I'm aware some individuals aren't
comfortable doing so, up to you.
> In terms of the testsuite, (sudo ./check 000-)
> some tests report problem like output mismatch, or some packages are
> not found(e,g, no docker binary found),
> but most of these tests pass.
> Do I need to investigate the test with problems and fix them?
Having tests return '[notrun] ...' is perfectly fine. So long as there
doesn't seem to be any major problems with the setup I wouldn't be
overly worried about a few fails for now (assuming there isn't a clear
pattern you can see with them). QA is quite important to the pcp
community as a whole, might be worth mentioning your testing plan in a
propsal at some point :)
[...]
> Sure, just be aware that we do have a memcache pmda, as well as
> several
> database pmdas already (check src/pmdas/ for a full list). That
> being
> said, there are always more databases to monitor. Feel free to
> choose
> one you're interested in and detail it in your proposal.
> I looked at the listed provided, I think I can write agents to monitor
> redis or cassandra database,
> if that's possible.
Sure, keep in mind that some data sources are easier to extract
meaningful metrics out of than others, and feel free to detail the
decisions behind your choice in the proposal!
Cheers,
Lukas
|