ally it's jockovish nadal dominating, right? Uh, there you go sinner at number three, which is you know, he'll be back next week Rubelev at four runa at five fritz at six jockovish at seven Citi pass at eight liveage at nine and hashin up at ten I expect liveage to stay where he is because he had a really good week hashin up two Um, citi pass might struggle struf's gonna go up. I think we're gonna agree with that Runa he might stick around in the top ten fritz as well. Oh, sorry fritz fritz actually had a bad loss to to song who Wasn't a bad loss in hindsight, but it was a bad loss at the time Um, so look we're gonna start seeing a little bit more of a clay court flavor expect elcores to be number one Um, Medvedev losing the character might push him down to maybe number possibly number three Uh, or number four depending on rubelev how high he rises, but um, yeah power rankings will look very interesting blue cup By the way is a team trophy Uh, united cup for the americans. That's why they have a blue trophy. Okay um Palo vindizel just flexing too many times okay, he's Talking anyways, um vindizel just playing up to the camera big time Anonymous has to be a lot of pressure on alcaras to win this match Yeah, imagine if he had lost in home country against a lucky loser the internet trolls would have crucified him Yeah, that is the pressure now for him to win every match Well, yeah, he has a lot of pressure in in madrid and and basa loner, right because he is um You know being the hometown favorite And everyone's looking for uh, everyone's looking for a um looking for raffa 2.0, right? They're like, well, we got we didn't usually see a raffa, but he's not here. So elcores is their new guy So there is a lot of pressure being spanish Hey, thank you la for coming back for another month. Appreciate that. Thanks for the great commentary Can fans the best. Thank you la. You're the best Uh, vlado back for another month as well 10 months appreciate But yeah, look because the spaniards have been so the spanish crowd has been so spoiled right With with raffa dominating their tournaments over the last You know Nearly 20 years Now elcores has come along and sort of taken his place The expectation on elcores is huge because they're like, well We expect you to win everything because you're spanish And raffa did it so you have to do it now So there's a huge expectation on elcores To be a spanish winner, you know hometown hero Elcores said he wants to win wimbledon Yeah, that'd be interesting That would be very interesting. Carlos is expected to win all tournaments. He has tremendous pressure. He has tremendous pressure I don't think elcores is expected in all tournaments I don't expect him to win rome People think he's like in the betting it's he's the favorite for the french I mean we'll find out next week if anyone steps up and decides they want to be in the conversation, but I don't expect like when he's playing in madrid at home. Yeah, he's gonna be expected to win But I don't I wouldn't expect him to win rome. Does that who thinks who's gonna who thinks elcores gonna win rome next week? You reckon elcores is gonna win rome? He's the favorite because he won this week, but He also played the last couple of weeks, you know, he's played a lot tennis lately And if you don't think it's elcores, who do you think's gonna win? Yeah, I think elcores will make it deep in rome, but I don't know if he's gonna win I don't know who he loses to but I don't know if he's gonna win Elcores gonna win rome record. I look It's such a slow surface Elcores could to be honest elcores could play somebody And lose early like third round unexpectedly remember Monte Carlo when he lost a quarter And we thought elcores was gonna win everything and he lost a quarter in the second round of Monte Carlo We're like, what the hell happened there? Quarter's great, but also we didn't expect it, right? So I don't know. I'm a little Not worried, but I'm a little I'm holding off on elcores winning rome because It's a lot slower than Madrid And he's not going to get the easy free points that he uh that he likes to get Cine for I think Cine could could win rome. Yeah, Cine could beat elcores to win rome I think city pass might get might be able to get revenge possibly in on a slow surface of rome Runa, okay. See look there are names that I think are going to be competitive for sure Rude is going to win rome. Can you imagine? Who am I picking for roma? I don't know actually. I've got to wait for the draw to come out Rubelev could win rome. Yeah, true. I want to see rubelev take on elcores. Come on now. This is getting silly I want to see them friggin play It's been too it's just taking forever We'll get them playing eventually Can elcores ever win rome? Yeah, I think he'll win rome one day, but I just don't think he's going to win rome I mean rome's going to be one of the hardest ones for him to win Because it's so slow He's not he doesn't get the free points, you know city pass looks He could lose to anybody Does he though? I mean city pass lost a fritz at Monte Carlo. He lost a he lost a struff here and he lost to elcores and Barcelona I mean Yeah, he hasn't done as well as weeks as usual, but I think I think losing a struff. I mean that was not a bad loss because struff Struff had a very aggressive game for the entire week I think I think city pass might win rome If jockovish doesn't play Rome is not as slow it's not slower than the french, but it's as it's as slow as the french What tennis players like slow surfaces? you know city pass um Nadal obviously rude, I think will would like it better Uh, yeah, no one's playing rome at this stage He hasn't pulled out yet Rome is like a 20 is like 22 on the index, right? Yeah, it's it's it was it was 22 like a few years ago, and I don't think it's changed Also, it's usually wet in Rome. So it's usually heavy conditions, you know not it's not high It's on normal altitude. So it's not going to be as far like, you know, the ball's not going to be flying through as fast So a lot of the players that played well this week Um, like I don't know well struff. I don't know But yeah, the players that got three points this week are not going to have it as easy next week Was rome or was it raining Where it's always yeah, rome's always raining. Um What's the weather next week in rome? Ah It's going to be raining Terrible weather on oh sh gah yuck Wednesday, thursday, friday sat day sunday. It's going to rain in rome. Oh god. It's going to rain for the whole week And they don't have a roof Oh chat, we're going to have to do a lot of tier list next week. It's going to be 26 degrees Celsius So it's nearly 80 degrees on tuesday and then when the actual tournament starts wednesday thursday friday It's going to be thunderstorms and rain Oh, it's going to be like consistently raining.  It's going to be we might not even get started until like next tuesday Tuesday week Oh god damn it. Okay They haven't got a roof They haven't got a roof Why don't they make it indoors because they don't have a roof Maybe make it indoors. How? Yeah, we've got plenty of stuff to do during rain delays. Don't worry. I got ideas I got things don't worry Sissy battles Varev who is playing better? Uh, who's better player uh city bus Man rome should move their venue. Oh man.  I mean it rains every year in rome. We always get delays Oh god, it's going to be brutal strap yourself at least we know what's what to expect. Yeah Tennyson slow motion.  There's gonna be all kinds of shit next week It's gonna be hard to watch It's gonna be very hard to watch But i remember rome in the 2000s was Always studying like in the worlds what happened.  I'm out of here Formula one's gonna start. I'm gonna watch that. I'm also gonna put a video together because uh, I know I need to feed you guys content um But they even joining us. What a week. What a great week What a great two weeks because this tournament is uh, basically a mini slam at this stage um I'm on a miss Alcara seemed rattled today, but glad he was able to pull out a win Building mental strength bicep spain Bicep spain indeed. Thank you for the uh, two bucks. Thank you everybody who became a member and uh joined and donated this week appreciate All the all the donations. It's very generous Um, yeah, we're watching the draw tomorrow for rome. I have no idea when it's on but um, stay tuned Because we'll watch the men's draw tomorrow Uh for rome stay tuned for all the uh content. You know that we're gonna the ranking show comes out Uh today Every monday ranking show you guys You guys know Oh formula one just start um And then rome next week. We're gonna be starting possibly on thursday depends on the draw Uh depends on the women because women start on the month on the wednesday then men start on the friday So we might might watch something in the first couple of days But it's so hard to watch rome, isn't it because uh hard to watch these events in the first two days Because it's not usually any really massive names in the first couple of days, but We'll see what happens. We'll see uh, if if any matches and hopefully it doesn't rain that much that we can actually Watch matches when the big players start to play but uh preview draw ceremony all that stuff previews coming out as well Stay tuned for all of the rome All of the rome uh preview stuff that is going to come out because that's what we do every big event So stay tuned again. Thank you for joining us. Don't forget to like subscribe all that stuff Alcro's goes back to back in madrid 643663 It wasn't pretty But he gets the trophy anyway, and he's now a back-to-back madrid open winner.  Winning rome. I will find out we'll find out how his draw looks We'll see who actually plays in rome as well because there's a lot of withdrawals from this tournament But hey strip created history this week and alcro's only 20 20 20 year and one day birthday Get the trophy. Is that a thing? No See ya


