Welcome back to the Environment, Climate Change and Land Reform Committee's 31st meeting of 2018, before we move to the sixth item in the agenda. Remind everyone to switch off their mobile phones as they may affect the broadcasting system. The sixth item on our agenda today is to consider a proposal by the Scottish Government to consent to the UK Government legislation using the powers under the European Union Withdrawal Act 2018, in relation to the storage of carbon dioxide regulations 2018. We are joined by Stuart Mackay this afternoon, the head of carbon capture utilisation and storage for the Scottish Government. Thank you for coming along to answer our questions. My first question is about the timing of the receipt of this notification to the committee. It was sent on Thursday, 26 November, with the expectation that it will be laid at Westminster a week later on 29 November. The lights and background is as to why I think there has been so little time given to the Parliament to consider this notification. We received the invite today to speak. We received the notification from the UK Government on 6 November, which is outside the 28 day period to begin with. I went through the usual processes. I had to consult the Scottish Government legal department and other policy officials and eventually get it through to the minister. It was very late in getting to you. I suppose that I want to know what discussion the Scottish Government had with Bays on the scope to lay the SI at this date, given that the Parliament would have a very short period of time in which to scrutinise and consider it. Of course. We have conveyed to the UK Government that this is not ideal and that it is challenging. We have sent a holding response to the UK Government and it conveys that message. Do you give any idea as to why this one has been particularly urgent? I think that it is because of the acceleration in this policy at the moment from the UK Government. I did send a note as an update to the committee, which sets out the activity that has happened in the past 12 months in the UK Government. That is a policy error that is accelerating in its development at the moment. The correspondence that we got did not indicate whether the draft SI had actually been shared by the Scottish Government from the UK Government, has it? We have not got the draft SI yet. I will pass on to some questions, given that you have said that. Can I just correct that? We have the draft SI and we have been consulted on that over the past few weeks, but we have not got the final one. You have not got the final one. That is what I meant to say. I apologise. The drafting, as it is, that you have seen thus far? Yes. It appears to be minor in a technical change rather than anything else. Our legal department is satisfied also. Questions from Anagis MacDonald? With regard to the categorisation of the notification, it has been classified as a category A. The notification indicates that the SI would transfer power to the UK Secretary of State. I would be keen to know what are the reasons for classifying the notification as category A rather than category B, given that it creates new powers for the UK Secretary of State. What that addresses is minor changes in a technical nature. Part of the legislation means that the UK Government would have to consult with the European Commission. That is about changing that to the Secretary of State. However, where it affects the Scottish Government is to do with the pipelines. If the pipelines cross the 12 nautical mile limit of the Scottish Government, it has an interaction with Scottish ministers. Because those pipelines will naturally come from onshore, in Scotland in this case, to offshore, crossing the boundary of the 12 nautical miles into the UK continental shelf, they straddle the boundary. In the process of accessing those pipelines and in the termination and decommissioning of those pipelines at the eventual end of life, there will be an interaction with the Scottish Government naturally. That is where those two things meet. However, what it does not affect is the Scottish Government's licensing ability or capability or competence. We also have licensing powers for CCS, but that refers to licensing CCS activities within the 12 nautical miles of the territorial seas of Scotland. It is very much because pipelines go across these boundaries, there will always be this interaction. What kind of interaction is that case of permissions, agreement? It would be consultation and agreement to decommission, for instance, in a certain way, to make sure that the Scottish ministers are content with that, and for access, for maintenance, etc. I appreciate the clarification, but given that there is a complexity, I would have thought that it should have been category B, but here we go. I think that it is just because of the sort of minor changes here in terms of changing the European Commission, consulting them to consulting in the Secretary of State of Scotland for the Secretary of State of the UK Government. It is always CCS because it crosses these boundaries between the 12 nautical mile limit and the UK continental shelf. It has always been a mixture of both Governments agreeing. I am not understanding your answers to Angus MacDonald just for the record, because you may already have answered some of those questions. What impact does the proposed statutory instrument have on devolved areas, and what are the practical implications? It does not really have any impact, to be honest. As I said, those pipelines are always by agreement because they cross the both boundaries. Both Governments are required in order to consent, to gain access and to terminate and decommission. Depending on which part of the sea that your activity takes place. As I said, it does not affect the Scottish ministers' competencies in licensing CCS within their jurisdiction. Right. Quite specifically, does the function of legislating to amend certain technical requirements in areas where the oil and gas authority is the licensing authority impact in any way on devolved areas, in addition to what you have already said? We do not believe so. There is reference within the legislation to updating technical innovations and other matters with that technology. The reference is that you would look to the European Commission to gain those updates and adopt them into your legislation. That part has changed because of that. That would be to the UK Government and the Scottish Government to update wherever that is relevant in technical terms. For the record, does the Scottish Government anticipate having a role in the exercise of this power, for example? Does it expect to be consulted on changes to UK technical requirements currently set out in the CCS directive? The answer to that is yes. The answer to that is yes. We have consulted with the UK Government on this throughout the years. Is it the intention of the Scottish ministers to have an equivalent power to modify technical requirements within the territorial sea adjacent to Scotland? If so, how does the Scottish Government anticipate that those powers will interact in practice? It is our intention to address the same technical issues. It is not a priority. We have other things that need to be done quicker than that. There are no live projects with CCS-injected CO2 into the geological formations, expected for a couple of years at best, so we feel that we have time to address that. The notification states that this addresses minor EU exit-related amendments and non-EU exit-related cross-referencing errors. What are those, in plain speak? CCS, by its nature, is affected by a number of things. One of them is the ETS, which I think the committee has discussed. A CCS project would need an ETS permit, for instance, if there was a live project happening. The interaction between the ETS and what happens with the ETS connects CCS in that way. Is that helpful? That is the purpose of those additional amendments and cross-referencing errors. The cross-referencing, yes. Again, some of the cross-referencing is to take out the European Commission and put in place the UK Government's Secretary of State for this particular SI. That leads me neatly on to just asking a couple more questions about CCS and the relationship with the EU ETS and what replaces that. How will the current incentives on carbon storage sites to avoid carbon leakage be replaced in the UK?  What is your understanding of how that will work? That is not my exact area, but in order to try and help, whatever replaces the ETS, a CCS project will be part of that and will need a permit from whatever is decided, like many large industrial projects. There is still uncertainty around the proposed mechanism and what the impact of that may be in capturing emissions and reducing emissions? Yes, there is. From my point of view, I am looking at CCS. The CCS project needs a permit for ETS. If ETS is replaced by something else, whatever that may be, that will stay the same. The CCS projects will still… There is no intention to change that at all. So the intention and the effect will be the same then? Yes, whatever that solution is, we will address the CCS. There is no intention to change that at all. I hope that that is helpful. Is CCS leaky? Would you expect projects to be using ETS or some other mechanism? I do not want to use the word backstab. It needs to be there in place, but the Schleipner project from Norway has been storing CO2 for 20 years in the North Sea without incident. Our geologists tell us that that is a safe thing to do. The way that you would choose a store would have to be characterised in such a way that the geology is suitable. There is an awful lot of hurdles to get through before you can say that a site is suitable for that sort of activity. The notification relates to the proposed SI and states that it does not amend the Scottish equivalent to the licensing regulations, the storage of carbon dioxide, Scotland regulations 2011. The regulations relate to the licensing of geological storage within the Scottish territorial waters and are expected to be amended in due course. I know that you have said that there is nothing coming forward for the next few years, but are there any implications in not amending the relevant Scottish licensing concurrently to ensure cohesive licensing? It is a matter of priority. We have chosen to prioritise other things at the moment. However, that is definitely on the list of things to do. It needs to happen, definitely. Any idea when? I do not have any exact date, but in due course it has already begun. There are no implications without it not being concurrent now. We do not have any live projects at the moment storing CO2. We have a number of projects that are starting to be developed, which is very interesting. There are no live projects operational. Any other members have any other questions that they want to ask? Or do you have anything that you want to say in relation to this that you have not covered already? Just to reiterate that it is a minor technical change and that we are addressing the Scottish part of that separately. Thank you very much for joining us. That is very helpful. That concludes the items of the committee's agenda in public session. It is next meeting on 4 December. The committee will hear evidence from the Cabinet Secretary for the Environment, Climate Change and Land Reform and the Cabinet Secretary for the Rural Economy and Connectivity on a number of environmental issues arising from the UK's exit from the European Union. As previously agreed, the committee will now move into private session. I request that the public gallery now be vacated.


