[openstack-dev] [charms] 18.11 OpenStack Charms release

Announcing the 18.11 release of the OpenStack Charms. The 18.11 charms have support for Nova cells v2 for deployments of Queens and later. The 18.11 release also has preview features including series upgrades and the Octavia load balancer charm. 47 bugs have been fixed and released across the

[openstack-dev] [charms] retiring the ceph charm

Hi All We deprecated and stopped releasing the ceph charm a few cycles back in preference to the split ceph-osd/ceph-mon charms; consider this official notification of retirement! Cheers James __ OpenStack Development

Re: [openstack-dev] [charms] Propose Felipe Reyes for OpenStack Charmers team

Core membership application approved, welcome aboard Felipe! FTR; I have also gathered a off-list +1 from David Ames On Wed, Sep 12, 2018 at 4:04 AM Alex Kavanagh wrote: > +1 from me too. > > On Wed, Sep 12, 2018 at 7:29 AM, Liam Young > wrote: > >> +1 and thanks for all your contributions

Re: [openstack-dev] [charms] Propose Felipe Reyes for OpenStack Charmers team

+1 from me too. On Wed, Sep 12, 2018 at 7:29 AM, Liam Young wrote: > +1 and thanks for all your contributions Felipe! > > On Wed, Sep 12, 2018 at 6:51 AM Chris MacNaughton < > chris.macnaugh...@canonical.com> wrote: > >> +1 Felipe has been a solid contributor to the Openstack Charms for some >>

Re: [openstack-dev] [charms] Propose Felipe Reyes for OpenStack Charmers team

+1 and thanks for all your contributions Felipe! On Wed, Sep 12, 2018 at 6:51 AM Chris MacNaughton < chris.macnaugh...@canonical.com> wrote: > +1 Felipe has been a solid contributor to the Openstack Charms for some > time now. > > Chris > > On 11-09-18 23:07, Ryan Beisner wrote: > > +1 I'm

Re: [openstack-dev] [charms] Propose Felipe Reyes for OpenStack Charmers team

+1 Felipe has been a solid contributor to the Openstack Charms for some time now. Chris On 11-09-18 23:07, Ryan Beisner wrote: +1  I'm always happy to see Felipe's contributions and fixes come through. Cheers! Ryan On Tue, Sep 11, 2018 at 1:10 PM James Page

Re: [openstack-dev] [charms] Propose Felipe Reyes for OpenStack Charmers team

+1 I'm always happy to see Felipe's contributions and fixes come through. Cheers! Ryan On Tue, Sep 11, 2018 at 1:10 PM James Page wrote: > +1 > > On Wed, 5 Sep 2018 at 15:48 Billy Olsen wrote: > >> Hi, >> >> I'd like to propose Felipe Reyes to join the OpenStack Charmers team as >> a

Re: [openstack-dev] [charms] Propose Felipe Reyes for OpenStack Charmers team

+1 On Wed, 5 Sep 2018 at 15:48 Billy Olsen wrote: > Hi, > > I'd like to propose Felipe Reyes to join the OpenStack Charmers team as > a core member. Over the past couple of years Felipe has contributed > numerous patches and reviews to the OpenStack charms [0]. His experience > and knowledge of

Re: [openstack-dev] [charms][ptg] Stein PTG team dinner

Sounds great James. Excellent choice of restaurant, I'm in! (My +1 will probably be pre-occupied with other things that evening, so only count me for the reservation) On Mon, Sep 10, 2018 at 11:13 AM James Page wrote: > Hi All > > As outgoing PTL I have the honour of organising the team dinner

[openstack-dev] [charms][ptg] Stein PTG team dinner

Hi All As outgoing PTL I have the honour of organising the team dinner for the Stein PTG this week. I'm proposing Wednesday night at Russell's Smokehouse: https://www.russellssmokehouse.com/ Let me know if you will be along (and if you have a +1) by end of today and I'll make the

[openstack-dev] [charms] 18.08 OpenStack Charms release

Announcing the 18.08 release of the OpenStack Charms. The 18.08 charms have support for the Rocky OpenStack, Ceph Mimic and Keystone fernet token support. 51 bugs have been fixed and released across the OpenStack charms. For full details of the release, please refer to the release notes:

