Okay. Well, I wanted to give a small introduction to Scalable Ogo, which is a Goopware server written on an object with C. First, a bit about token Goopware org. This is a larger project, which is, well, more like a framework for building Goopware servers, pretty much like no step is framework for building Goay applications. So we are focusing on building reusable objects for building such servers, because the requirements for Goopware servers are pretty different. So there's not just one Goopware server which fits all, but you usually want to have different kinds of Goopware servers. We have a lot of code, a pretty large code base for calendaring and contact management. We have some simple document management stuff. We have a lot of protocol implementations. By protocols, I mean protocols which are used between client applications like RSS feed tweeters or calendaring clients and the servers. And currently we have two implementations of the Goopware server. The first one is OpenGoopware, the regular cat OpenGoopware. It's for smaller work groups and has a pretty complex functionality and the Scalable Ogo, which is a bit newer, was, I think, started in 2004 or something, or 2005. It's a bit refreshed and has a different focus, which I come to soon. Well, again, as I said, OpenGoopware is not just for building those two implementations, but we really want to bring forward Goopware standards as well, like, for example, in Canada and Goopware. And we also do not want to reinvent the software. For example, we are not building any AP software on email servers, stuff like that, because there are really great projects which already exist. For example, SpyroSport, the mayor's service, or Korea's service, doesn't really make any sense to replace those. The email tax is integrated into the email system usually, so it's not really related to the Goopware part, but it fits in a larger picture. As I said, it belongs a bit to Goopware standards. We want to connect to clients. So, we do not want to be a web-coopware program. And, of course, we want to use a digital-free software, so we do not use any non-free software in building the implementations, but it's on GPR and GPR. So, to get back to ScalaAuto, it's a bit difficult to explain, especially end users do not understand why different approaches are necessary. For example, PetAuto has a lot of functionality. It's not really slow, but it's intended for a few hundreds of users at most. So, you can base a lot of CPU on doing complex stuff. In contrast, the ScalaAuto system is designed for hundreds, hundreds of thousands of users. And to do that, you need to take a lot more care about processing power and storage speed and stuff like that, so we really shrunk the functionality to get ScalaAuto started. So, what does ScalaAuto do? It's really based on the standard stuff. For email, of course, we use iMap4 and we just reuse the existing mail servers. And the address book and the calendar, which are integrated are completely based on iCalendar and WeCard. So, we actually store the data in iCalendar and WeCard. So, there's no mismatch between native clients or open-source native clients and the server. And it's also very simple. For example, in the Tet open bootware, you can have records which are really interconnected. For example, if you have company contact, you can assign those company records or employees and stuff like that. And the system maintains the connection between them. But database-wise, this is quite expensive because you need to do the joints between the different tables. It's not possible in ScalaAuto and ScalaAuto and a contact is always on its own. It's just a WeCard which is stored in the server. So, it's very simple to remove and very fast to retrieve and to store, but it doesn't allow those complex links between the objects. But as I said, a common problem in groupware is that if a groupware provides more functionality, like, for example, open groupware, the native clients usually don't support that. So, this is why many groupware projects provide web interfaces because they can do anything they want in the web interface. But native clients like evolution or contact, they're not easily extensible. So, it's hard to add a complex functionality, but they are the perfect fit for ScalaAuto because it just uses the same thing. About the history, ScalaAuto was initially developed for a large French ministry which had about 60,000 users which were to be supplied using that groupware solution. And they had three basic requirements. First, of course, it would need to be scalable because they wanted to host it on a smaller cluster, a single small cluster in a central location so they didn't have a thousand groupware servers, but just one. They wanted to support native clients, Mozilla native clients, Sunbird and Thunderbird because in France they wanted to replace the proprietary clients like Outlook using open source ones. And third, they still wanted to have a web interface but the requirement was that the web interface should look exactly like Thunderbird or Sunbird, like the desktop applications. And ScalaAuto was developed to meet all of those requirements. First, scalability. As I said, it's a very complex topic, but one thing is that regular database-based groupware servers like OpenGroupware, the old one or eGroupware, I think about a hundred more, they usually have a single database table, for example an events table, where all the events are stored, and all events of the system are stored in that single table. Of course, it's fine if you have a million events or something like that, it's fine for a SQL database, but if you have 60,000 users which have maybe 10,000 events each, it doesn't scale anymore because you get tables which are huge. So ScalaAuto is a source where ScalaAuto can distribute the data between different tables, and those tables can even live on different servers. So actually in the French project, we had three backend servers, so you could assign user groups to the servers and the data would be stored on different cluster machines. Then, as I mentioned before, it stores raw ICLN and read cards, it takes, for example, Sunbird writes an event into the server, it just takes the ICLN and stores that as it gets the event. So it's very fast operation, it's just a single update to the database, and to support the web interface, we also have an index over that information. That's necessary because if you just store the ICLN, files in the database, you can use SQL to have queries on them. So for example, if you want to show a week of events, you will need to pass each ICLN in a file, but that's too slow, so we have a separate table which extracts the core information from these files, like start time and time, and it's stored in an additional database table for fast queries in the web interface. So the web interface can say, give me the importance of this week. The next tables can also be split, there can be multiple tables, and they can even live on different database servers than the content tables which stores the payload. So it's very interesting because the content tables don't need to be on a very fast storage, because for example, they could be on a slow rate 1, something like that, which endures integrity because it's the important information. Whereas the index tables, they can be reconstructed on the content, so you can place them on a volatile storage line, a solid status or something. If it breaks, you can just throw it away and rebuild the index from the content tables. So it makes a lot of sense. So it can be more aggressive in optimization on the index tables. Well, the third item, if you don't use the web interface at all, but the native client, they just retrieve those pre-rendered iCleaner or vCard files. So it's not like in other rootware servers that the iCleaner or vCard are deconstructed into a database field and need to be reconstructed to the iCleaner file on retriever. We just store them as they come and we just need to pull them out of the database and send to the client, which is very reference. Native Client's all approach was to push open standards. So actually, we started out with roof.dev, which is not really a standard, it's like a convention we found with the KDE developers in 2004, I think. In the meantime, we have KALDA, which is now an official standard. It's an FC for something, I don't know the exact count, but it's a real internet standard and it's widely deployed with scanning a lot of momentum. For example, Google and Yahoo also support KALDA now. KALDA is in the works. KALDA is also going to be a regular IFC. So we are very close and finally having real standards for who we are. And close standards are also supported by a scalable organ. Actually, we extend some clients, the open source clients, which is very bad, do not support standards very well, unfortunately. So the KALDA implementations in Mozilla, for example, do not provide all the necessary features. The address book cannot do contact and stuff like that. Is not possible to write. I think in the regular, I don't know. However, we have plugins for those clients, which add some listing functionality. For example, we have the KALDA address book for the Thunderbird address book and there are also extensions for the KALDA connector in Mozilla. So it's actually the primary client for a scalable organ. It works really well. Then we have a Funnambore plug-in, which is Funnambore is a Java server which is used to synchronize mobile devices like KALDA and mobile telephones. And we have a plug-in which directly connects the database. Because the database does the iclinical files, you can just push that into the Funnambore. Well, because we support those standards, especially KALDA, of course you can use the iclan for the server. You can even use a regular Web Dev client for all the collections and stuff like that, which is also quite nice. Well, the Web Interface, as I said, it was a requirement that they wanted for the Web Interface that it looks exactly like the native clients. Now, the native Sunbird isn't very beautiful. It's actually quite ugly, but the Web Interface looks exactly like that. So people often ask us why the Web Interface looks so ugly, just because Mozilla Interface looks ugly. It's also very scalable because we do a lot of HTTP checks inside the Web Interface. HTTP is actually a very scalable code that has a lot of features to support scalable HTTP. One is the eTag. The eTag starts with a Web page changed in the meantime. For example, if the browser gets an HTML page, you can send a small token with that, which represents the state of that page. If the browser tries to re-get the same page, it just checks whether the token changed. If it didn't change, you can pull it from its local cache or in memory cache. So it's very fast. The same is true for proxies. Between the actual application server and the browser, you can put a proxy like Squid, there are other proxies. Apache also has a proxy module in that which can cache the information for multiple users. For example, the browser connects the proxy server and the proxy server asks the application just once, and if another user retrieves the same information, it's already in the proxy, so it doesn't need to be bothered with multiple users. And the thing that this is working best is emails because emails in an iMob server can be changed. There's always the same. If you would change an email in an iMob server, it wouldn't get assigned a new ID. So if you have an ID in the iMob server, it never changes what is stored in there. So actually, if an email is rendered by the Web interface, the HTML page of that email which shows that email, it can be cached by the browser locally. So if you retweet that once, and the user looks at the same email a second time, it's already in the browser cache, so it's really nice. Well, that's some bus work stuff. So Scalable Ogo is REST, which is basically another word for HTTP in my opinion because it's a style on how to write HTTP services, and Scalable Ogo is implementing or built around those web protocols which use the standard HTTP words put at the lead to read and write the iCalender and recut files. So for example, to see the iCalender in the web browser, you can just enter the URL to the iCal file and instead of adding a .html, you will add a .ics and then you get the iCalender representation directly pulled off of the database. That's pretty nice. Well, even for email, even the web interface is built around that REST principle or that that hierarchy. So you can actually use Scalable Ogo as an iMap HTTP gateway. For example, if you have a user, it's a login name in the iMap server, you can traverse the iMap folder hierarchy and get to the email ID, like 123 email, if you retrieve that using an HTTP library or a web browser or whatever you want to do, you actually get the line, the line which represents that email and it's even better because the iMap servers do not also have the facility to extract specific parts from such a line mail. For example, if you get a multi-part mail which contains a text and an image, you can actually address the image using a code. For example, that could be the image which is embedded in the MimeStore channel and all the work is done by the iMap server, so it's just a gateway. That's also how the web interface shows the images. If you bring up the HTML page representing that email, it's something like on2feed.html and that HTML page actually represents the part from the iMap server, so it's really fast. It's pretty interesting. I think it's pretty interesting for a lot of different projects as well, just that gateway because it makes it very easy to develop an email client because it's much easier to work with HTTP than the iMap which can be quite comprehensive. So, where are we? Actually, we are very close to a wonderful release, so it's one dot. Our release candidate 9 was released last week. Actually, it's a production at a really large customer side. So, I think in Canada, the guys who do the main development, which is Inverse, they have about three customers each with about 40,000 users. So, it's actually employed. Anyways, the final release will come soon. The development at this time is mostly done by a company called Inverse, which is in Canada, and they only do open source stuff, so they do not sell anything. So, it's not a licensed business or something like that. They are basically a hosting company for large ministries and education facilities in Canada. And well, you can get the code at a monotone repository from Inverse directly or from Subversion. Every time there is a release like RC9, they push the state to the Subversion server so that we have a proper release, history and incentive server. So, actually, the development is going very well. We don't need that much help on the core server, but what we would like to see is more suffered from more native clients. And that's something I said before, the situation and open source clients and open standards is very bad. So, we would really talk to evolution contact developers for improving that, because we are mostly doing or helping with the Mozilla stuff, so this is a primary client, but we would really love to get some people on improving evolution contact with subtle standards. Well, the code internals is written in Objective C, so it's a real compiled code, and you get a real demon out of that, not some virtual machine fire, which you need to run in something which takes 10 gigabytes of memory and just works a lot. So, Objective C is something you may not know that's really part of GCC as well, you compile that, you get a regular binary out of that, and it's very fast, it's optimized, it's not as boring like JAMA, and it's fast but compliant thanks to the iPhone, because the iPhone, I think, brings a lot of developers to Objective C because all the software written on that was written in Objective C, so it's quite great. And I try to bring up the diagram of how it all fits together. It's basically the Objective C one-time, which is coming with a new compiler. Then we have the new step-based library, which is used by Gable, although, and for Open Group there for historical reasons we use a different foundation library, but those foundation libraries contain stuff like string handling or map tables and all the basic stuff. Then we have the SOPE application server. This is doing a lot of things. As the name says, it's an application server, it does all the HTML rendering, but it also contains all the libraries which are used by Scalable, Ogo and Open Group there, for example, generating i-calender files or parsing them, drawing feed views in HTML and all the stuff, it's a lot of stuff in SOPE, and I would say it's about 17% of Scalable, Ogo, maybe even a bit more, because we use such a lot of the shared code. So, well, on top we have the two applications, the one which is more complex and the one which is very light-white and fenced. You can reach us, well, of course, using the website at Scalable, Ogo, or Open Group there, Ogo, and it's a mailing list for Scalable, Ogo, or SOGO at Open Group there, and it's open to everyone, everyone can subscribe, well, and join us and comment and help us test whatever. Yeah, that's about it. Questions? What's the status of the packaging of the SOPE framework and of the VR component of the Scalable? Because I have my cell freeze, I have to go installing the other Ogo server and all the compliance between the libraries of the SOPE framework and all the other components was a mess with Debian. Debian? Debian. I'm not sure they are providing Debian binaries, actually. I know that they provide young packages for Red Hat, but I don't know about Debian. Is there something for Red Hat? Yeah, but yeah, there's packaging for Red Hat, well, on the hands, and that's actively maintained by users. I think they're using the same packages for their customer deployments for it's supposed to work. I don't know. Actually, it's not that easy to build from source code because Scalable, Ogo, attaches a few things of SOPE. It's mostly because we use those different foundation libraries. Could you discuss what is the role of this foundation? Is that disappearing gradually? Well, why are you wondering? It's clearly a better library because I've never worked on it. Well, the foundation isn't really developed any further. I mean, it's stable, and it does what it does, and we do not put a lot of work into that to port it over to Moosa Base, but I think maybe this weekend, Sebastian was very active in that. Maybe he can convince Richard to work a bit more. The Big Apple now is on Scalable. Not anymore on the Ogo. Scalable Ogo is already using Moosa Base library. No, no, no. The Big Apple is now on development. Ogo is on the left side. We basically would like to replace this against a base library. The major advantage for OpenGoogle would be that Moosa Base library has better Unicode than them. So the foundation only really does Isolate in one. So OpenGoogle has a bit restricted with foreign languages, for example, and check, and check for 400. That's the basic advantage. I mean, stability-wise it's done. There are no major bugs in that. So it just works, but I think we will move to Moosa Base over time because it mostly depends on the people who work on it. My motivation is pretty low on doing that because it works for me. How lively is the community? Development? Well, I don't know. There are some mailings. Most of the work is my experience with groupware servers. OpenBook and Scalable Ogo is that a lot of people are not interested in doing that. So it's usually a small circle of developers which are also business in that domain. It's not like there are some students which likes groupware servers because it's a business application basically, and it's very hard to get a little community around that. But I think we are about 10 to 20 guys or something like that which are actively involved. Can you tell us about the current status? Can there be compatibility with different clients? Is it 100% compatible with... Cal? Scalable Ogo doesn't implement all of Cal. In fact, I think no server can support all of Cal because it's quite complex. Most groupware servers actually implement a subset which is required to post Apple icon. So that's... So we get more free business? Free business support eventually. So that's also an add-on for Mozilla. Mozilla is extended for free business functionality with Scalable Ogo. So it's not too bad. But my opinion is that people should rather use GroupDef because it's much simpler and you can actually implement all of that. And CalDef can be pretty complex because you need to implement provisioning as a whole bunch of stuff which is connected to that. But I'm doing CalDef talk tomorrow, so I can talk tomorrow. Yeah. Actually, we are not using a lot of that on Scalable Ogo because the GDR is an object mapping framework for those who don't know it. We can map database records to objects and that's too slow for what we are doing with that scale. So we are only using the adapter that's like JDBC or something like that. That's what we use in Scalable Ogo so it's not mapping stuff. We don't really need any features of GDR2. I was thinking about database backends because actually there are oracle adapters for that which are actively maintained. There are postcards for our I think we have a lot more adapters in GDR1 of Sophie than in GDR2. I've got a simple light one a minestore L1 what else do we have? We have the cybers one I think pretty much any database. Front-based. Let's give a bit of structure on the soapbox I heard. Yes, this is actually multiple libraries. So we use the code and the GDR1 library is part of Sophie but technically the GDR is the Gnuset database library. We just imported a previous version into the Sophie application server which was working for us and Gnuset is continuing the development of the Gnuset database library separately from that. So we built like the foundation situation. We have a pretty stable GDR1 library and here with a lot of connectors and stuff like that. We're well tested and the code possibly probably changed to GDR2 but it doesn't buy us a lot at this moment because the stuff which is new in GDR2 it's not interesting for us because it's all higher level modeling stuff which we do not use. We need to go pretty much down to the database to get the necessary speed. I think there are some things in the GDR1 where it stood the way from the original version and what if you give more speed like modifications and it will start with that and it's more important in the GDR1 library. That's actually a modified GDR1 which we did some stuff which just makes it fast or more reliable. For example our version doesn't throw exceptions. We don't throw all exceptions but return just proper error codes because exceptions in Objective-C are always a little bit fissure. I don't know. I don't trust them. Is there a plan to make a dedication against Kavanos or who were the regular ones? I know but there are also some deployments which actually use Active Directory as the ADIP service and I think but I know Kavanos expert and I know very little about that. On the open group to our site development is still going on or now for well, for example Sebastian is working on the user base port but functionality wise there isn't a lot happening more than what because the web interface of the open group is three years later than the available open but now by users. That's mostly a matter of time because the people I know are fine with web interface but the plan for me was using the scalable Ogu interface and something which was called the site store server does the i-calendar and v-card start for open group back so it maps things to i-calendar and v-card and it's pretty similar to what the scalable Ogu user interface does so it could possibly really use the interface on the other open group. I would like to have some time to try the scalability for the open group for one integration with the i-calendar and the v-card. Certainly that's true. Actually I am also doing a Java project with open group back so I actually implemented the whole stack from the fat open group in Java so there's actually an Ogu JMA but it only has a customized user interface for one specific client but it uses exactly the same data as and it's also a modern user interface but it's really tired to enter the information system for a pharmacy chamber so they have pretty specific requirements but maybe that will involve some tool in open group I don't know. Integration with proprietary software is the loudest question or Open group then? Well but a lot of stuff with LGPL My first question is can I make some question about proprietary integration? Can I ask for OpenGL Outlook? Is it integrated or Well actually I'm working for a company which does an Outlook platform and there's a new one coming which is we used to have an Outlook platform just for open group which was using an old protocol to talk to the open group server and we are just in the last three years we were re-targeting that Outlook platform to use KALDEV so you can actually use that KALDEV with any server which suffers KALDEV and KALDEV so that's in the works And you're going to see all the calendars of mobile phones and stuff like that because it was not compatible before? Mobile phones you could use Panambo on the scale but it's not even very good but for open group here you could use a so-called crime and you store an Outlook so you can replace your PC file to that store and then you can even synchronize mobile devices with that So it's much better Because I remember that the sync was going, you had two stores basically the one which is your primary one of the client and the secondary one which is given by the client but was not syncing and it's mostly a problem of Outlook because Outlook can only sync a so-called default KALDEV and to replace a PC file you need a so-called primary storage wire and the Outlook could be one it was not complex enough but the new one can be a primary store but it's reworked complicated actually you use a SQLite as a database and as a replacement for a PC file I had a project which we used Open Grouper to substitute completely the change file It's a current plugin which we are now developing and it doesn't do email yet so you would still have to get the primary store which does the calendar and the address box and then you have the iMac connector from so it's one additional configuration but we are working on that for you Yeah, the K point would push it in the real business Yeah, but it's not different from Outlook in the general case if you want a set of Outlook to use iMac you still also get two Yeah, if you are allowed to we have this change the point is to get three of you Yeah, more questions Why don't you work on the Java version it's so simple I will just make the new question Well I'm Christmas but because I'm also doing the work in Java I can assure you it's much more awesome to work in Objective C I am I know what I'm talking about Yeah, we are working


