- openstack-discuss - lists.openstack.org

Re: [openstack-dev] [horizon] how to get horizon related logs to syslog?
by Akihiro Motoki 19 Nov '18

19 Nov '18

Hi, Horizon logging depends on Django configuration which supports full python logging [1]. [1] does not provide enough examples. Perhaps [2] will help you (though I haven't tested it). [1] https://docs.djangoproject.com/en/2.0/topics/logging/ [2] https://www.simonkrueger.com/2015/05/27/logging-django-apps-to-syslog.html Thanks, Akihiro 2018年11月16日(金) 18:47 Tikkanen, Viktor (Nokia - FI/Espoo) < viktor.tikkanen(a)nokia.com>: > Hi! > > For most openstack parts (e.g. Aodh, Cinder, Glance, Heat, Ironic, > Keystone, Neutron, Nova) it was easy to get logs to syslog. > > For example for Heat something similar to this (into file > templates/heat.conf.j2): > > # Syslog usage > {% if heat_syslog_enabled %} > use_syslog = True > syslog_log_facility = LOG_LOCAL3 > {% else %} > log_file = /var/log/heat/heat.log > {% endif %} > > But how to get Horizon related logs to syslog? > > -V. > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

2 1

[openstack-dev] [Searchlight] New team meeting time
by Trinh Nguyen 19 Nov '18

19 Nov '18

Hello team, In order to welcome new contributors to the Searchlight project, we decided to change the meeting time [1]: - Time: 13:30 UCT - Meeting Channel: #openstack-searchlight - Meeting recurrence: bi-weekly starting from 19th Nov. 2018 [1] http://eavesdrop.openstack.org/irclogs/%23openstack-searchlight/latest.log.… Hope that there will be new blood into the project :D -- *Trinh Nguyen* *www.edlab.xyz <https://www.edlab.xyz>* __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

1 0

[glance] time to adjust your ML filters
by Brian Rosmaita 19 Nov '18

19 Nov '18

Hello Glancers, This message is sent from the new openstack-discuss mailing list so that you have a reference point from which to adjust your email filters. See Jeremy's message from earlier today [0] for more information about the new ML. cheers, brian [0] http://lists.openstack.org/pipermail/openstack-discuss/2018-November/000000…

1 0

Re: [openstack-dev] [tripleo] Proposing Enrique Llorente Pastora as a core reviewer for TripleO
by Gabriele Cerami 19 Nov '18

19 Nov '18

On 15 Nov, Sagi Shnaidman wrote: > Hi, > I'd like to propose Quique (@quiquell) as a core reviewer for TripleO. > Quique is actively involved in improvements and development of TripleO and > TripleO CI. He also helps in other projects including but not limited to > Infrastructure. It'll be grand. +1 __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

1 0

[ops][docs] operations-docs on StoryBoard
by Frank Kloeker 19 Nov '18

19 Nov '18

Hello, I've started today with a proposal on [1] to add docs for operations on StoryBoard [2].That could be useful to track bugs that people raise while reading the document. Also a rework for parts of the document could be planned in StoryBoard. A reference might be the work on the Contributor Guide which is mostly maintained in [3]. kind regards Frank [1] https://review.openstack.org/#/c/618722/ [2] https://storyboard.openstack.org [3] https://storyboard.openstack.org/#!/project/openstack/contributor-guide

1 0

Re: [openstack-dev] [tripleo] Proposing Enrique Llorente Pastora as a core reviewer for TripleO
by Juan Antonio Osorio Robles 19 Nov '18

19 Nov '18

+1 on making him tripleo-ci core. Great work! On 11/15/18 5:50 PM, Sagi Shnaidman wrote: > Hi, > I'd like to propose Quique (@quiquell) as a core reviewer for TripleO. > Quique is actively involved in improvements and development of TripleO > and TripleO CI. He also helps in other projects including but not > limited to Infrastructure. > He shows a very good understanding how TripleO and CI works and I'd > like suggest him as core reviewer of TripleO in CI related code. > > Please vote! > My +1 is here :) > > Thanks > -- > Best regards > Sagi Shnaidman > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

1 0

[openstack-dev] [octavia] Please give me some comments about my patchs
by Jeff Yang 18 Nov '18

18 Nov '18

Hi, Octavia Team: There are two patches I committed: https://review.openstack.org/#/c/590620/ https://review.openstack.org/#/c/594040/ The first implement l7policy and l7rule's quota management. The second provides some restrictions about the protocol when listener is associated with pool. I think these functions are useful for users. I hope to receive some suggestions from you. Thinks. __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

1 0

Re: [Openstack] (Juno - *sigh*) Want non-admin access to hypervisor:VM association.
by Ken D'Ambrosio 18 Nov '18

18 Nov '18

On 2018-11-18 09:11, Mohammed Naser wrote: > https://blueprints.launchpad.net/nova/+spec/openstack-api-hostid > > This should take care of it, don't know if it exists in Juno though. It *does* exist in Juno, it *can't*, however, do what I want -- at least, generically. The hostId that gets returned is a value that's (apparently) used to let you know, semi-anonymously, how affinity is (or isn't) working for your VMs. So you get a unique identifier for each hypervisor -- but it has no *obvious* bearing on the hostname. It's an id that's formed from the SHA224 hash of the ID of your tenant and the hostname of the hypervisor -- a bit of a catch-22, that, and prevents you from being able to make use of the hash if you don't know your back-end. But... I do. So I created an associative array with all the current (and, God willing, future) hypervisor hostnames in my company, with the key being the hostId/hash, and the value being the hypervisor name. Then I queried my VMs, got all the hostIds, used that as the index to query my associative array, and bingo! My hypervisor's name. Kinda fugly, but when you have a standardized hypervisor hostname nomenclature, it's sufficient, without having to go mucking about with changing poorly-documented Nova policy.json stuff in a four-year-old release of OpenStack. I'll take it. Thanks! -Ken > On Thu, Nov 15, 2018 at 1:49 PM Ken D'Ambrosio <ken(a)jots.org> wrote: > >> Hey, all. We've got a Juno cloud, and we'd like various end-users to be >> able to see which hypervisors their VMs spring up on. >> /etc/nova/policy.json seems to have some relevant info, but it's hard to >> tell what does what. "compute_extension:hypervisors" looks like a >> possible candidate, but that's so vague that there's no telling what, >> exactly, is meant by "hypervisors". So: >> >> * Given that I just want the hypervisor:VM association, any suggestions >> as to which rule(s) to modify? >> * Failing that, wondering if there's any for-real documentation on what >> the various options in policy.json *do*. I've found many, many lists of >> what's in a generic policy.json, but nothing that went into detail about >> what does what. >> >> Thanks! >> >> -Ken >> >> _______________________________________________ >> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >> Post to : openstack(a)lists.openstack.org >> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > > -- > Mohammed Naser -- vexxhost > > ----------------------------------------------------- > D. 514-316-8872 > D. 800-910-1726 ext. 200 > E. mnaser(a)vexxhost.com > W. http://vexxhost.com [1] Links: ------ [1] http://vexxhost.com/ _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack(a)lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

1 0