Re: [Openstack-operators] [Openstack-sigs] [all] Naming the T release of OpenStack

and any talks I give in Denver (Forum, Ops, Main) will include "sl". It's handy in a variety of ways. On Thu, Oct 18, 2018 at 9:39 AM David Medberry wrote: > I'm fine with Train but I'm also fine with just adding it to the list and > voting on it. It will win. &

Re: [Openstack-operators] [Openstack-sigs] [all] Naming the T release of OpenStack

I'm fine with Train but I'm also fine with just adding it to the list and voting on it. It will win. Also, for those not familiar with the debian/ubuntu command "sl", now is the time to become so. apt install sl sl -Flea #ftw On Thu, Oct 18, 2018 at 12:35 AM Tony Breeds wrote: > Hello all, >

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

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 parties come join us. And I'd put them at the start of day two. [Looks like the ac

Re: [Openstack-operators] Ops Meetups Team - meeting minutes from today's IRC meeting

I was unable to attend, thanks for the minutes. I wanted to note that there is an EARLY CALL FOR PRESENTATIONS DEADLINE for Berlin which is the end of June. If you plan a presentation (not an operator meeting as per se) you need to get your CFP response in by the end of June per: https://www.open

Re: [Openstack-operators] Proposing no Ops Meetups team meeting this week

Good plan. I'm just getting on email now and hadn't even considered IRC yet. :^) On Tue, May 29, 2018 at 5:53 AM, Erik McCormick wrote: > > > On Tue, May 29, 2018, 7:15 AM Chris Morgan wrote: > >> Some of us will be only just returning to work today after being away all >> week last week for th

[Openstack-operators] Fwd: Follow Up: Private Enterprise Cloud Issues

There was a great turnout at the Private Enterprise Cloud Issues session here in Vancouver. I'll propose a follow-on discussion for Denver PTG as well as trying to sift the data a bit and pre-populate. Look for that sifted data soon. For folks unable to participate locally, the etherpad is here:

Re: [Openstack-operators] Ops Session Proposals for Vancouver Forum

Dropped in 2¢ worth. ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Asking for ask.openstack.org

Hi Jimmy, I tend to jump on things but only those that go to my Inbox and don't otherwise get filtered. I'll see if I'm sub'd to ask.o.o and if so, I'll put that into my Inbox instead of it going into one of my myriad google filtered folders. OTOH, if it is truly just a web site I need to manually

Re: [Openstack-operators] Ops Meetups team - minutes of team meeting 3/20/2018

On Tue, Mar 20, 2018 at 9:16 AM, Chris Morgan wrote: > > On that note, please stand by for some exciting news and discussion about > the future of Ops Meetups and OpenStack PTG, as there seems to be > increasing support for combining the two events into one. I expect an email > thread about this

Re: [Openstack-operators] Ops Meetup, Co-Location options, and User Feedback

