| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2018-12-03 | |||
| 10:52:41 | bauzas | I agree | |
| 10:53:06 | bauzas | the only thing I could think of would be cpu_mode explicitely set to None | |
| 10:53:48 | izza_ | [libvirt] | |
| 10:53:50 | bauzas | which would make the guest using a very old CPU model that doesn't support SSE1 | |
| 10:53:53 | bauzas | SSE4* | |
| 10:54:04 | izza_ | live_migration_uri = qemu+ssh://stack@%s/system | |
| 10:54:10 | izza_ | cpu_mode = host-passthrough | |
| 10:54:16 | izza_ | cpu_model_extra_flags = sse4_1 | |
| 10:54:22 | izza_ | virt_type = kvm | |
| 10:54:47 | sean-k-mooney | izza_: host-passthrough will give you the same feature flags as the host. you dod not need the extra flags | |
| 10:55:14 | izza_ | noted on this..we will remove it.. | |
| 10:55:23 | sean-k-mooney | izza_: you have sse in the hosts /proc/cpuinfo right? | |
| 10:55:39 | izza_ | but we tried to remove it and set is as passthrough without flags | |
| 10:55:48 | izza_ | but still unable to get the other flags | |
| 10:56:07 | sean-k-mooney | every xeon since nehelem has had sse 4.2+ | |
| 10:56:26 | izza_ | yes, sse4.1 is available in /proc/cpuinfo | |
| 10:56:52 | sean-k-mooney | izza_: and your setting cpu_mode = host-passthrough in the /etc/nova/nova-cpu.conf | |
| 10:58:01 | izza_ | it is set as "none" in /etc/nova/nova-cpu.conf | |
| 10:58:12 | sean-k-mooney | izza_: that the issue | |
| 10:58:30 | izza_ | what should i do? | |
| 10:58:36 | sean-k-mooney | /etc/nova/nova-cpu.conf is used by the compute agent /etc/nova/nova.conf is used by the schduer/conductor | |
| 10:59:07 | izza_ | ok will try to change it | |
| 10:59:57 | izza_ | we will advise you for the result | |
| 11:00:08 | sean-k-mooney | [[post-config|$NOVA_CPU_CONF]] | |
| 11:00:11 | sean-k-mooney | [libvirt] | |
| 11:00:13 | sean-k-mooney | cpu_mode = host-passthrough | |
| 11:00:15 | sean-k-mooney | virt_type = kvm | |
| 11:00:19 | sean-k-mooney | that is how to set it in your local.conf by the way | |
| 11:00:51 | izza_ | ok noted on that | |
| 11:00:54 | izza_ | we'll try | |
| 11:01:00 | sean-k-mooney | you can change it locally and then restart the nova services with sudo systemctl restart devstack@n-* | |
| 11:01:20 | bauzas | what sean-k-mooney said | |
| 11:01:30 | sean-k-mooney | * by locally i mean in /etc/nova/nova-cpu.conf | |
| 11:01:34 | bauzas | izza_: your n-cpu service uses the wrong file | |
| 11:01:36 | izza_ | thanks guys | |
| 11:04:40 | sean-k-mooney | bauzas: well a different file we use /etc/nova/nova-cpu.conf instead of /etc/nova/nova.conf intentionally | |
| 11:04:49 | izza_ | got it...already capture the cpu details after changing the said file | |
| 11:05:11 | bauzas | 'wrong' is maybe not the right word | |
| 11:05:28 | bauzas | what I mean is that n-cpu uses another conf file by default | |
| 11:05:31 | bauzas | but you can change this | |
| 11:05:45 | sean-k-mooney | yep | |
| 11:05:56 | bauzas | just don't use systemctl in this case | |
| 11:06:11 | sean-k-mooney | ya not? | |
| 11:06:25 | sean-k-mooney | *why not? | |
| 11:06:50 | bauzas | just becauses it precludes the config file name | |
| 11:07:08 | bauzas | sometimes I prefer stopping the service and starting it by hand | |
| 11:07:21 | bauzas | maybe because I'm an old guy | |
| 11:07:40 | sean-k-mooney | systemctl is the correct way to do that in devstack for like 2-3 releases | |
| 11:08:12 | sean-k-mooney | infact that devstack docs use n-cpu as the example https://docs.openstack.org/devstack/latest/systemd.html#manipulating-units | |
| 11:14:37 | jangutter | bauzas: I'm still sometimes using 'ifconfig', where I should be using 'ip', and really, really, should be using 'nmcli'. | |
| 11:14:50 | bauzas | sean-k-mooney: you misunderstood me | |
| 11:15:19 | bauzas | sean-k-mooney: I'm not saying to not use systemctl (although there is still a devstack option for it :p ) | |
| 11:15:56 | bauzas | sean-k-mooney: I'm saying that, most of the times, stopping the incriminated service and restarting it by hand is preferrable | |
| 11:16:07 | sean-k-mooney | bauzas: noop the screen option was removed in rocky | |
| 11:16:15 | bauzas | gtk | |
| 11:16:44 | sean-k-mooney | oh you mean sudo systemctl stop devstack@n-cpu.service the nova-coumpute ... | |
| 11:17:29 | sean-k-mooney | runing the service directly can be usefaul for debuging | |
| 11:20:06 | jangutter | One thing I like is that I can go 'systemctl status PID' and get all the startup (and a bit of logs) for a service. | |
| 11:20:21 | jangutter | Is there something similar for docker/containers? | |
| 11:20:55 | sean-k-mooney | jangutter: docker logs <container name or id> | |
| 11:21:47 | sean-k-mooney | or depeneding on your container it may log to the hosts journal so journalctl -u <service in contienr> | |
| 11:30:41 | ShilpaSD | hi: All, please help me to understand, how this section, table format of notificaiotns, is added here 'https://docs.openstack.org/nova/rocky/reference/notifications.html#existing-versioned-notifications' | |
| 11:31:48 | izza_ | hi | |
| 11:32:28 | izza_ | encounetered error upon execution of tensorflow session | |
| 11:32:29 | izza_ | >>> sess = tf.Session() | |
| 11:33:01 | izza_ | 2018-12-03 11:30:11.110534: I tensorflow/core/platform/cpu_feature_guard.cc:141] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2 FMA | |
| 11:33:08 | izza_ | raceback (most recent call last): | |
| 11:33:48 | izza_ | were using tensorflow 1.11.0 | |
| 11:34:10 | izza_ | we tried to upgrafe it to tensorflow 1.12.0 but same error | |
| 11:39:24 | gibi | ShilpaSD: let me find the code that generates that table... | |
| 11:39:49 | gibi | ShilpaSD: here is the code that generates the table https://github.com/openstack/nova/blob/master/doc/ext/versioned_notifications.py | |
| 11:39:50 | ShilpaSD | gibi: thanks for that | |
| 11:41:05 | ShilpaSD | gibi: how to configure this with notifications.rst? | |
| 11:41:09 | ShilpaSD | the linking? | |
| 11:41:58 | ShilpaSD | gibi: what this line is doing exactly? https://github.com/openstack/nova/blob/master/doc/source/conf.py#L46 | |
| 11:43:24 | gibi | ShilpaSD: the conf.py line: ext.versioned_notifications instructs sphinx to load and run https://github.com/openstack/nova/blob/master/doc/ext/versioned_notifications.py#L54 | |
| 11:48:42 | ShilpaSD | gibi:i if i have this value set this getting 'ERROR: InvocationError for command '/opt/stack/<CODE BASE>/.tox/docs/bin/python setup.py build_sphinx' (exited with code 1)' error ehile docs creation, what action i need to take? | |
| 11:49:52 | ShilpaSD | this is i have added >> extensions = ['sphinx.ext.autodoc', 'oslosphinx','ext.versioned_notifications'] | |
| 11:50:19 | ShilpaSD | is i am missing any other supporting extensions? | |
| 11:51:27 | gibi | ShilpaSD: I don't know. This is the original commit added the notification extension https://github.com/openstack/nova/commit/05adc8d006b482e0aed2fcc9dc4885924aca74d0 | |
| 11:51:39 | gibi | ShilpaSD: in that I did not have to add any extra extension | |
| 11:52:12 | gibi | ShilpaSD: btw, what do you want to achive? do you want to reuse ext.versioned_notifications outside of the nova project? | |
| 11:55:11 | gibi | ShilpaSD: if I insert some python error to ext/versioned_notifications.py then doc generation command prints a proper stack trace for me | |
| 11:56:09 | gibi | ShilpaSD: nova uses the following build command in tox: sphinx-build -W -b html -d doc/build/doctrees doc/source doc/build/html | |
| 11:57:58 | gibi | ShilpaSD: this part of the conf.py in nova could be intresting to you as well https://github.com/openstack/nova/blob/master/doc/source/conf.py#L24 | |
| 12:03:48 | ShilpaSD | gibi: Hi, i am in the process of introducing notifications in Masakari, i have completed all coding and api doc, not only part remained is this sample notifications table | |
| 12:05:36 | gibi | ShilpaSD: so you copied ext/versioned_notifications.py from nova to masakari and would like to use it in masakari | |
| 12:05:49 | ShilpaSD | gibi: yes | |
| 12:06:05 | gibi | ShilpaSD: do you have a patch up on review that I can download and play with it locally? | |
| 12:07:09 | ShilpaSD | gibi: sorry for that, as of now no patch i have uploaded | |
| 12:08:09 | ShilpaSD | gibi: during tox, its giving error while 'Running Sphinx v1.8.2' | |
| 12:09:13 | openstackgerrit | Balazs Gibizer proposed openstack/nova master: Reject networks with QoS policy https://review.openstack.org/570079 | |
| 12:09:13 | openstackgerrit | Balazs Gibizer proposed openstack/nova master: Reject interface attach with QoS aware port https://review.openstack.org/570078 | |
| 12:10:33 | openstackgerrit | Balazs Gibizer proposed openstack/nova master: Reject networks with QoS policy https://review.openstack.org/570079 | |
| 12:11:04 | openstackgerrit | Chris Dent proposed openstack/nova master: Clean up header encoding handling in compute API https://review.openstack.org/606967 | |
| 12:11:06 | gibi | ShilpaSD: let me try to reproduce yor problem locally | |
| 12:13:29 | ShilpaSD | gibi: thanks for this | |
| 12:22:57 | gibi | ShilpaSD: with this change https://review.openstack.org/621558 I can make sphinx load the extension in masakari | |
| 12:23:23 | gibi | ShilpaSD: of course it still fails as the code in versioned_notifications.py tries to import nova | |
| 12:26:16 | openstackgerrit | Merged openstack/nova stable/rocky: Remove unnecessary redirect https://review.openstack.org/607400 | |