Welcome to Toffy TV, it is the Everton News Daily. Moise Keane has completed his move to Juventus this week, that is according to Fabrizio Romano, who is reporting it from someone else as well. Everton had obviously had this agreement in place, Keane has been on a two-year loan with the club, it was due to be completed in the summer, it's actually being completed this week or last week rather, in the last week. And that, Everton have had the money, so there you go, Moise Keane is no longer an Everton player, he was sent off on Sunday after 44 seconds in the 1-0 defeat, he went as a 1-0 defeat against Roma.  On what interest him, that is the last game as an Everton player he was sent off against Huddersfield and his last appearance as an Everton player he was sent off for Juve, so there you go. I'm not one, it was sadly a move that just didn't work out for him, you know, come with a lot of potential, I was quite excited personally when we got him, thought he could really develop well for us in that time and it just never happened for him. And then, did Everton look after him best he could probably not, obviously Covid was involved in that as well, away from family and friends, didn't quite work and in a house on his own and all that. And there was other mitigating circumstances, obviously Rafa Benitez didn't fancy him either and wanted him back out the door. And now he's gone back to Juve and this season he's really kicked on and has done well for them this season, so we wish him well as he's completed his move to Juventus. Everton today have been linked again with a move for Leon Stryker, Mousha Denbale, he becomes a free agent in the summer, Everton did enquire in January, the Stryker wanted to stay at Leon, he turned down a move to Southampton. But the 26-year-old is interested in Everton again and according to Tuto Mercato, Denbale wants to return to the Premier League and will be interested in joining Everton, should they remain in the Premier League is that big thing to sort out. Aston Villa have also been credited with an interest in the 26-year-old Stryker, so he might be a good option for Everton, I thought he'd be a very good option in January, he'd be a good option on a free in the summer should we stay up. The right frame, he's got goals, mostly where he's gone, bar on one post, spell on athletic home and drift, did really well at Celtic and he's a good age still, so we'll have to do our part of the bargain first, which has remained in the Premier League. Ben Godfrey said that he enjoyed being back in the Everton start line up on Sunday after he was drafted in at left back in Evans 2-2 draw at the City Grant. Ben Godfrey had been speaking about making sure the standards were high in training, he said that's been the message, keep your standards high in training and the good characters are carrying that through as well. He just wants to work hard to try and get back in and said that every point matters when you're in this situation, everyone is disappointed that we didn't win the game on Sunday, but there are positives to take from the draw. But we do need wins, we need wins as soon as possible, we've got another big game at the weekend, obviously Godfrey was in due to Michel Enco's illness on Sunday, it remains to be seen whether he'll keep his place in Saturday's game with Brentford or whether Michel Enco will come back in the start on 11. Tyler Ongyango has returned to Everton after he suffered a hamstring injury a couple of weeks ago for Forrest Green Rovers, he's been on loan with Duncan Ferguson, Duncan Ferguson confirmed that Ongyango has undergone surgery on his hamstring and will do his rehabilitation at Everton for the remainder of the season. Duncan said he didn't expect Ongyango back of Forrest Green this season, it's a blow because he'd obviously spent the first half of the season on loan of Beton and he'd moved to Forrest Green Rovers in January and obviously knew Duncan well from the time together at Everton, it would have been a good loan move for him to get games and to continue his education but obviously suffering that injury, it's a big blow to Tyler who has picked up injuries in the second half of the season in the last few years and it really has halted his progress and this is a big blow for him. Ryan Astley, who was on loan at Arachrington, stand these on crutches at the moment after suffering an ankle injury against Lincoln City last month but there is no plans for him to return to Everton for rehabilitation so that means that Arachrington is hopeful that he's going to return to action before the season finishes which is good news, he's made 34 appearances so far for them on loan this season. And there is a story today, the Daily Mail are reporting that Farad Meshiri will not sell Everton fully despite receiving several offers to buy Everton outright. The Mail go on to say it's due to concerns over his relationship with Alasher Usman, they think if he sells the club the government will look into that sale, so that's why according to this report, that's why he is favouring MSP buying a minority stake in Everton for the time being, there is some thought that MSP will take over Everton full time but it might be a softly, softly approach of first rather than a full sale. I don't know whether there's anything in this other than the fact that MSP are close apparently to completing their minority stake in Everton, so we'll have to wait and see whether anything else comes from that whether they do get in their foot in the door and then complete the full purchase over time, only time will tell with that one.