On Tue, Mar 20, 2018 at 10:03 AM, Thierry Carrez wrote: > > Personally, I'm not a big fan of separate branding (or "co-location"). > If the "PTG" name is seen as too developer-centric, I'd rather change > the event name (and clearly make it a work event for anyone contributing > to OpenStack, wha

Re: [Openstack-operators] nova 17.0.1 released (queens)

Thanks for the headsup Matt. On Wed, Mar 7, 2018 at 4:57 PM, Matt Riedemann wrote: > I just wanted to give a heads up to anyone thinking about upgrading to > queens that nova has released a 17.0.1 patch release [1]. > > There are some pretty important fixes in there that came up after the > quee

Re: [Openstack-operators] diskimage-builder: prepare ubuntu 17.x images

Subscribe to this bug and click the "This affects me." link near the top. https://bugs.launchpad.net/cloud-images/+bug/1585233 On Thu, Feb 8, 2018 at 1:53 PM, Volodymyr Litovka wrote: > Hi colleagues, > > does anybody here know how to prepare Ubuntu Artful (17.10) image using > diskimage-builde

[Openstack-operators] Ops Mid Cycle in Tokyo Mar 7-8 2018

Hi all, Broad distribution to make sure folks are aware of the upcoming Ops Meetup in Tokyo. You can help "steer" this meetup by participating in the planning meetings or more practically by editing this page (respectfully): https://etherpad.openstack.org/p/TYO-ops-meetup-2018 Sign up for the me

Re: [Openstack-operators] thierry's longer dev cycle proposal

On Wed, Dec 13, 2017 at 2:35 PM, Thierry Carrez wrote: > David Medberry wrote: > While it may have desirable side-effects on the ops side (something I'm > not convinced of), the main reason for it is imho to align our rhythm > with our current development pace / developer cap

Re: [Openstack-operators] thierry's longer dev cycle proposal

ne 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 back > in to > the -dev side. > > Sean > > On Wed, Dec 13, 2017 at 11:48:01AM -0700, David Medberry wrote: > > Hi all, > > &g

[Openstack-operators] thierry's longer dev cycle proposal

Hi all, Please read Thierry's email to the openstack-dev list this morning and follow the thread (getting long already just two hours in.) This references some ideas and concerns that have come from the Ops community, but this is specifically a -dev thread (but I suspect a lot of ramifications fo

[Openstack-operators] Fwd: [Openstack-sigs] [First Contact] New SIG: Let's get this party started!

Kendall indicates she'd like to see Operators involved as much as devs. I kind of agree--we're going to keep growing OpenStack with operations so there will always be newbies to First Contact. -dave -- Forwarded message -- From: Kendall Nelson Date: Thu, Nov 30, 2017 at 3:49 PM Su

Re: [Openstack-operators] Ops Meetups team minutes + main topics

Jon, I think the Foundation staff were very very wary of extending the PTG or doing dual sites simultaneously due to not saving a thing logistically. Yes, it would conceivably save travel for folks that need to go to two separate events (as would the other colo options on the table) but not saving

Re: [Openstack-operators] Ops Meetups team minutes + main topics

I'm actually pushing this out to a broader list and modifying the title as well. We need to try and get all operators viewing this (even if they are also devels, deployers, sigs.) Feel free to reply to me about spamming lists, but I think we need lots of eyes on this. On Tue, Nov 21, 2017 at 9:

Re: [Openstack-operators] Sydney Takeaways - UC

I took an action to work on this bit: 1. "stackalytics" for user community Closely tied to #5. Assists with non-developers being able to show their impact in the community and justify travel amongst other things. - We should discuss how to make this happen and prioritize - Started a

[Openstack-operators] Ops Meetup Meeting Tomorrow? 14:00 UTC

I presume we're still on track for a meeting tomorrow at 14:00 UTC (which will shift it an hour earlier if your timezone had previously recognized DST in the northern hemisphere.) See you there #openstack-operators on Freenode. -dave ___ OpenStack-opera

[Openstack-operators] Fast Forward Upgrades

Some good discussion at the Summit (right now) about Fast Forward Upgrades. Including some concerns that nova-compute INTENTFULLY fails if greater than N-1. More details are appearing in the etherpad. This convo is VERY well attended by MANY openstack devs. Very heavy dev room. https://etherpad

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

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 elsewhere[1]. Of note, they are moving away from "meetings" as meetings are too regional-

Re: [Openstack-operators] Ceph Session at the Forum

Looks like Blair Bethwaite already has one in there called CEPH in OpenStack as a BOF. http://forumtopics.openstack.org/cfp/details/46 On Fri, Sep 29, 2017 at 10:44 AM, Edgar Magana wrote: > Hello, > > I know Patrick Donnelly (@pjdbatrick) was very interested in this session. > Unfortunately,

Re: [Openstack-operators] Ceph Session at the Forum

Looks like Blair Bethwaite already has one in there called CEPH in OpenStack as a BOF. http://forumtopics.openstack.org/cfp/details/46 On Fri, Sep 29, 2017 at 10:44 AM, Edgar Magana wrote: > Hello, > > I know Patrick Donnelly (@pjdbatrick) was very interested in this session. > Unfortunately,

Re: [Openstack-operators] ops meetups team meeting 9/12

Yep, here at PTG also and breakfast got i the way of the meeting. Sorry. On Tue, Sep 12, 2017 at 8:29 AM, Chris Morgan wrote: > Brief meeting today since PTG is underway. Minutes below. > > Best bit of news is that Melvin Hillman reported from PTG that the > Foundation is "on board" to start han

Re: [Openstack-operators] Case studies on Openstack HA architecture

I'm not aware of any studies as per se, but we have long run rabbitmq, MySQL, and all the API endpoints on the same three nodes. On Aug 25, 2017 6:12 PM, "Imtiaz Chowdhury" wrote: > Hi Openstack operators, > > > > Most Openstack HA deployment use 3 node database cluster, 3 node rabbitMQ > clus

Re: [Openstack-operators] [ops meetups team] - resuming regular meetings

Thanks Chris, et al. ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] [dnsmasq] setting ntp-server

Cool beans. Thanks for asking/answering your own question! ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] Reminder: Tuesday after Memorial Day (US) Ops Meetup Planning is one hour earlier

