Hyperledger Foundation Fabric, 9 Mar 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Hyperledger Fabric with Cello and Kubernetes Operators - Tong Li, IBM & Manank Patni

Description

Hyperledger Fabric with Cello and Kubernetes Operators - Tong Li, IBM & Manank Patni

Hyperledger Cello aims to bring the on-demand “as-a-service” deployment model to the blockchain ecosystem to reduce the effort required for creating, managing, and terminating blockchains. It provides a multi-tenant chain service efficiently and automatically on top of various infrastructures, e.g., baremetal, virtual machine, and more container platforms.

An Operator, on the other hand, is a method of packaging, deploying and managing a Kubernetes application which in this case, is a Hyperledger Fabric Deployment.

Kubernetes is the preferred choice of many developers when it comes to deploying their Fabric Application. The cello project provides a way for them to quickly set up their fabric infrastructure while still maintaining a high level of customization whenever required. Operators allow us to make our application highly automated by describing the various events and the resulting actions making operators fit for implementing highly sophisticated business logic in the production stage.

The cloud-like capabilities that are encoded into the Operator code can provide advanced user experience, automating such features as updates, backups, and scaling. All of this is accomplished using standard Kubernetes tools, CLI and API.

----
Hyperledger – Open Source Blockchain Technologies

Hyperledger is an open source community focused on developing a suite of stable frameworks, tools and libraries for enterprise-grade blockchain deployments.
It serves as a neutral home for various distributed ledger frameworks including Hyperledger Besu, Fabric, Sawtooth, Indy, as well as tools like Hyperledger Avalon, Cactus and libraries like Hyperledger Aries, Ursa. Learn more about Hyperledger projects: https://www.hyperledger.org/use

Case Studies: https://www.hyperledger.org/learn/case-studies
Training & Certification: https://www.hyperledger.org/learn/training
Tutorials: https://www.hyperledger.org/use/tutorials
Webinars: https://www.hyperledger.org/learn/webinars
Events: https://www.hyperledger.org/events
Vendor Directory: https://www.hyperledger.org/use/vendor-directory

Subscribe to the Hyperledger Newsletter: https://www.hyperledger.org/newsletter

Follow-us on Twitter @Hyperledger

Learn about Hyperledger Membership: https://www.hyperledger.org/about/join

#Hyperledger #HyperledgerGlobalForum2020 #Blockchain

A

Hello, everybody have a good lunch. Yeah, okay, probably had too much lunch.

A

My name is Tong Lee work for IBM committer for cello talk about yourself.

B

So my name is manag Putney and I am blockchain developer I did an internship for the Linux Foundation and with that in that I worked for the iPad as a cello team.

A

Okay, so we're gonna talk about actually a little bit about cello, then we're gonna dive into the the Cuban eighties fabric operator. So what is the cello cello started being a tool actually supposed to help users to deploy?

A

You know the products under a high polish, a foundation. So when we started we we actually you know, project that cello will help users to deploy fabric and other products as well, but it turns out that majority majority of the developers on cello actually all folks on fabric and then we kind of lost the capability of a deploy other products. You know on their own hi pleasure.

A

So now, if you look at a cello, it's mostly the agents that we have, this term agents deploy fabric onto different targets, meaning either it's they say kubernetes cluster, or it is the darker environment or some other platforms. So cello is really a tool that helps you to deploy fabric network at moment.

B

Okay, so syrup allows us to manage the lifecycle of a blockchain. We can create start/stop delete nodes, we can customize a blockchain network and, like configuration like network size, consensus type, the database type, and we have a few different and lying infrastructures available like we can deploy it on bare metal. You can deploy it on dark, unities, etc, and we also provide advanced features like monitoring, logging, health and analytics of our chain. So this is kind of like the architectural design of Zillow.

B

At the top layer we have the dashboards and the dashboards and the code layer. Both of these are connected with the api's. The APS are made in Django and the code layer is also made in Python and other node.js. So the last layer under the last layer is the agent layer where we can have multiple infrastructures like darker. We can use suam, we can use cuban, it is etc. So what exactly's capabilities operators? So operators are clients of communities API? They are like controllers for custom resources that communities have so operator.

B

What operator do is they aim to capture the the work of a human operator? So you, human operators have deep knowledge about how a system would work, how it would behave in certain conditions, so operators are basically meant to do that automatically without the need of a human, so operator is a method of packaging deploying and managing a communities application. So it helps us extend these applications by providing custom configurations to them.

B

We do it by using custom resource definitions, so this is our operator works, so a programmer deploy is a custom resource as well as a controller, so custom resource holds all the configuration details and specifications of our app, whereas the controller it handles all the business logic it handles all the other actions or the behaviors etc. So, once we deploy a custom resource and a controller, the controller will manage all this footage.

