We'll begin here in a chapter 1, reading verses 1 through 3. I'll give to you an introduction, some background to develop this, and we'll move into our study. So Ecclesiastes chapter 1, beginning at verse 1, reading to verse 3, the words of the preacher, the son of David, king in Jerusalem, vanity of vanity, says the preacher. All is vanity. What prophet has a man from all his labor in which he toils under the sun? So we'll begin this series here in the book of Ecclesiastes, and I wanted to teach this particular book because of the timelessness of its message. Also, because it encourages us to discover our highest purpose. We're going to see as we go through Ecclesiastes that everything that disregards God is without purpose, ultimately, it's meaningless. Now that would include all human efforts. All that which is, he would say, is under the sun. The term under the sun, if you take notes, you might want to note this. That phrase under the sun is used 29 times in the book of Ecclesiastes. Another way to describe life without God, Solomon will point out to us, is by using the word vanity. The word vanity is used 37 times to describe a variety of things. Vanity speaks of human labor, wisdom, prestige and pleasure, youthful strength, knowledge. Everything that is done under heaven without God is completely useless, is what he's going to point out, or simply vanity. Now I'll conclude the book in its introduction, because at the end of the book Solomon concludes what is the purpose, what is the purpose of our lives. See, life's purpose, he's going to point out, is found only in a relationship with God. He'll say then in chapter 12, verses 13 and 14, where he writes, Let us hear the conclusion of the whole matter. Fear God, and keep his commandments. For this, he says, is the whole duty of man. For God will bring every work into judgment, including every secret thing, whether it's good or whether it's evil. So he concludes by telling us the purpose of the entire book. Everything done under the sun is meaningless without God. Now, couple basic things, notice there's no introduction with a name. It doesn't say, this is written by Solomon. But the book is attributed to King Solomon.  Notice verse 1, he calls himself the son of David, king of Jerusalem. In verse 16, he speaks of himself as the wisest man of chapter 1. That reminds us of 1 Kings chapter 4, verses 29 and 30, where it says, that God gave Solomon wisdom and very great insight and a breath of understanding, as measureless as the sand on the seashore. Solomon's wisdom was greater than the wisdom of all the people of the East and greater than all the wisdom of Egypt. And so he's referred to as the wisest man. In chapter 2, he speaks of himself as a builder of great works. He speaks of himself as having numerous servants, possessing great herds, having great wealth. In verse 9 of chapter 2, he speaks of himself as greater than all who had lived in Jerusalem. And so for these reasons, Solomon's considered the author of ecclesiastes. Now, Solomon was son to the King David and Bathsheba. He was the wisest man of his time. For dates, he was born in 990 BC. He was crowned the king in 970 BC, and he died around 930 BC. Now, in 1 Kings, 1 Kings records that God appeared to Solomon. And I want you to think about this for a moment. And he asks, what shall I give you? So often we ask for the wrong things. And rather Solomon's going to point this out as we go through the book. We ask for the wrong things, and when we actually receive those things or achieve those things, we know that they're not satisfying. I want this job. I want this car. I want to go to this school. I want to look like this. I want to have this relationship. I want to have this fame. I want to have these children. Sure you do. So, what would you ask for if you were given an unlimited line of credit? What would you ask for? Many years ago, I've shared this before, someone will remember this, but it's a true illustration, and it comes to mind that whenever I see things like that or we look at a subject like this. I used to give my children devotions when they were small. I gave them devotions all their life until they were in their teen years, and they had places that were going and things that were doing. But they grew up with devotions, and we were going through a devotion. And I asked my children, if you had the ability to ask God for anything, anything at all that you would like, what would you ask for? I started from the oldest to the youngest, and my daughter, Corinne, who was probably eight and nine years old at the time, I would ask, and she gave a spiritual answer in David Aaron, gave a spiritual answer, and so did Joseph. Then I went to my Anna, who was the baby. And I said, baby girl, what would you ask for if you could have anything you wanted? What would you want? She looked at me, she said, gum. And that's kind of, that's kind of how we are. You know, what would you want? Ask as high as the, the highest of the high. Ask for whatever you want. And then we asked for things that really don't last. We asked for the things that don't matter. Well, his answer in 1 Kings chapter three, verse nine was this, give your servant an understanding heart. To judge your people that I may discern between good and evil. For who is able to judge this great people of yours? And so God responded in chapter three of 1 Kings by saying in verses 10 through 13, well it says first that the Lord was pleased that Solomon had asked for this. So God said to him, since you have asked for this and not for long life or wealth for yourself, nor have asked for the death of your enemies, but for discernment and administering justice. I'll do what you have asked. I will give you a wise and discerning heart so that there will never, there will never be anyone like you, nor will there ever be. Moreover, I will give you what you've not asked for, both wealth and honor, so that in your lifetime you will have no equal among kings. You didn't ask for things that you could have very well asked for. And they were small things, but you asked for a great thing. You asked for wisdom to care for my people. And for that I'll give you what you didn't ask for as well as other things. Later on in 1 Kings in chapter four, verse 34, it says that the men of all nations from all the kings of the earth who had heard of his wisdom came to hear the wisdom of Solomon. Well, the time of the writing is estimated to be around 935 BC. It's actually the third of three books that are attributed in Scripture to Solomon. We all know that he wrote the song of Solomon, the word, the book of Proverbs, as well as the book of Ecclesiastes. And there are those commentators who like to point out that he would have written Song of Solomon as a younger man. Because when you read Song of Solomon, you see that it's a love song. It's a song of songs. He wrote Proverbs as he had grown and had aged and had maturity and experience. And then he would have written Ecclesiastes as he's near in the end of his lifetime. And that's how it's normally broken up. He wrote Song of Solomon as a young man, Proverbs, middle age, and Ecclesiastes as an older man. And so he begins in verse one by saying the words of the preacher, the Son of David, the king of Jerusalem. So he identifies himself. Notice this. And again, I'm giving you some basic things so you can use those as we said in the book. You notice he identifies himself as the preacher, the Son of David. He's the king in Jerusalem. He's the preacher, the Son of David. The word preacher is a word that's referring to a public speaker, a speaker in an assembly. That's a title. And it's a title that you'll see repeated once again as part of your introduction various times. It's found here. It's found in verse 12 and chapter 7, verse 27, as well as chapter 12, verses 8 through 10. He's the preacher. And so this preacher says vanity of vanities, all is vanity. So he begins this book as a preacher with a very strong statement. Everything that he's encountered in life is categorized as futility. The word vanity simply means futility. He's saying a life not dedicated to God is aimless, it's empty, and it's unsatisfying. And that's why he begins in verse three by asking a question, what prophet has a man from all his labor in which he toils under the sun? He begins with a question that people relate to. In other words, why do this? What's the use of all of this? Why am I working in the first place? There are a lot of people who don't, but those who work, they can't ask, why am I working in the first place? You see, I can find or try to find meaning in my job, but that will always be unsatisfying. I can work so hard that I become very rich and well known, but at what price? Now, of course, our work can bring a certain level of satisfaction, but at the end of the day, it leaves us empty. It provides, and thank God, it provides for my physical needs, but my job, if I'm driving a car, driving a truck or working in a field or in a factory or whatever, my job won't meet my spiritual needs. Later on in chapter six verse seven, he says it like this, all the labor of a man is for his mouth, and yet the soul is not satisfied. Physical labor, in other words, alone can't produce spiritual abundance, and it certainly doesn't bring us to completeness. Again, life without God is a life lived without meaning. It's simply grasping for straws. In chapter two verse 11, he's going to say, I looked on all the works that my hands had done, and on the labor in which I had toiled. Indeed, all was vanity grasping for the wind. There was no profit under the sun. Jesus said it like this in Mark 8, 36 and 37. He said, what will it profit a man if he gains the whole world and loses his own soul? What will a man give in exchange for his soul? So a life lived without God and hope for eternity has no purpose, and that's why the Bible teaches us that we should labor for the things that last beyond our lifetime. In John 6, 27, Jesus said, don't labor for the food which perishes, but for the food which endures to everlasting life, which the Son of Man will give you, because God the Father has set his seal on him. You see, ultimately, all the work, all that we do, all the saving, everything, ultimately, we leave it all behind, everything. We don't take it with us. You can't take it. That's an old saying, but it's out of Scripture. You can't take it with you. Now I've heard of people who have tried to. I remember hearing of a man who was buried in his Ferrari. It was pointed straight down, but again in chapter 2, and I'm kind of leading into chapter 2 without reading and teaching it yet, but in chapter 2, verse 18, he said this. He said, I hated all my labor in which I had toiled under the sun, because I must leave it to the man who will come after me. In chapter 2, verse 21, there is a man whose labor is with wisdom, knowledge, and skill, yet he must leave his heritage to a man who is not labored for it. This also is vanity and a great evil.  Somebody else uses it. Somebody else owns it. I was speaking to a pastor years ago and he said this to me, and it's interesting because he was speaking in a spiritual sense and I hope it makes sense in that way to you, but he said, you know all the years of ministry and labor, all the tears, all the duress, all that went into my ministry. He said it like that. He said, I'm going to leave in the hands of somebody who will one day pastor this church. He goes, I'm going to leave it in the hands of a man who never cried one day over this church. And it's true. That's absolutely true. When the day I step out of this ministry, I will leave it behind in the hands of a man, preferably will take it further on, but he will not have cried one day for this church. He will not have. He'll leave everything behind. Never forget that. And Solomon is pointing that out. He points that out. He says, I have to leave everything to the one who comes behind me. So the only thing that lasts eternally is what we've done for the Lord. Matthew 6, 19 through 21, Jesus said, do not lay up yourselves treasures on earth where moth and rust destroy, where thieves break in and steal. Lay up for yourselves treasures in heaven where neither moth nor rust destroys, where thieves do not break in and steal for where your treasure is, there your heart will be also. So he's going to point out the answers found in a relationship with God. And we know that it's a relationship with God through Jesus Christ. And that's why we prioritize our lives on a relationship. Now he says in verse 4, one generation passes away, another generation comes, but the earth abides forever. So he compares the permanence of the earth with the impermanence of man. From outward appearances alone, nature endures longer than human flesh. Nature seems to be simply an endless cycle of activity and nature seems to go on forever. In contrast, man is passing through from generation to generation. His lifetime is short compared to the creation that surrounds him. That's the point he's making. In verse 5 he says, the sun also rises, the sun goes down and hastens to the place where it arose. And so the sun he's pointing out is simply an endless repetition. It rises and it sets repeatedly over the years. The wind verse 6 goes toward the south, turns around to the north. The wind also has cycles, continually moving, never resting. Then he points out again, another natural point, verse 7, all the rivers run into the sea if the sea's not full. To the place from which the rivers come, there they return again. So though the river's run into the sea, the sea is never completely full, even if Al Gore says that it is. Seawater evaporates, it forms clouds, brings rain. It's an endless hydraulic cycle. Compared to nature's cycles he's saying man is here today, he's gone tomorrow. His life span is short in comparison to the mountains and the seas, to the rivers and the deserts. Job said it like this, he said in Job 14, 1 and 2, a man who was born of woman is a few days full of troubles. He comes forth like a flower does not continue. So compared to the centuries that some things exist, he's pointing out man's lifetime is brief. In Psalm 90, verse 10, Moses said it like this, he said the days of our lives are 70 years. And if by reason of strength they're 80 years, yet their boast is only labor and sorrow. For it is soon cut off and we fly away. So that's supposed to cause us to pause, to consider making the best use of our time. Here's something that you learn as you grow older, those of you who are gray-haired, silver saints, even if you try to wash away that gray. It should cause us to pause and make the best use of our time. Why is that? Because every moment that we have is a moment that will never again be repeated. My grandson David turned nine. I didn't tell him this because I didn't want to bum him. I and he's very sensitive, so I wouldn't. But I thought and I've done this with so many of my children, grandchildren. They went to bed at the age of eight. But they woke up at the age of nine. And that age of eight will never be repeated. You never return to that age. It passes by. I didn't want to tell him that because he'd cry. So I didn't tell him. I just thought it. And I cried. Some parents are listen up. Some parents are saying, I can hardly wait till they go. I can hardly wait until my children are out of the house. Then we'll be free again. Free at last. Thank God almighty. Free at last. But you know what, as you grow older you look at your children as they grow older and you begin to wish sometimes that they were young again. Just for one day. Just for one moment. I wouldn't want to go through that again. But that moment is true. Those of you without children or maybe even have small children you won't relate to this that well.  How did it move so quickly? We were so little at one time and you can. If you have even a small amount of sentimental heart and I happen to have one everybody knows that.  Where did the little girl where did the young boy go? Where did he go? Sometimes you say I wish he'd go but sometimes you'll think where did he go? And you can look at him and you can regret some things. You can say gosh I wish I'd have known I wish I'd have thought life seems to just creep on and then one day you realize it flew by. Many years ago and I'll say this hopefully without showing much emotion. It's one of the things that hit me when my children were very small and I was given a lady in our fellowship at the time, way back when we were in Ontario High School meeting there on Sundays approached me and gave me a hand written letter. It was not really a letter it was a poem it was called a poem of a grown up son and it's from the perspective of a mother who wrote to her boy and I'm going to read this and preferably I won't get overly weird about it but it touched me then and I have to tell you my kids are smaller than they are now but this is the poem and I'm saying this to parents right now those of us who are parents and for those who are not parents one day perhaps you'll appreciate this that some of us may at this moment but this mother writes my hands were busy through the day I didn't have much time to play the little games you asked me to there we go I didn't have much time for you I'd wash your clothes I'd sew and cook but when you'd bring your picture book and ask me please to share your fun I'd say a little later son I would tuck you in and at night hear your prayers turn out the light and tiptoe softly to the door I wish I'd stayed a minute more life is short the years rush past the little boy grows up so fast no longer is he at your side his precious secrets to confide no picture books are put away they're no longer games to play no good night kiss no prayers to hear yesterday my hands once busy now are still the days are long and hard to fill I wish I could go back and do the little things you asked me to we have to be aware that time moves we have to take every moment that God gives to us and enjoy those moments because once they're past they never return in James 414 it says you do not know what will happen tomorrow what is your life it is even a vapor that appears for a little time and then vanishes away he says in verse 8 all things are full of labor man cannot express it the eye is not satisfied with seeing nor the ear filled with hearing it's not just that man is working all the time nature itself is constantly at labor it is continually restless going through constant change he's saying that nature is in constant activity it is never resting and man for all his activities also constantly in motion and never resting and he will never really have rest outside of resting in the Lord notice how he says in verse 8 we are not satisfied with seeing nor the ear filled with hearing in an entire lifetime we never completely exhaust our ability to see as long as we have vision and to hear as long as we have the ability to do so our eyes and our ears never register full there's always something else to see in every way sight can be used there's always something else to hear and we never stop seeing and we never stop listening no matter what it is that we see no matter what it is that we hear we always desire to see and to hear more and beauty doesn't necessarily fulfill us because we always want to see something different and again in verse 8 at no point do we ever stop desiring and no longer we stop longing for the novel at no point do we desire to see being able to see and hear so he says in verse 9 that which has been is what will be that which is done is what will be done there's nothing new under the sun is there anything of which it may be said see this is new it has already been in ancient times before us man's desires complaints his pursuits are always basically the same and as far as something completely new ultimately we don't create we simply innovate people constantly look for something new and different but there's no such thing that's why again as a parent that's why you can take your child we'll say to the edge of the Grand Canyon stand at the edge of the Grand Canyon and they get bored okay you saw it let's go you're standing there holding hands man look how amazing you got this kid saying I see more than this you know on my iPod who needs this they get bored and that kind of shows what happens styles and music are constantly recycled comes around goes around so there's nothing really that's completely new is the point that he's making he says in verse 11 there's no remembrance of former things nor will there be any remembrance of things that are to come by those who will come after people don't remember their history they don't remember what is taking place they're not aware because history is forgotten it's forgotten in that never ending quest for something new and improved he's saying you know you're here today but you'll be gone tomorrow and nobody's going to remember you nobody will remember your accomplishments and that's a very true that's true of all human beings and that's true of some of the greatest people will say things like Chuck Smith didn't he use a pastor at church somewhere I think I've heard of him as accomplished as he was in the Lord as many great things as God used him to do people forget you can go into the Calvary Chapel today and you won't see any remembrance of him church you pastor for all those years because they come and they go that's what happens Billy Graham at one time was the greatest world evangelist known but you forget about him that's what happens that's the whole point he's making is that it's always a quest it's always different or new and so we're constantly searching for that we forget well in verse 12 he says I the preacher was king over Israel and Jerusalem I set my heart to seek and search out by wisdom concerning all that is done under heaven this burdensome task God has given to the sons of man by which they may be exercised he speaks of that and he says I set my heart the word heart is not speaking of his emotion it speaks of his intellect I applied my mind is what he's saying I determined to search out by wisdom everything that has been done under heaven I searched out the meaning and the purpose of life here on planet earth I wanted to understand why men do what they do socially and politically and even privately I wanted to know these things in verse 13 that this burdensome task has been given to the sons of man now it calls a burdensome task you see in the garden these things were already known but after the fall these things became a task it's something that we actually are trained by we seek out purpose we seek out meaning and then we find that life is difficult it's filled with pressure which helps us to seek the things of the Lord and to grow in him he goes in verse 14 I've seen all the works that are done under the sun and indeed all this vanity grasping for the wind I've looked how how human beings act and what drives them and I see that they're unsatisfied I see that life on earth is painful and I see that it can be so terribly painful when we break a person he's saying human effort and human achievement ultimately has no meaning in verse 14 again I've seen all the works that are done under the sun indeed all this vanity so frustration arises when one attempts to correct the problems of man without God when we encounter problems and we try to solve them without moral directions without considering God's help or looking for him in his word to fix our lives without him when it comes to a place of frustration what do we do when we try to solve the problems that we might have or that we see other people have I wrote a few things down what do we do to solve problems while we we prescribe puberty blockers for children wanting a gender change without notifying parents we legalize drugs we provide clean syringes to junkies we call various sexual partners lovers and we classify homosexuality as a normal way of life we say that AIDS is caused by a virus not drugs or promiscuous sex we refer to abortion as a woman's right to choose we call alcohol or drug dependency a disease we say men can compete with women in sports they can share locker rooms and bathrooms we have drag queen story hours for preschoolers and we provide porn in our schools for our children that's the answers people will provide for problems when they don't have God you're seeing that right now that's what we do so he's saying human wisdom excludes the spiritual and because it excludes the spiritual human wisdom is bankrupt he says in verse 15 what is crooked cannot be made straight and what is lacking cannot be numbered what is crooked can't be said in order what is lacking is something that cannot be provided he's saying by our own efforts somebody said human wisdom cannot make straight that which is crooked human deficiencies cannot be cured through man's vain attempt at solving problems that in their root is spiritual he says in verse 16 I communed with my heart saying look I have attained greatness I've gained more wisdom than all who are before me in Jerusalem my heart has understood great wisdom and knowledge I have great knowledge but I didn't apply wisdom to the knowledge that I have and because of my great knowledge I've become proud of all that I've known in 1 Corinthians 8 when it says it very simply so this is what I've discovered with all this wisdom and understanding if I'm excluding the things that are built on God and faith in him it's just vanity he says in verse 17 I set my heart to know wisdom to know madness and folly I perceived that this is also grasping for the wind I sought to become wise I wanted to understand what is madness and what is foolishness I desired to know why some people are wise and others are crazy fools I studied them I watched them I spoke to them the word study you do study people you may or may not realize that I think you do but perhaps you don't I've said this before but I'll say it very quickly you study when Peter was saying to husbands that we're to dwell with our wives with understanding when we are to observe them he is simply saying that the way that we'll understand our wife is by learning her men can observe and by behavior can begin to kind of understand and as chauvinistic and as politically incorrect as this is I'll say it anyway doesn't matter right I'm an old man you can just say that your wife can say something as blue for 40 years and then one day it turns yellow I thought I knew you you did then this is me now you have to watch them constantly husbands do that by the way ladies you may not hear the multitude of your words but we do watch your behavior and that's how we figure you out that's how we come to understand you I could go into this a lot I won't but that's just the truth I know my girl not simply by what she says I know my girl by what she does and when we were first married I said something like all day long that you love me but to me that's just a word it's just a word I'm gonna know that you love me by how you treat me that's how I'm gonna know you love me and the way that I know you love me and the way you treat me is gonna be demonstrated in love by the respect you have for me because that's how men understand love that's why Paul in Ephesians 5 would say that the wife is a reverence or to respect her husband why is that? because that's how he understand that she loves him and when she doesn't respect him when she puts him down in front of people when she makes him feel stupid that's her way of saying I don't love you that's how men hear and all day long we can argue about the words and what we meant but men don't worry about the words ladies you know that those of you who are married probably know that if you don't I hope you learn it because that's how we that's how we understand things that's how the average man understands it's not what you say it's what you do and when you say you love that's how you act that's how it works right and so we can do all that we want we can apply our knowledge to try and understand different things what human wisdom is I wanted to understand what craziness is I want to know what makes people tick it's like he took a sociology class I want to see this psychology class I want to learn these things that's the point he's really making and then he goes on to say verse 18 in much wisdom is much grief and he who increases knowledge increases sorrow isn't that interesting that's absolutely true actually has the result of sorrow and grief why is that I'll say it quickly because we're going to have communion in a moment it's because the more you gain the more you understand the more you learn the things of life and all the greater sorrow you can have when people don't care about those things that is one of the motivators of every pastor by the way as they grow in the things of the Lord and as they grow in the things of the Lord they want more people to see these things and that's what they try to do they try to teach these things to people and then what happens the people many people don't care all of the prayer all of the study all of the seeking of the Lord in every variety of ways it is done preparation and it's raining and people say it's raining I'll just stay home and he's thinking why didn't I just stay home I could stay home just like you why did I come and you didn't well maybe because you're supposed to be there you're the pastor that kid who got up his mother says it's time to get up got to get to church and he says I'm not going today she says you have to and he says I don't have to give me a reason why I have to go she says honey it's Sunday we go to church and secondly you're the pastor you have to go I made it my aim Solomon says to understand these things and at the end of the time I just discovered that with more knowledge comes greater grief the knowledge that ultimately satisfies and will bring peace is the knowledge of God in Jeremiah 9, 23 and 24 thus saith the Lord let not the wise man glory in his wisdom let not the mighty man glory in his might nor let the rich man glory in his riches but let him who glories glory in this that he understands and knows me that I am the Lord exercising loving kindness judgment and righteousness in the earth for in these I delight saith the Lord where is true wisdom wisdom is found in the knowledge of God he's beginning to lay that foundation the foundation that leads to the conclusion when he says this is summation of all things obey the Lord know him pursue him because in him is true life and so we're going to be looking through the book of Ecclesiastes and we're going to watch a man in pursuit of that which he is revealing to us what it means to have a relationship with God


