Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2018-12-03
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
12:27:30 openstackgerrit Jan Gutter proposed openstack/os-vif master: Extend port profiles with datapath offload type https://review.openstack.org/572081
12:30:38 ShilpaSD gibi: sorry, its still giving me Extension error:, i have updated my code for 'https://review.openstack.org/#/c/621558/1/doc/source/conf.py@19'
12:30:45 ShilpaSD from your patch
12:30:54 ShilpaSD rest already i ahve taken from Nova
12:31:46 gibi ShilpaSD: I get the following from my patch
12:31:47 gibi Could not import extension ext.versioned_notifications (exception: No module named 'nova')
12:31:47 gibi Extension error:
12:31:50 gibi ERROR: InvocationError for command '/home/ebalgib/upstream/git/masakari/.tox/docs/bin/python setup.py build_sphinx' (exited with code 1)
12:32:05 gibi ShilpaSD: and as I said this is expected as I just blindly copied versioned_notifications.py from nova
12:32:12 gibi and that python code imports nova
12:33:27 ShilpaSD ok, will check further, give me few time, will get back to you
12:33:49 gibi ShilpaSD: so the next step with that patch would be to adapt the code in versioned_notificaton.py to masakri
12:33:51 gibi ShilpaSD: sure
12:34:01 ShilpaSD gibi: sure
12:42:12 ShilpaSD gibi: thanks, after adding 'https://review.openstack.org/#/c/621558/1/doc/source/conf.py@19', its giving me proper stack trace, and now i am on the way to resolve errors listed
12:42:40 ShilpaSD earlier it gives, exception: cannot import name 'json_ref'
12:43:03 gibi ShilpaSD: cool
12:43:05 ShilpaSD after resolving its giving further error with detailed stack trace
12:43:17 gibi ShilpaSD: json_ref is also something that is inside nova
12:43:37 ShilpaSD gibi: yes, that i have got it
12:43:44 gibi OK
12:44:00 ShilpaSD now further issues with my code, will check and get back to you if any further hurdles
12:44:58 gibi ShilpaSD: sure, you can ping me any time (I'm working mostly in EU timezone)
12:45:28 ShilpaSD gibi: sure thnaks
13:11:34 sean-k-mooney sligtly off topic but does anyone know if any of the people from packet are on the nova irc?
14:01:34 stephenfin sean-k-mooney: packet?
14:02:18 sean-k-mooney stephenfin: https://www.packet.com/
14:02:41 stephenfin sean-k-mooney: You learn something new every day
14:05:33 sean-k-mooney i am planning on setting up a 2 node openstack over the christmas + nodepools/zuul but i was debating about using some burst capasity from them or another cloud provider also
14:06:03 sean-k-mooney i have the hardware locally to do ci but as you heard my rackmount server are not exactly quite
14:07:19 sean-k-mooney ahyway i might not but just wanted to ask them a few questions like can i set a montly limit on pricing that kind of thing
14:14:48 adrianc sean-k-mooney: Hi, regarding libvirt-neutron-sriov-livemigration, did you have a chance to look further at the code ? Also did you get a chance to work on the direct port support for POC ?
14:15:28 adrianc sean-k-mooney: i.e the detach/attach flow
14:18:46 sean-k-mooney adrianc: i hope to start working on the direct mode support this/ next week as my primary focus. i have been dealing with downstream bugs for the last week or more so other then deploying your code i have not made much progress
14:19:43 sean-k-mooney adrianc: i see you pushed a new version of the code yesterday
14:19:59 adrianc sean-k-mooney: ack, ill upload an updated PS today, dealing with some unit test issues
14:20:14 sean-k-mooney i should get a change to re review and redeploy with it tomorrow
14:20:33 adrianc sean-k-mooney: yes, addressing some of the issues that we talked abou, plus better clarifying the code
14:20:58 sean-k-mooney i will be respinnign the spec today/tommorow too by the way

Earlier   Later