<transcript><audio_6>aligning with maturing CN CF projects we are making it more capable secure resilient and simpler to operate airship one auto-created purpose-built services for lifecycle management because many of</transcript><caption><image_7>The image is a slide from a presentation titled "Airship 2.0". It has a white background and black text. The title of the slide is written in a bold font at the top. Below the title, there is a subtitle that reads "Evolve the Control Plane". 

Below the subtitle, there are six icons arranged in a grid-like pattern. The first icon is a blue circle with a white outline, representing the Airship logo. The second icon is an icon of a cloud with a lightbulb inside it, representing a cloud computing icon. The third icon is of a light bulb with the text "Align with maturing CNC projects". The fourth icon is for "More secure & resilient" and the fifth icon is from "Simpler to operate".

The slide appears to be a tutorial or guide on how to use the airship software.</caption><caption><image_8>The image is a screenshot of an Airship Control Plane. It shows two options - Airship 10 and Airship 20. On the left side of the image, there is a blue rectangular box with the text "Airship 10" written on it. Below the text, there are two buttons - "Kubernetes" and "OK". On the right side, there appears to be a white rectangular box. The background is white and the text is written in black.</caption><transcript><audio_9>the required capabilities didn't exist in any open source projects the primary CN CF project kubernetes has introduced a new community adopted framework for managing services as native objects</transcript><transcript><audio_10>airship taro is moving its purpose-built service logic into these native objects that will live in kubernetes airship tenido will also introduce a new intelligent client and user interface that will interact with these native</transcript><caption><image_11>The image shows two boxes, one labeled "Airsthip Control Plane" and the other labeled "Airship 10". The first box is labeled "airship 10" and has a blue background. The second box has a white background and is labeled with the text "Airships 20". The text is written in black and is in a sans-serif font.

The first box on the left is labeled as "airships 10" with a blue border. It has a rectangular shape and is filled with text. The text inside the blue box reads "Kubernetes" which is a type of control panel used in the airship control system. The control panel has two rows of text, one for each airship and one for the control panel. The first row has a list of different types of control panels, such as "control panel" and "control panels". The second row has the same text as the first row, but it is not filled with more text.</caption><transcript><audio_12>objects thus evolve control plane will further reduce the impact of upgrades improve the operator experience and airship wand Ohno also had to create supporting software packages for</transcript><transcript><audio_13>capabilities that didn't exist yet in any upstream project CN CF is also catching up in this area with a portfolio of projects that aligns closely with airships requirements and</transcript><transcript><audio_14>roadmap this will help expand the use cases and operational capabilities as well as features supported in the next generation of airship another benefit of airship to datos smaller runtime footprint is that it is uniquely</transcript><video><caption><image_15>The image is a screenshot of a webpage titled "Align with Maturing CNCF Projects". It shows two sections of the webpage. 

On the left side of the image, there is a table with three columns. The first column is labeled "Airship 10" and the second column is titled "Benefits". The table has three rows and three columns, each representing a different aspect of the CNC project.

The first row has a list of options for the user to choose from. The options are:

- Airship 10, Airship 2.0, and Airship 3.0. The table also has a table that shows the benefits of each option. The benefits include:
- Operational capabilities
- Operations capabilities

There is also a button at the bottom right corner that says "Benefit". This button is likely used to enter the benefits for the project.</caption><caption><image_16>The image is a black and white photograph of a pen with the word "Ed" written on it. The pen has a silver body with a black tip and a black cap. The body of the pen is cylindrical in shape and appears to be made of metal. The cap is slightly curved and has a small opening at the top. The background is plain white.</caption><caption><image_17>The image is a text-based graphic with the title "Edge Deployment with Airship". The text is written in black and is in a simple, sans-serif font. The background is white and the text is centered in the middle of the image. The text appears to be a title or description for an article or presentation.</caption></video><transcript><audio_18>positioned to manage network functions at the edge this is possible because only the state of the whole plane is stored natively in kubernetes whereas the service objects</transcript><caption><image_19>The image is a diagram that shows the edge deployment with Airsthip. It is a rectangular box with a blue background and a white border. Inside the box, there is a title that reads "Edge Deployment with Airship" in black text. Below the title, there are three bullet points that explain the concept of airship deployment. 

