Yet throughout the history of our species, humanity has perennially employed such monsters to do that which some of us cannot, to kill, destroy, maim, butcher, annihilate. The weight of this decision has varied, sometimes it is a last resort, unleashing that which we had previously contained only as a desperate gambit in the hour of greatest need. In others, it is an altogether colder and more calculating thing, a precise employment of those human society has deemed deviant or horrific, in a role that would see their horrible gifts used to our greatest benefit. And some, well, some are monsters of our own creation. The Emperor, beloved by all, crafted many, sculpted by his divine purpose to fulfill preordained roles. This is not meant to be a criticism of he upon the throne, far from it. If anything, he is the inheritor of perhaps the longest standing Faustian pact in human history, that to win, to conquer, one must in turn create monsters to bathe in the blood of one's foes. Empires are built upon the backs of soldiers, and too often have these soldiers been bade to sacrifice their humanity for the sake of a brighter future. Yet, not all monsters are easily discernible. There are obvious ones, yes, the scarred and deformed, twisted and cursed, the dead eyed and murderous, but others, others wear the face of angels, appearing as heralds of something great and good but possessing only murder and destruction in their hearts. These are truly the direst of creations, monsters with the face of men stalking amongst us. Can these twisted things ever change, though? When a monster shuck its fangs, divest itself of its claws and wicked intent, and become something truly different, I shall leave it to history to speak for itself and the history of the subjects of this particular chronicle. Know then that this is a record of the great host, the red drinkers of Baal, the sons of the angel, the ninth legion blood angels. The chronicles of the Unification Wars, scattered and fragmented though they are, are replete with tales of heroism, of battle honors, of great victories, all attributed to the early and yet nameless Liginez-Astati's proto-formations. Though most would only arise to full operational strength after Terran Unity, this did not prevent them from being a decisive addition to the conflict, earning accolades that would far outstrip the soon-to-be-only legendary Thunder Warrior Regiments. The annihilation of the Ethnarch of the Caucasus' Wastes by the 18th Legion, the fires that consumed Oryok fanned by the 17th, and the kneeling of the Nordafric Conclave before the 15th Legion, all were victories whose tales were told the world over, and emblems of which adorned the banners of these Ligians as they first left the cradle of the homeworld to conquer the stars. No such honors were given to the 9th Legion Astati's. Not for them were the privileges of leading at the van, being the first onto the breach or to plant the standard of unity atop the ruins of the enemy's empire. Around them only shadowed whispers and dread rumors float, fragmented accounts from the journals of early Imperial Army soldiers or fellow Astati's. They liken the 9th to a haunting, a Legion of Revenants entering battle under dour, ident tags, communing with no one, leaving only utter devastation in their wake. An inferno in transhuman form, unleashed to burn until only ash remained. Whereas other legions were small in number and had to be limited to precision strikes and rapid engagements, the 9th were easily the largest of these proto-formations, and the first to operate alone. Because of this, they were perennially assigned to the worst war zones Terra could offer, the most radiologically choked and toxicologically ravaged wastelands inhabited only by mutant clans and mad Psyker cults. This was no accident, nor simply by virtue of the Legion's size. It was in a very real way a product of their unique gene seed template. For their genetic building blocks, the 9th would take monsters and make them into angels. Poetic as this statement sounds, it was in fact very real, whereas other legions would simply scrub all the recruitment pools for the slightest hint of genetic deviance and take the finest, strongest, and healthiest recruits. The 9th actively called aspirants from the literal human dregs of Terran society. Whereas the 3rd Legion only accepted the scions of the oldest Terran nobility, the 9th's intake was formed of twisted and debased mutant humanity, scarred by generations of radiological and chemical sicknesses driven into the toxic wastes by what remained of baseline humanity upon the homeworld. The 9th Legion took them all, and from this emerged a breed of Astartes removed in every possible way from the aspirants that first submitted to their bloody surgical knives. Uniformly tall and fair-skinned, they were akin to ancient old earth statues, their pale faces possessing a beauty that seemed to be carved from the oldest and grandest marble at the hands of a sculptor attempting to capture the image of the divine. Few amongst the twisted mutant would survive the ascension process. Astartes' implantation procedures were never easy, and it has been noted as being especially painful and torturous for those submitting to the gene seed of the 9th. Scant few would make it to the ranks, but the 9th, unlike their cousins of other legions, cast an incredibly wide and frankly indiscriminate net across populations no other Legion would have dreamed of attempting intake from. By simple logistics and effort, the ranks of the 9th swelled to eclipse all others. While their presence was barely acknowledged in the records of unity, they became onto a legend to the mutant tribes of Terra. In their wake, they were dogged by what best can be described as a pilgrim caravan. For through the Legion, the twisted human waste of the planet saw a chance at truest salvation, an escape from a life of cancers and diseases, of shame and constant degradation. At first no more than a mob, this pilgrim train quickly became more organized, with red, rag-clad holy men emerging to stoke an apparently religious devotion to the 9th Legion. Shell casings from the bolters of lion Astartes, fragments of armor, scraps of penance, these little lost things became relics, objects of devotion to the truly desperate who only wished to escape their pitiful lives. The Red Brothers, as these clerics became known, used their station to herd their flocks into the open arms of the Legion's apothecaries, who readily accepted this arrangement for the easy and constant supply of manpower it provided. Should such acceptance of overt religious devotion strike one's students as odd, given that the Imperial truth formed the basis of the Great Crusade, worry not. The instant the Emperor proclaimed all religion and superstition outlawed, the 9th Legion turned their guns without hesitation upon these pilgrim hordes, slaughtering them, with a coldness that would make even the most stone-hearted of their Astartes' cousins bulk. This is perhaps the reason the 9th Legion endured the fires of unity with so few accolades. Their practices and comportment were both cold and unusually brutal, which, in combination with their sinister post-battle practices, marked them out as distinctly other from their fellows, even the Butchers of the 12th Legion and the Murderers of the 8th. It was not for naught that the 9th's first epithet was the Eaters of the Dead. The Emperor, in his wisdom, had granted to all of his Astartes an organ known as the Omophagia, four nerve bundles that served as a spinal extension to the brain that linked the latter with the stomach. Through it, and by means of the Master of Mankind's peerless gene-craft, Astartes can extract memories and experiences from the flesh of those which they consume. Effectively, this allows an Astartes to learn simply through eating. In the 9th, it appears as if this organ was highly overactive, operating at efficiency levels beyond that of their cousins, and allowing new recruits to be brought up to combat readiness simply by feasting on the fallen of any given battlefield. However, it also appears to have inculcated within the 9th Legion a horrid hunger for the flesh or blood of the dead. It went beyond the simple practicalities of training. The sight of the Beatific faces of the 9th, devouring the corpses of Terra's dead, their perfect skin and hair smeared with human blood and human viscera, was a thing of purest horror. Few who balked at such brazen and disgusting Anthropophagy knew of its purpose, or even the existence of the organ that granted it. But this ultimately only served to further isolate the Legion, marking them as monsters of darkest nightmare, cannibal ghouls to be shunned and avoided. The Legion itself cared not, for they knew the purpose of their creation, to be the monsters who fought monsters, to stalk the dark places of the world bringing ruin to those who defied the Emperor and to others would recoil in the face of. Their gifts, to them, were not shunned, but embraced, for it brought them to an operational size and independence no other Legion possessed, the mutations granting them priceless advantages in both combat and recruitment. Rumors, however, were want to spread, and those Astartes' cousins of theirs who had seen the Bloody Angels both in action and aftermath, wondered openly if the 9th were becoming worse than the creatures that they fought, and if action from the highest authority would be needed to curb their excesses. The Great Crusade, that swept outwards from Terra, did so with the 9th Eager to take their wars to the stars, but not for them were the glorious conflicts of the Jovian and Saturnine theatres. Instead, the Emperor, fully aware of the nature of his weapon, bade them make wake for Neptune to hold at bay the Xenos and mutant slaver clans that squatted in the dark reaches of the outer planets. He did so knowing full well the risk this entailed, as it put a full Legion of his Astartes far outside effective lines of resupply and support, and beyond the reach of any Imperial elements save for the isolated pioneer companies of the 5th Legion star hunters. It's a campaign to retake the arcologies of Saturn and the shipyards of Jupiter raged. No word was heard from the 12,000 Astartes of the 9th, neither word of victory nor word of destruction. Yet as forward scouts scutted out system from the volumes of the newly pacified gas giants, what they discovered was simply stunning. Legion space had been purged completely and utterly of enemy elements, and the 9th stood numbers intact, having aggressively recruited and trained new Astartes from the worst human filth of Neptune's moons. This would come to define their early years in the Great Crusade. Again and again the Legion was sent into the darkest pits the galaxy could provide, with no true expectation from those in Imperial command that they would fully survive. They lacked a Primarch yet to be reunited like their cousins of the 16th Legion Lunawolves or 10th Legion Ironhands, and lacked the political clout that came with the popularity of the yet unnamed 13th or 7th legions. They were not seen as dependably solid, like the 4th Legion Corpse grinders, nor notably self-sacrificing, as assumed to be named 18th Legion Salamanders.   Few amongst the Crusade would ever welcome their presence upon the battlefield, for they were seen to wreak the foulest monstrosities of old night, a revenant Legion impossible to see the humanity in. Their isolation and insularity deepened, cooling their already icy characters even further. They were still part of the Emperor's plan, a cog in his mighty military machine, but an unloved and even hated one, a tool of bitter necessity that knew no friends. Yet, as fate would have it, salvation approached, on pinions of purest white. The planet of Baal was a harsh thing, a rust-red rock set amidst one of the few stable warp currents near the maelstrom warp event. Once a thriving hub of interstellar trade, the Age of Strife had been particularly unkind to it, as some form of petty civil strife during the depths of old night had become a full-scale atomic conflict, collapsing a fragile ecosystem into rusty wasteland choked with radiation storms. It was to these deserts that the Primarch Sanguinius fell, a comet plummeting into the realms of the scant remnants of humanity that yet eaked out a pitiful existence here. For his earliest days he was alone. These are years he never spoke of, his story only beginning when he presented himself to one of the nomad herds. The contrast must simply have been breathtaking, for the ninth Primarch was truly unique. Legend refers to him as the angel, whilst some argue that this is allegory. It is in fact the pure and simplest truth for Sanguinius was, in aspect, an angel of old. Feathered wings of the purest white protruded from his back, strong enough and large enough to carry him through the air in flight. His countenance was beatific, unscarred by the tumours and mutations that ravaged the humanity of his adoptive homeworld. His rise was effectively preordained.  The angel did his best to belay these devotions, but ultimately knew it would be of no use, when his very aspect was so singular and his genetic talents so obvious. When the Emperor arrived, he found not a battle-king or civil leader he had elsewhere, but a god, ill at ease with his position at the head of a dogmatic confederation of the planet's clans. Sanguinius, possessed of psychic foresight that outstripped any imperial pyscher, save a few, had long foreseen his father's arrival, and the potential consequences of it. Alone, he met the Emperor, prostrating himself before the master of mankind in a plea to spare the lives of those devoted to him, knowing full well the severity the imperial truth would meet out upon his adoptive families. The bargain was struck, and as with the homeworlds of the Sixth Legion space wolves and Fifth Legion white scars, the full presence and rate of the Imperium would be spared from Baal, save that which Sanguinius himself would permit. In turn, the angel would depart with his father and serve at his side, and take his place as master of the Ninth Legion. To give the Legion time to muster in its full strength, Sanguinius was bade to learn the ways of war at the side of the 16th Primarch, Horus Lupacal. While the wolf and the angel formed a bond that was to persist for decades, the Revenant Legion was pulled from its campaigns and combat zones, not informed of the reason for their withdrawal, but expecting it to be some altogether newer and more dire war that required their grim talents.  Sanguinius, in his typically idiosyncratic yet deptlessly empathetic way, did not demand their loyalty. Instead he knelt, a primarch before his sons, offering them his own fealty. The impact of such a gesture cannot be understated. For their entire existence, the warriors of the Ninth Legion had been entirely shunned by the rest of humanity, cast out from the Imperium simply for being who and what they are, by prostrating himself at their fore, by treating them as human, not monster. The angel won their immediate adoration and respect. The worlds of the Tegar system, infested with a strain of abhuman humanity, too divergent to be integrated or let persist, was to be the first crucible upon which the angel would blood his already well-blooded Legion, and in the carnage that ensued he first beheld the darkness that lay within the hearts of his sons. Easily he perceived it too, for he founded a mirror of his own. His foresight showered him with echoey visions, of his blood soaked self at the head of a legion of crimson monsters. Yet, Sanguinius being Sanguinius, he spat in the face of this sight. He saw too the nobility of his sons was not simply an aesthetic aspect of their faces, but was there within each and every one of them. It was a seed he intended to fully nurture. These new blood angels would become the architects of their own fate. The angel petitioned his brother Horus for aid at once, and, as the first of his reforms, immediately assigned each and every company of the blood angels to fight alongside a company of the Lunawolves. Too long had his sons festered in isolation from the rest of their cousins. Now they would take their place alongside the vaunted champions of humanity. This exchange was soon broadened out to as many legions as would acquiesce, something smoothed over by the humility and charm of Sanguinius himself, who proved quite adept at winning the hearts of his brothers not through guile, but genuine warmth and friendship. The blood angels were now exposed to as many forms of warfare as the crusade could throw at them, learning not only the ways of the new types of war-making, but finding as well a newfound kinship with their cousins from other legions. The change in the ninth's character was as rapid as it was extreme. Seeking to emulate their primark in every way, the blood angels cast aside the cold callousness they had been known for, embracing a newfound compassion for those they served and served alongside. Their cannibalistic hunger was reined in, impossible to completely eradicate, but now tempered with an iron discipline enforced through every rank. As recruits from Baal swelled their ranks, they sought to cast off their barbarity of old, striving to become the champions they knew humanity wanted of the Astartes. They embraced culture, art, learning, debate and study, the finer arts even their fellow legions entirely disregarded as being wastes of time. To the blood angels, their only means of tempering their blood hunger lay in the embrace of all humanity's virtues. They still waged war with the fury unseen in all but a few legions, but did so now with an acute intelligence at work behind the crimson war plate. Rarely in the annals of the legion as Astartes has a change in character been so marked and so striking for the sheer good that it did. Not only for the legion, but for all humanity. The blood angels recast themselves, turning on their heel from being the pariahs of the great crusade to its icons. The speed of their assaults, the furies of their wars, the peerlessness of their art, the nobility of their bearing, all became rich pickings for the remembrancers that were drawn and openly welcomed to their expeditionary fleets. They turned from being tacitly hated to being openly adored, fighting at the forefront of the most noble of campaigns for the purest of purposes. Sanguinius became perhaps the most universally adored and respected of his brothers, as within that fractious family, a complex web of relationships, both wholesome and begrudging, had two centuries into the great crusade fully developed. The angel navigated this with a plan, admired by all his siblings, treating each with a warmth and brotherly love that was even known to have cooled Angron's famous collar. Only Horus stood above him, and indeed, were it not for him, Sanguinius would have likely been the head upon which the crown of Bormaster would be placed. Supercal himself, from the accounts of his Mornaval, had on his darker days openly wished it had been so, for he saw his angelic brother as embodying the truest virtues of the Imperium, and presenting the best aspects of their father to the masses of humanity. The Blood Angels followed suit, ever striving now to be the Paragons their gene sire seemed to exemplify so easily, both as cultural emissaries of humanity and as the emperor's descending angelic justice. So, when the call from Horus came to them to prosecute the reclamation of the seemingly lost Cygnus cluster, who were they to say no? The vagaries of fate. One cannot help but dream of that possible future, where Sanguinius had been invested as Warmaster, at the head of a legion reborn to represent the best we could aspire to be.  Ave Imperator. Gloria in Excelsis Terra.


Data mining has become increasingly important for analyzing large datasets over the past decade. It encompasses a wide range of techniques which can be applied to various problems such as time series forecasting.  This paper reviews the most recent developments in time series forecasting with a focus on electricity price and demand markets. This article was authored by Francisco Martinez-Alvarez, Alicia Troncoso, Gualberto Asensio-Cortez, and others.


Baw, what's up everybody? Once again, it's Brand Man Sean and today we got to answer a question I get asked quite a bit. Do artists need to have a website? No, that's pretty much it. Artists do not need to have websites, but it is a nice to have. Let's get into a little bit more detail. For starters, I find when most artists reach out asking me this question, they're at a very early stage in what they're building. The first thing that's most important is getting yourself seen and having a brand. Today we have a way better vehicle to establish that and that is social media. The reason it's so much better than a website is social media has all of these algorithms that if things are going well and you are doing a lot of other things that I'm not going to talk about here, there's an opportunity for you to organically grow. Not only that, there's just this thought process of you could have a billboard in the desert, pretty much a website, or you could go to where the people are and then advertise there. That's pretty much social media today, especially since websites take time and also the fact that your brand might not be completely established and figured out yourself yet. Feel free to hold off on making a website. It's not going to make or break your career. It's a nice holding ground once you start to build something and I know a lot of people ask, well, how am I going to collect people's emails? If you're trying to use a strategy where you collect fans' emails, there's a lot of other tools that you could simply use to collect emails, like a simple Google form. There's so many things that you do not have to have a website. Once again, it is a very nice to have and there are benefits to it, but it is not the first thing on the list. Because ask yourself a question, how are people going to find out about your website in the first place? Nine times out of 10 for a lot of years is going to be social media. That's where most people are going to find you. That's where a lot of people are going to keep up with you. Even if they find you in the world, where you all meet in person or at a show, they see you, they're going to likely follow you and keep up with you on social media. Without social media, getting people to go to your website again and again is expensive because you're going to have to run some kind of ad, still likely going to be on social media just to let them know your website exists or just to let somebody who might already be following you know that, hey, it's time to go back to my website because I released something new, which is totally different than doing a simple Instagram post. This is one of the reasons why even when you look at big artists, they have the most simple websites. You get a little bit of information you can, it doesn't update super often, maybe you get a few tour changes and things like that, but that's about it. Anyway, hope that was helpful for any of you guys who were still asking yourself that question and was just wondering, should I have a website? Is it time yet? You can get one whenever you want to, but more than likely, there's no big loss to not having a website at the very beginning. I would love to hear you guys thoughts in the comments below and other than that, if you liked this video, go ahead and hit that like button. If you like it, you might as well share it and if you're not subscribed, you know what to do, hit that subscribe button.


