[Openstack-operators] [large deployment] Large Deployment Team December Meeting

[Matt Van Winkle]

Greetings all,

First off, let me apologize for being behind on getting anything out on
this.  I sort of jumped right back into running a cloud after the summit
and then the holiday week snuck up on me, so this is way overdue.

Thanks again to all who came and participated in the discussion back on
November 6th.  It was very productive and I look forward to working with
all of you going forward.  If anyone would like to peruse the notes, you
can find them here:

https://etherpad.openstack.org/p/kilo-summit-ops-large-deployments


---Meeting Time 
During the initial session, we all pretty much agreed that once a month
was the right cadence for now.  I'd like to go ahead and get one in during
December to keep some momentum going. For now, I'm targeting Wednesday or
Thursday the week after next to beat the Christmas/New Year holidays for
most.  In order to make it as useful as possible, I've created the
following doodle to pick a time that works best for this month:

http://doodle.com/wgd4df5fsr684xz9

Going forward, we'll build in a little predicability to the timing (see #3
below).  We'll plan for an hour and see if we need to change that in
future months.


---Meeting Topics
I went through the Paris notes, pulled out a couple of Top Priority items,
layered in some unfinished business (regular meeting times) and at least
one of the things we said could discuss on a regular basis (specs).  This
gave me the following rough agenda:

1.  Designating "representatives" from the group to attend the various
mid-cycles
2.  A "Quick win" discussed in Paris: feedback to the devs on periodic
tasks that we have disabled/tweaked for various reasons
3.  On-going, set meeting times (with some options for different time
zones - alternate each month, two sessions a month, etc)
4.  Any specs that folks want to bring to the attention of the group
5.  Plans/goals for this group during the Ops mid-cycle
6.  Other business

I bet we'll be hard pressed to cover all that in an hour, and by no means
do we have to use this exact agenda, but it made sense to me to start the
conversation with these items.  I've gone ahead and created the following
etherpad:

https://etherpad.openstack.org/p/Large-Deployment-Team-Meetings

So we can hash things out further in there or here on the mailing list.


---Other Bits
I did try and get some wiki spaces, etc set up, but lack permissions, so
I'll harass some people to help me get that fixed up.  I noticed there
actually isn't even an overarching Operators page, so we should probably
see about that as well.  Once we've decided the ongoing meeting time
structure, I'll work to get that added here -
https://wiki.openstack.org/wiki/Meetings - too.


Go ahead and hit the doodle and note the options that work for you.  I'll
pick one that seems to provide the most coverage at the end of the week so
folks have time to plan it in their schedule.  Sorry again, that it's a
bit rushed this time around.  It will be easier in future months.

Let me know if you have any other questions.
Thanks!
Matt

-- 
Matt Van Winkle

Senior Manager, Operations
Rackspace
210-312-4442 (w)
Twitter: @mvanwink
IRC: VW_



 


___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Graphite dashboard

[Klein, Bradley]

