Re: [Openstack-operators] FIPS Compliance

Sean McGinnis writes: > I'm interested in some feedback from the community, particularly those running > OpenStack deployments, as to whether FIPS compliance [0][1] is something folks > are looking for. > > I've been seeing small changes starting to be proposed here and there for > things like

Re: [Openstack-operators] [Openstack-sigs] Dropping lazy translation support

Matt Riedemann writes: > On 11/5/2018 1:36 PM, Doug Hellmann wrote: >> I think the lazy stuff was all about the API responses. The log >> translations worked a completely different way. > > Yeah maybe. And if so, I came across this in one of the blueprints: > > https

Re: [Openstack-operators] [Openstack-sigs] Dropping lazy translation support

Matt Riedemann writes: > This is a follow up to a dev ML email [1] where I noticed that some > implementations of the upgrade-checkers goal were failing because some > projects still use the oslo_i18n.enable_lazy() hook for lazy log message > translation (and maybe API responses?). > > The

[Openstack-operators] [goals] selecting community-wide goals for T series

I have started a thread on the -dev list [1] to discuss the community-wide goals for the T series, prior to the Forum session in Berlin in a couple of weeks. Please join the conversation in that thread if you have any input. Thanks! Doug [1]

Re: [Openstack-operators] [sean.mcgin...@gmx.com: [openstack-dev] [ptl][release] Proposed changes for cycle-with-milestones deliverables]

Sean McGinnis writes: [snip] > The only problem we've seen is without the milestone releases during the > cycle, > there is quite a gap before the version numbers get incremented for anyone > doing more frequent testing. We wanted to reach out the operator community > since I know there are at

Re: [Openstack-operators] [Openstack-sigs] [openstack-dev] [goals][tc][ptl][uc] starting goal selection for T series

Dean Troyer writes: > On Wed, Sep 26, 2018 at 3:44 PM, Matt Riedemann wrote: >> I started documenting the compute API gaps in OSC last release [1]. It's a >> big gap and needs a lot of work, even for existing CLIs (the cold/live >> migration CLIs in OSC are a mess, and you can't even boot from

[Openstack-operators] [goals][tc][ptl][uc] starting goal selection for T series

It's time to start thinking about community-wide goals for the T series. We use community-wide goals to achieve visible common changes, push for basic levels of consistency and user experience, and efficiently improve certain areas where technical debt payments have become too high - across all

Re: [Openstack-operators] [nova][placement][upgrade][qa] Some upgrade-specific news on extraction

Excerpts from Matt Riedemann's message of 2018-09-06 15:58:41 -0500: > I wanted to recap some upgrade-specific stuff from today outside of the > other [1] technical extraction thread. > > Chris has a change up for review [2] which prompted the discussion. > > That change makes placement only

Re: [Openstack-operators] [Openstack-sigs] [all] Bringing the community together (combine the lists!)

Excerpts from Jeremy Stanley's message of 2018-08-30 17:03:50 +: > The openstack, openstack-dev, openstack-sigs and openstack-operators > mailing lists on lists.openstack.org see an increasing amount of > cross-posting and thread fragmentation as conversants attempt to > reach various corners

Re: [Openstack-operators] Ops Community Documentation - first anchor point

Excerpts from Kunzmann, Gerald's message of 2018-08-27 12:37:28 +: > Hi everyone, > > I think this is a great step to pull together all Ops related discussions > into > one common repo and SIG. > > I noticed that there was a proposal in the Vancouver discussion [1] to create > the repo

Re: [Openstack-operators] Ops Community Documentation - first anchor point

Excerpts from Jonathan Proulx's message of 2018-08-21 15:14:48 -0400: > Hi All... > > I'm still a little confused by the state of this :) > > I know I made some promises then got distracted the looks like Sean > stepped up and got things a bit further, but where is it now? Do we > have an

Re: [Openstack-operators] Openstack Version discovery with the cli client.

Excerpts from Saverio Proto's message of 2018-08-07 15:30:48 +0200: > Hello Jimmy, > > thanks for your help. If I understand correctly the answer you linked, > that helps if you operate the cloud and you have access to the > servers. Then of course you can call nova-manage. > > But being a user

