Wednesday, 2015-12-16

*** markvoelker has quit IRC01:29
eglute_sthank you hogepodge and thanks to Mark for commenting02:17
*** markvoelker has joined #openstack-defcore02:29
*** markvoelker has quit IRC02:34
*** markvoelker has joined #openstack-defcore03:46
*** markvoelker has quit IRC03:50
*** eglute_s is now known as eglute05:00
*** ChanServ changes topic to "Next Meeting December 16, 10 AM CST https://etherpad.openstack.org/p/DefCoreRing.6"05:01
*** markvoelker has joined #openstack-defcore05:46
*** markvoelker has quit IRC05:51
*** markvoelker has joined #openstack-defcore06:47
*** markvoelker has quit IRC06:52
*** markvoelker has joined #openstack-defcore08:48
*** markvoelker has quit IRC08:53
*** pilgrimstack has quit IRC09:35
*** pilgrimstack has joined #openstack-defcore09:47
*** markvoelker has joined #openstack-defcore10:49
*** markvoelker has quit IRC10:53
*** markvoelker has joined #openstack-defcore12:35
*** markvoelker has quit IRC12:39
*** markvoelker has joined #openstack-defcore13:09
*** breitz has quit IRC13:32
*** breitz has joined #openstack-defcore13:32
*** FallenPegasus has joined #openstack-defcore13:57
markvoelkerLooks vaguely familiar, no? https://www.cloudfoundry.org/cloud-foundry-the-only-industry-standard-cloud-app-platform/14:19
markvoelkerWow though: "The cost for certification of an offering is $50K USD for this certification year, discounted to $30K USD for Cloud Foundry Foundation members."14:26
*** mordred has joined #openstack-defcore14:38
mordredmarkvoelker, hogepodge: any thoughts on what term I should use in that resolution to be clear that it's about the compute trademark stuff?14:39
mordredis saying "OpenStack Powered Compute" there too specific?14:39
markvoelkermordred: http://www.openstack.org/brand/interop/ < I think OpenStack Powered Compute is fine.14:40
mordredmarkvoelker: if we added a new trademark program that also included compute though, would the TC need to come back and pass another resolution that says "it applies to this too"14:42
mordredI think the intent is "anything that includes a compute component needs this"14:42
markvoelkermordred: Probably not...if we create another program like "OpenStack Powered Platform" that includes compute capabilities plus other stuff, it'll likely have OpenStack Powered Compute as a subset (like Platform does today).14:43
markvoelkermordred: and either way, I think it's probably far off enough that we can worry crossing that bridge when we eventually come to it.14:44
mordredok14:46
mordredcool14:46
mordredthanks!14:46
mordrednew version uploaded - also includes a link to that :)14:51
markvoelkermordred: excellent, I'll give it a gander in a few14:51
hogepodgemordred: getting clarification that compute, in the context of OpenStack, means a full operating system, is very helpful. If a new component is created later on that captures things like containers, we will use distinct terminology15:08
mordredhogepodge: I honestly think that revelation last week in the meeting was _super_ helpful15:15
mordredhogepodge: I'm not sure any of us had thought about it in precisely those terms before, but at least for me it definitely makes the "how does OpenStack relate to containers" thing much more real15:16
hogepodgemordred: I've heard some opinions in the community that compute should be defined as broadly as possible, so it helps to have the TC nail it down and take the ambiguity away.15:17
hogepodgemordred: I'm happy to see how we're iterating on this process. We're doing good work imo (even if it's taking a bit longer than we might like and is a bit painful at times)15:17
mordredhogepodge: I believe we're well past the usefulness of broad definitions :)15:18
mordredhogepodge: ++15:18
mordredhogepodge: after this one - it sort of makes me want the TC to make a broader 'intent' document - because really specific intent like this is useful both for other folks, and and because it causes TC folks to really think about it too15:19
markvoelkermordred: personally I'd also like to see some of the individual projects do something like that.  Several have taken or accelerated individual actions once DefCore discussions surfaced issues now.  Feels like the time's ripe.15:25
mordredyah15:29
*** edmondsw has joined #openstack-defcore15:31
*** mfisher_ora has joined #openstack-defcore15:33
*** edmondsw has quit IRC15:38
eglutemarkvoelker that cloud foundry certification price is a bit high! it is not in the article you linked, do you have a source?15:50
markvoelkereglute: https://www.cloudfoundry.org/use/cloud-foundry-certified/frequently-asked-questions/15:50
eglutethanks! wow, they are basically charging for the trademark use.15:51
markvoelkereglute: BTW, I mentioned this in the etherpad, but I'll likely have to lurk for the 1st half of the meeting today on account of a conflict.  hogepodge is probably doing the same for the whole time today as he's in TX.15:56
egluteI just saw that, thanks markvoelker! I am also in TX, but will not be lurking :)15:56
*** dwalleck has joined #openstack-defcore15:57
*** zehicle has joined #openstack-defcore16:01
*** zehicle has quit IRC16:01
*** dwalleck has quit IRC16:02
*** zehicle has joined #openstack-defcore16:02
*** dwalleck has joined #openstack-defcore16:02
*** pbredenb has joined #openstack-defcore16:11
*** pbredenb has left #openstack-defcore16:12
*** pbredenb has joined #openstack-defcore16:15
*** pbredenb has left #openstack-defcore16:16
-openstackstatus- NOTICE: Gerrit will be offline for a software upgrade from 17:00 to 21:00 UTC. See: http://lists.openstack.org/pipermail/openstack-dev/2015-December/081037.html16:19
*** dwalleck has quit IRC16:27
mfisher_oramordred: please verify my understanding on this.  A remote_client that had Solaris-isms for the CLI commands would never be acceptable, because you can't test them.  Is it the way the gates are set up that you couldn't test them, or is it because you wouldn't have a Solaris image?17:01
-openstackstatus- NOTICE: Gerrit is offline for a software upgrade from 17:00 to 21:00 UTC. See: http://lists.openstack.org/pipermail/openstack-dev/2015-December/081037.html17:03
*** ChanServ changes topic to "Gerrit is offline for a software upgrade from 17:00 to 21:00 UTC. See: http://lists.openstack.org/pipermail/openstack-dev/2015-December/081037.html"17:03
*** ChanServ changes topic to "Next Meeting January 6, 10 AM CST https://etherpad.openstack.org/p/DefCoreRing.7"17:10
*** FallenPegasus is now known as MarkAtwood17:10
*** catherineD has joined #openstack-defcore17:12
mordredmfisher_ora: it's the solaris image part17:16
mfisher_oraokay, I just mentioned this to one of our developers and he points out that you can get the Solaris 11 image for free: http://www.oracle.com/technetwork/server-storage/solaris11/downloads/index.html17:22
mordredright ... but it's not open source17:22
mordredwhich means it violates https://wiki.openstack.org/wiki/Open17:23
mfisher_oraer can you point to me exactly what it would violate on that page?  My intention would be to make the solaris version of remote_client and add it to the Tempest tree so anyone could use it17:24
mfisher_oraAssuming QA accepts it of course17:25
mordredmfisher_ora: the problem is that solaris isn't open source - so although a human could download that image free of charge, that would put openstack engineers in a position where they had to use non-opensource tools to do things17:26
mfisher_oraI'm not trying to be dense, but can you give me an example of what tool?  This isn't about our out-of-tree driver, I'm just trying to address the gate tests issue at the moment17:27
mordredmfisher_ora: specifically, to test it, it would require downloading and using that image in a gate job. that would mena gate jobs would all of a sudden be using non-open source components17:30
mordredalso17:30
mordredif something goes wrong17:30
mordredthat would involve an openstack developer needing to troubleshoot what the failure is using non-open tools on an non-open platform17:31
mordredwhile there is nothing stopping consumers from running solaris in guests, making use of it a required component of a gate test means we've introduced a dependency on a non-open thing17:32
mfisher_oraEven if Oracle put ourselves on the hook to always be willing to fix issues like that when they came up?17:32
mfisher_orawilling / required17:32
mordredthat means the community is dependent on humans from one company to fix an issue17:32
mordredwhich is not scalable17:32
mfisher_oraokay, understood17:33
mordredI mean, I totally get where you're coming from - I wish a had a better / more helpful answer for you17:34
mfisher_oraWe're working on the other answer, it'll just take time :)17:34
mordredcool. I think the stable plugin interface thing you were talking about with mtreinish will certainly help here17:35
mfisher_oracertainly, and there's other things in the works to get us certification unless more stumbling blocks come up17:36
mordredexcellent17:37
*** logan- has quit IRC17:51
*** zehicle has quit IRC17:55
*** zehicle has joined #openstack-defcore18:49
*** MarkAtwood has quit IRC19:40
*** MarkAtwood has joined #openstack-defcore20:13
*** MarkAtwood has quit IRC20:18
*** zehicle has quit IRC20:39
-openstackstatus- NOTICE: Gerrit has been upgraded to 2.11. Please report any issues in #openstack-infra as soon as possible.20:59
*** zehicle has joined #openstack-defcore21:42
*** mfisher_ora has quit IRC21:51
*** MarkAtwood has joined #openstack-defcore21:58
*** zehicle has quit IRC22:00
*** zehicle has joined #openstack-defcore22:03
*** zehicle has quit IRC22:28
*** zehicle has joined #openstack-defcore22:52
*** zehicle has quit IRC23:24

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