Oleg, we should be able to automate and include what Gleb suggests. I think it could solve a particular deployment case where we want to set up a separate node to do some monitoring or profiling task. The way we configure cobbler today doesn't include a default vanilla profile. You must configure the node via fuel first before it can be provisioned.
In addition, I believe we could benefit from a minimal profile that installs common libs that will be useful, like all OpenStack client libs and vim. Feel free to elaborate here. On Thu, Jan 16, 2014 at 12:42 PM, Oleg Gelbukh <[email protected]> wrote: > Gleb, > > Doesn't separation of provisioning and deployment solve this problem? > > -Oleg > > > On Thu, Jan 16, 2014 at 12:40 PM, Gleb Galkin <[email protected]> wrote: >> >> Hello people, >> >> I think we need an "Empty Role" in FUEL. >> In case that you need to provision OS and install mcollective without >> syncing the manifests and running puppet agent. >> >> For example I have a project with Swift standalone. And I need to >> provision OS to the bunch of nodes for further manual installation. >> It looks convenient to have an empty role in this situation. >> Please consider it. >> >> >> -- >> Best Regards, >> Gleb Galkin >> OpenStack Deployment Engineer >> >> Mirantis Inc. >> www.mirantis.com >> >> >> -- >> 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 > -- Mailing list: https://launchpad.net/~fuel-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~fuel-dev More help : https://help.launchpad.net/ListHelp
