| *** efried1 has joined #openstack-powervm | 02:26 | |
| *** efried has quit IRC | 02:28 | |
| *** efried1 is now known as efried | 02:28 | |
| *** openstackgerrit has quit IRC | 05:18 | |
| *** esberglu has joined #openstack-powervm | 13:25 | |
| *** antxon has joined #openstack-powervm | 15:08 | |
| antxon | hi all! | 15:09 |
|---|---|---|
| antxon | i am checking openstack&powerVM integration and have some questions | 15:09 |
| antxon | found this in openstack website: https://wiki.openstack.org/wiki/PowerVM#Communications_.26_Meetings | 15:10 |
| antxon | i would like to know the powervm support level in different openstack releases | 15:10 |
| efried | edmondsw: heads up ^ | 15:11 |
| antxon | is there anyone who could help me? :) | 15:11 |
| efried | antxon: Are you aware of the nova-powervm project? | 15:11 |
| antxon | hi efried, yes, found to many references, and read about it | 15:12 |
| efried | We have had pretty complete support for PowerVM via nova-powervm, which is an out-of-tree compute driver for nova. | 15:12 |
| edmondsw | hi antxon | 15:12 |
| edmondsw | glad to help... did you have any specific questions? | 15:12 |
| efried | So if you install nova-powervm on top of your nova deployment, you can get most of the VM operations you would expect (spawn/destroy, live migration, snapshot, etc.) | 15:12 |
| antxon | my question is related to the openstack supported versions for powervm | 15:13 |
| edmondsw | how far back are you looking to go? | 15:13 |
| antxon | my goal is integrating such environment with an in-house cloud broker, but we only support openstack kilo | 15:13 |
| edmondsw | let me get you the kilo docs... | 15:13 |
| antxon | we are updating our openstack support to pike | 15:13 |
| edmondsw | and the pike docs :) | 15:14 |
| antxon | but I haven't found any specific documentation about the powerVM driver requirements | 15:14 |
| edmondsw | http://nova-powervm.readthedocs.io/en/stable-pike/ | 15:14 |
| antxon | nice! is there anything similar for kilo? | 15:15 |
| edmondsw | kilo is EOL now, and we currently have an issue where the docs aren't building for EOL branches, so unfortunately I can't point you to the kilo docs at the moment | 15:15 |
| antxon | our stable branch is integrated with kilom which was deprecated long ago | 15:15 |
| edmondsw | If I can get that fixed I will ping you | 15:16 |
| edmondsw | you can see the source that is used to generate the docs on github if you want to look there | 15:16 |
| antxon | sure! let me know the repo | 15:16 |
| edmondsw | efried I thought we started in kilo, but I'm not seeing a kilo branch on github... did we start with liberty? | 15:17 |
| antxon | earliest reference on the web mentioned liberty | 15:18 |
| antxon | i checked the branches and tags in the powervm driver reports, but no explicit mention to kilo | 15:18 |
| edmondsw | yeah, that's what I'm seeing as well | 15:18 |
| edmondsw | you said you're moving to pike... is that going to happen soon? | 15:19 |
| antxon | although the timelines would match with kilo | 15:19 |
| antxon | in some weeks, we will move to pike, yes, although we haven't tested it too much | 15:19 |
| antxon | kilo integration as already been tested, and although updated, it would be enough for our tests if the powerVM driver works with it | 15:20 |
| edmondsw | kilo was a bit before my time... let me try to catch the guy who was running things then and get back to you | 15:20 |
| edmondsw | antxon are you already familiar with / using NovaLink? | 15:22 |
| antxon | I read about it, but haven't get enough time to go in deep | 15:23 |
| antxon | as far as i saw, is a middleware for PowerVM VIOS management | 15:23 |
| edmondsw | sort of... | 15:23 |
| antxon | i assume this is the interface used by the powerVM nova components | 15:24 |
| edmondsw | yes | 15:24 |
| edmondsw | In traditional PowerVM, the HMC is responsible for virtualization management (e.g. creating an LPAR) | 15:24 |
| efried | edmondsw: Looking at our oldest patches, they're in liberty, not kilo. | 15:24 |
| antxon | yep, i was familiar with powerVM HMC some years ago | 15:25 |
| edmondsw | with NovaLink, the HMC would still be useful for other things like energy management, firmware updates, call home, etc... but the NovaLink would take over virtualization management responsibilities | 15:25 |
| edmondsw | so if you want to create an LPAR, trigger an LPM, etc. you talk to NovaLink instead of HMC | 15:26 |
| edmondsw | like VIOS, NovaLink runs as a special virtual machine on the host | 15:26 |
| edmondsw | there are a bunch of advantages to this | 15:26 |
| antxon | efried: that was my suspicion looking at the repos, but not being familiar with openstack developmnet, i came here to ask | 15:26 |
| edmondsw | more scalability, RMC is secure, etc. | 15:27 |
| edmondsw | the PowerVM OpenStack drivers require NovaLink | 15:27 |
| edmondsw | NovaLink also gives some flexibility in regard to how you want to do your networking | 15:28 |
| edmondsw | you can use VIOS, or you can let the NovaLink partition handle the I/O for you by configuring Open vSwitch | 15:28 |
| edmondsw | if you use Open vSwitch (OVS) you can do fancy software-defined networking (SDN) things | 15:29 |
| edmondsw | but you lose I/O redundancy, so it's more like x86 in that way | 15:29 |
| edmondsw | if you want to stick with VIOS and use Shared Ethernet Adapters for networking, then in addition to nova-powervm you'll also need networking-powervm | 15:30 |
| edmondsw | http://networking-powervm.readthedocs.io/en/stable-pike/ | 15:30 |
| edmondsw | that's not needed if you want to use OVS | 15:30 |
| edmondsw | oh, networking-powervm also supports SR-IOV vNIC | 15:31 |
| edmondsw | there is one other OpenStack project where we add some PowerVM support... ceilometer-powervm | 15:31 |
| edmondsw | http://ceilometer-powervm.readthedocs.io/en/stable-pike/ | 15:31 |
| antxon | yep, the instrumentation component | 15:32 |
| edmondsw | yep, metrics | 15:32 |
| edmondsw | that's the 10,000 foot view | 15:32 |
| antxon | i got all the components from this page: https://wiki.openstack.org/wiki/PowerVM | 15:32 |
| edmondsw | replace "stable-pike" with "latest" for the latest docs, or "stable-queens", etc. for other releases. If it's an EOL release, it will be something like "liberty-eol" when we get those working | 15:33 |
| antxon | getting basic VM management from our broker through openstack is our goal | 15:33 |
| antxon | so, we need to deploy a powervm compatible version first | 15:33 |
| edmondsw | antxon OpenStack doesn't use the wiki much any more, so that's probably a little stale, but it'll give you some ideas | 15:33 |
| antxon | we deployed a functional kilo with devstack long ago, and can deploy a pike version easily with devstack | 15:34 |
| edmondsw | antxon are you building OpenStack yourself, or are you using a distro like RedHat OSP? | 15:34 |
| antxon | we built it with devstack in ubuntu some years ago | 15:34 |
| edmondsw | I hope you're not going to use devstack in production :) | 15:34 |
| antxon | and did the same for pike integration | 15:35 |
| antxon | no, it is only for integration purposes | 15:35 |
| edmondsw | devstack is great for testing, but I wouldn't use it beyond that | 15:35 |
| edmondsw | ok good | 15:35 |
| edmondsw | we've got some devstack scripts in github. They could use some work, but should give you an idea | 15:36 |
| antxon | if used for real, we would most likely go with OSP | 15:36 |
| edmondsw | https://github.com/openstack/nova-powervm/tree/stable/pike/devstack | 15:36 |
| antxon | yep, i saw the pike branch in the repo | 15:37 |
| antxon | so, i guess Kilo is out of the equation and I should go for Pike for sure | 15:38 |
| antxon | a final question | 15:38 |
| antxon | edmondsw: you mention the openstack wiki is not being used much any more | 15:39 |
| edmondsw | yep, most information is in https://docs.openstack.org/ or on readthedocs | 15:40 |
| antxon | is this only for the openstack-powervm integration only? | 15:40 |
| antxon | or is openstack using it as weel? | 15:40 |
| edmondsw | no, I meant for OpenStack in general | 15:40 |
| antxon | thanks for your answer and time, guys! | 15:41 |
| edmondsw | anytime | 15:41 |
| antxon | i am not familiar with openstack itself, and was kind of lost trying to answer these questions | 15:41 |
| edmondsw | antxon let us know how it goes and if you have any more questions | 15:41 |
| antxon | sure! | 15:41 |
| edmondsw | and we're an open community... once you get the hang of things, if you see anything you want to fix yourself, we always welcome contributions! | 15:42 |
| edmondsw | we can guide you a bit there | 15:42 |
| edmondsw | not saying you'll have to fix things yourself to get something fixed... but it's nice having the option :) | 15:43 |
| antxon | i will take that into account. But first I have to get that Pike environment functional and working before going further :) | 15:44 |
| edmondsw | absolutely | 15:45 |
| edmondsw | pike is going to be a better starting point than kilo anyway... newer, more function, not end-of-life, etc. | 15:50 |
| edmondsw | antxon mind if I ask who you're working for? | 15:50 |
| edmondsw | and if you have any intention of traveling to the OpenStack Summit or PTG, and want to get together there, let me know | 15:50 |
| edmondsw | I did confirm that Liberty was our first release... We started dev during kilo, but it wasn't ready to be used yet until liberty | 15:51 |
| antxon | yes, we are aware of the issues of going on with Kilo, hence the move to pike | 15:53 |
| antxon | i am working in devops team for Abiquo, edmondsw | 15:55 |
| antxon | the integration is a poc for using powervm through our product for one of our customers | 15:55 |
| antxon | we integrated with openstack around 2 years ago, with kilo | 15:56 |
| antxon | our customer want to test whether abiquo could use a powerVM backed openstack to deploy workloads there | 15:57 |
| edmondsw | cool | 15:57 |
| antxon | our engineering team integrated with neutron around the same time when they developed SDN capabilities inside the product | 15:59 |
| antxon | but, given the pace of development, the integration stalled at kilo | 15:59 |
| *** openstackgerrit has joined #openstack-powervm | 19:58 | |
| openstackgerrit | Merged openstack/ceilometer-powervm stable/rocky: Update .gitreview for stable/rocky https://review.openstack.org/590527 | 19:58 |
| *** efried has quit IRC | 19:58 | |
| openstackgerrit | Merged openstack/networking-powervm stable/rocky: Update .gitreview for stable/rocky https://review.openstack.org/590529 | 19:59 |
| openstackgerrit | Merged openstack/nova-powervm stable/rocky: Update .gitreview for stable/rocky https://review.openstack.org/590531 | 20:00 |
| openstackgerrit | Matthew Edmonds proposed openstack/nova-powervm stable/rocky: Use nova's stable/rocky branch https://review.openstack.org/591502 | 20:09 |
| openstackgerrit | Matthew Edmonds proposed openstack/networking-powervm stable/rocky: Use neutron's stable/rocky branch https://review.openstack.org/591503 | 20:11 |
| *** efried has joined #openstack-powervm | 20:13 | |
| openstackgerrit | Matthew Edmonds proposed openstack/networking-powervm stable/rocky: Use neutron's stable/rocky branch https://review.openstack.org/591503 | 20:14 |
| openstackgerrit | Matthew Edmonds proposed openstack/ceilometer-powervm stable/rocky: Use ceilometer's stable/rocky branch https://review.openstack.org/591505 | 20:14 |
| edmondsw | efried I think we should merge those (^) before enabling CI on stable/rocky | 20:52 |
| edmondsw | probably fast-approve if they look good to you | 20:52 |
| edmondsw | zuul passed | 20:52 |
| efried | edmondsw: done and done | 21:01 |
| edmondsw | ty sir | 21:01 |
| edmondsw | efried missed the nova-powervm one? | 21:01 |
| efried | link please | 21:01 |
| edmondsw | https://review.openstack.org/#/c/591502/ | 21:01 |
| efried | My puter crashed so I lost some history. | 21:01 |
| edmondsw | scuses... ;) | 21:02 |
| efried | I thought we got the nova-powervm one for free cause we're under governance. | 21:02 |
| efried | or something. | 21:02 |
| efried | oh, wait. I thought we got *all* of them for free because under governance. | 21:02 |
| edmondsw | we get .gitreview and upper-constraints changes for free | 21:02 |
| efried | and | 21:02 |
| edmondsw | we don't get these, since they're custom | 21:02 |
| efried | okay. | 21:02 |
| efried | done | 21:02 |
| edmondsw | I merged the .gitreview changes earlier this afternoon | 21:03 |
| edmondsw | the upper-constraints changes can't merge until openstack/requirements cuts a stable/rocky branch, which they still haven't done yet | 21:03 |
| edmondsw | they are always a bit behind | 21:03 |
| efried | right | 21:05 |
| efried | Are you trackyng the py3-first email thread? | 21:06 |
| efried | subject: [openstack-dev] [goal][python3] week 1 update: here we go! | 21:06 |
| openstackgerrit | Merged openstack/ceilometer-powervm stable/rocky: Use ceilometer's stable/rocky branch https://review.openstack.org/591505 | 21:11 |
| openstackgerrit | Merged openstack/networking-powervm stable/rocky: Use neutron's stable/rocky branch https://review.openstack.org/591503 | 21:12 |
| edmondsw | efried yep | 21:13 |
| efried | good; I imagine it could inform some of the work we're doing in that direction. | 21:14 |
| edmondsw | or trying to anyway | 21:14 |
| openstackgerrit | Merged openstack/nova-powervm stable/rocky: Use nova's stable/rocky branch https://review.openstack.org/591502 | 21:16 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!