<div dir="ltr">Hi,<div><ol><li>We can try gofish [1]</li><li>I guess we need to discuss this topic since Redfish/IPMI/iLO usually set up to use out-of-band (OOB) data center network which has limited external access.<br></li><li>Since we are going to use K8s Cluster API + Kustomize + Metal3 and deployment data (i.e. evolved treasuremap or treasuremap 2.0) is stored as directory structure applicable for Kustomize rendering. Therefore all nodes should be described as Machine which is tied to BareMetalHost. AFAIK enduser has to mark particular Machine with specific annotation tag (e.g. ephemeral=true). I'm trying to use this approach in CR [2] (it's in WIP status so far) which adds ephemeral node cloud-init generator to airshipct. This CR assumes that our deployment data has following objects defined<br>kind: Machine<br>apiVersion: <a href="http://cluster.x-k8s.io/v1alpha2">cluster.x-k8s.io/v1alpha2</a><br>metadata:<br> annotations:<br> ephemeral: "true"<br> name: my-control-plane1<br>...<br>spec:<br>...<br>---<br>apiVersion: <a href="http://metal3.io/v1alpha1">metal3.io/v1alpha1</a><br>kind: BareMetalHost<br>metadata:<br> name: cp-host<br>spec:<br>...<br><br></li></ol></div><div><br></div><div><br></div><div>[1] <a href="https://github.com/stmcginnis/gofish">https://github.com/stmcginnis/gofish</a></div><div>[2] <a href="https://review.opendev.org/#/c/679563/">https://review.opendev.org/#/c/679563/</a></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Sep 2, 2019 at 12:40 PM Kanwar Saad <<a href="mailto:kanwar.sbl@gmail.com">kanwar.sbl@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi all,<div><br></div><div>I am planning to start contributing on remotedirect code for airshipctl(or join forces with anyone who is already working). For that, I was investigating Redfish APIs. I have a couple of questions to start with:</div><div><br></div><div>1. There is no good golang client for redfish. What I have investigated is that we need couple of REST API calls for the bootstrap operation. So should we create a small redfish util library in airshipctl itself or should it be a separate project or if anyone has any idea about a good go client for redfish? I have a minimal redfish go client for testing, we can start maturing it if we want to go with that approach.</div><div><br></div><div>2. For setting the CD image in redfish, it requires a HTTP(s) endpoint to download ISO file. After generation of ISO locally where should we put it so that it is visible to redfish server. Do we have any design decision about that? Or do we have a totally different way of pushing the ISO image which I am not aware of?</div><div><br></div><div>3. Redfish server would be managing multiple Systems. You can get a list of Systems it is managing from "redfish/v1/Systems" endpoint. How do we select a system for the ephemeral host? Should it be provided via config or we just randomly select one of the systems from the list? In the latter case, how do we ensure that any selected system should have minimal requirements for the ephemeral host?</div><div><br></div><div>Br,</div><div>Kanwar Saad</div><div>Ericsson Software Technologies</div></div>
_______________________________________________<br>
Airship-discuss mailing list<br>
<a href="mailto:Airship-discuss@lists.airshipit.org" target="_blank">Airship-discuss@lists.airshipit.org</a><br>
<a href="http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss" rel="noreferrer" target="_blank">http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss</a></blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div>Kind regards<div>Dmitry Ukov</div><div>Principal Deployment Engineer</div><div><div>Mirantis, Inc.</div></div><div><br></div></div></div></div>