foreign all right so i have two minutes after the servicenow team are we good to go ahead and get started okay yeah i think we're good um so good mor good morning everybody good afternoon if it's afternoon for you um welcome my name is aaron bennett i'm a tech alliances manager here at servicenow and i have the pleasure to introduce to you the uh the puppet team our friends and tech partners at puppet are going to be covering the capabilities they've built for the servicenow platform and these are available in the now store if you're interested in these after after the session uh we'll be fielding questions throughout the chat today or throughout the webinar today in chat and we'll um milad and molly will try to answer them in the flow of the presentation but we may we may hold some of them to the end depending on complexity please go ahead and ask questions as soon as you have them uh we'll try to get to all of them in the time allotted um at the end of the of the event we're going to have a replay of the recording available so you can if you did sign up for this and you missed it um welcome to you as well so now i go ahead and introduce our presenters for today molly earl's a principal product manager puppet she's worked in in close you know and closely with the integration team and obviously many other areas um she doesn't just focus on integrations but she's had a lot of experience in building what public has to offer so far and then uh milan guerishi is a senior software engineer on the integrations engineering team at puppet he's a certified servicenow admin developer and he's been vital to these integrations um that that you'll see in the store if you go and search for puppet there so i'll pass it over to emulate and molly um take it away guys awesome thank you aaron yep so as mentioned i'm i um i am have previously worked very closely with the integrations team continue to do so as it relates to servicenow and then milad will be giving our demo later in the presentation as he is one of our excellent development engineers on the integration side so looking at the why behind the servicenow and puppet integration we wanted to see how we could remove the barrier that previously existed between servicenow and puppet we saw servicenow is owning the process oriented space and puppet owning the action-oriented space and found that by removing the silo between or removing the barrier between the two tools forcing them to be siloed tools we could then use both in coordination with each other to capitalize both on the action-oriented space and the process oriented space to really make a one-stop shop as far as devops go so the first of our integrations is the service graph connector so what we first i'm sorry the the puppet spoke and so what we wanted to really focus on here was pr was allowing for out of the box catalog items to be used by those that actually install our puppet spoke so by doing this we wanted to remediate manual tasks that we often see companies as having to dedicate a good amount of resources and time too and instead we wanted to build those out of the box and then as many on the call know these can then be triggered via the larger flows we wanted to allow that that puppet action engine again to be part of the servicenow process oriented space so that we could really capitalize on those time savings so as you can see here we have many different out of the box items including managing a service rebooting a machine and this list is something that we continue to iterate on based on our customer feedback and where we can continue to adapt to where more users are using the larger flows and where we can position puppet in order to help you that action engine so the puppet spoke is available now on the servicenow store as aaron had mentioned so we have some more information there as far as documentation etc new compatibilities as well if you do if you do find it on the store and then we also have the service graph connector so this will be that cmdb mapping from puppet into the service now cmdb and where we really see this being beneficial is giving insight into everything that puppet is able to read in from your managed assets into the cmdb we also see this very being very beneficial when partnered with the puppet spoke so that when you're taking action and using those catalog items or those larger workflows you're then able to do so on top of that enriched database truly making those actions worthwhile but then also having a sense of auditability and then knowledge of exactly what data you're running those actions on top of so the service graph connector is also live on the store and again more more documentation and iterations as far as the compatibility goes all of that can be found in the servicenow store so with that i will pass over to malad for our demo thank you molly um i guess i will start with puppet spoke since uh we started the puppet spoke in the in the presentation uh just a quick uh review on some of the puppet technology behind the spoke uh puppet has a concept of tasks and plans uh task is basically a job that puppet server can run on one or more managed servers and this can be anything like installing a patch restarting a service rebooting a machine and so on and plans are bundles of tasks that can be chained together um as an analogy for that would be a task is similar to a servicenow flow designer action and and plan is more similar to flow itself or or software two really nice nice things about this integration is one all the communication between servicenow and puppet are through one authentication token uh because puppet already has secure communication channels so we don't have to worry about doing extra work to make this secure all you need is one token and you are all set uh puppet uh the other thing is uh or there's a there's a website called puppetforge which is a great resource for you uh which is similar to to servicenow store uh there's a lot of available modules there that you can go um and use there there are so many uh built-in tasks and plans in those modules so you don't have to build stuff from the scratch you can just go ahead and take a look at what you need over there and then uh just start using it and it's it's gonna be better tested and uh it's like many people are using it so it's gonna be a really great resource for you guys uh to use uh any question there okay uh so let's let's head uh to service now i'm going to share my screen okay um so after after you install puppet spoke in service now you can you can uh type public spoke in the filter navigator and and as you can see uh the application is available here for you uh the the puppet uh service catalog is when you click there it will take you to the service portal and we we created a category called puppet and you as you can see there are already uh some catalog items uh being built here for you so the purpose of this was to give you some example uh to see what what can be done in in here with puppetspoke and we already built these ones because we thought this is going to be useful for for customers to use and and you can definitely create additional ones if you need to uh the only thing you need to do is to make sure uh you you add all the parameters listed in in puppet for each task or plan you want to create here um let's so let's let's actually see how it works uh let's open one of them which is this one is the managed package so when you open one of these catalog items uh you can see um this form uh the puppet server is where you select uh what puppet enterprise you're using for this action and as you can see we support multiple pe so you can have multiple public enterprises set up for your system and and then use and connect it to servicenow so let's say let's say i'm actually doing it on this one and this is the puppet environment you need to set it is defaulted to production for for targets uh this is really useful uh we gave you uh three options here so the note group is like is a concept in puppet that you can actually group your notes um in your puppet enterprise uh such as like uh you can group the group servers together like if if you want uh to to make it easier if you want to run something on on group of servers rather than running one running it on one uh pool notes from cmdb you can if you have the service graph connector and you already imported everything into uh cmdb you can select this and then and then select the server from here to run on and and also we gave you the option to to type the fqdn comma separated here uh so let me just select one machine here you can you can of course select multiple if you want um and then you just uh give give it the name of the package and i'm gonna say just give me the status of this package and after you submit this form a request is getting created of course and then along with that a requested item gets created and as you can see the there's a update coming here it says a job is currently running in puppet enterprise related to this request and this is a link if you click on the job it will take you to the profit enterprise you can you can log in and and you can see the results of that task here in puppet or you can wait here and the results will come back to service now momentarily and as you can see in here when you run something from servicenow to puppet it actually shows in the description that who actually submitted what from servicenow what was the requested number requested item number and um and everything else here and then as you can see when i go back to service now uh i see the results coming back here in in servicenow so this is going to be really useful for many customer because uh when i go back to the back end here let me actually go to um the requested item table okay so this is the request we just created right you can see all the information here and we have uh placed these up these updates into um into the um activities additional comments so you can definitely communicate with the with the with the requester or or you can you can do whatever you want to do in that regard and also you can you can attach this request item to an incident like if there was an incident about a machine that you needed to install a patch on or whatever you can say you can actually run something here uh in servicenow and after the action is done in puppet it comes back to service now and it automatically populate this information in there in the requested item and you can attach it to that incident so it's going to be all in one system um heading back to uh puppet spoke uh so puppet logs is just there to show you like uh the action you've you've that you've done like it just says this was a task this was the result uh the connection was accepted uh the status was finished so if this if it fails or whatever you can see everything all the information about it here um and this node group uh like this category configuration just to show you show you a quick overview if you want to add anything extra here you need to create a record here and and this is what it calls in puppet and this is what it co this is the kala garden service now and that's going to connect these two together and the note group is what i told you uh it shows you um it shows you the uh the the note groups that are that exist in puppet it actually imported once a month but you can manually import it if you if you've recently added something and you want to have it here automatically so um one more thing i wanted to show you here is is the flow uh so we have tried to make this as user friendly and as simple as possible for users so we have created um we have created some generic flows so it anytime you create extra uh additional uh catalog items yeah the the good thing is you don't have to create flow for every single one of these you can just create the form and you can attach it to the existing flow and everything should work like you don't have to do anything else uh so we have one generic flow for task and one for plan and we also created some subfloors for you guys to use along with some useful actions if you want to build something more specific to your organizations everything is like provided here for you any any questions about the sport okay in that case i i can i can show you i can talk about the graph connector um so a little bit of background about uh the graph connector about about puppet before we head to graph director uh puppet is a configuration management tool it helps you manage and automate the configuration of servers you can install puppet in a central server called puppet server then you can add servers you want to manage manage to it and and then you write puppet code to define the desired state of those servers uh puppet code is declarative which means uh you you describe that this desired state and not the steps need to need to get there and papa will take care of that the rest for you uh the puppet code runs every 30 minutes by default and of course you can change that if you if you want uh to make sure the configuration is in sync for all the managed servers uh puppet server collects something called facts which is essentially hardware and software attributes for each system there are different kind of facts there are facts there are generic facts called core facts like serial number f2dn and and so on you will see some of them here in the demo um and also you can write your own custom facts if you have something specific you want to track uh in your system you can definitely write a code and write a custom fact to do so um if you're curious about facts you can you can look it up uh uh in in the puppet documentation uh look up puppet core facts and you can see what is available there for you so any questions about puppets before i show you the graph connector okay it's really quiet here today okay uh so let's let's see how it works in servicenow um so when you type when you type service graph connector here for puppet you can see this application and of course it is available in servicenow store you can download it and and after you download it this setup page is here for you uh to help you set up the authentication token for puppet define the initial set of facts you want to bring into the system and how often the sync is going to run so it is pretty straightforward it's really easy to to use you can just go step by step and and uh and set things up and start using it and of course we use uh we support uh uh multiple uh public enterprise support here like you can you can add multiple connections to the graph connector as well um so the we we have included this fact configuration table which is a really um useful table that uh when you when you click on it and you can see there are a bunch of facts listed here already these are actual the core facts i was talking about as you can see it says this virtual serial number this is how it actually uh listed in puppet and that's how you need to have a hearing service now if you want to bring them over so any fax you want to bring over to servicenow related to your infrastructure you need to you need to the only thing you need to do is to create the new record on this on this table and set the name and make sure it's active and you're good to go and this will bring uh uh and that and the next time the puppet runs the graph connector import runs it will bring in the the the new facts for you um and after after after so as i said you can you can um you can set like uh when you want this import to run uh and you know of course in the import schedules but after it runs it actually populates facts under this facts table as you can see and uh like service graph connector uses etl to do the to do the field mapping and uh and as you can see it is grouped by the configuration items and when i open one of them you can see actually we have a configuration item here we have fact name fact value configuration item and puppet server which means what a puppet enterprise a puppet server this is this data is coming from so you can visually here see what is the what is the puppet server that that manages manages this specific machine let's let's actually open one of these cis to see how it looks in the in the cmdb so a serious graph connector as i said you said use etl to do the mapping and as you can see some um uh some of the uh fields are already mapped here like uh like model id serial number asset and all these and also let's say let's say you have some custom facts that you don't have a field here in in the configuration item to map to you don't have to map them you can just uh like there's a we created a relationship here uh between the puppet fact table and and this and and the cmdb so you can you can just keep him here and you can have access to it from the cmdb so if i'm looking at the linux server a table now and i when i scroll down i can see all the facts coming from puppet related to this machine listed here for me so if i want to do a mapping i can just use etl to do extra mapping for for the new ones i bring in or i can just leave them here and it's going to be visible for you an important thing to mention is that the ingestion speed for the import is about 40 minutes for every uh 50 000 ci so hopefully that's enough for most customers and and i think that's it is there any questions on the graph connector that i will pass it over to molly awesome thanks milan so yes at this point we will open it up to any questions that anybody might have regarding either the spoke or the service graph connector or if you have any questions about puppet and uh and puppets products how these are integrated we'd also encourage you to ask these um so that we can we can get that information recorded for everyone who will watch this later okay great well um i'd like to thank the puppet team for uh their presentation today um we'll obviously uh follow up oh molly do you have some oh right uh molly did you want to say anything about the um additional information that's going to get posted to the webinar post uh presentation yep yeah absolutely um so we have a few different links here and we'll send this out with the webinar as well but we have a few different uh demos that we've walked through we have some solution briefs videos etc so we have a good amount of content here and then if any more information is needed you can obviously reach out to us rob moore is who we're going to work our communications through so rob is very tied in here he works on our alliance's team so if you have any more questions please feel free to reach out to rob moore otherwise our technical contact is on both the spoke and the service graph connector uh pages for for both of those store items so we are happy to help in any other way but i really appreciate everybody's time today going through this webinar i think that is it from our side aaron okay great thank you all for attending um check the chat one more time i don't see anything coming in so ah okay great good um thanks everybody again once again um look for the post recording if you missed this call and uh thanks again to the puppet team for your presentation have a great day thank you thank you everyone you