 So, I guess it's recording, yeah, it's recording. I guess you all can see my terminal, I'm making it a bit bigger, so that's invisible, I'm sorry for the color. So this is just, this is a Red Hat OpenStack deployment OSB 16.2, so it's the train release. This is the undercloud, and we have basically an overcloud with free controllers. And I have two bare metal nodes that I already registered in the overcloud, Ironic. So this is the C244 and C255, and I want to show basically two things that are pretty handy with Redfish. So both of those nodes, this one is the C245, they are configured with Redfish, so I think the only difference to the traditional IPMIS, you have to specify different driver info. And we set the boot interface for those to Redfish Virtual Media. And two things I want to show, so for the C244, I want to show basically the out of, so out of band introspection, so typically when you introspect the node to get like number of cores and CPUs in memory, it will boot an IP image, and then it will do an in band introspection using this Python, Ironic Python agent. So Redfish supports now an out of band introspection, basically it will query the BMC and retrieve those information without needing to boot an image, which is of course much faster than doing the whole pixie boot and starting the IP image. I would show you this with on this node, so basically this is a newly created node, you can see that it doesn't have any information except the standard ones, and I should be able to do a bare method introspect or inspect, I think it's called C244, and basically it should be as fast as you see on this other, you see on my other screen, that kind of, I want to conduct the, basically finished inspecting the node, and if I list the node again, you will see that it should hopefully, these properties, the Redfish, so the introspection, the Redfish introspection driver basically populated, so this was not said before. Only what the Redfish can do is, it can also detect the bare metal ports that this bare metal node has, and so there are some, of course some caveats, so the Redfish cannot do LLDP, so one useful feature I guess is for the invent introspection is that once you boot an IP image, you get LLDP information that you could use, for example, with I think the generics switch driver to plug it to the correct, or to do basically tenant plugging the bare metal node in tenant networks, so this one, this isn't yet supported by a heard from the ironic people that, in theory the Redfish standard could support this, so it depends actually on the BMC, and of course the invent introspection will give you much more information than the, I mean this depends actually on the Redfish implementation of the bare metal node you have, we have a Lenovo node, relatively new Lenovo nodes, and I think they give you kind of the basic information, but I think this with time will get better and better. So this would be the introspection, I think that's pretty handy. The other useful feature I want to show with Redfish, or specifically regarding Redfish is the booting of basically the whole, the whole pixie-less booting, so the C245 is again another node which we configured with Redfish, and in this one, so this is another node, the only difference with this one is that we had to also be created, we pre-created the ports because we need to specify which port is connected to which leaf switch, this is specific for our Cisco SDN, so that the Cisco SDN can properly plug the bare metal node into the provisioning network. So this was, this is the only difference to the C245, but for this one, we will now kind of clean the nodes, and finally this node is in, I think manage, in the variable state, I will move it back to the managed state, and now I will provide it, so typically in a non, so in the typical case, this will basically boot the IPA image, will clean the node, basically erase the disk, and then move it to the available provisioning state, and then the node would be ready for deployment, again using the IPA image. With virtual media, we won't do a, so we won't do a pixie boot, this will mount the IPA image into one of the virtual media slots, and I can show you this in the EMC interface, and just boot it directly without doing any pixie and any TFTP, so if I run this, we should see it now on this side, so this does a neutral plug-in, create the ports, and then you should see that it should, so it will go through the virtual media slots that the node has, and plug it to the first one it can detect, and you can see this in the interface, this is the node that, this is the specific node that we are now cleaning, you can see that this, it creates it, like it will on demand create, on the fly, it will create an ISO image, and it will mount this using HTTPS, you can also mount it from Swift, but the BMCs have to reach the controller, the ironic conductor in order to properly mount this, and then it will just boot the nodes, and now you will see that it won't do any pixie booting on node TFTP, so it will directly boot the IPA image, and then clean the nodes, and move it to the available state, this is the same way if you do the deployment later on, it will be the same process, so again without pixie boot, it will kind of boot the IPA image directly, copy the image that you chose onto the hard disk, and then make, then the node is actually ready, so this will take a bit of time, so probably a couple of minutes, but kind of this is the typical process you probably know from the regular pixie boot, so it will boot the IPA image now, this will take some time, so I think that's basically it, these are kind of the two small features that I really wanted to show, are there any questions?