Open Stack

Folks: I am new to this mailing list.
Why does the user advisory group have to be selected by these other groups?
If this is really going to be run by users, I think word should go out that a user advisory group is being formed and who wants to join.
Also what will the costs to participate in this advisory group.
Then once the group is 'formed', have them decide how they want to govern or pick the chair/co-chair to help facilitate
and work with the other groups.

-----Original Message-----
From: openstack-operators-request at lists.openstack.org [mailto:openstack-operators-request at lists.openstack.org] 
Sent: Monday, March 31, 2014 8:00 AM
To: openstack-operators at lists.openstack.org
Subject: OpenStack-operators Digest, Vol 41, Issue 25

Send OpenStack-operators mailing list submissions to
	openstack-operators at lists.openstack.org

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

or, via email, send a message with subject or body 'help' to
	openstack-operators-request at lists.openstack.org

You can reach the person managing the list at
	openstack-operators-owner at lists.openstack.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of OpenStack-operators digest..."


Today's Topics:

   1. Re: Atlanta Summit - More Ops? ;) (Tom Fifield)
   2. Unable to launch instance after basic	two-node DevStack
      installation (Nico van Gessel)


----------------------------------------------------------------------

Message: 1
Date: Mon, 31 Mar 2014 10:15:39 +0800
From: Tom Fifield <tom at openstack.org>
To: John Dewey <john at dewey.ws>
Cc: openstack-operators at lists.openstack.org
Subject: Re: [Openstack-operators] Atlanta Summit - More Ops? ;)
Message-ID: <5338CFCB.9060603 at openstack.org>
Content-Type: text/plain; charset=UTF-8; format=flowed

On 30/03/14 00:44, John Dewey wrote:
> Would it make sense to have an ops PTL?

So, my reading is we already have such governance established - but 
rather than being an individual, it is a committee - the user committee. 
We'll need to tweak it a bit I guess, but in fact it is already set up 
such that the TC _must_[1] listen to it ... for at least four hours per 
year ;)

Since the number of users majorly outweighs the number of developers in 
a project, we probably do need more than a single individual. Tim, Ryan 
and JC have done very well in this extremely difficult position so far.

However, I think if we can rally around the user committee, get some 
more people in and start doing even more things it might just satisfy 
the need for extra governance we're seeking.

Thoughts? What would you see this group doing?


Regards,


Tom


[1] 4.14 User Committee. The User Committee shall be an advisory 
committee to the Board of Directors and shall be comprised of at least 
three (3) Individual Members, one (1) appointed by the Technical 
Committee, one (1) appointed by the Board of Directors, and one (1) 
appointed by the appointees of the Technical Committee and Board of 
Directors. The User Committee shall organize its meetings and may, on 
approval of the Board of Directors, create elected seats to be filled by 
a vote of the Individual Members. On request of the User Committee, the 
Board of Directors shall invite the User Committee to attend each 
regular quarterly meeting and shall allocate at least one (1) hour 
during the regular quarterly meeting following the annual election to 
hear the report and recommendations of the User Committee. On request of 
the User Committee, the Technical Committee shall invite the User 
Committee to attend a regular meeting and shall allocate at least one 
(1) hour during such meeting up to four times each calendar year to hear 
the report and recommendations of the User Committee.



