Tuesday, 2019-02-19

*** aedc has quit IRC00:00
*** DanyC_ has quit IRC00:07
*** markvoelker has joined #openstack-ansible00:09
*** markvoelker has quit IRC00:14
*** sdake has joined #openstack-ansible00:26
*** chandankumar has quit IRC00:28
*** chandankumar has joined #openstack-ansible00:29
*** cmart has quit IRC00:31
*** vnogin has joined #openstack-ansible00:34
cloudnullcmart still around? -- I've not given OSA a go in such an environment. the largest I ever managed in a single region was: ~500 compute nodes, ~200 storage nodes, ~5 infra hosts, 3 L3 network nodes.00:37
cloudnullthe ops side of things was not really tough, but it did take a while to roll out updates.00:37
cloudnullthat was in the mitaka timeframe , so I suspect that same deployment would be a lot simpler to manage today than it was then00:38
*** vnogin has quit IRC00:39
cloudnullwe had to create a lot of monitoring and metric collection on services, we cared less about specific host downs and really drove toward scheduler available. so a lot of monitoring was focused on resource available and capacity planning00:39
jamesdentongood times had by all00:40
cloudnullindeed!00:40
cloudnullhost down was all about: quick fix if possible (reboot), evacuate (if possible), say sorry (if not), call hot hands to replace gear.00:41
cloudnullbut it wasn't a death march and wasn't something that required a lot of heads.00:41
cloudnulljamesdenton knows what I'm talking about :)00:41
jamesdenton:D00:41
cloudnull10/8 for life!00:41
jamesdentoni miss having those machines00:42
cloudnullme too.00:42
cloudnullhows it jamesdenton?00:43
jamesdentonit's goin. trying to get thru the nighttime routine and maybe sit down with some scotch and poke at an AIO00:44
jamesdentonbrb00:47
cloudnullooh, scotch and cloud. some great times to be had by all00:54
cloudnullbgmccollum did you make it go ?00:54
*** tosky has quit IRC00:57
*** sdake has quit IRC00:58
*** markvoelker has joined #openstack-ansible01:10
*** sdake has joined #openstack-ansible01:14
*** sdake has quit IRC01:16
*** sdake has joined #openstack-ansible01:21
*** sdake has quit IRC01:42
*** sdake has joined #openstack-ansible01:43
*** markvoelker has quit IRC01:44
*** sdake has quit IRC01:54
*** sdake has joined #openstack-ansible02:00
*** sdake has quit IRC02:22
openstackgerritAndriy Shevchenko proposed openstack/openstack-ansible-galera_server master: fix tox python3 overrides  https://review.openstack.org/61549002:31
*** markvoelker has joined #openstack-ansible02:41
*** hwoarang has quit IRC02:59
*** hwoarang has joined #openstack-ansible03:02
*** markvoelker has quit IRC03:13
openstackgerritKevin Carter (cloudnull) proposed openstack/openstack-ansible-ops master: Update grafana, use vendored role, and add es lb  https://review.openstack.org/63767203:20
*** mgariepy has quit IRC03:33
chandankumarcloudnull: Hello03:33
cloudnullo/03:33
chandankumarcloudnull: I have successfully deployed openstack-ansible aio_metal_heat scenario03:34
cloudnullsweet!03:35
chandankumarusing gate-check-commit.sh script03:35
chandankumarfrom source03:35
cloudnullnice!03:35
chandankumarcloudnull: now the problem is there I am currently ssh into the box it is dumping here [root@aio1 ~]03:36
chandankumarcloudnull: there is no lxc related commands there03:36
chandankumarcloudnull: or I missing something?03:36
chandankumarthere only openstack-ansible and tempest workspace exists03:36
chandankumarand openrc file03:36
cloudnullaio_metal_heat would deploy everything on the single host without using any containers03:37
cloudnullso all of the services should be deployed and running on that one AIO03:37
chandankumarcloudnull: so there is no lxc containers03:37
cloudnullif you check `ps auxf` or systemd-cgls you'll see all of the cgroups and processes but no containers.03:37
cloudnullchandankumar yes. there are no containers when using that scenario03:38
chandankumarcloudnull: awesome03:38
chandankumarcloudnull: now I can see the venv and other stuff03:38
cloudnullyes. a03:38
chandankumarcloudnull: why the version tempest-18.0.0.0rc2.dev370 ends with 18.0.0?03:38
cloudnullall of the venvs will be in the /openstack directory03:38
cloudnullthe venv or the version of the service in the venv directory03:39
cloudnullI would suspect "18.0.0.0rc2.dev370" is the version of tempest deployed03:40
chandankumarcloudnull: venv-<version>03:40
chandankumarcloudnull: tempest 19.0.0 is installed there on sourceing the venv03:40
cloudnullso that's the venv version ?03:41
chandankumarcloudnull: http://paste.openstack.org/show/745300/03:41
cloudnullsomething like /openstack/venvs/tempest-18.0.0.0rc2.dev37003:41
chandankumar(tempest-18.0.0.0rc2.dev370) [root@aio1 venvs]# virtualenv --version03:41
chandankumar15.1.003:41
cloudnull(tempest-18.0.0.0rc2.dev370)  is the activated venv03:42
cloudnullwhich in that case would be the OSA version03:42
chandankumarcloudnull: other venv http://paste.openstack.org/show/745301/03:42
chandankumarcloudnull: ok, got it03:42
cloudnullyou can see that in the /etc/openstack-release file03:42
cloudnullwe mark all of the venvs we deploy with the the OSA code version03:43
cloudnullwhich makes it easier to roll back if needed03:43
chandankumarcloudnull: DISTRIB_RELEASE="18.0.0.0rc2.dev370"03:43
cloudnull++03:43
chandankumarcool, thanks, Now I can debug heat stuff now :-)03:43
cloudnullsweet!03:43
cloudnullyou should also be able to redeploy from new sources as needed.03:45
*** shyamb has joined #openstack-ansible03:45
*** dave-mccowan has joined #openstack-ansible03:45
cloudnulla friend of mine, Miguel did a talk about this a while back https://developer.rackspace.com/blog/life-without-devstack-openstack-development-with-osa/03:46
cloudnullhttp://confreaks.tv/videos/openstacksummittokyo2015-life-without-devstack-upstream-development-with-osad03:46
cloudnullwhich was cool!03:46
chandankumarcloudnull: will check that thanks :-)03:51
*** udesale has joined #openstack-ansible03:54
*** mgariepy has joined #openstack-ansible04:06
*** shyamb has quit IRC04:06
*** markvoelker has joined #openstack-ansible04:10
*** vnogin has joined #openstack-ansible04:10
*** hamzy has quit IRC04:13
*** vnogin has quit IRC04:15
*** jamesdenton has quit IRC04:16
*** jamesdenton has joined #openstack-ansible04:16
*** chandankumar is now known as chkumar|ruck04:32
*** markvoelker has quit IRC04:44
openstackgerritChandan Kumar proposed openstack/openstack-ansible-os_tempest master: Added dependency of os_tempest role  https://review.openstack.org/63272604:46
*** irclogbot_0 has quit IRC04:55
*** medberry has quit IRC05:07
*** shyamb has joined #openstack-ansible05:08
*** dave-mccowan has quit IRC05:13
*** mgariepy has quit IRC05:29
*** mgariepy has joined #openstack-ansible05:30
*** udesale has quit IRC05:33
*** markvoelker has joined #openstack-ansible05:41
*** udesale has joined #openstack-ansible05:43
*** shyamb has quit IRC06:03
*** shyamb has joined #openstack-ansible06:09
*** markvoelker has quit IRC06:14
*** shyamb has quit IRC06:37
*** shyamb has joined #openstack-ansible06:39
openstackgerritChandan Kumar proposed openstack/openstack-ansible-os_tempest master: Added tempest.conf for heat_plugin  https://review.openstack.org/63202106:47
openstackgerritChandan Kumar proposed openstack/openstack-ansible-os_tempest master: Added tempest.conf for heat_plugin  https://review.openstack.org/63202106:50
openstackgerritChandan Kumar proposed openstack/openstack-ansible-os_tempest master: Use the correct heat tests  https://review.openstack.org/63069506:50
openstackgerritChandan Kumar proposed openstack/openstack-ansible-os_heat master: [DNM] heat tempest tests finding  https://review.openstack.org/63069406:50
*** bgmccollum has quit IRC06:53
*** rgogunskiy has joined #openstack-ansible06:56
*** DanyC has joined #openstack-ansible06:58
*** miloa has joined #openstack-ansible07:02
*** kopecmartin|off is now known as kopecmartin07:02
*** markvoelker has joined #openstack-ansible07:11
*** bgmccollum has joined #openstack-ansible07:14
*** DanyC has quit IRC07:28
*** shyamb has quit IRC07:33
*** markvoelker has quit IRC07:43
*** shyamb has joined #openstack-ansible07:45
*** udesale has quit IRC07:58
*** shyam89 has joined #openstack-ansible08:01
*** udesale has joined #openstack-ansible08:03
openstackgerritChandan Kumar proposed openstack/openstack-ansible-os_tempest master: Added tempest.conf for heat_plugin  https://review.openstack.org/63202108:03
openstackgerritChandan Kumar proposed openstack/openstack-ansible-os_tempest master: Use the correct heat tests  https://review.openstack.org/63069508:04
*** shyamb has quit IRC08:05
*** udesale has quit IRC08:07
*** udesale has joined #openstack-ansible08:08
*** pcaruana has joined #openstack-ansible08:11
*** shardy has joined #openstack-ansible08:15
*** shardy has quit IRC08:15
*** shyam89 has quit IRC08:16
*** dswebb has joined #openstack-ansible08:22
fnpanicmorning08:24
*** sdake has joined #openstack-ansible08:28
*** goldenfri has quit IRC08:31
*** shardy has joined #openstack-ansible08:31
*** shyamb has joined #openstack-ansible08:31
*** evrardjp_ is now known as evrardjp08:31
*** sdake has quit IRC08:37
*** electrofelix has joined #openstack-ansible08:38
*** markvoelker has joined #openstack-ansible08:40
*** tosky has joined #openstack-ansible08:42
*** goldenfri has joined #openstack-ansible08:44
*** sdake has joined #openstack-ansible08:45
*** hamzaachi has joined #openstack-ansible08:49
*** aedc has joined #openstack-ansible08:51
*** shyamb has quit IRC08:51
*** shyamb has joined #openstack-ansible08:52
*** DanyC has joined #openstack-ansible08:57
*** priteau has joined #openstack-ansible08:59
*** DanyC has quit IRC09:08
*** DanyC has joined #openstack-ansible09:09
CeeMacmorning09:14
*** markvoelker has quit IRC09:14
*** ostackz has quit IRC09:16
*** shyamb has quit IRC09:18
*** shyamb has joined #openstack-ansible09:19
*** sdake has quit IRC09:25
openstackgerritChandan Kumar proposed openstack/openstack-ansible-os_tempest master: Revert "Only init a workspace if doesn't exists"  https://review.openstack.org/63780109:27
*** sdake has joined #openstack-ansible09:28
dswebbcan anyone tell me what exactly needs to be set to deploy a cinder-volume container with osa?  this is a snippet of the config I thought would do it, but all I have is a cinder-api container that only runns the scheduler / api.  https://pastebin.com/4CGUrzhn09:45
*** sdake has quit IRC09:49
*** shyamb has quit IRC09:55
*** shyamb has joined #openstack-ansible09:56
*** markvoelker has joined #openstack-ansible10:11
*** DanyC has quit IRC10:18
*** DanyC has joined #openstack-ansible10:19
odyssey4medswebb cinder-volume goes on to a host by default, not into a container10:32
odyssey4medswebb this is a sample config: https://github.com/openstack/openstack-ansible/blob/master/etc/openstack_deploy/conf.d/cinder.yml.aio#L29-L4410:32
odyssey4methat will do cinder-volume with a lvm back-end10:33
dswebbonto one of the controller nodes by default?10:36
*** cshen has joined #openstack-ansible10:36
odyssey4meguilhermesp I expect you're going to want to port https://review.openstack.org/637275 back to the appropriate stable branches?10:38
dswebbI've just ended up with an install with no cinder-volume running at all, so trying to backtrack and figure out where it went wrong10:39
*** priteau has quit IRC10:41
odyssey4medswebb sorry - lost connection there, did you see any of my replies?10:42
dswebbI did, the sample config10:42
chkumar|ruckodyssey4me: hey10:43
chkumar|ruckodyssey4me: in morning, I finally have the osa installed system10:43
chkumar|ruckodyssey4me: using gate commit check script10:43
chkumar|ruckodyssey4me: heat tempest conf tests getting generated10:43
*** markvoelker has quit IRC10:43
chkumar|ruckodyssey4me: and the other issue guilhermesp was telling10:44
odyssey4mechkumar|ruck great!10:44
CeeMacjrosser, you around?10:44
openstackgerritChandan Kumar proposed openstack/openstack-ansible-os_tempest master: Revert "Only init a workspace if doesn't exists"  https://review.openstack.org/63780110:45
odyssey4medswebb ok, I now see your response in http://eavesdrop.openstack.org/irclogs/%23openstack-ansible/%23openstack-ansible.2019-02-19.log.html - you need to choose where your volume service will run... if you're using ceph, then a controller will do. if you're using an LVM back-end, then you may wish to choose a dedicated box.10:51
odyssey4meIt'll depend how much volume for cinder-backup you'll expect, because it can be heavy, depending on the back-end. In most cases, just using a controller is fine.10:52
*** shyamb has quit IRC10:56
*** shyamb has joined #openstack-ansible11:01
jrosserCeeMac: hello! i'm around11:02
CeeMachi!11:03
CeeMacdid a bit more digging through the logs on the hosts that are having network issues and it always seems to be around the lxc_hosts role with the apt install11:03
CeeMacsystemd upgrade is restarting the networking11:04
CeeMacdigging in more closely to the underlay, I don't think the Cisco blade switches I'm using implement lacp correctly / at all in the chassis11:04
CeeMacwhich explains why I lose network connectivity when the active port is restarted11:04
CeeMacmy controller host randomly lost networking at 6am today too11:05
CeeMacnot sure how this wasn't an issue when I first deployed OSA, but its not loving it now11:06
CeeMacso I'm probably going to have to revisit my network setup :(11:07
CeeMacmight still look at networkd as an alternative to netplan (if I feel brave later)11:07
CeeMacjrosser ^ sorry should have tagged you at the start of that :)11:09
*** udesale has quit IRC11:10
*** jawad_axd has joined #openstack-ansible11:28
*** cshen has quit IRC11:36
jrosserCeeMac: i needed extra config on my cisco switches for lacp, but that really very much depends on how the servers/switches are wired11:38
guilhermespmornings11:38
guilhermespah yeah odyssey4me will do that, thanks11:38
CeeMacjrosser, I have the bonds set to active/backup, so I didn't think lacp would be necessary11:39
CeeMacunless there is something blocking GARP somewhere11:39
guilhermespchkumar|ruck: nice too! Let me know if you need the hold I have for the upgrade jobs too, that could be helpful for debugging11:39
openstackgerritGuilherme  Steinmuller Pimentel proposed openstack/openstack-ansible-galera_server stable/rocky: Iterate over list of values of PPC packages dict  https://review.openstack.org/63782511:39
jrosserCeeMac: ah ok i had trouble with active/active, but have fixed that now11:40
*** markvoelker has joined #openstack-ansible11:40
CeeMaci'm also a little perturbed by the issues with native vlan tag, through to vlan interface11:40
openstackgerritGuilherme  Steinmuller Pimentel proposed openstack/openstack-ansible-galera_server stable/queens: Iterate over list of values of PPC packages dict  https://review.openstack.org/63782611:41
CeeMacdoesn't seem to like having a port on the native vlan where the vlan is also trunked on the same interface11:42
CeeMacreally need to rethink my networking layout for the environment11:42
jrosseri'm not sure that is possible11:42
CeeMacit worked on the 'base' ubuntu install11:42
jamesdentonAre you doing VLAN pruning? Where the vlan is allowed on the interface but set as native?11:43
CeeMacfell over when i created tagged interfaces on the bond11:43
CeeMacyes11:43
CeeMacas its passed through for the container too11:43
jamesdentonAs long as you don't tag that vlan, you should be OK.11:43
CeeMacoh, hey jamesdenton :)11:44
jamesdentonSo a neutron 'flat' network would be appropriate. good morning11:44
*** ansmith has joined #openstack-ansible11:44
CeeMacyeah, I'm thinking I'll be better off using a seperate OOB management vlan as the native for SSH access to the host, then keeping the br-mgmt vlan as tagged end to end11:44
jrosser^ good move11:44
jamesdentonthat's what we do11:45
CeeMacjamesdenton, any thoughts on active/backup bond to independant switches having issues when the active interface goes down?11:45
CeeMacor is bond across independant switches effectively not supported/possible?11:46
CeeMacI do it this way for ESXi, so figured normal linux bond would work too (massive assumption maybe)11:46
jamesdentonactive/passive to multiple switches should be OK. We have done that numerous times.11:47
CeeMacsorry, a bit off-topic for OSA11:47
jamesdentonwhen the active interface goes down... I've seen that behavior vary based on which side is acting up11:48
CeeMaci can't help but think this is related somehow to the issue i was seeing in VMware with virtual switches11:48
CeeMacits like GARP isn't working, so when the active interface goes down and the ARP timeout expires, the MAC disapears11:48
CeeMacthe GARP from the passive interface isn't being registered11:49
*** jawad_axd has quit IRC11:50
CeeMacexcept for 6am today which I haven't worked out yet, its always been associate with systemd update while doing minor upgrade11:50
*** jorti has quit IRC11:50
CeeMacsetup-hosts and setup-infrastructure both seem to reference lxc-hosts which upgrades systemd11:50
CeeMacactive interface goes down, bond goes down. comes back up on the host, but not on the network11:51
*** shyamb has quit IRC11:51
CeeMacI then have to physically shut/no shut both switch ports and networking comes back on the host11:51
*** shyamb has joined #openstack-ansible11:51
jrosserCeeMac: out of interest how have you configured your host networking? networkd?11:51
CeeMacjrosser, netplan11:52
jrosserhmmmm11:52
CeeMacrenderer: networkd11:52
jamesdentonbrb in 2011:52
CeeMack11:52
CeeMaci thought I was OK with netplan, but it still feels a little flaky for want of a better term11:53
CeeMacreally can't decide between going pure networkd or switching back to ifupdown11:53
CeeMaci feel ifupdown would be more stable, but networkd more futureproof?11:53
jrosserwell. i don't know, everyone has their own opinion on that11:54
CeeMacyeah11:55
*** jorti has joined #openstack-ansible11:55
CeeMacthat was a throw-away comment really :)11:55
jrossermy 2p is that i've learned the very hard way that anything that restarts the networking regardless of ifupdown/systemd unleashes a lot of brokenness11:55
*** jawad_axd has joined #openstack-ansible11:55
CeeMacoh11:55
chkumar|ruckodyssey4me: cloudnull any idea how to fix it http://logs.openstack.org/26/632726/12/check/tripleo-ci-centos-7-standalone-os-tempest/d22a454/job-output.txt.gz#_2019-02-19_09_46_00_505465 ?11:55
jrosserso anything you can do to ensure that never happens unless you really really want it to is a good thing11:55
CeeMacthat sounds ominous11:55
chkumar|ruckor do I need to change the path11:55
CeeMaci'm not a big fan of a lot of brokenness in general11:56
jrosserCeeMac: as an example, i have ansible playbooks that set up the host networking, and they are designed as one-shot, so only apply changes on a fresh box11:57
CeeMacjrosser, i still need to build out my build process, hand building right now11:57
jrosseryou have to explicily pass "-e yes_really_restart_networking=true" sort of variable to the ansible-playbook run to make it ever do it again11:57
CeeMacthat sounds emininently sensible11:58
CeeMacare you using a pxe server plugin with ansible to manage the inventory/ o/s build prior to running your config playbooks?11:59
CeeMacor are you netboot/preseeding?11:59
jrosserpretty much, pxe server built with ansible11:59
jrosserusing the ansible inventory to write out the tftp/dhcp config files and the preseeds per host12:00
CeeMacthat sounds fun/complicated, I'll get around to taking a look at that sort of thing eventually12:00
*** cshen has joined #openstack-ansible12:01
*** jawad_axd has quit IRC12:03
CeeMacneed to work on network stability first though12:06
*** ansmith has quit IRC12:08
jrosserguilhermesp: i am very close to getting magnum working, but not there yet - have you looked at magnum at all?12:11
*** prometheanfire has quit IRC12:12
CeeMachmmm12:12
CeeMaccould actually be an issue on the juniper swithches12:12
*** prometheanfire has joined #openstack-ansible12:14
*** markvoelker has quit IRC12:14
jamesdentonCeeMac what did you find on the juniper side?12:19
CeeMacat least for the SVI, update on garp is disabled by default12:20
CeeMacwhich would affect the gateway12:20
CeeMacnot sure that would affect the other hosts on the same vlan though12:20
CeeMacwill try set gratuitous-arp-reply and test later this afternoon12:21
CeeMacif i get time12:22
jamesdentonyeah, you may need to have an eye on the host and switches simultaneously, and put on your troubleshooting cap and go to town12:24
CeeMacyeah12:24
CeeMacmight leave that for later in the week, got other tasks to do like build out the RC environment to actually have multiple nodes under the HA roles12:25
CeeMacso at least I can move things around during upgrades which would part way mitigate the problem12:25
*** mkuf_ has joined #openstack-ansible12:29
*** mkuf has quit IRC12:32
guilhermespjrosser: for the moment I have a functional magnum cluster with rocky in one of our customers12:48
guilhermespI think using 18.1.1. Are you facing any others issues?12:48
jrosserguilhermesp: sort of basic question, is that with fedora atomic or coreos?12:49
jrosserthis in particular seems to need an update https://github.com/openstack/openstack-ansible-os_magnum/blob/master/defaults/main.yml#L14612:50
jrosseras it points you to fedora 25 which seems to not go so well12:50
*** udesale has joined #openstack-ansible12:55
guilhermespi've always using fedora-atomic. We need to use the version that matches the openstack release. I think we are using fedora-atomic-28, not sure. I can check it out12:56
*** shyamb has quit IRC12:57
guilhermespand yes, I agree with an update of this link you sent as we have particular versions of fedora-atomic for each version12:57
jrosserit says 27 here https://docs.openstack.org/magnum/rocky/install/launch-instance.html#upload-the-images-required-for-your-clusters-to-the-image-service12:57
kaiokmomagnum should use fedora atomic 27 since rocky, IIRC12:57
guilhermespyes, both of you are right jrosser and kaiokmo https://docs.openstack.org/magnum/rocky/user/#kubernetes-on-fedora-atomic12:58
jrosserok so my specific issue is that on the master node i can't find where this is laid down https://github.com/openstack/magnum/blob/stable/rocky/magnum/drivers/k8s_fedora_ironic_v1/templates/kubemaster.yaml#L42412:58
jrosserso it never completes (this is a different issue to internal/external endpoints)12:59
jrosserthe magnum code looks like it should be creating a systemd service on the master node which signals completion12:59
*** mkuf has joined #openstack-ansible13:00
jrosseroh sorry, thats the wrong link, thats ironic13:01
*** mkuf_ has quit IRC13:04
guilhermespthat's odd for me... the only issue I had with magnum after fixing the heat bugs was specific network issues from the company side13:04
jrosserso actually thats the thing, i really understand how the overall completion of the deployment is signalled in the fedora-atomic case13:04
jrosser*dont13:04
*** vnogin has joined #openstack-ansible13:11
*** markvoelker has joined #openstack-ansible13:11
openstackgerritLuis Filipe Domingues proposed openstack/openstack-ansible master: Fix keepalive pingable_check_script  https://review.openstack.org/63783913:15
*** phasespace has joined #openstack-ansible13:20
dswebbodyssey4me cheers for the help, finally managed to get osa to deploy the volumes containers.  worth mentioning that the mnaio ceph install doesn't work out of the box.13:21
dswebbunless I happened to miss a flag I should have set, which is totally possible13:21
odyssey4medswebb it'd be useful if you could register a bug with what didn't work, and the config you needed to add to make it work.13:23
*** sdake has joined #openstack-ansible13:23
dswebbwill do13:23
odyssey4meOr even better, if you're able to push up a review to fix it. :)13:24
*** vnogin has quit IRC13:24
dswebbI might try at the weekend, need to hand this env over to my devs for the week13:24
*** ArchiFleKs has quit IRC13:31
chkumar|ruckjrosser: odyssey4me one query, when we create public and private network do we need to use the same network_type while creating or different one?13:31
chkumar|ruckat one place it is flat for public network and vxlan for private network13:32
*** gokhani has joined #openstack-ansible13:32
chkumar|ruckhttps://github.com/openstack/openstack-ansible-os_tempest/blob/master/defaults/main.yml#L147 and https://github.com/openstack/openstack-ansible-os_tempest/blob/master/defaults/main.yml#L13513:32
odyssey4mechkumar|ruck that would depend on what you want, or have setup on the host as I understand it - whatever you set there needs to work with the host networking environment - jrosser knows that stuff better, and jamesdenton would also be of help13:33
*** med_ has joined #openstack-ansible13:34
chkumar|ruckodyssey4me: it is related to creating networks for os_tempest13:34
jamesdentonI'm not sure the private network is really tested. But the public network is likely flat so you can ssh via floating up13:36
jamesdenton*ip13:36
jrosseri guess the private network is implictly tested otherwise you'd not be able to ssh to the vm13:36
jamesdentontouche13:36
chkumar|ruckodyssey4me: jamesdenton jrosser https://review.openstack.org/#/c/637838/ on tripleo side we are using vlan at each place so asked13:38
chkumar|ruck*using flat at both place13:38
jamesdentonYou'd need two interfaces13:41
*** markvoelker has quit IRC13:43
*** ansmith has joined #openstack-ansible13:44
*** hamzy has joined #openstack-ansible13:44
*** chkumar|ruck is now known as chandankumar13:45
*** ArchiFleKs has joined #openstack-ansible13:48
*** dave-mccowan has joined #openstack-ansible13:49
*** sdake has quit IRC14:05
jamesdentonchandankumar Are you trying to solve for issues with multi-node testing? Curious why the change from vxlan to flat14:09
*** sdake has joined #openstack-ansible14:13
*** masterpe has joined #openstack-ansible14:13
kaiokmojrosser: I think maybe https://github.com/openstack/magnum/blob/stable/rocky/magnum/drivers/common/templates/kubernetes/fragments/wc-notify-master.sh#L14-L22 is what you are looking for14:14
*** sdake has quit IRC14:19
*** phasespace has quit IRC14:31
*** sdake has joined #openstack-ansible14:37
*** markvoelker has joined #openstack-ansible14:41
*** sdake has quit IRC14:53
*** udesale has quit IRC14:53
chandankumarjamesdenton: there we are doing single node testing14:58
chandankumarjamesdenton: here is the ara logs http://logs.openstack.org/60/634060/12/check/tripleo-ci-centos-7-standalone-os-tempest/2981018/logs/ara_oooq/result/11f3eab6-8fdf-4cda-afb6-8de4ff78bafd/14:59
*** sdake has joined #openstack-ansible15:00
cloudnullmornings all15:01
cloudnullanyone want to give https://review.openstack.org/#/c/588959/ a shove15:01
*** vnogin has joined #openstack-ansible15:02
jamesdentonchandankumar Unless I'm wrong, in os_tempest, the 'flat' label maps to eth12, and you'd only get one flat network out of that. You'd have to build a separate mapping (flat2:eth13) and then have to specify the label on each network (public and private).15:04
chandankumarjamesdenton: not sure 2019-02-19 08:13:14.027 ERROR /var/log/extra/errors.txt: ERROR /var/log/containers/neutron/server.log: 30 ERROR ovsdbapp.event [-] Unexpected exception in notify_loop: KeyError: 'neutron:ovn-metadata-sb-cfg'15:04
jamesdentonas for that error, do you happen to have access to the configuration of ml2_conf.ini from that build?15:04
chandankumar2019-02-19 08:13:14.027 ERROR /var/log/extra/errors.txt: ERROR /var/log/containers/neutron/server.log: 30 ERROR ovsdbapp.event Traceback (most recent call last):15:04
chandankumar2019-02-19 08:13:14.027 ERROR /var/log/extra/errors.txt: ERROR /var/log/containers/neutron/server.log: 30 ERROR ovsdbapp.event   File "/usr/lib/python2.7/site-packages/ovsdbapp/event.py", line 137, in notify_loop15:04
chandankumar2019-02-19 08:13:14.027 ERROR /var/log/extra/errors.txt: ERROR /var/log/containers/neutron/server.log: 30 ERROR ovsdbapp.event     match.run(event, row, updates)15:04
chandankumar2019-02-19 08:13:14.027 ERROR /var/log/extra/errors.txt: ERROR /var/log/containers/neutron/server.log: 30 ERROR ovsdbapp.event   File "/usr/lib/python2.7/site-packages/networking_ovn/ovsdb/ovsdb_monitor.py", line 98, in run15:04
chandankumar2019-02-19 08:13:14.027 ERROR /var/log/extra/errors.txt: ERROR /var/log/containers/neutron/server.log: 30 ERROR ovsdbapp.event     self._metadata_nb_cfg(row))15:04
chandankumar2019-02-19 08:13:14.027 ERROR /var/log/extra/errors.txt: ERROR /var/log/containers/neutron/server.log: 30 ERROR ovsdbapp.event   File "/usr/lib/python2.7/site-packages/networking_ovn/ovsdb/ovsdb_monitor.py", line 86, in _metadata_nb_cfg15:04
chandankumar2019-02-19 08:13:14.027 ERROR /var/log/extra/errors.txt: ERROR /var/log/containers/neutron/server.log: 30 ERROR ovsdbapp.event     return int(row.external_ids[ovn_const.OVN_AGENT_METADATA_SB_CFG_KEY])15:04
jamesdentonwhich plugin are you testing?15:04
chandankumar2019-02-19 08:13:14.027 ERROR /var/log/extra/errors.txt: ERROR /var/log/containers/neutron/server.log: 30 ERROR ovsdbapp.event KeyError: 'neutron:ovn-metadata-sb-cfg'15:04
chandankumarsorry15:04
chandankumarjamesdenton: http://logs.openstack.org/60/634060/12/check/tripleo-ci-centos-7-standalone-os-tempest/2981018/logs/undercloud/var/log/extra/errors.txt.gz#_2019-02-19_08_13_14_02715:04
chandankumarjamesdenton: this might be the issue15:04
jamesdentonIf you're testing OVN, then vxlan definitely isn't supported. It would need to be GENEVE15:04
chandankumarjamesdenton: they have recently migrating to ovn15:05
*** vnogin has quit IRC15:06
jamesdentonin that case, consider setting tempest_private_net_provider_type to geneve and see how that goes15:06
*** shananigans has joined #openstack-ansible15:10
chandankumarjamesdenton: thanks, updated that15:12
*** markvoelker has quit IRC15:14
openstackgerritMerged openstack/openstack-ansible-ops master: Update grafana, use vendored role, and add es lb  https://review.openstack.org/63767215:22
openstackgerritChandan Kumar proposed openstack/openstack-ansible-os_tempest master: Set tempest_private_net_provider_type to geneve as default  https://review.openstack.org/63787515:22
chandankumarjamesdenton: as per dalverz, we can set geneve as a default in os_tempest15:23
jamesdentonAre you using a forked branch?15:24
chandankumarjamesdenton: nope15:24
jamesdentonthe default today is vxlan: https://github.com/openstack/openstack-ansible-os_tempest/blob/master/defaults/main.yml#L135. So I'm guessing you just mean override that on your side?15:25
chandankumarjamesdenton: http://codesearch.openstack.org/?q=tempest_private_net_provider_type&i=nope&files=.yml&repos=15:26
jamesdentonyes15:27
chandankumarin OSA and os_tempest is vxlan by defalt15:27
jamesdentonyes15:28
chandankumarjamesdenton: let me comment on review itself on tripleo side15:28
jamesdentonyou mentioned changing the default to geneve, which would break the OSA gate today15:28
*** lucasagomes has joined #openstack-ansible15:28
jamesdentonthus the suggestion to override15:28
*** sdake has quit IRC15:28
chandankumarlucasagomes: Hello15:29
chandankumarlucasagomes: on osa side http://codesearch.openstack.org/?q=tempest_private_net_provider_type&i=nope&files=.yml&repos= vxlan is default, so changing in os_tempest will break it15:30
chandankumarjamesdenton: https://review.openstack.org/#/c/637838/215:30
lucasagomeschandankumar, hi there, lemme take a look15:31
lucasagomeschandankumar, ok, hmm I have to check how we can proceed then because vxlan is not a valid net type in OVN15:33
*** sdake has joined #openstack-ansible15:35
*** sreejithp has joined #openstack-ansible15:37
*** vnogin has joined #openstack-ansible15:37
openstackgerritJonathan Rosser proposed openstack/openstack-ansible-os_magnum master: Update fedora-atomic image to version 27 following upstream docs  https://review.openstack.org/63791215:42
*** cmart has joined #openstack-ansible15:42
*** weshay has joined #openstack-ansible15:51
weshay0/15:52
*** sdake has quit IRC15:52
*** dalvarez has joined #openstack-ansible15:53
dalvarezhey15:53
dalvarezchandankumar:15:53
*** vnogin has quit IRC15:53
chandankumardalvarez: lucasagomes is looking into it15:54
mnaserbonjour everyone15:54
*** cshen has quit IRC15:55
*** sdake has joined #openstack-ansible15:58
openstackgerritMerged openstack/openstack-ansible-ops master: Add monitorstack data collection into ES  https://review.openstack.org/63745515:59
mnasermass ping alert16:00
mnasercloudnull, DimGR, d34dh0r53, hughsaunders, b3rnard0, palendae, odyssey4me, serverascode, rromans, erikmwilson, mancdaz, _shaps_, BjoernT, claco, echiu, dstanek, jwagner, ayoung, prometheanfire, evrardjp, arbrandes, scarlisle, luckyinva, ntt, javeriak, spotz, vdo, jmccrory, alextricity25, jasondotstar, admin0, michaelgugino, ametts, bgmccollum, darrenc, JRobinson__, colinmcnamara, thorst, adreznec, eil397,16:00
mnaserqwang,nishpatwa_, cathrichardson, drifterza, hwoarang, cshen, ullbeking, mnaser, nicolasbock, jrosser, cjloader, antonym, dcdamien, jamesdenton16:00
mnaser#startmeeting openstack_ansible_meeting16:00
openstackMeeting started Tue Feb 19 16:00:14 2019 UTC and is due to finish in 60 minutes.  The chair is mnaser. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: openstack_ansible_meeting)"16:00
openstackThe meeting name has been set to 'openstack_ansible_meeting'16:00
guilhermespo/16:00
mnaser#topic rollcall16:00
*** openstack changes topic to "rollcall (Meeting topic: openstack_ansible_meeting)"16:00
mnasero/16:00
evrardjpo/16:00
admin0\o16:00
chandankumar\o/16:00
jrosserhello!16:00
fnpanichi16:00
*** ianychoi has quit IRC16:00
mnaser#topic highlights from last week16:02
*** openstack changes topic to "highlights from last week (Meeting topic: openstack_ansible_meeting)"16:02
mnaseranyone want to start sharing some of the work they did last week ? :)16:02
prometheanfireo/16:02
*** sdake has quit IRC16:03
guilhermespI think the bug squash days were a success. We should keep the mood16:03
mnaseri think so too, it was awesome, we burned down through so much stuff16:04
mnaserunfortunately i couldnt participate as much as i would have but hey that's life16:04
evrardjpsorry I couldn't attend to that16:04
evrardjpit's been epic here16:04
jrosserthe bug day was great16:05
mnaseri think it was just fun as well because we got to hack on plenty of things and i twas pretty feel-good overall :p16:05
evrardjpother highlights is that releasing will be easier in the future16:05
evrardjpmnaser: damn you're hitting my FOMO nerve16:05
guilhermespare we going to keep the idea?16:05
mnaserguilhermesp: i think maybe one every few weeks or so is better than like16:05
mnasera bug triage every meeting16:06
guilhermespsounds good16:06
mnaseri dunno, thoughts?16:06
guilhermespI think once a month and keep the bug triage every meeting16:06
mnaseryeah maybe we could do that16:07
evrardjpguilhermesp: some bugs need fast triaging16:07
mnaserother than that, any other last week updates to talk about?16:07
jrosseri have been digging at heat/magnum after a few folks had trouble with all the endpoint stuff16:08
guilhermespyes evrardjp that's why is important to keep in the meeting too every week16:08
evrardjpguilhermesp: sorry I don't know why I pinged you.. We were agreeing with each other :)16:08
guilhermespevrardjp: np!16:08
guilhermespjrosser: I saw you asked a question in openstack-containers16:09
jrosseryes, it's all a bit quiet in there16:09
guilhermespbut no reply till now16:09
guilhermespmaybe tag strigazi16:09
mnaserjrosser: can i help?16:09
mnaseri have contributed a bunch to magnum16:09
mnaseri can help make the appropriate fixes if they need to be done16:09
jrosseri'm sure, can we catch up after the meeting, i've found a few things i don't understand in the code16:10
mnasersure16:10
mnaserhappy to16:10
jrosseri think i've found a bug in heat about the endpoints too16:10
odyssey4meo/16:10
mnaserok, i'd be happy to ping the right people to get those fixed up16:10
chandankumarjrosser: http://logs.openstack.org/94/630694/13/check/openstack-ansible-deploy-aio_metal_heat-centos-7/bb028ec/job-output.txt.gz#_2019-02-19_09_22_50_86517416:11
*** markvoelker has joined #openstack-ansible16:11
chandankumarjrosser: is it somehthing like that on heat16:12
*** ianychoi has joined #openstack-ansible16:12
chandankumari can discuss after meeting16:12
mnasercool cool16:12
mnaser#topic open discussion16:13
*** openstack changes topic to "open discussion (Meeting topic: openstack_ansible_meeting)"16:13
mnaseri've been slowly trying to make this more office hoursy and looks like we have more .. people showing up and sticking around :)16:13
mnaserPTG is approaching, anyone wanna volunteer setup the initial etherpad? :)16:14
guilhermespIf I have a previous layout to be based on I can start this new etherpad mnaser16:15
mnaserguilhermesp: https://etherpad.openstack.org/p/osa-stein-ptg => osa-train-ptg ?16:15
cloudnullo/16:16
* cloudnull late but here 16:16
mnaser#action guilhermesp create ptg etherpad16:17
mnaserany other subjects that we wanna bring up?  maybe someone can help finish the last steps of aio nspawn in gate so we can maybe do the switch this cycle?16:17
guilhermespok mnaser16:17
mnaserwe're running out of time16:17
chandankumarmnaser: are we going to built container of tempest on nspawn?16:20
odyssey4mechandankumar we have all the bits in place, but there are a few outstanding issues with it which need addressing16:22
odyssey4meThe general plan is to move OSA to use nspawn instead of LXC for machine containers.16:22
guilhermesphttps://etherpad.openstack.org/p/osa-train-ptg WIP16:22
chandankumarodyssey4me: is it possible to run docker temepst container with nspawn? as tripleo uses kolla container so16:22
cloudnullchandankumar: docker no. but app container yes.16:23
odyssey4mechandankumar it is already, yes - we already do that with lxc - however, we use it as a machine container so we add systemd into it16:23
*** dswebb has quit IRC16:23
cloudnullsystemd-nspawn is the basis for rkt, which can run application containers.16:23
odyssey4meas cloudnull said, we could move to use an app container model16:24
odyssey4mebut that's a fair way off at this stage16:24
cloudnull^16:24
chandankumartempest is just an app, not a service, so I think it will work16:24
chandankumarok16:24
odyssey4mewe have a *lot* of assumptions around the services running on a full host, so the app container model does not work with OSA at this time16:24
cloudnullthat said, chandankumar if you have cycles to poke at it I'd be happy to help where I can16:24
evrardjpI am not sure we should outright kill that idea, it's just a binary blob after all :p16:25
chandankumarcloudnull: we are thinking to work on container support may be next cycle16:25
cloudnullsadly my time to focus on a lot of those things has largely evaporated16:25
evrardjpbut we are basically alone though16:25
chandankumaron os_tempest side16:25
odyssey4meyes, doing app containers is absolutely something we've talked about, but no-one has had the cycles to put into it16:25
odyssey4mechandankumar so if you folks have cycles to figure out a model, that'd be fantastic16:26
cloudnull+116:26
chandankumarsure!16:26
jamesdentonfolks, i have to bounce out for a bit. bbiaf16:27
cloudnullchao16:27
*** cmart has quit IRC16:31
*** cshen has joined #openstack-ansible16:33
odyssey4meFYI I've made some more progress on the python build simplification - just ironing out a few things before releasing them for review. Unfortunately my changes break the integrated build, so a few tweaks are still needed.16:33
odyssey4meIt's an issue with stackviz building left, which I just need a little more time on to get done.16:35
odyssey4meHeh, I see the issue and should have a patch up to solve it a bit later.16:37
chandankumarjrosser: still around?16:40
*** cshen has quit IRC16:40
jrosseryes i am16:40
chandankumarjrosser: http://logs.openstack.org/94/630694/13/check/openstack-ansible-deploy-aio_metal_heat-centos-7/bb028ec/job-output.txt.gz#_2019-02-19_09_22_50_86517416:40
mnaserodyssey4me: cool, when we're almost done, it would be good to get some info on that so we can replicate things across16:41
chandankumarjrosser: can you take a look at this failure, it is related to heat endpoint16:41
jrosserchandankumar: it is the same as other folks were seeing16:41
jrosserafter the meeting we can discuss some more16:41
chandankumarjrosser: https://github.com/openstack/heat-tempest-plugin/blob/9ca1fc2c55bceba078a6066d6d81447b1c8644d3/heat_tempest_plugin/tests/api/test_heat_api.py#L5716:43
chandankumarjrosser: sure16:43
*** markvoelker has quit IRC16:44
mnaserI think finding some more time to do reviews would be good too16:45
*** macza has joined #openstack-ansible16:47
mnaseri need to do more as well16:49
jrosserit would be great to get more of us on the case - we've all got different experience to bring16:49
*** hamzy has quit IRC16:50
odyssey4memnaser yep, I'll get the standard AIO done - then work up an etherpad for the rest for everyone to climb in while I shift focus to getting the AIO used for all tests16:54
mnaserodyssey4me: awesome16:54
chandankumarodyssey4me: is it possible to clone only those repo which are needed for a particular scenario?16:54
chandankumarin AIO16:54
odyssey4mechandankumar for now, no - but I have some ideas around how we could achieve that which we can discuss at the PTG, assuming I'm able to get there - unfortunately my travel is not yet approved16:56
* chandankumar is not going due to us visa issue :-)16:56
odyssey4mechandankumar :( At the next one then.16:56
chandankumarodyssey4me: yes for sure :-)16:57
*** pcaruana has quit IRC16:57
*** chandankumar is now known as kmrchdn17:12
odyssey4memnaser did I miss the end of the meeting?17:13
mnaser#endmeeting17:14
mnaserno17:14
*** openstack changes topic to "Launchpad: https://launchpad.net/openstack-ansible || Weekly Meetings: https://wiki.openstack.org/wiki/Meetings/openstack-ansible || Review Dashboard: http://bit.ly/2xA1eZC"17:14
openstackMeeting ended Tue Feb 19 17:14:01 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:14
mnaser:)17:14
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2019/openstack_ansible_meeting.2019-02-19-16.00.html17:14
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2019/openstack_ansible_meeting.2019-02-19-16.00.txt17:14
odyssey4mehahaha17:14
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2019/openstack_ansible_meeting.2019-02-19-16.00.log.html17:14
*** lucasagomes is now known as lucas-afk17:20
*** lucas-afk is now known as lucasagomes17:20
*** miloa has quit IRC17:21
jrossermnaser: got a minute for heat/magnum things?17:38
mnaserjrosser: sure, gimme 2 mins, do you wanna hop on zoom or something higher bandwidth to make it quicker/easier to explain?17:39
*** markvoelker has joined #openstack-ansible17:41
*** cmart has joined #openstack-ansible17:41
*** mma has quit IRC17:42
jrosseryes - i have about 20mins till i need to travel17:42
*** DanyC_ has joined #openstack-ansible17:43
mnaserjrosser: im ready if you'd like17:46
*** DanyC has quit IRC17:47
mnaserjrosser: https://zoom.us/j/330771324 if thats easier?17:47
mnaserunless you prefer ascii :)17:47
* jrosser tries the link17:47
*** kopecmartin is now known as kopecmartin|off17:53
*** markvoelker has quit IRC18:14
*** sreejithp has quit IRC18:14
*** sreejithp has joined #openstack-ansible18:14
*** hamzy has joined #openstack-ansible18:17
kmrchdnmnaser: anything we can improve in os_tempest report?18:26
kmrchdnit appears kind of boring, when I put all the all the reviews there18:26
*** kmrchdn is now known as chandankumar18:26
chandankumaras none wants to read long emails,18:26
chandankumarwhat about adding stuff which I learned each week?18:27
*** hamzaachi has quit IRC18:27
mnaserchandankumar: i really enjoy them tbh, i think they do a good update and i wish i can get myself to do the same for OSA18:33
mnaseri read through every single one and i find them informative, but maybe we can have some goals in there and then update each week about these goals and targets ?18:33
chandankumarmnaser: may we can reproduce a newletter as keystone or zuul does?18:33
chandankumarmnaser: open an etherpad people will highlight the stuff and we can can send it together18:34
mnaserchandankumar: yes, i think the neat thing that zuul does is they maintain an etherpad where they always add things into18:34
mnaseryeayh18:34
chandankumarmnaser: glad you liked the status update :-)18:34
odyssey4mechandankumar I like it too, now that I have fixed my access to the ML. :)18:36
chandankumarodyssey4me: :-)18:36
openstackgerritCam J. Loader (cjloader) proposed openstack/openstack-ansible master: Add iputils to utility container  https://review.openstack.org/63797018:46
cjloaderodyssey4me: mind reviewing ^?18:50
odyssey4mechandankumar cjloader given that https://github.com/openstack/openstack-ansible-os_tempest/commit/f30f002d4b5db1cb30a0b7d669ba19e774e99e8e added a dependency on ping (because the ping test is on by default), then surely the os_tempest role should install the requisite package for it?18:53
odyssey4mechandankumar alternatively, perhaps the default should be to disable that test?18:54
chandankumarodyssey4me: yes it should install required packages18:55
chandankumarodyssey4me: we have added ping stuff for debugging in lsx containers specifically18:55
chandankumar*lxc18:55
odyssey4mechandankumar I personally prefer to see dependencies implemented in the roles that depend on them. It helps with maintenance later, should that dependency ever go away.18:56
prometheanfireodyssey4me: is there some kind of gathering that takes place so that all the deps can be installed at once (union of nova/foo/bar/tempest)?18:58
odyssey4meprometheanfire no, ansible doesn't work that way unfortunatey18:58
prometheanfireodyssey4me: that's what I thought, not too big of a deal though18:59
odyssey4meexecution is task by task - it is very simple that way, even if it is very slow18:59
prometheanfireyep19:00
prometheanfireregistering vars would only work for following roles19:01
cjloaderso chandankumar odyssey4me prometheanfire are we agreeing it should go in the role?19:03
prometheanfirethe tempest role? yes19:03
*** electrofelix has quit IRC19:03
odyssey4mecjloader yep19:04
cjloaderokay19:04
odyssey4meprometheanfire can you propose the backports for https://review.openstack.org/636388 on top of https://review.openstack.org/#/q/Id4872caed2cba6b2ef31e850cde63a2a88d55250 please?19:07
prometheanfireodyssey4me: without looking, pike?19:07
prometheanfirenope19:07
odyssey4meprometheanfire well, with the other patches, the suplicate section is now present in all the other branches where those backports were proposed19:07
odyssey4me*duplicate19:08
prometheanfireah, thought I proposed it, will do then19:08
odyssey4meand I'm guessing you're going to want to port https://review.openstack.org/637210 back too once it merges, and that will need to be on top of the backports of https://review.openstack.org/63638819:08
odyssey4meawesome, thanks19:08
odyssey4meI'd really prefer not to have the duplicate section make it into a release by mistake.19:09
*** DanyC_ has quit IRC19:09
prometheanfireodyssey4me: I might just wait for stuff to merge since they are all workflowed back to pike19:09
prometheanfireand ya, that'd be nice to backport but as you noted it still technically works19:09
prometheanfireit's formatting only19:10
*** markvoelker has joined #openstack-ansible19:11
odyssey4meI think it'd be good to do - it reduces confusion when trying to figure out why something's not working.19:11
prometheanfireyep19:11
openstackgerritKevin Carter (cloudnull) proposed openstack/openstack-ansible-ops master: Ensure upper and lower memory limits are whole numbers  https://review.openstack.org/63797519:12
odyssey4meOK folks, I'm out for the night - and possibly the week too. I've got to sand and paint my kitchen this week, but I may check in from time to time to give my tired arms a break. ;)19:15
cjloaderwait odyssey4me19:15
cjloaderwhy shouldn't the utility container have the ability to ping19:16
prometheanfireodyssey4me: nn, sanding sucks, good luck19:16
cjloader(from d34dh0r53)19:16
prometheanfireuse machines as you can19:16
odyssey4mecjloader d34dh0r53 that's not the point - the point is that the dependence on ping is in the tempest role... if someone would like to ping from the utility container in general, then they can override the utility container package list or we can add another var for extra things... we've done a ton of work this cycle to reduce unnecessary package installation which slow down the deployment and increase the bloat19:18
odyssey4meOSA only needs to deploy what it requires - anything additional desired by a deployer can be implemented afterwards19:18
odyssey4meof course we can also implement something which is opt-in which adds extra nice-to-have packages to the utility container... but then the gate doesn't need it, so it won't opt-in19:20
openstackgerritKevin Carter (cloudnull) proposed openstack/openstack-ansible-ops master: Add dynamic group detection to openstack metrics  https://review.openstack.org/63798019:26
*** hamzaachi has joined #openstack-ansible19:33
*** sdake has joined #openstack-ansible19:34
*** mgariepy has quit IRC19:40
*** markvoelker has quit IRC19:44
cjloaderwell if the gates deploy os_tempest.....its a reqd pkg19:46
*** DanyC has joined #openstack-ansible19:49
openstackgerritMichael Vollman proposed openstack/openstack-ansible-os_nova master: Avoid distro installing unused services  https://review.openstack.org/63327519:51
*** sdake has quit IRC19:52
*** sdake has joined #openstack-ansible19:55
*** DanyC has quit IRC19:56
*** DanyC has joined #openstack-ansible19:57
*** sdake has quit IRC19:58
*** openstackgerrit has quit IRC20:09
*** alvinstarr has quit IRC20:25
*** DanyC has quit IRC20:28
*** DanyC has joined #openstack-ansible20:28
*** openstackgerrit has joined #openstack-ansible20:34
openstackgerritKevin Carter (cloudnull) proposed openstack/openstack-ansible-ops master: Correct service name when running with upstart  https://review.openstack.org/63799220:34
openstackgerritKevin Carter (cloudnull) proposed openstack/openstack-ansible-ops master: Add dynamic group detection to openstack metrics  https://review.openstack.org/63798020:35
openstackgerritKevin Carter (cloudnull) proposed openstack/openstack-ansible-ops master: Add dynamic group detection to openstack metrics  https://review.openstack.org/63798020:35
openstackgerritMerged openstack/openstack-ansible-os_nova stable/queens: Update the pci config for nova.  https://review.openstack.org/63639720:35
openstackgerritMerged openstack/openstack-ansible-os_nova stable/rocky: Update the pci config for nova.  https://review.openstack.org/63639120:35
openstackgerritMerged openstack/openstack-ansible-os_nova master: update pci_passthrough template variables  https://review.openstack.org/63721020:35
*** DanyC has quit IRC20:38
*** markvoelker has joined #openstack-ansible20:41
*** DanyC has joined #openstack-ansible20:43
*** coolj has joined #openstack-ansible20:44
openstackgerritMatthew Thode proposed openstack/openstack-ansible-os_nova stable/rocky: update pci_passthrough template variables  https://review.openstack.org/63800320:52
openstackgerritMatthew Thode proposed openstack/openstack-ansible-os_nova stable/queens: update pci_passthrough template variables  https://review.openstack.org/63800420:54
openstackgerritMatthew Thode proposed openstack/openstack-ansible-os_nova stable/pike: update pci_passthrough template variables  https://review.openstack.org/63800620:56
*** DanyC has quit IRC20:57
prometheanfireodyssey4me: all backported ^ https://review.openstack.org/#/q/is:open+project:openstack/openstack-ansible-os_nova+topic:pci-passthrough20:58
openstackgerritMerged openstack/openstack-ansible-ops master: Ensure upper and lower memory limits are whole numbers  https://review.openstack.org/63797521:06
*** markvoelker has quit IRC21:13
*** hamzaachi has quit IRC21:20
openstackgerritShannon Mitchell proposed openstack/openstack-ansible-os_tempest master: Update workspace tempest.conf on changes  https://review.openstack.org/63801421:25
openstackgerritJacob Wagner proposed openstack/openstack-ansible-ops master: Add ability to deploy designate with BIND9 servers  https://review.openstack.org/63561121:28
*** ArchiFleKs has quit IRC21:32
*** ansmith has quit IRC21:34
openstackgerritMerged openstack/openstack-ansible-ops master: Add dynamic group detection to openstack metrics  https://review.openstack.org/63798021:35
openstackgerritKevin Carter (cloudnull) proposed openstack/openstack-ansible-ops master: Correct service name when running with upstart  https://review.openstack.org/63799221:39
*** hamzy has quit IRC21:41
*** devx has quit IRC21:47
*** ArchiFleKs has joined #openstack-ansible21:51
*** yetiszaf has quit IRC21:52
openstackgerritCam J. Loader (cjloader) proposed openstack/openstack-ansible master: Add iputils to utility container  https://review.openstack.org/63797021:54
cjloaderd34dh0r53: noonedeadpunk ^21:54
jrosseri thought that the conclusion was that dependencies of tempest should go in the tempest role21:58
*** sdake has joined #openstack-ansible21:59
jrosserand the package names are not the same on all distros either afaik21:59
*** DanyC has joined #openstack-ansible22:03
openstackgerritMerged openstack/openstack-ansible-os_nova stable/pike: Update deprecated option for pci passthrough  https://review.openstack.org/63639822:04
*** dave-mccowan has quit IRC22:07
openstackgerritShannon Mitchell proposed openstack/openstack-ansible-os_tempest master: Update workspace tempest.conf on changes  https://review.openstack.org/63801422:07
*** DanyC has quit IRC22:07
*** sdake has quit IRC22:09
openstackgerritShannon Mitchell proposed openstack/openstack-ansible-os_tempest master: Update workspace tempest.conf on changes  https://review.openstack.org/63801422:10
*** markvoelker has joined #openstack-ansible22:10
openstackgerritMerged openstack/openstack-ansible-os_nova stable/pike: Update the pci config for nova.  https://review.openstack.org/63639922:12
cjloaderwell, d34dh0r53 had a question22:12
cjloaderso i'm updating the PR until resolved22:13
cjloaderjrosser22:13
openstackgerritShannon Mitchell proposed openstack/openstack-ansible-os_tempest master: Update workspace tempest.conf on changes  https://review.openstack.org/63801422:16
*** phasespace has joined #openstack-ansible22:17
*** DanyC has joined #openstack-ansible22:23
openstackgerritMerged openstack/openstack-ansible-ops master: Correct service name when running with upstart  https://review.openstack.org/63799222:27
openstackgerritShannon Mitchell proposed openstack/openstack-ansible-os_tempest stable/rocky: Update workspace tempest.conf on changes  https://review.openstack.org/63803022:38
*** markvoelker has quit IRC22:44
openstackgerritShannon Mitchell proposed openstack/openstack-ansible-os_tempest stable/queens: Update workspace tempest.conf on changes  https://review.openstack.org/63803222:45
openstackgerritShannon Mitchell proposed openstack/openstack-ansible-os_tempest stable/pike: Update workspace tempest.conf on changes  https://review.openstack.org/63803622:48
*** vnogin has joined #openstack-ansible23:05
*** shananigans has quit IRC23:06
*** vnogin has quit IRC23:09
*** ansmith has joined #openstack-ansible23:14
*** sreejithp has quit IRC23:16
prometheanfirejust want to make sure, but is it ever planned for OSA to support running one distro's container on another distro's host?23:34
*** markvoelker has joined #openstack-ansible23:41
*** tosky has quit IRC23:58

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!