[openstack-dev] [charms] Propose Felipe Reyes for OpenStack Charmers team

Hi, I'd like to propose Felipe Reyes to join the OpenStack Charmers team as a core member. Over the past couple of years Felipe has contributed numerous patches and reviews to the OpenStack charms [0]. His experience and knowledge of the charms used in OpenStack and the usage of Juju make him a

Re: [openstack-dev] [charms] Deployment guide stable/rocky cut

Hi Ed Yes, it's in hand. I've got a review up: https://review.openstack.org/#/c/598138/ but I also need to create some stable branches, etc. May take a few more days. Thanks Alex. On Fri, Aug 31, 2018 at 12:48 PM, Edward Hope-Morley wrote: > Hi Frode, I think it would be a good idea to add

Re: [openstack-dev] [charms] Deployment guide stable/rocky cut

Hi Frode, I think it would be a good idea to add a link to the charm deployment guide at the following page: https://docs.openstack.org/rocky/deploy/ - Ed On 17/08/18 08:47, Frode Nordahl wrote: > Hello OpenStack charmers, > > I am writing to inform you that  a `stable/rocky` branch has been

[openstack-dev] [charms] Deployment guide stable/rocky cut

Hello OpenStack charmers, I am writing to inform you that a `stable/rocky` branch has been cut for the `openstack/charm-deployment-guide` repository. Should there be any further updates to the guide before the release the changes will need to be landed in `master` and then back-ported to

Re: [openstack-dev] [charms] PTL candidacy for Stein cycle

On Sat, Jul 28, 2018 at 8:25 AM, Frode Nordahl wrote: > Hello all, > > I hereby announce my candidacy for PTL of the OpenStack Charms project [0]. > > Through the course of the past two years I have made many contributions to > the Charms projects and I have had the privilege of becoming a Core >

[openstack-dev] [charms] PTL candidacy for Stein cycle

Hello all, I hereby announce my candidacy for PTL of the OpenStack Charms project [0]. Through the course of the past two years I have made many contributions to the Charms projects and I have had the privilege of becoming a Core developer. Prior to focusing on the Charms project I have made

Re: [openstack-dev] [charms] PTL non-candidacy for Stein cycle

On July 27, 2018 4:09:04 PM UTC, James Page wrote: >Hi All > >I won't be standing for PTL of OpenStack Charms for this upcoming >cycle. > >Its been my pleasure to have been PTL since the project was accepted >into >OpenStack, but its time to let someone else take the helm. I'm not >going

[openstack-dev] [charms] PTL non-candidacy for Stein cycle

Hi All I won't be standing for PTL of OpenStack Charms for this upcoming cycle. Its been my pleasure to have been PTL since the project was accepted into OpenStack, but its time to let someone else take the helm. I'm not going anywhere but expect to have a bit of a different focus for this

[openstack-dev] [charms][ptg] Stein PTG planning etherpad for Charms

Hello Charmers, A etherpad for planning of the upcoming PTG in Denver has been created [0]. Please make a note signalling your attendance and any topics you want covered. 0: https://etherpad.openstack.org/p/charms-stein-ptg -- Frode Nordahl

[openstack-dev] [charms] 18.05 OpenStack Charms release

Announcing the 18.05 release of the OpenStack Charms. The 18.05 charms have full support for the Bionic Ubuntu series. Encryption at rest has been implemented in the storage charms. In addition, the vault and neutron-dynamic-routing charms have been introduced. 72 bugs have been fixed and

Re: [openstack-dev] [charms] [tripleo] [puppet] [fuel] [kolla] [openstack-ansible] [cloudcafe] [magnum] [mogan] [sahara] [shovel] [watcher] [helm] [rally] Heads up: ironic classic drivers deprecation

Hello, Thanks for the notice! JP On 16 March 2018 at 12:09, Dmitry Tantsur wrote: > Hi all, > > If you see your project name in the subject that is because a global search > revived usage of "pxe_ipmitool", "agent_ipmitool" or "pxe_ssh" drivers in > the non-unit-test

