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

On Wed, Nov 18, 2015 at 03:44:03PM -0500, Erik McCormick wrote: :I'm still fishing for more specific details, but here is a snapshot of :how the Ceph Development Summit is handled. : :http://tracker.ceph.com/projects/ceph/wiki/CDS_Jewel : :It was previously done via Google Hangouts, but is now

[Openstack-operators] Ops meetup: Ops Guide Working session.

;tldr Help fix the OPs Guide Monday 11:15am - 11:55am Hilton Austin MR 406 etherpad: https://etherpad.openstack.org/p/AUS-ops-Docs-ops-guide OpenStack operation have grown a lot since the Operations Guide was first written (and even since it's last major revision) both because OpenStack as a

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

On Wed, May 11, 2016 at 07:30:45PM -0400, Emilien Macchi wrote: :On Tue, May 3, 2016 at 11:43 AM, Matt Riedemann : wrote: :> Another thought is that deployment tools are just copying what devstack :> does, or what shows up in the configs in our dsvm gate jobs, and

Re: [Openstack-operators] PCI Passthrough issues

On Tue, Jul 26, 2016 at 05:09:21PM +1000, Blair Bethwaite wrote: :Next question - has anyone figured out how to make GPU P2P work? We :haven't tried very hard yet, but with our current setup we're telling :Nova to pass through the GK210GL "3D controller" and that results in :the guest seeing

[Openstack-operators] Blazar? (Reservations and/or scheduled termination)

Hi All, As a private cloud operatior who doesn't charge internal users, I'd really like a way to force users to set an exiration time on their instances so if they forget about them they go away. I'd though Blazar was the thing to look at and Chameleoncloud.org seems to be using it (any of you

Re: [Openstack-operators] Blazar? (Reservations and/or scheduled termination)

involved with Scientific Working Group (at least enough to follow the ongoing discussions) Thanks, -Jon : :Tim : : :On 03/08/16 18:47, "Jonathan D. Proulx" <j...@csail.mit.edu> wrote: : :Hi All, : :As a private cloud operatior who doesn't charge internal users, I'd :r

[Openstack-operators] PCI Passthrough issues

Hi All, Trying to spass through some Nvidia K80 GPUs to soem instance and have gotten to the place where Nova seems to be doing the right thing gpu instances scheduled on the 1 gpu hypervisor I have and for inside the VM I see: root@gpu-x1:~# lspci | grep -i k80 00:06.0 3D controller: NVIDIA

Re: [Openstack-operators] PCI Passthrough issues

Jon, : :Do you have the nouveau driver/module loaded in the host by any :chance? If so, blacklist, reboot, repeat. : :Whilst we're talking about this. Has anyone had any luck doing this :with hosts having a PCI-e switch across multiple GPUs? : :Cheers, : :On 6 July 2016 at 23:27, Jonathan D. Proulx

Re: [Openstack-operators] [openstack-community] User Survey - Deadline Feb 20th

On Thu, Feb 02, 2017 at 04:12:25PM +, Neil Jerram wrote: :I notice that at the end of the survey, when I click on the "SUBMIT YOUR :SURVEY >" button, I just get the same page again, and so could click :"SUBMIT YOUR SURVEY >" again, and so on... : :You might want to look at fixing that; and in

Re: [Openstack-operators] Shelving

On Fri, Aug 19, 2016 at 06:48:12AM +1000, Michael Still wrote: :Shelved instances still consume IPs and hypervisor disk IIRC, so they're :not free for nova. So, there has to be some form of accounting of shelved :instances to stop resource exhaustion, especially in the IP space. : :I'm not opposed

Re: [Openstack-operators] Shelving

On Thu, Aug 18, 2016 at 03:24:28PM +, Tim Bell wrote: : :We’re having a look at VM shelving for the CERN community and struggling to find a motivation for a private cloud user to shelve their instances (and free up resources they may be only using infrequently). : :The problem is that

Re: [Openstack-operators] [Puppet][Neutron] Mitaka ML2/OVS config file mismatch