I'm doing nothing at this point. I am doing nothing. You can let the guys out once your father has done it for you.


Hi, my name is Tarboos.  My personal trainer, Shaini, is helping me get less fat. Yeah, he cooks a lot.


Hi, I'm David Cantor with the Law Offices of David Michael Cantor and welcome to my blog. Today's topic has to do with Andrew Thomas' misappropriating RICO funds while he was in office. Now, RICO funds stand for Racketeering Influence Corrupt Organization Act and there's funds that are collected from assets during search warrants from criminal activity. In this fund, they're supposed to be used to combat organized crime. Well, when Andrew Thomas was in office, he used $127,000 out of that fund in order to pay outside law firms for legal work performed on civil cases regarding himself and Sheriff Joe Arpaio. Now, Bill Montgomery was the current county attorney stated, money spent out of a RICO fund has to be carefully watched. You don't want to create a slush fund that isn't closely related to the criminal cases they're supposed to be used for. Now he said he may form an independent tracking council which will look into all of these violations. In regard to Pinal County Attorney Jim Walsh, he stated, I would find it a stretch and I'm not sure I would find it appropriate regarding Andrew Thomas' conduct. Lastly, former county attorney Rick Romley was asked about this and he stated, to me it's just so far out of the realm and I believe it goes against state law. Now he also stated, you can make everything part of conspiracy regarding Thomas and Arpaio. I don't think you have the authorization to pay for civil things with RICO money. In fact, Romley himself turned down paying $180,000 legal bill to an outside firm from Washington D.C. with RICO funds when he was in office. All in all, it appears that again Andrew Thomas has harmed the citizens of Arizona and everybody's waiting for somebody to do something about this guy. I don't know what's taking the state bar so long. I don't know what's taking investigators so long but something has to be done. But that's what I think, tell me what you think.