[openstack-dev] [charms] [tripleo] [puppet] [fuel] [kolla] [openstack-ansible] [cloudcafe] [magnum] [mogan] [sahara] [shovel] [watcher] [helm] [rally] Heads up: ironic classic drivers deprecation

Hi all, If you see your project name in the subject that is because a global search revived usage of "pxe_ipmitool", "agent_ipmitool" or "pxe_ssh" drivers in the non-unit-test context in one or more of your repositories. The classic drivers, such as pxe_ipmitool, were deprecated in Queens,

Re: [openstack-dev] [charms] 18.02 OpenStack Charms release

URL correction for 18.02 OpenStack Charms release notes: https://docs.openstack.org/charm-guide/latest/1802.html Cheers, Ryan On Fri, Mar 9, 2018 at 2:46 PM, David Ames wrote: > Announcing the 18.02 release of the OpenStack Charms. > > The 18.02 charms have full

[openstack-dev] [charms] 18.02 OpenStack Charms release

Announcing the 18.02 release of the OpenStack Charms. The 18.02 charms have full support for the Queens OpenStack release. 112 bugs have been fixed and released across the OpenStack charms. For full details of the release, please refer to the release notes:

[openstack-dev] [charms] queens support release date

Hi All We're not quite fully baked with Queens testing for the OpenStack charms for this week so we're going to push back a week to the 8th March to allow pre-commit functional testing updates to land. Cheers James __

[openstack-dev] [charms] [ptg] charms dinner

Hi Team As I'm only managing to get to the PTG for Mon/Tues lets schedule a dinner for Monday night; I'll sort out a venue - lemme know direct this week if you'll be coming along! Cheers James __ OpenStack Development

Re: [openstack-dev] [charms]

> Data migration from where to where? We access the current state by retrieving the data from leader db, or am I missing something here? In case there are changes in how data is stored in one version of a charm vs the other. Another problem is application versioning: we do have

Re: [openstack-dev] [charms]

On Mon, Feb 19, 2018 at 9:05 AM, Dmitrii Shcherbakov wrote: > Hi Liam, > >> I was recently looking at how to support custom configuration that relies >> on post deployment setup. > > I would describe the problem in general as follows: > > 1) charms can get

[openstack-dev] [charms]

Hi Liam, > I was recently looking at how to support custom configuration that relies on post deployment setup. I would describe the problem in general as follows: 1) charms can get context not only from Juju (config options, relation data, leader data), environment (operating system

Re: [openstack-dev] [charms] Incorrect Padding for SSL Cert/Key

Hi All, I came across this thread when troubleshooting a similar problem, and wanted to drop in the solution we came up with for posterity: 1) If you're dealing with an API, and the API comes back with an "incorrect padding" error while parsing an SSL Cert, it usually means that the formatting

[openstack-dev] [charms]

Hi, I was recently looking at how to support custom configuration that relies on post deployment setup. Specifically about how to support designate optional configuration for the sink service. The configuration lives on the application units but needs the domain id of the designate domain that

Re: [openstack-dev] [charms]

Seems very reasonable. +1 On 02/14/2018 05:35 AM, Alex Kavanagh wrote: > Yes, that seems like a reasonable approach. +1 > > On Wed, Feb 14, 2018 at 11:29 AM, Liam Young > wrote: > > Hi, > > I would like to propose that we do not

Re: [openstack-dev] [charms]

Yes, that seems like a reasonable approach. +1 On Wed, Feb 14, 2018 at 11:29 AM, Liam Young wrote: > Hi, > > I would like to propose that we do not support the notifications > method for automatically creating DNS records in Queens+. This method > for achieving Neutron

Re: [openstack-dev] [charms]

+1 On Wed, 14 Feb 2018 at 11:29 Liam Young wrote: > Hi, > > I would like to propose that we do not support the notifications > method for automatically creating DNS records in Queens+. This method > for achieving Neutron integration has been superseded both upstream >

Re: [openstack-dev] [charms]

+1 On Wed, 14 Feb 2018 at 11:29 Liam Young wrote: > Hi, > > I would like to propose that we do not support the notifications > method for automatically creating DNS records in Queens+. This method > for achieving Neutron integration has been superseded both upstream >

