Re: [Openstack-operators] Openstack and Ceph

Another question is what type of SSD's are you using. There is a big difference between not just vendors of SSD's but the size of them as their internals make a big difference on how the OS interacts with them. This link is still very usage today: https://www.sebastien-han.fr/blog/2014/10/10/ceph

Re: [Openstack-operators] Reserve an external network for 1 tenant

I believe you can actually do this in Liberty.. http://docs.openstack.org/liberty/networking-guide/adv-config-network-rbac.html On Mon, Oct 3, 2016 at 1:00 AM, Kevin Benton wrote: > You will need mitaka to get an external network that is only available to > specific tenants. That is what the

Re: [Openstack-operators] MongoDB as Ceilometer backend - scaling

I think many people tried to run ceilometer with multiple different backends and for a while were truly unsuccessful. If you look at Liberty and now in Mitaka there has been a lot of work to separate out the alarms from the actual data parts. You now have Adoh from the alarming standpoint, and th

Re: [Openstack-operators] [Interop-Challenge]Please review the work load test scripts

It has been merged. On Thu, Sep 15, 2016 at 9:44 AM, Tong Li wrote: > Dear openstack/osop-tools-contrib core reviewers, please review the > following patch which provides ansible and terraform work load tests for > Interop-challenge effort. > > *https://review.openstack.org/#/c/366784/* >

Re: [Openstack-operators] Generate list of default configuration parameters

I'm not sure if this fits what you need, but the Kolla project produces a lot of default values that are included in their deployments. You could check that out and see if it works for you. On Wed, Sep 7, 2016 at 6:51 PM, Graeme Gillies wrote: > On 08/09/16 05:41, Dan Trainor wrote: > > Hi - >

Re: [Openstack-operators] Database cleanup scripts?

I took a look at the scripts that the CERN folks built and modified these for my specific use case.. Here is the repo: https://github.com/cernops/nova-db-purge Joe On Fri, Sep 2, 2016 at 1:57 PM, Edmund Rhudy (BLOOMBERG/ 120 PARK) < erh...@bloomberg.net> wrote: > Great post, thanks. nova is my

Re: [Openstack-operators] [OpenStack-DefCore] [OSOps] Ansible work load test for interop patch set

ybrid cloud. Or they may want to ensure > that two of their own private clouds are interop compatible. > > > > ___ > > Kris Lindgren > > Senior Linux Systems Engineer > > GoDaddy > > > >

Re: [Openstack-operators] [OpenStack-DefCore] [OSOps] Ansible work load test for interop patch set

ated, > that would be a good place for us to ask questions. Thanks! > > Catherine Diep > RefStack Project PTL > IBM > - Forwarded by Catherine Cuong Diep/San Jose/IBM on 08/31/2016 01:25 > PM - > > From: "Kris G. Lindgren" > To: Joseph Bajin , "

Re: [Openstack-operators] OpenStack-DefCore] [OSOps]work load test for docker swarm fix patch

HI there, That patch was merged earlier today.. The patch was rebased at 2pm EST. IT was reviewed earlier this morning again, and then +1 on the 25th of August. You should be good to go. If you do have any questions like this the OSOps Working Group is out there to help as well. We had anothe

Re: [Openstack-operators] [OpenStack-DefCore] [OSOps] Ansible work load test for interop patch set

atch? > https://review.openstack.org/#/c/351799/ > > The patchset was last updated Aug 11th. > Thanks! > > > > On Tue, Aug 16, 2016 at 7:17 PM, Joseph Bajin > wrote: > >> Sorry about that. I've been a little busy as of late, and was able to get >> around to taking a

Re: [Openstack-operators] [OSOps] [OpenStack-DefCore] Ansible work load test for interop patch set

t at least. > +1 > > I had contacted JJ earlier and he told me that the best person to contact > would be Joseph Bajin (RaginBajin in IRC). I've also added an OSOps tag to > this message. > > > > -Christopher > > > >> On Tue, Aug 16, 2016 at 7:59 AM, Tong

Re: [Openstack-operators] (no subject)