Thank you very much. I am a professor of population health and disease prevention at the University of California, Irvine, and I direct the training and empowerment for the One Health Workforce Next Generation Project, which is supported by U.S. AID. And I want to thank Sam Wang-Johi for inviting me to this wonderful conference and my colleagues at Afro-Hoon all over Africa have been very supportive of this work. I'm expected to talk to you today about the framework for sustainable implementation and collaborative One Health, particularly in education. So I will cover three major topics. One is the definitions of One Health that demands collaboration. I think the previous speaker really addressed this point in taking us through all of the pandemics from the last century up until COVID-19 and some of the gaps in collaboration that made those pandemics spread and have impacts beyond what we could control. Then I'll talk about the strategic framework describing core competencies for One Health, which is really the goal of this session. How do we decide what professionals need to know when we want to fill those gaps in collaboration that prevent pandemics from happening and other health risks as well? And then sustainability. How do we maintain the collaborations over time, especially during the periods where we do not have problems such as pandemics? I think a lot of the infrastructure that we're building now may respond to COVID-19, but we need to make sure that when the pandemic recedes that we don't let things relax too much and that sustainability will be important and I will talk about what we're doing with the One Health workforce academy. So the definition of One Health demands collaboration. You may all have seen last week the release of the definition of One Health by the high-level expert panel assembled by the tripartite FAO or EWHO and UNEP. And that definition, if you haven't seen it, really talks about an approach that mobilizes multiple sectors, disciplines and communities, which I highlighted on this slide. It is very important for us to not just take these words as mere words, how do we implement them in training and education that builds bridges across sectors, across society, and in the One Health framework of ecosystems, animals and humans. And so in the middle of this diagram, you have communication, collaboration, coordination, capacity building. Some of these competencies that we need to make sure that we're all aware of, but also that experts have the capacity to deliver on these words as promised. An example of that collaboration is a very recent last month, my participation in the technical advisory group for the tripartite One Health field epidemiology training program, a competency framework. Many, many people contributed to this effort. I am particularly proud of working with colleagues in the environmental and ecosystem health sector. And I think the results of this will come hopefully early next year so that we can all learn from it. Very recently, I published in the imaging magazine at the invitation of colleagues in Indonesia, the Indonesia One Health university network. And I talked about ensuring excellence in interprofessional skills for a competent workforce. I can share the link to that magazine for those who want to read it. But one of the things I mentioned consistent with the work on COVID-19 is that the need for international collaboration and training in integrative surveillance is more pressing than ever. And integrative surveillance, in my view, is one of those gaps that we need to fill with epidemiological training. I also want to share with you that we assembled a Delphi panel of experts across many disciplines and professions to help us think through the next generation of One Health competencies. This was presented at the IMED conference that just concluded and a brief summary of the presentation will be published in the International Journal of Infectious Diseases in January. And I will be able to share the link to those who are interested to look at the poster and hear my discussion of the disciplinary diversity and consensus on the panel. And then in terms of sustainability, I mentioned that we're building a One Health Workforce Academy. We want to have an opportunity to develop a One Health certificate program based on the core competencies that come out of the Delphi panel. We have lessons on this academy. We will eventually have a test for completion of the competencies and acquisition of the skills. And this academy we're hoping will live forever with trainees coming and going and employers and students making sure that we have a competent workforce. There is a pathway to certification clearly defined on the academy. For those who are interested, we encourage you to visit and explore what you can do for continued professional development and for employers to recognize those skills. You can preview our courses and pre-enroll. They are competency based and we're beginning to launch case studies, a sequence of courses. The quality assurance is important and we assembled an international board of One Health examiners consisting of Afro-Hoon and Siohoon Southeast Asian members that will make sure that what we build on the academy is of high quality competency based and prepares people for the workforce and those in the workforce can come back for continued professional development. So that's what I want to share with you. I look forward to hearing the other presentations and joining the panel for further discussion. Thank you so much.


