Hello everyone and thank you for taking part in this Minikube session. My name is Predrag Rogic and I am one of the contributors to the Minikube project. This session has two parts. First part is an introduction to the Minikube project, where we will cover why was Minikube project created, what it is and what it's not, where we are now and what are the plans for the future. Also we'll talk about how you can join the community and start contributing to the project. The second part will be deep dive to local Kubernetes learning environments and here Anders will introduce the three different environments that Minikube supports. Hypervisor, container and bare metal. There will be details about each process once and some suggestions where would you want to choose one or the other. And since this is a recorded session, we'll leave some time for answering your questions at the end. The session time is limited to about 30 minutes, so let's jump straight on and talk a little bit about the background and explain which problems were meant to be solved by this project. So this here is a special anniversary for Minikube that started five years ago, offering the solution that would improve the existing single node local cluster experience in Kubernetes. As you can see here, the original proposal was not to deal with multi-node clusters nor to be used for production workloads. And as we will see later on, this original vision changed a little bit, but for the better. The primary goal of Minikube is to make it simple and easy for people to run Kubernetes locally for learning and day-to-day development, including testing and debugging. And the main guiding principles are to be inclusive and community-driven, user-friendly, to support all Kubernetes features, to be cross-platform, reliable, high-performance and developer-focused. Here are some specific design goals derived from those principles. Simple UX that allows setup and tear-down of the cluster with a single command as easy as Minikube Start and Minikube Delete. Unified UX across operating systems, support for local storage, networking, auto-scaling, DNS, load balancing, and so on. Minimal dependencies on third-party software as much as possible and minimal resource overhead, and we'll touch on this one in more details here. You can also visit the link to original design proposal document if you're interested to learn more. We're now going to see how Minikube development is reflecting specifically these principles and goals. This is an example output of the Minikube Start command. All it takes to bring up a local Kubernetes cluster in less than 20 seconds. Also, you don't need to install separately Kubernetes tooling needed to operate your cluster, like Cube CTL, as you can use the ones conveniently provided for you by Minikube, for your operating system and your architecture. Now, there are other great tools as well that would allow you to achieve similar things. That is to run Kubernetes cluster locally, and they are usually specialized and focused on a specific operating systems or architectures, container technologies, or virtual machines. Minikube, on the other hand, is aiming to support as many configurations as our users commonly use. And what you see here is not a definitive list of supported components, rather those that are being actively developed and thoroughly tested. So, starting from the lowest layers, Minikube runs on AMD64 as well as ARM64 CPU architectures. In terms of the operating systems, Linux, macOS, and Windows are supported. Next, it can use a wide variety of hypervisors and drivers, like KVM, HyperKid, HyperB and VirtualBox, then Docker, Podman, and you can also use an existing operating system, whereas native driver would allow you to use your local OS, and SSH would allow you to use a remote operating system. For Bootstrapper, we use CubeADM, and for container runtimes, we support Docker, ContainerD, and Cryo. Finally, while Kubernetes officially support just last three minor releases, we recognize that there are some users who are for various reasons, still using older versions, and so we support at least the last six minor versions that are continuously tested. Similarly, this is not a definitive list of all the Minikube features, more of an overview of the most important or recent ones. Currently, there are 28 add-ons you can use to easily install Kubernetes applications, and two of them are installed by default, and those are the default storage class and storage provisioner. You can see all supported add-ons with Minikube add-ons list command, as shown here on the right. To install additional add-ons to the cluster, you can use Minikube add-ons enable command, and you can also disable, configure add-ons, and so on. And similarly, to other commands, simply use Minikube add-ons to get the detail usage help on that. For the advanced Kubernetes features, Minikube supports a load balancer, node port, pod system mounts, feature gates, and so on. And there are now eight ways to push images and some of them allow fast load and building. To support the next billion users initiative and make Minikube more inclusive, there is a continuous effort to support non-English speaking people by allowing them to report problems in their native language by GitHub issues, and currently there are seven languages supported. Then users can have a conversation in their native language with the project maintainers and contributors, which would use usually the help of Google Translate. So sometimes it may sound a little bit funny, but you know, we're trying. And Minikube itself currently supports seven non-English languages like German, Spanish, French, Japanese, Korean, Polish, and Chinese. And there are also plans to improve it further and add more languages. And here we need help from your side. If you remember from the beginning of the presentation, initially Minikube was envisioned as not to support multi-node. But it turned out to be the most wanted feature user asks for, so that changed the original assumptions and adding multi-node support came into the focus. It's one of the examples of how the community is actually steering this project. So after a couple of iterations and going through alpha and beta phases, multi-node finally became GA in December 2020. Now, while adding more features, more tests are also added to retain reliability, but they also require more resources. And since maintaining a high performance is also one of the guiding principles, it has a continuous focus. And that resulted in improvements of 86% faster start time and 20% less CPU usage. These metrics are measured with each PR, so that we know if something would negatively impact Minikube performance. Here on the right-hand side, I hope you can see an example of a PR metrics, where with the Docker driver start time is around 18 seconds. For details, I would recommend that you visit these two great presentations held by Media and Priya at Qcon last year. Also ARM64 support was added for Docker and Bodman drivers, as well as for Apple M1 chip. There are new commands introduced like image load and build, pause on pause, schedule stop, SSH cost, etc. Amongst the latest add-ons that were added are auto-pause, CSI hotspots driver, volume snapshot, and so on. To make Minikube more user-friendly and simpler, automation plays an important role. And therefore, the improvements in automating driver and CNI selection, setting default CPU and memory parameters appropriate for your machine, auto-pause, add-on, and so on. There's a monthly cadence for each new release, so many new features and improvements are delivered regularly. Okay, so what's ahead of us? The plan for the next release is captured in the current KitKat milestone plan. It's accessible through the link given here. And also, the development plan for this year, amongst other things, includes removal of dependency on lib machine that is deprecated and no longer maintained.  The documentation improvements using container runtime interface and container network interface by default, graphical user interface for star stop and potentially other commands. Future improvements to resource monitoring and alerts. And currently, as you saw, it takes about 18 sections to start up the cluster. And the goal is to go under 15 seconds. So we are closed, but not there yet. And also, the kernel assistant mounts like SIFs and NFS are in glance. Also, other things will be prioritized and added to the development plan going further. Minicube community is continuously growing. And by the time you see this video stream, the number will likely to be higher. There are more than 600 contributors at the moment, whereas the number of non-Google commits rose by almost 75% in the past couple of months. The GitHub project has more than 20,000 stars and more than 3000 works. And there are almost 5000 Minicube Slack channel members. How can you become a part of the Minicube? You can join the Slack channel, mailing lists for users and or developers. And since this is a community driven project, you can also take part in an open by weekly office hours meetings, as well as triage parties. Now triage party is a weekly meeting where maintainers and contributors discuss open issues, prioritize and make sure they are timely addressed. Last but not least, as seen in an example with the multi-node feature, anyone can impact the project by sharing how they're using Minicube and what they think could be improved or added. So feedback is also collected through an always open quick five questions away, and the results are regularly assessed. Please share your experience and thoughts with us, it really matters. If you would like to contribute to Minicube, here are some guidance of how you can start. The getting started and also how to contribute guides are on the website. Those GitHub issues that are considered a good starting point are marked with good first issue label. So look for those and don't be afraid. You will get further guidance and any help needed from maintainers and other contributors as needed. We also need lots of help with documentation and translation, as well as specific help with expertise in networking, testing, CICD automation, containers and so on. And due to time constraints, we could not go much further in details here, but there are links in the presentation that could point you into the right direction, should you want to learn more. I hope this was informative for you, and I want to thank you for your time and attention. Now, let's move on to the Minicube deep dive with Anders. Thank you. Hello, my name is Anders Birkjön and I've been working as Minicube maintainer for two and a half years now. And today, I will be talking about three different local Kubernetes environment, the hypervisor, the container and the bare metal environment. The hypervisor environment creates a virtual machine running a separate kernel. This is also called hardware-assisted virtualization. In the container environment, we create a system privileged container using the same kernel as the host. This is also called over-slevelled virtualization. And in the bare metal, we run the Kubernetes components directly on the host. And this host may in turn be a virtual machine. And then we will be using hardware-assisted virtualization under the hood. In addition to this environment, we also have Minicube running on different operating systems in the traditional meaning, not in the Linux distribution meaning. So, when we run on macOS or Windows, we will need to run the Kubernetes control-playing components in a virtual machine, either if it's visible to us or if it's hidden from us. In addition to this complexity, we also have different architectures. Currently, we are trying to support two out of the five Kubernetes environments, AMD64, the traditional 8664 PC environment, and also this new ARM64 environment, like the Apple M1 or the Raspberry Pi or similar device. For the Raspberry Pi, there is also the 32-bit ARM, which is not used for the virtualization, but it can be run in native mode with Minicube. So, when you go to install Kubernetes on a machine, the first thing you need to do is to install a server running Linux since the control-playing only runs on Linux at this time. In Minicube, this is done by using the driver. On this machine or server, we then need to install the container runtime. Traditionally, this was Docker, but you have other options to choose from as we will see later. In Minicube, this is done by the provisioner. The third and final step is to install the Kubernetes control-play components. In Minicube, this is done by the bootstrapper. This will install the software and configure and initialize the control-playing. In this presentation, we will not cover running multi-node or running multi-master, but after you have set up the control-playing, you can, for instance, join some working nodes to the control-playing node. You can install the Kubernetes client, CubeCDL, on the host, and finally go to deploy your applications. When you run a single node cluster with Minicube, we taint the control-playing node so that you can run apps also on the single node with this CubeCDL taint command. What's nothing is that Minicube not only provides Kubernetes access, but we also provide SSH access to the machine, and we even expose the container runtime to the user, for instance, for loading and building images. Traditionally, this was done by a command called DockerM that gave you access to the Docker daemon running on the machine, but in later versions, we have bundled this in a Minicube image command to make it agnostic to the different container runtimes, so there is an image load and an image build command. These three environments can be further broken down into six different environments. For the hypervisor, we have the traditional Oracle VirtualBox external installation, but you can also run with the so-called native virtualization of each operating system. For the container environment, we both have the Docker engine running as processes in Linux, and we have the Docker desktop environment which runs using virtual machines on micro windows. And for the bare metal, finally, you can either run it local, as we have done traditionally, or in the latest version of Minicube, we can even run a remote cluster, so that the actual cluster can reside on a different physical machine than your current laptop, and then we use SSH to connect to this remote machine. You can then break this down even further by looking at different vendors of the different solutions. So in addition to VirtualBox, you might also select VMware or Parallels for your external virtualization, and the operating system virtualization comes in different flavors. For instance, on Windows, you would use Hyper-V, and on Mac, you would use something X-Hive-based, such as Docker's HyperKit. And for Linux, we're using the Libvert daemon access to the KVM, the kernel virtual machine. For the container environment, we also support Podman as an alternative to Docker when running natively on Linux, and you have the Docker desktop running on Mac or on Windows. And there is also a new Podman machine that you can use as an alternative when using Podman on Mac. The bare metal, as we mentioned earlier, can come in a regular physical server or virtual machine server. This can be run locally connected to your local network, or it could be run as a virtual machine. It could even run remotely in a private cloud. Here we can look at the difference on the different approaches in the more simple common solution of having a physical server and then just installing the container runtime directly on this. We have one Linux kernel running directly on the server, and then this container runtime will start the pods for Kubernetes. When we have a virtual server, or when we're running Minicube in a virtual machine, then we have a hypervisor running the Linux kernel on the native kernel of the host, which could be a Linux kernel or it could be a Windows or Mac kernel. And in this virtual machine, we will then run the container runtime like we did in the physical. When running Minicube with a Docker driver or the Podman driver, we create a system container that emulates a node, and it works something like actual virtual machine, except that it is running on the same native kernel as the host, which gives it a lower overhead. Inside this driver runtime, we run the Kubernetes container runtime. So here we show Docker in Docker, but you can also run container D in Docker or cryo in Podman. And finally, the most complex solution where we have the Docker desktop driver, where we have Docker running in a virtual machine with a Linux kernel on the native system, and then inside this virtual machine, we have the same setup as with the Docker engine driver. So there are two different kernels involved here, but there are also two different container runtimes involved. If we look further at those three install steps, you can subdivide them into more detailed approaches. The first thing is that you need an image in order to start your operating system. And we do bundle a Minicube ISO for use with the virtual machine, which is originally was based on boot to Docker. When running in the container environment, we use Ubuntu 2004 as the base. Then you will use the machine provider to install the servers with Linux using this image, be it virtual box or be it Docker running the image. Then we have the second step where we provision the container runtime. We configured and installed Docker or container D or cryo. And we also make sure to make the Kubernetes images available in this runtime. We call this the preload step where we preload all the needed containers from a target into the environment or from a cache directory. And finally, the third step was to bootstrap the Kubernetes control plane and also to install the Kubernetes networking if we're running in a multi-node scenario or if we just want to replace the networking on the local single node device. For the operating system, we had the boot to Docker option same as Docker machine, which is based on Tiny Core Linux. This is now deprecated in favor of a custom build route environment, which was originally based on CoreOS. And this image is used for the virtual machine. It's called the ISO traditionally referring to the CD image. For the container environment called the kick for Kubernetes in container, we are using Ubuntu, which is the same as used in the kind Kubernetes product. And then we install the software using regular system packages inside this OS. You can also bring your own the next supported distribution. And we will try to configure and install Kubernetes based on the OS that you provide. And this is not fully supported, but we will need user support to support the more alternative installations here. For the container runtime, we have traditionally used the Docker as the container runtime in Kubernetes. And MiniCube has supported Cryo for many years as an alternative. For building the images for Cryo or for loading them, we use the podman command line tool running in the virtual machine. And the latest addition to this family is to run container D. And when using container D, we use the buildkit and buildkit demon as the means of building images using the MiniCube machine. And since the latest version of Kubernetes, the Docker shim has been deprecated, which means that we need to provide a CRI also for Docker. CRI stands for container runtime interface. And traditionally, MiniCube shipped all the Kubernetes component in a single binary around this. But since this was maintenance burden and also meant it differed a bit from the regular Kubernetes installation, we are now using the standard CUBE ADM installer. And this is the same binary you would use to install in a production cluster. And as I mentioned, we download the required binaries and the images for this CUBE ADM installer in the preloaded table. When it comes to the CNI or container networking interface, we have traditionally used Docker, but now since it's deprecated the Docker shim, we are making the CNI default to all the container runtimes, either using the standard single node bridge, or perhaps in the container environment, the kind net PTP alternative. But when it comes to multi-node, you would install something like Flannel or some other option for connecting multiple machines. So with all these alternatives, when would you choose to use a specific driver? And here I will give three examples on when you would use a driver. The first one is the so-called traditional setup where you would run Minikube in a batch machine, the way it's been done for years now in Minikube, traditionally using VoucherBox, but there was also these native virtualization alternatives. The second is to run Minikube in a system container using this new Docker driver. And the third option is running Minikube in a VM provided by the user in a local host shell on the control pane itself. So for the first use case, you would run Minikube start and select the VirtualBox driver. You can also run Minikube start-vm and it will pick the suitable native driver. And the pros of this approach is that it is running the OS provided by Minikube, which is then compatible with the Kubernetes version being installed. And this setup has been tried and tested. The cons are, however, that it is quite high overhead compared to some of the other options. And you will need a platform with support, for instance, for virtualization, or in this case, VirtualBox, which does not support the ARM64 architecture. If you have taken the Kubernetes introduction course, I believe this uses the VirtualBox player. The second driver, and the second driver we will look at here, is the new Docker driver. And this will then start a system container with Minikube and everything in it.  And the resource usage, when running natively on the host, means that you will not have to spin up a second kernel. And you can share memory with the other processes on the host. And the cons with this Docker driver is that the kernel compatibility is limited to what the host can offer. You cannot use this Minikube virtual machine to run all different kernel-based deployments when it comes to, for instance, storage systems or other uses of Minikube. And finally, the networking we're running in a virtual machine is somewhat limited, which means that we need to tunnel all the networking into this virtual machine running the actual container, as opposed to running the virtual machine directly where we have access to the network interface of the machine. And running Kubernetes in Docker is something that KIND has been doing for Kubernetes testing that has been adopted for Minikube use with the container building and the SSH access. And finally, we have the so-called non-driver, which means that Minikube will run all the QBADM commands and all the containers directly on the host. And the pros with this approach is that it's a low overhead since we don't have any virtualization or any containerization. And it's also quite simple in terms of which processes and which virtualization layers are running. And the cons, however, is that since we are logged into the control plane, we don't have all the niceties of running a regular desktop. And there is no isolation, which means that all processes started will run directly on the machine. So this is not something that is recommended to run on your laptop, but it can be used when running in a virtual machine that you have set up, or for instance, when running in CI. If you have done the Hello Minikube tutorial with the CataCoda from the Kubernetes website, this uses the non-driver in a virtual machine accessible from the web console. And that was it for the presentations. If you have further questions, you can always reach us on Slack or on GitHub when it comes to issues. And we will now be available in the chat to answer any other questions you will have. Thank you for listening.


Welcome to NT and Knightley. I am Jesse Leance. This edition stops stories. Cabinet approves concessions for farm workers and waiver of quarantine fees. The city police department to enforce the wearing of face masks and castries and girls of a feather craft storytellers. The Cabinet of Ministers has approved concessions on personal effects, tools of trade and motor vehicles for workers on the Seasonal Agriculture Worker Program Canada or any other worker program coordinated or endorsed by the Government of St. Lucia provided that they satisfy a set of criterion. The Government of St. Lucia recognizes the significant impact that the program has in reducing the level of indigence and the role that farm worker dollars play in revitalizing not only the rural communities but the nation's economy. As with all sectors worldwide, the program was severely hampered this year by the COVID-19 pandemic. With the increasing cost of chartered flights, mandatory quarantine on arrival in Canada reduced movement resulting in the purchase of items from vendors at a higher cost. The purchasing power of the workers was severely hampered. It is with this in mind coupled with a reduction in work and earning capacity of the workers that the Government of St. Lucia thought it prudent to waive the quarantine fees for returning farm workers. The Government of St. Lucia is of the view that the result would be a win-win situation as the money earned would be spent on their families and this contribute to the revitalization of the economy. Officers attached to the City Police Department will be enforcing the wearing of masks in the City of Castries. City Police officers made their first arrest on Monday of an individual, a male individual who was not wearing a mask. The young offender will be charged for failing to adhere to the COVID-19 prevention and control regulations. Recently, the Castries Constituency Council appealed to the flea market roadside and provisions vendors to adhere to the health protocols and guidelines set out by the Ministry of Health in a bid to limit the spread of COVID-19 virus. In addition, customers and staff members at the market were requested to follow public health guidelines that require face masks and maintaining a distance of at least six feet between people. Speaking on the issue, Castries Mayor Peterson Francis says anyone not abiding by the law on face covering will be fined. Those who fail to comply with the new rules will face a fine of up to EC$1,000. The City Police Department will be on active patrol to ensure that all public health protocols are adhered to. And meantime Honourable Guy Joseph, who has responsibility for the public transport sector, is encouraging commuters to play their part in keeping themselves and the nation safe against COVID-19 by ensuring compliance to the protocols on minibuses. If a driver is not compliant, passengers should not board that particular vehicle. If a driver is compliant but the passengers are not compliant, then other passengers along with that driver should help in the enforcement of this. Because it is not possible to have police officers everywhere. And I must say from the National Council's standpoint, they have been cooperating, they have been advocating that everybody comply with the established protocols. I mean up to this morning I had a discussion with the Grozily Minibus Association and one of the issues they are faced with is that in establishing or enforcing the established protocols, some of the passengers are leaving the stand and going to other bus stands that are not compliant with the said requirements. We have made it very clear that any driver who is found not compliant with the protocols will be suspended for free. And in the first instance, they would be suspended for 14 days. Minister Joseph says government notes the reduced income of minibus operators as a result of the 10 passenger limit and as part of an assistance package has provided payment relief from route banned fees. The $700 that had to be paid for the route permit for the next two years, these fees have been waived. That is already in effect. That is resulting in direct savings for the persons who have to renew their route permits. So their route permits are renewed without them paying any fees at this point in time. So whatever the government can do in the interim is being done to help facilitate. But it is not a situation where we can guarantee buses that whatever they were earning that they would continue to earn, it would be creating a false expectation. And I think that the council has understood what is there, what is in place, and how we are going to negotiate the process in terms of what is going to be done to assist in providing the public transport. Economic development, housing, urban renewal and transport minister, Honourable Guy Joseph there. The Bankers Association of St. Lucia has made another generous donation this time to the Rainbow Children's Home in the south of the island as part of its outreach initiatives for Financial Information Month 2020. We have more in this report. The Rainbow Children's Home opened in February of 2019 and has been playing a pivotal role in providing support, housing and care for children coming from abused homes across the island. The home was the latest recipient of a donation of essential food items from the Bankers Association of St. Lucia. According to the manager of the home, Sandra Foster, it was a timely gift of which she and her staff were very thankful for. It's absolutely a fabulous donation that we've been given from the bank today and it will go a long way in feeding the children for the next few months. The month of October is Financial Information Month, but according to representatives of the Bankers Association, observing the month is about helping the less fortunate, just as much as it is about empowering them through education. Giving back is part of our mandate in helping our communities prosper and in the midst of educating the public, in the midst of educating our children, we also have this side who would also come together to give back to society. So, this is what we're doing right now. The Rainbow Children's Home in Vierfort was the second but not the last on the list of NGOs to receive the support of the Bankers Association of St. Lucia. Officials from the collective group of financial institutions say that a visit to three more homes are on the list of activities for the remainder of October. From the Government Information Service, Lisa Joseph reporting. Empowering girls through their own stories. The Girls of a Feather organization recently wrapped up a three-week Storytel Her boot camp for creative adolescent girls. The closing ceremony for the Girls of a Feather Storytel Her boot camp was a showcase of talent displayed by participants of the three-week activity. The boot camp was a series of free virtual and in-person workshops introducing fundamentals of journalism, creative writing, art and filmmaking for adolescent girls who have a passion for storytelling. I just want to say a big thank you to Girls of a Feather for inviting me to be a part of this wonderful initiative for young women and girls. As someone who is passionate about having more women storytellers and filmmakers in the region, it was something that I was happy to be involved in. Society, where dreams are made and always come true, where brothers are always the brothers keeper and sisters are always their sisters keeper, where children believe in superheroes. Society, where all exist and all people love, care, share and live together. Welcome to society. Facilitator for the journalism workshop, communications professional Karmie Joseph spoke on her experience working with the girls. While we went through the fundamentals, the principles of it, I wanted them to write a press release about themselves. If you had to describe yourself, if you had to talk about who you are, what you hope to be, how would you do that? And that is what the press release piece was about. But for journalism, the girls went really ambitious. They wanted to tell a story about women who are successful in male-dominated careers or male-dominated professions. Cultural activists to June Frederick was the guest speaker at the close. She encouraged the girls to make use of their distinctive identity in their creative processes. I want to challenge you to learn all there is to learn about your country, its history, traditions, culture and as an artist to continue to hone your craft and learn lessons that life throws at you every day. I challenge you to dare to be original. Don't copy anyone's work, culture or traditions. Your original ideas, your own culture and traditions are so much more satisfying and beautiful. The Storytel Herboot Camp is the latest undertaking of Girls of a Feather, a mentorship and advocacy group for adolescent girls in St. Lucia. Up next, we have Primus Hutchinson with the Nobel Award. If you are in receipt of an abnormally high bill, it is highly possible that you have a leak. That leak may not always be visible. Before you contact Wasco, conduct a do-it-yourself test. One, record your meter reading. Two, do not use water for 30 minutes to one hour. Three, take another meter reading. If the reading changes, you have a leak. Contact a plumber to identify and fix the leak at the earliest. A message brought to you by the Water and Sewage Company Incorporated, Wasco. Welcome back, time now for the NTN Nouvella Quiole with Primus Hutchinson. Ladies and gentlemen, G.I.S., the National Television of the NTN Nouvella Quiole, and Primus Hutchinson. The technical mission of Taiwan, the collaboration, and the Ministry of Agriculture to continue to support the activities of these women, countries, and the various initiatives and programs, particularly the development of eclaflas. With that, the Quilt-de-Vauteuil, a vision 6, to participate in our ceremony to mark the end of the training of the ambassador of Taiwan for this issue, petitioned by Commitment, with my country, to assist the Quilt-de-Vauteuil, that is, the farmers, in this country. For the ambassador of Taiwan, this issue has surpassed almost $6 million to buy fruit and vegetables from the country. For example, chupom, moulon, cantaloupe, and tomatoes, each country has to continue to grow. The ambassador of Taiwan, this issue has surpassed almost $6 million to buy fruit and vegetables from the country. This is mainly the reason why the government of Taiwan works together, and then the government of Taiwan, to assist the farmers, mainly to advance the program in a sustainable way. There are women who participate in this program, that is, Iverson Calyx, to encourage all women to apply all these principles that will take part in the training, also to work with each of them, always write these principles to all of them, and advise women to work in collaboration, as they can operate, and also the women who have no more competition to help improve the agricultural sector in this area. And also the women, the women of Iverson Calyx, it was their collaboration of the Ministry of Agriculture, and their technical mission of Taiwan with ICA. PSAPA recently also has a total of 200 communication radios that have all advanced to help chain communication, and also a lot of women policemen have come to facilitate the world view, the Organization of Agricultural Machines, that is F.A.O., Agents of Climate Change in Karebla, and the Department of Fisheries, that's it. These radios, how is it possible for these fishermen to communicate, to go a distance, and then a lot of fishermen, with policemen, and then a lot of communication, and then, Minister of State's Department of Agriculture for the Presidents, Anuab Herod Stanislas, declared that it is not possible for these fishermen to find these fishermen in this area. It is because, to get this land, to build resilience, and to reduce the situation in the development of the fishing sector. For the village and the economy, I would like to thank Mr. Aja Salah for his equipment and for all the efforts he has made. I would like to thank Sakai Uedui and Phil for their efforts and for Mr. Aja Salah. I would like to congratulate the Minister of Agriculture and the fishing sector for this initiative. The government has decided to put the fishing sector in place for its life on Radio Salah. The Minister of Social Development, Social Justice and Equality has declared that the government has made enough to assist the people of this country. I would like to thank the government for their initiative to try and help the people of this country to assist the people of this country who are affected by the coronavirus. I would like to thank the Minister and the Minister of Agriculture and the people of this country who have gathered in the GIS to help the government to pay $75,000 to relieve the difficulty of the people of this country. But the Minister of Agriculture and the people of this country is not the only thing that the government has done. There is also a water service that the government has established to relieve the people of the country who are affected by the coronavirus. For example, the government is very happy to start a commission to help the people of this country. After that, we have to deliver food, food that is immediately given to people, especially the people. We also have people who work very hard, who are very busy here. We have 4,000 people who are in this situation. We have been living here for 3 months to solve the situation. We also have a situation where the school has to be open to the people. The people who are affected by the coronavirus and the people who are in trouble also have to provide assistance to the parents who are affected by the coronavirus. This is coordinated by the SSDF. Also, as a result of the situation, we have already asked the Ministry to assist us. For example, we have been living with SIDA, which is HIV AIDS. The mother of the children who are affected by the coronavirus is working with the people who are affected by the coronavirus. We are working with the people who are affected by the coronavirus because we are in a more difficult situation. We are in a more difficult situation. We have been living with SIDA for 2,600 months and we have been working with the people who are affected by the coronavirus. We have been working with the people who are in trouble for 2,600 months. I started to find information about everyone who is working with the SSDF to help their parents to get the health care. Thank you, ladies and gentlemen. Let's continue with our new interview. Today, I want to thank Mr. Otton for inviting me to come here. I want to continue with this interview and I want to thank you all for your time. I want to thank Jesse. Now, do stay tuned for more NTN programming.


Thank you all. Welcome back from lunch. I hope it was a pleasant experience. You had good company and good food. We're going to resume with the open session agenda here. Terry Monoglio is going to give you a presentation from the Genomic Medicine Working Group of Council. One of the requirements of council working groups is to make at a minimum an annual report back to the full council, and Terry's going to do that for you today. Great. Thank you. And good afternoon. So this is probably the fourth report we've done of the Genomic Medicine Working Group to the council. We try to do them every September. Just a reminder of who's on the working group. We have three current council members, Carol, Howard, and Dan.  You'll notice Jeff was on quite some time ago, as was Rex and a few others, and yet they're still on our list. So we welcome you just to stick around. And just a reminder that the sort of the areas that our working group addresses are sort of the latter two domains that were added in the 2011 strategic plan. So the advancing the science of medicine, improving the effectiveness of healthcare, is where most of our emphasis is. The charge to the working group is to assist in advising us on research needed to evaluate and implement Genomic Medicine by reviewing current progress, identifying gaps, publicizing key advances, planning Genomic Medicine meetings, which I'll talk about in some detail, facilitating collaborations and exploring models for infrastructure and sustainability of the programs that we propose. So I think I've described to this group in the past that we kind of began this whole effort shortly after the strategic plan was released. It was about June of 2011 when we held a meeting at O'Hare Airport of about 20 different groups that we were aware of were doing implementation of genomics in clinical care. And we just invited people to come and spend a day with us, which they did. And from that, we sort of learned that there was a whole lot more going on than we had expected, but a lot of it was going on in isolation. And one of the things we needed to do was to develop some joint programs. But we also produced sort of a roadmap from that of how one can go about implementing genomics in clinical care that was published in genetics and medicine. Our second meeting about six months later was to focus on forming collaborations. We had a third meeting with stakeholders and payers. It was one of many efforts we've had at engaging the payer community and others. The fourth was on physician education in January of 2013. Then we had one with federal agencies trying to work with our federal partners to try to develop strategies for implementation. The sixth was a global leaders meeting where we invited everybody that we knew in the world as opposed to in the U.S. to do much of what we had done in the first meeting. And then one on clinical decision support for genomics in medical care. An eighth one about a year ago that was kind of an overview of our existing programs just a little bit of a step back to see where we are. And we reported on that one I think about a year ago, maybe six months. And then just recently held one in April on a bedside back to bench that Carol's going to tell you about once I'm finished. So all of the meeting or content is webcast. Everything since the first one. And the slides and summaries and all of background materials and that are all available on the Genomic Medicine website. So if you just Google NHGRI Genomic Medicine, it should come right up. Outgross of these meetings, there have been many. Probably the one that came out most immediately was to have a meeting that we called ClinAction, which was a workshop right around the time of the second Genomic Medicine workshop actually two days before that was to try and figure out what variants are actionable. How does one go about determining this and how can we do it in a collaborative way so that we didn't have 20 different groups doing it 20 different times and coming up with largely the same answers. That then led to the solicitation for the clinical genomics resource or ClinGen that you heard Eric talk about. That has led to a close collaboration with the FDA. This line is dotted so we don't suggest that ClinGen actually produced the FDA. But it did produce a collaboration with it. We also out of that developed a collaboration with the National Institute of General Medical Sciences in their pharmacogenomics research network to apply a targeted sequencing panel in the Emerge cohort that we called Emerge PGX. The second meeting led directly to the solicitation for the Ignite program. The third payers meeting is a work in progress but continues to be an effort that we're trying to stimulate. The fourth led to the Inner Society Coordinating Committee on Practitioner Education that is now led by our division of education and communication. The fifth one on federal strategies produced collaborations again with the FDA and with Centers for Medicare and Medicaid Services and also produced a trans NIH working group of centers that are institutes and centers across NIH that are interested in application of genomics. I should say that given the conversations that we had earlier today with NHLBI and others, most of the institutes are not doing implementation in clinical care. What they're doing is primarily genomics in the biology of disease and still are a few steps away from actually applying it in clinical use. So we are sort of out in front on that. The Global Genomic Medicine meeting led directly to a workshop on Stevens-Johnson Syndrome, Toxic Epidermal Macrolysis, a devastating skin reaction to certain drugs in certain genetically susceptible individuals that was identified at the GM 6 meeting as being something that we could all coalesce around and actually do a collaborative research and intervention project in. And that then led to a program announcement that was released just recently, maybe within the past month or two for serious adverse drug reactions. And this is a collaboration of about five or six different institutes. Again, these will come in as investigator initiated applications. They are simply, it describes an interest of the various institutes in receiving applications in this area, which up until this time there had been relatively few. The decision, clinical decision support meeting led to an interaction with the National Academy of Medicine's Genomics Roundtable and their Digitized Electronic Health Record Genomics Project. Our eighth meeting I referred to, and I'll talk more about efforts that are still being developed from that. One of them is Harnessing Quality Improvement Efforts, another international education efforts that you heard alluded to by Eric, and a third, developing a knowledge base of genomic medicine programs. And it led directly to the ninth meeting, the Bedside to Bench, where there was a strong push to get basic scientists more heavily involved in genomic medicine and our planning. And Carol will talk a little bit about an outgrowth of that, prioritizing genes for functional studies. We are in the early stages of planning for our tenth meeting. We hold these meetings about every six to 12 months or so. This one is going to be a good year after the last one, primarily because trying to schedule meetings nine months after a meeting in April puts you in the middle of the winter, which makes it challenging. But at any rate, what we anticipate doing is focusing on research directions in pharmacogenomics, particularly as implemented in clinical care. So we will be surveying the national and international landscape of these programs, looking for synergies and promoting collaborations as we do in all of our meetings, looking for evidence gaps and what's needed to fill them, and then designing some strategies for large-scale evaluation and implementation of pharmacogenomics and clinical care focused on the U.S. So I thought I'd take most of the time today to talk about what GMWG has been doing since the last time you heard about us, and that has been focused primarily on the recommendations from the eighth meeting that we held back in April of, sorry, that's nine. When was it? At any rate, I was in June, sorry, June of 2015. And as I said, one of the big outgrowths was the ninth meeting that you'll hear about from Carol in just a moment. But in addition to engaging basic scientists, we also were encouraged to create an implementation commons for sharing tools for implementing genomic medicine. This was basically affected by the Ignite program, and we sort of had a feeling this was on its way. This is the Spark Toolbox, supporting practice through application resources and knowledge. Currently, it is primarily populated with resources from the Ignite program, but it accepts resources from everywhere, and we are hoping that this will become sort of the go-to place for implementation resources. We are also encouraged to develop dedicated programs for non-European ancestry populations to fill the gaps that we've talked about this morning, as well as many times around this table. A first sort of start on that was the effort in the Caesar renewal to have centers with enhanced diversity, as well as our usual centers, even those centers, increasing the diversity that they had typically provided. So this is an RFA that has now closed, but applications are in, and we'll be telling you more about them. This is just a baby step, we think, on starting down this road of trying to redress some of the imbalances in populations that have been studied and work that's been implemented, but we think it's an important step. We were also asked to maximize sharing of quality improvement projects. There was a lot of discussion about the fact that many hospitals are conducting these, and I'll talk about that in a moment, to explore joint training opportunities with other organizations and other countries, and to establish and maintain a knowledge base of ongoing genomic medicine studies. So looking at the first, quality improvement projects are conducted by many organizations. They are using this sort of model as a way of implementing genomic medicine projects. Dan, I believe the Vanderbilt project is largely done as a QI project, not as a research project. There are advantages and disadvantages to doing that, just as a definition, the Health Resource and Service Administration and the National Academy of Medicine describe quality improvement as a systematic, continuous actions that lead to measurable improvement in health care services and the health status of targeted patient groups, so really improving the quality of health care through a variety of venues. Such projects typically are individualized to meet the needs of a specific health service delivery system. They are evidence based. They're designed to improve patient safety and outcomes, and very often they're complex and multidisciplinary. Almost every hospital or large center conducts these. It's one of the ways that one demonstrates a commitment to quality, and actually in many of the sub-specialties, there's a requirement for continuous quality assessment and improvement. These are among the groups that are engaged in this area. The National Quality Forum is one of the major national groups. The ISQA, International Society for Quality Improvement, is an international group, and the AHRQ, Agency for Health Care Research and Quality, obviously funds research in this area, HRSA, helps to implement it. So these are all groups that we are working with and trying to coordinate with and doing this kind of work. We sort of started out, we thought we'd start small, by talking to having the members of the Genomic Medicine Working Group who were practicing in hospitals or working in hospitals who had quality improvement programs to contact their chiefs and just sort of ask them, are you doing anything in genomics? So what is it? If not, would you like to, and how could we work together to try to do this sort of thing? For the most part, those who were doing anything in genomics were doing it because of the Genomic Medicine Working Group members' involvement, so we knew mostly about those. But also there was a considerable interest in the potential of possibly bringing some of these programs together and not only disseminating them to other groups, but also trying to get them to coalesce a bit and improve sample sizes for actually doing some research along with the QI. So we're going to start out by organizing a small meeting to discuss the opportunities in genomics and how we can get other groups interested in those. One way would be to present genomic seminars at annual meetings of these groups. Unfortunately, their meetings have either just happened or are about to happen and it wasn't possible to get on their agendas, but that's a work in progress that we'll be following up on. Exploring joint training opportunities, this kind of came up during the eighth Genomic Medicine meeting when someone described very briefly the incredible investment that Genomics England is making in genomics education of providers who are going to be receiving basically the results of the 100,000 Genomes Project being conducted in England. This is an infrastructure building effort to actually make England basically genomically enabled for clinical care within the next three years, and it's about 25 million pounds being dedicated to this. They also have a mandate to share their information and expand internationally. In addition to that program, you heard mention of the University of Miami's Concurrent Master of Science in Genomic Medicine. This is actually concurrent with the MD degree, so students can apply and become part of it in their second semester of the first year of medical school and then follow through for four years. I think there are about 40 students now in that program across all four years, and they just graduated their first class last year. The Inter-Society Coordinating Committee for Practitioner Education in Genomics, or ISCC, is the one that grew out of the fourth Generate Medicine meeting that is run from here within collaboration with the professional societies. Jackson Labs has a number of valuable resources, including one of their most recent Precision Medicine for your practice series for education for the non-geneticist practitioner, and obviously the SHG, the college and our division of communications and education have a number of training programs, all of which we wanted to try to bring together, see where there were synergies, where we could collaborate and share materials, et cetera. So we held a meeting in August of this year that included the Genomics Education Program. They have a master's program that actually has a number of steps to reach the masters at any point in which you can kind of step off and receive a certificate. It's designed not only for physicians, but for nurses and others in the healthcare professions, and it's available online. They have a session on sequencing that's actually starting up in a week that will be available to, and you can sign up, I think, at the time I signed up, there were about 400 people that had signed up for it, and that was a month or so ago. Australia has the Australian Genomics Health Alliance, which is basically a national roadmap for the adoption of genomics and clinical care. They have a fairly substantial program in health education. Genetics Education Canada has this clever acronym, GECO, and they are doing something similar. This is based in Ontario, but their expectation is they will expand it throughout Canada. The G2MC that was a spin-off of our sixth genomic medicine meeting has a series of monthly ground rounds that are done by WebEx. These are a little bit challenging to do when you have sites in Singapore and India and Britain and the US, et cetera, but I think they usually happen about 11 at night in the US, in the Eastern time zone at least, and then the University of Miami's program I mentioned to you as well. So you'll be hearing more about this meeting at the February meeting. Heather Jenkins will give you a summary of it, and many thanks to Heather and Jean Jenkins, our colleague in DPCE for putting this program together. We should have a summary of it available very shortly up on the web, and we'll be pursuing a collaborative relationships with these other programs that we can tell you about in February. A third recommendation was to develop a knowledge base of genomic medicine studies. I always cringe when people say, gee, it would be really nice to have a list of all of the things that do X, Y, or Z. Many of you may be aware that the GWAS catalog started that way, that we thought gee, it would be awfully nice to have a list of how many of these could there possibly be, and they're now what, close to 3,000 of them, and show no sign of abating. So when people suggest things like this, I usually go and hide, but happily, we have Carol Bolt on our council, who said gee, you know, we do something like this in the mouse genome database, and you can have people sort of self nominate, and it would be very useful to compile information on implementation projects. It'd be a good way to stimulate collaboration and more effective evidence generation with larger sample sizes, and more generalizable approaches, et cetera. So Carol offered to help us, thank you, develop a self-nomination site with some degree of auto curation that would be modeled on the mouse genome database and on ClinVar, which has a similar kind of model. We thought we would begin with just simple project descriptive information, you know, the title, and the main aims, and the size, and that sort of thing, and then kind of go from there, see how useful it is, and how often, how much it is used. And we would also encourage submission to other databases that are better equipped to be able to handle many specifics of programs. Clinicaltrials.gov is one of them, and I would hasten to point out, clinicaltrials.gov actually has a large proportion, I think more than half, are not clinical trials at all. They're observational studies, and Geno-Wet Medicine implementation programs, whether trials or not would fit very well in there. So that's another opportunity. So many thanks to Carol, and to my colleagues, Cecilia DuPichet, who are working on that. And then lastly, one of the things that the working group has done from its inception is to identify sort of notable advances or accomplishments in genomic medicine and make these available on our website for largely for us, but also for others when people say, well, you know, what has genomics done for patient care? Well, now there's a list of them, and so if you look on our website, you can see it's divided, and these are overlapping, so it's a little hard sometimes to decide where to put them, but clinical implementation, oncology sequencing, et cetera. And then we, every month when we meet by phone, we review three or four or five papers that we think are candidates for this, and sometimes we decide, no, this isn't quite ready yet, and sometimes we decide, yes, absolutely, this should be on. So it includes papers like this one, recently published looking at CYP2C19, loss of functional leals. Dan was pointing out that this is a very nice example of what we were discussing earlier about the value of diverse populations, because the study was done in, somewhere in the Philippines, sorry, in China, I believe, somewhere in East Asia, forgive me, I'm geographically challenged, but at any rate, and they had, there's a much higher rate of variant alleles in that population, so they were able to detect a very significant impact on risk reduction in patients with TIA, the first time this has been shown, the previous positive findings have been in stent restenosis after coronary stenting. This is another one in practice guidelines from the College of Medical Genetics and Genomics on cancer predisposition assessment, a third on whole exome sequencing tests for detection of point mutations in bills, et cetera. So these are something that we try to update on a regular basis and keep them available for the community to take a look at. So I think I'll stop at that point, I would thank the many people, not only those on the GMWG, but also those who come to our meetings who participate either in person or by phone, it's always a very enthusiastic and lively group, and of course all of my colleagues at NHGRI who are involved in GMWG, and then of course the working group, so I'll stop there and be happy to take questions. Questions for Terry, to overwhelm them with progress. Yeah. What are the thoughts about training in MOOC, for example, fashion in ways that are much more massively, that have a wider reach? Yeah, so massively open online courses. Yeah, so that's, I'm not saying a course, I'm just saying using these kinds of platforms that let you, it always strikes me just from the outside that, especially for computational tools, that's so probably for experimental methods, for computational tools, this should be doable and could reach a much larger number of people. Sure, no, excellent point. It isn't something that we have explored in a large degree, and I haven't included the Institute's education efforts here, because we sort of have those in the training and education programs. We do have new Genomic Medicine T32s, but they are very standard. They are not anywhere near the MOOC model. No, and I was not thinking about MOOC as training for grad students and postdocs. I was thinking about the community of active researchers of any career phase that need to pick up the new tool, the new thing. Today they actually still either have to sit at some workshop or figure it out on their own or go to someone next door to train, and especially as you think about reaching outside the aficionados, whereas, which is where genomics is going, there's a gap there. So that's why I asked. I was just using MOOC as a kind of a metaphor almost. And were you also talking, so you just said for researchers, I was wondering if you also were implying another community of people to think about their healthcare professionals around genomic medicine implementation. Yes, and increasingly this would be the case, right, for people to be able to interpret and so on. So I think the people often think about MOOCs in the context of Coursera and edX serving the undergraduates somewhere else and so on. But even that is a misconception of MOOCs. The vast majority of people who actually use MOOCs effectively are people who are extremely well trained. They might have a PhD and a postdoc and they now want to take the cutting-edge thing and do something, and so they actually go and seek out this training because they're easy to train because they know how to study for a class and so on. And they have a huge level of motivation. I think the same would apply here. There is a lot of demand and there isn't a lot out there and there's the amount of time investment that's needed in order to make these materials well is non-trivial, but if you make the one investment and you have a platform like this and updating it is a lot easier. Yeah, well, and I might ask Sharon or Gail perhaps to comment on the report toolkit that's being developed by CSER, but while they're thinking of that, I might also mention the Genomics England effort actually does make theirs widely available and that's for all practitioners and there are several resources that our Division of Policy, Communication and Education has developed that are available that way too. Sharon, do you want to comment on the CSER effort? Well, so I think the toolkit's quite different from what Aviv was talking about and I was actually just talking with a relative this weekend who works for Merck who's doing exactly what you described. Like she has a very specific issue and she's been using these kinds of online courses for that. So it is something we haven't really thought about like in the CSER consortium or that type of thing. What we're developing is more of a point of care which will be hosted actually on the NHGRI website for practitioner information education, which is really like if you have a genomic, an exome or genome test report in front of you, what do all these sections mean? And we're like trying to be agnostic to laboratory so using all the different synonyms that like incidental findings are referred to. But the goal of that is really much more, there are more and more of these reports that are showing up in electronic health records as PDFs and I get emails from fellows or practitioners in other fields that are seeing the patient and have questions about these. So it's really designed to be kind of try to help someone walk through the different parts of an exome or genome report and then have it hosted on the web and then the dissemination will be the critical issue. But I think that the idea of MOOCs is important and one point of the dissemination is once we really get it up and test it and beta test it would be to try to ask if laboratories would include the link, for example, on their test report. That's what I was saying. We put together a MOOC like that from UCSF that ran for two years and a couple lessons I learned from it, it was for non-genetics clinicians and health care providers, not necessarily MDs, is that the impact on the international scene is even greater. This is a tremendous need for web-based learning for people that are not in three or four countries that do a lot of genomics. It's really incredible. They're the people we kept getting emails from saying, thank you, thank you, thank you for doing this. Yeah, and I think an important point right now with the data that are being collected with CSER is that CSER is a research project and it's obviously oriented toward moving into the clinical care, but that research clinical interface is thought of really differently across all of the projects. And so, while I think that what Sharon said is absolutely right, that that's what's, it's the point of care, and several of the studies are looking at the ways that non-genetics clinicians are grappling with the information. There's also the issue about what the participants, how the participants are responding and what they do and what they think about the kind of information that they're being told and the reports that they're being given and sort of who's in charge of that because I think a lot of them then take those right back to other practitioners. So there is also that participant slash patient stakeholder, if you will, who's in there and complicates things. Aviv, the other thing worth mentioning is what Terry's representing through this genomic medicine working group, of course, is sort of the extramural research programs, portfolio around genomic medicine. The other place at the institute, and you heard me talk about it in some of the slides in my direction, the other part of the institute that thinks a lot about healthcare professional education, engagement, also general public is our two different branches within the Division of Policy Communication Education, which is not part of the extramural research program. And there are a number of things brewing there that probably are premature for me to talk about quite yet, but I wouldn't be surprised if in the coming months or future council meetings, which might be able to capitalize on some of the ideas. In fact, it's probably more, I mean, if we needed to have research done, it probably would be done within the context of this working group, this council, and so forth. But if there are things that could be done that would just need to materialize or lead it or catalyze whatever words you want to use, it would be, I'm sure, a partnership that would certainly involve Terry's branch, I mean, Terry's division and their expertise, but also other parts of the institute, which is like where the Smithsonian exhibition came out of other educational programs, some of our short courses, et cetera, et cetera, two parts of the other division that are quite focused on that. And as probably that, Genesis, your question is, there's an incredibly acute need for this. And so I think there's a bigger role I'm looking to see NHGRI play, and it'll probably involve many parts of the institute. I have a question for Bob. How many people did you get in your course, Bob? About 8,000, well, I'm the part. So I only have 6,500 in mind, which is still running, called case studies and personalize, but I had to advertise somehow. I agree with Aviva. I mean, it's a gigantic pain in the rear to do it. And I just sent Terry the link, and my comment was two years worth of my gastric lining went into that link. And if I had it to do again, I'm smarter now, and I know how to do it better. But I think with all the audio visual support that NHGRI has and has invested in, it seems like a reasonable thing to think about. I mean, that's what it takes.  Case studies and personalized medicine, with a Z, not with an S. The S takes you to some Australian site. Actually, the one thing I would slightly, I think if we were gonna do this and do it well, I'm not sure it would be done internally to the institute. We could facilitate having it done. We'd probably want it done really well. It would require probably real professionals doing this, not just people in their spare time at the institute. So I also want to make the distinction between a full MOOC, which is what Dan was just describing, and I couldn't agree more. It's a huge amount of, it's just endless amounts of work to take even a class that you taught extremely well for years, and it is fully up to date and make it work in this format. But in particular for computational analytics, you could do, you could think kind of in a mini MOOC format. They tend to fall into these little recipes or steps or so on. It doesn't necessarily mean that you have to take a singular large scale endeavor, and you could still get quite a lot of bang for the buck. So if I think of something, it's just off the top of my head, like in variant interpretation, in even an administrative supplement to some of the groups that already do that so that they make a module. Not a big class, a module, a piece, but that piece explains something very well, even a tool that they already developed, such as a variant interpretation, this or that or the other. So I think that's why I said MOOC in the more metaphorical sense, not just we take our class at MIT or at Harvard or at Hopkins or something and we make it into a MOOC, which is a bigger thing to do. Okay, Dary, thank you very much. I think Teri has set the stage quite well for Carol. She's gonna come up and talk about the Genomic Medicine 9 meeting.


哈友鞋 as concept has been developed for sometime now. 哈友鞋 as concept has been developed for sometime now. HOぁ, lao, lao кажется 哈友鞋 is accept took everywhere in the world…罕叫行动民伴整体时间 lashes yun 来将三代内行 的反正所谓的by qun zheng 和隐形邱然 首页 大家看看 speed in votes covering from 来自观摄 估计~!! 分序自信 那种民伴 の回 rewards Wizard see that IoT can offer extraordinary opportunities первых hungry again, the IoT can offer Internet of Things concept Beijing is putting in place in difficult to achieve those calls by the end of 2030. Most important observation is I'd like to share with you每個地方都會談論中國的事件特別是這些年輕人 small, medium-sized entrepreneurs使用 IT and telecom technologies they understand their market they see the challenges to their society they try to help with their own solutions and if we engage all these people with those communities I think that we will be able to achieve our goals very very rapidly so I am very pleased to have the opportunity to work with CISCO to publish this IOT report for developing countries