[Openstack-operators] [glance] Summit sessions brainstorm
Greetings, Hey Folks, Now that RC1 is out (YAY!), we should start looking forward to Glance's Newton plans. More specifically, I'd like us to speed up our brainstorm on summit topics. I've set up an etherpad for it and we've got some interesting topics listed already. But there's more, there can be more! I would like to recommend folks to keep in mind what the Mitaka priorities were[0] and that most of this priorities will likely be adopted in Newton as well. While it's awesome to have many sessions (and especially diverse sessions) I believe it's better for Glance if we would keep most of them focused on what the priorities for the next summit are/will be/could be. We'll start discussing these sessions in our next meeting (Thursday March, 24th). Here's the link to the etherpad: https://etherpad.openstack.org/p/newton-glance-summit-planning [0] http://specs.openstack.org/openstack/glance-specs/priorities/mitaka-priorities.html Cheers, Flavio -- @flaper87 Flavio Percoco signature.asc Description: PGP signature ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] [openstack-dev] [all][log] Ideas to log request-ids in cross-projects
Excerpts from Kekane, Abhishek's message of 2016-03-16 05:56:25 +: > Hi Doug, > > Is there a need to submit a cross-project specs for this or should I create > individual blueprints in individual python-client for this. > Please let me know. > > Thank you, > > Abhishek Kekane You already have a spec for this work. If the details are wrong or incomplete, it can be updated. Otherwise, you should be able to just submit the patches necessary to complete the spec already defined. Doug ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] [openstack-operators] Fernet key rotation
Hi In a multi node HA deployment for production does key rotate need a keystone process reboot or should we just run the fernet rotate on one node and distribute it without restarting any process I presume keystone can handle the rotation without a restart? I also assume this key rotation can happen without a maintenance window What do folks typically do in production and how often do you rotate keys Ajay ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] [openstack-operators][neutron][telemetry] manual creation of metering labels and rules
Rubab Syedwrote: Hi folks, I'm trying to understand the metering of network traffic at l3 level with neutron-metering-agent [1]. In order to meter the traffic, we have to create explicit labels and rules. When we have a very large setup, is this still handled manually? Do we have some kind of automation script that detects all the networks attached to all routers of all the tenants and creates labels and rules accordingly? All traffic in case we want to monitor per interface bandwidth through ceilometer/monasca. That kind of orchestration would be out of neutron scope. I assume other projects should be utilized for what you want to achieve, like Heat. Ihar ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] [openstack-operators] Fernet key rotation
Fernet key rotation is easy. 1) You don't need a maintenance window 2) You can do one node at a time even with a long delay between 3) You don't need to restart anything We rotate approximately weekly. On Wed, Mar 16, 2016 at 3:44 PM, Ajay Kalambur (akalambu) < akala...@cisco.com> wrote: > Hi > In a multi node HA deployment for production does key rotate need a > keystone process reboot or should we just run the fernet rotate on one node > and distribute it without restarting any process > I presume keystone can handle the rotation without a restart? > > I also assume this key rotation can happen without a maintenance window > > What do folks typically do in production and how often do you rotate keys > > Ajay > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] [app-catalog] IRC Meeting Thursday March 17th at 17:00UTC
Join us Thursday for our weekly meeting, scheduled for March 17th at 17:00UTC in #openstack-meeting-3 NOTE: The time may be different for you due to US daylight savings time (it's probably an hour later for you if you're in the US) The agenda can be found here, and please add to if you want to get something on the agenda: https://wiki.openstack.org/wiki/Meetings/app-catalog Looking forward to seeing everyone there tomorrow! ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] [Contrail][DevStack] contrail-installer error
The contrail-installer repo seems to be broken - complaining about missing Cassandra directories. It appears this was a known issue [1] and was planning a fix but it seems the fellow who planned to do the work disappeared from the interweb (dsetia). Do any of the Contrail folks watching this list know the work-around? [1] https://github.com/Juniper/contrail-installer/issues/113 //adam *Adam Lawson* AQORN, Inc. 427 North Tatnall Street Ste. 58461 Wilmington, Delaware 19801-2230 Toll-free: (844) 4-AQORN-NOW ext. 101 International: +1 302-387-4660 Direct: +1 916-246-2072 ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators