openstack team mailing list archive

[Marton Kiss <marton.kiss@xxxxxxxxx>]

Hi Kevin,

I like suggest you to start with devstack first. It is the shortest
way if you like to deploy a working openstack on a single machine
(takes just a few minutes). Anyway if you like to see a different
deployment scenario, it requires a proper planning and more time. In
the last two days I've deployed Essex and Diablo using devstack, both
of them works well.

Essex on Ubuntu 12.04 Precise
requires a server deployment with openssh enabled

as root user:
adduser stack
apt-get install sudo -y
echo "stack ALL=(ALL) NOPASSWD: ALL" >> /etc/sudoers

after that, login as stack user:

sudo apt-get install git -y
git clone git://github.com/cloudbuilders/devstack.git
cd devstack

create localrc file:
LIBVIRT_TYPE=qemu
FLOATING_RANGE=192.168.122.224/28
FIXED_RANGE=10.0.0.0/24
FIXED_NETWORK_SIZE=256
FLAT_INTERFACE=eth0

You can comment out LIBVIRT_TYPE, I used this flag, because it was
deployed inside a kvm server.

I needed to modify the files/apts/glance file, and comment out the
python-argparse line, because it was provided by python himself, and
deployment stopped due an dependency issue.

python-eventlet
python-routes
python-greenlet
#python-argparse
python-sqlalchemy
python-wsgiref
python-pastedeploy
python-xattr
python-iso8601

After that, just start stack.sh:
FORCE=yes ./stack.sh

It will deploy the entire stack after a few minutes, and display
access accounts and urls for dashboard and api.

Diablo is the same process as above, with the following differences:
- deployed on oneiric server
- don't need to hack files/apt/glance
- requires an extra package if you like to use vncproxy, so don't
forget to apt-get install python-numpy.

My experience that success depends on proper OS environment and
openstack component configuration.

Regards,
  Márton Kiss, CTO
  Xemeti

2012/3/13 Justin Shepherd <jshepher@xxxxxxxxxxxxx>:
> Kevin.. would like to help you get this working.. and I understand the
> confusion as I recently got all or our chef recipes in shape for RC1 and had
> to work through the Keystone Light migration.
>
> 1. Where are you in the setup process?
>
> 2. Do you think you have a working Kesytone?
>
> 3. What services are you having issues with keystone integration (Nova,
> Glance, Swift)
>
> Thanks,
> Shep
>
> Kevin.. wanted to reach out to you off list for a sec.. I would be more than
> happy to help you get through this.. as I recently got all or our chef
> recipes in shape for RC1 and had to work through the Keystone Light
> migration.
>
> Couple of questions..
>
> 1. Where are you in the install process..
> - Do you think you have a working keystone?
> - Are you running into issues with Glance working with keystone?
>
> Let me know how i can hep
> On Mar 13, 2012, at 8:00 AM, Kevin Jackson wrote:
>
> Thanks a lot for the points Andi (and the links), but not to stray away from
> my original post: I don't want complexity at this stage - I want a single
> server that works.  I haven't even got that.
> I had a multi node set up working (to some degree of butchery) of an early
> Essex-1 release using Orchestra, PXE booting and doing appropriate
> post-configuration, if a little bit of a hack.  We're a modest size digital
> hosting environment - introducing alternative PXE booting and config
> management systems ontop of something that is already causing us pain isn't
> something we're looking at right now.  Given a fairly slick PXE boot
> environment already across multiple datacentres of the rest of our kit means
> we can move to using this for OpenStack.  That's an aside - I mentioned
> prod, but not confuse a way of rolling this out in our datacentres.
>
> The issues stem from a basic install.  I'd love to chat about bare-metal
> provisioning issues as it means I've got OpenStack running.  I haven't.
>  Yet.
> I've raised a bug just now (https://bugs.launchpad.net/glance/+bug/953989)
> which might shed light on my issues as it's possible its not a bug, but
> process/config issue.  This would be great to hear as it means there's an
> easy fix.
> Given that keystone underpins the rest of the environment means that my
> frustrations could be solved.
>
> Cheers,
>
> Kev
>
> On 13 March 2012 12:42, andi abes <andi.abes@xxxxxxxxx> wrote:
>>
>>
>> I first need to get to a world where a manual install works.
>> > I was getting desperate in having a demonstration available to those
>> > that
>> > pay my wages - the best candidate I had here were Kiall's managedit
>> > repo.
>> >  Great work (really), but it wouldn't have been anything to be
>> > considered
>> > for production for obvious reasons.
>
> --
> Kevin Jackson
> @itarchitectkev
> _______________________________________________
> 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
>