Thanks for taking time to attend our session. We would definitely be able to honor you with master's degree in troubleshooting NFV issues at the end of this session. It's going to be a crash course. So my name is Adik. I'm working as a senior cloud success architect for Red Hat, focusing on cloud and open stack with targeting NFV as a primary troubleshooting area. And this is my colleague, Jason. Hi, my name is Jason. I work as a senior technical support engineer in Red Hat. I work in open stack team. I work with integration of open stack with other products. And for some time I've been working on triple low and NFV use cases with open stack. So let me first explore a brief agenda to understand how the presentation is organized. We will first explore the high level architecture of the NFV. And we will then deep dive into exploring the challenges with troubleshooting NFV issues. Then with some examples related with AVNF crash due to canal panic. And Jason will take you over through a series of issues that he had faced with OVS DPDK, I mean non-working OVS DPDK and performance issues related with OVS DPDK. And what are the some of the troubleshooting methodologies that you need to apply to overcome these challenges? So let's get into the basic NFV architecture. So as you all know, open stack is an operating system for cloud infrastructure as a service. And NFV stands for network function virtualization. Originally, open stack was developed to cater the requirements of private cloud and public cloud for enterprises and service providers. But the initial development of open stack was to satisfy or meet the NFV use cases. Later on, we had to adapt open stack to meet or cater the NFV requirements. For this, we had to introduce a lot of changes within the open stack and outside of open stack when it comes to integrating open stack with other components within the NFV. As you know, open stack alone cannot deliver NFV. Open stack is just one piece in the puzzle. So let's try to just explore the basic architecture of the NFV. We have OSS, BSS. And we do have EMS that's connected to the VNFs. And we do have VNFs. And we do have a lot of vendors who build and deliver different use cases for the VNFs. And most importantly, we do have the NFVI platform. And NFVI stands for network function virtualization infrastructure. And the open stack is going to be the primary component that is going to power the NFVI in this architecture. And we do have MANO that handles the management and orchestration for the whole NFV architecture. So from this diagram itself, you will be able to understand how challenging a troubleshooting going to be within the NFV architecture. Because there should be, in a lot of cases, there should be a lot of gay area who is wrong, who is doing things in the wrong way. The symptoms may point that there is something wrong with the NFVI open stack, but the problem may be somewhere else within the VNF or within the way it was orchestrated. So the intention of this session, as I explained earlier, to help you to understand where to focus when it comes to troubleshooting NFV issue. So let me just try to explore what is the fundamental challenge with the NFV. As I explained, we have OSS, BSS, NFVI, and MANO, and VNFs. And in most of the cases, all these components are developed by different vendors in the market. And we are going to stitch all these together to deliver NFV architecture for a telco. So the basic challenge is all these vendors have different level of support and different level of technical support people who are working on these issues. And if there is a coordination between these people, when a telco is hitting a problem, then the problem will go nowhere. So again, to make this makes it very complex when we try to split down, when we try to split each component further, further deep. So that means you use NFVI open stack as an NFVI, and NFVI, maybe the open stack is given by Red Hat or any other vendor. And if you try to go deep into the NFVI, there should be dependency on other vendors. You may be using a different storage vendor. You may be using a different SDN vendor. And you may be using a different vendor to compute services. And a lot of other add-on services are integrated into the, to create the NFVI. So this means you further need to work with different vendors to troubleshoot an issue. So this makes the NFVI very, very complex to troubleshoot. But what we have to do to ideally achieve, I mean, we need to bring all the players into a single table to basically efficiently troubleshoot an NFVI issue. I'm not trying to say a physical table, but virtually everyone should be around the table to troubleshoot an NFVI issue efficiently. So let me just give you an example. So how we applied this methodology in one issue that we heat during well-deploying an VNF on, well onboarding a VNF for a telco environment. So the problem that I'm trying to explain is Red Hat open stack was used as an NFVI. And then the telco used a different vendor to VNFs from a different vendor on top of open stack. So basically the problem was that there is a compute node one and compute node two. And one VNF is running on compute node one and another VNF is going to run on compute node two. And they can run fine. They can spawn the instances, orchestrate the instances without any issues. But whenever the VNFs start transmitting data packets, at some point, one of the VNFs kernel panics, it crashes. So this means there is no pattern. It's pretty random. So you cannot say after five minutes or something like that it crashes. No, nothing like that. It may be one hour or two hour. After two hour you keep transmitting data packets between the VNF. And this is reliably reproducible. So because you just need to transmit the packets, at some point it will crash. And we got the kernel panic message from the VNF and we also got a VM core from the VNF. From that point of view, Red Hat is unable to analyze the VM core because it's using an operating system that people in Red Hat cannot do not know the code for that. So ideally, so the VNF is going to crash on either of the compute node. It doesn't matter on which one. So ideally the VNF vendor communicated that they have tested this VNF in their internal and open stack environment multiple times. For multiple days they have kept it transmitting packets but they never hid the kernel panic. So on the other hand, the NFVI infrastructure vendor, they say the VNF is going to, is crashing. So you need to analyze the VM core and tell us if there is anything wrong with the NFVI that we need to change. So if we work this way, then definitely this is going to be a big problem and we will not find out a solution for this. At this point, we need to have a collaboration between the VNF vendor and the open stack vendor to efficiently troubleshoot this. And we managed to do this and at the VNF vendor, they tried to analyze the VM core and on the red hat side, we tried to analyze what is wrong with the open stack environment. And we got the first symptom, we got the first symptom from the VNF vendor and they are saying that the VNF, the VNF is, both VNF is configured with a 1500 MTU, MTU of the target destination VNF is also 1500. But whenever a packet arrives on the VNF, the packet is getting defragmented because whatever arrives here is a 9K packet, a jumbo frame packet. So we were wondering if this send a 1.5K packet and the packet arrives here as a 9K packet and during the deep fragmentation, the operating system cannot handle the defragmentation of too many packets that it crashes due to a bug. So this actually helped us to deep dive into how the packet is being transmitted from one VNF to another VNF within the open stack and where is it actually, the packet getting changed into a 9K MTU. So to achieve this, we ran a TCP dump on all the intermittent interfaces to see where the packet, though originally it started with 1.5K MTU, where it getting changed into a 9K MTU and we found that within this flow, either on the tap interface, either of the tap interface, the packet is getting from changed into 9K MTU. So this actually led us to explore further and understand and investigate why the packet might be getting assembled here to a 9K MTU, though originally it started with a 1.5K MTU and we found that the open stack is configured for 9,000 MTU and the VNF is configured for 1.5K MTU and due to the security groups, being security group rules being applied on the tap interface and the way the IP tables works is that to apply the IP tables rules on a packet, it would assemble the packet to the maximum possible data packet size before it applies the IP tables rules on top of that and because this has a 9K MTU and to apply the security group rules, the packet is reassembled again into a 9K and after that it is never fragmented and it goes directly into the VNF because the VNF cannot handle jumbo frames, it again need to be defragmented. So you would originally, you would really think that, oh, this is very easy to troubleshoot, right? Change the MTU of the VNF to 9,000. It's very simple, right? Why don't you just change the MTU of the VNF to 9,000 to resolve this problem? But that is a problem because the VNF is not built to support 9K jumbo frames MTU. So we cannot change the MTU of a VNF to 9K, that's not a solution. Then you would think, why don't you change the MTU of OpenStack into 1.5K to match, to sync with the MTU of the VNF? It's very easy, right? But no, because the problem is that OpenStack does not support changing the MTU per port. You need to change the MTU of the entire OpenStack deployment. That means the same environment is expected to cater a lot of other VNFs which is going to get huge network performance benefit by using the 9K MTU. So by changing the whole OpenStack into 1.5K MTU, so we are actually killing the performance of all other VNFs, so it's not a solution either here. The other important thing that we could explore as a solution is enable port security. So port security is basically a feature within the latest OpenStack to actually disable security groups per port. So that means you may guess, why don't we just disable the port security so that there will not be any IP tables rules, so the packet will not be reassembled at the tab interface to 9K. So it's a right guess, but this is not true, because with port security, we are not bypassing the IP tables layer. We are only bypassing the IP tables rules. So there should not be any rule within the IP tables layer, but there should be a single rule that is accept everything. So to apply that single rule, the IP tables kernel will again reassemble the packets. So this is not a solution either. So another solution that we explored, the VNFs, none of the VNFs in this environment requires security groups. So why don't we just set a bridge NF call IP tables to zero so that the IP tables will be completely disabled on that specific compute node. So this is an acceptable solution, but the problem with this is that we cannot import any other VNF, which may require IP table support or security group support. So we explored this option, and we originally implemented this option, and we then again explored further options. So from the VNF vendor side, they did further research, and they inspected what can be changed on the VNF to support this, and from that investigation, they found that the VNF was configured to use an E1000 emulation, and if we change this NIC card to use what IO, so then they see that it improves the performance and it again prevents the crash. So why because the crash happened because of a bug within the E1000 emulation that is within the E1000 driver that is being used within the VNF. So it gave them two benefits, either I changed the performance improvements, then also a solution for implementing the prevent the crash. So is this the ideal solution? Of course, no, because the package still gets reassembled and defragmented. It's going to affect the performance. So ideally we should, the ideal solution for this problem is, OpenStack should support per port MTU, or at least per network MTU at a minimum, so that we can specify that the port that the VNF is connected should have a 1.5K MTU and all other ports within that network environment can use jumbo frames or 9K MTU. So with this, so we have created a bug, upstream bug for this and we have internally also recommended that to efficiently support and to efficiently make the VNF working within this environment with for telcos, we must support 1.5K MTU and per port MTU within the OpenStack. So as I explained earlier, we didn't apply any of the solutions that I explained earlier, because they are not, they have its own set effects. It's not fit as a right solution for this problem. Then we came back into the two last solutions and within this, this is something need to be developed within the OpenStack, so we cannot implement this right now, but and we finally decided to, to implement this solution. So that's all from my side. So what I want to highlight here is it was a great collaboration between the OpenStack because there was nothing wrong with the BSS and OISES and the manual orchestration layer here, because the orchestration was completely successful. The problems have started after the orchestration. So we cannot, we can rule out the possibility of the OISES, BSS or other manual layers causing this problem and we came down into the two options, either the problem is with VNF and or the problem is with the NFVI infrastructure and as you know, since we collaborated, we were able to find out a solution from the VNF point of view and from the OpenStack point of view to solve this problem. So this is more important if we collaborate, we can get a solution. So and it's very critical to collaborate more effectively within the troubleshoot NFVI issues. With this, I will hand over to Jason to walk us through some of the issues that he has been working. Okay. Thanks, Sadiq. So what I'm going to talk today is OIS DPDK troubleshooting. So what I want to present to you is the methodology we use troubleshoot OIS DPDK. So OIS DPDK is a very important and very interesting technology. Why? Because you can use any hardware and a NIC that supports DPDK and you can have fast packet forwarding using this DPDK libraries, which we are using in OIS. So although it is very interesting and it's very beneficial, people who have deployed an environment with DPDK would have known there are a lot of challenges around it. Those challenges mainly come because it DPDK, OIS DPDK integration requires an understanding of the hardware some configuration on Linux system and some configuration on OBS. Something goes wrong, then it may not work well. So before I go to the methodology and then to a scenario where I explain a scenario where we troubleshoot DPDK. So let me tell what you're looking at. So you have a compute node, which is Linux system. In my case, we usually use Red Hat Enterprise Linux version seven. You have some CPU cores which is isolated and tuned for this PMD workload. You have a NIC card which is supported by DPDK, which will be associated with VFIO PCI driver. And you will have huge pages configured for your instance and OBS, how much ever that is required. You will have OpenVswitch version 2.6 or 2.5, whichever has DPDK, it's fine. You have configured OpenVswitch with one NIC card. You have enabled huge pages per socket or however you want to configure it. You have already decided the cores you want for pole mode driver thread because you need to assign some cores for DPDK. And you should also need to know the number of memory channels which are configured in OpenVswitch. So this is a classic example of your environment. You have a VM with vortio emulation via LibWord. It acts as a Vhost user socket which your OBS DPDK or your pole mode driver thread will pole and get information and it will also communicate with your actual card. And it will make things work. So I have usually come across two types of issues when troubleshooting OBS DPDK. One is OBS DPDK does not work at all. You spawn an instance and it does not, you cannot ping it, you cannot ping outside, you cannot ping inside, nothing works. Other scenarios, when you get something to work you can ping outside, you can ping inside, but it does not match the performance you are expecting. So it's like fast data, so fast packet forwarding, right? So you would expect it to be much better and you may just find maybe like 30, 40% that's a big difference 30%, 30, 40% of what you expect. It's a big degradation, right? So these are two types of performance issues that I faced with OBS and I want to explain what are the normal methodologies I developed to fix the issue fast. Fixing the issue fast is a more critical thing for us. So there are two things that I do first. So that I can fix the issue in probably five minutes. Just run OBS VSCTL show command. What will I look at? I look at the output, does it look as it is expected? I expect a DPDK bridge, a net dev bridge. I expect a DPDK port under it. Everything looks fine. There are no errors seen. That's what I expect in OBS VSCTL show output. The next step is if at all that output does not give enough information, looking at the VSWD process log is also very important. So the main thing that gives you this benefit is this open VSWD process use DPDK library. So when open VSWD process starts, that is OBS-VSWD process starts, it initialized all the source required for DPDK. That is it starts the PMD threads. It detects the NUMA architecture of your compute node. It spawns a Polymode driver threads on the right course. The Polymode driver threads access the huge pages that is configured in your system. It creates, you already have a net dev bridge for DPDK. It will create a DPDK port. It will detect the NIC which you have assigned for DPDK and add the DPDK port inside the net dev bridge. So all these information you can see just in this log file. So it's a very important log file. It's a var log open VSWD. So the next step what I do is to check configuration of open VSWD and check the hardware. Does it match? So there are multiple things inside this that needs to match. It's supposed to be NUMA where you need to have core that is optimum for use of OBS DPDK. The next point, so just by checking the configuration you have for open VSWD, open VSWD DPDK and the hardware you have is not enough because your understanding of the hardware may be wrong. So you would probably set something in OBS DPDK and it's trying to accomplish that, trying to assign those resources. If there's something wrong about it, it'll just fail. So you need a tool or you need a set of commands which will give you a real-time information of what's happening in your Linux system. What's happening to your Polymer driver? Is it able to start the right way? Is it able to use a course that you wanted to? So all these informations are important. I will not list out all the commands required. There are a lot of open VSWD-related commands which you can use to check the output of the NetDev data path, is there or not, or the DPD port is not, there are a lot of commands. But I want to just give you an example. Some of the important commands which I used to get information from the Linux system itself is driver CTL to list all the PCI devices and the driver associated with them. So DPDK use VFI or PCI driver so I can make sure that the driver I want to use is actually associated with VFI or PCI rather than the kernel driver. The second command is also very interesting. I use PS command to list all the threads on the system. So open VSWD process starts the Polymer drivers as P threads and so if you do PS-EL, capitalized for thread and you can see under OVS, you will find a PMD something, 54 or 55 or something based on the PID. These are the threads, PMD threads. So you can see the threads that are running. You will notice that they have 100% CPU utilization because it keeps on pulling on the core. On that it keeps on pulling the socket and the NIC. So you will find the CPU utilization is 100%. You get the TID, the thread ID and you can check inside your PROC file system the NUMA map for that process. So ideally in slash PROC, you don't see thread ID, you only see process ID, but although it does not show a directory, you can still put the thread ID and you can check the NUMA map and you will find which all huge pages this Polymer driver thread is using. It's a very interesting command. I will show this later. Other as to check the huge pages assigned in each of the NUMA node. So you may have 12 huge pages of 11 GB, but you can assign all the 12 on one NUMA node. Another NUMA node can have zero also. So this is a very important command. And the last is you can also run a packet capture, packet capture as you know that in OBS DPDK you cannot use TCP dump because it's a user space process, PMD is the user space process to capture that you cannot use TCP dump. You can use a tool provided by DPDK, DPDK P dump which you can compile and use it. So the next set of issues, the next set of kind of issues I've seen is performance troubleshooting. So this makes it little more tough because you've got everything to work. So a simple log file does not, may not always help. So you have to understand the scenario. So first thing is to understand the scenario. What was the test about? Is it, what is the source and destination? Are they both VNF running on a compute node with both DPDK running? How are you testing it? Which tool are you going to use to test it? What is the packet size you're using? And how much you're getting? So all these gives you a good understanding plus the network devices in between them. They gives you a good understanding of what you're exactly trying to do. And then you can come to, what is the expected performance for the hardware? And plus the percentage degradation. Percentage degradation does not give much, I mean, it does not give you a quick hint of anything, but you will just know that how serious is the issue. I mean, it's a big difference or small. And so at some point, it will give you a good clue of what could be the issue. Next is the obvious configuration complements the hardware. So it's not that the obvious configuration is wrong and DPDK does not always DPDK does not work at all. There are scenarios where you can do the configuration wrong and it will give you bad performance. For example, memory. So you configure open V-switch with memory channels. So these memory channels are something on your motherboard. Each NUMA node has some memory channels on which your memory sticks are on. So what happens is when OBS assigns huge pages, it is good, it gives you good performance if OBS can set these huge pages at, huge pages contiguous space. So if you can assign this huge pages at the start of every memory channel, when OBS PMD thread starts, it can associate the objects at the start of this, which gives best performance. So if you give wrong memory channel, it will not work well. Your motherboard can have a riser sort slot. If your vendors build your server, probably they already know and they've kept your neck card on the best PCI slot, but it's good to look at your motherboard data sheet to understand if there's any other, any riser slot and you're not using this slot or a better performing slot on your motherboard. You can enable hyper threading course. So what you can do is enable hyper threading and make the Polymer driver threads use the sibling course. So advantage is this Polymer drivers maintains a cache for each core. So as much cores that much better. So you can also set optimum receive queue. So you have an option to set receive queue for DPDK physical port. So the next is you can have the course on which the Polymer driver runs tuned to this workload. Because this is a special kind of workload where the PMD thread takes 100% of your CPU cycle and you will need to isolate it to make sure no other processes run on it. So what I do is I use a tool called tune D and then there's a profile called CPU partitioning. So what it does is it adds an option inside inside the kernel which makes sure that there are no CPU ticks on this core. So that is if in case the processor or the core has only one process. If there are multiple processes does not work. So it's necessary that it has to be isolated. It has to have this no HZ full and the cores which are going to use for Polymer driver. It gives good performance. There are a lot of things that you can look at. Avoid mixing kernel data path and net dev data path on your compute node. If you have made something like that, your packets can take both paths and can give you low performance. You also have BIOS recommendations from DPDK developers, which is also there inside the OpenVSwitch guide which I will mention it later. So you will need to apply those BIOS optimizations to make sure the CPU or the cores run with maximum benefit of your system for the Polymer driver to work pretty quickly. So the next is a little more interesting point to understand which cache it's a lot. So in your OBS DPDK for you to get the best performance you need to, your traffic needs to get all the flows resolved in EMC cache, that is exact match cache. This is a cache that is maintained by the Polymer drivers. It's a part of OBS DPDK and if your traffic frequently hits this EMC cache, you will get best performance. But if at all, so the EMC cache has something called as a hash and there's an algorithm to fetch the flows from the hash. The size of EMC cache, everything is pre-compiled when you compile the OBS with DPDK libraries. So if the EMC cache misses, then you go to the mega flow which is also something in OBS in memory. If that also misses, so there is a considerable penalty or degradation of performance in mega flow. But if mega flow also fails to resolve the flow, it will go to open flow from OpenVSwitch which gives a very bad performance as equal to using ML2 OBS by itself. It is also very important for an individual to understand what is the next version of OBS and what version of OBS you're using because there are features coming in one by one and there has been a lot of active community contributions of suggestions and code to improve the performance of communication via OBS DPDK. For example, in OBS 2.5 and 2.6 itself, there are a lot of difference like MTU or having multiple QO or so on. So having a good understanding of which version of OpenVSwitch you're using, what are the drawbacks of that version and what is the advantage of the next version would be good. Profiling is the last pointer I have. Profiling is something you only go to when you get the issue. Otherwise you cannot simply profile a component because unless you are sure this component or there's a PolmoDrive thread is not functioning at its maximum or there's some kind of saturation. So then only you can get something out of profiling or else you're just getting a lot of data without any strong hint of this is the root cause. So let me come to OBS DPDK failures. So this is a scenario which I told first that it does not work at all. So this is the symptom, it does not work at all and this is the architecture. It's a common generic architecture. You have a NUMA hardware, there's two NUMA nodes. There are some set of cores. There are some set of memory sticks on each core and there's a NIC which is in NUMA node one which I'm planning to use. So I will talk about two scenarios in this OBS DPDK failures. So first issue is it does not work. That is the issue. It does not work at all. I start the instance, ping does not work, nothing works. So first thing I do is I took a look at OBS VSTL show output. And I see everything is almost as it's supposed to be. There is a BR link zero which is my net dev bridge and there is a DPDK port. Although DPDK port there has been some error in creation. So it says cannot create PMD threads due to out of un-pinned cores on NUMA node zero. So I could probably look at the next step. Let us look at the open VSwitch log and I found the same error. I could not find anything more. So just by looking at it, I would probably guess that open VSwitch was trying to start the power mode driver. And something went wrong when it tried to start a power mode driver thread on NUMA node zero. So next, so where is OBS trying to start the power mode driver threads, PMD threads? So I had to look at the OBS open VSwitch database. There's a column or other config and I look at the mask. It's 28, 28 is a hexadecimal value. I'll just convert it to binary. So this is CPU used, CPU mask starting from right to left which is from zero to nth CPU core. So in this case, zero, zero, zero, one, zero, one. That means it started zeros, first, second, third, fourth. So second and fourth core is the one which open VSwitch is supposed to use as per my configuration. I'll just have a quick look at the NUMA topology. There are a lot of commands. There are two, three commands which you can see the NUMA topology I usually use the NUMA CTL. So a quick look says core two and core four is on node zero. So what about node zero? Why is it not able to start on node zero? But DPDK port, NIC and R and port and NIC are on node one. So I can just use that OBS, OBS it'll show. So OBS it'll list interface and I can just say check the status and you will get a lot of information in the status. I just want to concentrate on the NUMA node over here and says NUMA node one. So you would probably say so what? So what is our issue here was that we were using OBS 2.5. So in OBS 2.5, the code forces a pole mode driver to be in the same NUMA node as the NIC port. You will know, you may have read somewhere that OBS 2.6 is NUMA aware. So you do not have this feature so that that's why it failed to start the pole mode driver. So this is what it was for OBS 2.5. What we did is we just move the pole mode driver to node one. So how did we do that? We just went to the same database and set hexadecimal value to use three and five cores inside this other config PMD-CPU have in mask. And we were able to fix the issue. Similarly, another one issue where OBS DPD cannot work at all. So first thing for me was to just look at OBS CSE to show output, see what's going on. Just like before, everything is fine except the DPDK port seems to have some error while creating. And this looks something more similar. It seems like cannot allocate memory, which looks very simple thing. So if I were to guess, I would say it tried to start the pole mode driver thread and it could not allocate memory. Why is that? So what exactly gives us information about which memory to use? So I am using huge pages. And huge pages, we mentioned which socket, how much memory we have in OBS DPDK. So I just had a look at the log, OBS vswtd log. The output is little more than what I saw in previous output. Here when the OBS vswtd process started, it tried to start the PMD thread and it crashed. Segmentation fault, it gives some more ideas. Segmentation fault means it's not able to access the memory segment it wants and crashed. And later it comes to the same error which we see in OBS VTL CTL short put. Something around socket one, possibly, right? So what next? Just let's look at which NUMA node it uses. OBS DPDK uses a NIC card which is in NUMA node one. And the next output shows looks like the socket, sorry, the NUMA had 8 GB of huge pages, sorry, the OBS DPDK had 8 GB of huge pages on node zero and 4 GB of huge pages on node one. Which is no reason to crash anyways. So you have some huge page, right? So it should still start the poor driver. So OBS trying to start, it knows how much it needs to allocate but does Linux provide that huge pages or not? So before you go, that's a by default Linux, if you enable huge page on Linux system, it divides the huge page across different NUMA nodes. So if you have 16 huge pages of one, one GB and you don't have any other configuration set in sys, sorry, start up, it will divide that 16 into eight huge pages on each NUMA node. So when your system comes up, you'll find eight huge pages on node zero and eight huge pages on node one. So you can get that information from sys file system. So I just had a look at the sys file system and I noticed that for nodes zero and one when I checked. So I do find 8 GB for node zero but zero for node one. So that means the Linux does not have huge pages ready for node one. So if any application tries to grab a huge page from node one, it will fail. So that is the root cause of the issue that the system did not have huge page on node one. So just to fix this, we just enabled echo four into the sys file system. So I did not require reboot. So what exactly happened was while testing all these configurations, we made a mistake of setting zero to node one, NUMA node one. So there was no huge page on that. And we had never rebooted the system to test it again. So it always remained a zero huge page on NUMA node one. Although I don't need to reboot it, I just need to directly set huge page as how much of a required by OVS. And that fixed the issue. So these are the methodologies I use. These are the issues we faced. But it does not cover everything. There are more points to add. There are more suggestions. I've also come across a question, how to check if there's a saturation, or check the CPU caches to understand where the performance. I'm still looking at more and more tools to understand what we can do to figure out quickly in OVS DPDK to understand where there could be a bottleneck issue. So for coming across all these steps, I had gone through OpenVswitch DPDK install guide, how to guide the Intel articles, the DPDK programming guide to make up all these steps to understand how we can do things better. So that's all for me. Let me just conclude this. Jason explained some problem that you may hit with NFV, maybe deep into OpenStack and the networking stack that you can fix alone. But some problems, it may not be clear initially where the problem is actually is. So it's very important that you drive the collaboration with multiple vendors. And let this presentation be a motivation for you to drive that level of collaboration. Thank you very much. So if you have any queries, you can come over at the mic and ask them. Hi, one of his group is saying I'm from Spartan Communication, and I have a question regarding measuring latency at the virtual interface between the various virtual entities, let's say between the BNS or if you are using OVS DPDK between OVS DPDK and the BNF and things like that, are there any tools out there to measure latency between the virtual entities? I think there are different tools that comes from different BNF vendors, but I cannot pinpoint you so exactly what general tool that being used. So there are a lot of, it all depends on what's your use case for the latency and how much you need to achieve. Right, so if I'm trying to troubleshoot, let's say, latency issues, and I want to find out which particular virtual entity, which BNF, or is it the OVS switch or DPDK, wherever the additional latency is getting introduced or service degradation is happening. So exactly, so if you want to find out whether there is any latency problem within the OpenStack layer, you basically need to use a lot of tools, profiling tools that Jason recommended. Maybe he can give you more details. And if the latency is to measure whether the latency is within the BNF layer or on any other layer, you may have to use a latency measuring tool recommended by the BNF vendor. Ultimately, you need to prove where the latency problem is. Maybe you want to. Does the hard part, the hard part? Yeah, sorry, go ahead. So at the first step, maybe I was at short one PMD hyphen show command, dpi of something slash, in which I showed EMC cache. So it also shows you the CPU cycles. So it shows that polling takes 100%. There's another one section, which is processing. So maybe at the first point, you can just look at if the processing percentage comes close to 100 or something like that. So basically, you're saying the processing cycles are coming to the top or threshold. That means that that will introduce additional latency and that might be causing the problem on the OVS Yes. OK. All right, thanks. Thank you very much. Thank you. Yeah. We just have two minutes. OK, my question is if you did any tuning inside the guests, because in my experience, I activated the multi-q and for instances. But when you do the performance test, you always get it on the same CPU. My question is if you've done any tuning inside the instances for this project? I think multi-q is already available within the KVM. And I think it's still not applied within the open stack layer. And I mean, there is still work in progress to support multi-q. And on the other hand, the other tuning that you can do inside the VNF is basically implement DPD can set the VNF as well. So the packet that comes from the hypervisor, by passing the hypervisor kernel, it also bypasses the VNF kernel and directly goes into the user space mode. But this is conditional on the support from the VNF vendor to tune it. And other tuning is really specific to the VNF. I don't see any general recommendation that I can provide that can be applied for all the VNFs. Because VNFs are having different operating system and different way of handling. It handles different functions from routing DPI into a lot of other functions. There may not be a single tuning parameter that fits every VNF use cases, right? It's going to be specific. So just to add to that, the multi-q you mentioned, you'd enable that from the VNF instance? No, I enable it. On the flavor, on Nova, you can enable it on flavor. But when you start the guest and you start doing performance tests, you always get it on the same CPU in the network. So what I did, inside the instance, I activated some kernel parameters that spread the load between all the CPUs. And my question is if this is recommended or not. And in your experience, you also do that? Yeah, multi-q is definitely recommended to give you the best performance. But there is still work needed to be done to manage the multi-q efficiently within the open stack layer. It's already there within the KVM or the hypervisor layer. So if you spline LibWat and KVM, it will work without any issues. But there should be a lot of testing and everything to make sure that this is working as expected. When you put it on open stack. Thanks, everyone. So you can catch us any time if you have more questions. And thanks for listening. Thank you.


