Hi Cale, Very sad to hear that. Let me try to help you. First of all, in Mirantis 8.0 there are no transformers enabled by default. The reason is that by default no Redis is installed for coordination. Anyway, I think we may start with running only one notification agent per cloud. The questions from me are: 1. Did I understand correctly that you use vmware? 2. Could you please send me the compute logs from computes? 3. Could you please send me the output of 'ceilometer sample-list -m ''cpu" -l 1'
Thanks, Nadya On Mon, May 9, 2016 at 6:18 PM, Cale Bouscal <[email protected]> wrote: > Not same hardware, no, neither is it the same software (openstack by > RDO vs by Mirantis). > > At the end of the day, it's just ceilometer "not working right" and > we're not sure why or where to look to figure out the culprit. > > > > -----Original Message----- > From: Remo Mattei <[email protected]> > To: Cale Bouscal <[email protected]> > Cc: [email protected] <[email protected]> > Subject: Re: [Openstack] Ceilometer - cpu meters not collecting data > Date: Mon, 9 May 2016 08:16:05 -0700 > > Basic question same hardware? > > Inviato da iPhone > > > > > Il giorno 09 mag 2016, alle ore 07:53, Cale Bouscal <cale.bouscal@get > > tyimages.com> ha scritto: > > > > We're running Mirantis 8 here, in a lab with a single compute node > > and > > 3 controllers. The compute node is actually a gateway to a vmware > > node. > > (I did not set this up and may not be describing this accurately). > > > > Problem: We wish to use heat templates to create an auto-scaling > > group > > based on cpu utilization spikes. We've created the templates and > > tested > > them in an RDO setup, with success (that is to say, we're confident > > that the templates are set up correctly). However, we're not seeing > > the > > poller pick up the event (the log says "Skip pollster cpu, > > no resources found this cycle"). In my functioning RDO setup, I see > > this line in the log: "Polling pollster > > cpu in the context of cpu_source" > > > > We've been working with our Mirantis support for about a week with > > little to show for it. We've checked the timing settings (making sure > > the configured time units are >= polling times in the pipeline.yaml). > > > > We're not sure where else to look, and I'm hoping the community can > > help. > > _______________________________________________ > > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/ope > > nstack > > Post to : [email protected] > > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/ope > > nstack > > > > !DSPAM:1,5730a8ac31376147515729! > > > _______________________________________________ > Mailing list: > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : [email protected] > Unsubscribe : > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : [email protected] Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