So there's one thing on the agenda for today, which is that we are giving a briefing on a report that we prepared for the RVA review. And I'm going to do this fairly simply, just by looking through the report, which is structured in a, I reminded myself of it today, we've prepared it, finished, completed it about two and a half weeks ago, and basically just give an overview of what we found and what we wrote up in there. We were working with ARDC, if I didn't introduce myself, I realised Simon Cox from CSIRO. So I don't know everybody who's on the call, so people I don't know, hi, hi, John, hi, Sharnjit, hi, I'm not sure which Andy that is, most of the rest of the people I've met in the past. So John's talking, but he's muted, so I can't hear him. Anyway, so I'm going to share my screen that should, hopefully you can now see the cover page of the report with the link to which has been, I believe, circulated to everyone on this list by Cell. Discovered today that some, there's been some feedback received, which Cell has been dutifully pasting into a second copy of this document that I've only just discovered the location of. So at the moment, the report that I'm going to brief on is the original copy and has not yet incorporated responses to a small amount of feedback that we've received from Natalia and a couple of other people. Let me just, yes, Natalia lears a couple of other people. So anyway, if you can see, I hope everyone can see on the screen the cover page of the report. Just scroll through and just to reflect on how the report is structured. We started out just with a summary of what the intentions are around doing this review of research for Caballaries Australia. A little overview of what research for Caballaries Australia is. A brief summary of the stakeholder survey that we ran back in June with feedback from there gathered into under two headings, potential enhancements and limitations of the current service. Then an account of the workshop that we ran in late June. A separate chapter, which is additional information that CSIRO, as the people carrying out this review, have fed into the review based on our expert knowledge, if you like, and also our survey of other vocabulary research for Caballary Services out there in the world. And finally, some recommendations, which are tabulated under five topic headings. So we'll probably be most interesting to sprint through to the recommendations at the end. But first, we'll just give a little bit of a survey of what else we have the reviewers undertaken and what we've documented in this report. So compiled by CSIRO in collaboration with ARDC and in response to the workshop and the survey. So the overall headline output is that RVA is meeting a clear need, provides the suite of capabilities valued by the community. There are some ideas about potential future improvements. So ARDC, picking up on the work that ANS had done over a number of years, are in a process of reviewing the infrastructure services that they actually host, as opposed to those services, which they've been working with other collaborators with. And in particular, those services are Research Data Australia, the Federated Index of Research Data Repositories and Research for Caballaries Australia. So this first document is looking at the latter of those, Research for Caballaries Australia. And the intention is to identify future directions for the ARDC data publication services. So I've already given you an indication as to how the review was conducted with the survey workshop and then some additional input, interviews with ARDC staff and then comments based on this feedback round, which this briefing, I guess, is a continuation of. So this part of the report just gives a little overview as to the general background as to the service that Research for Caballaries Australia provides. I won't go into detail on that at the moment. And then a summary of what the current state of Research for Caballaries Australia is. That is, it comprises a vocabulary editor, which is based on cool party, which is a commercial product, but which ARDC hosts on behalf of the Australian research community. So they're wearing the cost of the license on behalf of the whole community. There's a vocabulary repository, which is based on an RDF data store with sitting in front of it, a bit of some open source software, which provides a link data view of the controlled vocabulary is there. There's a vocabulary registry, which is the first thing that you encounter when you go into the RVA website. The registry is the work that ARDC have hosted on the back end for updating and versioning vocabulary, the vocabulary portal. I jumped ahead of myself there. That's the first thing you see when you're going to Research for Caballaries Australia, which is the initial discovery state and the high level summary of vocabulary, as well as user support documentation. This diagram you've probably all seen because it's part of the basic offering on the RVA website. So there's a browser user interface for discovery, a browser user interface for vocabulary providers, registration upload versioning, registration API for vocabulary maintainers, so you can update vocabulary, search and download, and novel piece of the RVA kit is the vocabulary widget, which provides a widget that can be dropped into websites based on content hosted at RVA. So as of the end of July, there was 217 controlled vocabulary in the portal, of which about a third, 80 of them, are just a link to an externally hosted web page and the rest, a mixture of ones maintained and uploaded from pool party and those prepared externally. So diagram there summarizing that. Though vocabulary is hosted by RVA, follow contemporary web best practice. Every term has a URI and you get a web page or a machine readable version of that depending on how you ask. So there was a survey distributed at the beginning of June, I think was open for a couple of weeks. I only got a relatively small response, but allowed some insight as to what the community thought was important. Particularly interesting was the narrative versions of limitations, a couple of providers provided quite a lot of detail as to what they thought was good and particularly some of the limitations of research for Cabrera's Australia. Top of the list there is that in some communities, they don't need vocabulary to be hosted in RVA. Possibly they could be registered there, but they don't need to be hosted because they rely on a discipline or community hosted service which already exists. And then there was some issues around the difficulty of searching for terms across vocabularies and some opportunities for maybe improving the way in which RVA vocabularies can be integrated with enterprise tools and processes. A couple of issues around governance, particularly that the level of community or domain endorsement, vocabulary is unclear. RVA has been run very much as a bottom-up process where anyone who is eligible to have an account at ARDC can register any vocabulary they like. That sometimes means that there's more than one vocabulary covering a similar scope. In that context, it's important for users to be able to make some kind of a judgment as to which one they prefer to use and that not always easy. We had a workshop with this set of attendees at the end of June. We're organised by CSIRO and ARDC. So good representation from across some of the other NCRIS facilities, but also from National Archives, ABARS, IATSIS and Geoscience Australia. Program was very interactive. There was a bit of an intro session, particularly focusing on some presentations from three exemplary users of controlled vocabularies, but then most of the work of the day was done in breakouts around tables to get maximum engagement, addressing in the morning these questions, what's working, what are the gaps, and then a report back and then in the afternoon, sorting those and sorting priorities. So we have some captures of the outputs of the group sessions, which are included in the report here. Something which came out quite strongly, particularly during the morning session, was the extent to which the community engagement activity provided by ARDC is valued. So essentially this is the support that Rowan and Richard provide to new players who come along, wishing new vocabularies providers in particular, wishing to take advantage or use RVA for publishing their vocabularies, plenty of hand-holding and that turns out to be very much appreciated. Some suggestions about changes in new features, which are in the details that I'll probably leave until we're looking at the tabulations at the end, and some suggestions about brand new features. We attempted in the afternoon session to get these sorted along a number of axes. There were sort of general comments and more specific detailed comments, and there was ones which we sorted them into quadrants, according to level of importance and level of urgency, and we ignored the quadrant that said not important. So we just focused on important and urgent and important, but we can wait a while. So that's what the tabulation here goes to. So more or less all of these topics are picked up in the recommendations at the end, so I'll leave discussion of those to that. Finally there was a subset of the people who were involved in the workshop who were not current RVA users. So rather when at the stage where we were doing a retrospective on people's experience and suggestions around the way RVA works at the moment, instead of doing, since they had no retrospective viewpoint to provide, rather they took on the job of brainstorming about what an ideal vocabulary service would be. Some of some topics of which are already present, some of which are fantastic ideas, but might take more than ARDC and the community is currently capable of doing, and other ones were able to feedback into the recommendations. So then as I say, we did some additional work on doing an external scan of related work, both in terms of a tabulation of some other initiatives and services. This is the kind of content-oriented part of the other work. So a wide variety of different services, and this is this can't possibly be comprehensive by the way folks, but it's the ones which we're aware of or have encountered vocabulary services for some research communities. The one at the top there is a very general purpose. This comes out of the library area. The DDI Alliance do a very good job of managing their controlled vocabularies in social sciences, official statistics, public health, those kinds of things. And then a series of sort of natural science oriented vocabulary services with links and also an indication, not only the scope, but some comments on the status. So in some cases they're very stable, some cases they're not sure if you call continuous maintenance stable. It means things actually do change regularly, but the service itself is stable. Some are wide open by a portal. Anyone a bit like RVA can submit a vocabulary as long as it conforms to our link and get in. It means there's a lot of vocabulary is there, but other ones it's much more curated. So I'm kicking the tires a couple of years ago, I submitted some vocabularies to AgriVoc and got a polite email overnight saying, I don't think these are agricultural vocabulary, so please remove them. So which was interesting to discover useful. So say quite, you know, a reasonable list here, and the community should be aware of these and a couple of emerging or new initiatives down at the bottom there. Some comments on governance patterns because governance was one of the things which the participants in the workshop seem to be particularly concerned about that governance patterns. There's not as much guidance as people would like when perhaps not as much information as people are expecting about the governance status of some of the vocabularies. You know, looking through what's in RVA to a certain extent, that's just it's down to the what's contributed by the people registering vocabularies in RVA, and I've even in the last week or so picked up on some of the vocabularies that Ann's now ARDC themselves submitted into RVA and said, hold on a moment, the descriptions in the metadata on the top page there is incomplete and makes it a little difficult to assess why you'd use this one versus another one. So the the floors go all the way up and down. I guess there's some questions about whether there needs to be more rigorous checking and whether the wide open nature of submitting them is meeting community requirements. But as an as a comparison, basically did a brief description of some governance arrangements for some other vocabularies and vocabulary services, which I was particularly familiar with. So increasingly, there's a lot of use of issue trackers and ticketing systems, particularly around GitHub. So that's, anyway, it's described in here. A little reference out to standard governance models as described in one of the standard stacks that some in our community use. This comes from the geographic information standards with the idea that you separate out the management of the content from a technical point of view for the management of the content from a sorry, the management from a conceptual point of view, and such like but basically this is just drawing attention to the fact that there are quite rigorous models for how content would be maintained and including some sequence diagrams flow diagrams, decision trees that which are in these standards. Finally, looking externally, a bit of a technical view here about some of the platforms which are available. RVA, primarily the link data API to vocabularies is based on the elder SysFox stack, which Jonathan and I were actually were involved in developing SysFox quite a few years ago. And when RVA was establishing its offer in the first place, there was a small working group that evaluated a number of options and decided to go with that primarily because of its open source nature and its compatibility with web standards around machine and machine readable and also human readable interfaces. But there's a number of other offers out there. Sorry, I'm not going to see because I'm scrolling up and down with and as I mentioned, the the tech stack which RVA that part of the tech stack is is, you know, arguably getting quite long in the tooth. Now, although there's no reason why it still functions perfectly well. But there's, there's, there's alternatives, which are listed in here. And and on and on and on. So the bottom ones on that page there to proprietary tools, pull parties already installed as an alternative from top quadrant, both of which come with moderately hefty price tags. But obviously RVA has been able to, sorry, ARDC has been able to absorb that cost on behalf of the whole community through their pool party offer. So okay, finally, getting into the recommendations, we sorted these into, as I say, I think five, the topic areas on engagement, training and practice, governance, tools and technology, content and impact and analytics tracking. And the the recommendations are numbered and they're also got a little color coded icon to indicate what the source of the particular recommendations were divided between things that ARDC themselves contributed as part of the consultation, two kinds of contributions from stakeholders, both from the workshop and from the from the survey. And the expert feedback was stuff that CSIRO should have in as part of our role in the review. So in the engagement, training and practice, big ticks to the current help, help desk service from Rowan and also sell, sorry, sell I ever should have mentioned you before, including the facilities for notifications and meetings of the Australian vocabulary services interest group is this session are all appreciated and should continue that was coming from the stakeholder feedback. And then there's number of ideas about improvements in the engagement, particular one that was coming through was the idea that there's not enough sharing of user stories about how different communities are able to effectively use RVA in them for the management and publication. The challenge there is that different communities have got different views of the have their own internal processes for how they manage their recoveries and how they want to publish them. In fact, there's a lot of flexibility in the RVA process, which means that having a map to get through that and how to effectively reflect your communities requirements on the technical platform that we're using need a bit of guidance on that. And the idea is that perhaps the best way of doing that is through through some user stories, which allow you to say, Oh, does my community operate in the way that this other community is already operating? This is how they went their way through. In the governance space, there is a recognition that the metadata is a bit messy. That because early on some of the metadata fields were free text, it means that sometimes you've got multiple entries for the same organization or the same person. I know my name is in there several times CSI Rose names in there several times. And that means that sometimes it's hard to keep track or get a proper evaluation of the provenance or source of the capillaries, because it's a bit tangled up and that needs to be some of that's because the means to do that was not always available or kid and ROR have only come along. Since RVA was established, our ROR is the registry of research organizations. And so that's a way of giving identifiers to research organizations until a year ago, that was a bit of a black art how to do that. But as the web of science or web of research, if matures, RVA needs to reflect that now that probably means there needs to be some remediation of existing of the existing offer in there, which is something which ARDC would have to someone would have to roll up their sleeves and do a bit of probably some manual work to remediate that if that was to go ahead. But the suggestion is that. Oh, I didn't say at the beginning. We've also got as well as those five categories, we've got the recommendations sorted into a continue improvements that can be made on a relatively short timeline one year and longer term improvements, say a three year timeline. So anyway, documenting the user stories and patterns of governance again is seen as something which needs to be, you know, is likely to, to spill out beyond the one year timeline. Looking at tools and technology, the pool party editor is very much appreciated by I mean, it looks like it's fairly heavily used. It's used for about half the total vocabulary is and for significant majority of the ones which are actually hosted by RVA supposed to just linked to. So pool parties appreciated the machine readable the report the API, the elder sysbox thing is also seen as good. And the the top level interfaces as well as the widgets are appreciated. And number of users commented that the term search is difficult to use because you get multiple hits from different recabularies but then to look at the details you have to burrow down into the individual vocabularies. And so cross vocabulary term searching needs needs an upgrade. Vocabulary mappings is an area where that's a never ending project, of course. But people are certainly interested in it. Some possible other issues about about updating or improving API access into other applications. Looking a bit further out, there's some richer functionality that potentially can be provided beyond just term search, including for example, a recommender by a portal runs one of those where you submit a bunch of text and then it says, ah, it looks like you're working in this discipline. And here's and here's the based on the key terms in here is the vocabulary or ontology, which covers most of it. So it might be the one that you that you want to use. And also there is the question about, you know, we don't want to just sit on our rolls. And if there's some of the other technology options would provide some improvements, then we need to keep our eyes open about about to adopting those. Terms of content. Although RVA is primarily based around SCOS type terms and definitions. It's not only limited to that. And certainly a couple of vocabulary which I maintain in there go way beyond SCOS. And that's seen as a feature to be maintained. One of the issues that comes up from time to time is the extent to which the sort of passive bottom up approach is enough in terms of content or whether ARDC could be more proactive in searching out and acting as a curator or adding additional content. And then there's vocabulary mappings, again, which is a content issue. And finally, on the impact and analytics tracking, the idea that vocabulary publishers need to be able to get feedback about how much use there is of their vocabulary and perhaps some information about who the users are. But that is kicked down the road a bit into the three years and later stage of the recommendations.