the stable/mitaka branch and see the commit in my working checkout. I hammered a kludge into place in my test env and when on to try and solve other issues, but I'll circle back and look more closely. Thanks, -Jon : :Thank you : :Saverio : : : :2016-09-01 16:32 GMT+02:00 Jonathan D. Proulx &l

Re: [Openstack-operators] Delete cinder service

On Thu, Sep 01, 2016 at 04:25:25PM +0300, Vladimir Prokofev wrote: :I've used direct database update to achive this in Mitaka: :use cinder; :update services set deleted = '1' where ; I belive the official way is: cinder-manage service remove Which probably more or less does the same thing...

Re: [Openstack-operators] [Puppet][Neutron] Mitaka ML2/OVS config file mismatch

On Thu, Sep 01, 2016 at 01:50:40PM +0200, Ihar Hrachyshka wrote: :ml2_conf.ini is to be loaded by neutron-server only. The agent should :not load it, instead relying on openvswitch_agent.ini file for :anything agent specific. If for some reason puppet does put agent :configuration options into

Re: [Openstack-operators] Converged infrastructure

On Wed, Aug 31, 2016 at 01:01:56PM +0100, Matt Jarvis wrote: : Like a lot of others we run Ceph, and we absolutely don't converge our : storage and compute nodes for a variety of performance and management : related reasons. In our experience, the hardware and tuning : characteristics of

[Openstack-operators] [Puppet][Neutron] Mitaka ML2/OVS config file mismatch

Hi All, I'm woking on testing my jump from Kilo->Mitaka Using puppet on ubuntu 14.04 with cloud archive packages. Puppet seems to be writing the ml2/ovs configs into /etc/neutron/plugins/ml2/ml2_conf.ini which is where the previously were, so I've spent a few day going around on this thinking

[Openstack-operators] [Nova] instance snapshot failure on mitaka

Hi All, In my continuing sporadic testing of Kilo->Mitaka upgrade I've run into an issue with Snapshotting instances. I'm seeing this Failure on the hypervisor: 2016-09-12 14:14:26.303 24723 ERROR oslo_messaging.rpc.dispatcher libvirtError: internal error: unable to execute QEMU command

Re: [Openstack-operators] Openstack team size vs's deployment size

I agree this would make a very interesting OPs session. As many have poitned out it's difficult to really quantify in a comparable way given the range of roles and approches. We have 1 region (going on 2) with 100 hypervisors providing a basic IaaS service (agian looking to expand into various

Re: [Openstack-operators] Openstack team size vs's deployment size

On Mon, Sep 12, 2016 at 03:26:02PM -0700, Clint Byrum wrote: :Excerpts from Mathieu Gagné's message of 2016-09-12 17:55:34 -0400: :> I also think that small team with small deployments has little :> incentive to invest in *heavy* automation (to help themselves) and/or :> tools to delegate its

Re: [Openstack-operators] ML2/OVS odd GRE brokenness

On Tue, Nov 08, 2016 at 06:27:34PM -0500, George Mihaiescu wrote: :Hi Jonathan, : :The openvswitch-agent is out of sync on compute 4, try restarting it. Nope. Restarted the agent on 4 and when that failed also on 1 they still can't talk. I had previously migrated 4 to a new host to test that

Re: [Openstack-operators] ML2/OVS odd GRE brokenness

Also I have restarted openvswitch-agent on both sides of the broken link and it made no difference... On Tue, Nov 08, 2016 at 05:43:27PM -0500, Jonathan Proulx wrote: : :I have an odd issue that seems to just be affecting one private :network for one tenant, though I saw a similar thing on a

Re: [Openstack-operators] ML2/OVS odd GRE brokenness

AM, Jonathan D. Proulx <j...@csail.mit.edu> wrote: :> :> :> Also I have restarted openvswitch-agent on both sides of the broken :> link and it made no difference... :> :> On Tue, Nov 08, 2016 at 05:43:27PM -0500, Jonathan Proulx wrote: :> : :> :I have an odd issue

Re: [Openstack-operators] [tags]Summit session to discuss about maturity of heat

