Re: [Openstack-operators] Uptime and SLA's

Really appreciate the feedback. > On Jun 2, 2016, at 6:51 PM, Bak, Ryan M wrote: > > Melvin, > > The Monasca wiki (https://wiki.openstack.org/wiki/Monasca) has a lot of > information on architecture, as well as links to several talks given at > summits over the past couple years. That’s prob

Re: [Openstack-operators] Uptime and SLA's

Thank you for your responses, I appreciate the insight. Dan Daniel Kingshott Cloud Dude (425) 623 4359 - Cell Best Buy Co. Inc. Technology Development Center 1000 Denny Way | 8th Floor | Seattle, WA | 98109 | USA From: "Bak, Ryan M" Date: Thursday, June 2, 2016 at 4:51 PM To: Melvin Hi

Re: [Openstack-operators] problem with DVR in Kilo and floating IPs

Hi, We have seen this kind of behaviour and it was because the qrouter had the following rules : -A neutron-postrouting-bottom -m comment --comment "Perform source NAT on outgoing traffic." -j neutron-l3-agent-snat -A neutron-l3-agent-snat -j neutron-l3-agent-float-snat -A neutron-l3-agent-floa

Re: [Openstack-operators] problem with DVR in Kilo and floating IPs

Hi, We have seen this kind of behaviour and it was because the qrouter had the following rules : -A neutron-postrouting-bottom -m comment --comment "Perform source NAT on outgoing traffic." -j neutron-l3-agent-snat -A neutron-l3-agent-snat -j neutron-l3-agent-float-snat -A neutron-l3-agent-floa

[Openstack-operators] oslo_messaging, rabbit, ssl and mitaka and xenial

Hi all, We’ve been trying out some mitaka packages as well as some Xenial hosts and have been having some issues with rabbit and SSL. If using rabbitMQ 3.6.x on Trusty I can’t get a mitaka host (oslo_messaging 4.6.1, python-amqp 1.4.9) to connect to rabbit over SSL. If I use rabbitMQ 3.6.x on

Re: [Openstack-operators] Uptime and SLA's

Hey Matt, I am looking into Monasca and would like to know your recommendation for resources regarding a) understanding and b) installing the project; especially since there is no install guide on the project wiki. Additionally, can you shed some light on whether this setup would run behind a l

Re: [Openstack-operators] Uptime and SLA's

We do this a few different ways, some of which may meet your needs. For API calls we measure a simple, quick, and impactless call for each service (like heat stack-list) and we monitor East from West and vice versa. The goal here is nothing added to the DBs, so nothing like neutron net-create. The

[Openstack-operators] problem with DVR in Kilo and floating IPs

Hi, Using DVR in Kilo, I've the following issue: - VM1 is in tenant network 1 (fixed IP 10.97.2.4) - VM2 is in tenant network 2 (fixed IP 10.97.0.4) - a router connects both networks - VM1 and VM2 both have floating IPs - I can ping from VM1 to VM2 using fixed / internal IP - I cannot SSH from VM

Re: [Openstack-operators] Ops Meetups Team - Next Meeting Coordinates and News

Hello, I think we need to increase the cap for real operators and not vendors but I have not attended the Ops meetups WG meetings so I do not know all the context about it. BTW. DO we have a place and date for the next mid-cycle one? Edgar On 6/2/16, 1:16 PM, "Melvin Hillsman" wrote: >Apolo

[Openstack-operators] Uptime and SLA's

We¹re currently in the process of writing up an internal SLA for our openstack cloud, I¹d be interested to hear what others have done and what metrics folks are capturing. My initial thoughts are success / fail spawning instances, creating and attaching volumes, API availability and so on. Can an

Re: [Openstack-operators] Ops Meetups Team - Next Meeting Coordinates and News

Apologies, * On a side note, can we decide on a [email-subject-tag] to help filter these in [Openstack-operators] * Suggestion: [ops-meetups-team] For the delay that is since rain and Houston, TX fight a lot and rain is winning these days unfortunately. I was tasked with submitting to the ML a

Re: [Openstack-operators] [User-committee] [recognition] AUC Recognition WG Meeting Today (6/2/16)

+1 :) On 2 June 2016 at 17:40, Edgar Magana wrote: > I love to see the AUC instead of the Non-ATC one!!! Kudos! > > > > Edgar > > > > *From: *Shamail Tahir > *Date: *Thursday, June 2, 2016 at 9:23 AM > *To: *openstack-operators , > user-committee > *Subject: *[Openstack-operators] [recognitio

Re: [Openstack-operators] [recognition] AUC Recognition WG Meeting Today (6/2/16)

I love to see the AUC instead of the Non-ATC one!!! Kudos! Edgar From: Shamail Tahir Date: Thursday, June 2, 2016 at 9:23 AM To: openstack-operators , user-committee Subject: [Openstack-operators] [recognition] AUC Recognition WG Meeting Today (6/2/16) Hi everyone, The AUC (Active User Co

[Openstack-operators] [recognition] AUC Recognition WG Meeting Today (6/2/16)

Hi everyone, The AUC (Active User Contributor) Recognition WG will be meeting today and the agenda has been posted on our wiki[1]. Meeting information: Date: 6/2 Time: 1900 UTC IRC Channel: #openstack-meeting-3 [1] *https://wiki.openstack.org/wiki/AUCRecognition#Meeting_Information

Re: [Openstack-operators] Collecting our wiki use cases

Thanks to everyone who helped collecting wiki use cases on that etherpad. I tried to categorize the various use cases and I think they fit in 4 categories: 1/ Things that are already in the process of being moved to reference websites or documentation That would be the main "portal" page wi

Re: [Openstack-operators] Nova 2.1 and user permissions in the policy file

On 05/23/2016 10:24 AM, Tim Bell wrote: > > > Quick warning for those who are dependent on the "user_id:%(user_id)s" > syntax for limiting actions by user. According to > https://bugs.launchpad.net/nova/+bug/1539351, this behavior was > apparently not intended according to the bug report feedba