Earlier  
Posted Nick Remark
#openstack-nova - 2018-11-12
11:55:19 lyarwood sean-k-mooney: yeah back to pike would be useful, feel free to post them now if you have time or I can look later today
11:55:54 sean-k-mooney just reading a spec so ill post them shortly.
14:15:14 openstackgerrit Martin Midolesov proposed openstack/nova master: [vmware] Cross vCenter live migration https://review.openstack.org/616590
14:29:23 ThomasWhite Hey all, a quick question I couldn't find a reliable answer to. How often or what would qualify running the "nova-manage db archive_deleted_rows" command? Is this something I should view as a routine operation, or only a as-needed step?
14:29:49 ThomasWhite Our galera cluster is stable and quick, no pressing need for it nor are we short on space, but just looking to implement any best practices
14:33:40 sean-k-mooney ThomasWhite: that is really up to you. if you want to be proactive and keep the current level of perfromace you could proactivly run that command on a fixed cadance
14:34:39 sean-k-mooney ThomasWhite: but if you have monitoring in place to determin you perfromance is within your accpeatable critia then you could decide to only run it when that critia is not met
14:35:46 sean-k-mooney ThomasWhite: if you upgrade every release then running it as part of your upgrade may be suffient if your cloud is relitivly stable with longer lived instnaces
14:36:27 sean-k-mooney ThomasWhite: if you are running a ci environment where you are constantly spawning and deleteing instance then you might want to run it on a cron job every X weeks
14:37:46 sean-k-mooney i personally would only run it on upgrade or when needed as i dont like fixing things that are not broken but perhaps some operators can share there experiance?
14:38:25 ThomasWhite Awesome - thanks sean-k-mooney. Would removal of individual entries from instance_actions do anything bad either - primarily as we need to take a look at a server (booting through rescue) but not leave the regular user of it with knowledge we've taken a look for compliance.
14:39:11 ThomasWhite Putting into single user could impact data reliability so booting into rescue is the preferred mechanism
14:40:14 sean-k-mooney ThomasWhite: that i dont know the anwser too. it if your billing system cannot elimitate teh run time of the insance using o
14:40:32 sean-k-mooney openstack to start the instance in that case my be ill advised
14:40:57 ThomasWhite Oh we'd only be looking to hide the fact it booted into rescue if that makes sense, the instance needs to continue existing and will be put back to normal post-rescue
14:41:48 sean-k-mooney yes i understand but you would need to remove two things first the fact ti was booted in rescue mode and second the fact it was running at all
14:42:08 sean-k-mooney i dont know of a clean way to do that today
14:44:21 ThomasWhite sean-k-mooney thanks, I'll give it a go and let you know
14:46:48 sean-k-mooney i generally stay away from such topics as i dont really agree with them ethiclaly but there may be a case to be made for having a inspect action that worked like rescue and was admin only that did not recored itself in the db.
14:47:54 ThomasWhite I agree, it isn't a public cloud situation, it's all data owned and operated internally though not to worry
14:48:03 sean-k-mooney that said such an operator capablity could expose the operator to liablity or prevent certen workloads form being used on an openstack cloud as the teanat may nolonger beable to fulfil there compliance requirements as a result
14:49:12 sean-k-mooney ThomasWhite: right it the tanant and the operator is the same company it makes sense in some cases hence why it think there could be an argument made for support this more cleanly
14:49:46 sean-k-mooney for public cloud i would be less keen on this but private could perhaps.
14:50:47 sean-k-mooney i would certenly feel much more comfortable supporting a db manage command to do the clean up of the event or an api then recommending db surgery to do the same.
14:54:51 ThomasWhite I think as a project, nova should probably remain neutral on the politics of it, as it's much more a niche concern. My own is only a one-off regulatory issue rather than regular procedure, so happy to experiment and report back as an FYI for others
15:39:37 ThomasWhite Ok, I removed the entries from instance_actions_events first and then the instance_actions entry for it, and worked like a charm. Done the usual stretch of actions ie rebuild, restart, console etc and works a treat.
18:17:10 openstackgerrit Merged openstack/nova stable/rocky: Update resources once in update_available_resource https://review.openstack.org/612293
18:18:13 openstackgerrit Merged openstack/nova stable/rocky: Handle online_data_migrations exceptions https://review.openstack.org/611701
18:18:19 openstackgerrit Merged openstack/nova stable/rocky: Fix os-simple-tenant-usage result order https://review.openstack.org/613853
19:37:28 ivaat hi all
19:37:40 openstack Launchpad bug 1801326 in OpenStack Compute (nova) "CRITICAL keystonemiddleware.auth_token" [Undecided,New]
19:37:40 ivaat seeking help for this: https://bugs.launchpad.net/nova/+bug/1801326
23:57:01 naptastic Is it possible, when instantiating a VM, to install more than one SSH public key?
#openstack-nova - 2018-11-13
02:17:38 openstackgerrit melanie witt proposed openstack/nova master: Make supports_direct_io work on 4096b sector size https://review.openstack.org/616580
07:14:38 openstackgerrit OpenStack Proposal Bot proposed openstack/nova stable/rocky: Imported Translations from Zanata https://review.openstack.org/614757
07:34:46 Iarvi hi
08:36:16 openstackgerrit Matt Riedemann proposed openstack/nova master: Make _instances_cores_ram_count() be smart about cells https://review.openstack.org/569055
08:36:17 mriedem dansmith: cleaned up ^
08:37:51 dansmith mriedem: ack
08:38:22 openstackgerrit Matt Riedemann proposed openstack/nova master: Add DownCellFixture https://review.openstack.org/614810
09:20:49 openstackgerrit Matt Riedemann proposed openstack/nova stable/rocky: Mention meta key suffix in tenant isolation with placement docs https://review.openstack.org/617535
09:57:41 openstackgerrit Brin Zhang proposed openstack/nova master: Remove useless sample and add the lack of tests in v266 https://review.openstack.org/614671
11:48:15 openstackgerrit wanghui proposed openstack/nova-specs master: Remove the duplicate words https://review.openstack.org/617615
12:46:49 openstack Launchpad bug 1801326 in OpenStack Compute (nova) "CRITICAL keystonemiddleware.auth_token" [Undecided,New]
12:46:49 ivaat hi i am seeking help to this: https://bugs.launchpad.net/nova/+bug/1801326
13:39:46 mriedem logan-: same logan vig?
15:35:26 openstackgerrit Martin Midolesov proposed openstack/nova master: Allow driver to specify switch&port for faster lookup https://review.openstack.org/617695
15:39:42 logan- mriedem: yep!
16:17:20 spatel sean-k-mooney: morning
16:17:28 spatel are you in summit?
16:17:50 spatel if no then i need 2 min from you..
16:18:03 sean-k-mooney spatel: no im not im afraid
16:18:12 spatel :)
16:18:32 sean-k-mooney how can i help
16:18:40 spatel i am testing influx + grafana for openstack dashboard...
16:19:16 spatel currently i am using telegraf and it looks amazing
16:19:27 spatel now i am confused what i should use collectd or telegraf ?
16:19:39 spatel need you honest opinion
16:19:43 sean-k-mooney ah ok thats a little out of my are of expertiese but i know its a solution many use.
16:20:15 sean-k-mooney well telegraf is much newer, collectd has more support but it is also a legacy solution
16:20:19 spatel This is first time i am going to use so want to make sure i won't hit the wall moving forward
16:20:29 sean-k-mooney it really depends on what you intend to use it for
16:21:06 spatel people saying telegraf has tags feature which will be very handy which collected doesn't support yet
16:21:47 spatel also telegraf doesn't have libvird support
16:22:10 spatel libvirtd*
16:22:30 sean-k-mooney spatel: well the 2 are not mutally exclcive
16:22:51 sean-k-mooney ralonsoh: you have worked on yardstick can you provide advice to spatel
16:22:52 spatel otherwise I think i will give it a try both and see...
16:23:12 openstackgerrit Dirk Mueller proposed openstack/nova master: Handle alternative UEFI boot loader locations on SLES https://review.openstack.org/348394
16:23:20 sean-k-mooney i would proably default to collectd jsut becase im slightly more familure with it
16:23:34 spatel make sense!
16:23:55 spatel also telegraf use go lang which is new for me too :(
16:24:08 spatel i can handle python easily
16:24:15 sean-k-mooney mnaser: what solution does vexhost user for its monitoring? is it internal or do you use collectd, telegraf, nagios or zabex
16:24:32 sean-k-mooney spatel: collectd is all or mostly c
16:24:39 spatel mnaser: is in Openstack summit :) i was him on youtube..
16:25:13 spatel but collected can use plugin written in pythn
16:25:20 sean-k-mooney spatel: yes he is. there will be a lot of people at teh summit that can provide input on this topic.
16:25:45 sean-k-mooney spatel: collectd can use plugins written in python java and several other languges
16:26:04 spatel lets me try both and see who is handy..
16:26:16 spatel worth exploring them
16:26:25 sean-k-mooney spatel: one of the advantages of it being around and used for so long is there are lots of language bindings
16:26:48 spatel hmm
16:26:52 spatel Point
16:27:16 spatel collectd is little fast because its written in C
16:28:42 spatel I have 165 compute node in my cloud :) running 207 VMs
16:28:42 sean-k-mooney spatel: well i hope that helped a little. enjoy the summit and try not to let two many vendors sell you things you dont need.
16:28:56 ralonsoh spatel, in https://github.com/opnfv/yardstick/blob/master/yardstick/dispatcher/influxdb.py you have an example of how to store the information in influxdb
16:29:00 sean-k-mooney hehe nice
16:29:05 spatel sean-k-mooney: i am in office :( not lucky!
16:29:30 ralonsoh spatel, you also need to retrieve this information from collectd. You can use rabbitmq to retrieve collectd information
16:29:34 openstackgerrit Dirk Mueller proposed openstack/nova master: Handle alternative UEFI boot loader locations on SLES https://review.openstack.org/348394
16:29:38 spatel thanks ralonsoh! reading...
16:30:33 spatel You can use rabbitmq to retrieve collectd information - this is interesting..
16:30:41 sean-k-mooney ralonsoh: thanks i rely on you and emma when it comes to monitoring to fill it the gaps as its not someting i normally dable in.
16:31:06 ralonsoh spatel, here you have an example of how to handle the collectd info: https://github.com/opnfv/yardstick/blob/master/yardstick/network_services/nfvi/resource.py
16:31:29 ralonsoh sean-k-mooney, well, I'm not contributing any more to Yardstick (for now)
16:32:02 sean-k-mooney ralonsoh: true but you have much more uptoday knowladge of where things stood then i.
16:33:10 ralonsoh spatel: collectd dumps the information in rabbitmq. How to create a mq consumer: https://github.com/opnfv/yardstick/blob/master/yardstick/network_services/nfvi/resource.py#L111
16:33:40 sean-k-mooney ralonsoh: collectd can also use the netwroking pluging to dump the data directly into infuxdb too

Earlier   Later