Live from the Sands Convention Center, Las Vegas, Nevada, extracting the signal from the noise. It's theCUBE covering HP Discover 2015. Brought to you by HP, and now your host, Dave Vellante. Back to HP Discover, everybody, this is Dave Vellante, and this is theCUBE. theCUBE goes out to the events. We extract the signal from the noise. Check out hpdiscover.social for all the social buzz. We're bringing that this year to HP Discover. Bill Hilf is here. He's the Senior Vice President of HP Cloud, and he's joined by Gonzalo Uquilis, who is the Senior Vice President and GM of Senase, who is a utility out of Ecuador, right? So welcome to theCUBE. Thank you. Thank you again, Bill, and thanks for coming on, Gonzalo. So Bill, let's start with you. Healy on a lot of buzz on the show. You guys have a keynote going on. You're taking over the Twitter sphere, all kinds of action and some announcements. So give us the update on Healy. We had a great event the other night. Five, 600 customers line out the door. A lot of excitement right now with Healy on. Yeah, it's good to be here again. I love coming on to CUBE. It's actually one of my favorite things to do here at Discover. Awesome. So it's good to see you guys again. So interestingly, personally, this is my two-year anniversary today at HP. And so it's great to kind of reflect back and see how much progress we've made as a company, but I also personally am looking back saying, wow, so far in this period of time. And so Healy on is our, for those that don't know, it's the name of our overall cloud portfolio. So includes our different software technologies, our hardware systems, our services. And it is basically how do we provide enterprises in cloud capabilities, not just for the new, but also how do we help them make the journey from their traditional to the cloud native? So at this event this week, our big announcement is Healy on cloud system nine. And that's, cloud systems are flagship private cloud solution that customers use to out of the box, build and get up and running a cloud environment for infrastructure or platform services. And so this is our bread and butter solution. We have thousands of customers around the world. And the big parts of that announcement this week are, we're shipping our full Healy on platform inside cloud system for the first time. That's Healy on OpenStack and our Healy on Cloud Foundry development platform that gives customers the ability to build both infrastructure as well as cloud native applications in the same environment. We're also building in support for Healy on Eucalyptus so customers can run AWS workloads on premise. And as I mentioned in the keynote on our main stage is probably the number one customer requirement that we're meeting with this release is customers are asking us for end-to-end IT management. Not just cloud, not just traditional, how they bridge it all together. How do you orchestrate and automate over everything that they have? Because that's what they look to HP for. They look to us for full IT, not just a sliced up portfolio. So our tools with cloud service automation that ship with cloud system are really critical in doing that. So people should think of your group as a solutions group that I'm going to go to.  And the different groups, the server group, the storage group, they're essentially arms dealers to you. Is that right when you build solutions out of those? Basically, we're measured through our attach to everything in HP and we're an overlay group to all the other business units themselves. So a good way to describe it is someone asked me, they said, Bill, do you have a public cloud sales team or a private cloud sales team or a VPC? We have a cloud sales team. So we sit down with the customer and say, what are you trying to solve? What are you trying to do? And then there's multiple pieces of our portfolio that we bring to bear into that. So Gonzalo, I wonder if we could turn our attention to Sena Say. So talk about Sena Say as an organization and what's your role there? Well, Sena Say is an independent system operator. We are in charge of handling the whole electricity network, country-wide in Ecuador. So we are responsible to provide a very special public service that's electricity. So in order to do so, we have to take advantage of best IT solutions like Cloud Helium, for instance, in order to improve our processes, the agility to reduce the cost, to reduce the time to deploy apps. So that's the main concern. So interesting business. So let's talk about your business a little bit if we may. So very capital intensive. You try to avoid making those capital expenditures if you can't. Be more efficient, so you can avoid that. You can't go down. You have to be responsive when there was a problem, natural disaster, accidents, and so forth. What are the pressures in your business? I mean, I'm speaking from a US perspective, but maybe you can help us sort of localize what's going on in your business and your part of the world. Well, in Ecuador, the provision of electricity besides the technical complexity has two important components. Political components and social components. That makes special this kind of service provision in Ecuador. And besides the business challenges in Ecuador, we are part of the electricity interconnection. So we will have a whole market starting with Colombia down to Chile. So electrical, regional interconnection imposes a big challenge for Senace. We would like in the future to become a regional operator, not just operator of Ecuador, but the electricity operator of the region. So that's one of the challenges that we have to face. Well, you have to get permission to do that, obviously, right? You can't just drive in and say, okay, we're going to start a business in Chile. We have to show that we have the best standards, the best people, the best end-to-end solutions, and be able to provide world-class services. So there's pricing, which is regulated, right? So you have to be very efficient. There's safety, and then the social responsibility, of course, it's coal, a lot of this is coal-fired. So you have to balance that. The important thing is that in Ecuador, we are deploying eight new hydro stations for the year 2016. The demand of electricity in Ecuador will be supplied 95% by hydro electricity. And what is it today? 50, about 50%. So still pretty significant hydro. 95% will be hydro. So we will be able to export green energy to Colombia and Peru. And besides that also, the government is replacing gas for cooking instead of using electricity. So we are deploying 3.5 million induction stoves to replace gas and using electricity. So it poses a very big challenge to handle the electricity network. So then we have to have some sort of partnership, like HP will have been working with HP 25 years ago. I see, so you're replacing LNG with electricity and the source of LNG is United States probably, right? Yes, exactly. But you know, to connect 3.5 million stoves to the grid, it poses a very high challenges of operating that complex system. Okay, so you have a lot going on in your business. So now let's connect it back to your IT infrastructure. So you've got HP, maybe take us through sort of what your infrastructure looks like. You know, when you are an independent system operator, you have two dimensions, IT and OT. Because we are in charge of operating the network. You have to supervise generation, transmission, distribution, transmission lines, and issue commands over that infrastructure. So one of the challenges is conversions between IT and OT and to use the best of cloud, big data, BI in order to have this predictable, predictive BI in order to foresee future problems in the management of the network. So we have to put three important things, cloud, BI, big data because we got a lot of information, real-time information from the system. So the challenge is that we have to deal with real-time operation. You know, electricity is different from other industries because you have to generate electricity at the same time when the demand comes. So the challenge is real-time operation using cloud, BI, and big data. So how are you using your analytics to predict essentially where demand is going to be and make sure that you can deliver that demand? Is that right or? For instance, we sample information from the substations and generation 60 times every second. 60 times every second. So you can imagine the quantity, the volume of information. And then we can process that information to identify parallels of possible and stability of the system. We work interconnected Ecuador and Colombia grids. So if we see some behavior that doesn't fit the standard way of doing things, we can predict if we don't take preventive actions, we will have a blackout in the future. Mm-hmm. Okay, now talk more about your cloud. What does your cloud look like and what do you do with it? We have deployed a private cloud, helium, and we have started, of course, with the infrastructure as a service. We have reduced the time of attending those requirements before it took several weeks. And now we have deployed that in a couple of days. But of course, we are, in the near future, we will use pass as a service in order to develop applications that are specific to the utilities. And of course, in the end, we will have an hybrid cloud to connect to the public cloud where we'll have a holistic management of all the IT resources. So Bill, if you want a client visit with Gonzalo, what would you ask him? What would you want to know from him? Yeah, so the pattern that Gonzalo described of starting with a private cloud and extending out to build a hybrid infrastructure is right in line with our strategy and what the pattern that we see from lots of customers like what they're doing in Ecuador because the business criticality of that workload, providing energy, the regulation, the political environment, you know, those are issues that HP deals with very well. That's right in our wheelhouse of what we're doing. So we often use the phrase, you know, getting to a hybrid cloud through the private cloud. And so that is exactly what Gonzalo is doing in his environment. So the types of things I would look at is and talk to him about are, they're using infrastructure as a service today. What sort of hybrid technologies does he need in the future? What sort of types of applications do they want to build, particularly in things like big data? Do they want to do, you know, analytical applications over and reason over that data that they're collecting from all the different environments? And what application environment do they want to build those in? To make sure that we and the product side are building the right tools and connectors and capabilities that he needs as he expands out. So where is your application portfolio going Gonzalo? We talked about, you got systems of record. Exactly. Now you're talking about business intelligence and big data and systems of intelligence, essentially. Is that where your application emphasis is going? Real time applications imposes two very demanding requirements. Cyber security and performance. Cyber security and performance. So we have deployed in the private cloud several corporate applications. And as mentioned in the keynote, we have to move the apps from the traditional IT to the cloud. But we have to prioritize the different apps where we can fit them, rehost to put our native applications in the cloud. So it's a journey. It's a path. We have to know exactly how many apps, what are the characteristics, and then decide how to move from the traditional IT to the cloud. So we have developed a complete program, a time schedule, and we feel that in the following two years we will be able to move most of our apps that are currently running using traditional IT to the cloud. A lot of what we do with our customers is that application portfolio assessment. So we sit down and say, let's look at the entire app portfolio and essentially tag which types of applications need to be moved as is, sort of lift and shift versus which types of applications could be refactored entirely into a new model. We're doing this inside HP IT. As we separate the companies, we're building a lot of our new IT systems on Helion and doing that same assessment and rebuilding applications to the new platform to cloud native styles. But for most customers, they have to have a range of capabilities. Some is just running a virtual machine, some is running in a true Paz or SaaS like environment and all sorts of shades of gray in between. So what we do that most successful engagements we have is deeply understand the portfolio of applications and help the customers understand what's ready, what's not and then what are the options along the way. So that's part of your services organization. Yeah, it's part of our assessment that we do through services and there's two parts of this, two sides of one coin. There's the assessment and making sure that we have a cloud platform that meets a broad set of those needs and that's what the Helion platform really is. Everything from infrastructure to full platform as a service. Yeah, so I mean that's the lifeblood of any IT is their application portfolio. And you have to care for that very carefully so you're identifying apps that can move, should move, maybe shouldn't, you just leave them alone. Okay, so that's part of it. So Gonzalo, I have the same question I asked Bill but in reverse, so you've got the top HP executive, he's got all the resources of HP at his disposal. What would you ask Bill when he comes to visit you? You know, we just had a meeting with the people from HP Ecuador in order to decide and to agree upon which are the next steps to go through this path to the cloud. And I think one of the principal topics and issues is to have the people at HP Ecuador, at the channel and also the customer will prepare to go through this path together. That's the only way to guarantee the success. We cannot go along, it's not HP, it's not just the distribution channel in Ecuador, we have to put all the effort together in order to be successful with the project. You're looking for a partnership. Yes, exactly. And a big part of that initiative. You have to invest, you have to invest for that partnership because it's a long-term relationship. Where do you want that investment to be? Is it people, time, transfer of knowledge? Education, that's a very specific topic. You have well-prepared people with the proper attitude that you diminish the risks of an accessible project. How much of the relationship gets into, beyond the technology, into the people and process side where the really hard stuff comes in. How do you work together in that regard? Yeah, education is something we hear all the time as people are trying to understand that journey to the cloud, that transition to the cloud. Because it's one thing to have the technologies. It's quite another to have an existing IT group or development group says, I don't know what to do with it. I don't know how do I even begin to make that transition. And then from a management point of view, how do I organize for this? What's a DevOps org chart look like? I get that question all the time. It's sort of a silly question a little bit because you wouldn't have a DevOps org chart. But what they're really asking for is, as I make that move, how does the org and my people move with it? And what's the right speed and cadence to do it? And what type of group should do it? So we hear the education question a lot and the training a lot. And the way that we address that is, we have a set of service offerings and content, of course, depending on the customer needs. Sometimes we actually do full education classrooms on site with customers and walk them through training side by side. We have some scenarios where if a large service provider wants to learn how to operate Helion, we'll bring them to our knock, our network where we run our public cloud. And they sit side by side with our operators to see how we run a live service. So it depends on where the customer's at and what they sort of need, but it is very much a common requirement right now. So, Gonzalo, what about the DevOps situation? What are you doing in regard to DevOps? Or sometimes I like to call it ops dev. There's a lot of times what people are doing is they're training their operations people to be more dev-like. That's probably the more common situation that we see. What's happening in your operation? I think that one of the key points to assure the success of these kind of projects is to involve the strategic personnel at the business. So cloud is not just an IT innovation project. We have to use EA enterprise architecture in order to check the goals of the business and then how the cloud change business. Not just the business, it's changing the way of living. Especially in the utility sector, for instance, we are using smart grids. That's mean electrical vehicles, smart home appliance. So we have to put everything, cloud, internet of everything, communications. So we have to have an holistic view of the way of living, the business, and then the IT to put everything together. So let's talk, I was going to ask you about the internet of things and what you're doing there. Smart grid you mentioned. Smart cities. Smart cities infrastructure for electric cars. Yes. All right, and that's a lot of data. Yes, all right. So maybe you could talk about that a little bit and how that's, so to give us a roadmap as to where you're going there. Well, in Ecuador we are deploying a smart grid program but in order to deploy all these initiatives, like smart homes, like electrical vehicles, you have to have a very strong electricity network. You have to have a very good communication platform. You have to have the cloud in order to use all those IT resources to have better way of living, better public services, better electricity, better water supply, better waste management, better security, better, improve the safety. So it has to have a holistic view and the focus is people. People, business, and IT. Now how about new apps? We talk about the cloud native apps, mobile apps, OpenStack, what are you doing in that regard? Is that a sort of separate initiative as you sort of slowly migrating existing apps into that new world? How are you bridging and what are you doing in terms of the new sort of application development paradigm? We are slow moving to the cloud because we have to be very careful with cybersecurity. Cyber security will have to be very careful because we are not just IT, we are OT people. We are in charge of managing the infrastructure of the grid. But we have, as I said, a time schedule, a program to move those apps from the traditional IT to the cloud. We feel that in the following two years, we will be able to have those apps running within the cloud. Yeah, because your customers want you to go there, but you have to be careful getting there. Yes, exactly. Otherwise, maybe we will be exposed to some cybersecurity problems. So this is an interesting example, Bill. We're almost out of time. I'll give you the last word. We're always talking about the digital economy. You guys are calling it the idea economy. Every business is going through some kind of digital transformation. Your industry is amazing what's going on there with data and digitization. So, Bill, I'll give you the last word. Where do you want to take customers like Gonzalo over the next three to five years? Well, instead of saying Gonzalo, they're the type of customers that we work great with because they are solving a large business. I mean, it's energy for a country. This is a utility. It's not a website for reserving a rental on the beach. I love that service, by the way, but this is a different level of criticality and this is where HP shines. Where we can come in and help a customer be aggressive in their goals, but without putting their business at risk. And so we can come in and help with the assessments, but also with the technology to help them get there in a fast, but logical and pragmatic way. So when we look at these transitions, we start with what are the business outcomes we're trying to drive, right? It's not just, can I get a better VM for cheaper? Can I spin up object storage? Or do I have a Node.js framework for our NAPS? We don't start there. We start with what are you trying to achieve with CENSA in Ecuador and your target markets? And then we work back from those business goals to say, okay, what are the technologies and solutions that can help you reach that as fast as possible? So one of the learnings I've had over dealing with many, many customers with cloud computing is really identify the TCO, the ROI, whatever metric you want. Identify the value at the workload level, not at the cloud level. Don't say like, should I go to the cloud? That doesn't make any sense. Ask the question, if I want to go and get better analytics from my substations, what's the improvement you want to see? Do you want to have more insight or 30% cost savings or higher performance? Like measure as discreet as possible for that given workload. You can then make the decision, should I use these technologies or not? And when? Right, because in some cases, infrastructure as a service might be all they need for a while. In other cases, you might need to write a new app. But until you have that discreet understanding, it's very hard to do. And that's what we specialize in. We can go into industries and verticals like utilities or financial services or federal customers, whatever it may be, and deeply understand the context of their business problem. Sound advice, Bill. Envision the business result. Start there, don't start with the technology. Gonzalo, great story. Thank you very much for sharing that with our audience. All right, we're extracting the data. You want more data, go to wikibon.com, check out all the free research. Siliconangle.com's got the news. Siliconangle.tv, we have videos like this up very, very quickly. Huge video archive, check out crowdchat.net slash HP Discover. We got all kinds of crowd chats going on. And also HP Discover.social, it's a stream of social data from HP Discover. This is theCUBE, everybody. We'll be right back right after this.


