Welcome to NewsClick, we have with us Comrade Krishna Prasad, Finance Secretary of the All India Kisan Sabha. He is going to talk to us about the agrarian crisis facing the country currently in the context of Narendra Modi inviting a cooperative farming into the country at recently in the World Food India Conference held in Delhi. Welcome to NewsClick, Comrade. Comrade, if you see that in India there are farmers are in a crisis and there are also protests that are happening in the context of, you know, on a large scale you see demonetisation has affected them, there is input cause that have risen and there are suicides that have been increasing. What do you think is the crisis affecting our country? Actually Narendra Modi is not requesting cooperative farming. It is the corporate, actually it is contract farming. So it is a policy announcement by the NDA government in the last budget, 2017-18. They said a model contract farm law will be introduced in all states and the first budget of this government in 2015-16 they announced 100% foreign direct investment in agriculture and retail. And they are now concentrating on food processing. So what they are thinking is that on food processing they would be able to bring a large change, a sea change by the intervention of the foreign direct investment and the contract farming with the presentry which is untrue. Never in India or wherever in there you can see this contract farm is going to help the petty producer. In India around 85-87% of the farmers are marginal or small. So that means because contract farming also the capitalist would need large land holdings and if this model has to become a viability that means all these farmers have to be, I mean have to leave agriculture is it not? No actually what is happening today is every day 2085 farmers are quitting agriculture because agriculture has become economically unviable under the capitalist especially the under the neoliberal regime. And you see in 1991 the percentage of the land less was 24% age. Now it has gone up to 44% age. So almost it is doubled within two decades of the neoliberal policies implementation and another aspect is the properization. So land scale properization, indebtedness, the suicide and the migration from rural to urban. And one thing which we can notice now is that earlier the demand for higher price 50% above, minority price 50% above cost of production which was a recommendation of MS Aminathan commission. So this was made or demanded by sections from certain regions. Now across the country, across the region, across the crops, from everywhere it has become a unanimous demand and also freedom from indebtedness. So these two demands are coming up from everywhere whether it is from Chattisgarh, Maharashtra, Rajasthan, Kerala, Tamil Nadu or Bengal and Asam. Why it is happening so? Because of the intensification of capitalist exploitation. Capitalism is advancing towards agriculture and agriculture is accused due to this exploitation and the growing expenditure for cost of cultivation and also cost of life. The root cause of it is the lack of land reform. So now also we can see around 5% of the landholders of the upper what to say size they are holding 58% of the cultivatable land. So this inequality that is growing in such a situation the petty producers are unable to sustain in agriculture and they are become more and more proliferates or workers. They are losing cattle, they are losing land, they are losing everything and they are forced to migrate as a migrant work. The proliferation of the peasantry. This is what the communist manifesto Marx and Engels very clearly was indicating under the capitalism what is going to happen and Leninus very correctly stated this that petty production cannot sustain under capitalism and they will lose everything. So this is the stage today all over the country and this shows the entire economy needs a system change. Without a systemic change you cannot move. So this change is needed not only by the farmer or the peasant but also by the capitalist class. That way they are trying to bring a new system of a contract farming and 100% FDI and they feel it will be a solution for the problem but unfortunately it cannot be and it will not be. Narendra Modi and his team who are leading the government is totally on a wrong path. What do you think could be an alternative so that this section of farmers for them farming can be a viable option? You see the studies welled over shows what is the crisis in agriculture today. You can consider that now under capitalism a modern industrial society is emerging and agro processing industries are an important role to play in that. And through the agro processing and marketing only the agriculture can be modernized and in such a situation what is happening today in India is the Indian capitalism is failing in undertaking this responsibility. They are more and more in lucrative areas of real estate, hotel business, tourism. So they are not entering into the agriculture at all. What they feel is that let the foreign capital come into it with a 100% FDI this is what they are saying. But on the other hand the studies all over the world shows out of the total value of the consumer products made out of the raw agricultural producers only 10% of that value goes to the primary producer. That means the farmer and also agriculture worker. So where does this 90% of the remaining surplus goes that goes to the industrial processor, that goes to the market here, the middlemen, the transporters and also the advertisers media. So all these are sharing this amount. This is what is happening. Why it is so? Because the monopoly capital is having a domination of the agro processing industry and also market. So without entering into this area, this field, the farmers cannot pitch to the relationship in production in favor of the farmer. So this is a challenge in front of the farmer today and we should address that. And that is possible not through the contract farming but only through a corporate use farming. So is there an example that you can give so that the viewers and through them everybody is educated. For example, some small example, can you cite of cooperative farming which actually help the farmers which you are aware of. Let us take a new example which we are now doing in Kerala. For example on 29th of this month, last month, October 29th, the finance minister of Kerala, Dr. Thomas Heiser has come to Wynard. So he initiated a project. That project is the industrial poultry farm inauguration of the project by Brahmagiri Development Society which is a cooperative. Two young women agriculturists, cultivators, named Gina and Jeanie, they initiated that first project. The 2000 chicks, their old chicks has been given to them and they paid the money also and they are purchasing feed also from the Brahmagiri. So Brahmagiri is the cooperative which is extending help to facilitate the input supply and they fix that rate. Now after 35 days, they are taking that back with 11 rupees per kilo as an income to the farmer. Out of 2000 beds, they may be able to have an income of around 30,000 rupees per month. If it is in the contract farming under the corporate companies, it can be below 15,000 only, so they can double it. And now the Kerala government want to promote it. So the minister announced there for each and every bed, they will give 5 rupees for subsidy. Brahmagiri is a cooperative which has a policy of not profiteering out of this business. They are only facilitating. What is the surplus created? They will share with the farmer. That way they are able to give 11 rupees instead of 5 rupees or 6 rupees. So this can be a model. Now around 150 farmers have joined the federation. It's a poultry farmers federation. So these sort of federations or crop wise mobilizations, these are the key in giving the petty producer a strength to checkmate the corporate exploitation in the market and develop a cooperative alternative. But then if you want to extend it to a larger scale, the MNCs have the power and the money to advertise and take their produce to different markets. So is that also viable in a cooperative model? It depends. For example in Kerala you can see around 90% of the people consume meat and Kerala is having a very high income level, what's a life standard, so that that market is there with you. You need not to explore any market outside of Kerala as far as meat is concerned. Second thing is that the Kerala, the problem is of production. So petty producers are under economic unviability because of this exploitation so the production is not coming up. So if you can develop it, then the market is assured, then the question of the money. You are saying the money is with the corporates. No, money is with the people. Either people are not purchasing, if their purchasing capacity is not there, then the corporate products also will be under slowdown. The concept needs to be understood by the majority of the working class and the farming class and they should advance to have a change in the system. So in that context we're talking about the workers and the properization of the farmers and if you see now in 2011 census about 144.3 million agriculture labourers were there in 2011. That's a huge population. So what do you think should be the policies even in a cooperative model to also help the workers who are engaged in agriculture? You see India is a largely an agrarian country, agrarian economy and the agriculture has become unviable and the farmers are forced to become a worker and in such a situation the worker and the person alliance, the farmer worker alliance, that is very important. You see there is always a contradiction between the farmer, especially the rich farmer and the agriculture worker because the rich farmer want to reduce the workers wage and the worker always want to have an enhanced wage. So this is the contradiction between them but as far as the petty producers are concerned the middle class of farmers or the poor farmers are concerned they are agriculture workers also. So if they are coming together and they are exploring the possibility of cooperative farming and establish their own market and industry for example that was the resolution of agrarian question in India that is the base of the democratic revolution in India as far as the communist parties are concerned the left political movements are concerned their major area of aim of political intervention is to bring an agrarian revolution. So agrarian revolution is the axis of the democratic revolution so without having an alternative to agrarian revolution you cannot advance your political movement also. In the existing situation Narendra Modi also has come to power with a left leaning slogans. For example he only have given in 300 plus public rallies the slogan that if Vijaypees water to power then they will give 50% above cost of production as remuneration price to each crop. So this is what the left movement is demanding this is what Kishansumma was demanding then Modi has promised it but in the last three and half years rule he never fulfilled that. The same he said the freedom from indebtedness to all the farmers because under neoliberalism under the congress rule under the congress economic policy the farmers are the most exploited they are under indebtedness and the Modi has put a left slogan of freedom from indebtedness but under three and half years rule his finance minister says even a single penny will not be given to pay for a debt relief a loan waiver scheme. So this is the double speaking of the Vijaypees and those farmers who have watered Vijaypees to the power now they have been fired at and they have been killed by the police under the Vijaypees state governments for example Mansu the Vijaypees government did not had any consciousness problem in firing on the innocent farmers who have watered them to the power and this demonetization and also now the GST this is affecting badly the farmer so under such a situation the farming class is forced to come against the government policies that is what we are seeing in Maharashtra continuous struggle and in 13-14 days struggle in Rajasthan which have been forced to the government to succumb to the pressure of the farming community and anonsome land waiver so this is happening in Chattisgarh today happening in Madhya Pradesh today so this is all Vijaypeer rule state and in Maharashtra where Vijaypees under rule they are unable to contain the suicides the rights of suicides of the farmers 42% hike is there under the Vijaypees government there are peasant suicides so all this shows that farmer community the peasantry is ready ready for any sort of fight today so what it shows that all sections of the farmers whether they are under Congress whether Vijaypea or whether left oriented they are now ready to fight this economic policies here a question is there whether the Congress is willing to change the economic policy because this economic policy which Vijaypea government is implementing Congress is want owned by the Congress also and even today Congress is not ready to change it under 20th of November the farmers also are coming in big number in parliament street to fight so the worker and peasant the alliance and the struggle this is the only hope today that can force the Vijaypea and the Congress to change their economic policy and force the RSS and Vijaypea to withdraw and what to say to the national mainstream by upholding the democratic tradition and also secular tradition thank you sir the cooperative farming is the antidote to the farmers facing the crisis presently the alternative is in the farmers coming together forming cooperatives and giving a tough fight thank you for watching news click