I'll try and make it. OpsTags a miniscule number of actuve participants (like maybe one and it's not me, but I have been more active in the past so might be of some use) so I'll conter propose attending: Ops: Ops Tags Team Tue 25 5:05pm-5:45pm AC Hotel - P3 - Montjuic

Re: [Openstack-operators] How do you even test for that?

On Mon, Oct 17, 2016 at 05:45:07PM -0600, Matt Fischer wrote: :This does not cover all your issues but after seeing mysql bugs between I :and J and also J to K we now export and restore production control plane :data into a dev environment to test the upgrades. If we have issues we :destroy this

[Openstack-operators] PCI passthrough trying to use busy resource?

Hi all, I have a test GPU system that seemed to be working properly under Kilo running 1 and 2 GPU instnace types on an 8GPU server. After Mitaka upgrade it seems to alway try and assing the same Device which is alredy in use rather than pick one of the 5 currently available. Build of

Re: [Openstack-operators] Setting default MTU for project networks?

On Sun, Nov 20, 2016 at 02:59:14AM -0800, Kevin Benton wrote: :Sorry about the delay, a couple of questions. No worries "working" was the important bit (which I got). Working correctly, well we can take our time :) :You're not setting network_device_mtu, right? no though maybe I should read

Re: [Openstack-operators] Disable console for an instance

On Thu, Oct 27, 2016 at 04:08:26PM +0200, Blair Bethwaite wrote: :On 27 October 2016 at 16:02, Jonathan D. Proulx <j...@csail.mit.edu> wrote: :> don't put a getty on the TTY :) : :Do you know how to do that with Windows? ...you can see the desire for :sandboxing now :-). Sigh yes I

Re: [Openstack-operators] Disable console for an instance

On Thu, Oct 27, 2016 at 02:27:48PM +0200, Blair Bethwaite wrote: : Looks like this is not currently possible. Does anyone else have an : interest in such a feature? : I'm thinking about it from the perspective of a public cloud user who : wants to build highly secure / sandboxed instances.

Re: [Openstack-operators] Disable console for an instance

That is an interesting angle. There *should* be a way to limit vnc acces to just the owner via RBAC. If you trust everything else to be setup right that's probbaly sufficient. Putting on my paranoid security hat, I wouldn't trust that. VNC access at least is completely unsecured at the

Re: [Openstack-operators] Question about ancient published OPS and Architecture guides

I always use the HTML versions and can't think of a case where I'd want the epub or mobi. If they are also out dated I definitly think they should be removed just to prevent confusion. If there's a wider desire for these formats (which I doubt) then they'd need to be published much more

Re: [Openstack-operators] Dealing with ITAR in OpenStack private clouds

On Tue, Mar 21, 2017 at 09:03:36PM -0400, Davanum Srinivas wrote: :Oops, Hit send before i finished : :https://info.massopencloud.org/wp-content/uploads/2016/03/Workshop-Resource-Federation-in-a-Multi-Landlord-Cloud.pdf :https://git.openstack.org/cgit/openstack/mixmatch : :Essentially you can do a

Re: [Openstack-operators] Flavors

I have always hated flavors and so do many of my users. On Wed, Mar 15, 2017 at 03:22:48PM -0700, James Downs wrote: :On Wed, Mar 15, 2017 at 10:10:00PM +, Fox, Kevin M wrote: :> I think the really short answer is something like: It greatly simplifies scheduling and billing. : :The real

[Openstack-operators] LTS Dreaming ... [was] Help: Liberty installation guide (English).

Riding the LTS tangent train ... On Tue, Apr 11, 2017 at 03:40:20PM +, Kevin Bringard (kevinbri) wrote: :Chasing trunk just isn’t feasible for larger organizations, and as Edgar mentioned, updating the code every 6 months (or even a year) is a really difficult proposition. : :There’s a

Re: [Openstack-operators] LTS Dreaming ... [was] Help: Liberty installation guide (English).

it's the Distros (and perhaps some larger users?) -Jon :Edgar : :On 4/11/17, 8:50 AM, "Jonathan D. Proulx" <j...@csail.mit.edu> wrote: : : :Riding the LTS tangent train ... : :On Tue, Apr 11, 2017 at 03:40:20PM +, Kevin Bringard (kevinbri) wrote: : ::Ch

