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 MD5 usage related to its incompatibil
On Wed, Oct 17, 2018 at 10:41:36AM -0500, Matt Riedemann wrote:
> On 10/17/2018 9:24 AM, Ivan Kolodyazhny wrote:
> >
> > As you may know, unfortunately, Horizon doesn't support all features
> > provided by APIs. That's why we created feature gaps list [1].
> >
> > I'd got a lot of great conversat
On Mon, Oct 15, 2018 at 03:01:07PM -0500, Jimmy McArthur wrote:
> Hi -
>
> The Forum schedule is now up
> (https://www.openstack.org/summit/berlin-2018/summit-schedule/#track=262).
> If you see a glaring content conflict within the Forum itself, please let me
> know.
>
I have updated the Forum w
On Fri, Oct 12, 2018 at 11:25:20AM +0200, Martin Magr wrote:
> Greetings guys,
>
> On Thu, Oct 11, 2018 at 4:19 PM, Miguel Angel Ajo Pelayo <
> majop...@redhat.com> wrote:
>
> > Adding the mailing lists back to your reply, thank you :)
> >
> > I guess that +melvin.hills...@huawei.com can
> > hel
m being able to get their work done.
Thanks!
Sean
- Forwarded message from Sean McGinnis -
Date: Wed, 26 Sep 2018 09:22:30 -0500
From: Sean McGinnis
To: openstack-...@lists.openstack.org
Subject: [openstack-dev] [ptl][release] Proposed changes for
cycle-with-milestones deliverables
Reply-T
On Fri, Sep 28, 2018 at 01:54:01PM -0500, Lance Bragstad wrote:
> On Fri, Sep 28, 2018 at 1:03 PM Harry Rybacki wrote:
>
> > On Fri, Sep 28, 2018 at 1:57 PM Morgan Fainberg
> > wrote:
> > >
> > > Ideally I would like to see it in the form of least specific to most
> > specific. But more importan
> On Fri, Sep 28, 2018 at 8:48 AM Lance Bragstad wrote:
>
> > Bumping this thread again and proposing two conventions based on the
> > discussion here. I propose we decide on one of the two following
> > conventions:
> >
> > *::*
> >
> > or
> >
> > *:_*
> >
> > Where is the corresponding service
On Thu, Sep 20, 2018 at 05:30:32PM -0500, Melvin Hillsman wrote:
> Hey everyone,
>
> During the TC meeting at the PTG we discussed the ideal way to capture
> user-centric feedback; particular from our various groups like SIGs, WGs,
> etc.
>
> Options that were mentioned ranged from a wiki page to
On Tue, Sep 18, 2018 at 02:27:03PM -0500, Matt Riedemann wrote:
> The release page says Ocata is planned to go into extended maintenance mode
> on Aug 27 [1]. There really isn't much to this except it means we don't do
> releases for Ocata anymore [2]. There is a caveat that project teams that do
>
> >
> > Yeah it's already on the PTG agenda [1][2]. I started the thread because I
> > wanted to get the ball rolling as early as possible, and with people that
> > won't attend the PTG and/or the Forum, to weigh in on not only the known
> > issues with cross-cell migration but also the things I'm
On Wed, Aug 22, 2018 at 08:23:41PM -0500, Matt Riedemann wrote:
> Hi everyone,
>
> I have started an etherpad for cells topics at the Stein PTG [1]. The main
> issue in there right now is dealing with cross-cell cold migration in nova.
>
> At a high level, I am going off these requirements:
>
>
>
> The solution is conceptually simple. We add a new API microversion in
> Cinder that adds and optional parameter called "generic_keep_source"
> (defaults to False) to both migrate and retype operations.
>
> This means that if the driver optimized migration cannot do the
> migration and the ge
On Tue, Aug 21, 2018 at 03:14:48PM -0400, Jonathan Proulx wrote:
> 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 active repo
> > Plan
> >
> > So to recap above, I would propose the following actions be taken:
> >
> > 1. Create sig-operators as a group to manage operator efforts at least
> > related
> >to what needs to be done in repos.
> > 2. Create an openstack/operations-guide repo to be the new home of the
>
> Plan
>
> So to recap above, I would propose the following actions be taken:
>
> 1. Create sig-operators as a group to manage operator efforts at least related
>to what needs to be done in repos.
> 2. Create an openstack/operations-guide repo to be the new home of the
>operations
Reviving this thread with a fresh start. See below for the original.
To recap, the ops community is willing to take over some of the operator
documentation that is no longer available due to the loss of documentation team
resources. From discussions, there needs to be some official governance over
Adding back the openstack-operators list that Matt added.
On 06/04/2018 05:13 PM, Sean McGinnis wrote:
On 06/04/2018 04:17 PM, Doug Hellmann wrote:
Excerpts from Matt Riedemann's message of 2018-06-04 15:38:48 -0500:
On 6/4/2018 1:07 PM, Sean McGinnis wrote:
Python 3
On 05/29/2018 06:14 AM, Chris Morgan wrote:
Some of us will be only just returning to work today after being away
all week last week for the (successful) OpenStack Summit, therefore I
propose we skip having a meeting today but regroup next week?
Chris
Makes sense to me. I know I have a lot o
On Tue, Apr 24, 2018 at 09:58:26AM +0900, Jean-Philippe Méthot wrote:
> Hi,
>
> This is a very strange behaviour that has causing me issues with my SAN ever
> since we upgraded to Mitaka or Ocata I believe, several months ago.
> Essentially, I used to be able to change the ID of a disk in the SA
On Mon, Apr 23, 2018 at 05:46:40PM +, Tim Bell wrote:
>
> Has anyone experience of working with local disks or volumes with
> physical/logical block sizes of 4K rather than 512?
>
> There seems to be KVM support for this
> (http://fibrevillage.com/sysadmin/216-how-to-make-qemu-kvm-accept-4k
On Mon, Apr 02, 2018 at 03:15:56PM -0500, Melvin Hillsman wrote:
> Unless anyone has any objections I believe we have quorum Jimmy.
>
I agree, I think the feedback I've heard so far is that all parties are willing
to give this a shot. I think we should go ahead.
> On Mon, Apr 2, 2018 at 12:53 PM
> While at it, we should also discuss about what will be the NEXT_MIN
>
> libvirt and QEMU versions for the "Solar" release. To that end, I've
>
> spent going through different distributions and updated the
>
Hey Allison,
I have a few comments below about the Cinder drivers. Would love to hear
everyone's input too.
On Thu, Mar 29, 2018 at 12:22:05PM -0500, Allison Price wrote:
> Hi everyone,
>
> We are opening the OpenStack User Survey submission process next month and
> wanted to collect operator
I have both set up already on my phone. Either WhatsApp or Hangouts work fine
for me.
> On Mar 5, 2018, at 23:31, Shintaro Mizuno
> wrote:
>
> Hi Chris,
>
> Hangout, WhatsApp is fine, too :)
___
OpenStack-operators mailing list
OpenStack-operators
I’m at the Hotel Gracery. Really rather not install slack, but if that works
well for everyone then that’s fine.
I’ll probably wander around the area to find dinner tonight. If I don’t meet up
with others, see you at the meet up tomorrow.
Sean
> On Mar 5, 2018, at 22:14, Shintaro Mizuno
> wr
Hey everyone,
There was some discussion about this in the operator community, so I just
wanted to make sure folks were aware of this recap that Thierry did. I think it
nicely captures and summarizes some of the issues brought up in the long thread
in openstack-dev.
Thanks,
Sean
- Forwarded m
Would be great to get ops-side input. I didn't want to cross-post because I'm
sure this is going to be a big thread and go on for a while. But I would
encourage anyone with input to jump in on that thread. We could also discuss it
separately here and I can try to answer questions or feed that input
Hey Chris,
Sorry, I know I had an action from last week, but I had a conflict so couldn't
attend this week's meeting.
Just to give a quick update, there is still ongoing discussion around what
should be the policy for a deployment project to be considered to be "following
stable policy". There is
On Thu, Oct 19, 2017 at 06:55:38PM -0700, Christopher Hull wrote:
> The qcow2 checksums are correct. They run via nova.
>
> I seem to recall that the cinder checksum calculation when reading in an
> image is faulty. I'm simply going to remove the offending code.
> -Chris
>
I have not heard thi
Just a heads up for anyone consuming Cinder APIs. The v1 API was
deprecated in the Juno release, but
we've kept it around for quite awhile because we knew there were client
implementations out there that
were lagging in getting up to date.
Well, it's now been many releases, and we've had the v1
First - yay, awesome work. Glad to see this made available quickly.
Nice work.
But second - are you aware of deployment issues with Cinder API
with these packages? I've had a report from someone on IRC that
they deployed their environment using these and they are getting
an error because it is no
Hey Adam,
There have been some updates since Liberty to improve handling in the os-brick
library that handles the local device management. But with this showing the
paths down, I wonder if there's something else going on there between the
NetApp box and the Nova compute host.
Could you file a bug
>
> >·What has been your experience with this; any advice?
>
> It works fine. With Horizon you can do it in one step (select the image but
> tell it to boot from volume) but with the CLI I think you need two steps
> (make the volume from the image, then boot from the volume). The extra
> steps
/blockstorage-image-volume-cache.html
Sean
On Tue, Aug 01, 2017 at 10:47:26AM -0500, Sean McGinnis wrote:
> On Tue, Aug 01, 2017 at 11:14:03AM -0400, John Petrini wrote:
> >
> > On the plus side for ephemeral storage; resizing the root disk of images
> > works better. As long as you
On Tue, Aug 01, 2017 at 11:14:03AM -0400, John Petrini wrote:
>
> On the plus side for ephemeral storage; resizing the root disk of images
> works better. As long as your image is configured properly it's just a
> matter of initiating a resize and letting the instance reboot to grow the
> root dis
On Wed, May 31, 2017 at 09:06:35PM -0700, Joshua Harlow wrote:
> Erik McCormick wrote:
> >I've been running Ceph-backed Cinder since, I think, Icehouse. It's
> >really more of a function of your backend or the hypervisor than Cinder
> >itself. That being said, it's been probabky mt smallest Opensta
>
> 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
> removing support for the old library and redirecting mysql://
> connections to use pym
On Tue, May 23, 2017 at 09:16:13AM -0600, David Medberry wrote:
> I have picked "Tuesday, May 30, 2017 8:00 AM (Time zone: Mountain Time)" as
> final option(s) for the Doodle poll "Ops Meetup Preferred Time."
Hey David,
Sorry, I'm sure this was stated elsewhere, but where is this meeting held?
T
Just wanted to put this out there to hopefully spread awareness and
prevent it from happening more.
We had a bug reported in Cinder of hitting a deadlock when attempting
to deelte multiple volumes simultaneously:
https://bugs.launchpad.net/cinder/+bug/1685818
Some were seeing it, but others were
On Mon, May 01, 2017 at 10:17:43AM -0400, Matthew Treinish wrote:
> >
>
> I thought it was just nova too, but it turns out cinder has the same exact
> option as nova: (I hit this in my devstack patch trying to get glance deployed
> as a wsgi app)
>
> https://github.com/openstack/cinder/blob/
On Sat, Apr 15, 2017 at 03:25:09AM +, Ravi, Goutham wrote:
>
> What is being deprecated: Cinder drivers for NetApp E-Series
>
> Period of deprecation: E-Series drivers will be around in stable/pike and
> will be removed in the Queens release (All milestones of this release)
>
Thanks for cl
izing the event. I found it well worth the trip.
Sean
On Mon, Mar 13, 2017 at 01:35:22PM -0500, Sean McGinnis wrote:
> The start of the Cinder session etherpad is available here:
>
> https://etherpad.openstack.org/p/MIL-ops-cinder-rolling-upgrade
>
> Please add whatever info
The start of the Cinder session etherpad is available here:
https://etherpad.openstack.org/p/MIL-ops-cinder-rolling-upgrade
Please add whatever info you would like to it.
I think the main interest was in rolling upgrades, but feel free
to add any other general Cinder topics you would like to dis
This is just a heads up for any operators that are interested. No
immediate action is being taken (at the moment), but that could change.
There was a discussion started on the openstack-dev mailing list
pointing out that the library "drbdmanage" has had its license changed.
It is no longer conside
Hi Belmiro,
In Cinder there is the "raw disk device" driver that has been used by some
for Hadoop and similar applications. That may be something to look at, but
with a big warning.
That being that it is deprecated in the Ocata release and will be removed
in Pike.
The reason it is going to be re
45 matches
Mail list logo
