---------- Forwarded message ---------- From: Andrey Grebennikov <[email protected]> Date: Mon, Jan 13, 2014 at 11:54 PM Subject: Fwd: [Fuel-dev] Deploy OpenStack w/o OS provisioning To: Dmitriy Novakovskiy <[email protected]>
---------- Forwarded message ---------- From: Matthew Mosesohn <[email protected]> Date: Sun, Jan 12, 2014 at 10:49 PM Subject: Re: [Fuel-dev] Deploy OpenStack w/o OS provisioning To: Andrey Grebennikov <[email protected]> Sorry. Maybe the rest of the team has an explanation for that. We have a few feature requests related to this topic specifically. On Jan 12, 2014 10:47 PM, "Andrey Grebennikov" <[email protected]> wrote: > Hi Matt, > > Could you tell me how exactly bootstrap node appears in the nailgun? All > what we could imagine at the moment for adding the node with OS existed to > Fuel env is to reboot it into bootstrap mode, add it into the env, then > reboot it again into normal mode, install all agents manually and improve > the database with pointing "provisioned" to the nodes. Is there better way > for doing the same? Bcos when I tried to reboot one node with OS existed > into bootstrap, I found that it cleared hdd somewhy (maybe smtng was wrong). > Thanks in advance > > > On Sun, Jan 12, 2014 at 12:49 PM, Matthew Mosesohn <[email protected] > > wrote: > >> I don't see why doing this on CentOS or RHEL will be any issue. You >> would still have to register the nodes to the Fuel Master like we do >> in bootstrap. I just think the only obstacle would be installing the >> reporting agent on Ubuntu and setting up the apt repo. >> >> On Sun, Jan 12, 2014 at 12:41 PM, Dmitriy Novakovskiy >> <[email protected]> wrote: >> > Hi guys, >> > >> > Recently, lots of clients started asking me about using Fuel to deploy >> > OpenStack on hosts w/o doing PXE boot and OS provisioning. I've >> outlined my >> > thoughts on this in a blueprint: >> > >> https://blueprints.launchpad.net/fuel/+spec/fuel-deploy-without-os-provisioning >> > >> > Now I'm interested in your thoughts on this, do you think a feature like >> > that would be useful? Or maybe it's doable with existing functionality >> > somehow? >> > I know the team who did a PoC for it with fuel-3.0.1, and another one >> will >> > happen for fuel-4.0 soon, so maybe it makes sense to integrate this work >> > with main project upstream >> > >> > Looking forward to have this discussion with Community >> > >> > --- >> > Regards, >> > Dmitriy >> > >> > -- >> > Mailing list: https://launchpad.net/~fuel-dev >> > Post to : [email protected] >> > Unsubscribe : https://launchpad.net/~fuel-dev >> > More help : https://help.launchpad.net/ListHelp >> > >> >> -- >> Mailing list: https://launchpad.net/~fuel-dev >> Post to : [email protected] >> Unsubscribe : https://launchpad.net/~fuel-dev >> More help : https://help.launchpad.net/ListHelp >> > > > > -- > Andrey Grebennikov > Deployment Engineer > Mirantis Inc, Saratov > -- Andrey Grebennikov Deployment Engineer Mirantis Inc, Saratov -- Andrey Grebennikov Deployment Engineer Mirantis Inc, Saratov
-- Mailing list: https://launchpad.net/~fuel-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~fuel-dev More help : https://help.launchpad.net/ListHelp