Deer meat has a thick, heavy silver skin that is usually found on the shank meat or on the front part of the legs.  Here it is found on the loin or back strap. If left on, the silver skin will draw up and won't dissolve when cooked. This will result in tough meat. Some people however still choose to leave it on. Once the silver skin is trimmed from the loin, you can cut it into steaks. There are several ways to do this. It can be left whole or cut into pieces and cooked as a roast. It can also be cut into steaks or butterflied. Here we will use four steaks to be cubed and one to be butterflied. To butterfly a steak, cut part of the way through on the first cut and then cut all the way through on the second cut and open it up. When you cut the meat this way, you have a little bigger steak that you can put on the grill. There's a good chance that your deer processor has not been trimming your meat all these years.  The best case is 25-30% of the live weight of the animal and meat after it is processed.


Genetic engineering comes up a lot in the news. We often hear of scientists altering the DNA sequences of organisms in order to achieve a desired function. This may include the production of new proteins, the expression of certain traits, or the emergence of new functions. For instance, in animals, genetic engineers may alter a muscle development gene to increase muscle growth, thus giving us animals with more meat, which could help alleviate world hunger. But exactly how ethical is this? We're changing the very code that postulates everything the body does, and those of other animals too. How do the individuals affected by this feel? Could genetic engineering be used for more sinister intentions? Let's say that you're thinking of having a child. Imagine going to the hospital and designing that child, picking and choosing the traits that you think are desirable, or better than other traits. How would you feel if you found out that your genetic traits were chosen by your parents, because they were the desirable traits that your parents wanted you to have? With genetic engineering, scenarios like this may become a reality. Many of you may be thinking, isn't this a good thing? With genetic engineering, we can design our children to be perfect, with no genetic defects or other genetic problems. But this could result in many social problems. It could create a culture where only certain traits such as certain hair, skin or eye color are considered good. People who've decided against genetic engineering could face discrimination or bullying because they don't have those desired good traits. Ethical problems arise because somebody is determining how you look based on their own personal opinions. It causes many problems as certain people are setting beauty standards for society as a whole. Animals are often a hot topic when it comes to genetic engineering. The main issue with genetically engineered animals is that we often only focus on the benefits they have for humans. This usually entails more profit from faster growth and development of the animal, more muscle growth and production of more offspring. However, are the welfare of animals taken into account? How are they treated in captivity? Do they get clean living quarters, ample space to roam around in a nutritious diet? Oftentimes, genetically engineered animals live in horrid conditions that are very detrimental to their health. They are jammed into small living areas with very little, if any, space to freely roam around, and their diet is far from nutritious. As if their living conditions are not bad enough, messing around with the genome of animals can lead to unintended side effects such as increased susceptibility to stress, lameness and genetic abnormalities, all of which can cause pain to the individual as well as the mother of that individual. In the past 100 years, half a billion people have died from infectious diseases. Some of these diseases like Ebola are extremely deadly. Once infected, survival rates are slim. Others, such as the ongoing COVID-19 outbreak, spread very easily. Given the lethleness of many of these infections, there is the possibility of turning them into bio weapons. Like in World War II, where the Imperial Japanese army used bio weapons to kill thousands in China. As if biological warfare wasn't crazy enough, with genetic editing, one could construct a pathogen to be more lethal, harder to detect, and easier to spread. Terrorists could engineer a certain bacteria to be resistant to several kinds of antibiotics. Modes of transmission could be expanded, making it easier for a pathogen to spread. People can engineer a virus to target crucial organs in the body, such as the brain or heart, to increase fatalities. The options for death and terror are endless. As genetic engineering becomes more common, people may develop a superiority mindset that humans are entitled to control the evolution of organisms. It could become normalized for nature to be full of just genetically modified organisms, with everything being a creation of or edited by humans. We may come to view ourselves as the advanceers of all life on earth, thus leading to the notion that humans control and problem solve the biosphere. This way of thinking contradicts directly with the views of environmentalists and animal conservationists who want to help wild animals survive in their natural habitats. However, the superiority mindset of humans leads them to want to genetically edit these animals so that they may improve their lives. This means that we are getting in the way of nature and natural selection, which has been happening for billions of years. Despite the fact that people think they are helping, too much meddling in the natural environment may do more harm than good. This includes the creation of powerful invasive species that may wipe out native species not fit to fight them off or compete with them. The widespread destruction of natural genetic diversity helps to give rise to superbugs. In a whereas before, superbugs really only affected a single species. Now, because scientists are inserting genes from one species into dozens of others, it sets the stage for a single powerful bug to be able to wipe out dozens of plant and animal species. Even more than that, genetic engineering can create selective pressures to create stronger pathogens, create new deadly allergens, and could end up threatening the food supplies of billions of people around the globe. To learn more about the harms genetic engineering poses to the food we depend upon, be sure to check out my video after this one. Back to you, science first. Zach is right. At the end of the day, genetic engineering does have a lot of negative aspects to it. However, if done the right way, it could have a lot of benefits. Genetically modified bacteria can be used to produce proteins such as insulin or human growth hormone, which can then be given to people suffering from diabetes and dwarfism respectively. Genetically modified crops that are resistant to pests can be planted in order to increase yield and end food shortages. We can change the nucleotide sequence of certain genes in order to stop the harmful effects of a certain disease. As long as we carefully regulate everything, ensure all people and animals are being treated right, and address specific ethical concerns, genetic engineering will help save lives and many world problems and relieve the pain of those suffering debilitating illnesses. So, if you want to keep exploring the untapped potential of genetic engineering, be sure to stay tuned for more science videos.