The first bullet point is labeled "Before Deployment only the state is stored" and is located on the right side of the box. The second bullet point reads "Airsthip" and has a list of options below it. The third bullet point has a description of the airship, which states that it is a state that is stored in the state.

There is also a label on the bottom right corner of the image that says "Age Host".</caption><transcript><audio_20>run when needed in addition to private cloud airship Toronto is positioned to manage network functions at more deployment targets such as third party clouds this is possible because airship tirado is integrating with the CN CF</transcript><caption><image_21>The image shows a diagram of a 3rd Party Cloud and more. On the left side of the image, there is a white rectangular box with a blue label that reads "Kubernetes". On the right side, there are two rectangular boxes, one labeled "Private Cloud" and the other labeled "Cloud". The first box is connected to the third party cloud, which is represented by a blue arrow. The second box is also connected to a cloud with a white label. The background is white and the text "3rd PartyCloud and more" is written in black at the top.</caption> aligning with maturing CN CF projects we are making it more capable secure resilient and simpler to operate airship one auto-created purpose-built services for lifecycle management because many of the required capabilities didn't exist in any open source projects the primary CN CF project kubernetes has introduced a new community adopted framework for managing services as native objects airship taro is moving its purpose-built service logic into these native objects that will live in kubernetes airship tenido will also introduce a new intelligent client and user interface that will interact with these native objects thus evolve control plane will further reduce the impact of upgrades improve the operator experience and airship wand Ohno also had to create supporting software packages for capabilities that didn't exist yet in any upstream project CN CF is also catching up in this area with a portfolio of projects that aligns closely with airships requirements and roadmap this will help expand the use cases and operational capabilities as well as features supported in the next generation of airship another benefit of airship to datos smaller runtime footprint is that it is uniquely positioned to manage network functions at the edge this is possible because only the state of the whole plane is stored natively in kubernetes whereas the service objects run when needed in addition to private cloud airship Toronto is positioned to manage network functions at more deployment targets such as third party clouds this is possible because airship tirado is integrating with the CN CF
{"source": "grass-yt-cc-by.13v3z4EIK9I|shard_10046_55|create_multimodal_data.extract_yt_and_generate_transcripts.36|shard_10046|create_multimodal_data.generate_captions.37|shard_10046|create_multimodal_data.generate_captions.58", "params": {"id": "13v3z4EIK9I", "channel_id": "UCQ74G2gKXdpwZkXEsclzcrA", "duration": 196, "view_count": 1527, "age_limit": 0, "chapters": [{"start_time": 0, "end_time": 8.0, "title": "<Untitled Chapter 1>"}, {"start_time": 8.0, "title": "Airship is ...", "end_time": 22.0}, {"start_time": 22.0, "title": "Airship is on a Journey", "end_time": 31.0}, {"start_time": 31.0, "title": "Airship 2.0", "end_time": 47.0}, {"start_time": 47.0, "title": "Airship Control Plane", "end_time": 94.0}, {"start_time": 94.0, "title": "Align with maturing CNCF Projects", "end_time": 123.0}, {"start_time": 123.0, "title": "Edge Deployment with Airship", "end_time": 145.0}, {"start_time": 145.0, "title": "3rd Party Cloud and more", "end_time": 196}], "like_count": 14, "channel_follower_count": 45900, "license": "Creative Commons Attribution license (reuse allowed)", "uploader_id": "@OpenInfraFoundation", "yt_tar_file": "/leonardo_work/EUHPC_E03_068/audio/fixed_download/grass-yt-cc-by//shard_10046/13v3z4EIK9I.tar.gz"}}