Hi Bonsoir and we want to Talk with you guys about our experience with open-stack and Installation in a financial institution. We are working for BBBA This is a Very big bank very big High number of Customers a lot of people working with a Lot of money well really the money is not ours It's the front our customers Why it's interesting organization and Why a bank Hasn't one billion of customers, you know, there is no banking in the world Which has one billion of customers? However Facebook or Apple or other digital companies has one billion of customers of 500 millions or so but banks now why Because we we can't it's a problem with infrastructure the infrastructure Which banks are using right now is not a scale not only on the sense of physical constraints, but the business model behind that Behind our business doesn't support that the scale In consequence we have a mission from Rob as you know and Everybody knows them films of Blue brothers, yes Well, we have the same Mission we have to save our company because there are a lot of digital companies taking our place For example Apple or Google We have to protect our developers giving them better infrastructure better Means in order to them to develop application applications are the mean we are giving value to our to our customers In our vision, we need a self provision infrastructure. We need a infinite infinite Scalable infrastructure With in a active active Configuration with a hybrid that data model Distributed private and public data both between Hybrid infrastructure and public and private cloud and having a programmable infrastructure in that sense Traditional SETA is not the able third is the IBM mainframe In that sense That infrastructure it has a lot of physical constraints, but it's more important the Business model constraints and we have to move our operation to better infrastructure Prebate cloud based on on open stack and both public cloud With a programmable infrastructure will can build a better better Application development life cycle including not only the code Including the infrastructure definition to Using that life cycle to develop test and Go to production or review maintenance both the Application code infrastructure code you have the same life cycle for both things But for this you need a programmable infrastructure in our plan is to have first a private cloud using Open stack In fact, we are in a couple of weeks. We will have that infrastructure in production with a real application real banking application and Next year we will have the another instance of Private cloud in in Mexico will have our operations our data center corporate data center in both in Madrid and Mexico Well Hi Good afternoon everyone today. I'm talking about how we design and build our open stack private cloud But first of all, I'd like to mention the world we have with the projects first of all is to provide the digital bank with a private cloud infrastructure similar to Amazon or Google in order to To work towards the cloud to do the same thing we are doing with Amazon or Google But you know in our internal network in our in our internal cloud The second one is to promote a cultural change within the within the bank We like to move from different groups for example security communication networking that works as different silos for each other with a lot of bureaucracy with lack of communication to small projects managed by a small or medium groups with different roles that start evolve finish and maintain the project The third one is to automate everything This is to automate virtual machine lifecycle to automate application deployment security network Almost everything that you can automate and finally To have the possibility of deploying application in a multi cloud way So we have some products in which we are using the services from Amazon or Google And how do we use it? We use it via dashboard via SDK, but mostly via API We are using also continuous delivery tools like Jenkins or Atlassian bamboo and cross-cloud libraries like for or g-clouds So why open stack? Because this is the product that give us the possibility of realizing of our goals Also because it's huge community not only members, but also companies its maturity and the innovation in parallel the interoperability and also the flexibility that it give us to change different solutions within the same underlying technology and Why read that? Because oh, I forgot to say that we are starting with a ice house Release we have tested some releases and we we are starting with I house and what read that we are working with different Providers and they give us not only a simple open stack installation They give us their expertise and also some other products to work with open stack and to make our life easier And how are we planning to use it? Well? I'll mention three topics the first of all is continuous delivery The second one is agile methodology and the third one is DevOps methodology or sec DevOps in this case Because we want to mix people from security to the team. I told earlier We are planning to give each project or team with a tenant and the possibility To link the tenant with the continuous deployment tool and also the possibility to link this their tenant to Another clouds so the tenant will have certain capacity and therefore they can work in a They can move to the cloud So open stack there we go. We have a couple of environments here Pre-production and production the idea is simple here is just to test everything in the first one before moving to the second one about the hardware we choose HP and Just to say that we have different nodes for different things I mean there's for example the cloud controller or compute nodes or administration nodes, which has more gigabytes of RAM Than for example, Swift however, Swift has obviously more more disk And what about cylinder and glands? Well here? We have several options to investigate new technologies such as a cluster fs or or theft to choose a well-known provider or a mixture between both We have decided to start with netapp Because our background with them because they are in the because why they are in the community They have some plugins for for open stack and also because we have found Some features that we haven't found in other in other cases. For example, they have a very good cloning Solution very good a snapshot in solution. They have the duplication In where you can deploy for example 20 bitron machines without having to copy 20 times the same image to the compute nodes or The storage tiring in which you can classify the storage in in several parts For example bronze gold and silver type of storage So open stack there we go. How we deploy the infrastructure we use for that for a man plus puppet We found it. We use the version a style path, which is the open stack installer plug-in for the format Here in the format we have defined it several host group once per open stack component and in these host groups we can Customize you adding some puppet modules So therefore we have the whole open stack Services with a puppet with a puppet module and we can Change their configuration in a centralized way Here is an example of some classes some puppet modules and classes and Also, we have Develop on our own Another another modules not for open stack services But also for another services that we are using in the installation like security services or and so on People from redact have helped us to to do this this task in In a complete way So open stack technical details. Well, this is not very technical, right? Yeah, I Wouldn't know this We have we want to to Open the access to our open stack to the internet not only horizon But also the public of the the API is so that's why we are here a couple of rulers in hi with Different internet connection with different providers as we usually do in the bank and then the big blue cloud so Yeah, the entry point of our open stack is the firewall on top Where there is a style and IPS to analyze traffic The firewall has access to a DMZ subnet In where public Components will be placed Also to a router which function will be explained later and then the router has access to the open stack management Network which is the main network here and I Will explain it also and here there are two other networks This one the service subnet in where we have place DNS and NTP It's used to install the open stack components Here at the bottom we have the BBBA internal management subnet And why because here we can connect our open stack platform to the BBBA to our data center via this firewall and here with some Management components and security components will be placed for example here we have a follow a color code the Green one Is belongs to security people from say the security group wanting to collect logs from the entire infrastructure and also to collect network traffic Then they have also another component with security staff that they are researching right now in order to to make the Infrastructure more secure then we have the yellow one Which belongs to management? Mostly to the system administrator group Here we have a couple of nodes with red at enterprise by virtualization From which we manage the complete the entire infrastructure This is connected to the NFS storage via this other network As you can see there are also a nice use virtual machine and a foreman as I explained later here Almost every component is virtualized. There's no physical node now And about the question why to put DNS and NTP here in a service subnet and out here in the BBBA internal network because We don't we don't want to to have traffic from the management open stack subnet to the BBBA internal subnet we only want to From from this to access here collect logs or traffic or whatever and no more It's kind of a security reasons When here we have switch the color code the green one belongs to to the open stack components Swift uses another subnet in order to perform the triple object copy, and this is the first node We have in bar method not virtualize About glance and unseen there as I told you before here We have the NFS storage cabin which is connected apart from the red at enterprise virtualization node to the management of the stack so Here is the way Okay, let's see the the DM said Here when a request comes to our private cloud it passes through the firewall and Reach the load balancer the load balancer just do load balancing. It's okay and then pass the request to the graph and if it's okay pass the request to the horizon and what what happened when the There is an api call api call The graph passes the The request directly to the load balancer of the cloud controller Obviously when the request in the previous example reach horizon then goes to the load balancer So as we open our private cloud To the internet we have to take some security so security Risks and we don't want to to have attack we want to prevent attacker From reaching our internal network. So that's why we have The wafting here the IPS and and so what? About the cloud controller, okay I forgot to mention that the horizon is Isolated is not within the cloud console controller, but for the same reason if someone can attack the horizon maybe then they cannot reach the internal network and The api's are within the cloud controller We have installed it in three nodes and because this was a readout recommendation for ha and also for some components of Open stack that needed an odd number of of services and We thought that three is a good number And we also have my SQL and rabbit MQ isolated We got could have put it these these services within the cloud controller But we have to we'd like to to manage it manage them in a different way. They are installed in Cluster mode with peace maker in a couple of of virtual machines And here appears the no bad compute nodes there. They are also physical and Here is where we can we are going to deploy the virtual machines The virtual machines we are we are deploying Copying the Amazon easy to format will have an ephemeral disk it 8 gigabytes This disk is placed in the same physical node that the Nova compute because this is cheaper and and also this is faster if If the people that manage the virtual machines wants more more disk they have to ask for them to the NFS storage And hey, what about you turn? Here is something miss. So I let the floor to my colleague Danny, which will explain the defect Thank you Yeah, hi everyone My name is Danny I'm going to talk about the integration of Noise BSP in our open-stack deployment at BBBA I will be fast Because we haven't too much time, but anyway, I have very interesting and useful for you Go with the first point With the reason that we choose to to use SDN solution different than standard and neutron approach Well from innovation team As my colleagues explained before We was working automation tools a fast way to deploy and It's a requirement of for for the future to do this that way, but Remember we are a bank and our security team Used to apply strong security Policies to the traditional IT and now with the cloud environment they they feel some afraid For they they feel that everything is a funeral everything is dynamic In the deployment way that we start to work Sometimes start to be outside the the security business flows And they request for us some kind of of solution to to take control over the deployment By the business request we need to have a solution that is possible to scale and Without too much headache and Geographically distributed in between in remote data center In In for innovation team we have in in our roadmap of Technologies to to introduce in the organization that's the end solution We felt that The project of the player open stack in the organization is a good point to start with this technology When we decide to go with SDN solution we was we were testing some some solution And we decide to to use a noice BSP Well, why noice? Noice is SDN solution that One of the more powerful future for us is the Astration that they call domain templates that's a low our security team to define the The network security topologies And by this reason they this request I'll I'll solve Have a user role system that allowed to isolate the administration task that inside the organization there are like different Technical teams and we need to isolate the task in the same tool Moreover automation When a VM VM is a start in with noice Automatically is assigned to a subnet and security policies that define before the Security team is automatically applied to this to this VM has a Ritz-Norbone API Have the distributing distributed routing and switching It's very powerful Now Eliminate the single point failure of Neutron Network node and Bring us the the possibility to grow up with larger three communication And it's hypervisor and nostic. That's important The integration is so easy via Neutron plug-in We start to To explain more in details in the same the the next slice The Operasta The noice integration open stack. Okay To explain the open stack The noice Bsp integration in our open stack. I need to explain The components of noice solution The main components are the virtualized services directory The virtualized services controller and the virtual routing and switching also a digital component is the virtualized services gateway that we needed to communicate the BNs with the Internet here you can see the Noice component in blue and the rest of open stack component in gray We start to talking about the BSD The BSD is the is where we define the policies And the network Have a recipe I on a web interface where I went define all this And XMPP is used to To a chain the information with the BSC and and be a G the BSC the virtualized services controller play the role of SDN controller and send send a chain the the configuration to the compute nodes via open flow entries and use mp BGP to a chain information with the rest of BSC and be a G the BRS is the The software agent that is the installer in the hypervisor and create the overlay data plane with VX LAN protocol and And and they keep working without the BSC Running that is what I say before that is is a good point and the BG is a element It's a physical element that Understand BX LAN and translate to to build LAN and in our configuration we use for a Floating a pizza a pro ads to connect the VMs with the internet well This is the components of noise and integration as I say before is via neutron plug-in Is installed in in our control in cloud controllers? And told it only with the BSD and be a race a bi Well more about the integration And once have some kind of a fashion that we need to map with the open stack as Russian there are a lot of ocean and by the business need we decide to to map the domain with a project in open stack and and we and made a customization of horizon to Automatically in the in the time that we create a new project inside the horizon to open stack DLD instantiate our domain template As you can see here. We add a new tap in the horizon menu when you create a new Project and here is a scroll where you can see The domain templates that the end user cool instantiate and The next screenshot is from the BSD dashboard where you can see the The domain template definition as you can see it here is a domain template definition And from the horizon we can instantiate in the same time that we create a new project Okay This all is about the integration of noise with open stack We would like to to talk a couple of features that for us are important for our decision and for the use of Open stack with SDM one of these is the The domain templates use as you can see in the picture is a screenshot of the BSD dashboard Where you can see a domain instantiate it and here is a green check that told us that the ACLs are forced from the domain templates when End user instantiate a new project the ACLs as you can see here are a force from the security team and this is So important future for our security team because this way they have to control at deployment time And it's very easy to to define the domain templates as you can see in the in the screenshot There are object to define the flow and inside its flow you can define the Allow it boards for a hand for example here. You can see that we allow HTTP and HTTPS For any to a zone in a zone is another level of stretching where you can Create subnet and in the bottom you can see the like open flow style ACLs that are applied other Good feature that the noise Brina's is the service chaining the sherry chain and allow us when we publish some TCP board and redirect the traffic for a different path that is easy way to Insert a new element for analytic or ideas on some kind of stuff for security That's all for integration and was I I Passed the the floor to Gemma to continue Thank you. Well and I Want to start with you some experiences takeaways for in our project You can see that that takeaways are more related with cultural change on organizational change because in fact technical or architectural questions are very Has a have a very good solution in collaboration with different companies Rehat or no as networks or other companies Intervening in in this project first is We'll have to organize Your development in order to consume the in a different way infrastructure because you can program that that infrastructure is completely different to Current approaching in companies normally in companies you have people working in infrastructure building Storage or systems, etc Take more than week or two weeks to have a Server written machine in order to to have or to do some tests First you have to Change your organization your way to to consume infrastructure and the second is the organization of the project itself and Our organization is very very complicated is Well, I think your companies are more simple, isn't it? No really not Big companies are complicated because are big and there are a lot of people a lot of politics It's fundamental in that kind of project in OpenStack Projects to to have one team working together Physically physically together if it is possible Taking people from security Working our systems Focus them on the final result of the of the project the Our goal is was to to have an infrastructure working in six months from from scratch and We win is it is fantastic because the team is one team We work very well with this approach Well, next steps. Well, we are thinking the same things you are thinking about OpenStack next versions how rolling up to the next version We are right now in nice house version. I Don't know if we are going to you know, or we are going to kilo But our goal is to it change the version one One time per year. It's a good and it's a Very very different goal to the to other infrastructure where Probably the same version is running for years Dockers theft and other approach to the storage compute different compute nodes different hardware We have a lot of things in there in our roadmap This is our team and I Have I want to pay to you to people who come Came here. Well, there is people here who is here like Philip or Jonas It's a fantastic team. We build up fantastic Group of people working together and I at the end. I think it's the best question related with that with this project I We are looking for people who knows about OpenStack if you want to send me A resume well, it's I am open you can find me Okay Finally remember we are Have a mission from God. Okay questions Yeah Yes, it's a very good question Starting the project we made a business case Analyzing every coast in intervening in the project Discovered that our cost over time Are converging with the Amazon coast more or less Coast we see of course This validate our our project from a cost perspective But most important thing for us is to integrate Agility and giving developers new tools in order to develop application In a more agile more with more speed. It's more the most important thing is is that The cultural change is so important We have we want to introduce we are at the end. I'm innovation team We want to introduce not only the technology, but the cultural change Changed minds of people who are working in traditional it If we have around 6,000 people working in in it Mostly in Spain and other countries If every single Person in that organization change his mind, it will be fantastic because the power the powerful Will be virtually infinite This is our vision Yeah It's our installation is right now Small because we have around 30 servers from HP the question is at the end We want to check the feasibility of of doing that thing inside and Grown that infrastructure is very easy We dimension our private cloud for a set of Projects inside the innovation area, but we are planning to extend offering that offering for other areas if We will matter that the consortium Making trends and Plans Grown Grown sub infrastructure when it needed And Yeah, we start with one that data center, but next year we will have another instance of that cloud in Mexico. We have two couples of big data centers to in Madrid and doing near to Mexico City Not right now we integrate our integrating Sail matter are you referring to sail matter or other? Well, we have different reporting capabilities something Some some one related with security. We have a powerful platform of security taking data from WAF with application firewall a learning We are introducing a self-learning web application application forward in order to a feedback the front end of of the APA Taking every information about the locks of the of the different components Analyzing in a fraud platform And Using sail matter that we can have information about different components of of the Our installation The loss balancer Virtual machine and it's used only for high ability of the openness that component Is that question? No, there are physical appliance but that firewall are Have Roles Define it is not the dynamic dynamic roles are applied by a new term by Noise network solution not now because our installation is so small small We only need authentication for DevOps people and DevOps people are Very small amount of people are is not necessary right now probably the platform grounds up we will need some authentic authentication system integrated with our LDAP or something like that Both We want to well for us. It's so important to have a platform in production with real application and to demonstrate that That concept using open stack in a big company is feasible The first intention is to to provide developers some platform where they come Set up virtual machines immediately But in second hand we want to put Production production Projects in fact that I think in December maybe in January the pen it depends on the Production calendar a schedule We want we will have an application from our Internet online service banking online service in Spain running in in our infrastructure One part of that project I Think it's very good because we demonstrate that open stack is so powerful Yeah Yeah Well, I Think it's Our vision is to separate Providing infrastructure to application right now in classical Companies are mixed you you have silos and you have the application risk application And you have an specific People running an infrastructure service storage Operation etc for that application Our vision is to separate infrastructure Have a common work with specialized services, but a common infrastructure programmatic infrastructure and All those people Can't be not so An amount How we will have right now we have a lot a lot of people doing this The other people will will be devops people working in in applications I don't know. I I think it is a very good approach to have people integrated because normally are more Engaged with the projects It's our particular vision Can you repeat to external developers? Yeah, yes, absolutely. Yes, we want to offer in Well in different ways I am let's say Official projects where people Devoting to to that project and with a specific planning and to give Developers some new tools in order to check new technologies. I don't know for example new version of MQ the developer wants to check it and to have the ability of Set up a new virtual machine in seconds and test the that new things is very Convenient for us. Okay. I understand. Yes When we start the project with with things in the fall stack But at the end we prefer to concentrate over the first thing that is infrastructure as a service Probably we will we will have club foundry or some past in place. I Don't know if next year it depends on Necessity for example in big data area. We are testing club foundry right now over other infrastructure if it's Successful we will put in place, but I don't know right now Yes Yeah, it's now a question Thank you. Thank you very much


Hi everyone, Joe for jazby's casebreaks.com. Coming at you with our last filler to unlock that hip parade basketball dual casebreak. I think we have like three or four full spots left if you're watching live. That's all we need to do. No more fillers after this, just full spots. Let's do the pack break first and we'll give away eight spots in that hip parade basketball dual casebreak. Big thanks to this group for making it happen. All 30 teams are in and let's roll it and randomize it. Five and a two, seven times for names and teams. One, two, three, seven. Got Nathan. Five and a two, seven times for the teams. One, two, three. All right, so there's the first half of the list right there. No trade windows and filler breaks. Second half right over here. Let's print and rip. Oh no, I got to print on the other printer. Sorry, my printer's out of ink. All right, TWC trade window closed. I'm gonna pause the video. I'm gonna go print this out. I'll be right back. All right, got the print out. There it is. Thanks everyone for getting in. Let's see if we got any surprises in here. 2019, 20, Lucca Donchich draft class, I think. Okay, Derek Rose, Kevin Porter Jr., Cameron Johnson, Jordan Pool being traded. Darius Garland, he's pretty good. The rest of these are just comments here. All right, not bad. But even better is who's gonna win those hip parade spots. That's like eight hits in this pack in and of itself. If you wanna think of it that way, let's gather everybody's names one through 30. Lucca, 18, 19. It's all blurs together now. Let's roll and randomize two and a six, eight times, top eight after eight. Good luck. One, two, three. All right, so from nine, sorry, James, from nine through 30, sad times. I appreciate everyone giving it a shot. Top eight, happy times. Sunny is happy. So is Ryan, Nathan, Kevin, Tristan, Sunny, Eric, and Kym, congrats to the top eight after eight. I'll see you in the next video for that hip parade dual case break. Go to guyspeakcasebreaks.com, bye.