Hey, what's going on guys? Rudinal coming back at you with some more Python tutorials. Let's get idle fired up And let's see what we can do here today. I'm gonna create a new script Call this file.python I'm gonna get my shabang line started up. Create a new class as always Define our constructor Passing self keyword Just like you would do with any function inside of a class and now we can test if this is the current script that we are running Create an object of our new class and we are set to go So now back inside of our class back inside of our constructor. Let's define a string So self.string and I'm gonna call mine this string It's not gonna call it this but the value is going to be this string and I'm having new line character here has New line characters actually I'm gonna put a new line character here has new line characters New line again in it Then we'll and we'll call it good with that So the string that you got. I'm sorry the function that you guys can probably guess we're gonna be taking a look at today It's a self.string and then it's called split lines And what it will do is it will turn every single law every single thing up until your new line character Into an element inside of an array. So if we let's do it our output is first of all here. Let's do print Self.string now we can add on new line Some new lines here and we can print on Self.string and then we can run our new function here split lines now if we run this We get this string has new lines new line characters in let's remove that s here This string has new line characters in it and when you look at our function It has this string has new lines characters in it And this is because every single new line has been has been taken out And we have been able to report everything else inside the string inside the element So let's try to recreate this all on our own But before we do that, let's I want to show you guys an interesting Interesting perimeter you can pass to this it has a boolean variable if we check out a control backslash Oh, it looks like we can't see but if we check it out inside the Inside the interactive shell if we do string dot split lines We can do is pass in here and we can use control backslash to see what do we have here keep ends Actually will let you keep the new line character that you've removed So this is a boolean variable you can pass in true and let's do that right here Let's do if we do false. That's a default value. It doesn't keep anything But if we pass in true it will keep these backslash ends that we have here or the escape characters It'll allow you to create a new line. So let's try and recreate this all on our own now Let's say I was to find a new function. I'm gonna call mine split lines I'm gonna have an underscore because I like those and I will pass in self as always We'll pass in the string and then I'm gonna call mine keeping characters because I think that's a good name If especially if we're doing boolean tests and we can set this to false by default We can get started. So now we're gonna need is the length of the string because we're gonna be looping through it with numbers So string length equals length of string And now we're gonna need what denotes a new line. So new line Denoter and this is going to be our string that has an escape sequence backslash n And now we can do the new line length We can set that to be the length of backslash n. I'm sorry. No the new lines in order And now we'll need a new string So we'll be able to keep track of what we're adding what we aren't adding we this can be empty for now And then we're gonna need the array that we're gonna be returning Now we think we can begin to loop through off through our string here. We can do for eye and range string length Let's get our code block started and now we can we can test If the string that we're splitting from the index I up until I plus the new line length If that's equal to a new line character In our case our new line denoter is what our variable is called. What we're gonna do here Is we're going to do array plus equals and then array form of new string and then we can reset new string Back to nothing Now this might look like we don't have anything a new string yet But this is where our L statement is going to come in what we can do here is if we find anything that isn't a new line character What we'll do is we can do new string Plus equals that string character So we can pass an I when we index our string here and now when we break out of our loop what we can do is Add the remaining pieces of the new string into our array because it isn't going to get all of it So what we'll do is we'll add in new string just like we did up in here in our conditional statement And then we can return the array finally So if we return array Then it looks like for now our function is complete So let's go and put ours up at the top here and let's try and run this and see how it looks We can do self dot split lines because that's the name of our function pass in self dot string And then let's give it a go if we run this we get this string has new line characters and all of which are our strings inside of an array and it parsed it correctly it understood everything that we wanted it to But we what we still have to work with this new argument here Whether or not we want to keep characters if we pass this in as true Into the top function we try and pass this in as true into our function The top function will get it right correctly because obviously it's already programmed to do that But ours doesn't have support for it yet So let's try and add it in if we go back into our function We're going to be taking a look at our loop here And we're going to test if the string has the if the string has that new line denoted inside of it What we're going to do is we're going to test whether or not we're keeping characters and Remember since this is evaluated to true if we pass it in it will we can just you have the name of the variable be our condition and What we can do then is new string and we can add the new string denoter on here I'm sorry the new line denoter and then we don't have to worry about anything else if there isn't Because this way we'll have this new line or that backslash and add it on here So let's try this We can run our function now and this does this has the exact same output as the function that we have up at the top here the built-in one So there are a lot of interesting things you can do with this and one of the things that we try to make our function a little Bit more versatile and that you can change what this new line denoter is you can change what will represent a new line You might not ever have to do this But in case you ever want a function that has this sort of this sort of process or this sort of method and Well like you know the action that actually happens when you run this function if you want to be able to customize that and maybe change What represents a new line you can do this by simply changing the variable here or you could just pass it in as an argument Which would be even better So yeah, there are a lot of interesting things you can do with this But it's a short little function here and it's understandable because I think it's it's pretty simple You loop through the string you test whether or not you're keeping things or not if you are you can just add On what you would have lost to begin with and that sort of thing But hey, thank you guys for watching. I hope you enjoyed this. I hope you can understand it It's comprehensible and that sort of thing, but please like the video if you do it if you did enjoy it It'd be cool if you could leave me a comment. Let me know what you think and maybe subscribe I don't know. It's just an idea But if you want to see some more things for me, it's generally a good idea and hey, I will see you in the next tutorial Bye