[openstack-dev] [charms]

Hi, I would like to propose that we do not support the notifications method for automatically creating DNS records in Queens+. This method for achieving Neutron integration has been superseded both upstream and in the charms. By removing support for it in Queens we prevent the charm from

Re: [openstack-dev] [charms] Propose Andrew McLeod for OpenStack Charmers team

+1 from me, too. On Mon, Feb 12, 2018 at 12:39 PM Alex Kavanagh wrote: > Positive +1 from me. Andrew would make a great additiona. > > On Mon, Feb 12, 2018 at 5:00 PM, Ryan Beisner > wrote: > >> Hi All, >> >> I'd like to propose Andrew

Re: [openstack-dev] [charms] Propose Andrew McLeod for OpenStack Charmers team

Positive +1 from me. Andrew would make a great additiona. On Mon, Feb 12, 2018 at 5:00 PM, Ryan Beisner wrote: > Hi All, > > I'd like to propose Andrew McLeod for the OpenStack Charmers (LP) and > charms-core (Gerrit) teams. Andrew has made many commits and

[openstack-dev] [charms] Propose Andrew McLeod for OpenStack Charmers team

Hi All, I'd like to propose Andrew McLeod for the OpenStack Charmers (LP) and charms-core (Gerrit) teams. Andrew has made many commits and bugfixes to the OpenStack Charms over the past couple of years, and he has general charming knowledge and experience which is wider than just OpenStack. He

Re: [openstack-dev] [charms] Propose Dmitrii Shcherbakov for OpenStack Charmers team.

+1 from me On Thu, 8 Feb 2018 at 18:23 Billy Olsen wrote: > Dmitrii easily gets a +1 from me! > > On 02/08/2018 09:42 AM, Alex Kavanagh wrote: > > Hi > > > > I'd like to propose Dmitrii Shcherbakov to join the launchpad > > "OpenStack Charmers" team. He's done some

Re: [openstack-dev] [charms] Propose Dmitrii Shcherbakov for OpenStack Charmers team.

Dmitrii easily gets a +1 from me! On 02/08/2018 09:42 AM, Alex Kavanagh wrote: > Hi > > I'd like to propose Dmitrii Shcherbakov to join the launchpad > "OpenStack Charmers" team.  He's done some tremendous work on existing > the charms, has developed some new ones, and has really developed his >

[openstack-dev] [charms] Propose Dmitrii Shcherbakov for OpenStack Charmers team.

Hi I'd like to propose Dmitrii Shcherbakov to join the launchpad "OpenStack Charmers" team. He's done some tremendous work on existing the charms, has developed some new ones, and has really developed his understanding of configuring and implementing OpenStack. I think he'd make a great

[openstack-dev] [charms] PTL for Rocky

Hi All It will (probably) come as no surprise that I'd like to announce my candidacy for PTL of OpenStack Charms [0]! We've made some good progress in the last cycle with some general housekeeping across the charms set, including removal of untested and generally unused database and

[openstack-dev] [charms] Dublin PTG devroom

Hi Team The Dublin PTG is not so far away now, so lets start on the agenda for our Devroom: https://etherpad.openstack.org/p/DUB-charms-devroom We had a fairly formal agenda of design related topics in Denver for the first day, and spent most of the second day mini-sprinting on various

[openstack-dev] [charms][nova-compute] Services not running that should be: nova-api-metadata

Trying to bring up an Openstack, I keep hitting this issue where nova-compute is giving a status "Services not running that should be: nova-api-metadata" - are others hitting this? juju status | https://paste.ubuntu.com/26480769/ Its possible something has changed in my infrastructure, but I

Re: [openstack-dev] [charms] evolving the ha interface type

Hi James, I like option 2 but I think there is a problem with it. I don't think the hacluster charm sets any data down the relation with the principle until it has first received data from the principle. As I understand it option 2 would change this behaviour so that hacluster immediately sets

[openstack-dev] [charms] 17.11 OpenStack Charms release

Announcing the 17.11 release of the OpenStack Charms. In addition to 125 bug fixes across the charms, the release includes official support for Gnocchi and support for QoS. Several charms have made the migration to python3 only run-time. For full details of the release, please refer to the

