openstack team mailing list archive

[Eugene Kirpichov <ekirpichov@xxxxxxxxx>]

Hi Anne,

On Wed, Aug 15, 2012 at 2:55 PM, Anne Gentle <anne@xxxxxxxxxxxxx> wrote:
> Hi Eugene -
> But I thought "everyone" was on the openstack list! :) Thanks for following up.
>
> On Wed, Aug 15, 2012 at 4:35 PM, Eugene Kirpichov <ekirpichov@xxxxxxxxx> wrote:
>> Hi Anne,
>>
>> I accidentally found this email of yours while looking for links to my post.
>> I'd probably have found it earlier if you cc'd me on
>> ekirpichov@xxxxxxxxx or ekirpichev@xxxxxxxxxxxx [yes, that's two
>> different spellings...] :)
>>
>> I support the idea that this should be somehow integrated in the docs,
>> but I'm not sure where exactly in the docs is a good place for
>> information of this style. Would it help if I just linked to the posts
>> from some wiki page or from the docs?
>
> I do like to put relevant blog posts on the wiki at
> http://wiki.openstack.org/BloggersTips, so you can certainly add to
> that page. If it's really missing information in the docs, though, it
> should be added to the docs. I know that's a tough judgement call but
> we all have to encourage that call.

Thanks. I added a link to the post to this wiki page and I'll now
spend some time picking what to integrate into the docs.

>
> Or would it only help if I (or
>> somebody) actually merged the relevant parts of the posts into
>> official documentation?
>
> I wouldn't say "only help" but I prefer that you merge the relevant
> parts of the posts. It's tougher for a doc team member to merge only
> parts in without violating the license of the content - you as content
> owner can certainly choose which parts to move into the official
> documentation though.
>
> Thanks for asking for clarifications - these are certainly gray areas
> that I'd like to shine light upon.
> Anne
>
>> On Thu, Aug 9, 2012 at 8:07 AM, Anne Gentle <anne@xxxxxxxxxxxxx> wrote:
>>> All, sorry for top posting, but this is a fine example of why we
>>> really need bloggers to help with the documentation. These fragmented
>>> instructions are difficult to rely on - we need maintainable,
>>> process-oriented treatment of content.
>>>
>>> Mirantis peeps, you have added in your blog entries to the docs in the
>>> past, let's find ways to continually do that and maintain going
>>> forward.
>>>
>>> I'm not so interested in more install guides, but definitely
>>> interested in more configuration guides. So Kord, while I like the
>>> idea (and execution!) of the StackGeek 10-minute guide, it's not one
>>> to bring into the official docs. But we would definitely welcome your
>>> reviews of incoming updates to the docs!
>>>
>>> Thanks Simon for bringing your difficulties to the list - we
>>> continually work on improving the docs. What you learn now could help
>>> hundreds if not thousands of others, so I'd love for you to improve
>>> the official docs with your findings.
>>> Thanks,
>>> Anne
>>>
>>> On Thu, Aug 9, 2012 at 4:42 AM, Simon Walter <simon@xxxxxxxxxx> wrote:
>>>>
>>>> On 08/09/2012 12:59 PM, Scott Moser wrote:
>>>>>
>>>>> On Aug 8, 2012, at 8:20 PM, "Simon Walter" <simon@xxxxxxxxxx> wrote:
>>>>>
>>>>>>
>>>>>> On 08/09/2012 06:45 AM, Jay Pipes
>>>>>> I guess I'll have to build a VM from scratch, as I was relying on the ssh
>>>>>> key to be able to ssh into the VM, which apparently is supplied by the
>>>>>> meta-data service.
>>>>>>
>>>>> use cirros.
>>>>> load an image, ssh on with 'cirros' user. pass is 'cubswin:)'
>>>>
>>>>
>>>> Thank you. That was good advice.
>>>>
>>>> Somehow I was not able to connect via ssh. I managed to get novnc working
>>>> and logged into the VM. I can't find anything about connecting via serial or
>>>> the like as you can with Xen. I need to read more about KVM I guess.
>>>>
>>>> Anyway, I think my networking setup is stuffed. I thought the "10 minutes"
>>>> install would be the quickest way to get and running. Now I find myself
>>>> pouring over documentation trying to understand how best to setup
>>>> FlatDHCPManager with two network interfaces. I understand many things have
>>>> changed. So I don't want to go reading something out of date. I found these
>>>> blog posts which explained a lot:
>>>> http://www.mirantis.com/blog/openstack-networking-flatmanager-and-flatdhcpmanager/#comments
>>>> http://www.mirantis.com/blog/openstack-networking-single-host-flatdhcpmanager/
>>>> But am I reading the wrong thing? I like the way Stackgeek had it set up:
>>>> http://stackgeek.com/guides/gettingstarted.html
>>>>
>>>> But I think they are missing details or it's out dated. For example, with
>>>> their setup the vnc console in horizon does not work because nova-vncproxy
>>>> is installed rather than novnc.
>>>>
>>>> I'm pretty sure I can figure the networking out if I have the right
>>>> documentation in the first place. Is there a clear instructions for this
>>>> anywhere? Or would someone mind walking me through it again. So far I've
>>>> followed the stackgeek setup above, but the networking is obviously stuffed.
>>>>
>>>> Must I have the flat_interface in promiscuous mode?
>>>> Or does it actually need an IP address?
>>>> Why are my VMs picking up an IP address from the public_interface DHCP
>>>> server and not from the flat_network_bridge?
>>>>
>>>> Too many questions to ask. So I thought I should just ask: what is missing
>>>> or incorrect from Stackgeeks 10 minute scripts?
>>>>
>>>> Many thanks for any advice, tips, docs, etc.
>>>>
>>>>
>>>> Cheers,
>>>>
>>>> Simon
>>>>
>>>>
>>>> --
>>>> simonsmicrophone.com
>>>>
>>>> _______________________________________________
>>>> Mailing list: https://launchpad.net/~openstack
>>>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>>>> Unsubscribe : https://launchpad.net/~openstack
>>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~openstack
>>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>>
>> --
>> Eugene Kirpichov
>> http://www.linkedin.com/in/eugenekirpichov



-- 
Eugene Kirpichov
http://www.linkedin.com/in/eugenekirpichov