Re: [Openstack-operators] Ops Survey Results!

Excerpts from Chris Morgan's message of 2018-07-03 15:51:09 -0400: > I've spent some time trying to find the old polls, but I don't think we > collected the numbers, we just announced the decision. Certainly for the > ops meetup in mexico last august I found a link for a doodle poll about > which

Re: [Openstack-operators] Fwd: Feedback on Ops Meetup Planning meeting today after the fact

Excerpts from David Medberry's message of 2018-07-03 09:37:15 -0600: > I missed the ops meetup but have the scrollback of what was discussed. > > I'd definitely like to see upgrades (FFUpgrades, etc) and LTS should be on > the Ops Agenda and socialized so that the distros and other concerned >

Re: [Openstack-operators] Ops Survey Results!

Excerpts from Chris Morgan's message of 2018-07-03 07:20:42 -0400: > Question 1. "Are you considering attending the OpenStack Project Technical > Gathering (PTG) in Denver in September?" > > 83.33% yes > 16.67% no > > (24 respondents) How does the response rate to the survey compare to

Re: [Openstack-operators] [openstack-ansible][releases][governance] Change in OSA roles tagging

Excerpts from Jean-Philippe Evrard's message of 2018-06-05 10:14:12 +0200: > Hello, > > *TL:DR;* If you are an openstack-ansible user, consuming our roles directly, > with tags, without using openstack-ansible plays or integrated repo, > then things will change for you. Start using git shas

Re: [Openstack-operators] Ops Community Documentation - first anchor point

Excerpts from Petr Kovar's message of 2018-05-28 16:03:41 +0200: > On Thu, 24 May 2018 07:19:29 -0700 > "Jonathan D. Proulx" wrote: > > > My intention based on current understandign would be to create a git > > repo called "osops-docs" as this fits current naming an thin initial > > document we

Re: [Openstack-operators] Ops Community Documentation - first anchor point

Excerpts from Jonathan D. Proulx's message of 2018-05-24 07:19:29 -0700: > > My intention based on current understandign would be to create a git > repo called "osops-docs" as this fits current naming an thin initial > document we intend to put there and the others we may adopt from > docs-team.

Re: [Openstack-operators] Ops Community Documentation - first anchor point

Excerpts from Doug Hellmann's message of 2018-05-23 22:58:40 -0700: > Excerpts from Melvin Hillsman's message of 2018-05-23 22:26:02 -0700: > > Great to see this moving. I have some questions/concerns based on your > > statement Doug about docs.openstack.org publishing and do not want to > >

Re: [Openstack-operators] Ops Community Documentation - first anchor point

Excerpts from Melvin Hillsman's message of 2018-05-23 22:26:02 -0700: > Great to see this moving. I have some questions/concerns based on your > statement Doug about docs.openstack.org publishing and do not want to > detour the conversation but ask for feedback. Currently there are a number I'm

Re: [Openstack-operators] Ops Community Documentation - first anchor point

You will want to follow the steps of the "project creators' guide" [1]. Not all of them apply, because this is a docs repo and not a code project repo. Let me know if you have questions about which pieces do or do not apply as you go along, and we can work on improving that document as well. The

Re: [Openstack-operators] [openstack-dev] Upstream LTS Releases

Excerpts from Clint Byrum's message of 2017-11-11 08:41:15 -0800: > Excerpts from Doug Hellmann's message of 2017-11-10 13:11:45 -0500: > > Excerpts from Clint Byrum's message of 2017-11-08 23:15:15 -0800: > > > Excerpts from Samuel Cassiba's message of 2017-11-08 08:27:12 -0800: > > > > On Tue,

Re: [Openstack-operators] Upstream LTS Releases

Excerpts from John Dickinson's message of 2017-11-10 14:51:08 -0800: > On 7 Nov 2017, at 15:28, Erik McCormick wrote: > > > Hello Ops folks, > > > > This morning at the Sydney Summit we had a very well attended and very > > productive session about how to go about keeping a selection of past > >

