Re: [Openstack-operators] :document an OpenStack production environment

We using chef to manage hosts. Data bags contains all data of all hosts. We keep hardware configuration and DC-wide-name in databags too. For the flowcharts we mostly use markers and whiteboard, sometime I sketch stuff in dia [1] or with wacom tablet in mypaint. [1] http://sourceforge.net/pro

[Openstack-operators] How to allow users to list services by modifying the policy.json file of Keystone

Hello. We have an user 'user1' in the tenant 'tenant1' with the assigned role '_member_'. We want to be able to list services with this user. In the default policy.json files we can find the following rules: "admin_required": "role:admin or is_admin:1", "identity:list_services": "rule:admin_requ

Re: [Openstack-operators] :document an OpenStack production environment

I really liked using sphinx for documentation back in the day, it has the benefit of being community compatible. I also enjoyed graphviz integration in sphinx for diagrams... and then there was templating gnuplots but i think I was probably considered a masochist on this front. at the very l

Re: [Openstack-operators] :document an OpenStack production environment

In my earlier days I had tried many formal schemes, but it always cause problems. For now I settle to following scheme: machine-used database (dns, chef, etc) for explit details like mac addresses, hardware, rack location, network communication. That database should be constantly used, not 'w

Re: [Openstack-operators] How to allow users to list services by modifying the policy.json file of Keystone

Is there any reason that the user can¹t just run keystone catalog which does not require admin permissions? On 1/26/15, 4:58 AM, "Christian Berendt" wrote: >Hello. > >We have an user 'user1' in the tenant 'tenant1' with the assigned role >'_member_'. > >We want to be able to list services with t

Re: [Openstack-operators] :document an OpenStack production environment

i wish hp would open source their cmdb code... that stuff was pretty neat. On Mon, Jan 26, 2015 at 10:03 AM, George Shuklin wrote: > In my earlier days I had tried many formal schemes, but it always cause > problems. > > For now I settle to following scheme: > > machine-used database (dns, chef

Re: [Openstack-operators] How to allow users to list services by modifying the policy.json file of Keystone

On 01/26/2015 04:02 PM, Fischer, Matt wrote: > Is there any reason that the user can¹t just run keystone catalog which > does not require admin permissions? Matt, this is just an example. We tried it with different list methods and it is also not working. We read your blog post about the topic (h

Re: [Openstack-operators] :document an OpenStack production environment

I use LibreOffice Draw for architecture diagrams. VRT Network Equipment [2] pretty much blows everything out of the water. For text documentation that I manually create (chef for example does this automatically) I'll put in plaintext files per environment that includes basic stuff such as host

Re: [Openstack-operators] Mar 9-10, 2015, Philadelphia, USA - Next Ops Meetup

On 1/23/15 4:55 AM, Tom Fifield wrote: On 22/01/15 14:36, Mathieu Gagné wrote: On 2015-01-12 12:11 AM, Tom Fifield wrote: Yup - standby for registration. Most likely some time this week. Any update? I would like to know the schedule to plan my return flight accordingly. http://www.eventbr

Re: [Openstack-operators] Mar 9-10, 2015, Philadelphia, USA - Next Ops Meetup

> Thanks Tom! Are there any details regarding hotel accommodations? It's not official, but several us from Time Warner Cable are staying at http://www.thewindsorsuites.com/ which appears to be fairly close and reasonably priced for the area. ___ OpenSta

Re: [Openstack-operators] Mar 9-10, 2015, Philadelphia, USA - Next Ops Meetup

On 27/01/15 05:38, Jesse Keating wrote: > On 1/23/15 4:55 AM, Tom Fifield wrote: >> On 22/01/15 14:36, Mathieu Gagné wrote: >>> On 2015-01-12 12:11 AM, Tom Fifield wrote: Yup - standby for registration. Most likely some time this week. >>> >>> Any update? >>> >>> I would like to know the

Re: [Openstack-operators] [openstack-dev][openstack-operators]flush expired tokens and moves deleted instance

+100 Dani On Mon, Jan 26, 2015 at 1:10 AM, Tim Bell wrote: > This is often mentioned as one of those items which catches every > OpenStack cloud operator at some time. It’s not clear to me that there > could not be a scheduled job built into the system with a default frequency > (configurable,

Re: [Openstack-operators] :document an OpenStack production environment

Excellent input, please keep it going. Maybe someone from HP will shed more light on their cmdb? Dani On Mon, Jan 26, 2015 at 4:28 PM, j wrote: > I use LibreOffice Draw for architecture diagrams. VRT Network Equipment >

Re: [Openstack-operators] Instance creation "boot from image (creates a new volume)" is Slow

You might get faster performance if the image was in raw format in glance. On Friday, January 23, 2015, Pedro Sousa wrote: > Hi all, > > I have a swift backend to store my glance images and a EMC storage to > store my volumes. > > When I try to boot the instance directly from the volume, the pro

[Openstack-operators] [Telco][NFV] Meeting facilitator for January 28th

Hi all, As mentioned in the notes from last week's meeting I am going to be in transit during our 1400 UTC meeting this Wednesday (28th) [1]. Is anyone else willing and able to facilitate in my absence? Thanks, Steve [1] https://wiki.openstack.org/wiki/TelcoWorkingGroup#Technical_Team_Meeting

[Openstack-operators] Configuration file validator

Do you think there is a need for a configuration file validator? Sometimes I have nasty issues in manual created configuration files (e.g. a parameter in a wrong section or a mistyped name of a section or parameter). The services themself to not validate the configuration files for logical issues