Hello, everyone, I'm Priyanka Sharma and I'm the general manager of the Cloud Native Computing Foundation. I am thrilled to be here today. Cloud Native technologies are fundamental to the deployment of 5G networks. As a result, it is imperative that telecom operators partner with foundations like CNCF and Linux foundation networking to run more performant, resilient and cost effective telecommunication infrastructures. By building a telco specific Kubernetes distribution in the R2 work stream, Anuket helps position the telco industry to go cloud native. We are excited to see future collaboration between Anuket and CNCF initiatives like the telcom user group and our very latest the CNF working group which defines cloud native network functions. Thank you so much for listening and I hope you enjoyed the show.


Good afternoon. My name is Randy Clark. I'm the president of the American Society of Anesthesiologists. It's my great pleasure to be with the Patient Safety Movement Organization. It's a great honor to be with you today and talking to some of the great leaders in the area of patient safety. Today I'm going to talk about two subjects that I am greatly interested in. Patient safety, specifically as it relates to anesthesiology, and also a little bit about aviation. I am the son of a U.S. Air Force officer who was a pilot in the Air Force. His last assignment was at the Air Force Academy in Colorado Springs, which is why I'm currently working in Denver. And while he was assigned there and I was a teenager, I obtained my pilot's license at that time and have been interested in aviation ever since. So I was very excited to be able to be asked to talk a little bit about innovation and how we can adopt innovation and aviation into medicine. This is an area that I have looked at for a number of years. It really comes down to how do we make progress in any area of human endeavor, not just in medical care. So I'm just going to give it a real simple overview. It's one of three ways. We can either adopt better organizations with better execution of existing ideas. We can have better efficiency in how we operate our groups and organizations, or we can adopt innovation. New ideas are adapting old ideas to new situations. And it's this third area that I'm going to talk about with innovation in aviation as it applies to healthcare. I looked a little bit at the history of the Patient Safety Movement Organization and it very much aligns with the Patient Safety Initiative taking place at my own hospital. We call this Target Zero and the goal is to eliminate preventable harm, which I think is in complete agreement with what your organization exists to achieve. This is highly desirable, a very laudable goal. It's also very hard to do. Eliminating all preventable harm while a very legitimate target requires some significant rethinking about how we deliver healthcare. I would like to introduce the idea of maybe a different approach to this issue, trying to achieve the same goal. And this would be what has been called in aviation, and specifically military aviation, the failsafe concept. And this is the recognition that incidents, accidents do occur. We have to adopt our systems to make the results as minimal as possible, recognizing that accidents can happen. The term failsafe was popularized by a book and an excellent movie of the same name as only Hollywood can do in the fiction book. Even in the best designed system, sometimes that leads to unhappy results. But in general, the idea of designing our systems to be failsafe is to recognize that errors can occur, but we just need to try and minimize the unanticipated effects of those errors. And so I'm going to emphasize that a little bit in my talk. This airplane is called the Cirrus aircraft. It's a technologically advanced aircraft that came onto the market in the early 2000s. Many people know this airplane because it's the airplane with the whole airframe parachute. This is the idea of failsafe in action. This aircraft in this particular picture was being transported ferried from the mainland US to Hawaii. When you do that, you need large ferry tanks of fuel because it would not ordinarily be able to fly that distance. As the pilot was approaching the Hawaiian Islands, he was not able to switch to his last tank. The aircraft ran out of fuel and he had to ditch in the ocean. So he activated the whole airframe parachute. Ditching in the ocean is difficult. It doesn't always result in a good clean outcome. But with the use of this whole airframe parachute, by the time the Coast Guard who took this picture arrived, the pilot was sitting on the wing of his airplane with his sunglasses on. So this is the idea of how we adopt our systems to be failsafe recognizing that events can occur. So it's with some trepidation that I give this talk to you because I know some of the backgrounds of the other individuals addressing you and they do incredible work in this area. I'm going to talk a little bit about that in just a moment. In terms of safety initiatives within the aviation industry, perhaps the oldest of the modern era is the aviation safety reporting system that was put in place in 1976. In this system, if there is a rule violation or some other problem that occurs during a flight that may make a pilot subject to administrative action by the Federal Aviation Administration. If this form is filed within a specific amount of time after the incident, it provides immunity from further administrative action taken by the FAA. These reports go into the details of whatever event occurred and collects as much information as possible in order to make recommendations back to the FAA on how to improve the aviation system to prevent those same kind of events from taking place in the future. This is a very active process. NASA itself processes this information to make it to take out all of the individually identifiable information before it reports it back publicly. When we adopt these systems in healthcare through patient safety organizations, they're not nearly as robust as the NASA aviation reporting system. We have trouble when we get into areas where patients experience injuries because then the tort system begins to take over. So it also creates a layer of obscurity around actual events that we may not necessarily be able to learn from if it wasn't reported through and actively analyzed in a peer review process. I do think that the aviation system for reporting these events is a robust one. We probably should look at something similar in medicine across all specialties. We have something similar to this in anesthesiology that I'll talk about a little bit at the very end, but we also may need to look at ways that we can open up our whole dispute resolution process to be more open and helpful in preventing errors that occur in medicine. So I mentioned previously some of the speakers to this conference have had a long history of studying safety and aviation. Peter Pronovost is a leader in this area. This report from 2009 in health affairs recounted the information on the commercial aviation safety team. This was a landmark group of investigators looking at how we can improve aviation safety. This was the group, the CAST group, that really promoted the use of checklists and training on how to use checklists in emergency situations. I can't emphasize that latter point more strongly. The one emergency aviation situation I've been in my flying career, not having worked on my checklist for that event in the recent past really did not allow me to use the checklist to the fullest extent possible. The idea between behind crew resource management and teamwork training arose from the CAST aviation reporting. The incident reporting system was reinforced for the value that that provides, even though it predated the CAST work simulator training and standardization. Anybody involved in patient safety know that standardization is absolutely essential to our ability to drive improvements in health care. If everyone is doing their own thing, it's impossible to measure and impossible to make specific recommendations for improvement. I do want to talk about one specific aspect of the crew resource management idea. CRM came about because of a failure in crew relationships that led to an accident when the co-pilot and the engineer for the aircraft gave excessive deference to the captain of the aircraft, allowing the aircraft to run out of fuel and crashing short of the airport. The idea of being a good follower was really established by this concept. The era of the infallible leader is over, but this does increase the responsibility on other members of the team. And everybody must approach their tasks and their role with diligence, honesty and mutual trust. And the whole idea of trust I think is essential to the ideas of how leadership can truly operate effectively and meaningfully. So what are some of the new areas in patient safety that might be applicable to aviation? Well, like aviation we keep trying to apply the principles of high reliability organizations to health care. I think that's an imperfect match for health care. The consequences of decision making in health care tend to be concentrated on individuals, not large populations. We have poor standardization in health care. Typically we're getting better. We operate more like a boutique rather than an HRO such as a nuclear power plant. And while we work in a technological environment, our decisions are both personal and individual. Technology is not always employed as a protective measure. One area that I learned about in my research on this topic and in my background in aviation, when we develop new aircraft, the flight envelope is slowly expanded to new speeds, new altitudes, new configurations of the aircraft. And so the envelope is expanded slowly. But by using new mathematical techniques, we can cause perturbations in the aircraft's situation, measure the reaction of the aircraft, and then use that to mathematically expand the flight envelope. And I apologize for the term spastic pilot, but you have to realize that these were engineers that came up with this concept, not people in polite company. So this idea I think is adaptable to health care. If we have intelligence systems that measure the response to the drugs that we administer, especially early in an anesthetic, and be able to look at or predict how the patient might respond to the same drug at different doses later in the anesthetic. So I think there's some opportunity here. This particular area, my two daughters are very excited about, we need to understand why women are safer in aviation. I want to give you three examples from the British experience. They found that their female pilots were much less likely to be involved in aviation accident accidents, even accounting for the small fraction of women in the British pilot population. This has held up in the United States studying accidents from 83 to 2002, with again about 6% of the flying done by women, but they only had 4% of the non fatal accidents. They only had 2.5% of the fatal accidents, even though they're 6% of the flying population, meaning that women may be two and a half times safer than men in aviation. And in the military itself, Army studied this area from 2002 to 13, 10% of Army helicopter pilots during this interval were female, and they accounted for only 3% of the accidents during this interval. And even the presence of a woman on a flight crew also resulted in a proportionally reduced number of crashes in this area. This area has been looked at in medicine, specifically in internal medicine. I would love to be able to look at this information in my specialty, see if this holds up for female anesthesiologists compared to males. So what are some of the other areas and how do they compare between medicine and aviation? Well, as I mentioned with the Cirrus aircraft, these are technologically advanced aircraft, meaning that they have very integrated digital monitors in the cockpit. We are developing these kinds of systems in the operating room. We expect even future improvements to be significant. Autopilots are almost essential to flying. They make flying easier and safer. And there are some techniques looking at what is essentially closed loop anesthesia that would serve as an autopilot in the operating room. That's a research area at the present time. And there are some discussions among commercial vendors of other areas where this might apply as well. And then finally, the area of artificial intelligence is absolutely under huge amount of investigation in medicine and specifically in anesthesiology. We're starting to see some of the early fruits of this labor by decision support tools where the equipment will look at the situation in an operating room and make recommendations for next steps in the conduct of the anesthetic based on machine learning of previous cases in large numbers. I do want to mention briefly some of those things that don't translate between aviation and medicine particularly well or maybe just not yet. For pilots, medical certificates are required for airline pilots at a very high interval. We don't do anything similar to that in medicine. We do have random drug testing and aviation that's not typically used in medicine. We have very frequent simulator testing for pilots in the airlines or flying for corporate flight departments. Check airmen will sit in the cockpit observing the pilots in real action and make recommendations for improved performance while some of the lean concepts of having people walk through the operating rooms. We don't really have much comparable to check airmen for our delivery of anesthesia care. Everybody knows about cockpit voice recorders and data recorders. Those are used to analyze what may have gone wrong in an aircraft accident and find root causes. There are attempts to incorporate this into operating rooms. There is a growing field of literature on this particular area, but it's still primarily of research interest and fairly new. We have not seen widespread adoption of this approach, which is ubiquitous in commercial aviation. I'm going to close just briefly by mentioning how ASA itself addresses innovation. We have a committee on this subject. It used to be called the committee on future models of anesthesia practice. This assignment was expanded somewhat to include all realms of innovation. The committee continues to look at practice models. It also looks at an expanded role for the anesthesiologist through the entire period operative period. This is the committee where those with expertise in artificial intelligence and machine learning bring that expertise to make recommendations to the anesthesiology community. We have a committee on equipment and facilities that looks at the technological aspects of our equipment. And we actually have a fairly large free standing anesthesia quality institute since 2008. It houses three different registries. Two of those are listed here. Our anesthesia incident reporting system is a national system that is somewhat analogous to the aviation safety reporting system that I mentioned earlier. And there is a wealth of information that is collected on these events. The difference between airs and the aviation industry is that these tend to be individual reports of events that are then collated into lessons learned across different aspects of care. We are currently investigating whether to hold an innovation summit or establish an innovation center. The center idea would be that if members bring to ASA some new concept that bears some investigation and may require some start-up funding, ASA may provide that. This would be analogous, we hope, to the extremely successful DARPA agency that advises the federal government. That work is still extremely preliminary. And then I would just like to briefly mention the ASA's quality and patient safety meeting. Last year we had over 300 attendees in the virtual event. This will be held this July. And if you're interested in this patient safety area specific to anesthesiology, please try and attend. So thank you very much. It's a great pleasure to be with you. And I'm very hopeful that I'll be able to meet with many of you in person in the near future. Again, thank you. Good afternoon. I am Edwin Lofton, Senior Vice President of Integrated and Acute Care and Chief Nursing Officer at Perish Medical Center in Titusville, Florida on the space coast. Perish Medical Center has had the honor of working with the Patient Safety Movement Foundation for several years now. In fact, we were one of the first hospitals to deploy every one of the actual patient safety solutions from the Patient Safety Movement Foundation. And they've made a difference in improving safety and reaching towards our goal of zero harm. Perish is also very humbled at this point in time to be recognized by the Patient Safety Movement Foundation as a high reliability organization. Being recognized that is not the end of a journey, but the journey itself. Perish has used our mission, healing experiences for everyone all the time as our guiding force to make sure that we continuously look for improvements in patient safety, patient outcomes, and the wellness of our community. Perish Medical Center has been committed to using objective scientific measures of performance improvement such as Lean Six Sigma to guide us in our processes of improving patient care and outcomes. Again, thank you Patient Safety Movement Foundation for this recognition. We commit to continuing the journey.


The session is by Andreas, who talked about disk image builder. Andreas, the stage is yours. Okay, thank you. Thank you very much. Thank you for coming. This talk is about disk image builder and creating operating system images with this tool. Before defining what an operating system image is, let's have a spot to the history. Whoops, sorry, that was too much. Once upon a time, operating system images looked like this. Anybody, any idea what it is? Yes, exactly. From Commodore 64, about 30 years old. So this type of data is something like I want to talk about. So this was about 8 kilobytes. And typically these days, the modern operating system are much bigger and stored on disks. But in principle, it's the same data. To send it's about me. So I'm currently involved in mostly three projects. The latest project is my joint user CNC router, which I built these little wooden things there. It turned out that this is mostly a software project. I never thought about it.  Then I have the RM2. It's an open source requirements management project, which I'm working on. And since about a year, I'm core developer for OpenStack Disk Image Builder. And this is why I'm here today. My agenda. So I hope I will finish in about 30 minutes. This is really an introduction talk to Disk Image Builder. I picked only two things out, which I want to explain a little bit deeper. But it's mostly really an introduction of what you can do with it. So the green lines, it's really an introduction. And then these things are a little bit more detailed. Oops, sorry. So an operating system image is mostly something like an operating system, especially in one format, maybe as stored on disk as an image, which means as a file somewhere on a disk. Other names are also golden images and templato as images. And typically they are used in environments like cloud images or virtualization platforms. This is one way to build operating system images, which means putting with B-stick or something like a DVD into your computer booted and you will get sooner or later something like a picture like this. And you have to go through the whole setup of installation and image. You have to specify which packages you have to install and so on. I think everybody knows how to, and mostly did it already, I think. Yes. So this is typically a way if you get in your computer, you put this. Then there is another way. This is using a tool which builds your image. So they are typically for each operating system. There comes a tool with you which just puts up an operating system on the disk, mostly as a street structure. There is an example for the bootstrap. So you just enter this thing with the bootstrap, stretch, dot, and then you have two minutes, three minutes later you have a complete Debian system in your directory. So these are, let me say, the historical things. The problem with this is for each operating system, something like this, for each operating system you need a special tool. You need a special configuration. And what you end up, so if you need a couple of them, you end up simply something like this for all of your environment, for all different operating system distributions, architectures, you have one configuration file, one tool, and then you run it and create something like a disk image. And disk image builder tries to solve this problem. It is something like it takes up one, only one configuration and builds really a couple of things, a couple of architectures, a couple of target systems from one configuration on one host system. You have some examples that you can get a feeling for it. So you can just have, for example, to install a Debian minimal system, a Debian minimal or Fedora minimal, send-off minimal and so on, and also what you can do is not only creating virtual machines, but also Docker images from it. What is under the hood is something like really the system, the system tools for this specific operating system are really used. So RPM or APT or DPKGA or something like this. So this is done inside. You as a user of disk image builder, you don't even see this. The support matrix of this, so it's really astonishing how much you can build. So you can build mostly all the mainline things and you can even build different architectures. And this is really done, really can cross to it. So you can have, for example, one MD64 and build something like for a PowerPC, an image from PowerPC. Or you can have an Ubuntu and then you can generate an open zooser for it. So it's really universal. And yes, you can see the bubble over there. This is something like under the hood. So under the hood it's something, it uses QEMO to run the target operating. So the post scripts, the binaries on the host system, which gives you a really complete, for example, complete installed binaries. Here are some environments. So this is which I've really tested. So VMWare, OpenStack, KVM, Amazon, Docker. This is what I tested. There are also possibilities really to use it as a bare metal. So you can use these images, create these images and then put it with some specific method and bare metal and can also use this, yes, this one image or this one based on this one configuration you provide. The disk image builder itself, it's something like a modular system. So what it has is something like elements and for each function or each function block is put into one element. For example, this tibian minimal is one element. VM is one element. The topic master is one element. You can think about hundreds which come directly with this image builder and there are a lot of these elements also in the internet. So for example, if you want to install an image for an Raspberry Pi you can grab it from the internet, specify Raspberry Pi and you add an image for the Raspberry Pi. Some example elements, so really the small set of examples. Yes, you can see. So I don't want to go into detail here. So there are a lot of things you can just put into your VM directly during creation. Some words, what is an element? So an element is mostly something like configuration. So let me start in this way. It resists in one directory and it's a collection of configuration files and directories. And in this directory there live some scripts. So I have here an example or a very small example. An element itself can be dependent on other elements. You can just have a small text file where you can all list the other elements which are also then included. The package installed. So these are the packages which are installed during the creation of the operating system image. And as you see you can just put the name here and also you can have something like different ways of specifying names. And there's also some way for different distributions because the distribution typically name the packages in a different way. Then there is typically some... So there are at least, let me say, there are about six, seven stages during this build process. For example, you just prepare things. Then they are installed. Then the boot loader is installed. Then the cleanup is run and so on. So there are seven different stages of this. And each of these stages are put into a separate directory and the scripts in this directory are then executed at the appropriate stages. So for example in the environment you can set some names which are then picked up by other elements or in the directories themselves there are something like scripts like these things. So this is really where all the work happens. Okay, then I want to talk a little bit about the block device layer because this is an important point. So there are a lot of things you have to really put into the operating system directly. So for example adding a package that can be done later with the configuration management system. So in a golden image. But you won't want, for example, to play around with your partition table with your LVM and so on later on. So this is something like you have to do first directly into the operating system during the build of the image. One year or something like this ago the complete block device layer was about it exists exactly one image and with one partition and that's all. And yes, there was a lot of work done during this last year to implement different ways. So what we did is something like we leveled, we did some levels. So we have something like, for example, one level in this block device layer inside the disk image builder which provides this space. The typical way is to have a loop device which provides local disk but other things are possible but not yet installed. Then there is a way that every one thing this is where mostly the complete work is done. So this is something like mostly combining things what you get from here. So for example you have two loop devices you can put in one partition table on the other LVM and whatsoever you can think everything or what you want and what is important you can put it this level really into itself. So what you can do is, for example, you can have a partition and on top of the partition you can have an LVM and based on this LVM you can have, for example, a crypt setup and so on and so on. Where I can say that the crypt setup is not currently implemented. So you get something like a stack. Yes, the other ways are mostly something like, okay, the other ways are mostly something like typically what needs to be done so you need to do a file system on this that needs to be mounted. It needs to end the FS step and because we have to, of course, path this over to the real system. One example that you can maybe have and think how it is configured but the complete configuration is done by means of a YAML file. It's one YAML file where you can describe the complete hierarchy for the block device layout. And here is one thing, I think it's mostly self-explaning. So you have a local loop there which is, yes, depth loop device handling. Inside this there is a partitioning done. Inside the partitioning is done with a master boot record and yes, there is, for example, one partition which is primary and so on and so on and the whole thing is done. So this is really a very, very simple example to have to get you an impression. So typically if you have something like a logical volume inside the partition table and you have five or six logical volume this gets really lengthy. So everything is possible here. This is just an impression to give you an idea what happens. Yes. Then there was a time where it comes to writing this MBR, this master boot record. These are 72 bytes which has to be at the correct position so I did a DD there that you have something like, so most of them are also zeros. And of course the typical way is look at the internet, grab something which is available and use it and we discussed it really on the development side and we really didn't find anything which we can use because all these tools are either not really thought for scripting or they are, yes, they're doing a lot of things they shouldn't. For example, we had to look at this parted so this is a new parted pro thing. One clash but we could, around this it was licensed because this is only GNU, it's really a GPL, not LGPL so it's a little bit, and the whole disk image builder is under Apache so we have something like maybe a problem there if we would have to use the appropriate libraries there. Calling parted would be possible but parted itself does a lot of things, in my opinion it shouldn't. So it just not only writes these bytes there but also do something like call to kernel for updating the partition tables, it calls Udev, it tries to optimize things and this is really what comes into mind where we really sorted it out, it tries to optimize things. So it looks for example into the kernel which are the buffer sizes of the disk which I want to create and tries to optimize, tries to align them but currently we are on the host system and targeting for a completely different system and we have measurements that using parted gave at some point performance for about only half the performance so you lose about 30 to 40 percent performance if you don't align correctly. So this is why we really implemented this thing as in Python in 150 lines of code so know it there, know it's tested. If you want to write, you'll have something like a master boot record, you can pick it there and you can use it. So then maybe some development insights. This is the OpenStack, this image builder is an OpenStack project, it's a part of the project and from the size it's really small so it's about 1200,000 lines of code and it's about 7,000 lines bash in Python mostly. The new block device layer which was created during the last year is about 3,000 lines of code. What is a little bit problematic what I think is that there are really many, many adoptions so let me say something like this, every third line is something like if you have this system we know that there is this problem and we have to work around this. This is a little bit problematic but for such a tool which aims to be universal you have to do something like this or you cannot just support it. Yes, also the design should be improved, I think we did already do a lot of things there for example this adding the block device layer because before it was something like spread around so each element has something, an own idea about it and now it's really centralized but there are other things which could be optimized. What is sometimes really annoying to me is the slow development cycle so you have your great idea, put it into a garret and nobody cares. This is really something really strange and it takes weeks or months that somebody else picks it up and they will look at it but this is I think in my opinion I'm not really sure about the other OpenStack project but this is for this image builder this is really a problem. We have I think one patch outstanding for AFI boot which is mostly two years old now. Yes, it's really hard. If you have some spare time you're invited to have a look at this so everybody can review it and have their own sort there. The last thing that is a little bit related to this is that all the different maintainers or the different contributors really focus on their own development but they just want to for example feature X and they just really try to put it in and even if it's really not in the right place if it doesn't really fit into it and even if it's really sometimes you get something like a mess so we have just to say no, not this way. Oops, that was one. One recap. So as I said in the beginning this disk image builder one configuration all targets but this is just for an ideal world. As I said there are a lot of problems and there is one matrix build so it's something like an element which in turn builds docker images which in turn then use disk image builder to build all the other things so what you have is something like really something like a building matrix and you don't have to read all the things but just to give you an impression on the top there are the hosts so it starts with center seven db and buster, jc, stretch and so on Fedora opens with it and this is not really finished so it goes on and here there is a target so which ones you try to build and I do this each some weeks to get an impression how stable it is and where is some work. As you see there are a lot of greens so there are a lot of things you can really build but you have to really take care that some just do not work so for example we have there are some problems like it's not here but for example it opens with just to pick one example there is something like that there are some no scripts for example to build up-to-date deviant systems so you just cannot do this because they are just missing something but the problem with the missing script is usually you just need to do a simulink because the bootstrap is using the same file for basically everything you should have and just one simulink it will not run as route anyway I just repeat what you said to get so you said that for two, four, five and six there is only the need to create a softlink to some other already existing version yes you're right I have no idea why this is done in this way the problem is that let me say you as a user just picks the things and wants to execute the program this image builder you can just install on mostly every distribution and you don't want to get root and try to get rid of or add some new simulinks okay some advantages is speed so if you have really set up a good environment for example having an HTTP cache or package cache, RPM, Debian cache the complete build of an operating system which is done typically in two to three minutes if you don't have something like a big thing so if you concentrate on the minimal things you have one configuration for all targets and as I said it supports many, many distributions, architectures and host and target systems the next one it's really something like yes it's as seen that only limited set of functions it's testing during the CI itself so the CI in Garrett in OpenStack it's Zool and it's mostly I think all things are run on the up-to-date Ubuntu version and up-to-date Fedora version and that's mostly all like not really tested during the CI process itself and what is also in disadvantage is that currently so you can build Docker images with this but it's not really optimized for it so when you get images you can use it as Docker images but they are in size not really comparable to something like a minimal system so there are a lot of packages installed that can be removed there so there has to be some work yes to do yes this I want to really to emphasize so what to put into a system and what not this is a little bit of learning of the last some years from my side and the thing is be as general and minimal as possible for the system don't install something like applications which you just need in 10% of your machines that's not needed of course what you want is you have to install for example hardware dependent things so hardware drivers which are needed to build to boot the system but be as minimal as possible the second point is yes I learned it on hardware let me say so don't do hardening this early hardening is a steady process so hardening should be done later on because typically what you do is you have something like a general image and you don't know what you install later on in this for example you have an image and you add for example a postgres database in it where you want to harden it so if you have the image hardened the postgres isn't hardened and also you have to really to to see what you want to do with this yes and when you have to do this so the best practice I see is that you have something like a puppet or a chef or whatsoever configuration management system provided by security there are also some projects on the internet and they should run don't know each day because for example if you update a package the hardening may be overwritten and the latest point is what I already said do the disk layout during operation image build directly so this is a general rule of thumb to think as late as possible okay that's from my side I think I'm in time we have about 10 minutes question and answers time so if you have questions yes sorry I didn't get this okay the question is if there is a plan to have CFS in the file system currently there is no such a plan it's not CFS sorry CFS also no ideas sorry I don't know this project so the question was what's the difference between this project and other projects like PECA and I cannot say that much to it because I have no idea about PECA so it's hard to say yes please we are currently let me say two and a half so there is one guy called iron he's sitting in Australia so it's a little bit hard to synchronize I think there is one yes one additional woman which is something like she really writes something but she's trying to test things so this is something like yes we are only two three which is not that much yes please the target is the question is what is the target from OpenStack? the target from this image builder is it only OpenStack or can you use it as Fedora or Debian something like this this image builder is rolled out with OpenStack but you can install it on mostly any distribution so for example Ubuntu and Debian have their own packages you can just up a ticket and install I'm not really sure about Fedora but what you can do is it's also available with PiPi so you can just use pip install this image builder and you have it and you can use it it's about two minutes there is an outstanding page yes exactly so this was my idea I created this page to have exactly this inside this image builder element you can just build and we have a test or development for this image builder yes please, sorry I didn't get this no this is the question was is there some ready to use element for data mining is it correct? is there the puppet correct? there is a puppet master element for this one it installs a complete puppet master yes please the question is what about GPT the partition table you think about there is really ongoing patch I hope something like maybe next or maybe in two weeks it will be there and will be in the next release I'm not really sure if there is some time for my questions maybe you at the top I'm only use GPT just install your directory okay when I understood it correctly it's something like how does a disk image builder have different ways of storing images like raw image so okay there are currently, so internally it works in a raw so it has a dup device it has a raw image and after the process it automatically converts it to something you give at the command line QCOW, VMDK, TAR whatever you want exactly everything is ended locally yes the top the question was why does disk image builder not pick up something like an existing project for describing the partitioning the block device itself correctly open speaking I didn't find something so if you can point me to something I'm very happy this was also really so my first touch with disk image builder looked through the internet exactly for finding something which gave me the whole bunch of things yes now which can be done with disk image builder now but I didn't find anything so this was one reason to put it there okay we had this question already it's about GPT partitioning there is currently really a patch outstanding and there is a lot of work done on this and I hope it's maybe merged next week or so any questions? the question is why I recommend against partitioning? no it's not outside the disk image builder yes because it's something like very basic for the image and you won't want to change these things later on so for example I would have something like a problem with it setting up an LVM with Puppet so maybe it's possible but for my opinion this is not really the correct time so do things I'm not really sure if I get you yes you can do this also so you can do something like a partition less thing so you can just use an image raw image this is also possible and then you can just put it into an image yes one question or no? okay time is up thank you