All right, welcome, everybody. Welcome to our session, Meet the OpenStack Personas. We have an Easter path set up with a lovely bit.ly link, bit.ly slash OpenStack Personas hosting. So we have a link to the presentation included. Also feel free to add in any comments or questions in the Easter path. And while you're doing that, let's get started. Welcome. And welcome to our session. So the session is about the personas around OpenStack. We're talking about the roles model companies around the cloud ecosystem for OpenStack. And the goal of this talk is really to help those that community understand who our users are and to add clarity when we're having conversations about these users around OpenStack. First, oh, let's see. How should I? Oh, yeah, there it is. There's a slap. Yeah, so the presenters. So we have Buster and Pete over there from Intel. We have Jeff, Shamal over there, and myself Stan from IBM. I will also highlight that Pete represents the UX project for OpenStack. He's a project PTL for the UX project. And Shamal represents the OpenStack product working group. And we would also like to dedicate this presentation to Jim West, Jim in the middle of this photo, in the center of this photo, typing out his laptop. At the time was a senior architect at HP. And he definitely helped us in building that understanding towards operator as a subject matter expert. Unfortunately, a couple of weeks after he participated in the Austin persona workshop last year, he passed away. So we wouldn't be able to get this far with the persona without his help. So we would like to dedicate this presentation to him. So yeah, to get started, I would like to talk a little bit about who are personas. A lot of you might have worked with persona before, just so that we are on the same page. Personas are a representation of your key users. It's usually based on either qualitative or quantitative accommodation of both based on this research. And as an example on the right, say dog, that's our persona for the domain operator. You can say it's usually depicted as a specific person, but in no way is a representation of a real person. It's by no means a real person. So by using the personas, it really helps the team to understand and to build on this agreement of who the users are and to help them focus, really focus in building, designing for a specific type of user. And you might wonder, so OK, I'm a developer. I don't really build graphical user interfaces. I work on backhand or I'm an operator. I don't really care about persona as well.  The persona is really relevant to you regarding to any type of interface, like be it graphical user face, be it CLI, be it the APIs. And on a high level, persona helps you to validate the assumption that you have on what the user would do with your product. And it really helps you to determine what features, what you need to build, and what you don't need to build for your product. And at a detail level, persona helps you to determine, say, the specific roles of your product, specific user roles. Helps you determine the arrow messages. Helps you to determine, say, the terminology. So even the default values of your product. And for the decision makers in the audience, the persona research as well as other research really helps you to understand the Cloud adoption strategy. We'll cover the cost or the benefits in doping to Cloud. You also help you to understand how well your company fit into this Cloud ecosystem by comparing your company with other model companies that we have from our research. Before we jump into specific research findings, I would like to highlight that it's really based on solid user research efforts. So we had a set of three workshops. We had a persona validation survey. And during the three workshops, we had a set of around a dozen different user-visual activities to help us in building these findings. So what was it? So we did a round of 20 user interviews and analyzed the data during the first workshop at React Space, we did a cost-shorting activity with three subject matter experts at the second workshop at IBM Design Studio in Austin. So now I would like to hand them my go over to Jeff, who's going to talk about the findings. Okay, so I am going to talk about the artifacts that we've created to help the OpenStack community provide more clarity about who users are, how do they differ, and what are the ecosystems where they work. And so we have not just personas, but we have a concept of model companies and we'll get to that in a few minutes. So this is one of the first things that we created, which was it came out of the second meeting in Austin. And so this is kind of a set of roles that map to a moderately or larger sized cloud environment. And it starts in the middle with what you'd call central IT or in a managed scenario, that would be the managed host. And then moving outward you're getting closer and closer to what you might call end users, but hopefully we'll convince you not to call anybody end users by the end. So the red is showing the personas or the roles where we focused on creating personas. And the gray are ones that we acknowledge are important, but we haven't delved into them yet. So we've all, okay. Okay, so in the middle we have data center ops. And then moving outward we have automation engineers, the service admin, so that would be the owners of different projects in OpenStack. CloudOps, infrastructure architect. So that's kind of the core. And then as you move outward you have domain ops, the developers, what's that? Sure. It's the top one. Okay, the project owner and then developers. Okay, and so, what's that? Yeah, so we included, we uploaded the presentation and we have a link in the user path. So you can definitely like, our reach through like after the presentation. Yeah. So I think a lot of these may be a little hard to see if that one was. So this is showing the different stages of cloud adoption and we map the roles onto them. And so what you can see is that there are some that are present throughout many of the stages and those are probably OpenStack Summit attendees. And then there's a group of them here, which are, you might call the end users, but these are the people who have not much investment in OpenStack. They're developers, they use OpenStack because that's what they have available. And if you're not providing them something that's easy to use and that's solid, then they're gonna go to AWS or someplace else. So they really need things that are focused on getting started and shortening their learning curve to get moving on OpenStack. The other ones, they're gonna delve into all the details and learn everything there is to know about it. And they are important and we want things to be easy for them, but they have a lot more tolerance for pain, that's a good way to put it. Okay, so this is the OpenStack personas. So these are based on the roles that we showed on the previous slides and I guess I can read through them too. So the two at the bottom are who you might call the central IT people or people who would work for a service provider. So there's Arnie, the infrastructure architect and Carlos, the cloud ops. So again, those are hopefully representing a lot of the attendees that are here. And then starting up at the top, there's developers and developers work together so they need somebody to manage the projects. So there's a team lead or a lead developer pay.  And then there's Doug, so Doug is a domain ops. And so you may have that kind of role in an enterprise setting, but you'll definitely have it in a managed provider setting. So that's the person who makes sure their provider is meeting their SLAs, that things are working, that it's running fast enough and so on. And also doing troubleshooting on the customer end. So with each of the personas, we have a description. And of course they have names and job titles too. But we have a description and then we have what does a good day look like in a bad day? And we'll make those available externally and if they're not readable now then please check them out later. Oh, good. Okay. Doug is on the, so the easiest way to imagine is to think about it as a hosted relationship where somebody's providing the infrastructure and Doug works for the customer. So Doug makes sure that the customer is getting what they expect out of the infrastructure provider. He's a part of the customer, but he makes sure the infrastructure's there. So in a large enterprise it would be probably a bit more informal role if they're using domains, but in a service provider type of environment he will definitely be there. Someone has to make sure that the provider's providing. Does that make sense? Yes, he would work on the customer's side. Actually the next slide will show that better. So that's kind of getting at one of the key messages is that roles that IT is complicated and that there's a lot of different types of business relationships. And so you really need to understand the different types of ecosystems. And so what we've provided here, and I don't think this is a complete list, I think maybe telecom is one that we're missing and there's probably other ones too, but the idea is to sort of have these personas of companies. So the idea of personas is pretty standard in the industry, but this idea is fairly cutting-edge. At least I haven't seen a lot of people presenting things like this. So on the left we have a research university. So they have a pretty informal setting. They even installed OpenStack. There's not many rules. They send an email when they need to, when they think they're gonna use a lot of capacity. It's not terribly structured the way things work. They're assuming everybody's gonna be a good partner. On the far right is an enterprise, and so enterprise is gonna have much more formal processes. They're gonna be very concerned about security. They're gonna be very concerned about compliance with various kinds of regulations. They're gonna have much more formal roles in the ecosystem, and then in the middle we have a service provider relationship. And so the service provider relationship is actually backwards in the title, but the MOI would be the customer, and Nuage is the provider, and so they would be providing a service to their customer. Many of the, so they're gonna be very concerned about security and keeping their customers from seeing each other's data, but many of the other things are gonna kind of inherit from their customers. So they comply with HIPAA or something like that. It would depend on who their market is. But then within each of these, they may have different sets of roles, which we haven't created personas for all those. We've kind of just picked one which we think is capturing most of the complexity that you might see in all the other ones too. So we really base the personas on a service provider customer type relationship. As you move to the other ones, you may see some of the roles disappear. So you may see Doug, the domain ops guy, not be a formal role in CNBB. In the research context, he won't be there at all. He'll be probably an administrator and lots of users. So then this is showing an example of drilling down into the model company. So these are still the works in progress, but the idea is to show what's important for these different kinds of companies. So Nuage is a service provider. They're very concerned with security. They don't want their clients to see each other's data. They don't even want most of their clients to know the other ones are there. Most of the time, they need high reliability.  Compliance is gonna kind of be inherited from what their customers need. And then I see a lot of other places that you could fill in here that would be characteristics for these different kinds of customers. So now that we have that, I am going to hand it over to Shamile, who maybe we should have warned. I was listening. Okay, so I work in the product working group within the OBSAC community. And so just an overview of who we are is we're a group of product managers in particular, but technologists, operators, et cetera, that are either building open-stack-powered products or consuming open-stack at scale. And so our goal is to identify user stories in the community from operator feedback, from market feedback like Telco Enterprise and other verticals, and document them so that way we can all collaborate on the priority of them and resources to get them from concept to reality, more or less. And so naturally, as a part of what we do, the user story is a critical artifact that we generate. And in a user story, basically, you have the problem definition, you have what the opportunity or justification is like, why is this problem a problem? And then you have user stories of as a role, I would like to do some capability so that I can achieve some benefit. And so as we document those, when we started the product working group in our user stories, the work being done by the UX team around personas in the community wasn't there yet, so we kind of just randomly chose roles to build. And the result of that was very generic roles. So everything became as a company, as a cloud service provider, or as an open-stack user, or as a app developer, there was not enough context to be able to say, why is this role interested in this capability and the benefits? And so one of the things that we're doing now is we're actually going back into our user stories, and this is actually a real example of the capacity management user story that we have, which was before as an open-stack user, and we're gonna go in and replace that with the domain operator, because the domain operator is really interested in being able to manage the resources this provider is giving him or her. And so we're gonna go back in, and I think with the addition of the personas into the user story, it makes the user story kind of be more compelling, and the context becomes much clearer in that regard. Another way that we're actually using them, and this is actually happening right now, there's other members in the product working group who are presenting a cross-project themes update. And so in the product working group, we also like to define as we're capturing requirements and we're also getting roadmap information for projects of themes. So basically, if a team is working on a capabilities like Cells V2 and NOBA, is that for resiliency benefits, manageability, scalability, interoperability, or modularity? And so Cells, by the way, is for scalability, but as we're doing that, we're now also starting to look at, okay, how can we help prioritize themes and identify themes through roles? And a good example of that is one of the slides that they're showing right now is they have the different personas, and one of the new themes that we're thinking about now is security. And the reason we're thinking about it, because security was a theme that regardless of the persona, it had impact or had some interest to that persona. So we kind of looked at themes and said, okay, out of the themes that we can discuss, which themes would have the broadest impact in the sense of personas? So that was another way we were able to leverage the personas to help make a decision within the community. And so as we move forward, we're collaborating heavily with the UX team and we're gonna start definitely integrating more and more personas into our work going forward. So it's been very helpful to have it. So just to close really quickly, we wanna talk a little bit about the user experience vision for the personas. And one of the things that we really wanted to do in the community is to build a common language or vernacular. You know, I want you to take a look at this quote right here, it really boils down to being, to having OpenStack act more like a single initiative versus a collection of projects. And this came from the user survey a couple of months ago and it was a very, very common theme. People, particularly the operators were pushing back on us because they felt that there's so much isolation between the projects and lack of coordination that it was becoming confusing for them.  Do you call it a project? Well, what's that? Is that you? Okay, could you stand up for me? I need everybody to turn around. Okay, good, good. So what we're trying to do really cross projects the drive consistency and how we talk about our customers within the community. And that goes from the OpenStack Foundation who we're working with, the user, excuse me, the user committee product working group, of course, and the OpenStack UX and specifically the individual projects as well. And, you know, we're doing that. In fact, we're doing that right now. We're having a meeting in a couple of weeks with the foundation to talk a little bit about their roles because as you know in the survey, you self-identify by role. And having that consistency, one of the things it does for us is the qualitative data or quantitative data as well that we generate from the user survey can be, if you will, more easily consumed by the community if we agree on roles. Otherwise it gets really hard to coordinate. So call to action. So a couple of things. I think the first one is particularly important, which is we really need you to start using or integrating these personas into your discussions as projects, right? So what we're trying to do is push the community away from talking about generic users because it's so incredibly vague that a borders on meaninglessness and start talking about, you know, start talking about Doug, start talking about Arnie and what Arnie's looking for and what Doug's looking for. And I think in particular, start talking about Arnie in context of the type of company that he works for. Is it a large enterprise? Is he a service provider? Is it a nonprofit? And that way we'll get a little more specificity and a little bit more focus on our features. The other thing too is we want you to participate. So there's a couple of ways you can do that. One is we are documenting the personas. We're working closely with the documentation project. As you know, then that's gonna go up for review and people can leave feedback. And it would be awesome to have people go in there and leave feedback and talk a little bit about whether they agree or disagree and how they'd like to change it. That would be awesome. I think the other thing too is this is gonna be a work in progress. And I would imagine that we're probably going to have, I wanna say meetings probably twice a year with various people to talk about the personas. How do we wanna update them? How do we wanna make them more useful? And so it'd be great to get participation in that as well. The other thing that I do wanna mention too is important to me is also discussions around the presentation of the personas. There's a lot of ways that you can sort of socialize personas. And what I wanna make sure is that we tailor that socialization or presentation of the personas to the community so it's consumable. So contributors. One of the things that we did wanna emphasize is this wasn't a couple of people in a room deciding that we wanted to have personas in the community. This is actually a collection of 15, 20 people that participated in it. It was cross companies. So we had IBM, Rackspace, HPE, Intel that were involved among other companies. In addition, we had subject matter experts. We had designers. We had operators. We had product managers as well that were all involved in this process. So it's very, very collaborative. So, have any questions? Wow, you're quiet. Anything at all? I'm calling out names. There we go. It always goes, I'm gonna let you go. Make sure you go to the microphone too. And I'm gonna have you guys come up here with me just to make sure that we can all answer questions. There's a URL there too. And you're also more than welcome to reach out to me if you wanna meet me afterwards on the PTL for the OpenSack UX project. So I'll definitely coordinate with you. We had somebody over there. Okay, thank you. As a product manager, I'm very close to personas and thanks for the great job. And I would love to contribute towards the community putting together personas. Question I have is about buyer persona. Did you guys consider it at all so far in the context of OpenStack? Is there a new buyer persona evolving? Sorry. So yeah, one of the things I think that Jeff sort of emphasizes is that when we showed the role ecosystem with the levels of distraction, remember the ellipse. So we chose to focus on four or five and it was just sort of us sitting down trying to identify what we thought was the most important. You know, we may have been wrong, but that's what we wanted to focus on because we had so much time. Now, I think it sounds like a great persona and my recommendation is to reach out to me, Jeff or somebody else and talk a little bit about that. And the next time we have a work session, we'll bring it up. Sure. Yeah, it's a good idea though, it's a great idea. And I think too that they are very related to the different kinds of ecosystems and so they really would probably be, It'd be interesting. It would be something we would add to that. And same things with other kinds of decision makers. And also, I would add the persons that we have, one of the activities we did in the last workshop that I attended was we actually mapped tasks to different persons that we built. And so buyer wasn't a persona that we identified, but the element of decision making or influencing was some of the tasks that were associated with some of the persons. So I think when you look at the documentation that's being built, you'll probably find that there might be elements of what would be a buyer persona spread across the persons from a task perspective. Yeah, I would like to highlight on like second on that. So if you look at like the cloud adoption stages, like the first stage is decide. That's like the buying decision that happens there. The other thing I wanted to add as well, is it's sort of an interesting, it's interesting that you brought it up because now you have me really thinking about it. And that's a pretty compelling persona because it does change significantly across the company type. So it's a great suggestion. So Adam Young with Red Hat and I'm a Keystone core and I want to say that this is absolutely fantastic. This is really getting to the heart of some of the questions I've been asking. I've been working on dynamic policy and on roles as the Keystone as the role-based access control implementation, which I think is gonna be the first consumer of the wisdom that you guys are gathering here. This is exactly the kind of information that we need to feed in. I'd like to point out some of the other efforts that are going on that are gonna be really complimentary. I think are really gonna be able to take what you're doing here and make it practical. One which is, and I'll be talking on this tomorrow on the advances in roles and role-based access control in Keystone, specifically the domain specific roles which are supposed to be a tool for a domain admin to give their own names. So once you have personas there, you can say this is the set of personas that apply to my domain or my deployment here. But the way that you're framing the discussion and the thing that I really like, especially that last thing I just heard about tasks, is I've often thought of this as access and obviously that's not the entirety of what roles are used for, but you identify a person, what they need to be able to do as their top level assigned, call it their role assignment or their job assignment, a middle tier which is the workflows and those are going to be reused across multiple personas, across multiple jobs and then at the finest grade level what APIs are actually able to call and to be able to take what you're using there, you're defining there and drive through a diagram and analysis for a given deployment or multiple deployments. You're giving us a really good language I think to talk about this stuff and so we'll try to consume this and use this as the way to drive what we're doing with dynamic policy and with access control. So I just wanna say thank you and I'll tie in with you guys afterwards. Yeah, that's actually a couple of things actually that I wanted to address. I think one is we are having, we were planning actually to have a meeting with some of the people that are doing the common policy roles in a couple of weeks and so it's gonna be a meeting with you folks, the foundation's gonna be part of that so they can adjust their survey and it's gonna be us as well. So I'm excited to do that. The other thing that's pretty interesting goes towards tasks is about nine months ago the foundation actually sent out a survey and it identified like a huge list of tasks and had people select them based on their specific role and it would be really interesting to do a cluster analysis on that to see how those roles sort of grouped because I think that's some serious quantitative data that we could use for sure. So you had a question or did anybody else wanna follow up? Okay, next question. So I was wondering whether you have differentiated between the size of the customer in the sense that whether the customer is a customer like Sun or Yahoo or PayPal, eBay or the customer is a enterprise customer with a capacity of maybe five to 10 racks or something like that. Have you differentiated because depending upon the size of the customer we may not have all the people that you have highlighted. Yeah, so I think, so the idea really is that those formal roles emerge more as companies get bigger and you're totally right and it's sort of an art of balancing having too many different choices and being able to capture the right level of variability between all those different roles. So we definitely think about it and we have to restrain ourselves from creating a lot more of the different kinds of model companies and ecosystems. I think we need some work to figure out what works but we're definitely conscious of that. I'd like to add on like so from not the person's perspective from the enterprise working group perspective we also work on publishing materials that can help people that are new to OpenStack learn what the capabilities are how to move from evaluation to deployment. But one of the questions we had in that exactly was is company size a factor? But we didn't include it because we got into an internal debate about when you say company size is it the number of employees? Is it the scale of the cloud? Is it the percentage of revenue being allocated to R&D and cloud budget? Like what is defining size? The budget or the people or the scale? So the other question I would like to get answerable I don't even know that you can answer yet is are there roles in the organizations that need to be able to do jobs that they can't do because of the structure of OpenStack? That Joe, he's that middle tier that domain operator that you have there. There's things that he's not able to do because in order to do what he has to have admin and the IT and the people who manage the physical resources are not comfortable assigning him that or they have to give him that and in doing so they're identifying that they are violating compliance or they're making something much more powerful available to somebody who only needs a limited thing. Are there places as we go through where the access control obviously I think in terms of that but the abstractions that we have across the board and it may be on the network level or whatever don't support the set of roles or the set of personas that we're identifying that people want to be able to have and that they can't because of gaps in what we're doing. I think we need more research in that area. I would bet Doug would probably be the place where that would be the biggest problem though. Because he's sort of a role that might be new to a lot of the OpenStack community. Have you guys had something like that? It's like an observer, is that right? Somebody who can look, the cap, or a... That's been a big request and being required. Right, yep. So I agree, I think Doug would be the one that probably would hit that. An example of that that I've heard in the past ops summit was there was an operator who needed to be able to audit the size of all the center volumes that they had across all tenants. And they could do it per tenant, but then basically he had to basically run the same command over and over again and aggregate himself because the way the policies were set up he couldn't traverse and get the full. That's actually a policy, at least he could do it. Yeah. It's painful if you do it. Exactly. It's not even able to do it. Yeah, exactly. That's the first thing I wanted to get into. Exactly, so I don't know any specific examples like that, but this was, yeah, exactly. This was painful, but doable, if you will. This is not so much a question as an observation. My name is Derek Kadzo, I also work at Red Hat as a content strategist for the documentation group for OpenStack and a few other products. I have done this kind of work before and dearly departed Nortel for their documentation. And back then when we were still delivering book structures to customers, this sort of stuff was very relevant and especially when you relate it to tasks as opposed to personas, structuring them according to tasks that people would find was useful because as you say, somebody who does maintenance in one company may not be the same person who does it in another company. But to your question about is the size of the company relevant for documentation, we found that it was quite a bit and this may still have a bearing in this environment as well. For large companies like Bell South, who was a customer for us, the expertise of the people doing the sort of low level work and using the documentation was much lower than in a smaller company. So in the documentation, we had to include much more detail in the task procedures for them than we would have had in a smaller company, even down to the point where at the end of a command we had to put and press enter. That's how detailed they wanted it. So for a larger company, that may be one factor that is relevant. And you did use organization size like some number of employees. In that as a way to judge small, large? Yes, and it's also a question that we're looking at today to see whether the larger companies are starting to get involved with right now will drive further detail required in the documentational procedures. Awesome, I'll keep an eye on that. Yeah. Thank you. So anybody else? We good? Yeah, I think we're good. So I appreciate your time. It's awesome having you here.