Just a reminder that the Tuesday after Memorial Day, bright and early (in the US) is the Ops Meetup Planning session in #openstack-operators on Freenode IRC at 14:00 UTC ie 10 am Eastern US, 9 am Central US, 8 am Mountain, and 7 am Pacific. Find your timezone time here: https://www.timeanddate.com

[Openstack-operators] [Nova] [Cells] Stupid question: Cells v2 & AZs

Hi Devs and Implementers, A question came up tonight in the Colorado OpenStack meetup regarding cells v2 and availability zones. Can a cell contain multiple AZs? (I assume this is yes.) Can an AZ contain mutliple cells (I assumed this is no, but now in thinking about it, that's probably not righ

Re: [Openstack-operators] UTC 14:00 henceforth for Ops Meet Up planning

600, 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 elsewh

[Openstack-operators] UTC 14:00 henceforth for Ops Meet Up planning

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." Follow this link to open the poll: http://doodle.com/poll/bccipuc8kfm36xna ___ OpenStack-operators mailing list O

Re: [Openstack-operators] [nova][ironic][scheduler][placement] IMPORTANT: Getting rid of the automated reschedule functionality

I have to agree with James My affinity and anti-affinity rules have nothing to do with NFV. a-a is almost always a failure domain solution. I'm not sure we have users actually choosing affinity (though it would likely be for network speed issues and/or some sort of badly architected need or pe

Re: [Openstack-operators] Fwd: [openstack-dev] [nova] Boston Forum session recap - cellsv2

Thanks Dan and Matt! On Fri, May 19, 2017 at 2:48 PM, Matt Riedemann wrote: > FYI > > > > Forwarded Message > Subject: [openstack-dev] [nova] Boston Forum session recap - cellsv2 > Date: Fri, 19 May 2017 08:13:24 -0700 > From: Dan Smith > Reply-To: OpenStack Development Mailin

[Openstack-operators] Vote on the best time for you to participate in Ops Meetup Planning sessions

Hi all, In Boston, we decided to solicit YOUR input on the preferred time for the Openstack Operators "Ops" meet up planning sessions. This is currently on Tuesdays at 15:00 UTC. However, it has been poorly attended. This may be, in part, due to other commitments you have. If so, feel free to vote

Re: [Openstack-operators] [LDT] Scheduling of 'plan the week' at the summit

I poked Matt VanWinkle this morning. He's working it. And apparently we're all starting to take a look at the schedule which is a good thing. I see no Ceph Operators meeting/discussion on the schedule. Some folks have asked me if there is one. (I didn't propose one but maybe I should have.) On Mo

Re: [Openstack-operators] Policy Updates

rator.conf On Thu, Feb 23, 2017 at 3:17 PM, David Medberry wrote: > Yep what Logan said. I'm pretty sure Sean Dague talked about this at the > last Operator's mid-cycle. The "blank" policy.json just means you get the > default policies. You set a value to override

Re: [Openstack-operators] Policy Updates

any case, that sounds like an awful approach because know if we > upgrade > > we will need to be sure that we have a proper json file while in the > past we > > at least were starting from the default one. > > > > > > > > Edgar > > > > > >

[Openstack-operators] Policy Updates

Nova no longer ships with a fleshed-out skeleton of all policy.json. It ships blank. Discussion in here on how to help operators select specific settings to include in their policy.json via documentation. You (as an op) may want to review and comment on this. This model is being proposed for all

Re: [Openstack-operators] [nova] Metadata service over virtio-vsock

Doesn't the virtio solution assume/require a libvirt or more exactly a QEMU/KVM based hypervisor? What about the N-1 other hypervisors? I think the idea of a "hot remove, hot add" of the configdrive has some merit (but remember it is not always ISO-9660 but could be VFAT as well to aid in some mi

Re: [Openstack-operators] Please give your opinion about "openstack server migrate" command.

Replying more to the "thread" and stream of thought than a specific message. 1) Yes, it is confusing. Rikimaru's description is more or less what I believe. 2) Because it is confusing, I continue to use NovaClient commands instead of OpenstackClient I don't know what drove the creation of the Ope

Re: [Openstack-operators] [nova] FYI: live_migration_progress_timeout will default to 0 and be deprecated in Ocata

On Thu, Feb 9, 2017 at 9:29 AM, Matt Riedemann wrote: > Thanks for the heads up Matt, ops appreciate. ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Any serious stability and performance issues on RBD as ephemeral storage ?

We've been using it and recommending it for years. It solves many many problems with a running cloud and there have been very few issues. Pay close attention when upgrading versions of CEPH and do things in the right order and you will be fine! On Wed, Dec 7, 2016 at 7:51 AM, Vahric Muhtaryan wro

Re: [Openstack-operators] Audit Logging - Interested? What's missing?

We've added ELK to our cloud (but of course it largely relies on the existing logging.) There will be a talk about this next month at OpenStack Days Mountain West in SLC. I can provide a link to the slides after that occurs. Our use of ELK is around added security, so ties in nicely with this use

Re: [Openstack-operators] Audit Logging - Interested? What's missing?

rather, here: https://openstackmountainwest2016.sched.org/event/8AkE/osdef-devops-driven-approach-to-securing-a-cloud-infrastructure-using-bigdata?iframe=no&w=&sidebar=yes&bg=no On Wed, Nov 16, 2016 at 5:07 PM, David Medberry wrote: > more info here: > http://www.openstackd

Re: [Openstack-operators] Audit Logging - Interested? What's missing?

more info here: http://www.openstackdaysmw.com/schedule/ On Wed, Nov 16, 2016 at 5:06 PM, David Medberry wrote: > We've added ELK to our cloud (but of course it largely relies on the > existing logging.) There will be a talk about this next month at OpenStack > Days Mountain West

[Openstack-operators] Ops Lightning Talks

we'll hold both. (And in spite of my natural levity, it can be a serious talk, a serious problem, or something completely frivolous but there might be tomatoes in the audience so watch it.) -dave David Medberry OpenStack Guy and your friendly moderator. _

Re: [Openstack-operators] Kilo to Liberty upgrade

Definitely read (and re-read) the release notes here: https://wiki.openstack.org/wiki/ReleaseNotes/Liberty paying close attention to the Upgrade Notes, API changes, etc. You might also search (google or otherwise) this distribution list for history on this topic as many of us did this q On Mon,

Re: [Openstack-operators] Kilo to Liberty upgrade

Definitely read (and re-read) the release notes here: https://wiki.openstack.org/wiki/ReleaseNotes/Liberty paying close attention to the Upgrade Notes, API changes, etc. You might also search (google or otherwise) this distribution list for history on this topic as many of us did this quite some

Re: [Openstack-operators] ElasticSearch on OpenStack

applies to KVM. (resending for clarity) On Fri, Sep 2, 2016 at 6:46 AM, David Medberry wrote: > Hey Tim, > We've just started this effort. I'll see if the guy running the service > can comment today. > > On Fri, Sep 2, 2016 at 6:36 AM, Tim Bell wrote: > >> >>

Re: [Openstack-operators] ElasticSearch on OpenStack

omitted on more line: give java heap 30GB, and leave the rest of the memory to the OS filesystem cache so that Lucene can make best use of it. On Fri, Sep 2, 2016 at 2:15 PM, David Medberry wrote: > From Nathan (on TWC Cloud team): > > Nathan: The page at https://www.elastic.co

Re: [Openstack-operators] ElasticSearch on OpenStack

ings off of that (i.e. choose a flavor with 64GB of RAM and as many CPUs as possible for that RAM allocation, then base disk size on testing of your use case) On Fri, Sep 2, 2016 at 6:46 AM, David Medberry wrote: > Hey Tim, > We've just started this effort. I'll see if the guy r

Re: [Openstack-operators] ElasticSearch on OpenStack

Hey Tim, We've just started this effort. I'll see if the guy running the service can comment today. On Fri, Sep 2, 2016 at 6:36 AM, Tim Bell wrote: > > > Has anyone had experience running ElasticSearch on top of OpenStack VMs ? > > > > Are there any tuning recommendations ? > > > > Thanks > > Ti

Re: [Openstack-operators] Update on Nova scheduler poor performance with Ironic

Great writeup @Mathieu and thanks @sean and @jrolls! -d On Mon, Aug 29, 2016 at 3:34 PM, Mathieu Gagné wrote: > Hi, > > For those that attended the OpenStack Ops meetup, you probably heard > me complaining about a serious performance issue we had with Nova > scheduler (Kilo) with Ironic. > > Th

Re: [Openstack-operators] Shelving

On Thu, Aug 18, 2016 at 6:43 PM, David Medberry wrote: > Shelve completely dissociates from a node. and when you unshelve it goes to a node (likely a new node but potentially the same one). The scheduling algorithm runs as if the instance had never been on the node. There does seem to be s

Re: [Openstack-operators] Shelving

g to keep a slot open for them on that > server, so when you unshelv does it go back to the same node or does it go > to a new node? > > > > ___ > > Kris Lindgren > > Senior Linux Systems Engineer >

Re: [Openstack-operators] Shelving

On Thu, Aug 18, 2016 at 3:12 PM, Jonathan D. Proulx wrote: > > True they do consume IPs. > > In my configuration they do not consume any hypervisor disk. I > *think* this is true of all configurations once the 'shelved' systems > are 'offloaded'. i concur, that's the intent of shelving as I un

Re: [Openstack-operators] [Openstack] Map Nova flavor to glance image

visible everywhere within that project. (As you might imagine this is a pretty common issue that we've directly addressed with Trove but have seen no real solutions for yet.) On Thu, Aug 18, 2016 at 5:45 AM, David Medberry wrote: > Adding the Ops list. > -- Forwarded messag

[Openstack-operators] Fwd: [Openstack] Map Nova flavor to glance image

Adding the Ops list. -- Forwarded message -- From: Jaison Peter Date: Wed, Aug 17, 2016 at 10:29 PM Subject: [Openstack] Map Nova flavor to glance image To: OpenStack General Hi all, Is there any way to map a flavor to some specific glance images? For example if a user chooses

[Openstack-operators] Operators Meetup to plan Mid-Cycle

Last two weeks there appears to have been no operators meetup to continue planning the mid-cycle. Is it completely planned now? (I've been in IRC at 1400 on Tuesdays at #openstack-operators to crickets.) ___ OpenStack-operators mailing list OpenStack-ope

Re: [Openstack-operators] Next Ops Midcycle NYC August 25-26

Would be sweet if that offer could be extended at least a week as we go through the corp travel process. OTOH, $99 is almost cheap enough to buy and not care I'll be doing that I guess. On Wed, Jun 22, 2016 at 9:44 AM, Matt Jarvis wrote: > Hi Mark > > Given we've not got the Eventbrite for t

Re: [Openstack-operators] DNS searchdomains for your instances?

and of course that was the WRONG picture https://www.dropbox.com/s/wxe9e9nu5cqgx9m/Screenshot%202016-06-20%2013.17.02.png?dl=0 On Mon, Jun 20, 2016 at 1:18 PM, David Medberry wrote: > Each tenant in our neutron network has their own subnet and each subnet > sets its own dns rules (s

Re: [Openstack-operators] DNS searchdomains for your instances?

Each tenant in our neutron network has their own subnet and each subnet sets its own dns rules (see pic). https://www.dropbox.com/s/dgfgkdqijmrfweo/2016-06-19%2005.15.29.jpg?dl=0 On Mon, Jun 20, 2016 at 1:07 PM, Kris G. Lindgren wrote: > Hello all, > > Wondering how you guys are handling the dn

Re: [Openstack-operators] NOVA build timeout: Time to fail a vm from build state

Ack. I'm picking my worst case with a 2T volume create and then doubling. On Wed, Jun 15, 2016 at 11:25 AM, Matt Riedemann wrote: > On 6/15/2016 12:09 PM, David Medberry wrote: > >> So, there is a nova.conf setting: >> >> instance_build_timeout (default to 0, nev

[Openstack-operators] NOVA build timeout: Time to fail a vm from build state

So, there is a nova.conf setting: instance_build_timeout (default to 0, never timeout) Does anyone have a "good" value they use for this? In my mind it falls very much into the specific-to-your-cloud-implementation bucket but just wondered what folks were usign for this setting (if any). 10 minu

Re: [Openstack-operators] Issue when trying to snapshot an instance

On Fri, Jun 3, 2016 at 6:22 AM, Grant Morley wrote: > > Turns out is in an issue with the keystone tokens that are timing out when > the snapshot is taking place. Yes, this is exactly the problem we have seen--token timeout. I didn't see the size of this image but we've had that issue on any la

Re: [Openstack-operators] Ops Meetup event sizes

On Wed, Jun 1, 2016 at 2:12 AM, Matt Jarvis wrote: > > The general consensus in the discussions we've had, and from the Austin > summit sessions and the Manchester feedback session, is that between > 150-200 attendees should be the maximum size. > Two comments, points 1) The last day of the Aus

Re: [Openstack-operators] About Live Migration and Bests practises.

In general with L-M on a libvirt/kvm based env, I would cc: daniel barrange (barra...@redhat.com) and I've done that since I didn't seem him specifically. We have taken to GENERALLY SPEAKING doing a single VM at a time. If we have high confidence, we'll go 5 at a time (but never more than that) an

Re: [Openstack-operators] Problems (simple ones) at scale... Invisible VMs.

at 5:26 PM, James Downs wrote: > On Wed, May 18, 2016 at 04:37:42PM -0600, David Medberry wrote: > > > It seems to bypass it... or I'm running into a LOWER limit > (undocumented). > > So help on limit -1 says it is still limited by osapi_max_limit > > You're

Re: [Openstack-operators] Problems (simple ones) at scale... Invisible VMs.

passes > that config option? > > ___ > Kris Lindgren > Senior Linux Systems Engineer > GoDaddy > > From: David Medberry > Date: Wednesday, May 18, 2016 at 4:13 PM > To: "openstack-operators@lists.opensta

[Openstack-operators] Problems (simple ones) at scale... Invisible VMs.

So, we just ran into an "at-sale" issue that shouldn't have been an issue. Many of the OpenStack CLI tools accept a limit parameter (to limit how much data you get back from a single query). However, much less well documented is that there is an inherent limit that you will run into at a 1000 VMs

Re: [Openstack-operators] Anyone else use vendordata_driver in nova.conf?

>>> hasn't really talked about this yet, but I am pretty sure I understand and >>> have addressed Sean's concerns. >>> >>> I'd be curious as to if the proposed solution actually meets your needs. >>> >>> Michael >>> >&g

Re: [Openstack-operators] [Nova] Significance of Error Vs Failed status

So I'm a big ol' -0- don't care on this. We've never used that list before (but will now). Seems like it would be useful though to have it the same for l-m and cold migration. On Wed, May 11, 2016 at 9:27 AM, Andrew Laski wrote: > > > > On Wed, May 11, 2016, a

Re: [Openstack-operators] [Nova] Significance of Error Vs Failed status

Kekane, Hi, This setting, how does it display in the "nova show $UUID" or in the "openstack server show $UUID"? Ie, I don't want a VM showing ERROR state if the VM itself is not in error. A failed migration doesn't leave the VM down (well, not always) but error generally implies it is down. If th

Re: [Openstack-operators] User Survey usage of QEMU (as opposed to KVM) ?

The only reason I can think of is that they are doing nested VMs and don't have the right nesting flag enabled in their base flag. On Tue, May 3, 2016 at 9:01 AM, Daniel P. Berrange wrote: > Hello Operators, > > One of the things that constantly puzzles me when reading the user > survey results

[Openstack-operators] ETHERPAD for today's Ops Session

Subject: ETHERPAD for today's Ops Session https://etherpad.openstack.org/p/AUS-ops-informal-meetup Room is kind of full but we'll let anyone in including lots of interior floor space. Add your name at the bottom of the pad ___ OpenStack-operators mailin

Re: [Openstack-operators] Anyone else use vendordata_driver in nova.conf?

Hi Ned, Jay, We use it also and I have to agree, it's onerous to require users to add that functionality back in. Where was this discussed? On Mon, Apr 18, 2016 at 8:13 AM, Ned Rhudy (BLOOMBERG/ 731 LEX) < erh...@bloomberg.net> wrote: > Requiring users to remember to pass specific userdata throu

Re: [Openstack-operators] Anyone else use vendordata_driver in nova.conf?

Ah, read the bug, we are using the default, not a custom driver. so NEVERMIND. On Mon, Apr 18, 2016 at 8:16 AM, David Medberry wrote: > Hi Ned, Jay, > > We use it also and I have to agree, it's onerous to require users to add > that functionality back in. Where was this disc

[Openstack-operators] BoF OVN call for ideas/discussion points

Hi, There is a Birds of a Feather session on OVN at Austin. If you've got experience or questions or issues with OVN, you can register them here: https://etherpad.openstack.org/p/AUS-BoF-OVN and participate in the session: Wednesday, April 27, 1:50pm-2:30pm https://www.openstack.org/summit/aust

Re: [Openstack-operators] Intel 10 GbE / bonding issue with hash policy layer3+4

I'd definitely post this somewhere that Ubuntu kernel folks would read it. File a bug against that kernel. We're still on 3.13.0- stream so haven't seen this ourselves. On Wed, Mar 23, 2016 at 3:53 AM, Sascha Vogt wrote: > Hi all, > > I thought it might be of interest / get feedback from the ope

Re: [Openstack-operators] [nova] RFEs: communication channel and process

On Mon, Mar 21, 2016 at 5:03 PM, Matt Riedemann wrote: > > I'd also like to get a Nova/Ops cross-project liaison in Newton. In my > mind, that person would attend the ops meeting(s), monitor the list, be in > the #openstack-operators channel and be a point person for bringing issues > from the op

Re: [Openstack-operators] nova-conductor scale out

How many compute nodes do you have (that is triggering your controller node limitations)? We run nova-conductor on multiple control nodes. Each control node runs "N" conductors where N is basically the HyperThreaded CPU count. On Tue, Mar 15, 2016 at 8:44 AM, Gustavo Randich wrote: > Hi, > > Si

Re: [Openstack-operators] [openstack-community] Recognising Ops contributions

On Wed, Mar 2, 2016 at 3:37 PM, Edgar Magana wrote: > We want to make this a reality by gathering a list of criteria that we as > a community feel that shows someone has demonstrated technical > contributions, using their skills as Ops. Our current ideas are as follows: > >- Moderating a ses

Re: [Openstack-operators] [openstack-dev] OpenStack Contributor Awards

On Tue, Mar 1, 2016 at 8:30 AM, Tom Fifield wrote: > Excellent, excellent. > > What's the best place to buy Raspberry Pis these days? > Raspberry Pi 3 is available to buy today from our partners element14 and RS Components

Re: [Openstack-operators] I have an installation question and possible bug

On Mon, Jan 25, 2016 at 4:15 PM, Christopher Hull wrote: > I have not installed Swift. Is that an issue? > No, not an issue. ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listi

Re: [Openstack-operators] I have an installation question and possible bug

Also, is it possible your token timed out during the upload (thereby truncating it)? Validate the byte size of the final uploaded (large) glance image. On Mon, Jan 25, 2016 at 10:59 AM, Abel Lopez wrote: > First question, what is your glance store? > Also, it sounds like you created the large im

Re: [Openstack-operators] Operational Director?

Tim, thanks for pointing out the User Committee. You are the second (or third) one to mention that to me in this context and is another great way to influence the direction OpenStack takes (and goes hand in hand with this operator's list, the midcycle, and operator's summit meetings.) -d _

[Openstack-operators] Operational Director?

Hi all, Isn't it time to get an operational director--or rather another/additional operators as directors? I've nominated a few (unnamed here) and you may be interested in nominationg others. Look for the email with subject line: Notice of meeting to elect Individual Directors

Re: [Openstack-operators] OPs Midcycle location discussion.

On Tue, Nov 17, 2015 at 11:45 AM, Erik McCormick wrote: > We're deciding not to innovate a solution to allow people to > participate in a group that is attempting to provide innovative ideas. > How ironic. I actually don't think it would require much innovation. > The Ceph guys run their entire d

Re: [Openstack-operators] OPs Midcycle location discussion.

Following up to what Matt said, even for the service (nova, cinder, etc) mid-cycles I've been in, typically only 1 or 2 folks participate remotely and they make sure to have someone pay attention/alert them when their topics are coming up. I don't think remote/virtual scales beyond 1-2 remote parti

Re: [Openstack-operators] [eu] European Operators Meetup February 15th/16th 2016

Thanks to Canonical, Codethink, Midokura, DataCentred and the EU operators that got this going! Nicely done. On Wed, Nov 11, 2015 at 2:11 AM, Matt Jarvis wrote: > Canonical, Codethink, Midokura and DataCentred ___ OpenStack-operators mailing list OpenS

Re: [Openstack-operators] OpenStack Tuning Guide

Great Kevin. Thanks for honchoing and sharing. On Wed, Nov 4, 2015 at 3:56 PM, Kevin Bringard (kevinbri) < kevin...@cisco.com> wrote: > Hey all! > > Something that jumped out at me in Tokyo was how much it seemed that > "basic" tuning stuff wasn't common knowledge. This was especially prevalent >

Re: [Openstack-operators] Informal Ops Meetup?

ah in the PAMIR (conf) building? Excellent. On Fri, Oct 30, 2015 at 11:02 AM, Dina Belova wrote: > We're on the ex-HP-lounge - 2F floor :) > > Cheers, > Dina > > On Fri, Oct 30, 2015 at 10:50 AM, David Medberry > wrote: > >> They all just moved up to the P

Re: [Openstack-operators] Informal Ops Meetup?

They all just moved up to the Prince Takanawa library. the "Prince" room was getting too loud. On Fri, Oct 30, 2015 at 10:38 AM, Balaji Narayanan (பாலாஜி நாராயணன்) < li...@balajin.net> wrote: > Hello Erik /Edgar, > > We are in the Prince room in building #44, closer to the projector screen. > > -

Re: [Openstack-operators] Informal Ops Meetup?

Near the projection screen @piet we've got three tables conjoined On Fri, Oct 30, 2015 at 10:26 AM, Dina Belova wrote: > Kruithof, > > Grand Prince Hotel Takanawa, B1F layer - big room with lots of round > tables. > > Cheers, > Dina > > On Fri, Oct 30, 2015 at 10:18 AM, Kruithof, Piet < > pieter

Re: [Openstack-operators] [openstack-operators] OSOps we have a room in Toyko!

Great Idea Lauren as all these things are blurring together in my mind. On Tue, Oct 20, 2015 at 2:47 PM, Lauren Sell wrote: > Done :) > > Would you like to add any further description about the project / team and > who should attend in sched, for those who may not be familiar? > > > > On Oct 20

Re: [Openstack-operators] Migrating an instance to a host with less cores fails

As Kris Lindgren noted, this has bit us big time. Defaults appear wrong, desired behavior would be other than it is. I'm re-reading this entire thread now (sorry for not weighing in earlier.) On Fri, May 15, 2015 at 12:52 PM, Aubrey Wells wrote: > Greetings, > Trying to decide if this is a bug o

Re: [Openstack-operators] [tags] ease of upgrade

Sure, I can take a pass at this. On Tue, Sep 15, 2015 at 2:11 AM, Tom Fifield wrote: > Hi all, > > One of our long mooted tags has been something that captures the ease of > upgrade for a service. > > We've got a lot of inherit knowledge about this stuff that would be great > to capture, for exa

Re: [Openstack-operators] Rate limit an max_count

Your users should also have reasonable quotas set. If they can boot thousands of instances, you may have a quota issue to address. (No problem with the blueprint or need to set an overall limit though--just that you should be able to address this without waiting for that to land.) On Mon, Sep 7, 2

  1   2   >