Open Stack

Hi Pierre,

On our side we are using Train running in LXC containers with Ubuntu 18.04. From what I see  from the role it installed Cloudkitty using pip.

Regards
Jocelyn Thode

From: Gökhan IŞIK - TÜBİTAK BİLGEM <gokhan.isik at tubitak.gov.tr>
Sent: vendredi, 13 novembre 2020 12:51
To: Pierre Riteau <pierre at stackhpc.com>
Cc: Thode Jocelyn <jocelyn.thode at elca.ch>; Henry Bonath <henry at thebonaths.com>; openstack-discuss at lists.openstack.org
Subject: Re: CloudKitty deployment on Train and/or Ussuri

Hi  Thode and Pierre,


I am also an OSA user. We are using cloudkitty in our pike environment. we are now upgrading our environment to ussuri version. We are planning to use cloudkitty again. At pike version, ı have some updates on cloudkitty role[1]. ı will work on cloudkitty ussuri version next week. We can make cloudkitty run. We can contact on #openstack-ansible irc channel. ı hope we can make cloudkitty run successfully.

[1] https://github.com/b3lab/openstack-ansible-os_cloudkitty/tree/stable/pike/

Best wishes,
Gökhan IŞIK (gokhani)
________________________________
Kimden: "Pierre Riteau" <pierre at stackhpc.com<mailto:pierre at stackhpc.com>>
Kime: "Thode Jocelyn" <jocelyn.thode at elca.ch<mailto:jocelyn.thode at elca.ch>>
Kk: "Henry Bonath" <henry at thebonaths.com<mailto:henry at thebonaths.com>>, openstack-discuss at lists.openstack.org<mailto:openstack-discuss at lists.openstack.org>
Gönderilenler: 13 Kasım Cuma 2020 14:28:26
Konu: Re: CloudKitty deployment on Train and/or Ussuri
ThodeHi Thode and Henry,

The CloudKitty role in OSA is using configuration options that were deprecated back in 9.0.0 (Stein) and deleted in 11.0.0 (Train). As I am not an OSA user (I use Kolla Ansible which supports CloudKitty well), I encourage you to submit your fixes to OSA.

About the error you are seeing in cloudkitty-api, I haven't seen this before. Could you give more information about your deployment? Are you using a packaged version (deb / rpm) or source? What is your Linux distribution?

Best wishes,
Pierre Riteau (priteau)

On Fri, 13 Nov 2020 at 11:50, Thode Jocelyn <jocelyn.thode at elca.ch<mailto:jocelyn.thode at elca.ch>> wrote:
Hi Henry,

Unfortunately as I did not get any answer I had stop investigating cloud kitty for the moment, so I was not able to make cloudkitty-api work. For now we have put this task in standby and looking at other alternatives from afar.

Let me know if you make any progress on your end. I'll let you know if we start working again on Cloudkitty on our side

Cheers
Jocelyn

-----Original Message-----
From: Henry Bonath <henry at thebonaths.com<mailto:henry at thebonaths.com>>
Sent: mardi, 10 novembre 2020 21:24
To: Thode Jocelyn <jocelyn.thode at elca.ch<mailto:jocelyn.thode at elca.ch>>
Cc: openstack-discuss at lists.openstack.org<mailto:openstack-discuss at lists.openstack.org>
Subject: Re: CloudKitty deployment on Train and/or Ussuri

Hi Jocelyn,

I am also an Openstack-Ansible user, who is in the same market of trying to find Rating-as-A-Service for my Train cloud.
I stumbled upon your message here after running into the same exact issue that you are having and searching for answers, and am glad to hear that I am not alone.
(Don't you hate when you only find more questions??)

I am testing Cloudkitty v13.0.0 right now and running into the same issue as you are as it relates to 'cloudkitty-api'.
I also found that the templated config you referenced needs to be updated as well.

I'm going to continue to soldier through this and try to get a working configuration, were you able to make any progress on the issue with cloudkitty-api?
Please let me know if we can work together to get this working, I can submit any patches to the openstack-ansible-os_cloudkitty repo.

-Henry

On Fri, Oct 23, 2020 at 2:38 AM Thode Jocelyn <jocelyn.thode at elca.ch<mailto:jocelyn.thode at elca.ch>> wrote:
>
> Hi,
>
>
>
> I was looking at the possibilities to have Rating-as-A-Service in our
> Openstack (currently train but planning to move to Ussuri) and I
> stumbled upon CloudKitty. I’m currently facing multiple issues with
> cloudkitty itself and with openstack-ansible. (We are using a
> containerized deployment with LXC)
>
>
>
> I noticed that openstack-ansible has no playbook yet to install a service like CloudKitty even though starting from Ussuri it was added in the ansible-role-requirements.yml. I have created a small patch to be able to install CloudKitty via openstack-ansible and if this is of interest I could potentially submit a PR with this.
> The os_cloudkitty role seems to kinda work and only with a relatively old version of CloudKitty. For example, here : https://opendev.org/openstack/openstack-ansible-os_cloudkitty/src/branch/stable/train/templates/cloudkitty.conf.j2#L38 since CloudKitty v8.0.0 the section should be named “[fetcher_keystone]”, but I found no information as to which CloudKitty version should be used with this role. Does someone have any recommendation as to which version should be used and if there is any interest in improving the role to support more recent versions of CloudKitty?
> Even when tweaking the configuration and installing v7.0.0 of Cloudkitty it only fixes cloudkitty-processor, I was never able to make cloudkitty-api work I always get an error like “Fatal Python error: Py_Initialize: Unable to get the locale encoding  ModuleNotFoundError: No module named 'encodings'”. Any input on this would be greatly appreciated.
>
>
>
>
> Cheers
>
> Jocelyn

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20201116/0c2270ad/attachment-0001.html>