fuel-dev team mailing list archive
-
fuel-dev team
-
Mailing list archive
-
Message #00258
Re: Deploy OpenStack w/o OS provisioning
Thanks guys,
I will:
- Make sure the teams who are working on PoC's with separated deployment
and provisioning have the links to this feature
- Include them into this thread if there will be some questions or
discussions along the way
- Update my blueprint and/or propose changes to documentation when these
PoC's are completed
---
Regards,
Dmitriy
On Sun, Jan 12, 2014 at 9:27 AM, Mike Scherbakov
<mscherbakov@xxxxxxxxxxxx>wrote:
> Dmitry,
> we've implemented separated provisioning and deployment in 4.0:
> https://blueprints.launchpad.net/fuel/+spec/nailgun-separate-provisioning-and-deployment-handlers
> ,
> so it should be pretty simple now to prepare target node first, as Matt
> says, and then start deployment on it. There is separate API call for it,
> and it is also available from the Fuel CLI:
> http://docs.mirantis.com/fuel/fuel-4.0/user-guide.html#cli-commands-reference
> .
>
>
> On Sun, Jan 12, 2014 at 12:49 PM, Matthew Mosesohn <mmosesohn@xxxxxxxxxxxx
> > 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
>> <dnovakovskiy@xxxxxxxxxxxx> 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 : fuel-dev@xxxxxxxxxxxxxxxxxxx
>> > Unsubscribe : https://launchpad.net/~fuel-dev
>> > More help : https://help.launchpad.net/ListHelp
>> >
>>
>> --
>> Mailing list: https://launchpad.net/~fuel-dev
>> Post to : fuel-dev@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~fuel-dev
>> More help : https://help.launchpad.net/ListHelp
>>
>
>
>
> --
> Mike Scherbakov
> #mihgen
>
References