text
stringlengths
0
1.62k
[2548.20 --> 2553.62] clever novel piece of tech in there um borrowed from the from the go world so definitely check it out
[2553.62 --> 2559.46] if if you haven't already um and you're interested in these sorts of things and now a word from our
[2559.46 --> 2567.10] sponsor rack space rack space rack space you know i thought about actually saying nothing but rack space
[2567.10 --> 2572.08] for the whole spot but i didn't think that would be cool and i don't think you would either and when i
[2572.08 --> 2577.16] told rack space about it they were like nah you can't do that but what they did want me to do is tell
[2577.16 --> 2581.22] you about how much they love open source and how much they appreciate you listening to the change log
[2581.22 --> 2586.44] and they want to give you and everyone else who wants it fifty dollars a month in credit for 12
[2586.44 --> 2591.76] months to explore their open cloud all you need is a free developer plus account to get started
[2591.76 --> 2595.96] go to the change law.com slash rack space and enjoy the open cloud
[2595.96 --> 2604.10] i really like that identity piece i've i've enjoyed that uh and go as well i think that's a great addition
[2604.10 --> 2610.64] to containers um what's the state of the specification is it like pretty much written are you looking for
[2610.64 --> 2618.72] feedback um how do people get involved so right now we are we're between a so the very first thing
[2618.72 --> 2624.02] we released was a 0.1.0 which is like essentially prototype here's ideas we wanted to put enough
[2624.02 --> 2629.02] rails on it that like the conversation you know could move forward but we didn't want to define
[2629.02 --> 2637.80] everything i think we cut yesterday 0.2.0 which is it's getting pretty good um but still moving um and
[2637.80 --> 2642.78] we've been keeping rocket kind of in track of the spec the whole time so we we are forced to think
[2642.78 --> 2650.04] through the spec with an implementation um and then our next major one is around a kind of we think
[2650.04 --> 2655.88] it's good so i'll you know outside implementations like go for it let's start doing the interoperability
[2655.88 --> 2661.44] thing folks that want to help kind of show that the standard works and then once we have a number of
[2661.44 --> 2666.92] sort of outside implementations then we'll call it 1.0 because that should just prove that the
[2666.92 --> 2672.12] the spec is pretty solid if we're able to get outside folks to contribute to it and and uh and
[2672.12 --> 2676.86] build their own things and we're starting to see it happen uh you know there was a c++ version that
[2676.86 --> 2682.30] was released of the app container spec um there's another one i can't recall off the top of my head
[2682.30 --> 2688.08] um but even that before we have a stable spec is pretty solid you know for a project that has been
[2688.08 --> 2694.86] out for about 45 days minus like 15 days of holidays in the middle there you know um so it's it's moving
[2694.86 --> 2701.42] moving along pretty quickly so no doubt you're eventually want to get rocket um in involved in
[2701.42 --> 2707.14] the core os product uh got a timeline on on that transition and will you continue to support docker
[2707.14 --> 2713.02] into the future so we'll definitely continue to support docker the rocket timeline depends on
[2713.02 --> 2720.52] how quickly rocket is production ready um and and so um you know it's a little bit tbd just because
[2720.52 --> 2726.16] we know like we don't even try to set timelines on our open source projects it's just kind of like
[2726.16 --> 2733.22] when it's ready it's ready um so uh it'll take a little bit of time to get 1.0 but um but it's moving
[2733.22 --> 2740.20] along very quickly we will you know at some point have a core os with rocket in it how those all
[2740.20 --> 2745.30] kind of play together uh you know we haven't really talked too much about i will say though
[2745.30 --> 2751.30] the original motivation of rocket and our use of containers is to treat it like a package manager
[2751.30 --> 2756.18] but our packages are different in that our packages are always up to date for you so you
[2756.18 --> 2762.06] could imagine building a package manager hint hint wink wink that also does auto updating you know
[2762.06 --> 2767.74] and and that's something that we would want to do for the docker platform itself you know as they
[2767.74 --> 2773.20] ship new features like constantly and ship uh you know security fixes and everything we would love to
[2773.20 --> 2778.54] deliver those extremely quickly to the user as an entire platform not just as treating it as our
[2778.54 --> 2783.46] package manager you know just like how we would love to help the mesos community run mesos on top of
[2783.46 --> 2788.42] core os um but to do that we would package it you know we would package those things we wouldn't make
[2788.42 --> 2794.68] it the primitive on core os for how you download and run the package if that makes sense yeah
[2794.68 --> 2802.00] cool sounds really cool um let me ask you this say i'm interested in core os because actually i am
[2802.00 --> 2810.08] kind of interested in core os say i am uh hypothetically um can it run pretty much anywhere
[2810.08 --> 2816.14] these days like amazon digital ocean is it just like any other linux distro that i can go install
[2816.14 --> 2825.70] onto a vps yep so we're on amazon digital ocean google open stack eucalyptus you know um on-prem
[2825.70 --> 2834.16] bare metal iso usb stick like vmware you name it um and you can run core os there um and the really
[2834.16 --> 2842.52] cool thing about core os is we when we when you run us on a bare metal server or you run us on a cloud
[2842.52 --> 2848.80] server the root file system is bit for bit identical we can pass a signature validation
[2848.80 --> 2854.58] on the on the entire root block device uh that says they're cryptographically identical which is
[2854.58 --> 2860.60] great from a security perspective like forget about ids it just doesn't matter anymore um and it's also
[2860.60 --> 2865.58] great from if you're at you know a developer and you want to target a consistent platform in different
[2865.58 --> 2872.02] environments we are we are 100 consistent so if you want to use abuntu on digital ocean and
[2872.02 --> 2876.46] amazon that's cool you can do that and they're pretty close but they're not like bit for bit
[2876.46 --> 2881.26] identical which is a kind of a requirement if you want actual portability uh between these things
[2881.26 --> 2886.92] um and so we we put a big emphasis on on core os to really nail some of these things home as we
[2886.92 --> 2889.72] as we get distributed across all the different cloud environments
[2889.72 --> 2899.16] i guess uh one closing question before we tail off to our super awesome end of show questions um
[2899.16 --> 2904.44] what what role does does quay play into if that's the way you said canadians say it k
[2904.44 --> 2911.42] maybe the french canadians key um what role does that play i guess into the future of core os and
[2911.42 --> 2917.74] uh this this open standard for the app container sure so first that's a great example of our commercial
[2917.74 --> 2923.76] offerings you could go and use an open source docker registry or you could use docker's hosted registry
[2923.76 --> 2932.58] um but we build a enterprise ready on-prem version of docker registry um that companies can go and buy
[2932.58 --> 2936.76] if they don't want to piece it together themselves and there's no alternative to that right now on the
[2936.76 --> 2942.86] market we have a complete monopoly on an on-prem kind of commercial ready version of of um of a docker
[2942.86 --> 2948.68] registry um so that's a perfect example of it's like hey you could go replace it with open source by
[2948.68 --> 2952.62] your teams piecing it together if they want or you could buy it off the shelf from us and you choose
[2952.62 --> 2958.02] and it incentivizes us to be interoperable with standards but also just do a great job of piecing
[2958.02 --> 2963.42] those things together for our customers now features of quay that we might add as they relate
[2963.42 --> 2967.22] to rocket and app container i think it's only natural to assume that we will support app container
[2967.22 --> 2972.44] and um docker you know just like all these other projects that are trying to target app container
[2972.44 --> 2976.92] it's moving right now so so we can't just ship it overnight we have to like get the spec firmed up
[2976.92 --> 2982.08] before we can have our tools support it as well um so that i think will only be another value prop
[2982.08 --> 2987.86] of of uh enterprise registry is you could choose the best container technology for you if you want
[2987.86 --> 2995.10] if you want the one that docker has put together that's fine if you want um you know ours uh you
[2995.10 --> 2998.72] could do it and we'll make sure they're all interoperable um and you can kind of choose which
[2998.72 --> 3005.20] one is best best tool for the job and having core os power all that's got to help the development team
[3005.20 --> 3013.26] sort of bug fix across the spectrum too exactly exactly well um alex it's definitely been fun
[3013.26 --> 3021.04] talking about uh app containers the standard uh rocket docker core os uh i think jared's excited
[3021.04 --> 3029.42] about it i've uh those who know the show well know i'm a front-end designer person who plays hacker
[3029.42 --> 3034.92] for fun on the radio as win used to say when he was co-host of the show he used to say that a lot
[3034.92 --> 3039.70] so it's kind of funny but i've actually done several server builds over the last couple years
[3039.70 --> 3045.46] and i've gotten more and more into my dev ops space but uh if jared's excited about core os i'm
[3045.46 --> 3049.96] excited about core os i hope it i hope you're excited about it because you don't want to care
[3049.96 --> 3054.90] about it i want you to say like i want to use core os because i don't ever want to have to worry
[3054.90 --> 3058.80] about a security patch i'll just let the core os guys take care of it for me because i think they
[3058.80 --> 3063.10] can do a better job than i see and that's exactly probably what you want right that's exactly what
[3063.10 --> 3068.82] exactly when harpley was around i was like oh man what do i gotta do and i'm not obviously as the
[3068.82 --> 3075.88] non-devops non-server builder person but does it part-time when he needs to sort of person um i was
[3075.88 --> 3080.50] thinking what the heck do i do i don't even know what the problem is exactly at the moment and then
[3080.50 --> 3085.26] you know i'm sort of playing ketchup because i'm less in the fringes on that stuff and you know while
[3085.26 --> 3090.44] we pay attention to open source and keep our finger on the pulse open source is big technology is big
[3090.44 --> 3095.58] you can't you know grasp it all and you know i was like what the heck do i gotta do and it would
[3095.58 --> 3100.68] have been nice to have a core os like thing where i can trust that you're going to auto update it on
[3100.68 --> 3105.50] my behalf with security but then you do have the fear side which jared pointed out earlier so you
[3105.50 --> 3110.36] sort of have this double-edged sword that so long as you keep doing your job right on security and
[3110.36 --> 3114.28] non-breaking i guess the containers sort of take care of that right well i can tell you what i did
[3114.28 --> 3119.86] on heart bleed is i went out and patched double-digit servers for my customers spent the whole day
[3119.86 --> 3126.22] patching servers so i could definitely uh get on board with somebody else pushing those security
[3126.22 --> 3131.34] patches onto my os that would be awesome we patched tens of thousands or hundreds of thousands of