wickar y ek y소 Ngu en Rabu  thereafter TV ek ek guink du eklaimed 6 migo nd nha kou from someone jun�로 들어� te surve nd anton b also do my own research How did you feel about this? Why do Africans practiced voodoo? This is what I found. Benin is actually the home of voodoo. And never knew that in Benin voodoo is completely normal. Completely normal? From my search results, I got scared. Because in 2019, I did a video practicing voodoo for the first time, and I lost a thousand people in one hour. Does this mean this time around I'm gonna lose a million mushrooms? ઋચ, �びうわ � == N గతౘల౮ salty కోక్రativity ప్� stick bless when he went to Geneva that just nominate me like the console of Geneva in I�데 programmer those. so as an African who is on a journey to educate African aba their culture and heritage are have to park my things and go checkout this mysterious festival that I had no idea it exists. we are finally in with jamami, this is where the festival gonna take place Today is definitely going to be a good day and this festival takes place every 10 January. It's an annual festival and actually today it's a holiday in Benin. The whole country is going to enjoy the Voodoo Festival. This is the city of Wida, locally known as Glehuwe. One of the foremost cities that have encountered the arrival of the colonizers, especially the Portuguese. So it has become a historic city in the history of Benin. This is the first city that got in contact with the Europeans. So I wonder, the Voodoo community never did anything. I don't know man, just let's go in there and then just go have some fun with the Voodoo culture. Let me, let me, I think I need to answer questions. The festival has not started yet. The main events are the beach. So they are going through town, okay? Performing basic rituals, visiting temples, visiting the deities before they reach the beach, for the grand deba, for the grand gathering. So this is the king himself? Yeah, this is the king of Wida. He's customarily that he goes through town, probably informing the deities that he's going to do something grand for them at the beach. That's incredible man. And you can do the best, walking with their king. But I'm trusting in God. I trust in God of course. But why people don't like to me and telling me to forget my God and to say the religion Jesus is the best? I believe in what we have in our land before they come. The presence of Voodoo in the Caribbean is the testament of the transatlantic slave thread. To the extent that when I came to this festival, I saw so many different people from the Caribbean present to celebrate their ancestors. You came for the festival? For the festival, yeah. It's the fourth time I'm coming already. Whoa! Fourth time, yeah. I'm from Suriname, South America. Why do you have to come every time, man? This is an international festival. Voodoo festival is our heritage.  In Suriname, do you guys practice Voodoo? Yes, also we call it Winty. Winty? I'm learning a new word today. Alright, it's nice to meet you, man. Hi, nice to meet you. You come from Suriname? You came for the festival? No, this is my second time. Second time? Why is this so important to you to be at this festival? Because it is the best festival to promote Voodoo. And Voodoo is the authentic religion of West Africa. My grandparents came from Africa. So in the diaspora, we were looking for the traces from the original African spirituality so that we can reconnect. We are bringing our forefathers, we are bringing their backs. Back home? Yes. That's beautiful. What do you do? My name is Baba Kenneth Feshbaba. In Haiti, which is a country in the Caribbean, apparently Voodoo isn't played an important role during emancipation. Beside the fact that evolution was sparked by a Voodoo ceremony, Voodoo enabled the people to meet together from political and cultural ideals and served as the starting arena for pro-independence speakers to get there. They are messaging across. I was not shocked to see my people representing at the festival. We are happy to be here. We represent the Haitian population. You travel all the way from Haiti to here? We are traveling all the way from New York. From Brooklyn. Okay. From everywhere. Why is this so important to you? Oh my God, that's my culture. We love. That's where we from. Our ancestors are from Wida. So we here for the first time, some of us, to show our respect and appreciation. You're from Haiti, right? In Haiti, you are from Haiti. Oh wow. In Haiti, both Christianity and Voodoo coexist, co-exist, right? Voodoo. And it's exactly the same thing in here. Voodoo. How does it make you feel when you come in here? There's another time about this. We are Voodoo and we are Voodoo. Voodoo. Christianity is Christianity. Voodoo. Let's keep it that way. Okay. Let's keep it that way. We Voodoo. You Voodoo. Voodoo. Haitian Voodoo. Represent Haiti. Look at me. Thank you. Yeah, I come from Grand Rapids in New York to here for Voodoo. On my journeys across Africa, I found myself in Togoville and it was shocking to see that Christianity and Voodooism co-exist in here. Even what is the very important is that in 1985, the Pope John Paul II. So he came here. He came here. And when he came here, there's a lot of people. And he was welcomed by the Voodoo priests who make a ceremony to welcome the Pope here. So the main religion that is here is the Voodoo. And right now they have the Catholic Church also in here. So which means that we have two religions in here. The Voodoo and Catholic. It was shocking to know that it's exactly the same thing that happens in Haiti. And being in Wither for the first time, it was shocking to see exactly the same thing over here. We are just in front of the Temple of Python here in Wither. And behind us you can see the Cathedral, which is a Catholic Church, the Basilica. There is only a space of about 30 meters in between the two worship places. This is the traditional worship of the Python, one of the original deities in this country. So in order to preserve this deity, they have kept the temple for it here in Wither. The Python do not harm. They can go out, go through town, be fed and return to this place. It's a real python. Well, I can only smile at this point. If anyone goes through, you find it, you bring it back to this place. You mean the pythons do not harm people? They do not harm. They are harmless creatures. Are you sure the pythons have been released sometimes? I know they are released into town to go and greet people in their houses and be fed and they return here. It's been here for over 200 centuries. The people have kept this deity for generations. So they are harmless. They are friends like we have other people. Snakes. Even a dead snake cannot get closer. Oh my goodness, look at how brave the lady is. If you want to come to Sudan, come to Sudan. Pythons do not harm people, they do not harm them. And one day on the mob, they open the door. African, you have to come to Sudan. I'm coming. No Sudan. I'm coming. Yes, you must come. So why must the king come in here? Yeah, it's a deity. So the king must pay some respect this morning before going for the grand festival on the beach side. I've been to so many festivals but I've never been to such a big and massive festival like this before. We actually head into the Deba Ground and as you can see, so many cars that are parked. Some are still moving, trying to find a place to park just to witness such a beautiful day. Man! Wow! I can't believe that I never knew that something like this exists in here. Go to the Deba Ground and it was filled with thousands of people from different parts of the world to witness such a colourful rituals and energetic performance of the Voodoo worshipers. Festival commemorates victims of slave trade between the 16th and the 19th century. It was a way of resisting slavery. Our brothers, sisters and parents were gone to the other side of the Atlantic. We didn't know where or when they could come back. So it was said that rituals needed to be performed so that they could come back. So this has been going on for decades to say that what is bad must not be repeated. It's a source of research for the Venet.  They came to build this centine benivua in reality. So the government is also working on this with all the work, the link to tourism, the rehabilitation of tourists. So it's a good thing. Good to see you. Good to see you too. You came specifically for this festival? Yes. Why is it so important to you? For me, Voodoo or Obia was our first religion. Before we were introduced to any other organized religion. So it's in our blood. It's part of us as Africans where it's part of who we are. You know, you could believe or you could not believe but it's part of who we are. And it's how we act. We use different aspects of our benefit. To me, Voodoo is not negative. Voodoo is a religion. It's a natural religion. It's something that should be accepted instead of fear. So that's what Voodoo remains to me. That's how I feel about Voodoo. It's part of us. And my African ancestry is this. We are one piece. If we do not include our history into our lives, nobody will know about it. And we have to continue to understand and respect Voodoo. Life. Life. Basic. It's in Africa. Yes. My ancestry is from Africa. So it's our roots. It's really our roots. That's why I come here for to see, for to live this one. Connecting back to the point of Voodoo that doesn't make you feel. I feel wonderful. Every time I come to the continent, I feel something different and I feel something new. And this is a new experience. So I am connected. I'm connected with the earth, with the people, with the culture. I am connected. Always. But I want to give you props for your program. I watch it every time. We love you. Thank you. Thank you. Wow. Everything. What is all that I do for time? And it was time for the final performance and I think everyone was just waiting for this one. But he keeps moving. He can't even dance. And I think there was something in there. So it doesn't mean it was a snake that was moving this, this whole time. I've never seen or experienced anything like this before. But hey, it's not done. Let's head to the final phase of this festival. This is the 10th phase of the whole festival, right? Yeah. This is the evening program. What is happening or what is going to happen? What is going to happen is that we are going to experience a festival called Egun Gun. Egun Gun. Say it after me. Egun Gun. What does that mean by the way? In the local language they are called Kuvito. The spirit of the dead. And the language that we all understand for the spirit of the dead. Yeah. Wow. It manifests through people, through dances. Are they going to wake the spirit up today? No. They are going to manifest through people. You don't see them, but you see them dancing. I'm here to enjoy an authentic African traditional festival. But to be honest, I don't really like what is happening. I feel like it's more touristic than being spiritual. You know, having a great time. But the fact that I'm surrounded by tourists, man, you can't even enjoy it. Literally, real voodoo culture. I mean, experiencing it, it messes myself, learn something new, learn something different. But at the moment, what I'm saying, I'm not impressed, man. Because it's like they are selling the values and the culture to other people. Let me know what you think, man. This is what I do. Egun Gun, right? Yeah. That's a painting of Egun Gun. Guess who did it? That's the gentleman. This is the guy. The genius behind it. So, it means, does it mean that he paints everything or he just paints Egun Gun? He just gave them the money. Yeah. Did they ask for the money? No, he's appreciating their kindness, what they are doing. Are they going to bless the man? Yeah. They pronounce blessings. They just bless upon him. They just bless upon him. Yeah, so, this is the masquerade in Benin. They have just paid home aid to him. What did they do to you?  Okay? He prayed to me. Oh, for you? Yeah, for me. So, you believed in it? Yeah. And you know that it's going to happen? Yeah. Oh, and you gave them money or they asked for the money? Yeah, I gave them. No, no. I gave them from your hearts. By myself. Okay. I attended a festival in Benin. Yes. This is my first time, but I feel like the festival is too commercialized. Yeah. You don't think so? Yeah, I think so. Because this year is the first time I saw many people who come to Nigeria, Ghana, and Ethiopian, and all the African people who like to visit Benin. But I encourage people to come next year to come and visit Benin about it. But was it always like this? Before? Was it always like this? No, no. It was always like this. Was it more local before? More local before. Don't you think that we are losing the heritage and the value by making it like that? Yeah, yeah, yeah. Because even this morning when I came, the locals were just standing and watching. Yeah, yeah, yeah. And then we, the tourists are like Yeah, yeah, yeah, yeah, yeah, yeah. I was like, what's going on? I mean, I thought it's a festival. The people need to get involved. Because, you see, Benin people, they are not, I don't know how to say, the diaspora, they are not include their self a lot. The Benin diasporans, the diasporans from Benin, they don't include themselves in their poetry. Too much, too much. Not like Ghanaians. Oh, why? Because they see who do like, to do, they want to keep people, you see. Oh, really? No, no, no. They are scared of them. But now, but now, is the people from outside that are now... I feel like there are more white people here than black ones. Yeah. I don't know why, because now I saw many people from Portuguese, come from Spanish, come from Brazil, come and visit them. Benin people look around, come and visit their show. The biggest show. We are scared because they painted voodoo to be what? Evil. My point of view, white people, they have the first people who say voodoo is not good, it's heavy, but it's there, the first people who come to visit voodoo and they want to know the secret of voodoo in Benin. I don't know why. This is my point of view. They say, oh, every opportunity needs to go up. We all pray, bro, you all pray? Yeah, pray. Pray, man, yeah, every opportunity needs to go.  I mean, on this note, thank you so much for watching and I'll see you all in the next one. Please don't unsubscribe because of this voodoo video. I love and I appreciate you all. We are exploring Africa and telling our own story. Peace out.