Γεια σας! Είναι Vicky εδώ και σήμερα θα φτιάξω 10 ευκαιρικές κατάστασης με αυτήν την Σάιμουσα Σταμπ ΑΕΜΑΚΑΙΚΑΙΚΑΙΤ Απότε πρώτα, ας δούμε ένα κομμάτι που βλέπεις. Έχει με αυτήν την ευκαιρική κομμάτρα της ευκαιρικής κομμάτρας ένα ευκαιρική κομμάτρα της ευκαιρικής κομμάτρας Εντάξει να ανοίξω τα ευκαιρική κομμάτρα, για να μπορείς να δεις τη διαφορετική σε δυνάλλακες κομμάτρας και σχέδες Είναι also a stumpset with flowers and birthday wishes ένα κομμάτι της ευκαιρικής κομμάτρας και θα ανοίξω να ανοίξω τα ευκαιρική κομμάτρα για να μπορείς να δεις τη διαφορετική κομμάτρα εδώ, λοιπόν Θα φτιάξεις όλες, φαρδίες, γερνόδες, λαμπίκες, μπανάδες και δυνάλλα σκουρακές σκουράς like these ones.   Πολλαίω ένα από τις βασικές κλπές, να βρεις ένα λίγο εμβελυσμένο και θα ανοίξω αυτό τίποτα από τη καρδιά μου για να χρησιμοποιούμε κάποιες τέμπες στον απόσοπο. Αυτό θα βρεις ένα λίγο τρίπων. Και η μία πρώτα καρδιά είναι γκρασία. Πύκ και σύμφουρα. Παρακολουθούμε να κάνουμε την δευτικοί εύκολες. Για αυτή την εξέλρα θα χρησιμοποιήσω μια μεξα Sure-V, από τα δυο μπατοτοκές. Γιατί στο τίποτα θα θα πω αυτο ένα μυαλό εξέντικο αναλυτερικό, που πηγαίνει, να δευτερικά παιδιά στην κυρ spoken.  Στον τρόπο μου ονομάζα μία φορά δυο χρωτές και λίγο μεγάλη τραγούδη Οπότε, σε ειχθώ, αντιμετωπιστήσαμε τα πιο κύτλωτος της κύτλου διότι χρησιμοποιήσαμε πολλές παραδοσές. Τώρα είχα φέρει, χρησιμοποιήσαμε τα κέντρα για να κάτω το κέντρο. Όχι και μεταφέροντας τάτσα, θα σηγωθώ να βγω μια μυκηρη λευκό στρίγγυο. Και να βγω να βγω ότι η μυκηρη λευκό στίγγυο δεν θα μεταφέρει. Θα σε βγω να χρειαζω δυο νοτσές. γιατί έχω χρησιμοποιήσει μου τονπιπί και να μείνω τονστήριοOpen. Αλλά δεν μπορώ να δούμε them really, γιατί θα χρησιμοποιήσω χρησιμοποιή είναι και να θέλω να χρησιμοποιήσω το μυαλό εποτάλλητο να χρησιμοποιήσω τα μυαλό εστικαλή μάνα και το μείνω να συμφωνίσω την σκέφτη και το σκώφω μπτωσί. Θα χρησιμοποιήσω τα γρήγομα μου για να χωρίζω τα ατήριδο. Και αυτό θα έτειται με τον ευρώ. Βαθάνουμε στο κινθόμιο για αυτό. Για αυτή την άκρη θα χρησιμοποιήσω αυτό το πατρίγωση, και με το πατρύγωσης μου θα κοπω όλα τα όλα τα ρίχνια. Για αυτό το πατρύγωση θα χρησιμοποιήσω μόνο 4 από τα ρίχνια, αλλά βλέπεις που έχω πολλές σχέσεις να εξεφαίσω το συγκλίψο. Μεταρρύγω τα αδύναμοί μετά, να δείξω ένα λίγο της γρήσης μου. Και θα τους κεφαίω με ένα νερολότυπο στην κεφαίωση. Αυτό θα χρησιμοποιήσω ένα λίγο της γρήσης που αγαπηθούμε. Έτσι, εγώ είμαι μπροστά, δεν έχω κοιμήθει κάτι, αλλά νομίζω ότι χρειάζω πολύ καλύτερα και είναι πολύ σκέφτερος και τελειάζονται. Είμαι also going to use the stickers and stick some of those words in some of the polaroids to embellish them and actually I have used my scissors to cut out a fishtail on some of them. And you can see that when I am creating 10 different cards out of one card kit I am trying to keep everything simple because this way I will not end up not having many supplies for the last cards. And I am going to show you the leftovers, you will see that I will be having many many leftovers. Now to finish off the card I am just using some glossy accents on some of the cards elements such as the heart, the camera lens. I think I will be adding some on the flowers as well as on the white polka dots. I am going to leave this card at the side to dry and I will move on to the next card. You will see photos of the finished cards at the end of the video. And here is another pattern paper that you can cut out many rectangles out of and I am going to show you how I will be using one of them. So I am going to stick the sticker with the typewriter just next to the saying and that says thinking of you.   I am going to embellish it a little bit more with some more stickers like this pink heart and the flowers as well as one of those circles that says love. Also I want to stick that flower sticker with foam tape at the back and make it a little bit dimensional. So I don't know if you could see that but I have used my powder tool to add a little bit of powder at the back and remove that stickiness. So now I am sticking it down with foam tape. I am going to stick one more sticker at the top and now I am going to create my holder with my crop-a-dile. I am also going to add a gold eyelet, security with my crop-a-dile and my tag is pretty much finished. I am just going to thread some string. I get asked a lot how much time it takes me to create those 10 cards. Well, I don't do them in one take, that's for sure. I finished those in three evenings and I believe you can tell since I am changing outfits and you can probably see that I have different sleeves from card to card. So anyway, I have cut out this panel using one of the patent papers. I am going to stick it at the top of the white cardstock and I also made sure that my yellow panel was slightly smaller than my card base. I always like to have that frame around because I think they make your cards look more professional and more finished. So all I have to do now is to stick the tag on top by using foam tape. So let's move on to the next card. Now this card is super easy. I am going to use my scissors and cut out this speech balloon. So I am just going to follow the line.  I usually go ahead and use my scissors directly to cut out the border but I will show you a tip because I get a lot of questions on how to leave a nice border that is pretty much the same width all around. Just use your pencil and then follow along with your scissors. Now I did that just because I wanted to stick it on this very busy pattern paper and I wanted to make sure that this is going to pop. I believe that the combination of this pattern paper on top of a red cardstock is really, really sweet. I have cut out just a panel and I have sticked that on top of my card base in an angle just to give it a little bit more of an interest. Since I am keeping this card very, very simple I am going to stick the speech balloon on the very top corner of my card and I am going to stick that with foam squares at the back. The speech balloon says be happy, be bold, be bright, be you and I think that the combination of this beautiful pattern paper with a bold card base is just perfect. I am going to add something at the bottom and I see that on these videos I go back again and again on those dies the tag, the scalloped edges and the rectangles and I think that those dies are really versatile and I think they are worth the investment since you can use them again and again in any style of cards. So I have created this white scalloped edge which I am sticking it down at the very bottom of my pattern paper to give it just a little bit of interest. My card I am using again my glossy accents over that speech balloon which is going to make it look as a premade embellishment once it is dry. So let's move on to the next card. For this card I am going to use those square stickers. My card base is going to be the pink one and I have already cut out a panel out of white card stock. So I am going to pick three different square stickers and I am staying more to the pale blues and pinks. So I am going to stick those stickers directly on top of my white panel by using foam squares to add a little bit of dimension and that is why I am removing again the stickiness from the back by using my powder tool. I am just applying a little bit of powder there. This is the tool that I usually use for my embossing but it's great for removing the stickiness out of any sticker that you have. So now I can add my foam squares and stick them down. I am going to create a row, stick them one on top of the other on one side of my panel. If you are not confident without eyeballing them you can always use a ruler just to make sure that they are nice and straight. And again I am keeping my card simple. I am going just to stamp the sentiment. For the sentiment I am going to use the clear stamp set from the kit and I will stamp the saying that says birthday wishes. I am using black ink and stamp it at the bottom of my card. Now all that's left to do is to stick that panel on top of my pink cardstock. I am using some tape adhesive and my card is finished. So let's move on to the next card. I have cut out a strip of paper from one of those patent papers that is full of small little images and I am going to stick it as a border on one side of my card base. I am going to cut out the excess paper with my scissors. And here is how you make the most out of your stickers. I am just going to use the black border which you would normally throw away as a thin strip of black paper on top of my card. And I think that this thin black strip of paper gives more definition to my border and helps them pop even more against that red. For my sentiment I am going to use another sticker that says hello and my card is pretty much finished. I am just going to add a star and now let's move on to card number 8. For this card I am going to do some embossing and I am going to stamp the flowers along with the leaves directly at my card base. I am using VersaMarking so you cannot probably see too much of how it looks at the moment but I am going to add some clear embossing powder on top and I heat set it with my tool. This is going to end up with a nice tone on tone look on my card base and at the same time it's going to give some shine on my background.  The sentiment says love as much as you breathe love as much as you live. I am going to stick it on top of a white panel and that is going to help it pop even more and now all that's left to do is to stick that directly on my card base and you can really use the exact same design with the rest of the rectangles that you get out of those pattern papers. So now let's move on to the next card. For this card I will be using those two Polaroid pieces. These are leftovers from a card I have created previously. Again, I need some dimension so I am using some foam tape at the back. I am going to stick them on top of white cardstock that I have cut out and that is slightly smaller than a card base. All my cards by the way are standard cards that's four and a quarter by five and a half. And the idea here is to create a cluster at the center of this panel. I am going to double up on foam tape on one side just to make sure that everything is nicely leveled and now I am going to use some stickers to embellish everything all around. So I am going to stick the camera three little hearts that come in the sticker set as well as a round sticker that says love. Also I am going to stick some of those stars and I am trying to tackle them behind those Polaroids and for the sentiment I am going with a bigger sticker that says EXO EXO. I am using tape adhesive at the back and I am going to stick this panel on my blue card base. Again notice how my panel is slightly smaller than my card base so I have that nice border all around. To finish off my card I am using some clear Wink of Stella glitter pen on the hearts as well as on the camera lens. And let's move on to the last card.  I have used just a little bit of pale blue acrylic paint diluted with water and with a very thin brush I am adding some splashes just a few here and there. So once I am happy with that I am going to make sure that this is nice and dry with my heat gun and again I am going to use a piece of pattern paper and this comes out of those pattern papers that were included in the kit that they were full of small rectangles. I am also going to embellish that by using one of those plastic paper clips that were included in the kit and I have used some tape adhesive at the back to add a little bit of dimension. This is where I decided to add those little sticker flowers inside the basket of the bike but you will see that later on I decided to remove them because I thought it made the card too busy. I am also going to add this cluster of flowers this is one of the stickers as well. Now this is where I have removed the flowers and I think I like that better. I used tape adhesive at the back and stick that on top of my last blue card base. For the sentiment I am using one of those black stickers that says it's a beautiful life and to finish it off I am just going to tie a bow around that plastic paper clip and now let's take a quick look on all the cards as well as the leftovers. So now leftovers. I have many many more plastic paper clips Of course I have the stamp set as well as the embossing powder the black embossing powder that I never used you can see that I had plenty of stickers left. I have 3 whole 6x6 papers that I haven't used and many more rectangles that I can use to replicate some of the designs. Some big panels and some squares such as those Polaroids and many more sentiments in squares and rectangles. Which means that with all those leftovers you can make even more cards with this kit. And these were the cards for today I hope you had fun and got inspired and if you did don't forget to leave me a comment as well as give me a thumbs up on my youtube channel. Here are some close up photos of all the cards that I have created today. And if you are not one of my subscribers consider hitting the subscribe button because this is the way to tell me that you love my videos and you want to see more. And if you need more inspiration here are 2 more videos for you. Thank you all for watching.