Everybody forced here ripping four of the 2020 to zero cool jack-ass trading card boxes for Jason s. Thanks, Jason Good luck me. I'll see you a nice auto one of these boxes or maybe a couple autos And just again, I'm not gonna be showing any of the graphic cards the nudity There's the thing Got a nice one. This was a beat-up around the edges All right, turn on the Mariners game we have ESPN on right now Uh field goal behind the lens Jackass 3d movie poster it looks like That looks like the cast and crew there or at least the actors Then I can't even tell if that's nudity or not. No, it's not.  Oh, man. That looks out. That's terrible. Come on. He's a chrome now. Come on Behind the lens there. I can't show that behind the lens A chrome and ghanu card there cup test chrome Eric Andre And cup test hockey Yeah, I think I knew this year. I think they made them before Yak charge Can't show that machine gunny kelly legend Sean cliver And cup test pogo like all the cup test cards are showing up chrome color coming up here after uh men underpants Blue 50 of 50 Is uh like a movie poster there Cannot show this blue to 50. It is called pontosaurus cannot show it 50 50 blue on the pontosaurus And I can't show the back of it none number or no number to 100 on this one is behind the lens Really good pack there. It's like three number cards and then a uh Coffee truck prank. I'll just keep on the base over here got uh toro totter Another card I cannot show Matt Hoffman Preston lacy And bush of bees which I cannot show uh tiny toilet Oh, I wish I could show that I'm not gonna show it though. Um Behind the lens here machine gun kelly Another jackass forever some people never learn crew there And the bull magician party boy Oh, man, uh, it's behind the lens Got zack holmes rookie chrome Red to 25 To the same card to 100 a minute to go behind the lens Not showing that card Big red rocket behind the lens Jalen ramsey uh lance banks and the backdrop All right moving on ox two Let's see an auto Classic the high five one of my favorites behind the lens there bed of nails chrome non numbered behind the lens chrome And milkshake uh can't show the helicopter got behind the lens jackass number two rachel wolfson And a scorpion lip injections field goal Behind the lens rob dyrdek rick cossack And zack ass lens to 100 cup test pogo Also to 100 behind the lens Slime by the ponosaurus bed of nails pk suban stevo chrome johnny noxville And marquee explosion beauty and the beast not going to show that one hold these for now on Uh jackass forever Can't show that one. It's one of the whole team though And the jalen ramsey tackle yak charge Behind the lens Chrome beauty and the beast Chrome francis and ghanu and icarus metan underpants behind the lens ghanu Loomis fall and hurricane slide That one's pretty nice Toro totter not going to show that behind the lens card Get a jackass forever high on poopies human ramp tiny toilets Behind the lens machine gun kelly Johnny noxville and electric tap dance two more Field goal not going to show this one spike jones eric andre chrome And slime by the ponosaurus poof behind the lens daniello tool brick cossack marquee explosion bed of nails behind the lens a movie poster chrome bathing beauty And jalen ramsey tackle the high five behind the lens dark shark stevo And scorpion lip injections. I'm not going to show that one as the pukano behind the lens eric andre chrispanias And quiet game poopies up in the tail and the donkey behind the lens a movie poster Jasper and ponosaurus jet ski Behind the lens chrome baby alligator chrome behind the lens And musical chairbags exploding room Behind the lens dj paul Lance banks and the mush which I will not show kind of weird a lot of color coming up visible man It's 100 pin the tail on the donkey Got an auto here shunt cliver to 50 There we go. There's an auto 50 on the shunt cliver got a red department store boxing to 25 and milkshake helicopter not going to show it behind the lens Movie poster That has some nudity in it. It's like a shot of the whole crew and zakas one more behind the lens movie poster there got the mini loop chrome and musical chairbags bed of nails behind the lens eric manaka Oh nice a gold it looks like yeah gold at 10 That's a nice card and the mush can't show it beauty and the beast Um, this is behind the scenes of the sweat super cocktail. I'm not gonna show that frances and ghanu shunt cliver milkshake yak charge Butt chugged to 100 on the chrome can't show it Nice, that's awesome. Do it a gold dark shark auto to 10 That's pretty cool dark shark to 10 Loiter squad if you all know that loiter squad, that's the best lute of 50 behind the lens with tony hawk and scorpion lip injections and underpants behind the lens machine gun kelly noxville and zakas Stayed in hope it doesn't like linger whatever it is slider dude insane Uh, toro totter behind the lens movie poster Can't show that one's got a little bit of nudity in it and ponosaurus uh field gold It's behind the lens. You can't show the front of the card pk suban stevo Pontosaurus again can't show it Tiny toilets behind the lens Is a Irving and gloria chrome I can't show it chrome and ghanu and marky explosion party boy behind the lens matt hoffman lance bangs and jaylen ramsey uh big red rockets behind the lens which i can't show jackass 3d Zach holmes rookie and flight of icarus and that is going to do it. Thanks again jason. We'll get these right out to you