Re: [openstack-dev] [charms] evolving the ha interface type

On 11/28/2017 01:50 PM, Dmitrii Shcherbakov wrote: Hi James, The side effect of using JSON is that we will lose type information: In [0]: json.loads(json.dumps([{1: 2}])) Out[0]: [{'1': 2}] In [1]: ast.literal_eval(repr([{1: 2}])) Out[1]: [{1: 2}] I'm not sure this is really an issue for

[openstack-dev] [charms] evolving the ha interface type

Hi James, The side effect of using JSON is that we will lose type information: In [0]: json.loads(json.dumps([{1: 2}])) Out[0]: [{'1': 2}] In [1]: ast.literal_eval(repr([{1: 2}])) Out[1]: [{1: 2}] This is a hard requirement in the JSON spec: https://tools.ietf.org/html/rfc7159#section-4 "An

Re: [openstack-dev] [charms] [designate] Domain and server creation during deployment

Hi Liam, We may do either of two but I think that we need to somehow make it clear to a user that a setup is not over yet e.g. via a status string. As a user you should be able to clear it if you want but I think we need to provide guidance to somebody who doesn't have a full knowdledge of all

[openstack-dev] [charms] [designate] Domain and server creation during deployment

The Designate sink service relies on sink file(s) that contain the domain id(s) of the domains that automatically generated records should be added to. At the moment the designate charm creates a server and domains during charm installation if the neutron-domain and/or nova-domain config options

[openstack-dev] [charms] nominating admcleod for core openstack charmer

Hi OpenStack Charmers, I'd like to nominate Andrew McLeod (admcleod) to be promoted as a core reviewer for the OpenStack Charms project. I trust Andrew's judgement in code review and collaboration with other core reviewers. Please take this to the next IRC meeting for discussion and

[openstack-dev] [charms] Sydney forum user feedback session (Tues@0950)

Hi All Apologies for the late creation of this pad: https://etherpad.openstack.org/p/SYD-forum-charms-ops-feedback if your planning on attending this session please add your name and any topics for discussion! Cheers James

[openstack-dev] [charms] evolving the ha interface type

Hi Team Whilst working on migrating to using Python 3 as the default charm execution environment, I've hit upon a snag with presentation of data from principle charms to the hacluster subordinate charm. Specifically the data presented on the relation is simple str representation of python dicts

[openstack-dev] [charms] bug day this Thursday

Hi All Reminder that as this Thursday is the first Thursday of the month its officially a bug triage/fix day! Our new (23) queue is looking better than ever [0] so it would be great to get that down to near 0. After that focus should switch to High (62) and then Medium (174) bugs already

[openstack-dev] [charms] PTG summary

Hi All Here’s a summary of the charm related discussion from PTG last week. # Cross Project Discussions ## Skip Level Upgrades This topic was discussed at the start of the week, in the context of supporting upgrades across multiple OpenStack releases for operators. What was immediately

[openstack-dev] [charms] 17.08 OpenStack Charms release

Announcing the 17.08 release of the OpenStack Charms. In addition to 204 bug fixes across the charms and support for the Pike OpenStack release, there is a new charm for Gnocchi, support for neutron internal DNS, percona cluster tuning and much more. For full details of the release, please refer

[openstack-dev] [charms] IRC meeting 11th September cancelled

Hi Team I'm cancelling next Mondays IRC; we're (mostly) meeting for the PTG anyway and can re-sync the following Monday. Cheers James __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [charms][ceph-radosgw] radosgw-admin?

Hello, Just wondering if the ceph-radosgw charm provides a method of configuring/accessing the radosgw-admin utility, or if there is a suggested way to get radosgw-admin working in conjunction with ceph/ceph-radosgw charms? In the ceph-radosgw charm, I see the radosgw-admin bin ends up in

[openstack-dev] [charms] Openstack charm with OVN as SDN

Hi all, I am looking to develop an openstack bundle which uses OVN as the SDN. I have been reading : https://docs.openstack.org/charm-guide/latest/ I have also read : https://docs.openstack.org/networking-ovn/latest/install/ index.html As far as I understand, this will require me to replace

