Hi QiLiang, We will likely contribute the scripts at some point, but right now, they are pretty specific to our environment, i.e. servers, addressing, etc. We're working to abstract this and make them more modular, which will make it easier to add the other scenarios, etc, Once we have that playing nice it will be easier to share / contribute.
Cheers, Lincoln On Tue, Jul 18, 2017 at 2:51 AM, liangqi (D) <liang...@huawei.com> wrote: > Hi Lincoln, > > Got it, thanks. So the users can get a pod with user specific opnfv > scenario installed, or a pod with user specific OS-only installed. > > BTW, I'm curious about how do the labaas's pods managed. Do the scripts > opensourced, can I get the code? > > Regards, > QiLiang > ------------------------------ > *From:* Lincoln Lavoie [lylav...@iol.unh.edu] > *Sent:* Tuesday, July 18, 2017 0:42 > *To:* liangqi (D) > *Cc:* Luke Hinds; opnfv-tech-discuss > *Subject:* Re: [opnfv-tech-discuss] Lab as a Service - Installer Support > > Hi QiLiang, > > Some answer inline below, at least for how we've set stuff up so far. > > > > On Mon, Jul 17, 2017 at 11:56 AM, liangqi (D) <liang...@huawei.com> wrote: > >> I can give some support from compass side. Also I'm recently working on >> opnfv installers' quickstart wrapper scripts( >> https://gerrit.opnfv.org/gerrit/#/c/36711/ ). Hope the scipts could ease >> developers/users better use the labaas resources. >> >> >> >> Here are three questions, after checked the wiki page: >> >> - How do the Laas resources allocated? Allocated as vpods pool and >> BM(1+3+2) pods pool? >> > We have systems setup to allow two virtual pods per hardware node to run > in the lab. This is based on RAM/Disk/etc. Access to a pod resource would > be scheduled through the Pharos dashboard system. > > >> - How do the vpods' and BM jumpserver's operating systems installed, >> manually pre installed by lab admin or auto installed trigger by jenkins >> when the pod is allocated? >> > We've built up some scripts and support to allow the virtual pod to be > "spun up" by the request through the dashboard. This isn't actually hooked > up to Jenkins, if I understand it correctly, it's its own thing. We are > trying to keep the system admin out of the request path. This does depend > on the installer supporting a virtual deployment and a "hands off" > deployment approach. > > This will likely start with basic requests, i.e. one 1 or 2 scenarios > supported and go out from there. We're also planning a developer version, > where the actual OPNFV deployment doesn't occur, so the developer can login > and pull their own artifacts onto the system to deploy from, etc. Because > the systems are self contained and "throw away." We'll be able to give > root access onto the environment for each Pod User. At the end of the > Pod's lifetime, it just gets deleted. > > >> - Do laas pods share the same jenkins master with other opnfv pods or the >> laas will host a jenkins master to manage all the laas resources? >> > No, see above. > > >> >> >> Regards, >> QiLiang >> ------------------------------ >> *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [ >> opnfv-tech-discuss-boun...@lists.opnfv.org] on behalf of Luke Hinds [ >> lhi...@redhat.com] >> *Sent:* Monday, July 17, 2017 22:39 >> *To:* opnfv-tech-discuss >> *Subject:* [opnfv-tech-discuss] Lab as a Service - Installer Support >> >> Dear Installer Projects, >> >> I have an action from the infra-wg to gauge which installers can support >> LaaS. >> >> Please peruse the following wiki link for more details on the effort. >> >> https://wiki.opnfv.org/display/INF/Lab+as+a+Service >> >> Recommend you go over the work flow in detail, and consider if you have >> interfaces that can accept the requests and process deployment status. >> >> Any question, please ask over this email or attend the infra-wg group. >> >> Many Thanks, >> >> Luke >> >> -- >> Luke Hinds | NFV Partner Engineering | Office of Technology | Red Hat >> e: lhi...@redhat.com | irc: lhinds @freenode | m: +44 77 45 63 98 84 | >> t: +44 12 52 36 2483 >> >> _______________________________________________ >> opnfv-tech-discuss mailing list >> opnfv-tech-discuss@lists.opnfv.org >> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss >> >> > > > -- > ************************************************************ > ******************* > *Lincoln Lavoie* > Senior Engineer, Broadband Technologies > > <https://www.iol.unh.edu> > www.iol.unh.edu > 21 Madbury Rd., Ste. 100, Durham, NH 03824 > Mobile: +1-603-674-2755 > lylav...@iol.unh.edu > <http://www.facebook.com/UNHIOL#> <https://twitter.com/#!/UNH_IOL> > <http://www.linkedin.com/company/unh-interoperability-lab> > > Ars sine scientia nihil est! -- Art without science is nothing. > Scientia sine ars est vacua! -- Science without art is empty. > ************************************************************ > ******************* > -- ******************************************************************************* *Lincoln Lavoie* Senior Engineer, Broadband Technologies <https://www.iol.unh.edu> www.iol.unh.edu 21 Madbury Rd., Ste. 100, Durham, NH 03824 Mobile: +1-603-674-2755 lylav...@iol.unh.edu <http://www.facebook.com/UNHIOL#> <https://twitter.com/#!/UNH_IOL> <http://www.linkedin.com/company/unh-interoperability-lab> Ars sine scientia nihil est! -- Art without science is nothing. Scientia sine ars est vacua! -- Science without art is empty. *******************************************************************************
_______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
