Earlier  
Posted Nick Remark
#openstack-nova - 2018-12-12
17:41:56 sean-k-mooney yes neutron allows you to add multiple subnets to the same network
17:42:19 sean-k-mooney you will need to add the second subnet to the router also
17:43:29 spatel I have VLAN base networking not tenant base..
17:43:44 spatel This is the command i used to create my first subnet..
17:43:48 spatel neutron subnet-create net_pub_vlan_200 71.xxx.xxx.0/24 --name sub_pub_vlan_200 --allocation-pool start=71.xxx.xxx.2,end=71.xxx.xxx.254 --dns-nameservers 8.8.8.8 --gateway=71.xxx.xxx.1
17:44:17 sean-k-mooney spatel: we should peroably swap to the neutron channel but that is fine
17:45:03 sean-k-mooney vlan networks are still teant networks the terminology is a littel overloaded
17:45:10 spatel You are saying i add just add new public IP in same "net_pub_vlan_200" network?
17:45:55 sean-k-mooney yes you can
17:46:15 spatel Something like this?
17:46:36 spatel neutron subnet-create net_pub_vlan_200 72.xxx.xxx.0/24 --name new_subnet_vlan_200 --allocation-pool start=72.xxx.xxx.2,end=72.xxx.xxx.254 --dns-nameservers 8.8.8.8 --gateway=72.xxx.xxx.1
17:46:55 sean-k-mooney yep
17:46:58 spatel net_pub_vlan_200 will be same right?
17:47:13 spatel perfect!! thanks for confirmation :)
17:47:46 sean-k-mooney the only other thing you need to do is add a new prot to the openstack or phyical router to connect to the new subnet
17:48:07 spatel new port?
17:49:09 sean-k-mooney if you are using a phyical provider router you need to asing 72.xxx.xxx.1 to it so it can act as a gatway but if you are using neutron routers then you just need to add a port on the neutron router to connet to n 72 subnet
17:50:45 spatel oh! yes i am running HSRP so yes.. i have to setup HSRP on my gateway switches :)
17:50:52 sean-k-mooney spatel: you can use the openstack router add subnet <route> 72.xxx.xxx.2
17:52:10 sean-k-mooney ah ok then ya you are using phyical routers instead of neutron routers for you public network so you can skip the openstack router add subnet command
17:59:21 spatel yes!!
18:00:04 spatel sean-k-mooney: quick question, now i am planning to build new Openstack cloud with NATing style floating ip, not VLAN base
18:00:31 spatel how do i scale that network? we have super high PPS rate in network... does virtual router can handle that traffic?
18:00:47 spatel I have option for DVR
18:01:59 sean-k-mooney spatel: lets take the converstation to #openstack-neutron
18:06:50 spatel sean-k-mooney: thanks :)
18:07:50 mriedem dansmith: can you think of anything besides flavor that we would have data migrated from system_metadata in the meta-api? i was thinking keypairs but that was different i think - it was a separate table and the data was migrated to extras
18:08:16 dansmith yeah, not keypairs
18:08:34 dansmith nothing off the top of my head, but I haven't thought about it much
18:18:31 openstackgerrit Matt Riedemann proposed openstack/nova master: Be smarter about DB joins in the metadata API https://review.openstack.org/624778
18:18:32 mriedem easy peasy ^
18:47:15 openstackgerrit Chris Dent proposed openstack/nova master: Use external placement in functional tests https://review.openstack.org/617941
18:50:24 openstackgerrit Chris Dent proposed openstack/nova master: Delete the placement code https://review.openstack.org/618215
21:08:30 openstackgerrit Matt Riedemann proposed openstack/nova stable/rocky: Handle tags in _bury_in_cell0 https://review.openstack.org/624813
21:43:47 brandor5 hello everyone: can anyone tell me where I can find the newton nova api reference?
21:48:07 jonher brandor5: this? https://developer.openstack.org/api-ref/compute/
21:48:31 brandor5 jonher: that's latest, I need the one for newton
21:49:07 brandor5 I'm trying to use the api to confirmResize after a migrate and I'm getting an error
21:49:16 brandor5 Cannot 'confirmResize' instance e1782f5c-7559-4cac-a628-6d4a75a015f4 while it is in vm_state stopped
21:50:04 brandor5 If i run `nova resize-confirm <instance_id>` it works and I'm running the same curl that it runs...
21:51:05 mriedem brandor5: the api-ref on master should be the same for newton - where there are functional differences they should be called out with notes or microversions
21:51:13 mriedem i.e. the api should be backward compatible
21:51:27 brandor5 mriedem: oh cool, thanks... any idea on the error I'm seeing?
21:51:38 brandor5 especially that it works when I use the command line client
21:52:18 mriedem can't confirm a resize on a stopped vm in newton https://github.com/openstack/nova/blob/newton-eol/nova/compute/api.py#L2924
21:52:38 mriedem nor master https://github.com/openstack/nova/blob/master/nova/compute/api.py#L3489
21:53:19 brandor5 hmm that's weird because `nova resize-confirm <instance id>` definitely works
21:53:32 mriedem works works? or just doesn't say it failed?
21:53:38 brandor5 works works
21:53:40 mriedem which version of novaclient?
21:53:56 brandor5 10.1.0
21:54:29 brandor5 and when I run nova in debug I've verified that I'm running the same 'curl' that novaclient is running
21:55:05 mriedem no magic there https://github.com/openstack/python-novaclient/blob/10.1.0/novaclient/v2/servers.py#L1533
21:55:44 mriedem can you show the server status before doing each (cli and curl) to verify?
21:56:10 brandor5 yeah, I'm doing that... I have a watch running `openstack server show <instance_id>`
21:56:29 brandor5 if I try to hit the api directly I get a 409
21:56:36 mriedem so you have some script or something that's just auto-confirming a resize as soon as the instance status is VERIFY_RESIZE?
21:56:37 brandor5 if I use novaclient it works
21:56:44 brandor5 correct
21:56:56 mriedem there is a config option for auto-confirming migrations
21:56:58 mriedem ..
21:57:33 brandor5 yeah, that's across the board and the docs say it's not recommended... my script is just for putting a compute into 'maintenance' mode
21:58:22 brandor5 It's actually ansible playbook that sets maintenance mode, checks for errored instances, manually moves shutoff instances, and then blasts the active instances'
21:59:11 brandor5 unfortunately right now I can't use the command line clients because ansible tower doesn't have them installed... (that's a ticket i have open with redhat)
21:59:21 mriedem gd red hat
21:59:31 mriedem i can't see anything that would be a difference between the client and straight curl
21:59:32 brandor5 haha
21:59:46 brandor5 i'll keep poking then... double check my headers and whatnot
21:59:55 brandor5 thanks for the help
22:00:09 mriedem are you polling on the 'status' field in the server show response or something like vm_state?
22:01:08 brandor5 https://pastebin.com/ijVe0J42
22:01:31 melwitt mriedem: what's the trick to bfv with more than one --block-device? I keep getting ERROR state saying 'no image supplied' even though the first one I give is bootindex=0 with source=image
22:02:06 mriedem brandor5: that looks ok
22:02:35 mriedem melwitt: are you trying to attach data volumes or have nova create the volumes?
22:02:54 mriedem it's probably easiest to just boot and attach 2 data volumes (so not boot_index=0)
22:03:08 melwitt mriedem: I'm consistently trying to have nova create the boot volume, and attach a non-bootable volume I created in cinder ahead
22:03:09 mriedem i.e. pre-existing volumes
22:03:27 mriedem what is your source_type and destination_type?
22:04:07 melwitt this was my latest attempt http://paste.openstack.org/show/737169/
22:04:32 mriedem --block-device source=image,id=d7b0d7cb-1373-456d-bcec-29fbec2f84e1,dest=volume,size=1,shutdown=preserve,bootindex=0
22:04:35 mriedem is that id an image id?
22:04:45 melwitt yes
22:04:51 mriedem --block-device source=volume,id=33550efe-6a7b-4956-a7e0-5bd50004ec30,dest=volume,size=1,shutdown=preserve
22:04:54 mriedem and that id is a volume id?
22:04:57 melwitt and that one is a volume id
22:05:13 mriedem you don't need to specify size on the latter, but nova should ignore that
22:05:36 melwitt I think it can be done but I don't know how. I think I've seen launchpad bug reports where people were booting with multiple volumes
22:06:09 mriedem where are you seeing the "no image supplied"?
22:06:27 melwitt in the nova show fault field
22:06:32 mriedem http://codesearch.openstack.org/?q=no%20image%20supplied&i=nope&files=&repos=
22:06:40 mriedem that's not in the code that i can see
22:06:43 mriedem besides the show response
22:06:48 mriedem which is normal
22:06:53 mriedem paste your fault
22:07:40 melwitt http://paste.openstack.org/show/737170/
22:07:56 melwitt oh sorry
22:07:57 melwitt dammmit
22:08:05 melwitt that was the image field
22:08:34 Kevin_Zheng mriedem: just shelve the vm and all the volume will be in reserved status and cannot be detached
22:08:36 mriedem yeah that's normal

Earlier   Later