[openstack-dev] [Ceilometer] Add a pollster plugin

Hi Folks, Is there any best practices or good way to debug whether new pollster plugin work fine for ceilometer? I'd like to add a new pollster plugin into Ceilometer by - adding a new item under enterypoint/ceilometer.poll.central in setup.cfg file - adding the implementation code

Re: [openstack-dev] [Ceilometer] Add a pollster plugin

Thanks a lot, Doug. It does work after configuring pipeline.yaml. Regards, Gary On Aug 12, 2014, at 4:11 AM, Duan, Li-Gong (Gary at HPServers-Core-OE-PSChttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev) li-gong.duan at

[openstack-dev] [Ceilometer] publisher metering_secret in ceilometer.conf

Hi Folks, I created a new pollster plugin for ceilometer by: - adding a new item under enterypoint/ceilometer.poll.central in setup.cfg file - adding the implementation code inheriting plugin.CentralPollster - adding a new source to pipeline.yaml as bellows:

Re: [openstack-dev] [Ceilometer] publisher metering_secret in ceilometer.conf

Btw, there is no service.stat record/row in meter table in ceilometer database. Regards, Gary From: Duan, Li-Gong (Gary@HPServers-Core-OE-PSC) Sent: Monday, August 18, 2014 3:45 PM To: openstack-dev@lists.openstack.org Cc: Duan, Li-Gong (Gary@HPServers-Core-OE-PSC) Subject: [Ceilometer

[openstack-dev] [Ceilometer] Generate Event or Notification in Ceilometer

Hi Folks, Are there any guide or examples to show how to produce a new event or notification add add a handler for this event in ceilometer? I am asked to implement OpenStack service monitoring which will send an event and trigger the handler once a service, say nova-compute, crashes, in a

Re: [openstack-dev] [Ceilometer] Generate Event or Notification in Ceilometer

of such a check for a keystone endpoint: https://github.com/ghantoos/debian-nagios-plugins-openstack/blob/master/plugins/check_keystone Best, -jay From: Duan, Li-Gong (Gary@HPServers-Core-OE-PSC) Sent: Tuesday, July 29, 2014 5:05 PM To: openstack-dev@lists.openstack.org Subject: [Ceilometer

Re: [openstack-dev] [magnum] Notes for Magnum design summit

Hi Tom/All, >6. Ironic Integration: >https://etherpad.openstack.org/p/newton-magnum-ironic-integration >- Start the implementation immediately >- Prefer quick work-around for identified issues (cinder volume attachment, >variation of number of ports, etc.) >We need to implement a bay template

Re: [openstack-dev] [magnum] Notes for Magnum design summit

[mailto:strig...@gmail.com] Sent: Monday, June 13, 2016 3:59 PM To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [magnum] Notes for Magnum design summit Hi Gary. On 13 June 2016 at 09:06, Duan, Li-Gong (Gary, HPServers-C

Re: [openstack-dev] [magnum] Notes for Magnum design summit

Magnum design summit Hi Gary. On 13 June 2016 at 09:06, Duan, Li-Gong (Gary, HPServers-Core-OE-PSC) <li-gong.d...@hpe.com<mailto:li-gong.d...@hpe.com>> wrote: Hi Tom/All, >6. Ironic Integration: >https://etherpad.openstack.org/p/newton-magnum-ironic-integration >- Start the

Re: [openstack-dev] [heat] issue of ResourceGroup in Heat template

lic IP in template). So your issue looks like a strange bug, because I can not reproduce it. Could you share traceback if your error and also provide information about Heat version. Please create new bug with all this data and ping us to review it. On 11 March 2016 at 08:25, Duan, Li-Gong (Gary, HPServer

[openstack-dev] [heat] issue of ResourceGroup in Heat template

Hi, I have 3 Heat templates using ResourceGroup. There are 2 resource groups(rg_a and rg_b) and rg_b depends on rg_a. and rg_b requires the IP address of rg_a as the paremeter of rg_b. I use "rg_a_public_ip: {get_attr: [rg_a, rg_a_public_ip]}" to get the IP address of rg_a both in the section

Re: [openstack-dev] [heat] issue of ResourceGroup in Heat template

it happens due to: - you create in rg_a some Server and probably it goes to active state before ip address becomes available for get_attr. It is necessary to check, but if it's try to add wait condition for this resource, then you will get created rg_a with fully available resources and I suppose

Re: [openstack-dev] [heat] issue of ResourceGroup in Heat template

o ensure that they can actually get the attribute. cheers, Zane. > On 9 March 2016 at 13:14, Duan, Li-Gong (Gary, HPServers-Core-OE-PSC) > <li-gong.d...@hpe.com> wrote: >> Hi, >> >> >> >> I have 3 Heat templates using ResourceGroup. There are 2 resou

Re: [openstack-dev] [heat] issue of ResourceGroup in Heat template

be available before the server > becomes CREATE_COMPLETE. If it isn't then I'd consider that a bug too > - as you pointed out, people are relying on the dependency created by > get_attr to ensure that they can actually get the attribute. > > cheers, > Zane. > >> On 9 Mar

Re: [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer team

+1 for Eli. Regards, Gary Duan From: Hongbin Lu [mailto:hongbin...@huawei.com] Sent: Friday, April 01, 2016 2:18 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer

Re: [openstack-dev] [Magnum] Magnum supports 2 Nova flavor to provision minion nodes

Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [Magnum] Magnum supports 2 Nova flavor to provision minion nodes Hi Hongbin. On Wed, Apr 20, 2016 at 8:13 PM, Hongbin Lu <hongbin...@huawei.com> wrote: > > >

[openstack-dev] [Magnum] Magnum supports 2 Nova flavor to provision minion nodes

Hi Folks, We are considering whether Magnum can supports 2 Nova flavors to provision Kubernetes and other COE minion nodes. This requirement comes from the below use cases: - There are 2 kind of baremetal machines in customer site: one is legacy machines which doesn't support UEFI

Re: [openstack-dev] [Magnum] Magnum supports 2 Nova flavor to provision minion nodes

Hi Eli, This is exactly what I want. If you guys think this requirement is reasonable, I’d like to commit a design spec so that we could discuss it in details. Regards, Gary Duan From: Eli Qiao [mailto:liyong.q...@intel.com] Sent: Wednesday, April 20, 2016 5:08 PM To:

Re: [openstack-dev] [Magnum] Magnum supports 2 Nova flavor to provision minion nodes

[Inactive hide details for "Duan, Li-Gong (Gary, HPServers-Core-OE-PSC)" ---20/04/2016 03:46:18 pm---Hi Folks, We are considerin]"Duan, Li-Gong (Gary, HPServers-Core-OE-PSC)" ---20/04/2016 03:46:18 pm---Hi Folks, We are considering whether Magnum can supports 2 Nova flavors t

Re: [openstack-dev] [Magnum] Magnum supports 2 Nova flavor to provision minion nodes

vision minion nodes From: Duan, Li-Gong (Gary, HPServers-Core-OE-PSC) [mailto:li-gong.d...@hpe.com] Sent: April-20-16 3:39 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [Magnum] Magnum supports 2 Nova flavor to provision minion nodes Hi Folk

Re: [openstack-dev] [magnum] Discuss the idea of manually managing the bay nodes

Hi Hongbin, This is really a good idea, because it will mitigate much of the job of implementing loop and conditional branch in Heat ResourceGroup. But as Kevin pointed out in below mail, it need a careful upgrade/migration path. Meanwhile, as for the blueprint of supporting multiple flavor