Hi all, welcome to the regular Jenkins governance meeting. Today is May 5th. We have several contributors on the call. So my name is Alec Ninovich, I'm one of Jenkins governance board members. So Uli Haffner is also a Jenkins board member. Mark Ways is a documentation officer and documentation special interest group leader. And Mark Jackson is a leader of the Advocacy and Nutrition Special Interest Group. So at this meeting, we just discuss what happens in the project and discuss and make decisions on key items submitted by the contributors and the developer may at least like voting for particular issues, et cetera. But the most of the discussions happen in the mailing list and this is a section, a session to just formalize these decisions. Okay, if you want to know more about governance meetings, so there is a page on Jenkins.io, Jenkins.io, slash project slash governance meeting and you can find all the information there. And you can also see the embedded document and by the way, here's our agenda. So we have a few topics for today. Some good news about the projects in Jenkins also my request for approval and hosting for Uli Haffner's first repository, ULI themes support policy and window support policy. So this is what we have now. And if you want to add a topic, just feel free to put it to the agenda. So, okay, I will start from roadmap updates. So we have a work in progress public roadmap for the Jenkins project. And there is a number of projects which are currently under active development. So you can see them here. It's actually quite a list. And we have some good news about these projects. So since the last meeting, there were multiple updates. First of them, that we finally named the official Docker images. So now it's Jenkins agent, Jenkins inbound agent and Jenkins SSH agent. There is a blog post on Jenkins.io with a summary. So it moves agent terminology cleanup project forward which we're handling and focusing on three special interest group. Then related topic, official windows images. So now we have official windows images for all the same agent repositories. We have continuous delivery process for them. We have releases and everyone is welcome to start using them. So they are considered as fully supported images and let's talk a bit about what fully supported means. Okay. Then another major update that the project by team Jack, Pauline, Newman, et cetera you have up identification support. It was at least as preview one month ago but now it's in J, so you can just go to the Jenkins Update Center, install a new version of GitHub branch source plugin and get the authentication as GitHub app. So you get higher rate limit using independent authentication and security, et cetera. So this is also an item in our roadmap. It's great to see that. And also there is ongoing development in the Google Summer of Code. Just today we have published the first video about proof of concept being developed by our student. So if you're interested to go to the Jenkins YouTube and you can find it. So this project in GitHub checks API for Jenkins plugin and maybe you would like to summarize the current progress all the way here. Yeah, of course. It was a really nice meeting today. We had a presentation of a prototype which already does a lot of things. So I now have a good feeling about that there will be a good outcome of the project. Of course, it's just a prototype and the code needs to be cleaned up but we already have a kind of design document and we know a lot of steps we should go forward. And I think, yeah, it will be a very successful project, hopefully. The fingers crossed. It's really important to the Jenkins community. So, yeah, thanks for working on that. And yeah, by the way, once you have this major updates please don't hesitate to leave the project description so that video, for example, is linked there. And hopefully we could have a blog post soon, who knows. Yeah, not now yet. Or do you think just for the prototype or for? Why not? If it helps to facilitate the feedback. Okay. Yeah. And same for other projects. So apparently all people on this call are mentors in one of GSoc project or maybe multiple ones. So if you have a prototype or whatever which would be a showcase, please do so. So Oleg, as a topic on that theme we've got an upcoming release of the Git plugin that will include symbols for pipeline and some other stuff. Is that a viable blog topic? Why not? Okay, all right. So that would be one where I could blog about it. Great. All right, thanks. Mm-hmm. Well, any blog posts would be appreciated because again, we want to share stories. We want to share improvements about the project and if it fits the user experience theme, yeah, you know what to do. We will talk about that later. Okay. Okay. So yeah, another thing which is coming soon, hopefully the next weekly is major update in system rate permission. I have an action item to discuss when would be the weekly release. So long story short, we have a pull request which is needed to finalize this story. And we need it for the next week for crowd testing with your UX hackathon because system rate is really important for users of integration is called. So there is a pull request from team which is waiting for reviews and more reviews who would be appreciated. It's here, extended system rate and extended for agents. So actually what I'm going to do, I'm going to ask core maintenance about having for this not on Tuesday as we're discussing now, but maybe on Monday or even earlier. So that we could start testing that. So there are three contributors who already tested that and I think that we could learn that. So yeah, I'm about asking for such deviation but I think it's really important for the project. So the idea then would be system read would be in a weekly build even at the launch of the hack fest. Yeah, we have an event scheduled to Tuesday about system read permissions with demo, et cetera. And by this time, it would be awesome to have it in the Jenkins victim. Well, as assuming that merge conditions are passed but actually they passed even now. I approve that I just moved it back to review because I wanted to test a bit more. But yeah, I'm happy to start the official measure come down so that we could integrate it tomorrow. Okay, so sorry for such teacher about incoming changes and ongoing changes but I think it would be useful if we cover it a bit at these meetings. And if you feel that we should focus on other stories, just let's discuss that. Okay, next important news. We have been accepted to Google Season of Dogs. This is our first ever year in GSOD and actually this is the second year of the Google Season of Dogs at all. What it means to the project, we will have a technical writer working on the project from September to December or maybe even long way for it's a long running project. And yeah, it's a good tip that you need to improve particular area of documentation. We have a number of project ideas published here for example, just like in documentation migration and update, documentation, documenting Jenkins on Kubernetes, recognizing user documentation and probably extending that and also creating new solution pages. So this is the project ideas we have now and if anyone is interested to submit more project ideas please do so. Thanks to Mark for submitting new be friendly issues, et cetera so that students can try contributing something. Apparently actually we got a number of pull requests and comment from potential mentors in this program. So you've got nine pull requests like Mark. That's right. Yeah, so and counting. So we already get some contributions and obviously we are ready to facilitate it. So if you have any project ideas, please submit them. So we have one month until technical writer applications start. So by that time it would be great to have all projects in place. Okay, so another quick update is Cloud Native Special Interest Group. So it has been dormant for one year. We had a long discussion at the Jenkins contributor summit in Brussels in February. In January and there was a consensus that yes we want to recover that. Yesterday we had a first kickoff meeting with those who joined the meeting. So we had around eight contributors there and we agreed to price it on this scope. So major change is important for the project that we rather switch focus to user stories. So it means your plugins within the CNCF and keep managing Jenkins in Kubernetes, Jenkins on cloud providers and other things you can see in the list. We still want to work on architectural changes but architectural changes would be rather scoped to focus on delivery and user features because before that the seat was highly focused on architecture or cloud native Jenkins and yet personally I'm not sure whether we really need a cloud native Jenkins or whether we need cloud friendly Jenkins and cloud friendly Jenkins for me is also a really good goal for this seat. Okay, if you're interested there is a recording that there are meeting notes starting from June we will have regular sessions but the seat is back and I will be updating pages. Okay, and yeah, other important update is Jenkins UI UX HardFest. So if you have participated in any community meeting over past two weeks you may have heard about that because we discussed it almost everywhere but yeah, the idea that we run a one week HardFest specifically focusing on improving Jenkins user experience and it's about user interface, documentation about sharing stories, updating tutorials, providing guidelines so that users can easily use Jenkins and easily can find the information. So right now we have three tracks. So it's user interface, it's user documentation and yeah, well it's spread the word I need to submit a pull request to fix that but yeah, just sharing whatever stories including leveraging the Jenkins the way program we have started two weeks ago which was approved at the governance meeting. So yeah, that's the plan. Currently we are aligning a number of events so he's a draft, we have already published a few of these events, others will be published by Friday and hopefully it will be a great event where we will have many contributors joining. Right now we have 50 RSVPs in our registration form and we have around 80 RSVPs to the opening meetup. Personally, I have no idea how many contributors we will get in total but yeah, our hope is to have around 15. So let's see. Any comments about that, any questions? So like the gathering, the contributors work, the repository that you proposed, I think that's later in the agenda, isn't it? Yeah, we can just switch to that actually. Ah, okay. Okay, so one of the challenges for us in this hackfest that it includes not only code contributions like submitting pull requests, that part is easier but it also includes non-concrete contributions. For example, reviews, user experience testing and also spread the word including submitting stories, posting about Jenkins, et cetera. So we need an engine which would allow us to record these contributions. As a part of discussions we discussed multiple ways to do that. One of the ways was to just have a Google doc where everybody would be able to record contributions. Another way is was to have a spreadsheet in Google forum is basically the same. But I actually suggest a bit more sophisticated way is having a separate repository where everybody would be able to submit their contributions. And this is what I propose here. So I'll briefly show it to you how it looks like right now. So there is a UI UX hackfest page. Basically it's just implemented in readme indeed. And it has some advantages being compared to the forum because we invite contributors to submit information about their contributions as GitHub issues. So for example, here I can submit the UI UX enhancement, bug fix or whatever area. And basically for each contribution we ask participants to summarize what they've done to share some links, to share screenshots, if possible. And yeah, if users submit such issues then what we will do, we will process them, we will include them to the list of contributors. So you can see it right here. We are using all contributors. It's a default, well, it's pretty popular engine which allows tracking contributions. So we will be putting them there. Also we can aggregate this information, for example, for daily summaries, weekly summaries and we can use that to generate reports when the hackfest is over. So that's why I propose using such maybe a bit more sophisticated engine but it will be hopefully more efficient in terms of collecting information. So just to reiterate, all I need to do as a participant in the hackfest is submit an issue to this repository and use one of the templates that's there to describe my contribution and that will have recorded that yes, I'm attempting to contribute. Yeah. So for example, recently improved, yeah, improved docs navigation part on Jenkins.io. So yeah, for example, I can just link my pull request. I want to do that because I need some time to find that. But what I can do here, I can just take a screenshot of the new bar I created. Yeah, I'm just showing it in live because it just to show how easy to implement it. Then yeah, link, okay, just user documentation. Then some other pull request, then after that, yeah. Improved the navigation bar. Yeah, now it doesn't take three pages. It's still difficult to navigate on a mobile UI but yeah, at least it's better. Yeah, and user doc sections can be easily found. So yeah, basically I report such contribution. Okay, here how it looks like. And after that, then somebody who reviews that, what you will do, we'll use the bot because yeah, I forgot the command but it's easier so that all contributors. So somebody reviews my pull request at something like that. Aleksey Nashev for documentation. So I will cheat a bit because I haven't submitted the documentation pull request as a part of this hackathon but please be sure I will do. Right. Okay, I just asked the bot to update the page. And here there is a pull request which basically adds documentation to the table. And that's it. So right now it has been added only to the metadata but then there will be incremental pull request which will update this page and it will set the documentation icon here. So it's a widely used engine and open source and I think the hackathon is a good opportunity to try it out. I will also welcome bot there. I will let other bots which summarize these issues and create daily reports. Again, together with SmartKey we've been at the JSOC Mentor Summit in Munich this autumn, last autumn, and there are at least two sections which were related to community bots and promoting that. So I have a bunch of notes and I'll use it as my playground if you agree that it's a good approach for sharing the events. I would love to help on that. I have notes as well. Okay. So basically what I'm asking here is everybody fine with hosting? So there will be something like seven plus ones in the developer mailing list. So does it matter whether it's hosted in Jenkins Infra or Jenkins CI? Does the organization which hosts it matter? I would prefer to host in Jenkins CI because they have admin access. So I can basically hack things quickly if needed. Okay, that suits me just great. Is that does that slow down any linking of pull requests into it? They just hyperlink into them with a pasted hyperlink and that's sufficient. They don't have to use the GitHub link of pull request facility. Excuse me. Well, it doesn't really matter because GitHub pull request facility works across organizations. It does. Oh, okay. Good. All right. So it impacts, for example, team mentions but to be honest, I'm not sure why we would need that. I will probably create a team for reviewers, organizers and whoever wants to help us update into this website. But yeah, that's it. Okay. So then ultimately this read me page will represent when it's, when as we get towards the end of the week, the read me will have on it pictures of all the people who've contributed. So we'll have 50 or 60 people as contributors there. Exactly. Nice. So that's my plan. Everything is more or less automated. So yeah, as long as we don't have someone who uses strange GitHub profile, et cetera, it will be easy. Okay. So if you're fine, I will just move it because I needed for the documentation update anyway. So transfer Genki CI, that's easy, right? Okay. I will fix the team access later. So I will create a new team, but then something happened. I still didn't understand how the things work sometimes. Where are they? But okay. So now it's hosted on Genki CI I will go to move the prefix. Okay. So yeah, it will keep patching it, but yeah. I think that it's a good start. So thanks for your time on that. And yeah, at least you've got it published. So any questions or should we move on? None for me. Okay. So the next question is about themes support policy. And again, it's related to the hackfest because one of the items we put there right now is support of the dark theme. And why do they, they would be interested to have other things updated to have a better marketplace for themes and other topics which are currently in the draft Google doc. So in order to do that, we needed an official support policy for themes because the UXC, when we were discussing this topic, there were a lot of concerns about how do we align themes support policy with the need to evolve Jenkins UI. So there was a pull request from me which is based on the dev list discussion. So at that dev list discussion, I guess we got a bunch of plus ones. Notably, we got plus one from Tobias who is a maintainer of simple theme plugin. So it's a key feedback for us. Then yeah, there was this pull request. Actually, I didn't intend to have it merged before the meeting, but I forgot to put on hold. Sorry about that. But yeah, I just, I still want to discuss it here and officially sign it off because the policy is basically that we don't provide compatibility for themes. So it seems that we can break the themes by UI updates which is must have for roadmap. They will have stories like UI overhaul. And definitely it's not something which could be delivered without breaking changes in layout structure, et cetera. So there was a page and right. Yeah, I'll just show the current version since it got merged. It's to be then managing. So it's here, themes for user interface. So yeah, this policy includes two bits. One is yeah, things are provided disease without any warranty, just taken from MIT license. Y explains why we need that guidance, how to report that and best practices for developers. So this is what was proposed in the mailing list and signed off just to use a better text. So my question to the governance meeting, are we fine with that being host disease or would we review it, re-approve it, maybe reverse it? It's just fine. So in this, just merge it. Or it is already merged, but... Right, yeah. Sorry. And I don't know how to say it. I clearly approve, I merged it. So yes, absolutely. Well, it's a post merge approval. Yeah, sorry about that. Well, no worries at all, it's my mistake. I didn't mark it that proper accordingly. And the mark was totally right to merge it because it's within the user documentation. So it's hoping the editor who makes the decision whether we merge it or not. And I'm not sure whether it was a good idea to put the policy in documentation, but yeah, I just decided that until we have something formal, why not? But okay, if everyone agrees, we can just approve that, approve. So we will probably make some updates during the hardfest and this pages, but it works. Okay, the next topic is a bit more interesting. It's about our Windows support policy. So Jenkins project is 15 years old and during this 15 years, so basically we had no Windows support policy at all. Well, and for what it was, we still didn't have Linux support policy or support policy for any other system. So the theory behind that is that if you're able to run support Java version, most likely Jenkins will work. And this is a good theory, but we have a lot of native code in particular JNR, JNI, we also have Windows Service Rapper and other components. So it's not guaranteed that Jenkins will work on any platform. And this policy basically suggests a change. It documents the support levels we want to have. This is what we discussed in the developer menu list. Right now there is no conclusive decision there whether we measure this document or not, because, yeah, so let's check what we have there. So we have some more positive comments about having policy in general, but you know approvals in the developer menu list for this particular pull request. We have approvals from Mark, from Team Jcamp and from Sliden about the policy. And yeah, I suggest to briefly discuss the meeting and to see whether we need to get the most feedback or whether we can publish a day's version and the iterative needed. And I think we should publish and iterate. I think it's adequate and beyond. So it's a really great policy to have even if we didn't know iteration. It describes levels of support and which things we're actively testing in which we aren't. Yeah, so there are some follow-ups which will come up to that and which are worth noting. For example, currently we bundle .NET framework to .Zero binaries. For example, for Windows Service Rapper, we want to go to for .Zero. Basically it means dropping support for Windows XP Service Pack 3 and so on. I'm not sure whether it's that important in 2020, but it's a big technical depth for the project to maintain to .Zero. If you look at the code, we have a lot of branches. It also impacts current Google Summer of Code project because there is no YAML parsing libraries which would support .NET framework to .Zero at the moment. So we want to move forward and basically drop compatibility of some Windows versions. Yeah, and our support policy is basically level one is just the latest supported versions of 64-bit and versions which we put in Docker images which is currently not latest, but at least we put it explicit. Then level two is whatever is supported by Microsoft which is 64-bit. Level three, it's everything else. So it's no longer support versions of 64-bit platforms, 32-bit platforms, basically all other exotic, well, exotic versions. For example, I spent a significant part of my career working with Windows Embedded. And the Jenkins works there, but I'm not sure whether we are ready to support that especially since we have no practical way to fix issues at the moment and to test that. So I put it to tier three. Same for preview releases, same for wine, arctos and other Windows API emulations. I have no idea where the Jenkins works there to be honest, but I definitely know that it works with Siegwin. Again, it's not something I would wish for the support, but yeah, whatever. And yeah, level four would be unsupported. So things which we definitely don't support. So it's Windows XP all the way there's a typo, all the way when service pack three, then I put Windows phone, just an education, edge case example. And yeah, basically any other Windows platforms before 2008, so. Yeah, no Windows Visto support, not now, not ever. Well, it's up for discussion, but with the current policy it actually would to be tier three. Oh, yeah, tier three. So I still need to fix spelling a bit before merging, but in principle, this is what I support. And Moeva wants to improve this policy, open the platform specialist group we will welcome contributions. Okay, so what do you think about merging that? Assuming that I fix typos. I'm a plus one. I did not comment on this PR because I don't know enough about Windows. I didn't sort of, it's a non-binding plus one, if you will. I'm plus one, I think it's the right thing to do. And I promise to continue using Windows and making sure that it keeps working. Okay, Moeva, what do you think? Yeah, for me it's a plus one. I don't use Windows, but I think it's a good thing to have it working because a lot of my students are using Windows and they would be happy if they can use Jenkins and Windows. Josh, you're just a gentleman in the middle of the meeting, but if you want to comment. Give me a moment to try and find the documents that you're walking out of. Okay. Yeah, so they'll shade in the comments. This chart, this chart. Okay. I think I need to bring my son to bed. So goodbye and see you next time. Bye. Yeah, thanks, oh yeah, yeah, bye. Bye. Yeah, I think we are closing down more or less. Josh, you used that. Yeah, so do we have any other topics for today? I don't have anything. None for me. Okay, so the next meeting I guess it would be as usual. So it's something like June 3rd, I guess. June 3rd. I don't care about anything happening on this day. So I think you just schedule it as is. Again, I'm not sure whether it will be Zoom or IRC. So let's see. I prefer Zoom on my own, but yeah, I guess that might be contributors who prefer IRC. Let's see. Okay. Yeah. Josh, would you like to finish the discussion here? Sure, I mean, I look through it in the preview, it seems fine. Sometimes I wear Windows hat, sometimes I don't. My current Jenkins environment does not, but I definitely deal with Windows. Overall, it seems reasonable. Is the idea that right now you have zero documentation as to what you support? Exactly. So we will gradually improve in this documentation. For example, we just updated web browser documentation when we were working on Java 11 support, we created support policy for Java, but operating systems is still a terrain for us. Okay. Future document will be, will include Docker, or will future additional pull requests will try to talk about Docker in a similar way. Okay. Yeah. So I left one little comment in the GitHub. There's one line, which is a little weird. Cool. Okay. The colon, the colon, windows, I don't know what it's trying to do. You mean this plugin? Yeah, like, is, is, is plugin colon windows dash slaves a proper name of a thing, or is it? Yeah, so it's a macro. This macro will basically resolve to this website. Ah, okay. Yeah. So yeah, this is a special case. As a happy maintainer of this plugin, I would say that I see no real use case for that on modern Windows versions. And just configuring this plugin to be working on Windows versions would be a good challenge. But yes, since it's still, they decided to reference it. Okay. Right. We know we have talked about slaves, but masters is still the canonical term for the other side. Yeah. So we renamed agents. So now there is no slaves. There are agents. Right. We have a project in our roadmap to finish the cleanup, because there are still a lot of things to do. But yeah, we just discussed renaming Docker agents before that we renamed the SSH built agents plugin. So these were two major issues, but still a lot of minor things here and there. So we will gradually clean it up. It's here, but so there is just a link to the epic. For master terminology. So personally, I don't have strong opinions. I know that Marki has. So I think that we put it on the roadmap to name something like Jenkins server or whatever. But yeah, right now there is no specific plan for that. Okay. So as a general thing, we at my employer are in the process of moving away from Jenkins, this is a slight disclaimer, but I'm always happy to help out with terminology and things. So when you guys do get around to it, please feel free to ping me. I'm sure I'll still be reachable. Thank you. That's great. Thank you. Yeah, I'm, should I mark and approve in the PR or? Well, if you see it's funny, I feel free to just approve. So basically all our pull requests and the Jenkins project open for comments. So yeah. All right. I'm happy with it. Thank you for taking the time. Yeah, it's perfectly fine. Thanks for your feedback. Okay, so my next steps there, I will fix a few typos and then hopefully we will measure them tomorrow after the platform seek meeting. Okay, that's all of these requests to agenda and thanks to everyone for your time. Yeah, I will publish the recording soon. Thank you all. Also you online. Okay. Yeah. All right. Cheers.


