DB can be involved in PCP backend

To:	Netflix/vector <reply+01105b8c433952c80af73d2a5b0163878188f48abe7c29c192cf0000000112ffee4792a169ce08668fce@xxxxxxxxxxxxxxxx>, Netflix/vector <vector@xxxxxxxxxxxxxxxxxx>, "pcp@xxxxxxxxxxx" <pcp@xxxxxxxxxxx>
Subject:	DB can be involved in PCP backend
From:	"Panda, Manas Ranjan (NFV BU)" <manas.ran.panda@xxxxxxx>
Date:	Fri, 22 Apr 2016 06:23:42 +0000
Accept-language:	en-US
Authentication-results:	reply.github.com; dkim=none (message not signed) header.d=none;reply.github.com; dmarc=none action=none header.from=hpe.com;
Delivered-to:	pcp@xxxxxxxxxxx
Spamdiagnosticmetadata:	NSPM
Spamdiagnosticoutput:	1:23
Thread-index:	AdGcXzehyGhM+0sZQ/GKba2pjyyQKQ==
Thread-topic:	DB can be involved in PCP backend

Dear Team,

Please let me know is there any DB can be involved in PCP backend? If so please let me know the procedure to implements the same. And one more ask can multiple PCP shared in same DB?

Please respond as I was trying to send mail via : pcp@xxxxxxxxxxx and got a notice as delivered failed.

Thanks,

Manas

<Prev in Thread]	Current Thread	[Next in Thread>
DB can be involved in PCP backend, Panda, Manas Ranjan (NFV BU) <= Re: [pcp] DB can be involved in PCP backend, Nathan Scott

Previous by Date:	pcp updates: add -x noidle to pmiostat, Nikhil Kshirsagar
Next by Date:	Re: [pcp] DB can be involved in PCP backend, Nathan Scott
Previous by Thread:	pcp updates: add -x noidle to pmiostat, Nikhil Kshirsagar
Next by Thread:	Re: [pcp] DB can be involved in PCP backend, Nathan Scott
Indexes:	[Date] [Thread] [Top] [All Lists]