| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2017-04-07 | |||
| 19:44:04 | cdent | the past is a pain | |
| 19:44:14 | cdent | but what we've got | |
| 19:44:31 | sdague | right, but given that we needed that before | |
| 19:44:49 | sdague | I don't think it's fair to say "we've solved it forever" now | |
| 19:46:58 | sdague | I do really wish that python packaging had more rich constructures for things like SHARE directory and CONFIG directory like perl packaging does | |
| 19:47:13 | sdague | because being in SHARE would be ideal | |
| 19:47:52 | mriedem | does go have all of the packaging issues solved? because if so, let's move to go. | |
| 19:48:05 | mriedem | i heard dependency management in go is great. | |
| 19:48:12 | thomasem | Lol | |
| 19:48:45 | thomasem | Coming along https://github.com/golang/dep | |
| 19:48:50 | mriedem | dansmith's toilets are all running on golang now | |
| 19:48:52 | mriedem | i heard | |
| 19:49:07 | mriedem | toilet apps i should say | |
| 19:49:25 | dansmith | as far as you know | |
| 19:49:27 | thomasem | I can just imagine the applications. | |
| 19:49:38 | thomasem | "I can't do that, Dave..." | |
| 19:49:38 | mriedem | the toilet app in go wipes your ass in half the time | |
| 19:49:53 | mriedem | *blistering* speed | |
| 19:49:55 | dansmith | hah | |
| 19:50:00 | dansmith | ouch | |
| 19:50:33 | thomasem | D= | |
| 19:51:31 | cdent | I think this might be a good time to leave. | |
| 19:51:48 | mriedem | thanks, i got what i needed out of this https://review.openstack.org/#/c/454866/ | |
| 19:51:52 | mriedem | to keep ttx at bay | |
| 19:52:30 | cdent | \o/ | |
| 19:56:28 | mriedem | we can have an index on a nullable column right? | |
| 19:56:35 | mriedem | wondering if we should put an index on services.uuid | |
| 19:56:40 | mriedem | for the lookups that the api will be doing | |
| 19:57:22 | mriedem | we don't have one for compute_nodes though i guess | |
| 19:57:35 | mriedem | maybe we should, we look those up by a list of uuids from the scheduler, but would an index help there/ | |
| 19:57:36 | mriedem | ? | |
| 19:57:54 | mriedem | where is leakypipes when i need him | |
| 20:02:49 | mriedem | hmm, if we declared the field as unique=True we wouldn't have to index it, but these are not specified that way, presumably b/c they are nullable=True for existing entries that are None | |
| 20:03:55 | mriedem | zzzeek: can you have a unique=True and nullable=True column? | |
| 20:04:06 | mriedem | or does the nullable=True defeat the unique constraint? | |
| 20:04:18 | mriedem | i know you can't do that in db2, but i think mysql lets you get by with it | |
| 20:04:31 | zzzeek | mriedem: yes but the rules for if NULL is counted are not necessarily consistent across backends | |
| 20:06:12 | mriedem | https://www.postgresql.org/docs/9.0/static/indexes-unique.html | |
| 20:06:16 | mriedem | Null values are not considered equal. | |
| 20:06:16 | zzzeek | mriedem: A UNIQUE index creates a constraint such that all values in the index must be distinct. An error occurs if you try to add a new row with a key value that matches an existing row. For all engines, a UNIQUE index permits multiple NULL values for columns that can contain NULL. | |
| 20:06:32 | zzzeek | mriedem: yeah I think SQL server is the one that might be different | |
| 20:06:38 | mriedem | and db2 | |
| 20:07:00 | mriedem | i at least know that db2 never allowed a unique constraint with nullable columns | |
| 20:07:09 | mriedem | it would allow a unique index though i think... | |
| 20:07:22 | mriedem | it's been a long time since i had to remember | |
| 20:07:40 | zzzeek | db2 makes oracle look like sqlite, installation-wise, so ive hardly ever run a DB2 | |
| 20:07:44 | mriedem | anyway, it sounds like mysql and postgresql are ok with this | |
| 20:07:47 | zzzeek | yep | |
| 20:07:58 | mriedem | db2 install requires a phd i think | |
| 20:08:11 | sdague | mriedem: just half a shelf of manuals | |
| 20:08:21 | mriedem | certified db2 installer | |
| 20:08:45 | mriedem | i think i asked someone 5 years ago for a db2 server rpm for simple install and was laughed at | |
| 20:09:20 | sdague | which, is kind of dumb, because honestly the install steps are very repeatable | |
| 20:09:48 | sdague | they wrote them in the manual, why they didn't just write them in the rpm post-install always blew my mind | |
| 20:09:53 | sdague | brb | |
| 20:10:23 | mriedem | zzzeek: if i wanted to make a column unique=True in an alter during an offline migration, is that a pretty bad time sink? | |
| 20:10:28 | mriedem | for the compute_nodes table | |
| 20:10:51 | mriedem | so not something as big as the instances table, compute_nodes is what, 10s of thousands at biggest? | |
| 20:10:59 | zzzeek | mriedem: well it probably depends on the datatypes you're uniquing, it has to build an index | |
| 20:11:00 | mriedem | not sure where rax is at this point | |
| 20:11:12 | zzzeek | 10's of thousands is not much | |
| 20:11:16 | mriedem | uuid = Column(String(36), nullable=True) | |
| 20:11:59 | zzzeek | it should not be a huge time sink but, I dont have an ironclad guarantee on that | |
| 20:12:17 | zzzeek | if youre < 1M rows, nothing should be that big of a deal | |
| 20:12:30 | mriedem | i don't think cern is running 1M compute nodes yet | |
| 20:21:50 | openstackgerrit | Anusha Unnam proposed openstack/nova master: Add description to policies in server_password.py https://review.openstack.org/452259 | |
| 20:26:02 | mriedem | dtp: some comments in https://review.openstack.org/#/c/453025/ | |
| 20:27:37 | dtp | ok mriedem | |
| 20:29:24 | openstackgerrit | Anusha Unnam proposed openstack/nova master: fix admin context scenarios for cinderclient https://review.openstack.org/384799 | |
| 20:32:53 | openstackgerrit | Pushkar Umaranikar proposed openstack/nova-specs master: Stop using Neutron admin token https://review.openstack.org/439890 | |
| 20:33:28 | openstackgerrit | Pushkar Umaranikar proposed openstack/nova-specs master: Use service token to authorize neutron port binding https://review.openstack.org/439890 | |
| 20:41:38 | openstackgerrit | Matt Riedemann proposed openstack/nova master: Add compute_nodes_uuid_idx unique index https://review.openstack.org/454887 | |
| 20:41:46 | mriedem | dtp: ^ is the unique index for compute_nodes.uuid | |
| 20:41:50 | openstackgerrit | Brianna Poulos proposed openstack/nova-specs master: API Option for Signature Verification https://review.openstack.org/312225 | |
| 20:42:06 | dtp | ok | |
| 20:42:33 | openstackgerrit | Anusha Unnam proposed openstack/nova master: Add description to policies in servers.py https://review.openstack.org/451966 | |
| 20:47:18 | mriedem | dtp: you want me to start working the online data migration patch to live on top of this one? | |
| 20:47:24 | mriedem | the services.uuid patch i mean | |
| 20:47:33 | dtp | that's fine w/ me | |
| 20:49:21 | openstackgerrit | Eric Fried proposed openstack/nova master: PowerVM Driver: spawn/delete #1: no-ops https://review.openstack.org/438119 | |
| 20:49:35 | efried | mriedem ^^ requirements bump to match latest g-r | |
| 20:49:59 | efried | mriedem Thanks for the detailed review on #2 as well. Working through it. | |
| 20:55:04 | openstackgerrit | Matt Riedemann proposed openstack/nova master: Remove dead db api code https://review.openstack.org/454889 | |
| 20:55:05 | mriedem | dansmith: fun one for you ^ | |
| 20:55:55 | dansmith | "fun" | |
| 21:05:13 | student_ | Hi there, I think I have an issue with the nova resources management, I do not have any instance running but it tells me "No valid host was found. There are not enough hosts available." | |
| 21:05:49 | student_ | I think it is a config problem with nova, when I am using "nova hypervisor list" command it brings me empty table | |
| 21:06:29 | student_ | it looks like it is waiting to populate, but I cannot create new instances so it is not working | |
| 21:06:53 | student_ | and I am using newton on Ubuntu 16.04 | |
| 21:15:10 | mriedem | student_: nova hypervisor list being empty means your nova-compute services aren't registered | |
| 21:15:15 | mriedem | there is a problem with the compute nodes checking in to the controller | |
| 21:15:20 | mriedem | has nothing to do with running instances | |
| 21:15:40 | mriedem | this isn't really the channel for debugging that, | |
| 21:15:51 | mriedem | see the channel topic - #openstack is better for general questions like this | |
| 21:21:13 | student_ | mriedem they have send me here :| | |
| 21:21:43 | mriedem | well your compute node isn't checking in so i'd check your nova-compute logs for errors | |
| 21:21:56 | mriedem | and make sure it's configured correctly to talk to the controller | |
| 21:22:26 | student_ | mriedem I have only one server- controller node | |
| 21:22:36 | student_ | my nova-conductor.log http://paste.openstack.org/show/605649/ also nova-scheduler.log file http://paste.openstack.org/show/605647/ | |
| 21:47:48 | efried | student_ First suspect is to check the compute log (might be called nova-compute.log or n-cpu.log) and see if an exception prevented that guy from starting up. | |