[Openstack-operators] migrating instances from one NFS-share to another.

[Tobias Schön]

Hi,

We are a hosting company that use openstack as a public cloud service for our 
customers and have a stack built based on redhat director. We are using NFS for 
both cinder and nova ephemeral storage and are going to migrate all of our data 
from one physical storage to another. Using NFS with openstack is not that 
common nowadays but I've checked with the support if multiple ephemeral 
mountpoints are possible but it's not.

How do we solve this the easiest way without downtime. I understand if there's 
no solution for doing this without downtime. even possible to do?
Do we have to take down all our services during this migration? We would like 
to be able to continue using the director ofcourse.

Would appreciate all advices on how to solve this or get forward to a "good" 
solution.
It's a quite small environment so far, around 6-7 TB so it shouldn't take that 
long time to migrate it as we have a 10G backend. But I'm still concerned that 
it might take a lot of time to get complete and preserve the permissions and so 
forth.
We do have cinder-volumes as well not sure how to solve that migration.

MVH/Best regards,
Tobias Schön
Sysadmin/Drifttekniker AreaX
VCP6-DCV

[VMW-LGO-CERT-PRO-6-DATA-CTR-VIRT]
[cid:image001.png@01CEED18.59C12030]

Kvarnkroken 7, 805 92  GÄVLE<http://www.fiberdata.se/>
Box 6027, 800 06 GÄVLE<http://www.fiberdata.se/>
www.areax.se<http://www.areax.se/>
www.fiberdata.se<http://www.fiberdata.se/>

Överväg miljöpåverkan innan du skriver ut detta e-postmeddelande

This communication and any attachment(s) to it are only for the use of the 
intended recipient. The information in it may be confidential and subject to 
legal privilege. Reading or dissemination of it by anyone other than the 
intended recipient is strictly prohibited. If you are not the intended 
recipient please contact the sender by reply e-mail and delete all copies of 
this message and any attachments from any drives or storage media and destroy 
any printouts.

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

Re: [Openstack-operators] What would you like in Pike?

[Tobias Schön]

This is a feature that would help a lot when building mssql-server cluster with 
shared disk instead of setting up iscsi inside the machines.

Skaffa Outlook för Android



On Mon, Jan 16, 2017 at 2:02 PM +0100, "Yaguang Tang" 
> wrote:

I'd like to see this feature  "Attach a single volume to multiple instances" 
https://blueprints.launchpad.net/nova/+spec/multi-attach-volume to be 
implmented in Nova side.

This feature has been working for more than two years, but hasn't been accepted 
by upstream...

On Sun, Jan 15, 2017 at 2:53 PM, Joshua Harlow 
> wrote:
I'll add a couple:

Cascading deletes,

Ie when a tenant/project/user is removed from keystone there should be someway 
to say deny that request if that tenant/project/user has active resources or 
there should be a away to cascade that delete through the rest of those 
resources (so they are deleted also).

Orphans (not the annie kind),

Pretty sure the osops-tools-generic repo contains a bunch of scripts around 
orphaned items cleanup; this seems *similar* to the above and it feels these 
should be like umm fixed (or those scripts should be deleted if its not an 
issue anymore)?

$ find . | grep -i "orphan"
./libvirt/cleanup-orphaned-vms.sh
./libvirt/remove-deleted-orphans.sh
./neutron/delete_orphan_floatingips.py
./neutron/listorphans.py
./nova/orphaned_vms.sh
./ansible/playbooks/orphaned-vm-clenaup.yaml
./ansible/tasks/orphaned-vms.yaml
./cinder/orphaned_volumes.sh

Same with https://github.com/openstack/ospurge (which seems like a specific 
project to try to clean this mess up, sorta funny/sad? that it has to exist in 
the first place).

Just search google for 'openstack orphan cleanup' and you'll find more scripts 
and code that people have been writing...

-Josh

Melvin Hillsman wrote:
Hey everyone,

I am hoping to get a dialogue started to gain some insight around things
Operators, Application Developers, and End Users would like to see
happen in Pike. If you had a dedicated environment, dedicated team, and
freedom to choose how you deployed, new features, older features,
enhancements, etc, and were not required to deal with customer/client
tickets, calls, and maintenances, could keep a good feedback loop
between your team and the upstream community of any project, what would
like to make happen or work on hoping the next release of OpenStack
had/included/changed/enhanced/removed…?

Kind regards,

--

*Melvin Hillsman*

Ops Technical Lead

OpenStack Innovation Center

_mrhills...@gmail.com 
>_

phone: (210) 312-1267

mobile: (210) 413-1659

Learner | Ideation | Belief | Responsibility | Command

_http://osic.org_

___
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



--
Tang Yaguang



___
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

Re: [Openstack-operators] [publicClouds-wg] Public Cloud Working Group

[Tobias Schön]

This sounds very interesting indeed, i'll join up on that aswell!

//Tobias

-Ursprungligt meddelande-
Från: Mohammed Naser [mailto:mna...@vexxhost.com] 
Skickat: den 15 november 2016 16:30
Till: m...@mattjarvis.org.uk
Kopia: OpenStack Operators; user-committee
Ämne: Re: [Openstack-operators] [publicClouds-wg] Public Cloud Working Group

This sounds very interesting, put us down! :)