WTTC is very important in arranging a national or international agenda for the ICT telecommunication sector that involves all regions driving towards one goal for the upliftment of the sector to the benefit of all peoples. Well the WTTC itself is incredibly important to bring together the world behind one single mission and that mission is to ensure that every child regardless of which community share he is born in the world is connected to everyone else and it's connected to the world of information that is available over a communications infrastructure so that their lives are happier healthier better educated more productive. My hopes and expectations for this conference are to make broadband communication more available all around the world in every country in every continent and we also like to provide our part to this. It's the top policy conference in the BDT that addresses the development needs of the developing countries. Today the ICT sector is booming fast and in my opinion I think members of the union has to cater for such developments and the fast developments of the sector that's why being under one roof being under one conference such WTTC conference the needs and the developments will be freely discussed among all the members will be shared in very open minded with all the delegates and the resolutions or the outcome which are expected to be to be resulted from the WTTC is going to take care or tackle or cater for the entire membership whether they are developing countries developed countries or even least developing countries. We as sector members as the industry we create the technologies that enable people to talk enable people to work and do different kind of things now by development we ensure that everybody around the world even people from the developing world people from the developing nations can also be able to benefit from these technologies. Well the D of course is for development and for us that means capacity building it means helping people who are building networks to do the best job to make the network available to everyone. We in developing world have already been seen that it is coverage in many ways and mobile services are available to citizens in most places of the world and now we are living a next stage which is creating new services of broadband services and delivering the last generation of services to citizens and I think this is very important for citizens in all countries of the world. This conference will create great environment and strategic objectives of developing ICTs and in generally the new direction of ITU work especially in the field of providing broadband for population especially in developing countries. There is an expression of Albert Einstein it's in German sounds like fantasy is wichtiger als Wissen. This Wissen is begrenzt which means that fantasy is smarter or better than knowledge of science because science has its limitations and you know borders so I think that what we expect is that part of these discussions about the resolutions and the contributions and the interventions of other countries I mean the development is going so much together with the growth and we think that you know this conference will in a way to very big extent set the new limits and borders for all of us in representing the whole world.