Open Stack

On Mon, Mar 24, 2014 at 9:38 AM, Phil Hopkins <phil.hopkins at rackspace.com>wrote:

>
>
> Sent from my iPhone
>
> On Mar 24, 2014, at 8:12 AM, "Anne Gentle" <anne at openstack.org> wrote:
>
>
>
>
> On Sat, Mar 22, 2014 at 7:20 PM, Phil Hopkins <phil.hopkins at rackspace.com>wrote:
>
>> If one cannot set up networking one doesn't need to be installing
>> Openstack, My $0.02
>>
>>
>  Phil, I can't have us thinking this way yet... everyone takes a
> meandering path to OpenStack and may not have all the (pick your distro)
> networking knowledge we'd like. We have to be advocates for our users no
> matter where they started their journey. I won't ever be persuaded by this
> line of thinking.
>
>
>  Anne i was sending from My phone and was being cryptic. Sorry if my
> intent was misunderstood. I would never mean that we shouldn't help folks
> that are new to OpenStack. However we need to gently point the to resources
> whereby they can learn rather than repeating those resources in our docs.
>
>  We all were new to this at one point and it is important to remember
> that. So that said we help them on the path to learning about OpenStack.
>


HURRAY! Thanks for sending, I was pretty sure you felt this way and
appreciate the longer explanation. :)

I agree with laser focus on the OpenStack education, that's a great point.
There's a stack of tech you'd have to learn (database, message queues,
networking) and let's give the best pointers we can.

Anne



>
>  Phil
>
>
>   That said, Matt's arguments are sound for maintenance purposes. We
> heavily rely on MySQL documentation for all but the very basics. Can we
> draw a similar line here and refer to the distro's documentation for
> networking?
>
>  Anne
>
>
>
>
>> Phil
>> Sent from my iPhone
>>
>> > On Mar 22, 2014, at 5:45 PM, "Matt Kassawara" <mkassawara at gmail.com>
>> wrote:
>> >
>> > While updating the networking section of the basic OS configuration
>> chapter in the installation guide, I found my step-by-step instructions
>> quickly making the source file rather large and complex with plenty of "os"
>> conditionals. Do we really need to provide step-by-step instructions for
>> basic OS configuration including network interfaces, name resolution, etc?
>> I would much rather include more generic steps and let users reference
>> their distribution's documentation for specific instructions.
>> >
>> > For example:
>> >
>> > Use this...
>> >
>> > Compute node
>> >
>> > 1) Configure the network interfaces:
>> >   a) Management (eth0)
>> >
>> >   IP address: 10.0.0.31
>> >   Netmask: 255.255.255.0
>> >   Gateway: 10.0.0.1
>> >
>> >   b) External (eth1) ...
>> >
>> > Instead of this...
>> >
>> > Compute node
>> >
>> > 1) Configure the management network interface:
>> >   a) Edit the /etc/sysconfig/network-scripts/ifcfg-eth0 file to include
>> the following:
>> >
>> > ONBOOT="yes"
>> > NM_CONTROLLED="no"
>> > BOOTPROTO="static"
>> > IPADDR="10.0.0.31"
>> > NETMASK="255.255.255.0"
>> > BROADCAST="10.0.0.255"
>> > GATEWAY="10.0.0.1"
>> >
>> > 2) Configure the external network interface:
>> >   b) Edit the /etc/sysconfig/network-scripts/ifcfg-eth1 file ...
>>  > _______________________________________________
>> > Openstack-docs mailing list
>> > Openstack-docs at lists.openstack.org
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>>
>> _______________________________________________
>> Openstack-docs mailing list
>> Openstack-docs at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140324/d87d9084/attachment.html>