Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2017-04-26
09:36:54 bauzas asettle: so, about documentation, I don't know what to say
09:36:59 johnthetubaguy asettle: the wider context, is we get everyone off ports as we get all the APIs onto apache, I think
09:37:00 bauzas asettle: because some use that port
09:37:05 bauzas asettle: some are not
09:37:14 sfinucan lyarwood: on it
09:37:15 johnthetubaguy bauzas: its tempting to say, find URL that your placement API is hosted on, and add it in here
09:37:34 bauzas johnthetubaguy: yup, it's definitely a config
09:37:43 asettle I think what we might have to do is write a very big IMPORTANT note that reminds people you can use that port, but do not use it if you intend to use Senlin. Whihc is really messy but I"m not seeing too many ways around it, to be honest. Using the placement is *not* working, we can't argue that right now.
09:37:47 asettle We need to have some working documentation.
09:37:52 lyarwood sfinucan: cheers
09:38:04 bauzas johnthetubaguy: but unfortunately, that depends on distros
09:38:41 bauzas asettle: deployers don't have choices, it's untrue to tell them that
09:38:44 johnthetubaguy bauzas: right, thats what I mean by find the URL
09:38:59 johnthetubaguy we can give its usually this or this, etc
09:39:07 bauzas asettle: it's rather, deployers need to know the related option depending on their distro
09:39:35 asettle Okay. So how do we communicate that in a short, concise, documented, step?
09:39:40 bauzas (at least until all distros move to a non-port URL)
09:40:00 bauzas asettle: the main question is, how deployers can discover that ?
09:40:15 bauzas I'd be tempted to say all distros use httpd
09:40:30 bauzas so we could say to deployers to look at the /etc/httpd/ path
09:41:03 bauzas either sites.de or sites-enabled depending on the OS
09:41:46 bauzas or grep something in /etc/{httpd|apache}
09:42:14 bauzas either way, the idea is to find the placement virtualhost configuration
09:42:23 bauzas *if they use httpd*
09:42:40 bauzas because if they use nginx+uswsgi, then it's totally different
09:43:54 johnthetubaguy so these docs are for specific packages right?
09:44:01 johnthetubaguy can't we just find out that answer
09:49:48 bauzas johnthetubaguy: the other problem is that it's unrelated to packages :p
09:50:07 johnthetubaguy bauzas: I thought the packages installed the apache conf?
09:50:32 bauzas johnthetubaguy: unfortunately no, because TripleO wipes that packaged conf and provides its own
09:50:46 openstackgerrit Balazs Gibizer proposed openstack/nova master: Add BDM to InstancePayload https://review.openstack.org/448779
09:50:47 openstackgerrit Balazs Gibizer proposed openstack/nova master: Add keypairs field to InstancePayload https://review.openstack.org/419730
09:50:53 johnthetubaguy it can be overriden, for sure, but I thought they general added one
09:51:02 johnthetubaguy if not, our guide should tell them how to set that up
09:51:14 johnthetubaguy so we just need the URL to match the guide, and its easier?
09:51:20 bauzas johnthetubaguy: in other words, openstack-nova in RDO uses port 8778 AFAIK but if you puppet-nova on top of it, it will use /placement
09:51:30 johnthetubaguy sure, thats fine
09:51:44 openstackgerrit Gábor Antal proposed openstack/nova master: Transform instance.soft_delete notifications https://review.openstack.org/460029
09:51:49 johnthetubaguy this is about using RDO packages manually, so seems like 8778 is the correct answer
09:52:06 johnthetubaguy now a warning say, there be dragons here if you change the package defaults is a good idea
09:52:24 bauzas johnthetubaguy: this is fine, you mean ? http://imgur.com/c4jt321 :D
09:52:57 johnthetubaguy so the guide is about using the packages manaully
09:53:06 johnthetubaguy if you don't do that, the guide will be very wrong in many ways
09:53:40 bauzas good point
09:53:50 bauzas I'm not that seasoned with docs
09:53:59 bauzas although I patched docs in 2013 :p
09:54:28 bauzas but IIRC, it was far less complicated, either you deployed with Ubuntu or Fedora
09:55:35 openstackgerrit John Garbutt proposed openstack/nova master: Add description to policies in floating_ip files https://review.openstack.org/459791
09:55:50 bauzas johnthetubaguy: asettle: so I guess if it's that simple, we should just have variable doc depending on which distro they use nope?
09:56:05 johnthetubaguy alex_xu: cool, glad we got that deprecation sorted, makes those docs much simpler ^
09:56:10 asettle bauzas: the variables are easy. We can manage that. We already do. So. Yep?
09:56:17 johnthetubaguy bauzas: thats what we do
09:56:41 bauzas asettle: could we then just try to have that reviewed by most of the distros ?
09:56:56 bauzas and having endpoints different between them ?
09:57:11 bauzas idk, just seems to me the easiest solution
09:58:14 openstackgerrit John Garbutt proposed openstack/nova master: Add description to policies in migrate_server.py https://review.openstack.org/459711
09:58:36 openstackgerrit John Garbutt proposed openstack/nova master: Add description to policies in migrate_server.py https://review.openstack.org/459711
10:04:02 cdent asettle, bauzas, johnthetubaguy did you resolve the above discussion satisfactorily? I tend to agree with johnthetubaguy: make the docs match the packages and leave it at that (for now)
10:04:16 asettle cdent: uh not quite. I think bauzas lost me with his last comments.
10:11:44 Dinesh_Bhor johnthetubaguy, sfinucan: Hi, if you get time then please take a look at it: https://review.openstack.org/#/c/457890/
10:12:00 openstackgerrit Zhenyu Zheng proposed openstack/nova master: Support tag instances when boot(2/4) https://review.openstack.org/459569
10:15:58 openstackgerrit Gábor Antal proposed openstack/nova master: Transform instance.soft_delete notifications https://review.openstack.org/460029
10:22:57 sfinucan Dinesh_Bhor: I'd seen that but I'm not 100% sure if we can do it. Comments now left saying as much
10:26:59 Dinesh_Bhor sfinucan: ok, will wait for others to take a look at it. thanks you so much
10:41:07 cdent johnthetubaguy: if you're willing and able this looks good to go: https://review.openstack.org/#/c/455710/
10:41:18 cdent or alex_xu
10:49:31 cdent thanks sdague, you're up early
10:53:20 sdague cdent: not that early :)
10:53:33 cdent anything before noon is early to me
10:53:51 sdague cdent: I just went through the devstack nova wsgi patch about what the transition plan needs to be
10:54:04 cdent it's a bit messy...
10:56:32 openstackgerrit Alex Szarka proposed openstack/nova master: Transform instance-exists notification https://review.openstack.org/403660
10:58:12 openstackgerrit Alex Szarka proposed openstack/nova master: Transform instance.exists notification https://review.openstack.org/403660
10:58:15 cdent i'll need to digest that sdague, I was thinking it might be possible to have grenade from-ocata to switch to uwsgi hosting the api, but I guess there's stuff that's relying on the URL for the API saying the same?
10:59:20 cdent another way to achieve the same thing would be to run uwsgi, but on a port (when in grenade)
10:59:26 cdent (as I've done for the metadata service)
11:00:11 sdague cdent: so in every transition we made here before we've left the configuration the same, we've not modeled a transition between 2 different service modes
11:00:56 sdague because I think that's really a post upgrade decision. Get onto the new code, then transition from one run mode to the other.
11:02:10 cdent yeah, I've never understood that because that means two events that are effectively upgrades. If I were deploying I'd change both at the same time (assuming some out of band testing beforehand)
11:07:19 sdague cdent: I wouldn't. I would validate the same configuration path worked as before before changing that out.
11:08:44 cdent different strokes. but that's fine. I'll have to stick a lot of stuff back into lib/nova, but that's also fine.
11:23:11 jaypipes *yawn*
11:23:13 jaypipes morning.
11:24:17 ralonsoh jaypipes: good morning. Flash question: https://review.openstack.org/#/c/451777/6/nova/objects/pci_device_pool.py
11:24:34 ralonsoh jaypipes: do we need to bump the version of an object if the parent is updated?
11:24:51 jaypipes ralonsoh: no
11:24:54 ralonsoh thanks
11:25:06 jaypipes ralonsoh: flash answer :)
11:25:08 ralonsoh that's all, enjoy your coffee
11:25:14 jaypipes hehe
11:41:43 jaypipes moshele: mornin. just approved the hw-tc-offload os-vif patch. excellent work on that.
11:42:23 moshele jaypipes: thanks :)
12:45:34 alex_xu nova api meeting is in 15 mins at #openstack-meeting-4
12:50:55 openstackgerrit sahid proposed openstack/nova master: numa: fix an uninitialized local variable https://review.openstack.org/458848
12:52:21 openstackgerrit Stephen Finucane proposed openstack/os-vif master: Require OVS 2.8 (presumed) and kernel 4.8 for offload https://review.openstack.org/460093
12:52:22 openstackgerrit Stephen Finucane proposed openstack/os-vif master: Standardize README https://review.openstack.org/460094
12:53:04 sfinucan jaypipes. moshele: noddy doc fixes ye should check out ^
12:53:14 sfinucan sean-k-mooney too ^
12:53:30 johnthetubaguy sfinucan: about your comments here, I am just quoting from the api-ref, which seemed the correct thing to do: https://review.openstack.org/#/c/459711/3
12:55:33 sfinucan johnthetubaguy: Yup, I get your reasoning. I'd rather have it "correct" in one place myself but I'm not too worried to hold it up on that

Earlier   Later