master detective tonight's curious adventure missing Harold escort for Nick Carter and the great kidnapping mystery and here's Nick Carter himself to tell you the story as you've probably already noticed I'm not going to tell you the story that I announced last week instead I want to tell you a rather different kind of tale one would start it as Patsy and I rang the doorbell at the rather magnificent home of Mrs. Philip escort just off the upper end of the park at about 10 30 one morning yes I'm Nick Carter Mrs. Ascot's expecting me yes Mr. Carter won't you come in please thank you if you and the young lady will go into the living room I'll tell Mrs. Ascot you're here certainly gosh Nick the escorts must have more money than they know what to do with just look at this place yes Patsy the escorts belong to one of the oldest families in the city old and conservative rich but never ostentatious so I think I wish I could I think I hear Mrs. Ascot coming oh Mr. Carter I want to thank you for coming so very promptly I know how busy you are but I really am in trouble desperate trouble and I don't know who else to turn to but you why Mrs. Ascot I'd be very happy to help you if I can this is my assistant Patsy Boone how do you do now what's wrong it's my son Harold mr. Carter he's been kidnapped I found this note inside my newspaper this morning what is it saying says we've got your son you want him back don't call the cops we'll tell you what to do later there's no signature can you tell anything by that letter Mr. Carter of course the handwriting is obviously disguised half printing and half writing papers good bond paper as a watermark it looks like a dragon's tail top of the sheet of papers been cut off pair of scissors apparently is the cut isn't quite even why do you suppose they did that there was probably a letterhead on it and the writer didn't want the paper traced of course but they didn't cut quite all of the pinning off can't read what's left but later on it may help to identify it looks like hotel stationary doesn't it me especially just what I was thinking I'll have scabby make a run of the hotels and see if you can find the one it came from who mr. Carter do you think you can find my boy I certainly hope so mrs. escort and I'll do my best but in the meantime just sit tight and wait until you hear from me again or until the kidnap gang makes its next move hi and Nick didn't take you long to get here no time to waste in the kidnap case coming you never could be sure when the gang will get frightened or annoyed and kill the victim are you fine the same kind of note paper here you say I sure did Nick the same size same watermark and as near as I can tell from what's left in the kidnap note the same pretty at the top good but what now Nick how does the paper came from here help you know the paper came from here it's quite possible that whoever wrote the kidnap note was staying here in the hotel at the time yeah and if he was the hotel register may give us a further clue oh but the handwriting on the note was disguised Nick quite so scabby but it's impossible to completely disguise any writing so that it may not be identified even when the writing is apparently completely changed there will always be some peculiar characteristic left that'll give it away oh I didn't know that oh clerk is you mind if we look at your register a moment not at all sir here you are now let's see young escort disappeared on Tuesday afternoon and it's possible that's a signature we want might be under Sunday or Monday's date well you know what to look for yes or no scary I've memorized the looks of the writing in the kidnap note and I expect to recognize any similar peculiarities in a signature here no nothing here under Sunday's date let's try Monday okay right over here here here look at this one James Cannon I never heard of him of course you haven't either of I but look at that s yeah and the J note how oddly they're made this signature like the kidnap note is half written and half printed to ever agree the work of a man to learn to write late in life and a man who never writes easily oh I see what you mean no questions got me this is our man yes sir is this James Canada in the hotel James Canada no sir he checked out this morning I was afraid of that you recall what he looked like medium height sandy haired little mustache he had a crooked little finger on his right hand I remember him because he asked a lot of questions last night thanks for well do you know I'm like well yes coming but I sent that man up the river three years ago for a five-year stretch well maybe he's out maybe I know a man who can tell me I'll get my ring and see come on well whom did the description fit Nick sounds like Jack Vincent scabby yeah for journey con man no time or the business I can't see for the world how oh pardon me for a minute oh sure Nick I'll wait here this is Nick Carter oh fine fine thanks say a bill is Jack Vincent still up at state prison oh two weeks ago no nothing special yet well thanks Bill good luck goodbye well what do you say Nick Vincent was pardoned two weeks ago he's our man all right you know it's a funny thing Nick but while you're in there phoning a couple of men went by me and I heard one of them say to the other I saw Vincent grady's bar last night maybe that's where he hangs out you say you just heard that now scabby yeah just now that's clear oh how do you mean scabby things are going a bit too easily a note paper that can be traced the name and the register the description and now the conversation you say you overheard you mean you think it's some kind of a frame up might be scabby oh gee if it is Nick you better is I'm going ahead just as I was before just be a little bit more careful that's all well they want me to go to grady's bar that's where I'm going see at the office later scabby pretty Jake hook line and sinker just like you said I got a hint to you and you told him where he could find me I said it real loud right beside that stooge is I said I'd seen you in grady's place here he's coming here now yeah I beat it on a head to let you know he was coming good we'll take care of him when he gets here you're off with smart Jack ain't no wonder I can't go for you but don't forget I only want to he sent my pop to the chair for bumping off that old rat of a watchman last winter I ain't forgot that you bet you okay cut the gab looks like Carter's coming in now he can't see us where we're sitting yeah that's him hey do I look okay in this apron I borrowed from paper sure you look like a regular waiter Ben hey got a tray here right here you sure he don't know you been broke up my record last year but he never seen me we all got it in for him eight week you bet we have and here's where I pays off watch bring me a large in general cool coming right up lots of familiar faces here but nobody really know one intervention might have moved out of town after this match and that conversation scubby overheard if he did over here it sounds to me I said oh thanks yeah give a change thank you sir well at least this ginger ale's cold doesn't taste that bad so the odd flavor to it must be a new brand of coke they mix with it and see that I enjoy it isn't hot enough in here to make me dizzy like this it seemed to be Nick you fool you've been doped you bet you've been you must have made it strong you bet I did I ain't taking no chances I put three of them in I go on goodie and get the car and make it fast I don't want none of Carter's friends to come looking for him before we can get him out of here okay this is the day I've been waiting for for three years it's like a great detective does he all tied up and gagged like that I'll say don't he looks more like a trust up chicken or a dead duck and that's what he's going to be as soon as he wakes up dead duck you mean you ain't gonna kill him now there's no fun in killing them when he don't know who's doing it I want him to look me in the eye when I sent a bullet into his brain oh gee Jack I thought you'd let me kill him nothing doing this is my party private and exclusive to get his guns yeah both of them hey should we leave him here in the back room for now Jack yeah he won't come to for another couple of hours you'll be safe here you will Gertie stay here and watch I got some stuff I want to take care of I'll be back with the time he wakes up okay here you go mr. master detective day you stayed till we're ready for you have a nice sleep and keep your eye on Gertie then she might forget and bumpy more fall by herself Carter's office why no he isn't has something else come out good heavens a hundred thousand dollars I've no idea where he is he should have been back here long ago you better just do nothing as he said until we hear from him he's bound to call me pretty soon unless unless something's happened to him being such an idiot I knew what I was walking into and I walked right into it gosh but it's dark in here wish I could send my cop to the chair did you never send nobody else there cuz you ain't gonna live no longer I'm gonna fix you right now I'm but so I'd have to be so rough with you lady it's my life for yours you're only stunned now I can reach that knife she had dropped before she gets her senses back I can cut these ropes they're only see behind my back where is that my able to reach it now just quite quiet you try to call for help I'll be forced to kill you did you I heard you coming in so I sat up stuck my legs out and kept you you dropped your knife knocked your head on the floor and I stunned you then I found that I've cut my ropes now I'm getting out of here no you can't Jack I'll kill me he'll murder me should have thought of that before I don't try anything your friends overlook this little pistol I carry in my shoulder hoster it's very small but effective I assure you what are you gonna do why'd you do open bring me here to kill me well Jack and Ben were scared you'd try to break up their plans for the kidnap job listen carefully who else is in this house now only then he's in the next room when I tell you to call Ben tell him you're afraid I'm waking up ask him to come in here but don't you warn him you want me to ask him to come in here yes but no funny business now call him all right then then I think Nick Carter's waking up you better come have a look at him yeah now stand aside I'm leaving here and don't try to stop me I'll be seeing you both later under different circumstances in the world if you've been we've been waiting for you for hours sorry Betsy anything special been going on anything special I should say so Mrs. Ascot is called five times she got a note from the kidnappers telling her it would cost her a hundred thousand dollars to get her son back and she's going crazy waiting for you to tell her what to do Hey Patsy have you heard anything from me scubby well Nick what happened to you Jack Vincent laid a trap for me and I walked into it did you learn anything no scubby I didn't accept that it all has to do with the kidnap case we're working on well did you have any trouble Nick well depends on what you call trouble scubby tomorrow that later what about Mrs. Ascot well she wants you to call her as soon as you come in I'll get her for you all right Betsy you gotta move fast maybe too late even now my being there and getting away doesn't help any Mrs. Ascot just a minute please here she is Nick hello Mrs. Ascot sorry I've been held up where you couldn't get hold of me what's up oh Mr. Carter I received a note from my son it says that I'll have to pay his kidnappers a hundred thousand dollars if I want to get back the note also says that I've got to take you off the case or he will be killed he says that so far they've not mistreated him but he begs me to pay the money and get him free is the note in your son's handwriting oh yes yes I'm sure that what shall I do Mr. Carter or does the note give you any way of getting in touch with him yes it says to put an ad in the personal column of the clarion address the safety and let them know what I decide good put the ad in the clarion tell them you're willing to pay the money and ask them how they want to pay all right Mr. Carter but not getting rid of you you know what I understand Mrs. Ascot tell them in the ad that you'll guarantee that I'll have nothing further to do with the case but that that would be alive wouldn't it yes of course it would but would you prefer that the kidnappers kill your son all right then put the ad in just as I said and let me know the minute you get an answer then we'll plan our next step Carter I'm so glad you come an answer to the ad that I put in the paper just came in the morning mail here it is thank you on route 77 be five and two tenths miles north of route 31 is a large single oak tree right beside the road it's the only tree around make up a bundle of 10 20 and 50 dollar bills $100,000 no throw the bundle out at the foot of the tree this afternoon at five o'clock sharp drive by it not less than 25 miles an hour and do not stop your son will be sent back to you tomorrow morning you'll be alive if you follow directions he'll be dead if you don't pass it where's that map I asked you to bring along here it is Nick I still don't know how you could tell what section of the state we're going to need a map of Patsy when I went back to the gang's hideout yesterday afternoon it was deserted the only things I could find that interested me were a rough draft of the original kidnap note made in the back of an envelope addressed to Jack Vincent and also a timetable showing trains running to a certain part of the state and what part was that the part I asked you to bring the map up very simple very simple to you well where is it here now let's see route 77 B is here route 316 crosses it right here it's about 45 miles out of the city a very thinly settled section what shall we do about it mr. Carter we do just exactly as the note says have your bankers make up the bundle of $100,000 in 10s 20s and 50s take patsy with you and have your chauffeur drive you up to the spot designated in this note throw the bundle out and then leave the rest to me I'm sure glad it's clear today otherwise we'd be out of luck see anything scubby no that's yet hey Nick do you suppose anything has gone wrong I doubt it I have entire faith in Patsy's ability to follow instructions she sure as sort of deserted around here isn't it yes only a few scattered houses and very little traffic oh yes scubby suppose you take over the controls of the plan for a while while I take the glasses and have a look around sure Nick here thanks got the stick yeah I'll set these glasses are really our power don't they hey I think I could yes yes there they are and right on time are you sure this is the right road James yes Miss Asgard this is the right road oh I feel so much safer if mr. Carter were here why if any little thing were to go wrong it might mean my boy's life that's why I'm here Mrs. Asgard just to see that nothing does go wrong the place you want is about a half a mile ahead Mrs. Asgard dear so soon I'm all of a jitter miss Bowen you'll have to throw the package out I just can't do it now don't you worry Mrs. Asgard I'll take care of everything slow down just a little will you please James yes miss I wish I knew how Nick is planning to get the money back again could go anywhere from here and we'd never know where it was I hope mr. Carter won't do anything to to end fear with my getting my boy back he's worth all the money I have you can trust Nick to do the right thing there's the tree just ahead now help me up with the package all right that's it yeah no I'm gonna let it go out the window here it goes that's that oh you're wonderful miss Bowen did you see anybody no no nobody not a soul around here anywhere I still can't see anybody the bundle is still right by the side of the road where it fell oh heck this curve cuts off the view entirely well at least we've done our part we've done our part the rest is up to Nick yep those are Nick's orders sheriff drive as close to the house as you can and then park your car in the bushes just off the road okay where's Carter now oh well he went on ahead to get the layout of the place wants to get his plan set by the time we get there I don't understand how you know them fellas are hiding out there you say neither you nor Carter never been near the house well I'll tell you sheriff it's really very simple when this is escort drop the bundle of money out of her car this afternoon Nick and I were overhead and explain watching everything through his extra high-powered field glasses yeah we saw the crooks come and pick up the money and then we watch them beat it back to the farmhouse they took every back road and cow pad they could find a keeper being fallen but we could see them no matter where they went yeah all the time the one man that they're really afraid of was up there over their heads watching hey that's quite a stunt I've heard tell me sneak Carter's quite a fella I don't believe closer to the house with the car I'll just run her off into the bushes here so I wonder where Nick is you ought to be here anymore yeah I want to take a chance and find the window and see for myself I want to be able to slip the latch and I know window like this this knife will do what I think longer I guess it's safe to use my flashlight here sound keep absolutely quiet you all right yeah quite a pretty bad cold yesterday though but who are you you're not one of the game I'm not one of the game I'm Nick Carter yes gee I've heard of you you're gonna save me huh that's just what I'm gonna do I'll get these ropes off your arms and I feel better because she is not see if you can stand up well it's not very easy yet but I'll be all right good boy we got to get you out of here Pronto before one of the gang comes up to have a look at you all right how do we get out out of the window same as I came in but come on now quiet okay whatever you say Mr. Carter climb out the window under the roof easy now easy that's the boy gee it's dark out here can't see anything hardly just follow me there's a post in the corner of the porch we can slide down I came up it careful now there it is here we are okay I'll come right behind you you go ahead Mr. Carter not Mr. Carter Harold just call me Nick Nick am I gonna have something to tell the fellas when I get back home all right gee that was easy wasn't it all right son sure let's get going away from here all right my friend scubby in the sheriff whatever you were there on the edge of the brush hey that's you Nick yes cubby and I have the boy to suffer and catfish mr. Carter how in heaven the same do you get him out of there I get caught it was easy Nick's a good detective I bet he can do anything thanks for the plug Harold now here's my idea are the three of them still in the living room where they were a few minutes ago yeah I just took a look and they're still there what's your idea Carter this is it they think Harold is still tied up nice and snug in a static room now they should happen to hear him out here in front of the house they've probably come rushing out to see what's up wouldn't they sure I don't want any shooting if I can help it somebody might get hurt so you and I will stand one on each side of the front door scubby while the sheriff goes round to the back door ready to come up from behind them and Harold will stand out here in front of the house and shout good and loud they'll come out to see what's what and we'll poke our guns in their backs no shooting no trouble all nice and simple gee that's well what'll I yell Nick oh whatever comes into your head anything at all okay sure yeah sounds nice and simple if it works well here goes your rear guard come on scummy and get your guns ready okay and Harold if anything goes wrong you run for the woods they'll never find you out there at a back night like this okay Nick when do I yell count five slowly that'll give scubby and me time to get into position beside the door okay one two three four five rent rule is a mounted yippie wow get your hands up and fast don't try reaching for your guns we've got you surrounded Nick Carter how did you just keep those hands in the air Vincent all right scubby get the guns okay Nick only one on Ben and two on our friend Jack find your scale trying to skip out the back way so I'll brought her along she blows this outfit I'll see she does she was the one to watch me while the men went out for the money well looks like we got everything going it certainly does share everything but the ransom money which must be here in the house somewhere Nick can I hold a gun I'm one of them quite sure son yeah take Jack's gun and keep it pointed right at him all the time hey Carter don't have that gun he don't know nothing about guns it might go off and somebody to get her quite right Vincent but would it interest you to know that I wouldn't care if it did as far as I'm concerned kidnappers are pretty filthy things the lowest of the low Mr Carter how can I ever repay you for what you've done for me and my boy I'm very happy that we were able to get the boy back for you Mrs. Ascot and the money too please tell me how much I owe you Mr. Carter I want to send you a check at one for a big one you owe me nothing Mrs. Ascot but Mr. Carter you really want to repay me I suggest that you put at least an extra ten thousand dollars into war bonds in this fourth war-lone drive and give the bonds through the associated boys clubs of the city I can think of no better way to spend money right now buying the bonds helps the boys who are fighting for us today and giving the bonds to the boys clubs helps the boys of tomorrow it's a wonderful combination this has been another of the strange adventures of Nick Carter master detective which are brought to you regularly at the same time by W. O. R. Mutual what can you tell us about next week's story Nick well all I'm going to tell you about it is this there's such a weird and unusual case that for the only time in my life I was almost compelled to believe that vampires really do exist I call it death after dark or the mystery of the vampire killing so long so long see you next week in the strange adventure you have just heard Nick Carter was impersonated by Lon Clark Patsy by Helen Chote scubby by John Kane original music was played by Lou White the entire production was written and directed by Jack McGregor next week at the same time listen to another curious experience of Nick Carter entitled death after dark or Nick Carter and the mystery of the vampire killings this story is a copyrighted feature of Street and Smith Publications Incorporated the return of Nick Carter is broadcast in the studios of W. O. R. and is broadcast over most of these stations every week this is mutual


