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. > > Also,

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

Re: [openstack-dev] [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. > > Also,

Re: [openstack-dev] [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, >

Re: [Openstack] [cinder] Pruning Old Volume Backups with Ceph Backend

Hi Chris, Unless I overlooked something, I don't see Cinder or Ceph versions posted. Feel free to just post the codenames but give us some inkling. On Thu, Aug 23, 2018 at 3:26 PM, Chris Martin wrote: > I back up my volumes daily, using incremental backups to minimize > network traffic and

Re: [openstack-dev] PTG Denver Horns

, Aug 8, 2018 at 5:30 AM, Colleen Murphy wrote: > On Wed, Aug 8, 2018, at 12:18 PM, Adam Spiers wrote: > > Matthew Thode wrote: > > >On 18-08-07 23:18:26, David Medberry wrote: > > >> Requests have finally been made (today, August 7, 2018) to end the > horns on >

[openstack-dev] PTG Denver Horns

Requests have finally been made (today, August 7, 2018) to end the horns on the train from Denver to Denver International airport (within the city limits of Denver.) Prior approval had been given to remove the FLAGGERS that were stationed at each crossing intersection. Of particular note (at the

Re: [Openstack] Live migration failed with ceph storage

~]# nova --version > 9.1.2 > > I am using Pike 16.0.15 (My deployment tool is openstack-ansible) > > > What are my option here? > > > On Wed, Jul 25, 2018 at 8:19 AM, David Medberry > wrote: > > It's not clear what version of Nova you are running but perhap

Re: [Openstack] Live migration failed with ceph storage

It's not clear what version of Nova you are running but perhaps it is badly patched. The 16.x.x (Pike) release of Nova has no "migrate_configure_max_speed" but as best I can tell you are running a patched version of Nova Pike so it may be inconsistent. This parameter was introduced on 2017-08-24:

[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

Re: [Openstack] flavor metadata

Bernd has this right. Host aggregates (sometimes called Haggs) is the right soluton to this problem. You can setup a flavor to only run on a certain hagg. This works well (in production, at scale). On Sun, Jul 1, 2018 at 7:52 AM, Satish Patel wrote: > Folks, > > Recently we build openstack

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

[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:

[openstack-dev] 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

Re: [Openstack] [pike] general how to get off the ground questions

Generally recommended to start with a cloud-image and these are available for Centos and RHEL. You can then customize (either via cloud-init which would be the cloud-way or via making a new image from your existing customized instances.) RHEL

Re: [Openstack] nova live migration setup

Best practice is to use shared storage and then the "copy" is really only the active memory. A few changes came about in about the newton? timeframe that allows for some memory convergence. Take a look at the nova release notes from that time forward and you should see reference to the change(s).

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

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

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

Re: [Openstack] [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

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

[Openstack] 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

[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

[openstack-dev] 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

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

On Wed, Dec 13, 2017 at 2:35 PM, Thierry Carrez <thie...@openstack.org> 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 developmen

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

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

[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

[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,

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

Re: [openstack-dev] [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

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

Re: [openstack-dev] [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

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-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.

[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

Re: [Openstack] Ocata Update libvirtd Error

Hi G., I don't have Ocata up anywhere, but as a "best practice", I generally do the: nova reset-state --active $UUID followed immediately by nova reboot --hard to try and "restore/resurrect" errored instances. The reset-state --active doesn't actually do anything to the instance, it just

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

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

Re: [Openstack] Pike NOVA Disable and Live Migrate all instances.

Best practice is to never migrate more than one at a time. Maybe that has been encoded. I.e. no more than one off of a compute at a time and no more than one onto a compute at a time. On Sep 19, 2017 5:37 PM, "Steven D. Searles" wrote: > Hello everyone and thanks in

Re: [openstack-dev] [nova] Queens PTG team photos

Are you sure Dan @get_offmylawn wasn't just photoshopped from one pic to the other? On Mon, Sep 18, 2017 at 10:27 AM, Matt Riedemann wrote: > Here are the links to the Nova team photos from the PTG. > > https://photos.app.goo.gl/JoYZyouzm0J670mH3 > >

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

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

[openstack-dev] openstack/openstackclient vs openstack/python-openstackclient

What's the relationship between openstack/openstackclient and openstack/python-openstackclient (the first appears to depend upon the latter but I can't ken much more than that.) __ OpenStack Development Mailing List (not

Re: [openstack-dev] [nova] Thanks gibi!

and now recommended for Core too, quite the feat of accomplishments (resting on the solid work!) On Fri, Aug 11, 2017 at 1:40 AM, Balazs Gibizer wrote: > On Thu, Aug 10, 2017 at 8:43 PM, Jay Pipes wrote: > >> On 08/10/2017 01:57 PM, Matt

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

Re: [Openstack] Installing iPerf3 on Cirros

Cirros is a MICRO distribution for verifying a cloud works, not for doing performance analysis. There are no "packages" for it as it is not designed to have functionality added to it. You can instead install a complete version of Linux (say, Ubuntu) and then run performance analysis as you would

[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:

Re: [openstack-dev] [Nova] [Cells] Stupid question: Cells v2 & AZs

Thanks all. On Wed, May 24, 2017 at 8:08 AM, Dan Smith wrote: > > Thanks for answering the base question. So, if AZs are implemented with > > haggs, then really, they are truly disjoint from cells (ie, not a subset > > of a cell and not a superset of a cell, just unrelated.)

Re: [openstack-dev] [Nova] [Cells] Stupid question: Cells v2 & AZs

re basically aggregates. > In cells_v2 aggregates are defined in the cell_api, so it will be possible > to have > multiple AVZs per cell and AVZs that spread between different cells. > > Belmiro > > On Wed, May 24, 2017 at 5:14 AM, David Medberry <openst...@medberry.net>

Re: [openstack-dev] [tc][all] Etcd as a base service for ALL OpenStack installations

On Wed, May 24, 2017 at 6:14 AM, Davanum Srinivas wrote: > http://tarballs.openstack.org/etcd/ There are older versions of etcd (3.1.0) in both Debian and Ubuntu. Is that new enough or do we need 3.1.7? As an operator, I'd much prefer to see a packaged version of this

[openstack-dev] [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

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

e, 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 t

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

Re: [openstack-dev] Boston Forum Schedule

Are the three rooms roughly the same size? On Mon, Apr 10, 2017 at 3:35 AM, Tom Fifield wrote: > Hi everyone, > > Thank you for the many excellent topics submitted for our first Forum. We > have updated the topic submission site with the status of each - please > check

Re: [Openstack-operators] Policy Updates

On Thu, Feb 23, 2017 at 3:17 PM, David Medberry <openst...@medberry.net> 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

Re: [Openstack-operators] Policy Updates

t; > > > > > > > In 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. > > > > > >

[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

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

Re: [openstack-dev] [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

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

Re: [openstack-dev] [nova] allow_resize_to_same_host true needed for affinity

hmmm, it says "not for usage questions" so maybe I'll just propose a change to nova/conf/compute.py as supporting affined hosts is a perfectly valid PRODUCTION reason for setting this (above and beyond the single node testing.) On Sat, Jan 28, 2017 at 5:15 PM, David Medber

[openstack-dev] [nova] allow_resize_to_same_host true needed for affinity

Hi, If you allow "affinity" server via the ServerGroupAffinityFilter it looks like you need to set allow_resize_to_same_host to true. Should I add a bit more description that this is needed to the description (reason) in the config file? (Users do need to sometimes resize things that are in an

Re: [Openstack] live migration issue

Does "virsh capabilities" return the same tree on both hosts? On Wed, Jan 25, 2017 at 4:10 AM, fabrice grelaud < fabrice.grel...@u-bordeaux.fr> wrote: > Hi, > > i ‘ve got live migration issue in one direction but not in other. > I deploy openstack with OSA, ubuntu trusty, stable/newton branch,

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

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==yes=no On Wed, Nov 16, 2016 at 5:07 PM, David Medberry <openst...@medberry.net> wrote: > more info here: > http://www.opensta

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 <openst...@medberry.net> 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 Open

[openstack-dev] Ops Lightning Talks

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

[Openstack-operators] Ops Lightning Talks

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

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

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 <openst...@medberry.net> wrote: > From Nathan (on TWC Cloud team): > > Nathan: Th

Re: [Openstack-operators] ElasticSearch on OpenStack

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 <openst...@medberry.net> wrote: > Hey Tim, > We've just started this effort. I'll

Re: [Openstack] Question about VM credentials - newbie

cloud-init and cloud-config is how one can add a password to a cloud image though it is NEVER recommended. See: http://cloudinit.readthedocs.io/en/latest/topics/examples.html and read about users and groups and mkpasswd cloud-init will read this at vm boot time and apply the cloud-config

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

Re: [Openstack] Ubuntu Xenial Options

Exactly. Since Xenial released alongside Xenial, UCA is not required. You will find Newton packages in UCA (if not now in pre-release, at some point closer to release.) On Wed, Aug 24, 2016 at 12:51 PM, Erdősi Péter wrote: > 2016. 08. 24. 17:55 keltezéssel, Kiriakos Krastillis

Re: [Openstack-operators] Shelving

ux Systems Engineer > > GoDaddy > > > > *From: *David Medberry <openst...@medberry.net> > *Date: *Thursday, August 18, 2016 at 3:49 PM > *To: *"Jonathan D. Proulx" <j...@csail.mit.edu> > *Cc: *"openstack-operators@lists.openstack.org" < &g

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

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

ere 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 <openst...@medberry.net> wrote: > Adding the Ops list. > -- Forwarded mes

[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

Re: [Openstack] Disable compute node from accepting new VMs?

nova service-disable $SHORTNAME nova-compute --reason NO_MORE_SCHEDULING_HERE will prevent new VMs from going on but doesn't do anything with existing. On Tue, Aug 2, 2016 at 3:01 PM, Ken D'Ambrosio wrote: > Hi, all. Trying to figure out how to disable a compute node from

[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

Re: [Openstack] Built in security group?

No, I don't think there is a way to "add" a rule that isn't already in your default settings to an instance so that it can reach the metadata server. If users bypass the "default" (presuming you allow default to access the metadata server), they simply won't have that access. On Tue, Jul 12,

Re: [Openstack] Guidance to start contribution

Asaka, The openstack-dev mailing list may be a better place to ask but since you asked here Read this: https://wiki.openstack.org/wiki/How_To_Contribute with special attention to this: https://wiki.openstack.org/wiki/How_To_Contribute#Bug_fixing with these Low Hanging Fruit bugs:

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

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 <openst...@medberry.net> wrote: > Each tenant in our neutron network has their own subnet and each subnet &

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

Re: [Openstack] nova "get-password " returns blank line

Ribeauville < jpribeauvi...@axway.com> wrote: > Hi, > > > > This parameter is set to true in nova.conf . : > > > > *enable_instance_password=true* > > > > > > J.P. > > > > *From:* medbe...@gmail.com [mailto:medbe...@gmail.com] *On Be

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 <mrie...@linux.vnet.ibm.com > wrote: > On 6/15/2016 12:09 PM, David Medberry wrote: > >> So, there is a nova.conf setting: >> >> instance_buil

Re: [Openstack] nova "get-password " returns blank line

It all depends on how you have setup your cloud. Most/many OpenStack clouds DO NOT inject into the instance and the password feature is null and void. Look at: enable_instance_password = *True* (BoolOpt) Enables returning of the instance password by the relevant server API calls such as create,

[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

Re: [Openstack] dumb neutron question

to the neutron router (but I suspect it doesn't really care if your provider net is RFC 1918 or not. On Sat, Jun 4, 2016 at 11:59 AM, David Medberry <openst...@medberry.net> wrote: > Of course, there are almost always two routers on a subnet... (unless it > is the end of the line). Wh

Re: [Openstack] dumb neutron question

Of course, there are almost always two routers on a subnet... (unless it is the end of the line). What makes you think the neutron router has to be at .1? Mine are typically .1 on the VM side (but it is totally fine to use something else) and not .1 on the provider side. On Fri, Jun 3, 2016 at

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

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,

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)

  1   2   3   >