Earlier  
Posted Nick Remark
#openstack-nova - 2017-06-20
11:49:04 openstackgerrit OpenStack Proposal Bot proposed openstack/nova master: Updated from global requirements https://review.openstack.org/475563
11:53:30 openstackgerrit Moshe Levi proposed openstack/os-vif master: hardware offload support for openvswitch https://review.openstack.org/460278
11:56:37 openstackgerrit Gábor Antal proposed openstack/nova master: Transform instance.rebuild_scheduled notification https://review.openstack.org/473929
12:30:46 openstackgerrit Jay Pipes proposed openstack/nova master: placement: separate normalize_resources_qs_param https://review.openstack.org/475599
12:30:47 openstackgerrit Jay Pipes proposed openstack/nova master: placement: scheduler uses allocation candidates https://review.openstack.org/475600
12:30:47 openstackgerrit Jay Pipes proposed openstack/nova master: placement: support GET /allocation_candidates https://review.openstack.org/475448
12:36:28 bhagyashris boolman: Hi, you can make sure that the [placement] section is there in the /etc/nova/nova.conf if its not then you should add this and restart the nova compute service.
12:40:08 sfinucan moshele, jaypipes: Am I missing something with https://review.openstack.org/#/c/460278/?
12:40:08 mriedem sdague: when you get some time, can you go through the bottom set of +2ed changes in melwitt's quotas series? starts here: https://review.openstack.org/#/c/446241/ - they are mostly mechanical conversions from old style to new style quota checks.
12:40:11 rfolco jaypipes, could you please review https://review.openstack.org/#/c/460147/ ?
12:40:38 sfinucan fwict, you have nested try-excepts for the same exception. Surely there's no reason for that and the whole thing could be flattened?
12:41:09 sfinucan ...but I can't seem to get that point across in Gerrit, unfortunately :)
12:41:54 sdague mriedem: yeh, probably an hour from now
12:44:54 ftersin mdbooth: hi. any news?
12:51:21 dtantsur dansmith: hi! remember I was talking about nova-api traceback on adding an ironic nova-compute host to an aggregate? here it is https://paste.fedoraproject.org/paste/giaZIJ~cymkC3nNXO1spaA
12:51:29 openstackgerrit Gábor Antal proposed openstack/nova master: Transform instance.resize_prep notification https://review.openstack.org/465081
13:00:56 moshele sfinucan: to me it just a style issue, but I will do the change
13:01:45 moshele sfinucan: sure I will put you as Co-Authored-by :) I will put the patch workflow -1 for now
13:09:20 alex_xu jaypipes: bauzas edleafe, would you remind me about why we put the resource-classes in the extra_specs? I'm thinking of the same question for required_traits in the flavor. Put something new in the extra specs, that means something undiscoverable for the API user, so I didn't understand why.
13:13:32 dtantsur dansmith (or anyone): isn't it doomed to fail: https://github.com/openstack/nova/blob/master/nova/compute/api.py#L4383 ? even my basic deployment has 2 cells (cell0 and default), and the service can be found in both (for whatever reason..)
13:18:26 edleafe alex_xu: IIRC, it's simply an interim solution until we can overhaul the handling of flavors.
13:26:03 sfinucan edleafe: Remind me, most of the operations you refer to in the "Trying to understand the proposed direction" occur in, what, cell 0?
13:26:20 sfinucan except for the actual booting of VM, which occurs in the target cell, of course
13:28:08 sfinucan or the super cell, even
13:31:35 edleafe sfinucan: they occur in placement/scheduler. It is the super conductor that moderates the flow, and eventually dispatches the build to the cell chosen by the scheduler
13:32:04 sfinucan and the scheduler is running outside of the cells?
13:32:13 sfinucan i.e. there isn't a super-scheduler?
13:32:30 edleafe sfinucan: yeah, just one. No per-cell schedulers
13:32:43 sfinucan Gotcha. Thank you :)
13:32:53 edleafe np
13:33:22 dtantsur speaking of which, is there something like "nova cells 101" for absolute beginners?
13:33:47 sfinucan dtantsur: dansmith's talk from the ATL summit it excellent
13:34:00 edleafe sfinucan: remember that what I called the "current flow" isn't what has merged into master; it was the design agreed to before the recent changes
13:34:02 kashyap Yeah, was about to suggest that
13:34:05 dtantsur sfinucan: cool! I've found something from ATX right now
13:34:35 sfinucan edleafe: Yup, I haven't bothered including the "current flow" - just the new one
13:34:46 sfinucan and can -WIP it til code is merged
13:34:48 mriedem dtantsur: those are also linked here https://docs.openstack.org/developer/nova/cells.html
13:34:57 edleafe sfinucan: ok cool
13:35:10 dtantsur sweet. thanks mriedem
13:35:15 boolman bhagyashris: the [placment] section is there, configured and all. ( if missing or incorrect the nova-compute wont start )
13:35:22 dansmith dtantsur: oh you probably have some control services in your cell0 and some computes in cell1, with the same id
13:35:26 dansmith dtantsur: you need mriedem
13:35:29 dansmith er
13:35:32 dtantsur dansmith: this is definitely the case
13:35:37 dtantsur or wait
13:35:39 dansmith dtantsur: you need mriedem's set which is converting that API to uuids
13:35:47 dtantsur what is cell1?
13:36:03 dansmith dtantsur: I just mean "the other cell that is not cell0, the real one"
13:36:15 dtantsur aha
13:36:29 dtantsur so, sorry, what do I need? is there some patch up?
13:36:49 mriedem dtantsur: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/service-hyper-uuid-in-api
13:37:00 mriedem is the wip for converting os-services and os-hypervisors APIs to use uuids
13:37:17 dansmith mriedem: the -2 on that is for microversion sequencing I assume?
13:37:22 mriedem dansmith: yes
13:37:25 mriedem those need to go together
13:37:30 mriedem well, they do'nt need to
13:37:32 mriedem but we said they would
13:37:49 dansmith oh I see the one behind it?
13:37:52 mriedem only thing left in os-hypervisors at the top is docs and paging
13:38:14 dtantsur does it mean that I'll have to stop referring to host names when adding them to aggregates? please pardon my ignorance, I'm not sure how it solves the problem in question
13:38:16 dansmith he needs services
13:38:39 dansmith dtantsur: oh are you getting that while querying for a service by hostname?
13:39:08 dtantsur dansmith: I'm doing $ openstack aggregate add host baremetal-hosts overcloud-controller-0.localdomain
13:39:20 dtantsur do add the ironic host to an aggregate
13:39:38 dansmith I see
13:39:40 dtantsur which may be not a perfect approach to a problem of hybrid bm-vm environment, but that's what we do now
13:39:42 dansmith let me look a bit
13:40:26 dansmith ohhh
13:40:42 dtantsur I don't like this "ohhh" :)
13:40:43 dansmith because you have multiple per host maybe
13:40:57 dansmith hang on, I have no coffee in my system. this is not good.
13:41:05 dtantsur multiple what? I definitely have only one nova-compute process per host..
13:41:09 boolman Hi guys, I'm having trouble with a new deployment.. I'm using juju to deploy ocata, so all the configuration is automated, and yes I have the [placement] section. and I seem to have issues with my compute-nodes/placement API, http://ix.io/xHP http://ix.io/xHO
13:41:19 dtantsur dansmith: sure, lack of coffee is an urgent priority bug :)
13:42:25 dansmith dtantsur: hmm, no this should work.. are you running control services on the same node as a compute?
13:42:33 dtantsur dansmith: I am
13:42:40 dansmith dtantsur: with different config files I assume?
13:42:54 dtantsur dansmith: I don't think so actually
13:43:12 dansmith dtantsur: if not then they wouldn't be in different cells...
13:43:32 dtantsur are cells assigned via nova.conf?
13:43:50 dansmith no, but which cell you check into is determined by which database url you have configured
13:44:32 dtantsur hmm, ok. these hosts may indeed end up in a wrong cell.. however, it does not quite explain to me why we have duplicate hosts exception
13:44:50 dansmith well,
13:44:51 dansmith if they
13:44:53 dansmith are in different cells,
13:45:28 dansmith and they both report the same hostname, then there are multiple services with the same hostname but in different cells
13:46:09 dtantsur they = who? for now it seems that I have nova-api, scheduler and ironic's computes in one cell, then real compute in another
13:46:18 dansmith right
13:46:30 dansmith they = any service (n-api, n-cpu, etc)
13:46:49 dansmith since they have the same hostname as what n-cpu is reporting,
13:47:13 dansmith we could look that service up to find the cell, but end up getting the wrong one
13:47:22 dansmith which is why we now check for dupes and fail if the result is ambiguous
13:47:41 dansmith dtantsur: can we check to see if they are using the same config and thus reporting into the same cell for the moment?
13:49:02 dtantsur dansmith: I have only one nova.conf (provided by puppet, I guess), so I think that's the case
13:49:11 dtantsur I still don't quite understand why the result is ambiguos
13:49:20 dansmith actually, that query should be looking specifically for a nova-compute service, which shouldn't be duplicated if you only have one compute
13:49:26 dansmith dtantsur: that's what we're trying to find out
13:49:30 dtantsur right
13:49:43 dansmith dtantsur: can you dump the services table for your cell0 and other cell databases for me?

Earlier   Later