We let our people access the Glance API. Glance uses Keystone, so user authentication is done the same way all the other services are done within OpenStack. We allow the glance api ports to be available to them so they can use the service. What are you thinking that would prevent you from offeri

Re: [Openstack-operators] [OSOps] Bi-Weekly Meeting - This coming Wednesday 7/20/2016

Hello, I'm going to have to cancel this week's OSOps meeting set for this today, unless someone volunteers to run the meeting. If not, then the next meeting is set for August 3rd, 2016 with the same agenda. --Joe On Mon, Jul 18, 2016 at 7:41 PM, Joseph Bajin wrote: > Ever

[Openstack-operators] [OSOps] Bi-Weekly Meeting - This coming Wednesday 7/20/2016

Everyone, The agenda is up for this week's OSOps meeting. You can find the agenda here: https://etherpad.openstack.org/p/osops-irc-meeting-20160720 I hope to have some ideas on how OSOps can help and how we can get more people to participate. The meeting will start at 1900 UTC in #openstack-me

Re: [Openstack-operators] Bandwidth limitations

Hi there, It looks like QOS is already available within the Mitaka release. Maybe it doesn't have all the features you need, but looks to be a good start. http://docs.openstack.org/mitaka/networking-guide/adv-config-qos.html I haven't used it yet, but maybe someone else will pipe up with some e

Re: [Openstack-operators] [osops] OSOps meeting today in #openstack-meeting-4 1900 UTC

Jun 1, 2016 at 8:44 AM, Joseph Bajin wrote: > Operators, > > Our bi-weekly meeting is today in the #openstack-meeting-4 room beginning > at 1900 UTC. > > There isn't much on the agenda today, as we haven't gotten a lot of > participation or volunteering. You can re

[Openstack-operators] [osops] OSOps meeting today in #openstack-meeting-4 1900 UTC

Operators, Our bi-weekly meeting is today in the #openstack-meeting-4 room beginning at 1900 UTC. There isn't much on the agenda today, as we haven't gotten a lot of participation or volunteering. You can review the agenda here. [1] If you have anything that you think the Operators community

Re: [Openstack-operators] Fwd: [openstack-dev] [nova] I'm going to expire open bug reports older than 18 months.

All the different projects have different ways of reporting bugs and looking for features. You can see a few of the different ways that the Operators discussed back at the Summit here - https://etherpad.openstack.org/p/AUS-ops-Requests-for-Enhancement-Process That should give you some more contex

Re: [Openstack-operators] VPNaaS and FWaaS

We have actually started to look at VPNaaS as a way to tie two different region's Tenant Networks together.. This will hopefully allow us to not have to look at users using too many Floating IPs to just support tools and products that have issues with Floating IPs. On Tue, May 10, 2016 at 4:18 AM

[Openstack-operators] [osops] OSOps Meeting - Wednesday 1900UTC #openstack-meeting-4

Everyone, Our next OSops group meeting will be help this coming Wednesday at 1900 UTC in the #openstack-meeting-4 IRC room. I've posted our agenda for this week: https://etherpad.openstack.org/p/osops-irc-meeting-20160518 Thanks Joe ___ OpenStack-op

[Openstack-operators] Gathering Actions from the Informal Operators Meetup

Everyone, The OSOps team would like to get help from the Operator Community to help gather issues and problems from the informal Operators meetup.[1] Here is the etherpad that we have setup.[2] We are asking users to take a look at the etherpad[1] and if they identify issues that should be raised

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

There is also a golang library that can validate tokens.. http://gophercloud.io/docs/identity/v3/ On Thu, May 12, 2016 at 11:25 PM, David Medberry wrote: > There's a jython implementation of keystone and I thought there was other > work to validate tokens from within Java. Added Jim Baker to

Re: [Openstack-operators] Moving from distro packages to containers (or virtualenvs...)