> John
>
> On Friday, March 28, 2014 at 2:34 AM, Tom Fifield wrote:
>> All,
>>
>> I had a bit of a play around, combining some similar things from the
>> suggestions, and was able to come up with something that I think covers
>> everything that was suggested. If it's way off - no problems, we can go
>> to a vote or similar.
>>
>> Also had a go at selecting moderators for sessions based on our
>> volunteers - feel free to strike yourself out or move around.
>>
>> All of this is up for discussion and change, so read below and head on
>> over to the etherpad, or post a reply email :)
>>
>> https://etherpad.openstack.org/p/ATL-ops-unconference-RFC
>>
>>
>> Monday
>> 0700 - 1115 Registration, Keynotes, Break
>> 1115 - 1155 Ask the devs: Meet the PTLs and TC, How to get the best
>> out of the design summit
>> 1205 - 1245 Reasonable Defaults
>>
>> 1400 - 1440 Upgrades and Deployment Approaches
>> 1450 - 1530 Architecture Show and Tell, Tales and Fails
>> 1540 - 1620 Architecture Show and Tell, Tales and Fails
>>
>> 1730 - 1810 Security (MODERATOR NEEDED)
>>
>> Schedule: Friday
>> 9:00 - 9:40 Enterprise Gaps
>> 9:50 - 10:30 Database
>>
>> 10:50 - 11:30 Issues at Scale
>> 11:40 - 12:20 Monitoring and Logging
>>
>> 1:20 - 2:00 Ansible (MODERATOR NEEDED)
>> 2:10 - 2:50 Chef
>> 3:00 - 3:40 Puppet
>>
>> 4:00 - 4:40 Networking
>> 4:50 - 5:30 Best discovery of the week, Meta Discussion - ops
>> communication and governance
>>
>>
>> Regards,
>>
>>
>> Tom
>>
>> On 27/03/14 11:20, Tom Fifield wrote:
>>> All,
>>>
>>> The idea for this "Operators Summit" has received excellent support, and
>>> we have more than twenty session ideas proposed in the etherpad:
>>> https://etherpad.openstack.org/p/ATL-ops-unconference-RFC
>>>
>>> We've blocked out a room on Monday to host it.
>>>
>>> What we need now is:
>>> 1) Find moderators for the sessions
>>> 2) Select which sessions are going to happen
>>> 3) For the architecture show-and-tell, we probably need to select who
>>> will present in this.
>>>
>>> If you can help with any of this, please do get in touch, or get your
>>> name down on the etherpad. I'll be in contact soon.
>>>
>>>
>>>
>>> Regards,
>>>
>>>
>>> Tom
>>>
>>> On 17/03/14 07:54, Tom Fifield wrote:
>>>> Hi all,
>>>>
>>>> Would you like more time at the summit to talk OpenStack ops? Read on!
>>>>
>>>> Of course, we will have a dedicated Operations track in the conference -
>>>> and it's going to be better than ever this year, with an all-new
>>>> selection group ... all of whom actually run clouds.
>>>>
>>>>
>>>> However, we've never really had many design-summit style
>>>> feedback/sharing sessons for ops. Let's change that.
>>>>
>>>>
>>>> Would you find it useful to have a space to share architectures, best
>>>> practices, and give feedback on the bits of OpenStack that are giving
>>>> you pain? Or perhaps find out how to get more involved in the Open
>>>> Design process? Help us justify locking away a few rooms :)
>>>>
>>>>
>>>> Just to start the discussion, I have written up a straw man proposal/RFC
>>>> of one potential use of the time. It's specifically designed to be
>>>> ripped to shreds - so please do!
>>>>
>>>> The idea is to have something that's more like a design summit feel -
>>>> people sitting in a room discussing things, as opposed to more
>>>> presentations.
>>>>
>>>> https://etherpad.openstack.org/p/ATL-ops-unconference-RFC
>>>>
>>>>
>>>> So, what would you like to see?
>>>>
>>>>
>>>> Regards,
>>>>
>>>>
>>>> Tom
>>>>
>>>> _______________________________________________
>>>> OpenStack-operators mailing list
>>>> OpenStack-operators at lists.openstack.org
>>>> <mailto:OpenStack-operators at lists.openstack.org>
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>>
>>>
>>> _______________________________________________
>>> OpenStack-operators mailing list
>>> OpenStack-operators at lists.openstack.org
>>> <mailto:OpenStack-operators at lists.openstack.org>
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>>
>> _______________________________________________
>> OpenStack-operators mailing list
>> OpenStack-operators at lists.openstack.org
>> <mailto:OpenStack-operators at lists.openstack.org>
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>




------------------------------

Message: 2
Date: Mon, 31 Mar 2014 12:50:38 +0200
From: Nico van Gessel <nico.vangessel at biologie.uni-freiburg.de>
To: openstack-operators at lists.openstack.org
Subject: [Openstack-operators] Unable to launch instance after basic
	two-node DevStack installation
Message-ID: <5339487E.5050805 at biologie.uni-freiburg.de>
Content-Type: text/plain; charset=ISO-8859-1

Hey there,

for three weeks I am struggling to get a basic OpenStack environment going. I learned a lot during my work but am still relatively new to Linux
networking and the cloud architecture. After several luckless attempts to manually set up the machines following the official OpenStack documentation
and some other tutorials I finally landed at using DevStack and still am unable to get things going.

