| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2017-01-13 | |||
| 14:56:28 | amoralej | ok, then i have a new doubt, :) | |
| 14:56:29 | bauzas | it's for failed instances not having a compute node | |
| 14:56:50 | bauzas | ie. when the scheduler returns NoValidHosts, then the instance is mapped to cell0 | |
| 14:56:59 | lyarwood | mdbooth: nope, my change introduces the lookup, previously all the calls made by BlockDevice to libvirt would work with either a path or target dev | |
| 14:57:03 | amoralej | so, for single cell deployments, do i need only cell0 or cell0 and "reall cell" ? | |
| 14:57:05 | bauzas | instead of being mapped to the cell that the compute belongs to | |
| 14:57:17 | mdbooth | lyarwood: Of course. Got it. | |
| 14:57:37 | bauzas | amoralej: for real deployments, you need cell0 *and* a single cell | |
| 14:57:52 | amoralej | ok, understood | |
| 14:58:19 | bauzas | amoralej: that's why we populate cell0 with a db sync | |
| 14:58:35 | bauzas | so that we have everything like if it was a normal cell | |
| 14:58:37 | bauzas | anyway | |
| 14:58:47 | bauzas | EmilienM: amoralej: so, in order to tackle your problem | |
| 14:59:51 | bauzas | https://github.com/openstack/nova/commit/a18f601753f92ff4a2a42be0962a188f583bbfb9 just canary-tested an existing problem | |
| 15:00:13 | bauzas | because previously, it was returning 0 as you were already having a cell0 | |
| 15:00:20 | bauzas | now, we're going past this point | |
| 15:02:02 | amoralej | yes bauzas, i'm going to summarize this findings in the LP | |
| 15:05:19 | mandy | hi | |
| 15:06:32 | mandy | could you anyone help me ?? | |
| 15:08:12 | bauzas | amoralej: so, just verified and FWIW, we create cells (and run the single cell command) *after* starting n-cpu in devstack | |
| 15:08:18 | bauzas | EmilienM: ^ | |
| 15:08:29 | bauzas | that's why the upstream nova jobs aren't trampled | |
| 15:08:35 | figleaf | mandy: just ask your question. | |
| 15:08:41 | openstackgerrit | Davanum Srinivas (dims) proposed openstack/nova: [WIP] try py35 functional with a clean slate https://review.openstack.org/419968 | |
| 15:09:01 | amoralej | bauzas, could you take a look to comment #3 in https://bugs.launchpad.net/nova/+bug/1656276 and confirm if it's right? | |
| 15:09:01 | openstack | Launchpad bug 1656276 in tripleo "Error running nova-manage cell_v2 simple_cell_setup when configuring nova with puppet-nova" [Critical,Triaged] | |
| 15:10:39 | mandy | actualy i am successfully create one vm in openstack using devtsack | |
| 15:11:01 | mandy | * devstack but unable to ping that vm ....could you plz help me | |
| 15:11:02 | mandy | ?? | |
| 15:11:34 | EmilienM | bauzas: interesting | |
| 15:11:41 | EmilienM | bauzas: link? | |
| 15:12:09 | mandy | i used private network | |
| 15:12:56 | mandy | is anyone there | |
| 15:12:57 | mandy | ?? | |
| 15:13:26 | mriedem | ceph job is now non-voting, fyi | |
| 15:13:29 | openstackgerrit | sahid proposed openstack/nova: compute: reset instance events https://review.openstack.org/420026 | |
| 15:13:56 | diana_clarke | mandy: Those kinds of support/usage questions don't typically get answered here (see channel topic). | |
| 15:14:08 | mandy | ok | |
| 15:14:11 | mandy | thanks | |
| 15:14:13 | mandy | bye | |
| 15:16:35 | EmilienM | mwhahaha: out of your mind, would it be doable to run this cell_v2 simple_cell_setup *after* starting nova-compute in tripleo? | |
| 15:16:44 | EmilienM | mwhahaha: I'm wondering about the steps | |
| 15:17:02 | bauzas | EmilienM: http://logs.openstack.org/90/409890/1/check/gate-tempest-dsvm-neutron-full-ubuntu-xenial/447ab55/logs/devstacklog.txt.gz#_2016-12-12_21_54_28_042 | |
| 15:17:13 | mriedem | mdbooth: how are you feeling about https://review.openstack.org/#/c/312488/ ? | |
| 15:17:16 | bauzas | (sorry, in internal meeting now) | |
| 15:17:26 | mriedem | the vz ci is running test_verify_created_server_ephemeral_disk now | |
| 15:17:36 | openstackgerrit | Vasyl Saienko proposed openstack/nova: Implement interface attach/detach in ironic virt driver https://review.openstack.org/419975 | |
| 15:17:55 | openstackgerrit | Vasyl Saienko proposed openstack/nova: Implement interface attach/detach in ironic virt driver https://review.openstack.org/419975 | |
| 15:18:02 | mwhahaha | why is this cell v2 setup stuff so complex | |
| 15:18:13 | mdbooth | mriedem: In a meeting. Get back in an hour or so. | |
| 15:18:37 | mwhahaha | it's so not 'simple' if you require cross node coordination prior to running it | |
| 15:19:00 | amoralej | EmilienM, i can start by removing the command as part of nova::db::sync and adding it at the end in p-o-i | |
| 15:19:12 | amoralej | that would be the first step, am i right? | |
| 15:19:26 | amoralej | mwhahaha ^ | |
| 15:19:37 | mwhahaha | no | |
| 15:19:44 | mwhahaha | it's lined up in the nova::deps | |
| 15:19:52 | EmilienM | amoralej: change needs to happen in puppet-nova, not poi (if we have to change something) | |
| 15:19:56 | EmilienM | right | |
| 15:20:07 | mwhahaha | https://github.com/openstack/puppet-nova/blob/master/manifests/deps.pp#L23-L26 | |
| 15:20:55 | mwhahaha | also we would need to remove https://github.com/openstack/puppet-nova/blob/master/manifests/db/sync_api.pp#L45-L47 | |
| 15:21:24 | amoralej | this one is the one i have seen, not the deps stuff | |
| 15:21:50 | mwhahaha | we would want to touch both because we want to run sync after compute service starts | |
| 15:22:08 | mwhahaha | i still don't understand why these things keep getting added as hard requirements after the fact | |
| 15:22:29 | mwhahaha | first it was the db upgrade that broke everything and now it's you have to run it after computes, is any of this stuff documented? | |
| 15:22:48 | EmilienM | I agree it's not easy for deployers :( | |
| 15:22:48 | bauzas | EmilienM: amoralej: so, about a very short-term fix, here are my thoughts | |
| 15:22:57 | EmilienM | mriedem: ^ fyi | |
| 15:23:00 | amoralej | not really mwhahaha, i've spent the whole morning trying to understand it | |
| 15:23:26 | mwhahaha | i've probably wasted over a month on this stuff and operators are expected to use it? | |
| 15:23:30 | bauzas | EmilienM: amoralej: while I understand the point that it could be fancy for operators to have a way to automatically add the cell mapping when starting the compute, that's not written yet | |
| 15:24:07 | mwhahaha | why is cell v2 being a hard requirement if docs and the code aren't written yet? | |
| 15:24:14 | bauzas | EmilienM: amoralej: here, instead, in order to punt your problem, I'd rather recommend you to modify https://github.com/openstack/puppet-nova/blob/master/manifests/db/sync_cell_v2.pp#L32 and accept return codes to be 0 and 1 | |
| 15:24:16 | amoralej | bauzas, and requiring to run discover_hosts after every new compute nodes should be automated too, imho | |
| 15:24:39 | EmilienM | bauzas: but would tables be created in DB? | |
| 15:24:51 | mwhahaha | bauzas: that still doesn't handle the upgrade case where we need to have it created before we run the api sync for n ->o | |
| 15:24:59 | mwhahaha | bauzas: that's not acceptable | |
| 15:25:09 | bauzas | EmilienM: amoralej: it would put your CI back green, but would still require the cell command to be run *after* starting the compute | |
| 15:25:41 | bauzas | mwhahaha: upgrade is a very different case | |
| 15:25:48 | bauzas | mwhahaha: because you already have computes | |
| 15:26:09 | mwhahaha | bauzas: please point me to the documentation for upgrades vs install of cell v2 | |
| 15:26:46 | bauzas | mwhahaha: here, the discussion is about the critical bug that tramples both puppet users and the TripleO CI | |
| 15:27:00 | bauzas | I'm just trying to tackle the problem asp | |
| 15:27:02 | bauzas | asap | |
| 15:27:15 | mwhahaha | this problem has existed in one form or another for more than a month | |
| 15:27:34 | mwhahaha | and every time we make progress, nova checks a change that completely destroys what we thought the process was previously | |
| 15:27:46 | mwhahaha | so i'd like not to have to repeat this again in a week | |
| 15:28:09 | mwhahaha | so we all understand how this thing is supposed to work, is there any documentation around how this is expected to function | |
| 15:28:43 | bauzas | mwhahaha: http://docs.openstack.org/releasenotes/nova/unreleased.html#id2 can help you | |
| 15:28:47 | EmilienM | I agree this thing is complex to deploy outside devstack | |
| 15:28:52 | EmilienM | specially in production | |
| 15:28:53 | bauzas | "Ocata requires that your deployment have created the cell and host mappings in Newton. If you have not done this, Ocata’s db sync command will fail. Small deployments will want to run nova-manage cell_v2 simple_cell_setup on Newton before upgrading. Operators must create a new database for cell0 before running cell_v2 simple_cell_setup. The simple cell setup command expects the name of the cell0 database to be <API database | |
| 15:29:02 | mwhahaha | bauzas: that's what we're doing | |
| 15:29:10 | mwhahaha | bauzas: but no mention of discover hosts or anything else | |
| 15:29:17 | mwhahaha | also release notes != documentation on the overall process | |
| 15:29:49 | EmilienM | it doesn't mention ordering with nova-compute process, does it? | |
| 15:33:20 | bauzas | EmilienM: well, that's because we added the simple cell command in Newton :( | |
| 15:33:27 | bauzas | EmilienM: to answer your question, http://docs.openstack.org/releasenotes/nova/unreleased.html#id10 | |
| 15:35:01 | openstackgerrit | Davanum Srinivas (dims) proposed openstack/nova: [py35] Fixes to get rally scenarios working https://review.openstack.org/419476 | |
| 15:35:26 | mriedem | so docs is a known gap, i.e. docs that aren't release notes | |
| 15:35:34 | mriedem | i think dansmith was working on a blog post to start that, | |