Hello there, today I'm here for a short review on a book that I was given an arc copy of. This is called The Quest for the Golden Plunger. And it was actually written by Jackson Dicker, who was one of the minds behind Campfire. And I was not paid for this review, but he did just offer me an advance copy, so now that that's out of the way, let's go. This is the introduction song. It's not very good, but it's not too long. So if the title didn't tip you off, then this book is a comedy. You know, it's a pretty simple story about a bunch of teen boys who are friends and they go off to a summer camp, and they take part in a contest, actually a variety of contests, all to win this prize, which is just called The Golden Plunger. And it's exactly what it sounds like.  It'll be like one of the last things they get to do together as friends. You know how this sort of thing works, and then shenanigans ensue. And when I say shenanigans, I mean like regular kid stuff shenanigans, you know? Like they play pranks on each other, sometimes it means spirited pranks, but they're still funny.  There's no magic, there's no aliens or evil vampires or anything. The plot is pretty laid back, I should say, and, well, dare I say, it's not that important to the book at all, because whether the heroes win The Golden Plunger or not is really not that important. I'm just along for the ride, you know? I'm enjoying their interactions, I'm enjoying the jokes and the comedy that's in here. I, I'm just having fun with that. And on occasion, on occasion the book does try to have more serious moments and it's not that those were bad, it's just that they never grabbed me that much and I kind of just wanted things to go back to being funny. Like, you know, kids talk about sometimes heavy stuff and I don't think that something has to be pure comedy or pure drama in the slightest. It's just that in this instance I didn't care that much about the drama because I was just here for the laughs. Now thing about comedies is that they're hard to review because if it's a good comedy then you're just sitting there going, yeah, this was funny and this other thing was funny too and I enjoyed that. That was, that made me laugh. Whereas if it's a bad comedy, you're sitting there going, that wasn't funny. That wasn't funny. That wasn't funny either. Like, there's only so many different ways you can say that. So in the interest of fairness, here's a couple of excerpts to give you an idea of what this book's humor is like. When they're first introduced to The Golden Plunger, it's described like this. The Golden Plunger sparkles in the sunlight, it's verge and surface having never touched a toilet bowl. Looking at it always makes me feel poetic. The Plunger holds some kind of special power to invoke something primal inside me, inside many of us. The Plunger was created for one purpose, to fuel a testosterone-driven contest for simple-minded boys every summer. There's no reward for winning it. No cash, no hoes, no violent video games. The winning troop gets bragging rights and their picture taken, but bragging rights over every other group of guys in camp is enough to turn ranger against ranger, mother against child, and perhaps even Christ himself against humanity. Tis a beautiful thing. And at another point, this happens. Alright people, I'm gonna give you some fast facts. Uncle Ruckus counts them on his fingers.  Second, eye contact with the ladies is a tricky thing to master. If you use too much, you're creepy. If you use too little, you're shifty. But never make eye contact with another guy while you're peeing at a urinal. And beyond that, there's just stuff like... there's someone called the Waffle Stomper, which is a legend at camp, and people talk about it in hushed tones as though something really bad happened years ago when in reality it's just someone pooped in the shower and stuffed it down the drain. Like, things like that, you know? It's really childish, but occasionally it gets a little more adult as well. And I'm up to minds on that, because on one hand, the story as a whole feels mostly geared towards kids, you know? I feel like I read a bunch of stuff similar to this when I was, like, 10 years old. And so the more mature stuff did take me out of that. But at the same time, I think back to, like, movies and stuff from the 80s and how kids acted in those, like in stuff like The Goonies or The Monster Squad. And I think, yeah, kids kind of are like that, you know? We were kind of little assholes when we were that age. And they do act more adults, even if they don't do it around older people. So I'm up to minds on this on one hand.  So I guess it's not a huge problem. And really, that's that's all I can say here. I think that this it's it's not really for kids. I wouldn't give it to them. But for teenagers and young adults and older and stuff, I think this is a good reminder of what it was like to be young at the risk of sounding cliched. I think it was that. I think there were some really good laughs in there. I had a good time reading it. It's not that long. So if the quest for the Golden Plunger sounds like something that you might have fun with, then go ahead and check it out. It was fun. And thanks again to Jackson for the arc. Thunk to patron names you see here and thank also to $10 and up. Oppo Savalainen, Olivia Ray and Brother Santotys, Carolina Clay, Christopher Quinten, Mbis, Great Gebo, Joel, Carcat Kitsune, Liza Rudecova, Lord Tiebreaker, Madison Lewis Bennett, microphone, Sad Martigan, Samuel Nevin, Tobacco Crow, Tom Beanie and Vevictus. Without you guys, this would not be possible. And if you want to get your name on here and you want to participate in stuff like polls to determine what my next video topic will be or early access to my videos, then consider becoming a patron. If not, then maybe become a channel member because that's a thing now. And I'm not good at outros. So goodbye. See you later. Bye.