My setup consists of
- one physical controller node ("controller", 10.8.234.100, 4 cores, 16 GB RAM, 1 TB RAID1) and
- one physical compute node ("compute1", 10.8.234.101, 8 cores, 64 GB RAM, 1 TB RAID1)

Both run on fresh Ubuntu 12.04 Server installations and connect to the same network (10.8.234.0/24) on eth0 through a gateway (10.8.234.254), using
aspecific proxy (http://proxy.uni-freiburg.de:8080) and DNS (132.230.201.111).

Using Ubuntu's environment variables I added proxy addresses, the no_proxy and the substitution of "git://" to /etc/profile:

------------------------
export http_proxy=http://proxy.uni-freiburg.de:8080
export https_proxy=http://proxy.uni-freiburg.de:8080
export ftp_proxy=http://proxy.uni-freiburg.de:8080
export no_proxy="localhost,*.local,127.0.0.0/8,192.168.0.0/24,10.8.234.0/24"
git config --global url."https://".insteadOf git://
------------------------

To get a simple nova-network with basic services I configured the devstack/local.conf on both nodes accordingly:

------------------------

[[local|localrc]]
## Controller Host ##
HOST_IP=10.8.234.100
MULTI_HOST=1

## Network nova-network ##
FLAT_INTERFACE=eth0
FIXED_RANGE=192.168.0.0/24
FIXED_NETWORK_SIZE=254
FLOATING_RANGE=10.8.234.128/27

## Leaving Default Services Enabled ##
DISABLED_SERVICES=neutron

## Passwords ##
ADMIN_PASSWORD=password
MYSQL_PASSWORD=password
RABBIT_PASSWORD=password
SERVICE_PASSWORD=password
SERVICE_TOKEN=token

## Logs ##
LOGFILE=/opt/stack/logs/stack.sh.log
VERBOSE=True
LOG_COLOR=False
SCREEN_LOGDIR=/opt/stack/logs

RECLONE=yes

## Images ##
IMAGE_URLS+=",http://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64-disk1.img"

------------------------

[[local|localrc]]
## Compute Host ##
SERVICE_HOST=10.8.234.100
HOST_IP=10.8.234.101
MULTI_HOST=1

## Network nova-network ##
FLAT_INTERFACE=eth0
FIXED_RANGE=192.168.0.0/24
FIXED_NETWORK_SIZE=254
FLOATING_RANGE=10.8.234.128/27

## Compute Node Services ##
ENABLED_SERVICES=n-cpu,n-net,n-api,n-vol

## API URIs ##
Q_HOST=$SERVICE_HOST
MYSQL_HOST=$SERVICE_HOST
RABBIT_HOST=$SERVICE_HOST
GLANCE_HOSTPORT=$SERVICE_HOST:9292
KEYSTONE_AUTH_HOST=$SERVICE_HOST
KEYSTONE_SERVICE_HOST=$SERVICE_HOST

## Passwords ##
ADMIN_PASSWORD=password
MYSQL_PASSWORD=password
RABBIT_PASSWORD=password
SERVICE_PASSWORD=password
SERVICE_TOKEN=token

## Logs ##
LOGFILE=/opt/stack/logs/stack.sh.log
VERBOSE=True
LOG_COLOR=False
SCREEN_LOGDIR=/opt/stack/logs

------------------------

After succesfull completion of devstack/stack.sh on both nodes I can log in to Horizon and am able to see both Hypervisors "controller" and "compute1".
Though when trying to launch an instance I get the following error message:

------------------------
Error: Failed to launch instance "Test": Please try again later [Error: Remote error: ProcessExecutionError Unexpected error while running command.
Command: sudo nova-rootwrap /etc/nova/rootwrap.conf env CONFIG_FILE=["/etc/nova/nova.conf"] NETWORK_ID=1 dnsmasq --strict-order --bind-interfaces
--conf-file= --pid-file=/opt/stac].
------------------------

Is there somebody having an idea on what could be the problem here? My initial thought was that there maybe a conflict with the given DNS and/or
proxy. But I don't know how to analyze this possibility.

I'd be deeply grateful for some suggestions...

Regards, Nico



------------------------------

_______________________________________________
OpenStack-operators mailing list
OpenStack-operators at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


End of OpenStack-operators Digest, Vol 41, Issue 25
***************************************************