 Hello everyone. Good morning, good afternoon, or good evening, depending on where in the world you are zooming in from. I'm glad to have you joined and we will be starting in just a couple of minutes to give some other people time to join as well. Hello everyone. Good morning, good afternoon, or good evening, depending on where in the world you're zooming in from. Welcome to Hyperledger Foundation in-depth webinar with Ziv about enterprise DevOps automation for launching and managing your blockchain network. We will be starting in just a couple of minutes to give people a chance to join. While we wait, I would encourage you to use the chat to say hello, tell us where you're zooming in from. I'm zooming in from Heidelberg, Germany, where it's currently 7pm in the evening. We'll be starting in just a couple of minutes. Hello everybody that's joining and good morning, good afternoon, or good evening. And welcome to the Hyperledger Foundation in-depth webinar. We'll get started in a couple of minutes and while we wait, please use the chat to let us know where you're zooming in from and just to say hello. Hello everybody joining us. Good morning, good afternoon, or good evening, depending on where in the world you are zooming in from. You are very welcome and we're happy to have you at our Hyperledger Foundation in-depth webinar with Ziv on enterprise DevOps automation for launching and managing your blockchain networks. We are delighted to share our next webinar with you. My name is Tomas today and I'm an ecosystem manager at the Hyperledger Foundation. Today, I will have a chance to introduce you to our panelists and also take you through some housekeeping. So our panelists for today are Sankalb Sharma, who is a co-founder and VP of engineering at Ziv and Lakshar Gaur, blockchain architect at Ziv. First, as and as usual, if you attended any other Hyperledger Foundation webinars, we have some housekeeping. First of all, I would like to emphasize that everyone is welcome in the Hyperledger community. We are committed to creating a safe and welcoming community for all. So please follow our code of conduct when interacting with each other and when talking to other people in community as well. You can find their code of conduct in our wiki and on our web page as well. Our Hyperledger Foundation member webinars are held under antitrust policy, which you can find on our wiki and on our web page as well. We are recording this webinar and the recording will be available for you to review later in our webinar library and also on YouTube. And we are also live on YouTube. So hello everybody joining us on the YouTube as well. Now we encourage these sessions to be as interactive as possible. So please stay active and the more active you are, the more everybody will get out of it. So please use your raise your hand button to get unmuted and to speak up and we will have a Q&A session after the presentation. You can also use either chat or Q&A box and we will be answering those questions as well. For those following us on YouTube, please use the comment on YouTube and we will get to your questions also. Now without further ado, I would like to give the word over to Sankalp and Lakshay and really looking forward to the presentation. Sankalp and Lakshay, over to you. Hi everyone. Thanks for tuning in. We're very happy to be here and present you what you've been working on. And hopefully you guys will be as excited to see what we've got for you as much as we have to show you. I'll share my screen and I think we can just quickly go over to the whole agenda as above. So we've been here at Zee, we've been working at Blockchain Automation for quite a while now. We decided working with Hyperjit Fabric when it was just a nascent level project at its alpha stage. We remember the 0.5-0.6 version when it was first introduced and we were just some crazy researchers trying to pull some threads into it and trying to make something happen. Those were some complicated days, but yeah, a lot has changed since then. So what have we seen over our experience with Hyperjit community with all the blockchain interests that has been peaking around the world? We found that there's so much of potential that is still untapped, but much of it is now getting converted to a good extent. But over the time we're working with so many domains, we found out that the adoption is still very slow and there are a lot of challenges that companies like R face ourselves at the time. And these adoption challenges are easily somewhere which are unexpected than what most people would expect. So we know that blockchain has been picking up quite a bit, especially on the enterprise segment where we have, we understood and decided our strategy priority. Blockchain in production has increased quite a bit and we've got so much of technical strength, you know, bringing contributing to our blockchain projects around the globe. So that has really picked up as well. We've seen a lot of value chains, creating assets and putting it on blockchain and people can really confidently say that it's really giving value to what our processes are. And we can see governments all around really giving a good participation to all of this and making things happen, which is really grateful for us to be to them. And it's supposed to go more and more from here on the, it's only getting started. But what were the challenges that we actually saw. They were around, not as much as development or testing or thinking around outside the box that was, maybe had too many brains over much of the documents that was already happening. But the difficulties were more from the infrastructure side, more from the DevOps side that people didn't really understand how to treat this as a technology. Right, so they had a lot of trouble, people had a lot of learning curve, and it came to picking up blockchain frameworks like such as happily fabled. There was a big learning curve to understanding the depths of it, what is security, why standard for it, what is, you know, good for your project for your performance, what kind of quality you should go for, there was just too much. And then you would expand your consortium to a second stakeholder and you would come see more challenges, multiplied by the model stakeholders. The second one would mean that you have to redo it again, perhaps in a different deployment strategy with a different cloud provider or something like that. So adoption was really slow and difficult and it's too costly to painful. So we came over to trying to solve this problem for ourselves and that's when we came about to have a seat as a platform, which can help us manage our blockchain networks, scale our blockchain networks, scale our consortiums, and still, you know, use the tools of today to do the things for tomorrow. Right, you know, that's the whole purpose of how we came about to have a zero platform. Xeva is heterogeneous to all cloud departments so you can configure your own cloud account to which you want to deploy your blockchain networks nodes towards. It can provide you real-time monitoring analytics for your blockchain nodes and networks so it captures not only system level details, but also blockchain details as well which are very much relevant for you and very hard to come by when you are managing your blockchain networks. It ultimately solves your time, it cuts down your time by quite an extent, you can create your DAF applications in just a fraction of the time that you could have done otherwise. And all of this pretty much means that if you cut down your cost by 60%, that's what we've observed. This is on the a lenient side of things. It can cut down your market time to market by 90% and that's because much of the complications go towards devolves automation of your environments with its DAF staging prod and then scaling your prod towards the stakeholders so that can take quite a bit. So it cuts down your time to market by quite a bit. And we've got a whole community for you guys so it's for you to make benefit from. So we've got a lot of bunch of a big knowledge base and the standardized space to be able to come together so the same way that the biggest enterprise would define and manage the same way that you would be to find your nodes and networks as well. So a couple of things that we can maybe discuss, you know, talk about is that medical thought provision so we support again, medical clouds you can in a matter of few clicks, have your network in just a bunch of minutes or otherwise you know it will take in to a month or two. And then again you would be worried about the security still because you really don't know how your network which you created from scratch would behave. You would have unified dashboards and the security is something that you build it once and it is automated and present for everybody for the platform so that's what we provide as a speciality that you can make benefit from. Blockchain integration so you can integrate, use it for different tools, different services and you know it provides bunch of services like T as well, decentralized storage. So it's got a bunch of things provided together and what we like to call ourselves is like we're trying to be the AWS of Web 3.0 and hopefully are able to deliver all those promises. So resource monitoring, auto scaling, healing, unified dashboards again for all of this bunch of stuff where you can see your alerts, you've got a network visualizer, you've got CSCD pipelines for you for your blockchain networks. And again, a bunch of stuff that you can always expose more and more for. So Z for happiness fabric is such that we've got a bunch of features we've been working on for quite a while. And while you can start from the time creating yet scaling and onboarding people to your network, you can use it for doing a lot of monitoring as well they can check the system and metrics as well as optional metrics that will come about to in this demonstration itself. You can do a lot of node management you can add, stop, start, restart, all kind of node based operation is something that you can do from our UI panel itself. You're smart contract so smart contract management is very specific, there's specific way every doctor protocol provides that you should be able to deploy your chain codes or smart contracts to and we try to standardize that methodology to all our customers using our own tools that we provide, which again will be showcasing you. We've got CLA operations for integration with tools so it doesn't matter you use Jenkins or Gitlabs or GitHub actions or you use Terraform or Ansible for setting up your infrastructure side of things. Our CLA tools can really integrate and fit really well with your tools that you're using directly in order to allow you to automate your deployments as such. We've got alerts and logins which are present for our customers so if you're having any issues, let's say your node is not syncing or it is not connected with other nodes, they're able to give you alerts so your node is not behaving that way. It should be also sure if any RPC connection is having issues it's getting broken down again and again we send all of those kind of alerts as much as possible. Fully fixable fabric technology so ultimately it's you who should decide how you should fit in, who should hold the order of nodes, CA nodes, all those kind of stuff, and giving much some flexibility is busy sits beside everybody else in all of this. And of course, you know, being part of a platform you can use our services for 24 seven support from our DevOps experts. So, just a little bit of explanation how a lot of our customers are a lot of enterprises you see today is that they've got their traditional tools. They're, you know, mythology still intact of Jenkins or a terraform, but they are able to integrate CLA as a platform within those tools itself in order to make all of this happen whether it's setting up the environment from the very beginning. Or it's, there's CSC debates where you are constantly creating your smart contracts, your application will be able to deploy them as you go along for your projects. So Ziva select tools that you can utilize with your repos you can integrate them you can deploy your chain quotes in just matter of few actions, and all the signatures that are required will be able to pick up from there we will do so. And we will deploy your chain quotes perfectly within your notes. And if there's an issue, let's say your chain quotes are running too many. And your cluster is currently having a lot of issues with scaling with the performance because of their too many containers and be able to give those insights as well in terms of alerts that needs to you or email or in applications and such. So this is what we are and of course, you know, we've been very lucky very fortunate to be able to have so many interesting customers many people in the community looking to a platform giving us a lot of feedback. And hopefully that is what we'll be able to get from you guys in the coming time to help us grow even. So I think we'll switch over to the demonstration now. My colleague here Lakshay will bring up his screen and I think we can show you some cool bits. So you can get a good idea of what we've been working on. Over to you Lakshay. Hi guys. Welcome to the webinar. Let me share my screen and then then we can start with the platform demonstration. So I've already logged into my Ziv account. You can obviously check it out at zip.io. There are a bunch of protocols that we support as of now. There are options to sign in and if you're a new user, you can sign up with much of your social handles using Google account or GitHub account. Or if you want to create your account with just your email, you can do that. So if you log into your Ziv account, there are a bunch of components that you see when you go to the dashboard. You can add your multi subscription details, your cloud usage distribution to understand what are your cloud consumptions as of now with your different blockchain workloads and services. And then there are components that you're using inside Ziv, which includes networks, nodes and the endpoints that you're consuming. And then we have protocolized distribution of your networks and blockchain services and then some system health sites that help you understand your Ziv account usage. Now, before you start creating network on Ziv, there are two ways that you would want to create a network. So let's take a look over this on how to authorize a cloud account or how to, you know, the step one that you should take when you're going to create a network with Ziv. So Ziv supports two approaches when you're creating a network, which is BYOC, which we call which is bring your own cloud and then Ziv supports managed Ziv deployments in which you don't have to worry about cloud account or cloud deployments. You just have to get the subscription from Ziv and Ziv will create the interest services for you. So for an enterprise network, you would want the services running inside your own cloud services. So for that, you would want to come to my cloud section settings and then authorize your own cloud account. So let's say you want to authorize your AWS account, you would select my cloud and then you would select AWS from here, and then you would select add AWS button. Now this form is going to ask you a few details on the label of this credential that you want, and then access key and secret key that you can generate from your IM section of AWS. So when you're generating these keys, you can also limit this user with a bunch of permissions according to the network requirement that you're going to create. And then we have this extra credential label which helps you identify your credential that you're creating with Ziv. Now with this feature, you have the capability of creating heterogeneous cloud networks where you can deploy a bunch of workloads in one cloud and then you can create a bunch of other workloads in different cloud account. For example, let's say part of your network is deployed in AWS and then part of your network is also deployed in DigitalOcean so that it helps you migrate the services and helps you cut down the cost, gets the benefit out of both and everything. Same goes for DigitalOcean. If you want to add your DigitalOcean account with Ziv, you can select DigitalOcean and then you can select add DigitalOcean cloud button and then it is going to ask you for API key which you can generate from DigitalOcean settings button. And then you can also provide permissions there which is read and write permission for Ziv to get started with your network creations. Now after you have authorized your cloud account, you would want to get started with your Ziv network. Now for that, we can come to dedicated node section and your dedicated node section would be different than mine. I already have two networks deployed here, one Ethereum and one Hyperledge Fabric network. So in your account, which is obviously without a network, you would see just an add network button there. Once you click this, it is going to ask you to buy a subscription or if you've already bought a subscription from Ziv, you're going to see the list of subscriptions from the subscription that you've bought. Now, let's say you want to create a Fabric network with DigitalOcean subscription, you would want to select BYOC DigitalOcean. Now in my account, I have both a subscription even for AWS and DigitalOcean both. Now you're on to Fabric network creation page. The entire Fabric network creation page has been divided into four steps. The first three steps are all blockchain steps that you have to decide. And then the last step is about cloud configuration that you want your network to be created with. The first step is going to ask you to decide the Fabric version that you want to go with. So we support two LTS versions. One is 2.2 and then one is 1.4. Other one is 1.4. So with 1.4, you have choice of consensus between Raft, Solar and Kafka. And with 2.2, we only have Raft supported since other consensus type have been deprecated in this version. So let's say you want to go with this latest LTS version, which is 2.2. You select Raft as your consensus type as you click next. Now in this step, you have the capability to decide your organization level details in which you will click add organization button. And it is going to ask you to decide your organization configuration. So first thing that you want to do is name this organization. So let's say I want to name it organization one. And then I have to decide my CA admins username and password. So I'm going to put down watch even admin here. The same I can put down for password as well. You will want to secure your passwords with different password policies that your company or your individual comply with. And then you have persistent volume checks, which allows your CA services or any blockchain service that you're going to create in this section. Be spawned with a persistent volume, which helps you take a backup of the service. Also, if you want to shut down the service for a while, you can do that. And when you create the service once again in your cluster, this is going to be created with the point where you stopped it. So you can put down volume size and everything according to your own requirements. If you don't want to bear an extra cost, you can uncheck this button. Every volume creation is going to be creating an additional cloud volume inside your cloud account. And then we have order services that you would want to create in your organization. So let's say I want to create just one organization network. I would want at least three orders inside my network. So I can do so with the add order button. And then I would want to add peer into my network. If I go down below, I'll see that there's one default peer already. Now with Ziv, you have choice of database for your peers to start with. Default choice of database would be level DB. And if you have complex queries in your smart contracts, you would want to create your peer service with CouchDB. Now with CouchDB, again, you have this check for persistent volumes, which creates your CouchDB service with an additional cloud volume. And then you can also specify the size for it. But if you want to go with low, go with level DB, you can just scale up your peer volumes. And that helps you, again, take backups of your peer services and maybe stop it if you're not using it in your network. And at the end section, we have CSR Details, which is Certificate Sign-in Request, which helps you create your certificates of organizations with the details that you provide here. So this is an optional step. If you want to fill these details out, you can definitely do so. Otherwise, if you're just creating a staging network, a test environment or a dev network, you would want to skip this step to fast pace your development process. At the end, you would want to click Next. And after this, we have Challenge Details. So we have selected the version, we have selected the organization settings, and now we're on to our last blockchain step, which is deciding upon my system channel details, which are my global blockchain configuration. And then I have this provision of creating an application channel as well. So with this check, you're going to bootstrap your network with an application channel and all of your blockchain services and workloads are going to be started within a default channel, a bootstrap channel to be precise. And every peer that you've created in the organization section is going to join this peer, sorry, channel. So once you click this next step, it is going to ask you for your cloud configuration details at the end. And in here, because I selected my BYOC Digital Lotion Account subscription, it has already picked and selected Digital Lotion for me. Now, my last step is to name my network. So let's say I want to just name it DevNetwork or anything that I want to. I can do so. So I want to create a Hyperledge Fabric DevNetwork here. And then there is choice of workspace that you have. So workspaces are logical entities that Zeev helps you encapsulate your network in. So you would want to divide your networks according to your departments or maybe environments that your company or your individual department is handling with. So you can divide your workspaces maybe in staging environments or production environment or pre-prod environment with these workspaces section. So for me, I've only decided the workspace in between the choice of protocols that I go with. So for me, public nodes are there and then there are a bunch of permission protocols. For this network, I want to go with Fabric Networks. And then I have to decide what cloud account I want to go with. So I only have Zeev demonstration credential attached to my DigitalOcean account. So I can select it here. And then I have to decide the region that I want to deploy this network in. So all of these regions are supported by DigitalOcean. So I want to deploy it in NYC1 region. And then I have to decide the number of worker nodes that this Kubernetes cluster and I'm going to create with this network how many number of instances I want to go with. So let's say I want to go with three number of worker nodes and then I want to decide the instance details which is the type of worker nodes that I want my network to be started with. So let's say I want to start with 2VCPU and 4GB of RAM. I can do so with this checkbox here and this dropdown here. So I've selected all of my details. Let's click create. When I do this, it is going to check if my cloud account has enough formations and enough code available to start with the network. So yeah, I did. And my network has successfully initiated. Now it is going to take a while to spin up my cloud services and create my gate cluster inside my DigitalOcean account. So that is why you're seeing all the data I can share. So it says that all of the services that I've installed it is now because it is not seeing the live status for them. Now if I check my notification sections, yeah, so I have one infrastructure in provisioning. It is going to take at least 15 to 20 minutes to get provisioned, 10 minutes to start the to create the infra and then a few minutes to provision our blockchain services onto this infra. Now to save us some time, I have one already deployed network here which we can see which is demo fabric network. Now if I go inside this network, I have a bunch of options available for me. I have a graphical view representation of my organization that I've deployed inside this network and I have a bunch of services that belongs to this organization and are ultimately owned by me. So when you create these services inside your networks, you get to take the full ownership of these services, which includes deleting these services from your network or restarting or stopping these services if you want to save some clouds of cost. So in this list, you'll see the cloud account that this service was deployed with, the type of organization that this service was deployed with, the type of service that it is and the region the service was deployed inside. So this network was deployed inside US West 2 region of AWS and then we have a deletion option here and then restart and stop, but to stop these services from my network. And after you have deployed your network, the next thing that you would want to do with is connect your application SDK with your blockchain network and for this we have artifact section here which helps you download these crypto artifacts which contains enough crypto material to connect your application SDK with this and then you need a connection profile. If you're working on Node.js SDK for Hyperledger Fabric, it requires a connection profile to communicate with your peer services and order services. So to save some development time there, we have this option here already which creates automatic connection profiles for your organization. So if I open this attachment, I should see the connection profile here. So I have two connection profiles for ROG1 and ROG2 which are part of my network. So if I open this up, it is going to show me the entire JSON object. So yeah, it is there. It has intendition and then you have everything there. You can just plug it in your application SDK and then you can start interacting with your network. Now this covers up your application interaction, but as a network admin, you would want to control your network and you would want to see how your services have been deployed and you would want to take ownership of your network in terms of cluster and its services. For that, you can download crypto artifacts and once you download crypto artifacts, you will see it has your Kubernetes authorization as well, which helps you see all the workloads that have been deployed and also these services are running there. So if I extract this, I should be able to see the things inside it and we extract it and then we can go to our terminal and we'll see the services that have been deployed inside. We'll come back to this section in just some minute and then we have a bunch of actions with our networks. So you can add organizations with the fabric networks. You can add more pairs into your organizations. You can create more channels and ultimately you can see the blotching details that this network is deployed in. So let's see how easy it is with Zeef to create an organization into your blockchain network. So add organization is divided into a few steps. First thing that you want to select is or decide is the name of the organization that you want to add into your network. So let's say I want to name my organization ORG3 and then the application channel that you want to deploy this or create this organization into. So let's say I want to create this organization into my bootstrap channel, which was my channel and then I want to decide the admin user name and password for my CA that is going to be created inside my organization. So let's say I want to again go with the same password policy with the ORG3 admin and then the same password as well and then these same options for persistent volumes there if you want to check these buttons it will create your persistent volumes for these services. And then I can add more pairs into my organization and again the choice of databases that you would want to go with your peer services. So let's say I want to go with default level DB settings here and I can also decide my CSR details just like before. And then there's this last step which is going to ask you to if you want this creating organization to be added into the network consortium. So it allows you to add order with this organization which is going to be spinning up with an order service. And then we have configuration which allows this organization settings and reader and writer and admin policies as well as endorsement policies. So let's say if I want to add an order I can do so and I can decide my reader, writer and endorsement configurations. So for this we can select what type of entities should be a reader for this organization. So let's say I want any member to be the reader and let's say I want to go with the same choice for writer settings as well. And then for admin we only support admin configuration and then for endorsement you have peer only to be endorsing this chain code or anything that happens inside this organization. Once I click create it is going to do a bunch of crypto signing for my proposal that I've just created for my third organization and it is going to spin up the organization blockchain services and notes inside my cluster. So it is going to take a few minutes meanwhile we can see how you can create an application channel into your network. So if I click create then there is create channel form which is again divided into few steps. Our first step is to decide the organization configuration for my application channel and then second step is to decide the organization permissions for this channel. And the last step is to decide the number of peers that you would want to make join this channel. Let's say I want to add a channel with NFT channel here. So for this you can decide the organizations that you want it to be part of let's say I want ORG1 and ORG2 to be part of this application channel. Then I can decide the individual configurations for these organizations. So let's say I want to go with the same approach here as well. We can decide admin policies and then I can also decide the endorsement policies for my organization for this channel and the same goes for second organization as well. Right. So after deciding all of my policies you would want to go to next step. And at this point I want to decide my application configuration policies and channel configuration policies. So you can decide the proposal that it should accept from. So let's say I want it to be either from organization one or organization two and then I want it to be same for writer policies as well for admins let's say I want to go with majority admins. Same I can do for life cycle endorsement as well. So these are the combinations that Zeep creates for you when you are creating an application channel. And then in channel configuration you can also decide which policy you would want to go with. Say I want to go with any reader and then I want to go with any writer and same for admin settings as well. And next step it is going to ask me to choose my peer services that I want this channel to be part of. So let's say I want my every peer to be part of this channel in NoRG1 and NoRG2 both I can do. So click create and it is going to add NFP channel to my network. Right. That's amazing feature because otherwise you know your major focus is to make the organization participate in your network and you really overlook what kind of permissions are they going to be using being part of the consortium. So Zeep allows you to do it in a couple of minutes and keeps your focus on what kind of permissions are you actually granting each and every organization to your network. So yeah. That's it. Yep. Thank you. Right. So I think let's go to a terminal and see the blockchain workloads that have been deployed in this network. Let me copy my artifacts from the artifact that we downloaded. Let me copy the artifacts from my local repository actually I can't see my screen now. It's occupied by Zooms from there I want to download my artifacts from my download directory and do so. There I have it. We have artifacts with us. If I want to select keep contract file here and do so with this and if I want to check the workloads that have been deployed I can do so. All right. Yeah. So we see the blockchain workloads that have been deployed so far. So I can see there are workloads for organization one and workloads for organization two. So some of the workloads for second organization have been deployed with CouchDB for one of the peers and with blockchain three I have just one pair running with leveldb there and it is also going to deploy some of our addresses well inside my blockchain or g3 namespace. Now if I want to check the logs of it with the same kubectl command and it gives you full ownership of your networks it gives you the add-in privileges and let's say if you want to remove some services from your networks you can do that without going to go to the ZIF panel again and again. So it just requires some knowledge of Kubernetes to be working with these networks. Right. And yeah just a pointer here so we've got a couple of services that can help you get used to analytics about what has been deployed and how's it doing. So we've got ZVGint which allows you to get a lot of insights of your network that I think you'll be checking out really quick on where dashboards are at analytics stream. Yeah sure. I think we can go to analytics then and then we can go to pipelines to see the ZIFs automated CICD pipelines for chain code and smart contracts that supports the entire chain code lifecycle. So like Sankal explained that you get a bunch of analytics for your networks which includes blockchain-level analytics and your resource-level analytics for your blockchain networks. And here I'm going to see the basic health utilization which includes memory and CPU that is consumed by my network as of now. I can also see drill down reports of working node-wise that have been deployed in here. Same I can do with the namespaces that have been deployed. I can drill down to particular namespaces and particular parts to see the exact details that are being consumed by my powered application. Yeah so the list so the details goes on. You get to see network utilization, memory utilization, disk utilization and then you can also put down alerts for the same utilizations in your cluster which helps you to keep your network healthy and running and helps you with the uptime of your blockchain services. Now we can also see the blockchain-level analytics for my peers and other services as well. So we captured these details and we're able to give you alerts on the support system as well as your blockchain metrics. So let's say if your node is not getting any artist's permission or it's not possible with other blockchain nodes then we are able to easily provide you the details and show you all of those analytics as well. You can drill down to any specific timeline in this whole duration and it gives you a lot of information of how to maybe you're taking too much resource or you're underutilizing your cluster so it will provide you all of that information as well. Right. So this is the new peer that I just deployed. Let's say if I select one of the peer that I've already deployed I should see some different level of details. I can see the chain codes that have been deployed in this peer and same goes on for other services as well. So I can see that there is once CLI go one chain code that has been deployed there have been some comments on to my blockchain ledger blocks and same goes for other services as well. I can select it here. So after this analytics you would want to deploy your chain code onto your blockchain networks. For that we can come back to our pipelines and configurations that are required to run these pipelines. So let's check out the pipelines section first and then we can go to the required authorization that should be there when you're running the pipelines with the CLI. So when you click pipelines you get to see the list of pipelines that have been run on your application. If you don't have any pipelines running you will see an empty list here. So I had to run few pipelines in this particular network and if I click on one particular pipeline I can see the jobs that have been running inside it. If I click on the particular job I get to see the logs that this job produced. So this was a job which committed my chain code onto my network. So I can see that this was committed with a particular transaction ID and I can see the valid commit status in my commit job. Now before you start working with chain code pipelines there is an authorization process which you have to perform in settings section. So other than interacting as a web application or a web platform you can also interact with your ZEV networks using ZEV CLI as a CLI tool. Now in order to do that you need an authorization which you can generate with the APA credentials in your settings section. So when you click on APA credentials in your settings section there is a create key button which is going to open a form for you if you click it and then you can provide a name to this API key. So let's say for my network it is a HLF network key and then I can decide the type of service that I want this key to be created for and say I want to create a key for my networks then I can select the network that I want to create this key for so let's say I want to create this key for my new network that I just deployed then I can also decide my permission that I want this key to have. So let's say I just want this key to run pipelines and only view pipelines I can do so and then I can create key here and there we have it we have our access key and secret key I can copy it and I can save it somewhere where I can make use of it when I'm running the pipelines. So after you've done this you would want to go back to your networks page there we go and you would want to go back to the pipeline section and from here you'll see that there are no pipelines and then you can go to your CLI terminal again and there you can install Zeef CLI using NPM package manager so it says simple command you can do NPMI Zeef and then you can install it globally with this it is going to install Zeef globally onto your machine and from this point onwards you can start using Zeef CLI and if I go to Zeef CLI's help section I can see the operation that it supports for fabric chain codes right so we support entire chain code life cycle which includes packaging of chain code, installation of chain code chain code approval, deployment of chain code and at final stage we allow you to commit your chain code so now let's say if I want to run a pipeline I can do so I think we can run this pipeline or we should be able to run this pipeline onto a new network that we just deployed that we check if our network is ready and if not then we can run this in our existing networks should be able to right so our network is ready so BI nearly took I think 10 to 15 minutes to get this network ready up and running now if I go to my pipeline section I can see that there is no data because there is no pipeline here and if I go back to my detail section I can see the data so from here I would want to get my network ID to tell my Zeef CLI tool which network it should target now I have one script ready which helps me run pipelines for my network so let's go inside it right so if you have it I have my access key configured here a bunch of operations that I generally do when I am running a network when I am running pipelines on my network so in network ID section I want to paste my network ID here now I have peer URLs so for that I can get it from I can get it from my network view section here I can copy this service URL and then I can paste it in here I should be able to run my pipelines then right so we have it all let's run it now it is going to package my chain code which I already have in my local territory it's a simple chain code it's a marble chain code which has been modified to run as an external service so I go to my Zeef account I will see there is one pipeline so there is one pipeline which is running so the yellow status tells us that this pipeline is running then we go inside it I can see the job and in here I can see that it is building my chain code it is packaging it and at the end it is going to push it into my digital ocean registry container registry and from there it is going to deploy it onto my cluster same steps same goes for here as well if I want to download the artifacts I can see the deployed workloads here we can see the cluster that has been created from Zeef right so with that I think we can conclude our demonstration presentation and I think we can open up the Q&A section or Q&A round right Sankar over to you yeah I have been answering all these questions on the chat actually there have been quite a few interesting people putting all kind of curiosity in places it's good to see so right now I don't think we have any open questions but just to maybe go over them I think we just found one now so how the dev team can test the network locally so yeah I mean you can go ahead and create your applications for whatever purpose and you don't really have to spawn a network set it up locally instead you can just come here deploy the network in a couple of minutes the topology that you want the number of orders belong to different organizations and such and you can just use the connection profiles use the artifacts that Lakshya has on right now on the screen and you can connect to the nodes directly and you can deploy your chain codes with the same actions and you can do all kind of transitions if you want to deploy a chain code you can do it as easily as well as Lakshya showed right now and the Azure application will usually do using the SDK of IPv4 we had a second one as well is cloud migration possible so we have done it for a bunch of our customers previously because they have running a lot of times for their projects and we can help you out with all of that so it's creating new certificates for your new domains or whether it's to migrate the whole data from one cloud to another use the platform we can help you out with all of that the step procedure is of course manual it's not just a few clicks like this but hopefully one day we'll have the automated there as well but yeah cloud migration is definitely possible we've done it a couple of times how about certificates backup so yes every certificate is packed up into your own cloud deployments as EBS volumes so we have constant short for what we're doing attached to your modes and there is proper backup for your data as well as your certificates as well so a couple of questions I think we caught earlier on maybe I just put them out where we have still have a couple of minutes we were asked if I was a Fabulous Fabulous by a good doctor continuous with Kubernetes it's Kubernetes clusters that we go towards because that's a production development that most enterprises look towards and usually you start yes manage Kubernetes cluster which are cloud you're choosing it's usually but you also have bare metal clusters for on-premise deployments that we have capability to do so in some of the deployment strategies I was actually so persistent volumes so persistent volumes are just for persistence of your data a lot of times when you do development or testing you don't really require so much data to be persistent because it can cost you on your cloud side to save you on this cost such an option to take it off when you don't need it can we use the same code for multiple on-premise server deployments so yes you can but on-premise deployments can be quite specific so they can be a bunch of stuff customizations that you may require to do so but a lot of enterprises use it as that where they need to have an on-premise on this service I think we've caught maybe a couple of questions any explorer for blockchain data so not really we have gotten this question quite a few times you can deploy deploy your own explorers to blockchain cluster that you have right now but we ask it as if to not provide it as such you can look at a lot of analytics of chain codes and number of peers each and every node is connected to our connections which are specific to blockchain but explorer which can you can see all the transitions so that's not something that Zee provides here Zee doesn't look into your blockchain data in such either so we don't have it but you can always deploy it by itself using the same connection profiles and details what about private data collection does it support as a feature in Faber to Linux yes so this is something that we are trying to provide it over we should do it manually for the time being but we can we experts can help you out if you're struggling with any of private data collection setup but that's something for a December release that we've been preserving and hopefully we'll be able to roll it out pretty soon so look into that and I'll look for that I think it will be quite an interesting feature to have from Zee's platform in the demo it looked like there's highly automated and distortion deployment automation in particular is this similar automation for other public protocols like GCP or so yes so we've been working on GCP and we've already had early access to some of our customers and we are waiting for December to come by in December release we can expect GCP and other bunch of family features like sharing your consortium around different cloud accounts users who can log in as well and then you can use it like that so that's something that is coming in as well that's going to be a big release and we're looking very much forward to it it's going to have a bunch of stuff that we've been gathering for you guys a couple of comments here really appreciated thank you very much and yeah I think that's it Tamaz I think over to you sorry if I took all those questions I started answering myself so I think we have five minutes left so if anybody would like to speak up let me know I can unmute you otherwise I think you covered everything thank you so much and thank you Laxia as well I think you covered a great presentation as you can see in the comments as well and you managed to cover really a lot so let us wrap this up and you know if you have any other questions please feel free to reach out to us at Hyperledger or the Zeeve team directly as well and we'll be happy to assist you and connect you to the Zeeve team as well now to wrap it up I would like to invite you to join our Hyperledger discord we have quite an active discord community it's related to projects our special interest groups our working groups we have a group of developers I think we lost your voice at the mass we can't hear you we can't hear you we just try to do with your earphones or something yeah I think there was some there is it any better yes well we're about to wrap this up thank you for pointing it out we have a meet-up London coming out where the demonstration of formally verified chain code generation for Hyperledger fabric will be presented now and this wraps it up so thank you everybody for watching and thank you again Stan Kalpenlaksha for this great presentation and very useful information so feel free to reach out to us and to the Zeeve team whenever you have any questions or comments thank you very much and hope to see you again soon thank you thank you bye