Re: [openstack-dev] [charms][ptg] PTG planning pad

A reminder that the PTG is only 2 1/2 weeks away. Please remember to take time to add any topics that you wish to discuss or sprint on during the week. https://etherpad.openstack.org/p/ptg-queens-charms Thanks, Billy On Wed, Aug 9, 2017 at 2:14 AM, James Page wrote: >

[openstack-dev] [charms] PTL cover for the next two weeks

Hi All As I'm off in the backwaters of Scotland with zero chance of any internet access for the next two weeks, I'm delegating my PTL responsibilities to the capable Ryan Beisner until my return. I'll be back just after the charms final freeze in the leadup to the charms release at the start of

[openstack-dev] [charms][ptg] PTG planning pad

Hi All I've started a planning etherpad for the PTG next month; feel free to add topics you want to discuss/sprint on during the week. https://etherpad.openstack.org/p/ptg-queens-charms Cheers James __ OpenStack

[openstack-dev] [charms] ptl for queens

Hi All I would like to announce my candidacy for PTL of the OpenStack Charms project for the Queens development cycle. We've made some good progress during the Pike cycle in terms of improving documentation, with a new deployment guide in the works which should make things much easier for new

Re: [openstack-dev] [charms] Onboarding session at next weeks summit

I'm looking forward to it! On Thu, May 4, 2017 at 5:57 PM Andrew Mcleod wrote: > I'll be there too! :) > > > Andrew > > On Thu, May 4, 2017 at 5:34 PM, Alex Kavanagh > wrote: > >> I will be there too. Looking forward to catching up

Re: [openstack-dev] [charms] Onboarding session at next weeks summit

I'll be there too! :) Andrew On Thu, May 4, 2017 at 5:34 PM, Alex Kavanagh wrote: > I will be there too. Looking forward to catching up with existing and new > people. > > Cheers > Alex. > > On Tue, May 2, 2017 at 11:36 AM, James Page

Re: [openstack-dev] [charms] Onboarding session at next weeks summit

I will be there. It will kind of be an on-boarding experience for me, too :-) On Thu, May 4, 2017 at 11:37 AM Alex Kavanagh wrote: > I will be there too. Looking forward to catching up with existing and new > people. > > Cheers > Alex. > > On Tue, May 2, 2017 at

Re: [openstack-dev] [charms] Onboarding session at next weeks summit

I will be there too. Looking forward to catching up with existing and new people. Cheers Alex. On Tue, May 2, 2017 at 11:36 AM, James Page wrote: > Hi All > > The OpenStack summit is nearly upon us and for this summit we're running a > project onboarding session on

Re: [openstack-dev] [charms] Onboarding session at next weeks summit

I'll be there. -- David Ames On Tue, May 2, 2017 at 3:36 AM, James Page wrote: > Hi All > > The OpenStack summit is nearly upon us and for this summit we're running a > project onboarding session on Monday at 4.40pm in MR-105 (see [0] for full > details) for anyone who

Re: [openstack-dev] [charms] Onboarding session at next weeks summit

I'll be there as well. Looking forward to seeing everyone and meeting some new folks. Corey On Tue, May 2, 2017 at 6:36 AM, James Page wrote: > Hi All > > The OpenStack summit is nearly upon us and for this summit we're running a > project onboarding session on Monday at

Re: [openstack-dev] [charms] Onboarding session at next weeks summit

I plan to be there. Looking forward to it! -Ryan On Tue, May 2, 2017 at 6:36 AM, James Page wrote: > Hi All > > The OpenStack summit is nearly upon us and for this summit we're running a > project onboarding session on Monday at 4.40pm in MR-105 (see [0] for full >

[openstack-dev] [charms] Bug Day Thursday 4th May

Hi Team Just a quick reminder that this Thursday is charm bug day! Please focus on triage and resolution of bugs across the openstack charms - the new bugs URL is in the topic in #openstack-charms on Freenode IRC. Happy bug hunting! Cheers James

[openstack-dev] [charms] Onboarding session at next weeks summit