OK, hello, everyone. I'm here to talk a little bit about OpenCost, which is an open-source cost monitoring tool for Kubernetes and other cloud-native environments. A little bit about me. I'm Ajay Tripathi. I'm one of the co-founders of StackWatch, one of the original authors of the KubeCost project. And before this, I was working on similar problems as an infrastructure engineer at Firebase, Google, and Yelp. So before we get into monitoring costs on Kubernetes, I just wanted to talk a little bit about Kubernetes if you're not one of the 5 million back-end developers already using it. Kubernetes is container orchestration. And basically what it lets you do is take your applications to production faster, rapidly scale things out with things like auto-scaling, release code to production more frequently with containers, and be portable across multiple environments, whether that's on the edge in data centers or in one of your favorite flavors of cloud providers. But with a lot of this flexibility and power, it comes the inability to operate efficiently. There's a lot of different abstractions people can be using in Kubernetes. And just increased sprawl, right? Because if it's easy to launch a production service, it's easy to launch too many production services. I don't know how many of you guys are using Kubernetes today, but you've probably left a couple of clusters running right now that you're not using. So to help address this problem, we built OpenCost, which is an open source Kubernetes cost monitoring application. There's a community-built specification, as well as a software implementation of it. So who's in this community? Some of the contributors are practitioners like Adobe. Some of them are actual cloud providers like AWS, Google. Some of them are tooling companies like KubeCost, where I am a co-founder, and companies like D2IQ, New Relic, as well, along with consulting companies like Minecraft Curve. OK. Why are people excited about this? Basically, OpenCost gives you the ability to track and monitor container resource costs in real time and let you see how much of a VM that container is actually taking up. There's native support for shared resources, things like load balancers or system applications like your DNS router or things like that. And tagging is supported, but the majority of slicing and dicing you want to do across different dimensions is going to be without tagging. And there's support for AWS, Azure, GCP, and on-prem. Actually, I wanted to add to this list. Today, there is a pull request for scaleway support, which we're all really excited about. And I think that leads into the next question, which is, why are we doing this open source? In addition to getting people to bring their own cloud provider and extend KubeCost to support it, basically, we wanted consensus around a common language for cost calculation. There's a notion of fairness if you're going to actually be charging back individual containers for the price of the system they're running on. We want this to be interoperable. And we want open costs to be kind of a data source for existing open source tooling in the Kubernetes ecosystem. Things like the cluster autoscaler, which can turn down nodes. And the horizontal and vertical pod autoscaler can now become, effectively, you can send cost data to them as the inputs for doing that kind of scaling. So it's important to us that costs basically become a first-class citizen of concepts within Kubernetes. So I'm going to do my best to demo here. I couldn't get my displays to mirror, so we're going to have to do it over the shoulder. Cool. So here's an example of an application that you might be able to build with open cost data. You can see spend over the last week. And that spend can be broken down. The default view here is to break it down by namespace. Namespaces are folders for your applications. And then you can sort of, because the open cost spec goes all the way down to individual container costs, which are the building blocks of Kubernetes applications, you can drill down and sort of see data for all of those. And it's important, like I said, to be able to aggregate by a variety of Kubernetes concepts and the other first-class members of Kubernetes definitions, things like services, controllers, deployments, et cetera. And then sort of on the other side of the coin, we have the backing resources that Kubernetes itself is running on, although these aren't necessarily like first-class Kubernetes concepts. The open cost spec tracks things like nodes, cluster management fees, disks, load balancers, et cetera. Cool. Let's jump back if I can. So I just wanted to talk a little bit about the specification behind open cost, starting with clusters and cluster costs. So essentially, total cluster costs can be broken down into your cluster asset costs, things like nodes, disks, et cetera, and overhead, things like licensing or management fees. The asset costs themselves are broken down into resource allocation costs, things like hourly CPU cost, hourly RAM cost times a number of units that you get charged for regardless of how many you're actually using, and actual usage costs, things like network ingress, egress, cross zone data transfer, things like that, that only depend on the amount purchased. So making that a little bit more concrete, like I was saying, resource allocation costs are things like nodes, CPU RAM, persistent volumes, et cetera. And usage costs are things like network egress, and overhead costs are the management fees. So I think the next question is generally, how do you go from a node cost to speaking the same language that your containers and workloads are speaking, which are requests and usage of CPU, GPU, RAM, and persistent volumes? Here's a very simple sample analysis of how we arrive at those numbers from the total cost of the node supplied by your provider. For example, we'll take something like a T2 medium and a T2 large. In this sample, a T2 medium costs $0.04 an hour, has two CPU 4GB, T2 large is $0.08 an hour, two CPU and 8GB. So we can deduce that the cost of RAM is a cent per gigabyte based on the difference in cost and the difference in actual underlying resource. We do this analysis across a number of different providers to come up with this marginal unit cost of the underlying resource. That's just being a simple sample of how we might do that. So now that we are speaking the same language between resource costs of nodes and workload costs, we can express workload costs as just the sum of all the resources that that workload allocates. And when I say allocates, I really mean it's the maximum of the actual utilization and the requests. The reason that we think it's important to do it this way in Kubernetes is because when you request a set of resources, the scheduler will block out space so that nothing else can run in that space, so you should effectively be charged for it. And when your usage exceeds requests, you're subject to eviction, so you get charged for the full amount that you use. OK, so here's like an example of how we might actually put this in practice. Exact numbers and names have been changed to protect the innocent here. So you can see kind of we go to a team, look at some data. Notice that the Prometheus server costs are pretty high. Then we can kind of go say, hey, what's going on there? Because we know the names that it's running in, we presumably know the team responsible for it or the applications responsible for it. So you can look here and see that the network cost is high relative to the other sorts of workloads running in this sample cluster. Upon kind of like going in and doing some research, we saw a lot of cross zone network traffic. So a solution here might be to, for example, shard the application to only support traffic within its own zone. And yeah. But once we kind of address that, we come back, see the costs are still high. We noticed that there was a big GPU cost in the namespace, dug in a little bit, found that somebody was running a Bitcoin miner, for example. So those are kind of the simple, obvious places of, hey, this thing isn't doing what I expected it to do. It's a very simple monitoring problem. Once we get through that kind of first order of optimizations, we want to be looking at things like efficiency. The notion of efficiency for workloads in Kubernetes is relatively simple, although there's a few wrinkles. It's simply the amount used over the amount requested. Oh, that's a typo. Should say resources requested. There's a few wrinkles here. Namely, that CPU is compressible, for example. So you can actually, you'll get throttled, but you can go well over your requests and be over 100% efficient. I think exactly how to address those kinds of over-provisioning or under-provisioning, I guess, is beyond the scope of the open cost talk today. But happy to talk more after. Once you've sort of got workloads right-sized and running efficiently, the next step is actually turning down their backing resources to save money. So you can think of that as optimizing the cluster costs. So we have a notion of cluster idle cost. That's just the total cost of all the assets in the cluster minus the workload costs. And the efficiency is just the idle over the allocation. So tools like the cluster autoscaler can kind of peg you to a certain workload efficiency. But by supplying them with actual cost data, you can get pegged to a cost efficiency for scaling your cluster up and down. So yeah, just sort of in summary, putting it together. The idea is to monitor your applications, optimize your workloads, optimize the cluster, and then continue to monitor. And that's kind of the baseline of what the open cost project can do for you. Cool. We can take questions. Yeah, we're in the CNCF Sandbox, I believe. Is that someone should confirm that? But CNCF Sandbox is a project. We haven't put any logos on yet. This talk was designed before we were accepted into the CNCF process. All right, another one. I don't know if it's Scaleway itself. There's a PR today submitted by someone for supporting prices, node prices in Scaleway. So there's an interface that you fill out. I think you probably, it depends how complicated the pricing is in that platform. For a simple one, you probably do it in a day. Cool, I know this was a longer talk, but I'm happy to keep answering questions. If you want to talk, yeah, there's one back there. Yeah, so the question was, is it just cost monitoring for Kubernetes or are there plans for other things? I think there's a lot of interesting Kubernetes-adjacent projects or projects built on top of Kubernetes. I'm going to blank on the name for the Fargate, I think is one of them, like AWS Fargate uses Kubernetes-like systems of resources and requests. The ideas are generally extensible to anything where you have an underlying asset cost and a request and a usage. So yeah, it's extensible to other container monitoring frameworks. You could certainly fill out the open cost spec for things like Mezos or other things like that because the ideas are all transferable from within the spec. The specific implementation that I showed on screen is Kubernetes only, but the spec, I think, is generally applicable for containers. Yeah, the question is, is there a process for submitting a proposal to the spec? And yes, it's in the same GitHub repository as the implementation is today. I think, yeah, I think we should get those links added. But if you just go on GitHub and look up open cost, you should probably find it along with the spec. I think that's all the questions unless we've got anything from the stream. OK, yeah, thanks everyone for coming. Thanks for tuning in on the stream.