Re: [Openstack-operators] [openstack-dev] Upstream LTS Releases

Excerpts from Clint Byrum's message of 2017-11-08 23:15:15 -0800: > Excerpts from Samuel Cassiba's message of 2017-11-08 08:27:12 -0800: > > On Tue, Nov 7, 2017 at 3:28 PM, Erik McCormick > > wrote: > > > Hello Ops folks, > > > > > > This morning at the Sydney Summit

Re: [Openstack-operators] Technical Committee (TC) learnings, updates

Excerpts from David Medberry's message of 2017-10-27 12:05:09 -0600: > Hi, > > I've volunteered to try and track what the TC is doing for the next few > months and report back to Ops. So, all of this is pretty much done in the > open (on IRC) so don't expect anything here you can't get

Re: [Openstack-operators] [OpenStack-docs] [doc] Operations Guide removal

Excerpts from Chris Morgan's message of 2017-08-18 17:04:02 -0400: > I have just completed loading the files into the wiki for perusal. You can > see the files here in my contrib list > https://wiki.openstack.org/wiki/Special:Contributions/Cmorgan2 That looks like a great start. There are some

Re: [Openstack-operators] [OpenStack-docs] [doc] Operations Guide removal

; Over-Subscription and Thin-Provisioning > Data ONTAP Thin Provisioning > E-Series Thin Provisioning > Unidirectional CHAP Authentication > Establishing an iSCSI Session > iSCSI Session Scope > Configuration Optio

Re: [Openstack-operators] [OpenStack-docs] [doc] Operations Guide removal

Excerpts from Yuki Kasuya's message of 2017-08-10 17:09:48 +0900: > > I tried to convert all docs under ops-guide dir using pandoc. Like > below, toctree,term and some directives doesn't work after converting. > But, at glance, almost fine after converting. > If you don't mind, I'll able to

Re: [Openstack-operators] [openstack-dev] [all] Announcing openstack-sigs ML

Excerpts from Melvin Hillsman's message of 2017-07-13 08:51:16 -0500: >1. Start the openstack-sigs mailing list You can subscribe by visiting http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs Doug ___ OpenStack-operators mailing