Hi All The OpenStack summit is nearly upon us and for this summit we're running a project onboarding session on Monday at 4.40pm in MR-105 (see [0] for full details) for anyone who wants to get started either using the OpenStack Charms or contributing to the development of the Charms, The

[openstack-dev] [charms] Charms IRC meetings

Hi This is just a quick reminder that there are two meetings at different times for folks interested in discussing the OpenStack charms. This is so we can get more geographic coverage: - ODD weeks (next on Monday 27th March at 10:00 UTC) - EVEN weeks (next on Monday 3rd April at 17:00 UTC)

[openstack-dev] [charms] bug day this thursday (2nd March)

Hi All Just a reminder that we'll be running our regular bug day on the 2nd March (this coming thursday). Focus, as always, is to touch new bugs and work through in priority order for any fixes! Please co-ordinate any activity in the #openstack-charms channel! Cheers James

[openstack-dev] [charms] 17.02 OpenStack Charms release

Hi All I'm pleased to announce the 17.02 release of the OpenStack Charms. In addition to 120 bug fixes across the charms and support for the Ocata OpenStack release, there are new charms for Ceph FS and Manila and to support integration of Keystone with LDAP/Active Directory leveraging domain

[openstack-dev] [charms] no irc meeting today

Hi Team As most people are at the PTG today, we'll skip todays team IRC meeting. Cheers James __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [charms]

Hello Charmers, Today marks the start of regular feature freeze of OpenStack Charms, for the planned OpenStack Charms stable release on Feb 23. During this time, we focus on any critical bug fixes, any items with a feature freeze exception, additional test coverage, and an increase in edge case

[openstack-dev] [charms] PTG topics

Hi Team We're only a few weeks off the PTG, so I think its about time we started the ball rolling on planning our time out over the Monday/Tuesday. I've created an etherpad so we can brainstorm a schedule for the two days: https://etherpad.openstack.org/p/openstack-charms-ptg-pike If you're

[openstack-dev] [charms] minutes from todays IRC meeting

Hi All Here are the links from todays Charms IRC meeting: Agenda: https://etherpad.openstack.org/p/openstack-charms-weekly-meeting-20170129 Minutes: http://eavesdrop.openstack.org/meetings/charms/2017/charms.2017-01-30-10.03.html Minutes (text):

Re: [openstack-dev] [charms] Incorrect Padding for SSL Cert/Key

Ok, progress. I've encoded my cert and key to base64 strings and specified them in my haproxy config, and seem to be getting past the padding error. My issue now, is that I am not seeing the cert/key in /etc/ssl/private on the haproxy host once deployed. I'm thinking specifying the ssl cert/key

[openstack-dev] [charms] Incorrect Padding for SSL Cert/Key

I'm having issues with padding when trying to specify key/cert as config options for Haproxy, and have experienced the same issue in the past, when trying to specify key/cert for the Openstack charms. Could someone give an example of what the correct padding of a base64 encoded ssl cert might look

[openstack-dev] [charms] Thursday 2nd February - Bug Day!

Hi Team Just a quick reminder that next Thursday marks our second bug day for the year. Please focus on triage and resolution of bugs across the openstack charms - the new bugs URL is in the topic in #openstack-charms on Freenode IRC. Happy bug hunting! Cheers James

[openstack-dev] [charms][ptl] PTL candidacy

Hi All I would like to announce my candidacy for PTL of the OpenStack Charms project. Over the Ocata cycle, we've been incubating the community of developers around the Charms, with new charms for Murano, Trove, Mistral and CloudKitty all due to be included in the release in February. We've

Re: [openstack-dev] [charms] monitoring interface