At Time Warner Cable, we’re in the process of standing up monasca 
(https://wiki.openstack.org/wiki/Monasca), and it uses grafana as well.  While 
a bit cumbersome to initially get setup, it is very flexible in terms of custom 
metric plugins (as well as a rich set of default metrics).  We’ve also been 
helping to add puppet support for install 
(https://github.com/stackforge?query=monasca).

Brad

From: Michael Dorman mailto:mdor...@godaddy.com>>
Date: Tuesday, December 2, 2014 at 9:03 PM
To: 
"openstack-operators@lists.openstack.org"
 
mailto:openstack-operators@lists.openstack.org>>
Subject: Re: [Openstack-operators] Graphite dashboard

At this point we’re not doing anything crazy with collectd, I think I will take 
advantage of some of your custom ones!

On compute nodes, we’re running Diamond to handle per-instance metrics pulled 
from libvirt.  https://github.com/BrightcoveOS/Diamond

Mike


From: Xav Paice mailto:xavpa...@gmail.com>>
Date: Tuesday, December 2, 2014 at 7:10 PM
To: OpenStack Operators 
mailto:openstack-operators@lists.openstack.org>>
Subject: Re: [Openstack-operators] Graphite dashboard

On 03/12/14 13:34, Michael Dorman wrote:
I’m curious what people are using for a Graphite front-end?  We’re finally 
getting around to recording a bunch of metrics, and now we need something good 
for visualization.





___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.orghttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

+1 for grafana.

I'd love to know about any shared plugins for collectd etc (assuming that's how 
you're getting stats into Graphite).  Our current ones are on 
https://github.com/catalyst/collectd-openstack and I'm working on making them 
happy with more than one region.


This E-mail and any of its attachments may contain Time Warner Cable 
proprietary information, which is privileged, confidential, or subject to 
copyright belonging to Time Warner Cable. This E-mail is intended solely for 
the use of the individual or entity to which it is addressed. If you are not 
the intended recipient of this E-mail, you are hereby notified that any 
dissemination, distribution, copying, or action taken in relation to the 
contents of and attachments to this E-mail is strictly prohibited and may be 
unlawful. If you have received this E-mail in error, please notify the sender 
immediately and permanently delete the original and any copy of this E-mail and 
any printout.
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Wrong URL returned on Keystone /v2.0

[Jean-Daniel Bonnetot]

Hi Ops,

Thanks! First try, success. 
Nice shot and thanks again.

I had similar problem on nova:
curl -v -H "X-Auth-Token:`cat token`" 
https://mycontroller.ovh.com:8774/v2/b2abfe4f92de4571ad716b70d00f7e21/servers

{"servers": [{"id": "2354ee79-2123-49e3-948b-336e19c1c070", "links": [{"href": 
"http://172.17.126.1:8774/v2/b2abfe4f92de4571ad716b70d00f7e21/servers/2354ee79-2123-49e3-948b-336e19c1c070";,
 "rel": "self"}, {"href": 
"http://172.17.126.1:8774/b2abfe4f92de4571ad716b70d00f7e21/servers/2354ee79-2123-49e3-948b-336e19c1c070";,
 "rel": "bookmark"}], "name": "instance"}….

Corrected by:
/etc/nova/nova.conf
[DEFAULT]
osapi_compute_link_prefix=https://mycontroller.ovh.com:8774/v2

curl -v -H "X-Auth-Token:`cat token`" 
https://mycontroller.ovh.com:8774/v2/b2abfe4f92de4571ad716b70d00f7e21/servers

{"servers": [{"id": "f934feb6-13e7-4202-8760-489b306bc361", "links": [{"href": 
"https://mycontroller.ovh.com:8774/v2/3effbdc4ae6346b8ba786bd0feb4bc84/servers/f934feb6-13e7-4202-8760-489b306bc361";,
 "rel": "self"}, {"href": 
"https://mycontroller.ovh.com:8774/3effbdc4ae6346b8ba786bd0feb4bc84/servers/f934feb6-13e7-4202-8760-489b306bc361";,
 "rel": "bookmark"}], "name": "c7-root"}, {"id": 
"56c96728-d47a-4550-9298-48e4b7370924", "links": [{"href": 
"https://mycontroller.ovh.com:8774/v2/3effbdc4ae6346b8ba786bd0feb4bc84/servers/56c96728-d47a-4550-9298-48e4b7370924";,
 "rel": "self »},

Rgds,


--
Jean-Daniel
@pilgrimstack




Le 2 déc. 2014 à 19:02, Fischer, Matt  a écrit :

> Making that call just returns some details on the API version you¹ve
> selected. It really doesn¹t have anything to do with the catalog URLs. The
> URL you¹re looking at is a reference to the server who returned you the
> info. Perhaps it¹s your load balancer if you don¹t recognize the IP? It
> should either be that or the keystone box itself.
> 
> On 12/2/14, 10:27 AM, "Jean-Daniel Bonnetot"
>  wrote:
> 
>> Hi Ops,
>> 
>> I get the wrong URL on this call :
>> 
>> curl -i -X GET https://mycontroller.ovh.com:5000/v2.0/ -H "Accept:
>> application/json" -H "User-Agent: python-keystoneclient"
>> HTTP/1.1 200 OK
>> 
>> {"version": {"status": "stable", "updated": "2014-04-17T00:00:00Z",
>> "media-types": [{"base": "application/json", "type":
>> "application/vnd.openstack.identity-v2.0+json"}, {"base":
>> "application/xml", "type":
>> "application/vnd.openstack.identity-v2.0+xml"}], "id": "v2.0", "links":
>> [{"href": "http://172.16.64.1:5000/v2.0/";, "rel": "self"}, {"href":
>> "http://docs.openstack.org/api/openstack-identity-service/2.0/content/";,
>> "type": "text/html", "rel": "describedby"}, {"href":
>> "http://docs.openstack.org/api/openstack-identity-service/2.0/identity-dev
>> -guide-2.0.pdf", "type": "application/pdf", "rel": "describedby"}]}}
>> 
>> I get "href": "http://172.16.64.1:5000/v2.0/«  witch is not my publicURL,
>> not my internalURL and not my adminURLŠ
>> It¹s a kind of ip based internalURL, very strange.
>> 
>> My catalog is :
>> # keystone catalog --service identity
>> Service: identity
>> +-+--+
>> |   Property  |Value |
>> +-+--+
>> |   adminURL  | https://mycontroller.ovh.com:35357/v2.0  |
>> |  id |   3e83b592262149ee9a007df65ac9c431   |
>> | internalURL |http://controller284:5000/v2.0|
>> |  publicURL  | https://mycontroller.ovh.com.com:5000/v2.0   |
>> |region   |  regionOne   |
>> +-+‹‹‹+
>> 
>> There is something anywhere where I can set the url return by this call ?
>> 
>> Rgds,
>> 
>> ‹
>> Jean-Daniel Bonnetot
>> @pilgrimstack
>> ___
>> OpenStack-operators mailing list
>> OpenStack-operators@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
> 
> 
> This E-mail and any of its attachments may contain Time Warner Cable 
> proprietary information, which is privileged, confidential, or subject to 
> copyright belonging to Time Warner Cable. This E-mail is intended solely for 
> the use of the individual or entity to which it is addressed. If you are not 
> the intended recipient of this E-mail, you are hereby notified that any 
> dissemination, distribution, copying, or action taken in relation to the 
> contents of and attachments to this E-mail is strictly prohibited and may be 
> unlawful. If you have received this E-mail in error, please notify the sender 
> immediately and permanently delete the original and any copy of this E-mail 
> and any printout.


___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators