All right folks good afternoon and welcome on back here this Wednesday June 30th end of the pay period great to see all of us live inside cybergroup Gregory who's commenting on the VTNR trade as we speak Kathleen Bonnie Ray Norman Kevin Stefan Robert. All of our students and trial members alike inside our live trading room cybergroup and alongside them all of us in social media Facebook live in YouTube actually I'll say no Facebook live today just YouTube. I don't know what's going on with StreamYard but I guess they have some issue but for all of us in YouTube welcome on back so we have Fausto's phase three course continuing today that's his live trading session going into the market close so. Where as we post our picks and make our call outs live inside our live trading room well Fausto's gonna be trading them in class later on today so for all of our gold platinum diamond C2 students you have access to that class will post the link coming up for that very shortly from now but with that in mind. Got to rip through our picks here go across the gainers and losers list really quick just to kind of build up our watch list before Fausto begins class so you know for any of the big moves that we ended up catching from earlier today I'll quickly go over them as we find them. You know number two for instance CUEN you could see all of my lines still up on the screen right now actually bear with me for a quick second because that probably looks really annoying so I'm gonna. Clear that out for the meantime but you could see at least across the day today the CUEN trade ended up building up beautifully going into the market open I don't know how much percentage wise it was up right at nine thirty. It was up enough for me to say at the market open at nine thirty I'm expecting a pullback for a stock that was up I mean more than the hundred sixty one percent it is currently up I would expect a big pullback profit taking right away at the market open and that's what exactly happens. Now the thing is is that you hope to see support build after you hope to see you know more buying for a slingshot perhaps and God bless we ended up seeing that it ended up bouncing roughly off of like seven thirty ish and held off seven fifty ultimately to make the squeeze up practically to nine above nine. But this thing has been through the spin cycle today I like to say that for a stock that's been moving up down and then back up later on today. You can't keep expecting a stock to just break out higher and higher later on once the volume dies off with that in mind so this ended up dropping off towards six eighty and bounced from there a strong level I was watching from pre market here right before the open. When it ended up making this crazy shake I ended up taking a twenty cent hit I took a twenty cent loss here I jumped in from eight fifteen it was a big level. And at the time I thought I was in the clear this thing popped up so fast and I was preparing to sell. Well the stupid thing came right back down and shook me out I got stopped out for an eighteen cent loss nineteen cent loss I think even but ended up dropping all the way down lower as you could see I stopped watching it from that point at least you know for a little while and then up until now I mean little bit after two o'clock we ended up seeing the stock begin to build a higher low move back up. So for what it's worth the C. U. N. trade it's reminiscent of M. R. I. N. it's reminiscent of the you know B. S. Q. R. trade from yesterday P. B. T. S. if I if I got that right all the stocks from this past week you know low float relatively speaking trading way more volume than what it typically does on a day to day basis is it likely to see the stock break higher I don't know if likely is the right word but I think just over the last couple of days with all these runners that we've had it's hard for me to not put this stock. On our watch list so far just more so given this move from seven you know built off seven and we had the pop popping off of seven again for just about fifty to sixty cents so for right now C. U. N. I'll definitely put back on our on our watch list. And this B. L. I. N. not as much right now as you can kind of see ended up popping after the open made the slingshot from five got halted I think like two times on the way up once twice. I don't know if this is a halt on the way down I don't think it is but as you could see though once the selling volume came in support broke took a little while but this thing dumped off quite a bit so I don't know the C. U. B. N. still has some signs of life left to it it seems in this B. L. I. not as much. All right Fausto was calling out calling out this W. E. I. stock from earlier today was more so in his. First in the morning the phase three course it called us out off the pot from one ninety essentially from there got in so I know that he did really well on this trade with most of us from the cyber group right now. Ended up making a nice rally going into the early afternoon as you could see broke above resistance roughly off of two twenty five moved up towards the high of the day two seventy five clean fifty cent move. Right now it just built a little bit of a lower high in comparison to that H. O. D. and it's on the way back down now seemingly towards two twenty five it didn't really test that price yet as support kind of bounced off two thirty here. I feel like this is more likely to break down lower at this stage if it ends up making some wacky move by the time I finish this meeting then let me know but I feel like going to move on. All right talk about tongue twister stocks for anyone that suffers from traders dyslexia like myself. Then I know that you were pulling your hair out here between B. R. Q. S. number seven on the gainers list. And B. S. Q. R. number two on the losers list I mean the same letters just jumbled up you know ever so slightly but this was the former runner from yesterday it's on the losers list today. B. R. Q. S. was more of a pre-market move I think ended up you know showing a big pop early in pre-market if not mistaken. Yeah really early ended up dumping off towards a low of the day off of one twenty ish and I don't know it was moving up just before hit the high of the day you know not the pre-market highs but you know high off the regular session roughly off of one forty seven toppled off from there so you know if it was closer to the highs at this time today or at least if it didn't dump off just like it did I don't know maybe I'd put it on our list we'll see what else we got the A. S. T. S. another you know pick from this morning ran up early in pre-market as you could see ended up popping out the gate. I would have expected the pullback so here's our pullback after and then fortunately for this trade at least you know thankfully this didn't get crushed and come all the way down it ended up making a new run from that point so rebroke above thirteen ended up running up towards a high of the day over fifteen if not mistaken like fifteen forty five year. Yeah so for right now again lower highs coiling up you know maybe it pops maybe it doesn't I'm not too interested in maybes we'll see it also got. I mean practically every pick that we call out is a maybe right we don't have a crystal ball but in terms of direction that one seemed to have been dropping off a bit more so. Little apples to orange is there a V. T. N. R. Gregory R. I hope he hit it big on this trade he was talking about this just before I was watching this earlier much earlier in the afternoon off twelve eighty I jumped in from twelve eighty I got like thirteen or twelve cents on a half size position it really wasn't much I stepped away from my desk I mean a little bit earlier waiting for this type of move and I missed it so. Ended up making the slingshot from thirteen pushed up nicely for over a dollar. Let's see if Gregory ended up getting it on this trade I know he was commenting all about this saying there is a decent sized seller thirteen forty just got taken out and it ran that was at two twenty five eastern then he said it just made a slingshot through fourteen before we started so hey Greg I hope that you're in this trade or I hope that you were in the trade and got out off off that fourteen but. Yeah given the run so far I'll at least come back to this at the end I think that we have more stocks on my proverbial side list that we do on the main watch list but I like to be picky and choose here at this point. All right any E. G. G. I don't know popped earlier looked all right but came back down rather fast so. This one looks pretty interesting it did pull back down quite a bit off that spike to the high of two forty but. H. U. S. A. I mean popped right as we started this meeting so I don't know just curious for the meantime we have class coming up so I just want to make this fast but. H. U. S. A. no news on it zero news it's a low float stock has about nine million shares in its float says Benzinga pro. Hey we don't need news to trade a stock but you'd like to have some sort of catalyst either way look to see the stock build a higher low I'm assuming off of two and we'll hopefully see it make the bounce from there. But yeah H. U. S. A. I'll put on our main list for right now. X. E. L. B. I guess I was at the highs actually I'll come back to that later on. Oh cup and making a bit of a pop not not just there I'd say here this is the bigger pop that we caught off the low of the day bounce roughly from five ended up or five twenty ish and pop right off of five seventy five here I thought it would have given us a lot more but perhaps that can come later on today. Again another stock maybe I'll come back to at the end you know just kind of cherry pickle all these stocks that are like kind of maybe is for me so far. And see which one looks like the absolute best so far really I mean out of the eighteen stocks or so I've ran through on the gainers side. The only two that I'm like really jumpy towards are the two on our list the C. U. E. N. and the you know recently popping H. U. S. A. trade. Dare from earlier today that was a nice trade but not a whole lot going on now. All right we'll keep it going across the gainers and tier folks just looking for some familiar names M. O. X. C. I saw breaking H. O. D. earlier today and. You know you can say it's at the highs right now still kind of close to there it's got such a spread out in order book so just looking at what the stock did back like two weeks ago or maybe in the beginning of June rather but ended up running all the way up from six to like twenty two twenty three that is but what goes up comes back down twice as fast that's the scare on low float stocks like the M. O. M. O. X. C. you know what I'll put it on our list for right now more as a level four to five stock for any of our more advanced students here I say this you know just full fledglingly telling you I'm probably not going to trade this myself I like to just follow stocks that you can get a better grip on right so if anyone's trying to play the game and just try and try and trade a couple shares or rather for any of our more level five students perhaps you try and jump in on this. B. B. B. Y. seems to be still fairly active right now bouncing from thirty two up to thirty three and change. End up making a big pump from earlier this is the second wind type of move that you're getting maybe it runs up a little bit more. Oh no wrong stock I'm sorry I was thinking about verb V. E. R. B. not V. E. R. V. but not a whole lot happening here either right. Check out B. T. U. fast and we'll hop over to the loser's list B. T. U. at least and as you can see still at the highs but ended up making a really nice run for us earlier today ran from roughly seven off the slingshot broke under and over that level ran up towards roughly seven eighty ish and you know they're now of course so it's a stock we are familiar with B. T. U. it's not the fastest mover but still looking really strong at this point in the afternoon here. All right jumping back to V. T. N. R. really quickly I want to give him the shout Gregory R. commented on that trade Michael picked up twenty five cents on a short but Gregory ended up getting in from thirteen thirty. Out at thirteen ninety eight really good trade from Gregory R. he says thanks to David A. one of our students live inside the trading room for that call out excellent job Gregory nice call out from David like to work together as a team there right beautiful. All right quick water break let's hop over to the loser's list though otherwise B. S. Q. R. down big from yesterday's run up for as much as it ran up when's it gonna bounce or when's it gonna drop and bounce from there so as you could see it ended up building a bit of a support little bit above five and. Fill you drop lower later on so maybe tomorrow we'll catch back in on that stock B. S. Q. R. not to be confused with B. R. Q. S. A. L. T. for as much down as this was no surprise to see a small short term you know squeeze to begin the morning here pop from like ten thirty ish ten forty ish up towards I mean just about a buck eleven fifty topped off underneath from that price and came back down pretty hard. You know what the stock actually shortable on my end at least you know if it shortable for you the stocks at the low of the day right now. I find that to be pretty interesting so you know what A. L. T. will put on our list if it could break lower but if the shorts continue to cover or rather if they you know once again cover perhaps you'll see another short term squeeze up like we had at the open. All right so either way we'll put that A. L. T. on our watch list I see it also we got just going to down the rest of the losers list here folks there's actually a lot that's down percentage wise markets pretty flat today you know barely up but. Got to say just looking at the loser side got a lot of stocks that are down like eight and a half percent or more. V. B. I. V. from yesterday it's at the lows but flat M. D. W. D. shortable but kind of flat. And that just about wraps it up folks I don't know I think that's all I got from my end. I would have put Tilray on our watch list but that is just. Watching the grass grow we had two really big spikes of volume on that trade so I'll tell you right now I'm actually in from eighteen as we speak I don't have a stop set. But I probably should be getting out pretty soon with lower highs likely to break lower but eighteen was a nice support V. Wop off seventeen eighty nine is going to be strong. I don't know this stock for as much volume as we had popped into this trade I know there is some rumor or news about the federal pop bill for July that's the reason why this got the pop. But nonetheless I don't know I feel like I'll just jump out of this trade really soon we'll keep this on our side list. All right so let me just check in really quickly on YouTube no Facebook today but on YouTube I got nothing here on the chat hopefully the stream is working on YouTube that would be a shame if I'm talking to nobody there. I think that we're all good though otherwise on the stream if there's any stocks you folks that you folks would want me to look at let me know. Actually see a bunch of us on YouTube today so outside of that for all of us live inside the trading room Michael David Brian. Bonnie let me know if there's any other stocks up down left right more than five percent you would want me to check out or look at here. I guess I said I'd come back to that VTNR at the end a few stocks that I know put on that quote unquote side list and just check them out pretty quick. VTNR given that spike you know I feel a little compelled to put this on our watch list but at the same time though if it ends up beginning to make a false pop and come back down wouldn't shock me to see this come all the way back down at 13. Yeah the CUN's already on our watch list there. All right folks I think that just about wraps things up at least I'll show my Bitcoin chart tomorrow ended up seeing a really tiny drop off very negligible if anything not a whole lot really happening. Actually if anything maybe crypto is going up right now who knows because it got right at the high of the day actually. Mara at the high of the day running right now or maybe kind of a power walk but you know I think right now at the way some of these stocks are looking actually at the end to your right. Perhaps I put this on our main watch list it's not up or down anything percentage wise but it's at the high of the day so that part interests me and it's the familiar name. David A. here at the end he's just asking hey PBTS doesn't have much room for a short does it. Technically it does technically it's got just about two dollars and seven cents. No but really though I you know perhaps two could be a nice base it's been moving so slow that's my only gripe on it David like you know to see a drop down to two that make a respectable bounce that you'd actually feel happy about taking the profit on. It's a lot to ask for given the pace of the stock is moving at right now. So come tomorrow morning I think that could be a nice play. I was looking at 240 m PBTS from earlier today and that didn't really work out too well. All right so that just about wraps it up now folks so in total we got two four six seven stocks to put on our watch list so far. Not too little not too big the shoe just fits I like to say outside of this list though if there's anything else that pops or drops makes a big move at least for all of us today. All of us live inside cybergroup you folks know that we'll to work together as a team call it out when we see it and try and capitalize at that moment for all of us on social media though if you're interested in joining our live trading room. Go right down to the link on the banner below just sign up for a quick small trial a week long trial in our inside our live trading room. You'll get to experience our call outs going into the market close today and across the next five trading days from that point. All right aside from that I look forward to speaking to all of us live inside the trading room coming on in just a little bit. I'll be back on the mic myself right around three thirty I'll talk to you then.


That was funny. The only person I see on TV is Walo. Break number 5. Jump it over, niggas. Over there, barbecue with niggas. I'm like, man, let them niggas get it all. That's one person in the world that can stop and play as Walo. He's got hope. I'm making a refugee.    Hey, you know they giving out $20 to $40.


So commercial capabilities continued. So in the in the second phase of this Bell and Morrison model where he has shown the four stages and 12 capabilities. So the second stage is divided among these 12 capabilities in such a manner that which is the seeding phase. So in the seeding phase which is more or less between one and two the entrepreneur should look for venture capital and persuade investors to support his or her idea. So without funding, without capital, no product can be developed. Now the product can be developed, now its sales and marketing can be done. So in this seeding stage this is very important that the entrepreneur look for the resources from which it can get the capital.  They look at its potential, its feasibility, the possibility of success. So there are various criteria. But one product which has not been developed yet and an all together innovative product and it is difficult to say anything about whether it works or not. And the factor of risk is more. So in the same way when the factor of risk is more, then its profitability element is also more. So those are the people which we call as venture capitalists. So those financial institutions, those organizations which fund it and initial funding and later on funding, they need to understand and present their project and stop the fund. The third which is product development phase, here the things change more or less and they lie between two and three. Now sales gains importance and marketing becomes a dominant force. Now when you are doing product development, then the market input is very important that you share your thoughts and your concept about product with the end user because there are potential buyers or the industry in which you have to make that product, so your synergy develops between your engineering and production team and your sales and marketing team. What do they want to make? What does the market want? And then the concept of entrepreneur is discussed with the end user and the market and then accordingly what possible changes can be brought into the product development stage. Then the fourth stage which is the final stage that concerns market development. It is usually between stage three and four and gives a key role to sales. Now the market development means that we have some initial customers who are adventurous, who want to use that product, and we have to increase their number because we have made products and tested products and we have to try to increase that segment of initial users and also we have to try in the next segments so that other people who are not very adventurous but we have to bring users in front of them and convince them to use the same product or process so that sales can be increased. So at this stage, development, stage of development, all attention should shift towards scaling up the business so that business can be expanded. Segment, one segment or other segments can be added and within segments we can convince more users and more buyers to use the same product.


In the Dunmah method of determining the molar mass of a volatile liquid, we will start out massing an empty 125 milliliter Erlenmeyer flask, a small piece of aluminum foil, and a small piece of copper wire. We will then add approximately 5 milliliters of the unknown liquid. We will cover the mouth of the flask with the aluminum foil. We will use the copper wire to hold the aluminum foil in place. We will place a small pinhole in the top of the aluminum foil. We immerse the flask in a beaker of boiling water. The liquid inside the Erlenmeyer starts to boil and vaporizes. As it vaporizes, it pushes air out of the pinhole. Eventually, all the liquid vaporizes and the flask is filled with just enough vapor to fill the flask at the temperature of the boiling water. Once the liquid has completely vaporized and the vapor has reached the temperature of the water bath, we will remove the flask from the water bath. The vapor inside the flask will condense to a liquid. When the flask is cooled to room temperature, the liquid that has condensed was the amount of vapor that would fill the flask at the temperature of the boiling water bath. We will now mask the flask, the liquid, the aluminum foil, and the copper wire. Since we know the mass of the empty flask, aluminum foil, and copper wire, we can get the mass of the liquid. We will determine the volume of the flask, which is also the volume which the vapor occupied at the temperature of the boiling water bath. We will remove the copper wire and the aluminum foil. We will fill the flask completely with water, and we will pour the water into a graduated cylinder. We will record the volume of the water.


Hi everyone, this is my talk on replacing extensions about me. I live in New Jersey for a long time. I lived in New York, but we moved last year. I'm the author or co-author of about 20 media wiki extensions. The number keeps growing, but my most important one is the first one I created, which is called Page Forms. I'm also the founder of WikiWorks, which has existed since 2009. That's a media wiki consulting company. And I wrote a book called Working with Media Wiki. Oh, there it is. Peter's holding it up, which is the only media wiki book that's been published as far as I know since 2010. And it came out in 2012. And I've updated it a few times since then. And I now work at a company called Genesis. Since 2017, there have been people from Genesis at previous conferences. They use media wiki. And they're trying to spread it further within the company. Yeah, so I'm still at WikiWorks, but I'm not doing day-to-day stuff there anymore. OK, we're heading right. OK, let's jump right into it. I want to talk about replacing extensions, when it makes sense to create alternatives for extensions, when it's happened before, and that whole idea. So the first case study is an extension called Flag Revs, which allows for displaying a revision other than the latest one to users. And on Wikipedia, it's known as Pending Changes. It's very complicated. It has a lot of what I think are unnecessary features. There's actually a way to review for each revision on different scales of quality, whether how good it is. And then you can have a consensus to decide what should be the revision that's shown to users. Approved Revs, I created this extension. It's the first extension I created that duplicated another extension that wasn't really doing anything new. In theory, it's very simple. There's just one approved revision per page, or at most. Whoever is an administrator can change that and set a different one to be the approved one. It's somewhat complicated, and it gets more complicated as new features get added. But I'm trying to keep the complexity manageable, and Flag Revs serves as a warning beacon or something, I guess, to make sure it doesn't get too complex. And you can see it at that URL. This might be the closest. I don't know how many people actually still use Flag Revs. This might be the closest one of my examples to a true replacement in that Flag Revs seems to have just fallen off the radar. I know some people are still using it, but it was supposed to be heavily used on Wikipedia, and it's sort of dropped off. Nuke is an interesting one. I think a lot of people still use it. Does anybody here use Nuke? OK, a few people. Yeah, OK. It lets you delete a large group of pages, and the way you do it is just say this user or this IP address is clearly a vandal. So if they just created 200 pages, then delete all of them by clicking on one button. I don't think it's that helpful. People may disagree. In my experience, spam, maybe it's changed in the last five years, but it seems to be that once spammers know about your Wiki, they're going to hit it with a lot of different newly created user accounts. It's like create account spam, create a new account spam, et cetera, every five seconds or something. And the same goes for they cycle through IP addresses also, or maybe just to get around protections like Nuke. So I don't think it's that helpful. And you can see, actually, on the Nuke Talk page, some people say, I accidentally entered the username of an actual user in Nuke. How do I get back the 500 pages I just deleted? Smitespam is an extension I oversaw during a Google Summer of Code project, I think two years ago, or I think two years ago, two and a half years ago. It doesn't go by IP address or username, although you can put those in a whitelist saying, you know, don't look at these. But basically it just looks at the text of pages. I mean, one thing that's common to a ton of media wiki spam is it doesn't actually use wiki text or very little, just enough to put in a link or something, but there's no section headers, internal links, anything else. So it's not, you know, it doesn't do neural networks or any fancy AI stuff, but even the simple algorithms it uses tend to be pretty good at identifying spam if you've just been hit by a lot of it. I don't know how much this gets used, but personally I think it's a much better option than Nuke or that kind of approach. So yeah, if you're interested in, this is really just a plug for Smitespam, but if you're interested in it, you can get it at that URL. Semantic media wiki. OK, this is probably going to be my most controversial slide, I'm sure, from more than even the one where I needlessly slagged UML yesterday. So what does it do? You guys all know this, but it's used for storage querying, browsing, and visualization of data in the wiki. It's a good extension, and I really don't want to say too much about this. I'm sort of including it here just for completeness. I personally, this is just my personal opinion, think it's a little overly complicated to install and set up data structures and query, because you have to learn a whole custom query language. And if we have time at the end, maybe this is worth discussing, maybe not. I don't know. The alternative is Cargo, an extension I was the original author for, and I'm still the main developer. It's one extension instead of up to 15 if you really use all the Semantic Media Wiki family. The big advantage is that it uses standard database tables instead of providing its own custom storage system. So that just makes a lot of things easier in the process, less code and less custom storage and querying happening. And there's the URL for it. Pony Doc, this is really another kind of trivial one, because I'm almost sure no one here has used it or heard of it. But it's used to, it's interesting in concept to let you document software and hardware. So if you have a lot of pages about different products and different versions and so forth, then you can create a hierarchy of those. And of course, if you're already using SMW or Cargo and Pageforms, then you can just have a structure just using those. But it does a few nice things, and I wish I had included a screenshot, like linking to the same documentation for different versions, that kind of thing. It's all stuff that can be done probably in a custom way, but it is convenient in some ways. I also include some access control for different products, that kind of thing. It's poorly implemented. I'm sorry if any Pony Docs developers are watching this at any point. The people who did it clearly, that's the one media-weakie extension they ever created. It is used, the reason I know about it, and I mention it is because it's used at my company, Genesis, but we're trying to move away from it. So I've created a competitor, Docs Extension, which doesn't have a name yet, but hopefully that will get released sometime this year, and start to get used to replace Pony Docs. Collection, this one is interesting. I don't know if anyone here uses it. It lets you create PDF files out of multiple Weki pages, and it was developed by a company called Wikipedia Press, I think, who make books like Travel Guides and so forth that are basically just a collection of Wikipedia articles on that subject all put together. And for a long time, it was the only PDF solution, as far as if you want to make a book or whatever else. And that was pretty much it. It's hard to set up. I don't know if anyone here has tried using it. Yeah, OK, would you agree that it's not ideal? It's hard to set up? OK. Yeah, and it has dependencies and so forth. There is an alternative just released last month, and I know about it because it was developed by WikiWorks for NATO, actually. The impetus for it was that they needed formatting that collection doesn't provide, which is not hard to do, because collection doesn't really provide any formatting. So it's called DocBook Export, and not PDF Export, because it saves it into DocBook Format, which is a standard format used for books and documents. I'm more familiar with a format called Lattec, but DocBook is simpler and I guess more popular for books and stuff like that. So what it does is it takes the HTML from a page, unless the media Wiki parts are due the Wiki text to HTML, then it uses this thing called Pan Doc, turns it into DocBook, and then turns it into PDF. And what that means is that that process allows it to do a lot of customization. You can do indexing and include figures, and of course you have a whole lot of styling options, fonts, and everything else. And I think it's pretty easy to install. I mean, you need to set up Pan Doc and these other utilities that are used for these different steps, but it seems to be, I mean, I got it working, and I still haven't been able to get a visual editor installed, so for what it's worth. Oh yeah, sorry, question. Do you use the word? Yeah, maybe I should have shown an example. Basically, there's just a parser function called, I think it's called DocBook, where you just specify these are all the Wiki pages I want in this order, and then you specify some other stuff, like use this to create the index and that kind of thing. Oh, I've just been locked out of your laptop, Brian, sorry. So anyway, so it's just a parser function, so you can just keep adding to it, and actually every time somebody goes to get the PDF at the moment anyway, it newly generates the PDF, so there's never a concern about caching or anything. There probably should be some caching, but anyway, yeah, it's easy to change. It's easier than also to do that than with collection, where you have to, there's a whole structure you have to create of books, define a book, and so forth. Yeah, that's done outside of the Wiki. I'm new to all of this stuff, so I might not be totally right, but DocBook uses something called XSL style sheets, which is sort of like CSS, but for DocBook instead of for HTML. So it comes with some built-in XSL, but you can go into the server and put in your own style sheets, XSL style sheets instead, and then it'll just work as far as I know. Yeah, oh, with collection? Oh, yeah, oh, I forgot, that's another big advantage of, I should have just made my talk about this. Yeah, as far as I know, collection uses the Wiki text in order to create the PDFs, which means parser functions in general won't work, and that's especially true with queries, SMW queries. If you wanna show a table or a map or something, it just won't, I don't know exactly what it does, it just won't show it, it just shows the, it just, yeah, it just prints the Wiki text. Yeah, that's another huge advantage of DocBook export because it takes the HTML of the Wiki page instead of the Wiki text, then what you see is what you get, that's what you get the output. Oh yeah, I'm Mark. How does this compare with what Wiki? Never heard of it, I don't know. Oh, okay, well, great, yeah, if, yeah, okay, if there's gonna be, if anybody didn't hear that question, there's a new extension coming called ElectronStack, is that an extension or what? Elect, okay. It's not called ElectronStack. Okay, oh, Electron. It's under development, it uses Electron. Oh, I see, Electron is some third-party thing. Okay, I see, but can it take multiple Wiki pages? That's the part they're working on. I see, okay, then, then, sorry. Oh, oh, is this better than the Electron thing? I don't know, I guess we'll have to see it. I'm just looking at what you're saying about, you know, yeah, that's right, yeah, that's right. I'm guessing that they have something more like collection data, which was this page. So that, you know, the UI there is a little better. Yeah, there's advantages and disadvantages to doing that. The advantage with a parser function is that anyone can change it, and you know, it's not admin-only, that kind of thing. And it's easier to make, to modify the extension, but that's not relevant. Okay, Visual Editor, speaking of Visual Editor, I just mentioned this. WizzyWig, it does WizzyWig editing of Wiki pages and it's been discussed here before. It works great, I can't, you know, some people say it's slow, it can be slow. It seems to, the speed seems to be a function of like the square of the size of the page or something. It's like, I guess, exponentially slower as the page gets bigger, as far as I can tell. So it's, but the main problem I see with it is just that it's hard to install it. And again, I've never been able to install it. And it requires parsoid, I don't know, that's misspelled. And, yeah, I mean, that's the thing. And it doesn't work with page forms, although that is going to change in the next few months. I'm pretty sure. But still, that installation is a real problem, in my opinion. So, this is very new. This just came out a week ago, although it's been in the works for a long time, for over a year. Mostly developed by another guy, I don't know if I should mention his name, although it's there on the Wiki page. A guy named Duncan Crane in England, whom I've been in close contact with. And so I've helped out to some extent. It's not a replacement in that it will never be as good at editing Wiki pages with all the edge cases and so forth as visual editor, but it's just incredibly easy to install compared to visual editor. It's just JavaScript, you just install it and it works. And it works, oh, the slide doesn't actually say that, but it does work in page forms already. And there's the URL and here's a little screenshot of the output, which is basically exactly what you'd expect from a WYSIWYG editor. That's it, yeah, good. I don't know actually what would happen if you tried using them together. Each one of them creates a new tab. So in theory, you could have three editing tabs for a single page. Yeah, yeah, yeah, sorry. So if it was strict, then... Yes, you can do that. Can you do that? Because that seems like it would be useful that way, you know? Well, the way it works is pages that are form editable will just have the edit with form tab. And there, within the form, you can specify for each text area, I want tiny mce here, et cetera. Pages that are not form editable will get the separate tiny mce editing tab. And what I'm saying is, if a page is form editable, you won't see that tab, so it's always off. Oh, I see, pages that aren't form editable. I'm not sure actually. I see what you're saying. I'm not sure, but it should be easy to add that setting if it's not there. Right, right, yeah, yeah, that is an option. Although if you already have visual editor installed, then if and when visual editor support comes in for page forms, then you might as well use it for everything. Sure, but I'm looking for a quick page. Okay, well, all right. All right, here's an interesting one. I think this is my last one. An extension called flow until what, two months ago or something, and then they decided to change it to structured discussions. It offers a structured layout of talk pages. So instead of a talk page, this is the top page for the main homepage on mediawiki.org, there's tabbing and all that stuff. You can see there, I don't know if you can see the search interface, but yeah, there's just a bunch of things, features there. And notice that it's a relatively small column inside the overall page, and there's a big sidebar that's reserved for just description and stuff like that. Oh, okay. I think personally it's as clunky as its new name. I don't know if there's anyone here who's involved in the name change, but that's just horrible. I mean, I can't imagine anyone saying structured discussions over and over when talking about this extension. I like flow. I think flow is a great. Oh, I see flow, not flow in quotes, not the name, but the thing. I don't know. I like the name. It grew on me. Yeah, no, no, no, yeah. Echo and flow sort of came together. I don't know. I like the whole, the sound of it. Maybe, yeah, maybe it sounds better to me now after seeing the alternative. Yeah, I mean, it's very hard. I'm certainly not the only person who's said this. It's very hard to follow long discussions on it because it's, in large part, because it has big fonts, lots of white space, and has this thing, infinite scrolling, which I was never a fan of, even though it's become really popular on the web. Yeah, and there was a plan to implement it on Wikipedia and there was a big user revolt and that's not something new, but with new extensions. But anyway, if other people have different opinions on flow-structured discussions, I'd be glad to hear them. This is just my personal opinion again. Yeah. I like the integration of that here. I like the way the support dance works. Yeah, yeah, yeah, yeah. Extensions that integrate with Echo are great. I don't really... Yeah, sure. Yeah, notifications are great. It would be good if more extensions integrated with Echo. Yeah, it just, infinite scrolling just makes it, I think it's hard. It makes it hard to find anything that was a year ago or something. Right, right, right. So this is the one use case that I wasn't involved in developing in any way, but there's an extension developed at MITRE called Comment Streams, which I think is better. It's more configurable, it's less intrusive. Yeah, it works more like the Facebook style comments that you see at the bottom of pages, sometimes, of Wiki pages sometimes. And you can, in fact, include it. The bottom page is not just in the talk page. And there's the URL for it. Sorry? And it's integrated with Echo. Okay. But... It's soon visual editor, hopefully. Sorry? It's soon visual editor. Oh, and soon Comment Streams will be integrated with visual editor. Yeah, and yeah, stick around for Friday afternoon if you wanna see something more about that. So yeah, I mean, these are just disparate examples. I've tried to find a thesis behind this whole thing. The question is, for anyone who is thinking about creating an extension or hiring someone or telling someone, asking their employees to create an extension or something, the question is, when is creating an alternative justified? When should you bother if there already is an extension that nominally does what you want it to do? Often, it's when the current solution is too complicated. So yeah, well, for three of these seven cases, the alternative extension does less, not more. Often, I think that's the way to go is simplifying things versus adding more features. Four of these are maintained by the Wikimedia Foundation for what it's worth. That may just be more a function that their extensions are always the standard to go by. Let's see, are there any other? This is sort of an open question. Are there other candidates for replacement? And actually thinking about this made me think about flow again, besides this should really be another possible alternative to flow slash structured discussion slash comment streams. And this is really just an open question, just something I've been thinking about. A lot of the point of these is that it's just hard for users to learn the syntax. You have to figure out how to indent it to exactly the right number of spots, and then you have to put in the four tildes to make your signature. So this is just a random mock-up I put together. This is from the Wikimedia Talk page on Houston. And the idea is you just have a little bit of JavaScript. It says, you can't even read that. It says, add reply here. You just a little bit of JavaScript that puts in arrows. And so you can click on any of those and it would pop up a window that just lets you put in your wiki text, and it'll take care of the signature and the indenting and everything. Just signature and indenting, I guess. And it might validate your wiki text. So yeah, it's just something to think about. I don't know if anyone has any thoughts on that. Of course, there's always a need for it to have a true commenting system, but this could potentially be a lightweight approach to that same thing, especially if you already have a lot of content in talk pages and you just want to make things easier for your users. And is that it? Yeah, I think so. That's it. Any questions, comments, but I guess PDF Explorer was the big issue with anything. Yeah. Yeah, man. Oh yeah, microphones. Yoan, thanks for that. In terms of semantic media wiki and the forms and the cargo. Yeah. I mean, is there a way of combining the both of them rather than these sort of two separate extensions? Is there, it just seems a shame that we've got the, they're not competing, but it seems a shame we've got these two extensions that seem to be sort of doing some of the same job for each other. Yeah. The question is just semantic media wiki and cargo. Can they just be friends or something? I mean, there are what I would say is, there are cases of people using the two of them together and you certainly can use the two, not together, but on the same wiki and people have done that. They can't really work together. They each have their own storage system and they can't read each other's data. So that's pretty much it. But certainly cargo, I mean, yeah, I mean cargo is basically just the look and feel of it was pretty much stolen from semantic media wiki. I mean, I just copied all of that. So it's not, I don't see it as, I don't know where that's going really, but it's not, I'm not trying to reinvent the wheel. I guess I did reinvent the wheel, I don't know. It's another thing. Okay. I guess all the main questions were about PDF export. Yeah. I agree with you about flow in terms of a light-rate JavaScript thing with reply buttons to hide the syntax sugar over the indentation thing, basically. Sounds like a great idea to me. I've kind of thought of similar things at times too, like it just seems like a very nice in-between of old talk pages versus full-on flow or liquid threads or whatever. I don't know, people should make it. Cool. Yeah, that's really good to hear. That's interesting. Yeah. So I was wondering about the doc book export because I wrote the HTML to wiki export using Pandoc as well. So I don't know if you know anything about the HTML to wiki extension, but I was curious, when I saw Pandoc and all the formats that it converts, I was thinking about making an extension that has a universal format converter and importing. Yeah, Pandoc is incredible and it seems almost wasteful to just use one little part of it. It even actually does wiki text. It does anything to anything, like any of these four things you can convert to one another using Pandoc, as far as I know. Yeah, yeah, yeah. The feasibility is there, right? Right, yeah, it would be great to see. Swiss Army knife of... Sure, yeah, yeah, absolutely. By the way, I didn't really explain it, but it's an open source utility that you can just download it. You said it converts from any... Does it convert from PDF to wiki text? I don't know, I don't know, but I wouldn't be surprised. No, I don't think so. Okay, well, because why? Because if it can go from PDF to something that's just text-based, it can do wiki text. I don't know, maybe someone should look it up, but I can't imagine it would work that well, but that's a whole separate question. Probably, I don't know, tables would get lost and all this stuff like that. Oh, yeah, sure, yeah, yeah. PDF is... Yeah, but yeah, but back to that question while Cindy gets the mic. Yeah, I think it would be great to have more extensions or maybe just a Pandoc extension that really opens all this functionality. We did have an issue once at MITRE where we needed to generate a wiki from a Word document and we had somebody who wrote a bunch of scripts using Pandoc that converted from a Word document to wiki text, so it's theoretically, at least. Yeah, that's good. Pandoc gives an example on their page of... From Pandoc? Yeah. Oh, Pandoc. I don't know from PDF, sorry, from PDF to later. Yeah, okay. So maybe. It's, we're half the way there or 80% of the way there, so. Right, yeah, well, then Word to wiki text, so that's probably, yeah, that's probably something. Pandoc, it was Pandoc. It was Scripts to Invoke Pandoc. What I'm saying is it wasn't an extension but there's no reason that if it's possible from Scripts that it couldn't be packaged as an extension. And the cool thing was is that it actually took all of the images and uploaded them as files, too. Okay, thank you.


Hi everyone, welcome to theCUBE's presentation of the AWS startup showcase, open cloud innovations. This is season two, episode one of the ongoing series covering the exciting startups from AWS ecosystems. Today, episode one theme is the open source community and open cloud innovations. John Furrier, your host. We've got two great guests, Webb Brown, CEO of KubeCost, and that's the Lynn Head of Business Development at KubeCost. Gentlemen, thanks for coming on theCUBE for the showcase AWS startups. Thanks for having us, John. Great to be back. Really excited for the discussion. Webb, great to see you theCUBE alumni from many, many KubeCost go.  So first of all, we know one thing for sure. Kubernetes is the hottest thing going on because of all the benefits. So take us through you guys macro view of this market. Kubernetes is growing. What's going on with the company? What is your company's role? Yeah, so we've definitely seen this growth first hand with our customers in addition to the broader market. And I think we believe that that's really indicative of the value that Kubernetes provides, right? And a lot of that is just faster time to market, more scalability, improved agility for developer teams. And there's even more there, but it's a really exciting time for our company and also for the broader cloud native community. So what that means for our company is, we're scaling up quickly to meet our users and support our users. Every metric at our company has grown about four X over the last year, including our team. And the reason that one is the most important is just because the more folks and the larger that our company is, the better that we can support our users and help them monitor and reduce those costs, which ultimately makes Kubernetes easier to use for customers and users out there on the market. Okay, so I want to get into why Kubernetes is costing so much, obviously the growth is there. But before we get there, what is the background? What's the origination story? Where did Kube cost come from? Obviously, you guys have a great name, cost, Kube. You guys probably reduced cost in Kubernetes, great name. But what's the origination story? How'd you guys get here? What itch are you scratching? What problem are you solving? So yeah, John, you guessed it. Oftentimes the name is a dead giveaway there where we're cost monitoring, cost management solutions for Kubernetes and cloud native. And backstory here is our founding team was at Google before starting the company. We were working on infrastructure monitoring, both on internal infrastructure as well as Google Cloud. We had a handful of our teammates join the Kubernetes effort, early days. And we saw a lot of teams struggling with the problems we're solving. We were solving internally at Google and we're solving today. And to speak to those problems a little bit, you touched on how just scale alone is making this come to the forefront, right? There's now many billions of dollars being spent on Kube. That is bringing this issue to make it a business critical question that is being asked in lots of organizations. That combined with the dynamic nature and complexity of Kubernetes makes it really hard to manage costs when you scale across a very large organization. So teams turned to Kube cost today, thousands of them do to get monitoring in place, including alerts, recurring reports, and dynamic management insights are on the nation. Yeah, I know, we talked about KubeCon before, web. And I want to come back to the problem statement because when you have these emerging growth areas that are really relevant and enabling technologies, you move to the next point of failure. So you're scaling, there's abstraction layers, now services are being turned on, more and more Kubernetes clusters are out there. So I have to ask you, what is the main cost driver problem that's happening in the Kube space that you guys are addressing? Is it just sheer volume? Is it different classes of services? Is it like different things are kind of working together? Different monitoring tools? Is it not a platform? Take us through the problem area. What do you guys see this happening? Yeah, the number one problem area is still actually what the CNTF FinOps survey highlighted earlier this year, which is that approximately two thirds of companies still don't have kind of baseline visibility in to spend when they moved to Kubernetes. So, even if you had a really complex, charge back program in place when you were building all your applications on VMs, you moved to Kubernetes and most teams, again, can't answer these really simple questions. So we're able to give them that visibility in real time so they can start breaking these problems down. They can start to see that, okay, it's these deployments or staple sets that are driving our costs or no, it's actually these workloads that are talking to S3 buckets and really driving egress costs. So it's really about first and foremost, just getting the visibility, getting the eyes and ears. We're able to give that to teams in real time at the largest scale Kubernetes clusters in the world. And again, most teams when they first start working with us don't have that visibility, not having that visibility can have a whole bunch of downstream impacts, including kind of not getting cost right, performance right, et cetera. Well, let's get into that downstream benefit, problems and or situations. But the first question I have just throw a naysayer comment at you, would be like, oh yeah, I have all this cost monitoring stuff already. What's different about Kubernetes? Why, what's the problem? Are my other tools going to work for me? How do you answer that one? Yeah, so I think first and foremost, containers are very dynamic, right? They're often complex, often transient and consume variable cluster resources. And so as much as this enables teams to construct powerful solutions, the associated costs and actually tracking those different variables can be really difficult. And so that's why we see why a solution like Kube cost that's purpose built for developers using Kubernetes is really necessary because some of those older, traditional cloud cost optimization tools are just not as fit for this space specifically. Yeah, I think that's exactly right, Alex. And I would add to that just the way that software is being architected, deployed and managed is fundamentally changing with Kubernetes, right? It is deeply impacting every part of software delivery process. And through that, decisions are getting made and engineers are ultimately being empowered to make more cost impacting decisions. And so we've seen organizations that get real time kind of built for Kubernetes or built for cloud native benefit from that massively throughout their culture, cost performance, et cetera. Well, can you just give a quick example because I think that's a great point. The architectures are shifting, they're changing. There's new things coming in. So it's not like you can use an old tool and just retrofit it. That's sometimes that's awkward. What specific things you see changing with Kubernetes that environments are leveraging, that's good. Yeah, one would be all of these Kubernetes primitives or concepts that didn't exist before, right? So I'm not managing just a generic workload. I'm managing a staple set and or three replica sets, right? And so having a language that is very much tailored towards all of these Kubernetes concepts, abstractions, et cetera. But then secondly, it was like, we're seeing this very obvious push towards microservices where typically again, you're shipping faster. Teams are making more distributed or decentralized decisions where there's not one single point where you can kind of gate check everything. And that's a great thing for innovation, right? We can move much faster. But for some teams, not using a tool like KubeCost, that means sacrificing, having a safety net in place, right? Or guardrails in place to really help manage and monitor this. And I would just say lastly, a solution like KubeCost because it's built for Kubernetes sits in your infrastructure. It can be deployed with a single home install. You don't have to share any data remotely, but because it's listening to your infrastructure, it can give you data in real time, right? And so we're moving from this world where you can make real time automated decisions or manual decisions, as opposed to waiting for a bill, a day, two days or a week later, when it may be already quote too late to avoid these. You're fired by the end. Or he got the extra cost. And nobody wants that. And he got to fight for a refund. Oh yeah, I threw a switch or wasn't paying attention or human or code because a lot of automation is going on. So I can see that as a benefit. I got to ask the question on developer uptake because you mentioned a good point that's another key modern dynamic. Developers are in the moment making decisions on security, on policy, things to do in the CICD pipeline. So if I'm a developer, how do I engage with KubeCost? Can I just download something? Is it easy? How is the onboarding process for your customers? Yeah, great question. So first and foremost, I think this gets to the roots of our company and the roots of KubeCost, which is born in open source, everything we do is built on top of open source. So the answer is you can go out and install it in minutes like thousands of other teams have. It is the recommended route or preferred route on our side is a helm install. Again, you don't have to share any data remotely. You can truly lock down namespace egress, for example, on the KubeCost namespace. And yeah, in minutes you'll have this visibility and can start to see really interesting metrics. And again, most teams when we start working with them either didn't have them in place at all or they had a really rough estimate based on maybe even a KubeCost Grafana dashboard that they installed. How does KubeCost provide the visibility across the environment? How do you guys actually make it work? Yeah, so we sit in your infrastructure. We have integrations with, for on-prem, like custom pricing sheets with cloud providers will integrate with your actual billing data so that we can listen for events in your infrastructure say like a new node coming up or a new pod being scheduled, et cetera. We take that information, join with your billing data whether it's on-prem or in one of the big three cloud providers and then again, we can in real time tell you the cost of any dimension of your infrastructure, whether it's one of the backing virtual assets you're using or one of the application dimensions like a label or annotation, namespace, pod, container, you name it. Awesome, Alex, what's your take on the landscape with the customers as they look at cost reductions? I mean, everyone loves cost reductions. Certainly I love the safety net comment that Webb made, but at the end of the day, Kubernetes is not so much a cost driver. It's more of a, I want the modern apps faster, right? So, so people who are buying Kubernetes usually aren't price sensitive, but they also don't want to get gouged either on mistakes. Where is the customer path here around Kubernetes cost management, reduction and scale? Yeah, so I think one thing that we're looking forward to here in this upcoming year, just like we did last year is continuing to work with the various tools that customers are already using and meeting those customers where they are. So some examples of that are working with like CI CD tools out there, like we have a great integration with Armoury and Spinnaker to help customers actually take the insights from Kube cost and deploy those in a more efficient manner. We're also working with a lot of partners like Grafana to help customers visualize our data and integrate with D2IQ or Rancher, which are management platforms for Kubernetes and all of that I think is just to make cost come more to the forefront of the conversation when folks are using Kubernetes and provide that data to customers in all the various tools that they're using across the ecosystem. So I think we really want to surface this and make cost more of a first class citizen across the ecosystem and the community partners. What's your strategy at the biz dev side? As you guys look at a growing ecosystem with KubeCon, CNCF, you mentioned that earlier. The community is growing, it's always been growing fast. The number of people entering in are amazing, but now that we start going, the S-curves kicking in, integration and interoperability and openness is always a key part of company success. What's KubeCost's vision on how you're going to do biz dev going forward? Absolutely, so our product's open source, that is deeply important to our company. We're always going to continue to drive innovation on our open source product. As Webb mentioned, we have thousands of teams that are using our product and most of that is actually on the free, but something that we want to make sure continues to be available for the community and continue to bring that development for the community. And so I think a part of that is making sure that we're working with folks, not just on the commercial side, but also those open source types of products. So for FANA's open source, Binnaker's open source, I think a lot of the biz dev strategies just sticking to our roots and make sure that we continue to drive a strong open source presence and product for our community of users. Keep that DNA and open source and keep it stable. Webb, I got to ask you, obviously the wave is here, I always joke going back, I remember when the word Kubernetes was just kicked around pre-open stack days, many, many years ago, it's the luxury of being old cube guy that I am 11 years doing the cube, all fun. But we remember talking earlier in the early days is that with Kubernetes, if it worked, the phrase was rising tide floats all boats. I would say right now, the tides rising pretty well right now. You guys are in a good spot with the cube cost. Are there areas that you see coming where cost monitoring is going to expand more? Where do you see the Kubernetes, what's the aperture if you will of the cost monitoring space that you're in that you think you can address? John, I think you're exactly right. This tide has risen and it just keeps rising, right? Like the sheer number of organizations we see using Kubernetes at massive scale is just mind-blowing at this point. What we see is this really natural pattern for teams to start using a solution like cube cost, start with again, either limited or no visibility, get that visibility in place and then really develop an action plan from there. And that could again be different governance solutions like alerts or management reports or engineering team reports, et cetera. But it's really about phase two of taking that information and really starting to do something with it, right? We are seeing and expect to see more teams turn to an increasing amount of automation to do that. But ultimately that is very much after you get this baseline, highly accurate visibility that you feel very comfortable making potentially critical, you know, very critical related to reliability performance decisions within your infrastructure. Yeah, I think getting it right is key. You mentioned baseline. Let me ask you a quick follow-up on that. How fast can companies get there? When you say baseline, there's probably levels of baseline. Obviously all environments are different. No, not all ones the same. But what's just anecdotally you see as that baseline? How fast do people get there? Is there a certain minimum viable configuration or architecture? Just take us through your thoughts on that. Yeah, great question. It definitely depends on organizational complexity and you know, can depend on application complexity as well, but I would say most importantly is the array of cost centers, departments, complexity across the org as opposed to technological. So I would say for less complex organizations, we've seen it happen in hours or a day less, et cetera because it's one or two or smaller engineering teams they can share that visibility really quickly and they may be familiar with Kubernetes and they just quote, get it right away. For larger organizations, we've seen it take kind of up to 90 days where it's really about infusing this kind of into their DNA when again, there may not have been visibility or transparency here before. Again, I think the bulk of the time there is really about kind of the cultural element and kind of awareness building and just buy in throughout the organization. Awesome, well guys got a great product, congratulations. Final question for both of you. It's early days in Kubernetes, even though the tide is rising, keeps rising, more boats are coming in, harbor's getting bigger, whatever metaphor you want to use, it's really going great. You guys are seeing customer adoption, we're seeing cloud native. I was talking with my friends at Docker, the container side's going crazy as well. Everything's going great in cloud native. What's the vision on the innovation? How do you guys continue to push the envelope on value in open source and in the commercial area? What's the vision? Yeah, I think there's many areas here and I know Alex will have more to add here, but one area that I know is relevant to his world is just more really interesting integrations, right? So he mentioned Kube costs insights, powering decisions and say Spinnaker, right? I think more and more of this tool chain really coming together and really seeing the benefits of all this interoperability, right? So that I think combined with just more and more intelligence and automation being deployed. Again, that's only after the fact that teams are really comfortable with his decisions and the information and the decisions that are being made. But I think that increasingly we see the community again being ready to leverage this information in really powerful ways. Just because as team scale, there's just a lot to manage and so a team leveraging automation can supercharge them in really impactful ways. Awesome, great integrations, Alex, expand on that. A whole different kind of set of business development integrations when you have lots of tool chains, lots of platforms and tools kind of coming together, sharing data, working together, automating together. Oh yeah, so I think it's going to be super important to keep a pulse on the new tools, right? Make sure that we're on the forefront of what customers are using and just continue to meet them where they are. And a lot of that honestly is working with AWS too, right? Like they have great services in EKS and managed for Meteos. So we want to make sure that we continue to work with that team and support their services as they launch as well. Great stuff. I got a couple of minutes left. I thought I'll throw one more question in there since I got two great experts here. Just a little bit change of pace, more of an industry question. That's really no wrong answer, but I'd love to get your reaction to the SaaS conversation. Cloud has changed what used to be SaaS. SaaS was, oh yeah, surface of service. Now that you have all these kinds of new kinds of integrations, you have automation, horizontally scalable cloud and Edge. You now have vertical machine learning, data-driven insights. A lot of things in the stack are changing. So the question is, what's the new SaaS look like? Is it the same as the old SaaS or is it a new kind of refactoring of what SaaS is? What's your take on this? Yeah, it's a web. Please jump in here wherever. But in my view, it's a spectrum, right? There's customers that are on both ends of this. Some customers just want a fully hosted, fully managed product that want to benefit from the luxury of not having to do any sort of infrastructure management or patching or anything like that. And they just want to consume and create products. On the other hand, there's other customers that have more highly-regulated industries or security requirements, and they're going to need things to deploy in their environment. Right now, KubeCost is self-hosted, but I think in the future, we want to make sure that we have versions of our product available for customers across that entire spectrum so that if somebody wants the benefit of just not having to manage anything, they can use a fully self-hosted set or a fully multi-tenant managed SaaS or other customers can use a self-hosted product. And then there's going to be customers that are in the middle, right? Where there's certain components that are okay to be SaaS or hosted elsewhere, but then there's going to be components that are really important to keep in their own environment. So I think it's really across the board and it's going to depend customer to customer, but it's important to make sure we have options for all of them. Great, guys. Web, SaaS, same as the old SaaS, what's the SaaS playbook now? Gosh, I think it is such a deep and interesting question and one that it's going to touch so many aspects of software and our lives. I predict that we'll continue to see this tension or real trade-offs across on the one hand convenience and then on the other hand, security, privacy and control. And I think, like Alex mentioned, different organizations are going to make different decisions here based on kind of their relative trade-offs. I think it's going to be of epic proportions. And I think we'll look back on this period and just say that, this was one of the foundational questions of how to get this right. We ultimately view it as like, again, we want to offer choice and make every choice be great, but let our users pick the right one given their profile on those trade-offs in those areas. I think it's a great common choice. And also you've got now dimensions of implementations. Multi-tenant, custom, regulated, secure, I want to have all these controls. It's great, no one SaaS rules the world, so to speak. So it's, again, great dynamic, but ultimately, if you want to leverage the data, is it horizontally addressable? Multi-tenant, again, this is a whole nother ball game. We're watching this closely and you guys are in the middle of it with cube cost, as you guys are creating that baseline for customers. Congratulations, great to see you, Web. Thanks for coming on, appreciate it. Thank you so much for having us again. Okay, great conversation. AWS startup showcase, open cloud innovators here. Open source is driving a lot of value as it goes commercial, going the next generation. This is season two, episode one of the AWS startup series with theCUBE. Thanks for watching.


Nothing good or productive comes out of that, and in fact, it'll keep you stagnant or moving backwards. Think about it. If you have negative emotions directed at yourself or someone else, it isn't hurting anyone but you. If you're feeling resentment or anger or whatever towards someone else, is that really affecting them? No, probably not. But is it affecting you? Oh yeah.


The third book of our cable to let go of the screen is set up just like second right to the action. It's called a... Build Level Sensitive Light, basically.


cognizant of the public's interest and concern regarding the state of affairs on the St. Jude Hospital Reconstruction Project. Prime Minister Hon. Philip J. Pierre, during a September 24 town hall meeting in New York, has provided more insight on his decision to resume construction on the buildings situated on the original construction site, Phase 1. Upon assuming office last July, Hon. Pierre requested a status report from the Ministry of Economic Development on Phase 2. Phase 2, or a new construction site, was erected near the original construction site between 2019 and 2020. Nearly three years after construction on Phase 1, the original construction site was abandoned. Hon. Pierre confirmed the Economic Development Ministry's report does not recommend proceeding with Phase 2. Given the logistical challenges of finishing the construction of the top floor of the facility, while the ground floor operates as a functional hospital, it is considered that the pursuit of the ground floor approach may not be the most prudent. An independent committee appointed last August was tasked with assessing both phases 1 and 2 of the St. Jude Hospital Construction Project. The committee's report concluded construction on Phase 1 could have been completed as early as 2017. We formed the committee to look at both of the things. The committee had absolutely no gain in anything. And listen to what the committee said. It is evident from the financing that was secured and accessible up to August 2016. The level of construction of the St. Jude Hospital Phase 1, the procurement schedule, and the planned delivery of outstanding materials, the availability on Island, on FF&E, and services already paid for in full. The schedule commissioning of the facility by September 2017 was achievable. Further. Further. The committee said currently there is no program for completion of any part of Phase 2. That's the box. To facilitate the transfer of the operations of St. Jude Hospital from the stadium into part or any lower level of Phase 2. The ill-advised decision to stop construction on the original St. Jude Hospital construction site, which was nearly 80% completed in 2016, has to date cost St. Lucia taxpayers more than $115 million. Prime Minister Pierre has honored his commitment to St. Lucia to action the most prudent, safest, and immediate option to deliver the St. Jude Hospital. Guided by the recommendations in official reports from two technical reviews, Honourable Pierre has announced construction on the original St. Jude Hospital construction site will resume in November.


The Shostra-Sutherland-Lattice-Band II ZNS-5 exhibits a 2q antiferromagnetic order below Tn equals 2.9k, as determined by single crystal neutron diffraction. This order can be explained by the orthogonal arrangement of local is-ing nd spins, which were identified by polarized neutrons. When a magnetic field is applied along 1-10, two magnetic sublattices corresponding to the propagation vectors q1 backslash u2009 equals backslash u2009, one-half, one-half, zero, and q2 backslash u2009 equals backslash u2009, minus one-half, one-half, zero, are revealed. The first sublattice displays a nil-type arrangement in each single layer, while the second sublattice is suppressed at a critical field hc1.7t. The hc varies with temperature and is manifested in the ht-phase diagram constructed by measuring the magnetization in band II ZNS-5. This article was authored by Madeleine Marshall, Brianna R. Billingsley, Xiaojian Bai, and others. We are article.tv, links in the description below.


One thing I like a lot about FECON is that it's a really high energy place and you can meet a lot of different people. There's a lot of young people here and a lot of people who are very passionate. A friend I met at a youth conference in Egypt told me about FECON and when I searched it up on the internet I found it was about economic freedom and I was definitely interested. I went last year and I loved it last year. First out of the gate, this was an amazing conference. I'm a community organizer and I realized that ideas really wouldn't change the world unless we organize people and communities really feed on fun and a sense of belonging and ideas are important too but the thing about FECON is that it's freaking fun. I'm very excited about hearing Tina Guo perform. She's amazing. I was really excited about the opportunity to speak and perform here at FECON because I think it is an amazing convention and I'm personally very, very passionate about entrepreneurship as a musician but also outside of that in every other way. The presentations have been great, everything I've gone to but then walking around the exhibition hall and talking with people in smaller kind of ad hoc groups has just been great.  Different people come from different parts of different industries you know we all have different backgrounds but we're all coming together because we have a lot of the same values and a lot of the same interests and we're all so hungry to learn and to connect and to make the world a better place. I love the spirit of FECON, it's not about orthodoxy, it's not about being doctrinaire it's actually very human and very humane. I'm honored to sponsor FECON especially in its second year because it is growing by leaps and bounds. I love the fact that FECON is trying to build a community. They're using technology, they're using ideas, they're using language, they're using storytelling. The reason that I'm here is I think FECON is one of the groups that is getting it right and I want to be part of it.


Michael Williams a continuous lean great to see you got one question for you. What is the most important rule of men's style? The most important rule of men's style. I'm glad you asked this question Is that there are no rules and I think that you see that at pity here in Florence? Everyone's sort of following like what inspires them and so I think you know let go of the all of the constraints I think people have and just feel free to express yourself and dig into what makes you feel Like the best version of yourself. That's awesome. Thank you so much


Hello, my name is Lise from ST Microelectronics, and today I'd like to tell you about our YouTube channel. You can find us easily on YouTube if you search for ST Microelectronics. Don't forget to subscribe to this channel by clicking here. You can see that we have a number of different playlists, each corresponding to a key theme or product group for ST Microelectronics. We would like to help you, our customer, learn how to easily use our products, and keep you informed when we have great new products out on the market. To do this, we have organized our videos in categories like events, learning, product demonstrations, and so on. For example, you can check out our sensor tile and blue coin demos, our ST25 product demos, our microcontrollers, and visit the events we have attended like Embedded World, APEC, Maker Faire, etc. Did you know you can find a community of more than 60,000 people at community.st.com? If you have technical questions, want to learn more, or share what you are doing with ST products, this is really the place to go. Discuss and collaborate with your peers. Get help from both ST employees and other community members, and get inspired by other projects. And because we know that our YouTube community are always looking for tutorials to explain how to use our products, including our wide range of microcontrollers within our development environment, we would like to give you a quick pointer to our education website. This is the place to learn about our wide range of products. We also have a blog that has loads of interesting articles describing our products and applications. It is at blog.st.com. Thank you very much for watching our video. For more detailed information about our products, please do visit st.com. You will find application notes, product descriptions, the latest software releases, and much more. Come and see us on LinkedIn, Facebook, Twitter, and Google Plus to see all of the updates we are making on our products and for our events. Thank you.


I came back after the break, you hear correctly right if you want something to hear about Cloud Foundry. I see a little change of the people here sitting, some are the same, some are others. Now I'm talking a second time about our service broker framework. There was another talk today at two o'clock, which has a little different kind of focus. Some slides are the same at the beginning and then we're switching over to another theme because we start at the same idea from this thing. My name is Christian Brinker, I'm from Iwala, we're a cloud consulting, cloud software company from Germany, Cloud Foundry is a server member and my colleague Sebastian is ill at home, I hope he gets well. And what we are talking about, what I'm talking about now is about how to provide access to services which are brought to you by a service broker using a trick with the APROX and floating IPs. What's the problem? Here, the ones who were here at the other session, you already know this slide with Bob. Bob has this cool application and Bob wants to put his application on Cloud Foundry. Who in the room did not use Cloud Foundry already or doesn't have a clue? So we can skip the next slides perfectly. If you're interested in Cloud Foundry and so on, you can go back in the video from the first talk or one of the others here today. So Bob wants this database, access and he gets it with a service broker. We have heard something about the Brooklyn service broker, we heard something about our service broker framework today. But the service here, this database, he works on it with his application and then he runs into some failure, he don't have a clue. So he wants some access to it on some way to directly debug some errors here. But that's not only going through databases maybe for all that things here on the right he's using. So if you recall, we have our cloud application on Cloud Foundry, we have our service and it's put there on some services, we have this life cycle ongoing between our user, Cloud Foundry, the service broker and its back end like Brooklyn or like Heat or whatever. So we have this different kind of services, managed services, user provided, bindable, not bindable, router services, syslog drains, volume services. And they all have the same interaction. So you create a service broker, the catalog got fetched, you can get it accessible in the marketplace then you create your service instance and it's there and then the interesting point is you create service bindings for the access. So you get credentials back from the service broker to the Cloud Foundry controller and the application. But that's for the application, it's in the application environment. If you delete that application, that information is gone. So you have no possibility to access the database because the access is binded to the application and that's only in the network of the application, we see that later on. One little advertisement, we are having a framework for this cool stuff here implementing the whole workflow here. It's developed in Java, I've talked about a little bit in the other slot. The blue things are the implemented of the framework and the rest you can exchange. Some configuration stuff by that here. We want to access our service, that's called in Cloud Foundry the service key management. So Bob has his service and he wants directly access. The old workflow that doesn't work. So the change is here that Bob is the one who's getting the access. The exchange for Bob is two other commands in the CFC Ally. So instead of creating a service binding, he creates a service key which he can address a name to which is intensely the same as he has a service binding, it's the same object, it's the same credentials, but the use case is a little bit different because instead of the application being in the private network where the host and the Cloud Foundry environment is and so on, Bob isn't in that private network. So if Bob wants direct access to the service instance, it has to be in the internet accessible, which isn't that cool stuff. So what you really want to do is the workflow here is the same like here, only a little bit different because Bob is going into the Cloud Foundry, you get to the service instance created, you get your service binding information from here, it goes, it's got back the information that the user and so on has created with IP address and so on, got back to the Cloud Foundry and from there on to Bob provided. And then Bob gets direct access, but the service instance is in the internet. So what do you want is this, the service instance is encapsulated in your private network and the service broker isn't the private network, no one can access both from outside from the internet and Bob has only has some interaction with it, but somehow he has to access the database. And that's when we got this little change here. Looks at the first place looks a little bit much, I hope you can read it, I see the writing is a little bit small from behind, from there behind. We have several components here and the first thing is we put an HAProxy into the internet because that's something well known, many people can have knowledge about the configuration of it and you can use it for scaling things, you can use it for high availability, you can make sanity checks and so on, but the problem with the HAProxy here is how does the service broker communicate with it? How can he reconfigure it? So we do not need one HAProxy per service instance. So we can use one HAProxy for all of our services because Bob only wants to debug, he do not want to make a large impact on the database to run through batch jobs or something with Big Lord, but only wants to look after the data. So we want to do it with one floating IP for the internet and one HAProxy for example. So we install some agent into the HAProxy server because the HAProxy in itself does not provide a rich API for reconfiguration from the network. So this is a little program written in Python which connects to Revit MQ for the information oh you have to get a new configuration for the HAProxy from somewhere. And that is done, is produced by the HAProxy backend we wrote, which is called by the service broker when you want a service key. When the service key is asked for, the service broker makes this whole thing with a service instance, hey, make a user, what looks up the IP address from the service instance and then he gets this information, gets the IP address to the HAProxy backend and saying here I want some public accessibility for that IP address. The HAProxy backend knows the configuration of the HAProxy because it started somewhere and then makes some reconfiguration of it because it adds some port binding of something and gets the HAProxy agent to know, hey, there's a new configuration and it gets it from here. Why this complicated setup? If we look at the production environment, we have many services, we have many service brokers maybe, and we have maybe many users on it. And some users may make different accessibilities at the same time, requesting service keys at the same time. So we have the problem that the HAProxy has to be reconfigured from different ways or the same time. So if we get the information, hey, agent, get your new configuration for the HAProxy, you get the actual one, not that one in between, it gets the state from that point of time but does not have to expose some external API because the HAProxy agent thing here does not expose some endpoint outwards. So there's no attack point because all connection is done actively by the HAProxy agent to the RabbitMQ. What does it mean? If we go to our HAProxy conflict, we have, for example, we want to have a cluster of a database with three nodes. We have the possibility to address each node with a binding of a public port to our private IP address, private port. So we get that three nodes differently accessible. One set up, you will see that's not the typical HAProxy database configuration you see all over the Internet because what was our idea behind it? He wants to debug the cluster, which means no failover interesting from the connection of the service broker but getting to know what that single node does. So we have to provide an access directly to the node. For that, we have some knowledge about the reconfiguration, the providing of options to that. But we have also other setups, interests, maybe the connection to our database is not for debug purposes, but we have some application in some other private network which is not directly accessible for our Cloud Foundry internal network, but that application has also to be able to connect to that database. We have no other way but proxying through from one network to another because the problem is if you make it by router or something, you have that wide open channel from that network to another, open for some assaults from that network to the Cloud Foundry environment. So maybe that's not that kind of coolness you want to introduce to your production environment. So you maybe want to only make some failover configuration of your HAProxy and by that made it accessible through the other network and here maybe introducing some access control list, making you some IP sub-address constraints so only your application node which has your application in some OpenStack tenant is able to connect to your database and nothing else.  So for example if you have an elastic search cluster, you have as a rest endpoint each separation of data. So you have your document list in some collection of data you have there and you have another one. There are some different rest endpoints behind an HTTP endpoint and what you want maybe is making that accessible but not the rest. You have this distinct endpoint you want to be accessible and within with this HAProxy config thing you can make only this accessible to the other network. So you have a really distinct small accessible point which is canonized through the router through the other network. So if we jump back we have this to get what's also a problem here is you see one service broker for components which have to be introduced to your stack, to your implementation but that's the only thing which is special for that service. So you can reuse your HAProxy back end and your HAProxy for different service brokers. So you can have a whole bunch of service brokers using the same HAProxy back end and using the same HAProxy. So you can manage different services going through from another network. And why that RapidMQ we see later on. Jump back. Our benefits from that setup we have access control list for optimizing your connection protocol for several restrictions like a P subnet and so on where you can make sanity checks like we've done here. This line here in that configuration makes clear that a connection to the database made through the HAProxy is always correct because the connection to that node is tested before the connection is established through the HAProxy. Because the HAProxy has some user which is only able to make a connection but nothing else to the database. This has to be introduced to your service instance provisioning that the role is there but then you have made a connection to the HAProxy. It gets sanity check that the node is healthy it wants to provide to you and then makes you a tunnel through the HAProxy to the database node which is really there not some failover mechanism needed at the client because the HAProxy is a failover proxy for load balancing purposes. You have no direct access to the database so if you run for example a DDoS attack against the HAProxy IP address the database isn't really caring about it because if the HAProxy goes down the database is healthy your application connecting to the HAProxy is healthy your cloud found instance is healthy because it has another IP address has other load balancers and so on so the complete stack isn't corrupted by a DDoS attack against this HAProxy. And that is done because you have a separation of the routing because the routing through the go route a load balancer go router to the application to the service is not is a completely other route than through the HAProxy to the service instances. Failover strategies we talked about load balancing you can have more than one node behind one port or IP address and also what you can do is limit the connections if you provide a service with your service broker you may want to limit the number of connections. So you say you have a plan in your service catalog which only provides five connections at the same time to your database because large scale applications using 100 application instances may should be other treated like a service instance which is laying low. And then they should buy some other service instance which is more capable of handling this high traffic which is more expensive and you want to push your users there not by restriction but by encouraging them. So you restrict the number of connections to the database. The HAProxy has some ACL rule for restricting the number of configurations so instead of using the HAProxy for the service key management you can also use it for the normal service binding management. So the connection from your cloud foundry deployment of your app through the HAProxy to the database cluster can be managed by that. So you can use the failover mechanisms and so on and you can use the limitation of connections for providing a smaller service plan than maybe possible as well. And like I told you connections between different private networks are possible in your company network so you have HAProxy usually establishing this special connection maybe because it's he's in both networks but nothing and no one other. So what alternatives are there for providing such access from elsewhere you have this trick with CFSSH and port forwarding. Cloud foundry if you have a user you can lock in with the CFCLI to the cloud foundry you can use CFSSH to jump into an application container and from there on you can use port forwarding without having to know about some SSH key because this is introduced by the CFCLI making an HTTPS connection to the cloud foundry controller and from there on you have an SSH connection. But the application the connection starts with the CFCLI installed. If you want to connect an application to your database which is not home in your cloud foundry as a cloud foundry application you don't you have to install a CFCLI there or you have to introduce some SSH key there which is also installed on the service but that's not possible on the public clouds. So there's some limitation and also some there are cloud foundry installations they regulate the SSA mechanism by disabling it because they see there are some security issues like I've seen in the Volkswagen Group RT cloud and the connection you're doing is to localhost that from your if you're but that's the smallest problem. The other possibility is having a virtual machine or container or something using as a jump host which is more or less the same trick as above. From there you get the SSH portfolio awarding thing but there you don't have the limitations and so on. The constraints you cannot do are limiting the number of connections and so on. I told you about we come back to the rabbit and here we're working actually on scaling the things a little bit up and we talked about I told you about the thing with may from one network to another when I do something like this you have one service broker who wants something goes to the service broker back end and then yes he knows okay if you want that connection I have to go to that HAProxy making a connection from there to there then from there to there and from there to there and so you can go through a whole proxy chain which is in company networks really often can be found or you want to do it because you have a failover system in your HAProxies you have two HAProxies for failover if one goes down the other comes up so you have to incorporate both and the last one is already there the second one we are working on it because it's you need to have some management of the proxy chain inside of the service broker back end because he has to know it has to know what is the proxy chain we want to go through so the service broker can ask for open me that chain not only open me that HAProxy like I told it's an open source framework for developing service brokers you can find us in GitHub you can contact us we are happy for contributions if you need more more support on it you can also buy it your company but we are also happy for for the open source project here also the HAProxy agent and the HAProxy back end is on GitHub so you can they are getting contact with us raising issues bug fixing making pull requests help us with the docs if you have tips for us hey look at that that's a good idea we're happy for it so I hope you and I got something out of my talk and I'm off for questions there are two microphones there because we are recording please use it with if you have questions now as you can contact us wire that