On Thu, Jan 19, 2017 at 12:44:22PM +, Liam Young wrote: > Thanks for looking into it. I think things should actually work out of the > box as they are now. So, > > Should add nagios checks for glance and cinder to the juju deployed nagios. > (Taken from >

Re: [openstack-dev] [charms] monitoring interface

Hi Brad, Thanks for looking into it. I think things should actually work out of the box as they are now. So, juju deploy nrpe nrpe-glance juju deploy nrpe nrpe-cinder juju deploy nagios juju deploy glance juju deploy cinder juju add-relation nrpe-glance glance juju add-relation nrpe-glance

[openstack-dev] [charms] monitoring interface

Hi all, We're looking at adding the monitor interface to the openstack charms to enable us to use the nagios charm, rather than via an external nagios using nrpe-external-master. I believe this will just be a matter of adding in the interface, adding an appropriate monitor.yaml that defines

[openstack-dev] [charms] bug day this thursday

Hi All Just a quick reminder that this Thursday (5th January) is our first bug day for charms of the year. Objective is to blast through the un-triaged bug backlog assigning some initial priorities and then fixup as many bugs as possible! Please co-ordinate via #openstack-charms so we don't all

Re: [openstack-dev] [charms] ceilometer metering and event time-to-live defaults

Hi Julien On Tue, 3 Jan 2017 at 09:17 Julien Danjou wrote: > > In the current ceilometer charms, we retain all ceilometer data > > indefinitely; the TTL can be overridden by users using configuration > > options, but to me it feels like maybe retaining all data forever by >

Re: [openstack-dev] [charms] ceilometer metering and event time-to-live defaults

On Tue, Jan 03 2017, James Page wrote: Hi James, > In the current ceilometer charms, we retain all ceilometer data > indefinitely; the TTL can be overridden by users using configuration > options, but to me it feels like maybe retaining all data forever by > default is a trip hazard to users,

[openstack-dev] [charms] ceilometer metering and event time-to-live defaults

Hi All In the current ceilometer charms, we retain all ceilometer data indefinitely; the TTL can be overridden by users using configuration options, but to me it feels like maybe retaining all data forever by default is a trip hazard to users, and the actions required to backout of a full DB for

[openstack-dev] [charms] bug squash thursdays

Hi Team Our last (and only) bug day was quite popular/successful, so lets try and have one focus day on bugs a month. So from January, the first Thursday of the month will officially be 'Charm Bug Squash Day'. The objective of the day is to triage any untouched bugs, sift through triaged bugs

[openstack-dev] [charms] irc meetings for next few weeks

Hi All As we're approaching a period where quite a few people will be having time off, I'm cancelling the IRC meetings on Mondays (1000 and 1700 on alternate weeks) until the 9th January at 1700 UTC - at which point we'll resume normal service, with the next meeting after that at 1000 UTC on the

[openstack-dev] [charms] Default SSL Service Endpoints

Running into a few bumps deploying keystone charm with SSL [1]. I'm wondering how others feel about having the Openstack charms account for a heightened level of security by opting to use SSL endpoints over plain http endpoints by default? Something tells me having services default to using SSL

Re: [openstack-dev] [charms] Barbican + Identity Standalone - AWS

Hey James! We were looking at adding Keystone as a user management backend for Kubernetes. This is a great step forward in making that possible, I noticed the barbican charm in the AWS deploy was "local", are there any major changes to the charm from ~openstack-charmers needed for it to run in

[openstack-dev] [charms] Barbican + Identity Standalone - AWS

Another great day of Juju driven successes - deploying the barbican standalone stack for identity mgmt and secrets mgmt. For those that don't know, newton horizon brings support for identity only! This means you can (as I am) use the openstack-dashboard for mgmt of just users, projects, and

[openstack-dev] [charms] regular bug day

Hi Folks We have an organised bug day prior to the OpenStack Summit in Barcelona; I felt that this focused everyone onto collaborating on bugs in a good way, and gave us a great checkpoint on what the key issues are that people are hitting and reporting back on the charms. I'd like to proposed

Re: [openstack-dev] [charms] layer/source charm project-config changes

Following review initial review and corresponding mods, this is ready for re-review. Cheers, Ryan On Mon, Nov 21, 2016 at 2:16 PM, Ryan Beisner wrote: > Good day OpenStack Charmers, > > Project-config change proposed, ready for review: >

[openstack-dev] [charms] layer/source charm project-config changes

Good day OpenStack Charmers, Project-config change proposed, ready for review: https://review.openstack.org/#/c/399299/ To address bug: https://launchpad.net/bugs/1642981 Which is preventing landing of even trivial changes in the source/layer repos:

  1   2   >