On Tue, Nov 15, 2016 at 5:43 AM, matt Jarvis  wrote:
> So after input from a variety of sources over the last few weeks, I'd 
> very much like to try and put together a public cloud working group, 
> with the very high level goal of representing the interests of the 
> public cloud provider community around the globe.
>
> I'd like to propose that, in line with the new process for creation of 
> working groups, we set up some initial IRC meetings for all interested 
> parties. The goals for these initial meetings would be :
>
> 1. Define the overall scope and mission statement for the working 
> group 2. Set out the constituency for the group - communication 
> methods, definitions of public clouds, meeting schedules, chairs etc.
> 3. Identify areas of interest - eg. technical issues, collaboration 
> opportunities
>
> Before I go ahead and schedule first meetings, I'd very much like to 
> gather input from the community on interested parties, and if this 
> seems like a reasonable first step forward. My thought initially was 
> to schedule a first meeting on #openstack-operators and then decide on 
> best timings, locations and communication methods from there, but again I'd 
> welcome input.
>
> At this point it would seem to me that one of the key metrics for this 
> working group to be successful is participation as widely as possible 
> within the public cloud provider community, currently approximately 21 
> companies globally according to 
> https://www.openstack.org/marketplace/public-clouds/.
> If we could get representation from all of those companies in any 
> potential working group, then that would clearly be the best outcome, 
> although that may be optimistic ! As has become clear at recent Ops 
> events, it may be that not all of those companies are represented on 
> these lists, so I'd welcome any input on the best way to reach out to those 
> folks.
>
> Matt
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operator
> s
>



--
Mohammed Naser — vexxhost
-
D. 514-316-8872
D. 800-910-1726 ext. 200
E. mna...@vexxhost.com
W. http://vexxhost.com

___
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

Re: [Openstack-operators] Quota exceeded for resource router

[Tobias Schön]

Hi,

What does your log say?


MVH/Best regards,
Tobias Schön
Sysadmin/drifttekniker Area X
[cid:image001.png@01CEED18.59C12030]

Kvarnkroken 7, 805 92  GÄVLE<http://www.fiberdata.se/>
Box 6027, 800 06 GÄVLE<http://www.fiberdata.se/>
www.areax.se<http://www.areax.se/>
www.fiberdata.se<http://www.fiberdata.se/>

Överväg miljöpåverkan innan du skriver ut detta e-postmeddelande

This communication and any attachment(s) to it are only for the use of the 
intended recipient. The information in it may be confidential and subject to 
legal privilege. Reading or dissemination of it by anyone other than the 
intended recipient is strictly prohibited. If you are not the intended 
recipient please contact the sender by reply e-mail and delete all copies of 
this message and any attachments from any drives or storage media and destroy 
any printouts.

Från: Davíð Örn Jóhannsson [mailto:davi...@siminn.is]
Skickat: den 1 november 2016 10:33
Till: openstack-operators@lists.openstack.org
Ämne: [Openstack-operators] Quota exceeded for resource router

Ubuntu 14.04
Liberty
Neutron network

I’m trying add a router to a new project that has no configured router but I 
seem some how to manage to hit a "Quota exceeded for resource router” in 
horizon. I even tried to set the quota to 500.

+-+---+
| Field   | Value |
+-+---+
| floatingip  | 50|
| health_monitor  | -1|
| member  | -1|
| network | 10|
| pool| 10|
| port| 50|
| rbac_policy | 10|
| router  | 500   |
| security_group  | 10|
| security_group_rule | 100   |
| subnet  | 10|
| subnetpool  | -1|
| vip | 10|
+-+---+

Any ideas to what could be the cause of this?
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] glance, nova backed by NFS

[Tobias Schön]

Hi,

We have an environment with glance and cinder using NFS.
It's important that they have the correct rights. The shares should be owned by 
nova on compute if mounted up on /var/lib/nova/instances
And the same for nova and glance on the controller..

It's important that you map the glance and nova up in fstab.

The cinder one is controlled by the nfsdriver.

We are running rhelosp6, Openstack Juno.

This parameter is used:
nfs_shares_config=/etc/cinder/shares-nfs.conf in the /etc/cinder/cinder.conf 
file and then we have specified the share in /etc/cinder/shares-nfs.conf.

chmod 0640 /etc/cinder/shares-nfs.conf

setsebool -P virt_use_nfs on
This one is important to make it work with SELinux

How up to date this is actually I don't know tbh, but it was up to date as of 
redhat documentation when we deployed it around 1.5y ago.

//Tobias

-Ursprungligt meddelande-
Från: Curtis [mailto:serverasc...@gmail.com] 
Skickat: den 12 oktober 2016 19:21
Till: openstack-operators@lists.openstack.org
Ämne: [Openstack-operators] glance, nova backed by NFS

Hi All,

I've never used NFS with OpenStack before. But I am now with a small lab 
deployment with a few compute nodes.

Is there anything special I should do with NFS and glance and nova? I remember 
there was an issue way back when of images being deleted b/c certain components 
weren't aware they are on NFS. I'm guessing that has changed but just wanted to 
check if there is anything specific I should be doing configuration-wise.

I can't seem to find many examples of NFS usage...so feel free to point me to 
any documentation, blog posts, etc. I may have just missed it.

Thanks,
Curtis.

___
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