B

Stateful sets, it will manage the services, pod secrets, etc, and it will do it in any any actions like something happens to our pods. The controller will take charge and it will change. It will change the state. So we used operator SDK for that operator SDKs of framework. It allows us to write high-level, api's and scaffolding into and it is used for scaffolding and code generation. So, with the operator SDK, we can quickly ask bootstrap a new project which uses operator operators.

B

So now this is a typical life cycle. While we develop an operator using operator SDK, so the foundation level is where we create custom resources, we create controllers, etc, we define them and then we can test it locally and after we have tested it, and everything is fine. We can publish the images on any hub dock and help or something then we can test. It live with the cluster.

B

The operator image lives in the cluster and it will manage all of our all of our pods and other sub resources from there, so how we utilize the framework, so we created custom resource definitions for all of the nodes for fabrics such as see a pier and order, and then we implemented controllers for them. So what controllers did was to take the specification? For example, one is here so, as you can see, the kind of this resource is a cuss certificate authority. So and the specifications are not the usual ones UVC. These are.

B

These are custom definitions. We made them ourselves, so you can see we can provide the admin username, the admin password. You can also provide the size of our certificate authority. We can also pass on certificates here and we can pass on other details like how okay I wonder.

A

How many of you guys actually familiar with Cuban a DS operator or okay? We have quite few okay, good, okay, you might ask you know, there's so many different ways to deploy something application on to kubernetes. Why why do you choose to develop? You know, operators to deploy fabric right, you can use called chart, you can use I, don't know just the plain old uyama files to deploy various components, I said pods or whatever you know, PVC or like and stuff.

A

So the main reason why we pick the this framework is that you know, as some of you already know, that kunis operator is really. If you develop something that's operator, actually those things we call the customer defined resource, so it's become like a first class of cuba Nettie's resource. So you operate those resources. Just like you operate parts or services. Those sort of things, those are the men advantage, is why we pick the operator framework to develop those components that you can deploy fabric onto cuban on is environment.

A

I just want to add you probably wondering why I mean you're doing this.

B

So this is our dashboard. This is the cello dashboard and you can see there are multiple agents here, I created two of these agents, or both of them are operator frame operator agents. Only so, as you can see, these are the peers in CA are deployed on them. So once you have your agent set up on cello, you can deploy your nodes on there. So we have a very simple UI for doing that.

B

All you have to do is give some some information about your node and provide a configuration file that that is going to have this kind of details. So right.

A

I mean to be able to actually deploy component onto your kubernetes cluster. You normally you you would provide like you know the cubicle figure file right. So then you can actually access your qns cluster. So in this case you you create like this agent, then you say: hey I want to either create a see, a node or pure node or older node. So you pick different types. Then the operator itself actually will take. The information. Take your request. Yep you want to appear and we're gonna create a peer note on this queue in this cluster.

A

So this is what Monaca is showing.

B

Yeah, so, as you can see, we have three pol +, 1 CA and all of these are deployed on this agent, the agent fabric operator, one and yes, that's it. You can find the seller team on wiki on a rocket chat or fr coded is deployed on github at hi, Felicia, slashed cello, and you can find the documentation to do all of this stuff on AHA Daughtery the doors at I/o, and thank you.

A

B

Yeah, actually, we did enable TLS on it. You can see, we have a TLS certificate and a TLS key, which we can also provide with the ml file.

A

We start safe from scratch. Then you can use, say a that's one of the reason why we actually tried to see you know. First, then you can get all your certificates. Then when you do the peer note or older note, you supposed to provide those information.

A

Right I mean those tours, it doesn't have to always come from your say. You can have your own yeah.

B

A

And now the agent agent in cellos term actually is really a piece of program actually help you deploy those notes once those notes actually up running those the agent goes away. So it's not something constantly running so I I think he chose a really bad term here.

A

It it can run on many different clusters. It's just when you create this agent. It's a piece of a program and say hey it's more like a configuration of your agent say you have to provide some information in the points tokens so that we know as chello. We know that where you want your components to run so that's it.

B

Yeah, the agent we choose.

B

A

B

Different configuration, yeah yeah.

A

I mean once your peers up running, you still have to go through the fabric. No more, you know join tier two channel. That right, that will not be part of what cello is doing. Cello is get your notes up running right, I mean, then you have the api's to perform all those fabrica operations.

A

Yeah yeah yeah.

B

A

We considered that you know it's outside of a telescope.

A

B

A

That's the advantage of using accumulates operator, so you know if your nose actually goes down, it will start up restart yeah for you yeah. That's the one of the event other mines here just for used an operator.

B

Thank you, anything is well.

A

B

Thank you guys.