text stringlengths 0 1.62k |
|---|
• The platform provides a centralized patching and deployment system for users who opt into the service |
• For users who do not use the commercial update service, Core OS provides a package manager (Docker) to manage updates |
• Core OS has made its updates available for free as a community service, and commercial products are used to sustain the effort |
• Docker was initially used as a package manager and was a key component in building the Core OS system |
• The platform has also developed a tool called etcd, a distributed key-value store, to enable sharing of configuration across servers and to make it easier to build distributed platforms. |
• etcd's GitHub page and its maturity as an open-source project |
• Docker's evolution from a tool to a platform and its divergence from the original containerization philosophy |
• The reasons behind the creation of Rocket, a new tool for containerization, and its specifications |
• The announcement and reception of Rocket, including the subsequent press frenzy and controversy |
• The team's internal reaction to the launch of Rocket and the handling of external pressure and criticism |
• The lack of an open standard for containerization was a major issue |
• CoreOS decided to build their own solution, Rocket, instead of contributing to Docker |
• Rocket aims to provide a more secure, composable, and Unix-like containerization solution |
• CoreOS has invested in Rocket and it's coming along nicely |
• The goal is to create a shared standard for containerization between Rocket and Docker |
• Containers will be more widely adopted when there's a clear, open standard in place |
• Multiple implementations of a standard exist and it's beneficial for everyone |
• CoreOS is guiding the direction of containerization, but also wants to create a better Docker |
• The focus is on creating a better containerization solution, not just duplicating Docker |
• Docker and Rocket are compared and contrasted |
• The interviewee sees Rocket as a container runtime, like the original concept of Docker, while Docker is a more comprehensive platform |
• The interviewee believes that Rocket and Docker serve different purposes and are not redundant efforts |
• The interviewee discusses the benefits of competition in the marketplace, citing Firefox and Chrome as an example |
• The interviewee highlights security concerns with Docker's architecture and the need to refactor it to separate individual applications |
• The interviewee notes that rewriting Docker's architecture would be necessary to address these security concerns. |
• Discussion of Docker's security issues and the decision to refactor it into individual components |
• Comparison of Docker to Chrome and Firefox, and the idea of making it more composable and interoperable |
• Rocket's creation from scratch instead of forking Docker, due to differences in architecture and goals |
• Docker's change of business model from Docker Cloud to a new model, and its impact on the containerization ecosystem |
• Core OS's business model and approach to monetization through free updates and community services |
• App Container specification, a community-driven effort to standardize containerization |
• Review of the App Container specification, its components, and ownership. |
• Runtime environment consistency and portability |
• Container state and arguments (environment variables, config drive, metadata service) |
• Identity for containers (signed version of data posted to metadata service) |
• Image format, runtime, and image discovery specification |
• Docker's tightly integrated hub and image discovery/download process |
• Open source and interoperability with Rocket and Go programming language |
• App container specification progress and involvement opportunities |
• Rocket and CoreOS product transition and support for Docker |
• Motivation for Rocket and containers is to treat them like a package manager, with always-up-to-date packages |
• Desire to deliver updates quickly to Docker platform users, not just package managers |
• CoreOS can run anywhere, including Amazon, Digital Ocean, Google, and on-prem |
• Root file system is bit-for-bit identical, ensuring security and portability |
• Quay plays a role in the future of CoreOS and app container standards |
• Enterprise-ready on-prem Docker registry is available from Docker |
• Features of Quay will support app container and Docker standards |
• CoreOS will power development and bug fixing across the spectrum |
• Open source and core OS development |
• Security and auto-updating of OS |
• App container standard and interoperability |
• Need for third-party implementations of app container spec |
• Contribution opportunities for listeners, including system programming and distributed database work |
• App container spec available on GitHub as appc |
• Core OS CEO discusses what they would be doing if they weren't working at Core OS. |
• Desire to work more directly on products and technology. |
• Enjoyment of outdoor activities, such as windsurfing and white water rafting. |
• Mention of inflatable kayaks for river crossings. |
• Appreciation for being part of Core OS team and having control over projects. |
• Acknowledgement of sponsors, including Rackspace and CodeShip. |
[0.00 --> 15.86] welcome back everyone this is the change log and i'm your host adam stekowiak this is episode 138 |
[15.86 --> 23.14] jared and i talked to alex pulvey the ceo of core os great conversation today talking about |
[23.14 --> 28.78] containerization specifically their awesome new open source product called rocket a competitor |
[28.78 --> 34.56] to docker specifically to standardize the app container spec great conversation around that as |
[34.56 --> 41.04] well um alex great guy today going to have this conversation we have some awesome sponsors making |
[41.04 --> 46.12] the show possible code ship top towel and for those who do not know what i'm saying when i say top towel |
[46.12 --> 54.24] i'm saying t-o-p-t-a-l.com i'm assuming their their name i have never asked brendan this so this is |
[54.24 --> 58.62] going off the script a little bit whether or not their name is based on top talent i'm going to |
[58.62 --> 65.32] assume that but it's t-o-p-t-a-l.com top towel great support for the show and not to mention we also |
[65.32 --> 70.36] have the support of rack space we'll tell you a bit about those guys later in the show but code ship |
[70.36 --> 75.64] is an awesome sponsor of ours uh in fact one cool thing i want to mention about code ship recently |
[75.64 --> 81.02] they just listened to all sorts of feedback they got from their users uh and recently redesigned |
[81.02 --> 85.48] their entire application not only does the new design look better but it also has tons of new |
[85.48 --> 90.24] usability improvements to make things even easier than before you can set up continuous integration |
[90.24 --> 95.06] for your app in just a few steps and to pull your code with all your tests to pass no matter what |
[95.06 --> 98.00] language you use no matter what framework you use they have great support for lots of languages |
[98.00 --> 103.84] and frameworks they integrate with github or bitbucket uh you can deploy to cloud services like |
[103.84 --> 110.40] roku and aws setup takes just three minutes you can find code ship at code ship.com |
[110.40 --> 117.04] slash the changelog make sure you go to that url use the offer code the changelog podcast to get a |
[117.04 --> 124.26] 20 discount on any plan you choose for three months also you want to check out their blog at blog.coachship.com |
[124.26 --> 130.66] to get updates again the offer code to use is the changelog podcast and get 20 off on any plan you |
[130.66 --> 138.98] choose for three months and now on to the show all right today we're back hey the changelog here adam |
[138.98 --> 146.92] jared and alex alex pulvey from core os the ceo of core os uh we're here to talk about core os |
[146.92 --> 155.00] linux containers rocket specifically um maybe a little bit about docker who knows but alex welcome |
[155.00 --> 160.24] to the show how are you thank you for having me doing great doing great happy to share the story |
[160.24 --> 168.98] yeah i think um we've been watching docker closely um and obviously we're excited to see a new |
[168.98 --> 176.42] opportunity for you know not just docker but what rocket offers and you seem to have a unique way you |
[176.42 --> 182.44] brought it uh out i guess into the ecosystem of open source but before we go there maybe give an |
[182.44 --> 189.46] introduction to you know who you are and what you do at core os maybe maybe uh from that we'll blend |
[189.46 --> 196.80] into more a little bit more of like what chorus is just for the audience who may not know sure um so |
[196.80 --> 203.72] i am the ceo of core os i'm one of the co-founders with brandon phillips uh we started working on core |
[203.72 --> 210.60] os about two years ago now um before core os i was at rackspace uh which i joined through the |
[210.60 --> 216.42] acquisition of my previous company cloud kick um cloud kick built tools for cloud server monitoring |
[216.42 --> 224.02] management um and before coros brandon was um at novelle uh working on susi as a as a linux kernel |
[224.02 --> 230.10] developer so you know when you put a kernel guy and a cloud guy together you get a caudios |
[230.10 --> 239.78] there you go um and this is actually this is episode 138 right jared right and so since you |
[239.78 --> 244.04] mentioned rack space rack space is actually a sponsor of this show so it's kind of funny that |
[244.04 --> 252.40] you have some rack space in your blood yeah i bleed red yeah austin texas well the you know those who |
[252.40 --> 258.02] listen to the show forever but you may not know this alex um the changelog's born in texas right so |
[258.02 --> 264.38] we're not very far from your your your previous mothership so to speak got it got it so maybe a bit |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.