Okay, so I'm Maxime Autran, I'm the product manager for the public cloud offering of OVH, which is based on OpenStack. We provide Swift and Nova as a service, and I'm going to share with you some of the insight and some of the choice we made to make this product easier, especially for most of our prospects and customers that do not know anything about OpenStack and sometimes do not know anything about the cloud in general. For some reasons, I will focus on the VMs on our Nova offering. We also have a lot to say about Swift, but I will not cover that today. So basically, to give you some insight, we launched the offer a bit more than a year ago. We now have more than 100,000 VMs running, commercialized on this offer. And we have a large variety of customers, and that's where I wanted to start the presentation. When we speak about offering OpenStack to the masses, we think, oh, that's a perfect product for a specific persona, which is the DevOps, because OpenStack allowing to spend new machines in seconds is totally controllable through an IPI, and therefore is really a perfect solution for customers that do infrastructure as code and want the infrastructure to be totally flexible. And that's right. When we discussed about launching this new offering internally, OpenStack was a perfect choice for it. It was just maturing at that time, being mature at that time. We saw a lot of implementation, and we decided to go with this solution. But even internally, we discovered that most of our colleagues did not get the full added value of offering the solution based on OpenStack and exposing the OpenStack API. So we waited a little bit, and we designed and marketed a solution around the different persona we saw in our current customer base at that time. And we went back from the use cases to adapt our public cloud offering. So this is the four different persona we decided to work on. So I just spoke about the DevOps, but we also discovered that the needs for the other were kind of different. For example, we were originally a bare metal provider for infrastructure, and we have a lot of cease and mean profiles amongst our customers. And the priority for that persona is actually high availability. It's also the performance. And at the end, it measures, for example, if the solution is good, checking the uptime of a machine. So we had to work a lot on that point. This need was also shared by another persona, which we called the newbie. So basically, it's the customers that wanted an easy way to spawn sometimes their first server ever. The first time they would become a system administrator, and they wanted to spawn it quickly and do basic operations through an easy-to-use user interface, a graphical user interface. And finally, we had a lot of requests coming from project manager or business unit manager from the company we provide infrastructures to. And their needs were about giving more freedom to their development teams for staging and development. And also, they wanted to be able to get predictable costs. That was a great concern for us. So this is an exercise, of course, I invite you to do if you provide a commercial solution. But even if you are in charge of providing infrastructure internally, do not forget to map your customers, and you will maybe discover that you've got different types of customers, and you can categorize them using personas. There is actually a persona working group within the OpenStack community. I had the chance to attend a few of the meetings in the previous OpenStack summit, and I invite you to join them or at least to read through their work on the OpenStack QX Wiki. One of the key differences between the different persona you saw before is, of course, the famous pet versus cattle approach. So we historically have a lot of customers using bare metal servers, VPSCs, and what we call private cloud internally. VPSCs and private cloud were solutions we have been providing for years, and they used VMware solutions. So the key message for those customers were high availability and redundancy of their data. And when we discussed, we had some focus group with them about the upcoming public cloud based on OpenStack, their main concern was even sometimes about the keyword instance, because that terminology was against their value. They wanted servers that would stay during a long time and never get down actually. So we worked a lot on high availability, and we decided, for example, to only launch commercially the product when we have a tested live migration working well, distributed storage using SAF with triple replication, that's the default type of storage you would get from us. And for the customers that were already in a cattle mindset, we also offer an alternative based on local SSD based instance storage for better performance. So each time we are about to improve the product, we always think about our different persona, and we may offer different kind of functionality or service. We also built a large catalog with huge instances. This is a bit against the cattle and the cloud approach, but we had a lot of customers asking for it, because, for example, we offer instances up to 32 cores, up to 240 gigs of RAM, and this is because we see a lot of customers coming from bare metal servers to the public cloud offering, but not changing really the way they manage their servers at first. So they come essentially for features like snapshots, but they do not use the total flexibility they could get from the public cloud at the beginning. Some have workloads that rely also on constant resources, and they were afraid because they tested some other public clouds where the performance could vary over time because of the noisy neighborhood and stuff. So again, we decided to have a quite drastic approach with absolutely no overcommit on our offering. So we communicate clearly about the actual resources you would get when you spawn a server. The last trick we did, that's maybe an idea for some of you, to ensure total vertical scalability, because we have a lot of customers that are still adding and removing resources in a vertical way, so adding, for example, RAM to a server and decreasing the RAM to a server. We offered all the flavors with the same disk size, 50 gig. This way, customers can easily increase and decrease the CPU and the RAM without reinstalling the servers and keeping their IP, because, again, they are not in a cattle approach. Each server comes with an active IPv4. We do not offer flexible IP yet. And each IPv4 is attached to a specific server. We also offer what we call failover IPs, that's an historic offering at OVH. You could move from a server to another and also to other products at OVH that are not controlled by OpenStack. So that people can create an hybrid cloud and move IP from other type of products to our OpenStack cloud. There is some specific adaptation we made also hearing the use case of our customers. For example, our IP are geolocalized. That's interesting for SEO purpose and it can sound really conservative, but that's something our customers wanted to. We have plans to offer floating IPs. We have plans to offer load balancing as a service directly integrated in OpenStack. And after that, offering also it as a service because we see more and more customers starting with a traditional approach and now wanted to benefit from the cloud flexibility and orchestration and automation. So this is what our UI looks like. It's really simplified. We also offer horizon as a service for those that are used to horizon. But we made this UI for a few reasons to simplify the use case. And one of the reasons when we early tested the product showing horizon to our customers is that they were completely lost with the fact that OpenStack is by default designed region by region. So for example, in horizon you have to choose a specific region you want to work in. And that's really not the mindset the customers add in mind because for specific projects, they would use two server in a region and another server in a second region, for example. So the web view you see when you connect to our cloud, show all the resources of the tenant across different regions. All the instances, volumes, IPs, et cetera. I made a really small recording, I hope it will be perfect, where you could see what the product looks like. So for example, if you had a cylinder volume, just click add a volume. You choose the size of the volume and it then appears in your infrastructure and you could just drag and drop it to one of your servers. So again, discussing with CIS admins, we just put in a web view what they would draw on a sheet of paper so that they are really keen with this web user interface. As you can see, there are other small tricks we did. I don't know, I think it's not readable, but at the top bottom of the page, you've got a notification because the server just finished launching. And you get the actual line you would copy and paste to your terminal to connect through SSH to your server. This is really something that makes the product really easy to use for customers that are not used to using this kind of product. So actually, the server is being started. So the volume is being added, you just take it and drop it to the server you want it to be attached to. And behind the scene, it would restart the machine also. Everything you would do in the common line interface is done automatically in one click here in the UX. Going further with the region limitation of OpenStack, we had exactly the same request from customers saying they wanted to create a private network through the different region of the OpenStack at OVH. So we came from the native and we are totally compatible with the native way to create private networks in OpenStack. So this is, for example, two different VMs linked in a private network. A second private network linking to other VMs, for example, in the same region. And we leverage OVH technology that makes L2 layer networks across our data centers. And we just link the private networks that share the same VLAN ID across regions so that our customers can actually create VLANs throughout the world through the different data centers from OVH. It is not closed to OVH data centers because customers could also make what we call a direct connecting from their own data center on premise or from other providers linking to their private network to the VRack. And you can also add other types of products such as bare metal servers or VMware private cloud that are also products provided by OVH. And this is valid in our different data centers. Coming back to a really simple problem, when we launched the product, we had a great success and we had dozens of calls, literally dozens of calls every day because of a specific choice that we made. Historically at OVH, when you would spawn a bare metal server, you would receive a root password directly by email. We considered it was not good enough to, it was not good to do it with a new product and with a public cloud. So we decided to make the SSH key usage mandatory. And people just were not able to create SSH key. So we included directly in the tutorial when you create a server, a small tutorial explaining how to create a key pair in Windows, in Linux, in macOS, just a four line tutorial so that customers can add SSH key within OpenStack and adding it to their server. So I talk about features, I talk about chewiks, but we also made choices around the billing policy. Because the main concern we got from customers trying or hearing about public cloud at other providers were about the billing. They were afraid not to be able to control their costs and not to say they were afraid just to pay a lot more than they used to using bare metal servers. So we made a few choices that were integrated in the business models that we decided to launch. The first one, it's a huge one, is that we decided to make unmetered traffic. So you would only pay the resources based on the early price or the monthly price of an instance, and you wouldn't pay anything more, whatever the outgoing or ongoing traffic is. We also chose to make a single bill, that's what most providers do. And we made a bill by Tenenter Project. So I spoke a bit earlier about the project manager persona. And this was really something that they wanted to have and they wanted to be able to do easily. Is to get the actual cost usage for each of their business projects. So we just told them, okay, create a tenant bar project. We're a technical tenant project within the OVH user interface. And each project will get a bill. Of course, we provide a credit card, of course, we provide PayPal to pay. But we also had a lot of corporations or administration wanted to pay using other ways, such as check or a bank transfer. And we offered them the possibility to top up some credits and then use the credit to pay the bills automatically. A native feature, also included, it's very basic, but it answers the need from the customer is the ability to define a certain level and answer the prediction of what you will use this month goes above this trigger you would receive an email. And finally, for the most conservative customers, we also decided to offer what we call the monthly plan. So basically, you can commit to each server and say, okay, I commit for this server for the month. And you get a 50% rebate and you pay immediately as the monthly price of that server. That's also helps us predicting the supplies. Because we know that if the customers commit for the month, there is a huge chance they will still use the servers the next month. So that's basically what we did to improve the onboarding. But I also wanted to share with you, to be totally transparent, the ways that we consider we are not perfect concerning our public cloud offering. And the first fail is actually the product name. Because when we, especially we were from France and when we launched the product, we launched it in France at the beginning. Now we've found worldwide. In France, the term cloud is commonly considered as a synonym for Dropbox or object storage. And we launched at the same time object storage using Swift and also cloud servers. And we had a lot of efforts to explain to the customers what OVH public cloud server means. OVH, so that you know as a large catalog of infrastructure and adding those public cloud servers essentially made the offer more difficult to read. We also discovered that the virtual machine market is really crudded. And it's crudded mainly by over committed VPSs. And it's again very difficult to differentiate in the market and make our differences clear, such as the no over commit policy. We did not manage to find a way to explain that really clearly too. We also, I think, did a mistake offering at the same time object storage and VMs servers because the market was not ready to understand the key differences between, for example, sender volumes and object storage. Even I think in the room everybody is really aware of the difference. It was not the case of our prospects and customers. And even in the interface you just saw earlier, for example in the billing you would get a single bill for object storage and for servers and that's a choice we should not have made. Because we discovered now one year later that the use case are totally different and the customer are totally different. So it makes sense to integrate, for example, Nova and Cinder because you would never use Cinder volumes without a Nova instance. But we have a lot of customer using only Swift or using only Nova. So we may split those two products and market them differently in the future. Another point where we are far from perfect is our management of images. So like all other products at OVH we will provide pre-installed OACs, about 15 different flavors of Linux plus Windows and free BSD. But we had to comply with OpenStack because we are OpenStack powered. We are one of the ones in the interrupt challenge yesterday. So it's really important for us and for our customers to stay totally compliant with OpenStack. But at the same time, we had to design the screens like that with a dash deprecated, etc. Because we do not handle well the deprecation of images. We made small acts to include, for example, Windows listening within the pricing of our servers. So you would actually get the standard flavor and the flavor dash windows that we would build differently. And that would include the Microsoft Windows license. So a lot of small acts that we made and that we still have to improve because I find this screen not really readable, for example. And we are just short on stuff also to have this OACs up to date on a daily basis. We also have work to include features to import and export images from other public cloud providers, also from VMware and stuff. So all this is natively offered within horizon and within the API. But our customers find it not that easy to use because they have to upload it somewhere, for example, at first, because their connection is not a performance enough. So we have to include those import and export services within our offering in the upcoming months. And the last thing that we still have to do a lot of work on is pre-installed software stack. So currently what we propose is just type your user data, script here, but we want to include a catalog of scripts there. And finally, one of the top requests we have from our customers is having a clearer and more accessible documentation. So today, most of the time we refer to the official open stack documentation, which is not always up to date and which is more targeted to develop since these admin operators mainly. So we make a huge effort to contribute to that documentation, but also to write a more comprehensive documentation targeting to our early cloud users. So we started working on webinars. We are working currently on tutorials. And we still have a lot of effort to do at that point. And finally, for example, during this summit we were a sponsor of the OpenStack Academy and we want to learn from that to replicate that in the event that we organize ourselves. So basically that's all I had. I'm available to take some questions. Maybe some of you are also public cloud providers. Maybe some of you are providing infrastructures to other teams within your organization. So do not hesitate to use the mic if you have any questions for us. So any questions? Perfect. Thank you.


Hello everyone, welcome to Veil Colorado. I'm Greg Lewis along with Natalie Bensevenga and Veil is known for many things and among them a very famous orthopedic surgeon Dr. Richard Steadman and tonight he is being celebrated after his retirement by the Olympic athletes that he treated and many who went on to win Olympic medals after they were treated by him. Natalie, a special evening. It's an incredibly special evening to have them all under one roof here to celebrate Dr. Steadman and everything that he has been able to accomplish. A lot of these people were treated by Dr. Steadman and were also mentored by him so I'm excited to see what they have to say about his legacy and about the future of both the Steadman Clinic and of Spry. The great thing is Natalie has never skied before, but if she does and she has an injury, she knows she's in the greatest hands error, is that correct? It really couldn't be a better place to get hurt, I guess, than here in Veil Colorado, but let's hope that doesn't happen.