Re: [Openstack-operators] [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

Excerpts from Emilien Macchi's message of 2017-06-07 16:42:13 +0200: > On Wed, Jun 7, 2017 at 3:31 PM, Doug Hellmann <d...@doughellmann.com> wrote: >> >> On Jun 7, 2017, at 7:20 AM, Emilien Macchi <emil...@redhat.com> wrote: >> >> On Tue, Jun 6

Re: [Openstack-operators] [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

> On Jun 7, 2017, at 7:20 AM, Emilien Macchi wrote: > > On Tue, Jun 6, 2017 at 6:08 PM, Emilien Macchi > wrote: >> Following-up the session that we had in Boston: >>

Re: [Openstack-operators] [openstack-dev] [upgrades][skip-level][leapfrog] - RFC - Skipping releases when upgrading

Excerpts from Dan Smith's message of 2017-05-26 07:56:02 -0700: > > As most of the upgrade issues center around database migrations, we > > discussed some of the potential pitfalls at length. One approach was to > > roll-up all DB migrations into a single repository and run all upgrades > > for a

Re: [Openstack-operators] DB deadlocks due to connection string

> On May 23, 2017, at 4:01 PM, Doug Hellmann <d...@doughellmann.com> wrote: > > Excerpts from Sean McGinnis's message of 2017-05-23 11:38:34 -0500: >>> >>> This sounds like something we could fix completely by dropping the >>> use of the offending li

Re: [Openstack-operators] DB deadlocks due to connection string

Excerpts from Sean McGinnis's message of 2017-05-23 11:38:34 -0500: > > > > This sounds like something we could fix completely by dropping the > > use of the offending library. I know there was a lot of work done > > to get pymysql support in place. It seems like we can finish that by > >

Re: [Openstack-operators] DB deadlocks due to connection string

Excerpts from Arne Wiebalck's message of 2017-05-23 15:50:43 +: > As discussed on the Cinder channel, I’ve opened > > https://bugs.launchpad.net/oslo.db/+bug/1692956 > > to see if oslo.db would be a good place to produce a warning when it detects > this potential misconfiguration. This

[Openstack-operators] [forum] extra session rooms at the forum

We have a full forum schedule planned, but based on past experience it's inevitable that something was missed, the scheduled slots won't be quite long enough for some deeper discussions, and that new topics will come up during the week. To accommodate those extra discussions, we have 3 session

[Openstack-operators] looking for feedback on proposals to improve logging

I am looking for some feedback on two new proposals to add IDs to log messages. Please see the thread on openstack-dev, and comment there or on the specs referenced there. http://lists.openstack.org/pipermail/openstack-dev/2017-April/115958.html Thanks! Doug

Re: [Openstack-operators] need input on log translations

cycle and someone wants to own tracking that goal, I can help with the write-up. Doug > > Thanks, > > -amrith > > -- > Amrith Kumar > amrith.ku...@gmail.com > > -Original Message- > From: Doug Hellmann [mailto:d...@doughellmann.com] > Sent: Monday,

Re: [Openstack-operators] need input on log translations

Excerpts from Doug Hellmann's message of 2017-03-10 09:38:43 -0500: > There is a discussion on the -dev mailing list about the i18n team > decision to stop translating log messages [1]. The policy change means > that we may be able to clean up quite a lot of "clutter" throughout the > service

Re: [Openstack-operators] need input on log translations

Excerpts from Doug Hellmann's message of 2017-03-10 09:38:43 -0500: > There is a discussion on the -dev mailing list about the i18n team > decision to stop translating log messages [1]. The policy change means > that we may be able to clean up quite a lot of "clutter" throughout the > service

[Openstack-operators] need input on log translations

There is a discussion on the -dev mailing list about the i18n team decision to stop translating log messages [1]. The policy change means that we may be able to clean up quite a lot of "clutter" throughout the service code, because without anyone actually translating the messages there is no need

Re: [Openstack-operators] Packaging Virtualenvs

Excerpts from Silence Dogood's message of 2016-06-23 15:45:34 -0400: > I know from conversations that a few folks package their python apps as > distributable virtualenvs. spotify created dh-virtualenv for this. you > can do it pretty simply by hand. > > I built a toolchain for building rpms

Re: [Openstack-operators] [openstack-dev] [all][log] Ideas to log request-ids in cross-projects

Excerpts from Kekane, Abhishek's message of 2016-03-16 05:56:25 +: > Hi Doug, > > Is there a need to submit a cross-project specs for this or should I create > individual blueprints in individual python-client for this. > Please let me know. > > Thank you, > > Abhishek Kekane You already

Re: [Openstack-operators] [openstack-dev] [all][log] Ideas to log request-ids in cross-projects

Excerpts from Kekane, Abhishek's message of 2016-03-15 08:28:13 +: > Excerpts from Kekane, Abhishek's message of 2016-03-01 06:17:15 +: > > > Hi Devs, > > > > > > Considering return request-id to caller specs [1] is implemented in > > > python-*client, I would like to begin discussion

Re: [Openstack-operators] [tc][security] Proposal to change the CVE embargo window

Excerpts from John Dickinson's message of 2016-01-25 10:58:19 -0800: > I'd like to lengthen the embargo window on CVE disclosures. > > Currently, the process is this > (https://security.openstack.org/vmt-process.html): > > 1. A security bug is reported (and confirmed as valid) > 2. A patch

Re: [Openstack-operators] [openstack-tc] [Performance] Where to place OpenStack performance documentation?

We have had teams publish to readthedocs.org in the past. Linking to the docs there from a home page in the wiki should make them discoverable. Doug > On Dec 2, 2015, at 4:01 AM, Dina Belova wrote: > > Thierry, > > the main issue is to publish docs somewhere people

[Openstack-operators] Upcoming changes to server version numbering for Liberty

As we approach the Liberty-1 milestone, we are applying the changes to server versions discussed at the summit and on the mailing list [1][2]. The tl;dr version is that we are switching from date-based versioning to SemVer (semantic versioning [3]). This will result in version numbers appearing