On Thu, May 12, 2016 at 5:04 PM, Joshua Harlow wrote: > Hi there all-ye-operators, > > I am investigating how to help move godaddy from rpms to a container-like > solution (virtualenvs, lxc, or docker...) and a set of questions that comes > up is the following (and I would think that some folks o

[Openstack-operators] Need Operators thoughts and opinions on NOVA specs! Get your opinions heard!

Operators, The Nova team has requested feedback from the community and especially the operators on two specs that they are reviewing. The first spec is regarding some logging changes to the scheduler: - Mailing List: http://lists.openstack.org/pipermail/openstack-operators/2016-May/010322.html

[Openstack-operators] [osops] OSOps Meeting - Tomorrow 2016-05-04 1900 UTC

Everyone, The OSOps group will be having their next meeting tomorrow May 4th, 2016 at 1900 UTC. It will be hosted in the #openstack-meeting-4 room. The agenda has been added to the etherpad and wiki. You can find that here. [1] The primary goal is to follow-up on the discussions that we had at

[Openstack-operators] [osops] OSOps Meeting Notes from Summit

Hello Operators, I wanted to provide some updates to the OSOps Operators Meeting that was held last week. You can find the etherpad located here. [1] The highlights of the meeting were the following: - People see OSOps as an advocation group for patches, tools, and features that operators need

[Openstack-operators] [osops] Requests for Enhancement Process Meeting Notes

Hello Operators, I wanted to provide some updates to the Requests for Enhancement Process Operators Meeting that was held last week. You can find the etherpad located here. [1] The highlights of the meeting were the following: - RFE's should be groomed by the Operators first before being sent o

Re: [Openstack-operators] Maintenance

ool > repository. > > Tim > > From: Joseph Bajin > Date: Friday 22 April 2016 at 17:55 > To: Robert Starmer > Cc: openstack-operators > Subject: Re: [Openstack-operators] Maintenance > > Rob/Jay, > > The use of the OSOps Working group and its repos is a grea

Re: [Openstack-operators] Maintenance

Rob/Jay, The use of the OSOps Working group and its repos is a great way to address this.. If any of you are coming to the Summit, please take a look at our Etherpad that we have created.[1] This could be a great discussion topic for the working sessions and we can brainstorm how we could help w

[Openstack-operators] [osops] OSOps Summit Etherpad is up!

Operators, The OSOPs Summit etherpad is up and running. You can find this etherpad located here. [1] For those that are not aware of OSOps, it stands for OpenStack Operators. Currently, we maintain the operators focused github repositories as well as working with other projects to help address th

[Openstack-operators] [osops] No Meeting this week..

OSOps, I'm thinking it may be good to cancel this week's OSOps meeting and just meet during the summit. We have 3 sessions that surround the topics that we have been talking about and I hope we can get some more topics as well as participation next week. Here are the details for the sessions at

Re: [Openstack-operators] [Neutron] Operator Pain Points

Hi Carl, This is great.. We also have two sessions going on for Operators in hopes to determine the best methods for gathering these types of requirements. This is to help Operators get them to the right people as well as ways for the Operators to track these for follow-up. The two sessions we

Re: [Openstack-operators] Configure cinder to allow volume delete when RBD snapshots present

You could make a backup of the snapshot and then transfer it to a different tenant In the event that you need to restore it, you could transfer it back to the user. I think you could do this in an automatic fashion as well, but you'll have to do some testing though to make sure it does what you n

Re: [Openstack-operators] [osops] Finding ways to get operator issues to projects - Starting with NOVA

Sean, I think this is exactly what I think we are looking to change. There is a lot of work that is captured via etherpad's at each of the Midcycle and other meetups that is probably not sent up to each of the groups. The reason I think this is because I see the some of the same issues that Oper

Re: [Openstack-operators] [osops] Finding ways to get operator issues to projects - Starting with NOVA

t; [1]https://wiki.openstack.org/wiki/ProductTeam > [2]https://github.com/openstack/openstack-user-stories > [3]http://lists.openstack.org/cgi-bin/mailman/listinfo/product-wg > > On Tue, Apr 5, 2016 at 12:29 PM, Joseph Bajin > wrote: > >> Hi Christoph, >> >> This is a g

Re: [Openstack-operators] [osops] Finding ways to get operator issues to projects - Starting with NOVA

ess, we (me) are keen > to engage and help, > > Let us know if anyone else is on the same level working on things, > > c > > > Christoph Andreas Torlinski > > +44(0)7872413856 UK Mobile > > christ...@nuagenetworks.net > > On 26 March 2016 at 20:47, Joseph B

Re: [Openstack-operators] [osops] Finding ways to get operator issues to projects - Starting with NOVA

Just sending this out to the Operator Community for more feedback. We'll be having a session at the summit about it, but I'd like to get this discussion going a little more here if we could. --Joe On Sat, Mar 26, 2016 at 4:47 PM, Joseph Bajin wrote: > Operators, > > At t

Re: [Openstack-operators] [neutron] Attach routing rules to networks?

We use the host-route flag as mentioned above. It makes it easy to sent internet like traffic to a gateway type of box and internal traffic to the inside for tenants that do have public access. On Sat, Apr 2, 2016 at 10:33 PM, James Denton wrote: > Hi Mike, > > You should be able to update the

Re: [Openstack-operators] [nova] Removing seeded flavors

While I think it's fine to remove this from the normal setup, I think there should be either a file or process that one could run to add these basic flavors. I think without you will have things such as DevStack and other beginners not being able to get up and going. I think having the migration

[Openstack-operators] [osops] Finding ways to get operator issues to projects - Starting with NOVA

Operators, At the last OSOps Tools and Monitoring meeting, we had mriedem (Nova Team) talk with us about a proposal that they are working on. The Nova team would like to abandon the use of a wish-list as it has grown to an unmanageable size. They have posted a few times to both the operators list

[Openstack-operators] [osops] OSOps Tools and Monitoring Meeting - Wendesday 1900 UTC

Operators, We will be having our bi-weekly meeting in the #openstack-meeting-4 room at 1900UTC. I have published the current agenda for this meeting. You can find that here: https://etherpad.openstack.org/p/osops-irc-meeting-20160323 Either let me know or please go ahead and add to the ether

Re: [Openstack-operators] Liberty neutron issues

Your entire configuration for VLAN, VXLAN, etc should be done within the ml2 configuration and not really through ovs. All OVS needs to know about are the bridges that you setup and what they are called and going to be used for. Any specific configurations will happen on the system side and not t

[Openstack-operators] [Tools/Monitoring] Meeting Notes from Operators Tools and Monitoring Working Group

Operators, The Operators Tools and Monitoring Working Group met at its new time 1900 UTC today. Meeting notes can be found here: * https://etherpad.openstack.org/p/ops-tools-monitoring-agenda-20150923 We also have a wiki page that we are updating which can be found here: * https://wiki.

[Openstack-operators] [Tools/Monitoring] New Time submitted and approved

Everyone, Based on the feedback I did receive, we have moved the Operators Tools and Monitoring Working Group to a later time in the day to accommodate as many different timezones as we could. Meetings will be held at 3pm (15:00) EST on odd Wednesday's starting this Wednesday 9/23/2015 in the IRC

Re: [Openstack-operators] [Swift] deploying behind apache?

We don't deploy swift behind apache, but instead we are using NGINX in this particular case. The only reason we went with NGINX was it allowed us to control turning up and down particular services which apache couldn't do. One day we will move back to apache when we move swift into containers. Th

Re: [Openstack-operators] [OpenStack][Operators] Follow-up on Mid-cycle discussion on RPC Compatibility

We recently just upgraded to Juno from Icehouse. We used the upgrade_levels feature to get Nova off the ground, but ran into major issues around conductor being too slow to respond to messages and would cause a lot of our instances to not create. This would only happen at a particular high amount

[Openstack-operators] [Tools/Monitoring] Finding a new Tools and Monitoring Working group Time

Hi Everyone, One of the items taken from the Operators Meet-up was that the time (10am EST) was too early for the west coast people. I've been looking at the meeting calendar and have a few suggested times that I'd like to see if they would work for others to get more participation. Odd every o

[Openstack-operators] [Ops Tools/Monitoring] Next Meeting - 7/29/15 - 10AM EST

Operators, The next meeting of the Operator Tools and Monitoring working group is set for 7/29/15 (Wed.) at 10AM EST. We hold the meeting on IRC in the #openstack-meeting-4 room. You can see the logs from our previous meeting here: http://eavesdrop.openstack.org/meetings/operators_ops_tools_mon

Re: [Openstack-operators] Scaling the Ops Meetup

I agree with all of these items especially with not having Vendor booths. The only thing I would want to mention is that it would be great to have something centrally located within the US, if we are going to choose the US for a session. That way it is only a 3-4 hour flight instead of a 7-9 hour

Re: [Openstack-operators] OpenSource ELK configurations

I think those from the Infra Project are a great start, but I do think they are missing a lot. Instead of breaking down the message into parts, it just breaks down the type (INFO, DEBUG, etc) and then makes the rest of the message greedy. That doesn't help searching or graphing or anything like th

[Openstack-operators] Customer Onboarding/Off-Boarding Session

Hi, We didn't have a lot of people attend this session (most likely because it was schedule at 5:30 so many probably went off to dinner), but those that did attend provided great input. Coverage of the session can be found at this etherpad: https://etherpad.openstack.org/p/YVR-ops-customer-onboa

[Openstack-operators] [CMDB] CMDB Vancouver Working Group

Hi, I wanted to provide a recap of the CMDB working group from the Summit. There was good attendance with people that had a great amount of experience working and building a CMDB. While it may seem easy on the surface, it actually is a pretty big project with a lot of different options and theor

[Openstack-operators] Vancouver Summit - Customer On-boarding/Off-boarding

Hi, I will be moderating the Customer On-Boarding/Off-Boarding[1] session at the summit, and wanted to make sure we get as much feedback into the etherpad[2] as possible. Both adding and removing users seems like a pretty simple idea, but it gets complicated pretty quickly. So any suggestions, re

Re: [Openstack-operators] Modification in nova policy file

The Policy file is not a filtering agent. It basically just provides ACL type of abilities. "Can you do this action? True/False" "Do you have the right permissions to call this action? True/False" If you wanted to pull back just the instances that the user owns, then you would actually have to

Re: [Openstack-operators] expanding to 2nd location

Just to add in my $0.02, we run in multiple sites as well. We are using regions to do this. Cells at this point have a lot going for it, but we thought it wasn't there yet. We also don't have the necessary resources to make our own changes to it like a few other places do. With that, we said th

Re: [Openstack-operators] CMDB

Hi Tom, If you don't get anyone to sign-up for it, and it doesn't conflict with the "On-Boarding" session, I'm willing to do it. I have some interest in it and curious to know what others are doing. --Joe On Wed, May 6, 2015 at 6:04 AM, Tom Fifield wrote: > Hi, > > Is anyone interested enough

[Openstack-operators] Operator Help to get patch merged

I wanted to see about getting some Operator Help to push through a patch[1]. The patch is to not give the user a 404 message back when they click the cancel button why trying to change their password or the user settings. The patch resets the page. It's been sitting there for a while, but started

Re: [Openstack-operators] MTU on router interface (neutron & GRE) without jumbo

The size of MTU only really matters for the server and client. The between connections need to be larger than the packets that are being sent. Scenario 1: Server - 1400 MTU Client - 1400 MTU Switches - 9216 MTU OVS - 1500 MTU Result: Successful - Traffic passes without any issue Scenario 2:

Re: [Openstack-operators] Storage error

You do have to create something for cinder to have as a backend. That could be an LVM volume on a particular node, or it could be a CEPH setup, that's up to your requirements. Also, you didn't state the error that you are getting when you try to create a cinder volume. That would certainly help

Re: [Openstack-operators] Draft agenda for PHL Ops Meetup (9-10 March)

I agree. This looks really good, and I like the working lunch. I'm excited to meet everyone and hear all the different topics. Some of them like the monitoring and large deployments are happening at the same time, so I'll need to figure out how to be in two places at the same time. On Sat, Feb