Earlier  
Posted Nick Remark
#openstack-nova - 2017-03-16
09:51:10 alexey_weyl gibi: no problem. thanks :)
09:52:01 bauzas gibi: in theory, once you accept an instance to be created on that AZ, then your contract becomes harder
09:52:18 bauzas because some people trust you for caring their instances
09:52:30 gibi bauzas: true.
09:53:42 gibi bauzas: what if just the az name needs to be changed but not the meanin of it? I mean the renamed az still means the same failure domain.
09:54:21 bauzas gibi: what I need to understand is why operators need to update their AZ names
09:54:33 bauzas it's just a string
09:54:42 gibi bauzas: renaming the room in the building? :)
09:54:57 bauzas so they would expose their topology semantically?
09:55:16 jith Hi all, I have configured openstack kilo setup in debian jessie with one controller node and two compute nodes. I have used glusterfs for shared storage. I have mounted the shared storage in /var/lib/nova/instances on both nodes. I can do migration of vms between nodes.. But live-migration throws following error.. Pls do guide me.. http://pastebin.com/DHPWEkaZ
09:55:24 gibi bauzas: you are right. My point is not really valid.
09:55:37 gibi bauzas: anyhow I'm just playing devils advocate here.
09:55:47 bauzas jith: I'm sorry, this channel is focused on development questions
09:56:00 bauzas gibi: nah it's fine, I could be wrong
09:56:28 gibi bauzas: az name should not reflect real topology. It should be failure domain A , B etc
09:56:47 bauzas gibi: the only problem I see with preventing the AZ rename is that it's becoming hard to migrate instances
09:56:47 gibi bauzas: so your point seems OK to me
09:57:01 bauzas say I made a mistake and I want to fix that
09:57:14 gibi bauzas: does admin can migrate instance by ignoring AZ?
09:57:25 bauzas migi: he could force the migration
09:57:42 bauzas oops
09:57:47 bauzas s/migi/gibi
09:57:53 migi :)
09:57:56 gibi bauzas: force migration could work for me
09:58:00 gibi migi, bauzas: :)
09:58:23 openstackgerrit Stephen Finucane proposed openstack/nova master: tests: Validate huge pages https://review.openstack.org/399653
09:58:24 openstackgerrit Stephen Finucane proposed openstack/nova master: libvirt: create functional test base class https://review.openstack.org/407055
09:58:37 bauzas anyway, migrating from one AZ to another is a big deal
09:59:03 sfinucan jaypipes: Fixed that hugepages functional test https://review.openstack.org/#/c/399653/
10:00:06 bauzas gibi: since one host can't be in two AZs at the same time, I'd suggest to place the host on a specific aggregate that is not AZ-facing
10:00:29 bauzas gibi: and then move the host to the new aggregate with the right AZ name
10:00:59 bauzas rather than issuing a live-migration
10:01:49 bauzas I should test that in devstack
10:03:52 mdbooth lyarwood (or anybody else): Do you know what would consume volume.detach instance notifications?
10:04:41 gibi bauzas: ohh, I see
10:05:52 lyarwood mdbooth: no sorry
10:06:00 lyarwood mdbooth: is this regarding the ordering change?
10:06:19 mdbooth lyarwood: Yeah
10:06:27 mdbooth Also, the notification should probably live with the detach
10:11:41 mdbooth lyarwood: Yeah, reading the contract on those notifications, notifying after makes more sense to me.
10:14:27 sfinucan jlvillal: https://review.openstack.org/#/c/445622/1
10:15:48 openstackgerrit Mikhail Feoktistov proposed openstack/nova master: Add is_vz_container function https://review.openstack.org/445947
10:21:09 sfinucan sean-k-mooney, jaypipes: Shouldn't this be in os-vif? https://review.openstack.org/#/c/441183/
10:33:35 mdbooth We've had references to Cinder attachment_id in Nova since Mitaka
10:33:42 mdbooth lyarwood: ^^^
10:34:01 jith Hi all, I have configured openstack kilo setup in debian jessie with one controller node and two compute nodes. I have used glusterfs for shared storage. I have mounted the shared storage in /var/lib/nova/instances on both nodes. I can do migration of vms between nodes.. But live-migration throws following error.. Pls do guide me.. http://pastebin.com/DHPWEkaZ
10:34:18 mdbooth lyarwood: What am I missing there?
10:34:30 lyarwood mdbooth: yeah cinderv2 attachment_id's
10:34:42 openstackgerrit Stephen Finucane proposed openstack/nova master: Replace obsolete vanity openstack.org URLs https://review.openstack.org/443266
10:34:45 mdbooth How are they different?
10:35:05 lyarwood mdbooth: I think they are only optional when detaching
10:35:06 mdbooth Are the underlying objects the same?
10:35:16 lyarwood mdbooth: on the Cinder side? I have no idea.
10:35:25 lyarwood mdbooth: but in the API yes
10:35:35 lyarwood mdbooth: that's all we care about right?
10:35:47 mdbooth So a cinderv2 attachment_id is the same as a cinderv3 attachment_id
10:35:53 mdbooth i.e. the uuid values are the same
10:36:01 lyarwood mdbooth: that I don't know
10:36:06 openstackgerrit Stephen Finucane proposed openstack/nova master: Replace obsolete vanity openstack.org URLs https://review.openstack.org/443266
10:36:06 gibi mdbooth, lyarwood: I think we you want to change when the volume.detach is sent then it would make sense to send a detach.start and a detach.end
10:36:30 mdbooth gibi: Out of scope for this change, tbh.
10:36:36 mdbooth Waaaaaaaaay out of scope
10:36:47 gibi mdbooth: then let's not change when to send the volume.detach :)
10:36:47 lyarwood gibi: but I can follow up with that after
10:37:07 gibi lyarwood: I think it is not super important
10:38:08 mdbooth lyarwood gibi: I don't know enough about the practical uses of notifications to know how important that order change is, but if there's any doubt we should leave it alone
10:38:36 mdbooth It's not at all relevant to lyarwood's change
10:39:00 mdbooth lyarwood: So that means moving the notification with the detach call
10:39:37 lyarwood mdbooth: sure, then the notification comes before bdm.destroy
10:40:04 mdbooth lyarwood: I don't see a problem with that.
10:40:14 gibi mdbooth, lyarwood: OK
10:41:06 openstackgerrit John Garbutt proposed openstack/nova-specs master: Add policy-remove-scope-checks spec https://review.openstack.org/433037
10:41:14 openstackgerrit John Garbutt proposed openstack/nova-specs master: Add additional-default-policy-roles spec https://review.openstack.org/427872
10:41:15 mdbooth lyarwood: As I see it, it's more about the behaviour when detach fails, tbh
10:41:35 lyarwood mdbooth: true
10:42:02 openstackgerrit Sylvain Bauza proposed openstack/nova-specs master: Proposed block accepting AZ renames https://review.openstack.org/446446
10:42:15 lyarwood mdbooth: I need to run for a dentist appointment, back in ~90mins or so.
10:42:23 lyarwood mdbooth: are you around for the cinder/nova meeting later today?
10:42:30 mdbooth lyarwood: kk
10:42:44 mdbooth lyarwood: Possibly. Talk later.
10:42:52 lyarwood mdbooth: ack, thanks
11:03:21 openstackgerrit Sean Dague proposed openstack/nova master: remove hacking rule that enforces log translation https://review.openstack.org/446452
11:22:40 openstackgerrit Jianghua Wang proposed openstack/nova master: XenAPI: device tagging https://review.openstack.org/333781
11:23:45 openstackgerrit Bing Li proposed openstack/nova master: Add server-action-removefloatingip.json file and update servers-actions.inc https://review.openstack.org/446471
11:30:22 gibi dansmith: Hi! I left some suggestion in https://review.openstack.org/#/c/445697
11:43:50 gibi alexey_weyl: I checked the aggregate notification in a new devstack from master.
11:44:02 gibi alexey_weyl: It works for me. See the logs in http://paste.openstack.org/show/602943/
12:06:41 alexey_weyl gibi: Hi
12:07:41 alexey_weyl gibi: I have checked it also, and i saw that notifications work for vitrage with master. but still notifications don't work on liberty (notifications about the aggregated hosts)
12:10:05 gibi alexey_weyl: I don't have access to Liberty test node right now. Also Liberty is already reached end of support
12:10:48 gibi alexey_weyl: so even if it is buggy we cannot fix it on Liberty
12:14:37 alexey_weyl gibi: ok, i see that, and it is ok. but I have some other issue
12:15:25 alexey_weyl gibi: The thing is that for example in devstack when you create it, you don't have an "aggregated host" but we have AZs.
12:16:41 alexey_weyl gibi: After our talk before I thought that I could use only the Aggregated hosts to get the needed data, but it seems that I would need to get the AZs by calling the availability-zone list and thus because it doesn't has id we have a problem
12:17:03 mdbooth lyarwood: You back?
12:19:01 robcresswell Quick question; someone's added a patch to Horizon that hides the Soft Reboot button if the Instance state is anything other than Active; is this correct? Had a look at the API docs but they only seem to show how to form the request, not any of the conditions around its usage.
12:19:54 mdbooth robcresswell: soft reboot doesn't make sense for an instance which isn't running
12:20:38 robcresswell mdbooth: Yeah, I'm not clued in on every specific status nova supports
12:20:44 mdbooth error, perhaps
12:21:30 mdbooth robcresswell: I mean, regardless of what the api allows, from a UI pov that restriction makes sense to me

Earlier   Later