Re: [Openstack-operators] LTS Dreaming ... [was] Help: Liberty installation guide (English).

On Tue, Apr 11, 2017 at 06:01:00PM -0500, Matt Riedemann wrote: :Right, but the distros aren't interested in funding developers for LTS :upstream work, much less a lot of the stable branch support upstream. It :shouldn't be surprising why, that's where they can make money. No doubt that's their

Re: [Openstack-operators] usage hours

On Wed, Aug 02, 2017 at 04:56:13PM -0500, Juanjuan Li wrote: :how does OpenStack calculate the vcpu hours, total disk usage hours : : :I created a cirros VM with the flavor of m1.tiny without further operation :on that VM.I created it around 2 hours ago but on the dashboard"Overview", :it shows

Re: [Openstack-operators] community vs founation membership

On Tue, May 22, 2018 at 04:06:43PM +0200, Ignazio Cassano wrote: : Hi Jeremy, thanks for your help. : I am interested in openstack testing (no code contributing). : Becoming community member give me any advantage ? : At this time I am testing on ocata on centos 7. : My environment is in

Re: [Openstack-operators] community vs founation membership

On Tue, May 22, 2018 at 03:12:28PM +, Jeremy Stanley wrote: :On 2018-05-22 08:02:34 -0700 (-0700), Jonathan D. Proulx wrote: :[...] :> Again seeing these reviews is public but writing reviews requires :> foundation memebership in the same way being a code contributor does. :[...] : :I

[Openstack-operators] OSA migrating existing deployment to OSA

Hi All, Having attened Fast Forward upgrade session and Upgrade SIG this morning in Vancouver I'm convinced my upgrade problem is really a config management problem. I'm runnig an old deprecated config system that worked gread in 2012, but has aged poorly. I've been meaning to move to OSA for a

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

Thanks for kicking this off Chris. Were you going to create that new repository? If not I can take on the tasks of learning how and making it happen. -Jon On Wed, May 23, 2018 at 06:38:32PM -0700, Chris Morgan wrote: : Hello Everyone, : In the Ops Community documentation working session

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

On Thu, May 24, 2018 at 07:07:10AM -0700, Doug Hellmann wrote: :I know you wanted to avoid lots of governance overhead, so I want :to just mention that establishing a SIG is meant to be a painless :and light-weight way to declare that a group of interested people :exists so that others can find

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

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. My understanding being they don't to have this type of documentention due to much

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

, Jonathan D. Proulx : <[1]j...@csail.mit.edu> wrote: : : On Thu, May 24, 2018 at 07:07:10AM -0700, Doug Hellmann wrote: : :I know you wanted to avoid lots of governance overhead, so I want : :to just mention that establishing a SIG is meant to be a painless : :and light-weig

Re: [Openstack-operators] pci passthrough & numa affinity

nding so being able to say "this is on the road map and could be accelerated with developer hours" is useful. I expect patience is what will come of that but very good to know where to go when I get some clarity and if I get some resources. -Jon : :Thanks, :efried : :On 05/24/2018 05:1

Re: [Openstack-operators] pci passthrough & numa affinity

On Fri, May 25, 2018 at 07:59:16AM +1000, Blair Bethwaite wrote: :Hi Jon, : :Following up to the question you asked during the HPC on OpenStack :panel at the summit yesterday... : :You might have already seen Daniel Berrange's blog on this topic:

[Openstack-operators] [neutron][ovs]Leaking flow?

Hi All, Running Mitaka on Ubuntu 16.04 so perhaps this is an ancient bug, but... I have a project with it's own vlan-provider network that spans their legacy physical hosts and cloud systems (probably not relevant but it is weird). They noticed on of their VMs could over hear one unicast flow

Re: [Openstack-operators] operators get-together today at the Berlin Summit

On Tue, Nov 13, 2018 at 12:57:02PM +0100, Chris Morgan wrote: : We never did come up with a good plan for a separate event for : operators this evening, so I think maybe we should just meet up at the : marketplace mixer, so may I propose meet at the front at 6pm? : Chris : -- : Chris