Open Stack

So... we're really talking about ironic? If so, similar requirements
apply... and I see packages for Liberty on Ubuntu and RHEL/CentOS. As you
can probably tell, I don't have a SUSE environment available. However,
ironic requires more hardware resources than manila... at least another
host for it to provision as a compute node. Looking at the existing
installation guide [1], ironic also requires rather significant
configuration changes to a variety of services plus introduces additional
concepts such as PXE and TFTP. However, the guide appears nicely
comprehensive in terms of providing step-by-step procedures for the type of
audience the installation guide attracts. So, we need to consider the
following items before adding ironic to the primary guide as an optional
service:

1) What additional hardware resources does it require? For example, a third
host with W processor, X disk, Y memory, and Z network interfaces. Fewer
requirements generally lead to more people willing to try it, but you don't
want to significantly impact the experience in terms of performance

2) What changes to the existing hardware resources does it require? For
example, additional memory or network interfaces on the controller node.

3) Can someone add ironic without impacting existing functionality? For
example, the ability to launch VMs on a conventional compute node.

4) Does ironic require configuration changes that must occur during initial
configuration of any other service? For example, someone without immediate
plans to install ironic must configure nova differently if they want to add
ironic later.

5) Can ironic consistently provide resources to update the instructions and
verify them on all distributions prior to each OpenStack release?

Matt

[1] http://docs.openstack.org/developer/ironic/deploy/install-guide.html

On Thu, Dec 17, 2015 at 12:12 PM, Lília Sampaio <liliars at lsd.ufcg.edu.br>
wrote:

> Hi Matt,
>
> Sorry for the late reply. That's a nice thing to try out, thanks for
> proposing it! I sure can start an etherpad with what I find regarding
> *Ironic's* installation packages and such. Regarding Manila, unfortunately
> I can't be of much help. I know the thread is about adding Manila to the
> official Install Guide, but I replied because Ironic is also out of scope
> according to the discussion here, and we def want to do something about it.
> So if you're up to it I can manage to have this etherpad done, just please
> give me some dates to handle this to you before it's too late for Mitaka
> (as we are approaching holiday season and stuff I need to plan ;p).
>
> Thanks,
> Lilia
>
> On 14 December 2015 at 18:44, Matt Kassawara <mkassawara at gmail.com> wrote:
>
>> Lilia,
>>
>> As of Liberty, at least RDO and Ubuntu seem to provide packages for
>> manila. However, I am not sure they work... and we need to determine if OBS
>> (SUSE) also provides packages. If you (or someone else with the project)
>> can create basic instructions in an etherpad (or similar place) that use
>> the installation guide architecture for at least one distribution, I can
>> try to reproduce the installation in my lab environments. If necessary,
>> note any architectural changes such as additional nodes including minimum
>> hardware requirements and configuration. If successful, we can consider
>> moving ahead with adding manila to the installation guide for Mitaka.
>>
>> On Mon, Dec 14, 2015 at 2:00 PM, Lília Sampaio <liliars at lsd.ufcg.edu.br>
>> wrote:
>>
>>> Hi all,
>>>
>>> Just wanted to express Ironic's interest in this. We also would love to
>>> have our install guide in the official docs. I understand the concerns
>>> discussed here, but I do believe that at least a supplementary guide would
>>> be a nice thing to have. Maybe this can even be a starting point on full
>>> inclusion, if we get to find a way that reduces the testing burden on docs
>>> folks.
>>>
>>>
>>>> >>>>> Something I'd like to see implemented with a spec for doc tooling
>>>> is this:
>>>> >>>>> 1. Author install guide articles in your doc/source directory.
>>>> >>>>> 2. Create a common TOC to pull many install guide articles
>>>> together to
>>>> >>>>> build an install guide that goes beyond defcore projects to
>>>> >>>>> docs.openstack.org/ <http://docs.openstack.org/
>>>> ><relname>/<distro>/
>>>> >>>>> 3. Serve multiple users needs by building on existing install
>>>> guide in a
>>>> >>>>> modular way without burdening the center.
>>>>
>>>>
>>> Also, +1 on this. Sounds like an approach that would facilitate things
>>> for both sides. I can't have a take on this alone, ~too many things to do~,
>>> but if anyone is available to have a chat about it, maybe even hack on
>>> something, I'm willing to do so :)
>>>
>>> Thanks!
>>> Lilia
>>>
>>> --
>>> Lília Rodrigues Sampaio
>>> Graduanda em Ciência da Computação - www.ccc.ufcg.edu.br
>>> Membro do Laboratório de Sistemas Distribuídos - www.lsd.ufcg.edu.br
>>> Universidade Federal de Campina Grande - www.ufcg.edu.br
>>> <http://www.lsd.ufcg.edu.br/>
>>> Campina Grande - PB, Brasil
>>>
>>> *"We don't get a chance to do that many things, and every one should be
>>> really excellent. Because this is our life. Life is brief, you know?"*
>>>
>>>
>>> _______________________________________________
>>> OpenStack-docs mailing list
>>> OpenStack-docs at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>>>
>>>
>>
>
>
> --
> Lília Rodrigues Sampaio
> Graduanda em Ciência da Computação - www.ccc.ufcg.edu.br
> Membro do Laboratório de Sistemas Distribuídos - www.lsd.ufcg.edu.br
> Universidade Federal de Campina Grande - www.ufcg.edu.br
> <http://www.lsd.ufcg.edu.br/>
> Campina Grande - PB, Brasil
>
> *"We don't get a chance to do that many things, and every one should be
> really excellent. Because this is our life. Life is brief, you know?"*
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20151217/b1aed31f/attachment-0001.html>