[Openstack-operators] [openstack-operators] OpenStack Board of Directors 2016

2016-01-11 Thread JJ Asghar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512


Hey everyone,

Today, you hopefully received a ballot for the OpenStack Board of
Directors election. If you are reading this, you likely have a vested
interest in the Operator Community for OpenStack. I'd like to ask for
your vote[1].

If you've been tracking my work, both completed and in progress, I
hope you agree and support these changes. I can take this momentum to
the elected position and help make positive changes on the Board also.

I promise to do my best to represent the OpenStack Operators
community, and thanks for your time and consideration.

[1]: http://bit.ly/JJ-4-OpenStack-BoD-2016

- -- 
Best Regards,
JJ Asghar
c: 512.619.0722 t: @jjasghar irc: j^2
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJWlCqeAAoJEDZbxzMH0+jTxJAP/0WpmO0dIhgDtHfOoEEHu7fK
VfsB97YrsJmDwJxepA1ZSx1rK3WGNBtKuaJ/GrfUEIoED9kvNeeUZxdC2KcSKsJQ
BmuGa8CIH/pcCszw6BQAEEq05CbFdS0w3ryIeJDO9VCtUTEeT/9oo2a17Yb/bxwZ
ErcTmzoAlFiNZblXAedhEU0L/0XoKMcK95dXLKQ5NW6fdqx8YNvy/Kv2KZTfSPcA
iD2zp839ocn8Jo/RkoPsZm87AGWyNDxgz+/fkzoiMjbUrrG9clKAnJC5WidOOvR2
hzmEkfKxgI5ZxbFlWhJRWNXai69UQcpz5OXPkrJrUiAB25hCKwvE7af+/Qs4NVO/
7j47FLgEphJVHMqdmA7C1Yeb+5sBI+0Z9U1aD3yHsXPDbmXIehWxI9MGmh9HqXL7
XtxwSDLCQOdjx5zZu3akYxL8HcMAijEFghEWRMHWqimduPEiV1CclSDDtsu5z6s2
7b6jSsFue4n6ppiPPSnoWT1uOI8Rt+XbMAnX/7svGjoRMUkqE8iUyAJwAZC82RHr
5Z/EFunbBu4k9ypuInoXB52oNCw8sbGOnir2J7gX7VC5e4uXEyRyalp6UggJc4yA
zLrVbu1wjllMABzfuwqnwfY1HAaRgUDIKP9GgfqFeH9Y7A62yzd/9F/RrrOpnmOG
6EXJvWXE47r3kwTWhef8
=Omiv
-END PGP SIGNATURE-

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


[Openstack-operators] security groups not working on one compute node

2016-01-11 Thread Akshay Kumar Sanghai
Hi,
I am running a kilo openstack setup with 3 nodes, 1 controller and 2
compute. Suppose i have 2 VMs , vm1 on compute node1 and vm2 on compute
node2 . When i change the security groups for vm1 when vm is running ,then
i can see the change is implemented. But for vm2 ,change is not implemented
while vm is running. For example, i am able to ping vm1 and vm2. But when i
remove the security group for icmp for both vm1 and vm2, I can't ping vm1
but i am still able to ping vm2. The change is implemented only when i
reboot the vm. I have checked the confiuration file for ml2_conf.ini , its
same for both compute nodes. What can be other possible problems to look
into?

Thanks,
Akshay
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


[Openstack-operators] question on project_id formats

2016-01-11 Thread Sean Dague
It has come in looking at ways to remove project_ids from API urls that
the format of a project_id is actually quite poorly specified in
OpenStack. This makes dual stacking supporting the project_id and not
the project id at the same time a little challenging because the
matching to figure out which controller is going to get called goes a
little nuts.

For anyone using upstream Keystone, they'll get a uuid (no dashes)
unless they work really hard at changing it.

RAX currently doesn't use upstream Keystone, they use ints as their
project ids.

What I'm curious about is if anyone else is doing something in
specifying project_ids in their cloud. As this is going to impact the
solution going forward here.

We're currently pondering a default enforcement of uuid form if you are
using the project id in the url, with a config override to allow a
different schema (as we know there is at least one cloud in the wild
that is different).

Comments welcomed.

-Sean

-- 
Sean Dague
http://dague.net

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


Re: [Openstack-operators] [nova] Recovering instances from old system

2016-01-11 Thread Kris G. Lindgren
Seconding what Matt said.  You are also going to need to spend some time at the 
kilo code level to do the flavor migrations.  As that was a requirement from 
kilo -> liberty.  I also know that you needed to be on kilo.1 (or .2) to go to 
liberty to fix a bug in Numa Node pinning (iirc).

I would also look at the upgrade requirements for every version between 
icehouse and liberty and you are also going to need to perform those actions.


___
Kris Lindgren
Senior Linux Systems Engineer
GoDaddy

From: Matt Fischer >
Date: Monday, January 11, 2016 at 8:29 AM
To: Liam Haworth 
>
Cc: 
"openstack-operators@lists.openstack.org"
 
>
Subject: Re: [Openstack-operators] [nova] Recovering instances from old system

Personally, I'd just try to load the instance images like you said. If you try 
to load Icehouse records onto Liberty code its not going to work. Typically 
you'd do the upgrade one step at a time with database migrations done at every 
step.

On Sun, Jan 10, 2016 at 9:58 PM, Liam Haworth 
> wrote:
Hey Abel,

When I say 'wiped everything clean" I mean that we made backups of the 
databases and configuration on all hosts before reinstalling Ubuntu 14.04 LTS 
on top to start with a clean slate, we did this because we decided to make the 
change to the LinuxBridge agent from the OpenVSwitch agent plus we where 
upgrading from Icehouse to Liberty, this along with a major restructure with 
how our network is laid out.

Really I'm just looking for some input on if I should attempt to extract the 
records of the instance backed up from the database and manually insert them or 
if I should take the instance dicks and load them in as images and spin them 
backup from there.

Hopefully I made a bit more sense this time, sorry.

On Sat, 9 Jan 2016 at 03:26 Abel Lopez 
> wrote:
I would expect that if you have the databases in place, and they went through 
the proper migrations, that your instances would still be there.
You can check the nova database instances table using the uuid.

How exactly did you 'wipe everything clean'?

On Jan 7, 2016, at 5:35 PM, Liam Haworth 
> wrote:

Hey guys,

I just recently rebuilt the OpenStack infrastructure at my work to upgrade from 
Juno to Liberty, before wiping everything clean I made dumps of all the 
databases and the instances where persisted though the upgrade via NFS.

Now that I have the infrastructure up and going again I was wondering what 
would be the best way to import the instances back in, I understand I may need 
to change some fields in the database dumps to change project ids and such but 
I just wanted to get some input on if this is a good idea or if there is a 
better way to do this?

Kind regards,
--
Liam Haworth | Junior Software Engineer | 
www.bluereef.com.au
_
T: +61 3 9898 8000 | F: +61 3 9898 8055


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

--
Liam Haworth | Junior Software Engineer | 
www.bluereef.com.au
_
T: +61 3 9898 8000 | F: +61 3 9898 8055



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


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