Re: [Openstack-operators] libvirt: make snapshot use RBD snapshot/clone when available

[Logan V.]

Have been using it since kilo. It was a clean pick into Liberty and worked
great for me.

Logan

On Friday, September 2, 2016, Saverio Proto  wrote:

> Hello,
>
> this is merged upstream in Mitaka:
>
> https://review.openstack.org/#/c/287954/
>
> anyone already did a cherry pick in Liberty and is running this in
> production ?
> I plan to test this soon. Any feedback is appreciated !
>
> thank you
>
> Saverio
>
> ___
> 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] Nova

[Adam Lawson]

Mike that's just as I suspected. To be super clear, does KVM in particular
know how to distinguish between Ubuntu v12 versus v16? In other words, do I
need to be running a specific version of KVM hypervisor so it can host
guests running the latest version of Ubuntu?

Again, this was brought up as being a firm requirement but I've never ever
heard of such a requirement unless we're debating KVM versus ESXi so I
wanted to get my facts straight before I confirmed to the team one way or
another.

//adam


*Adam Lawson*

AQORN, Inc.
427 North Tatnall Street
Ste. 58461
Wilmington, Delaware 19801-2230
Toll-free: (844) 4-AQORN-NOW ext. 101
International: +1 302-387-4660
Direct: +1 916-246-2072

On Fri, Sep 2, 2016 at 1:53 PM, Mike Smith  wrote:

> Hi Adam -
>
> The OS of the guest is independent of the Openstack version.  Your choice
> of hypervisor (KVM, VMWare, HyperV, etc) would just need to support the OS
> version that you want to run on your guests.
>
> Mike Smith
> Lead Cloud Systems Architect
> Overstock.com 
>
>
>
> On Sep 2, 2016, at 2:46 PM, Adam Lawson  wrote:
>
> Hey everyone, do specific versions of OpenStack necessitate specific
> versions of guest os's? I.e. if I'm running a mitaka cloud platform, do the
> guest vm operating systems need to be a specific version of Linux? My
> understanding is the two are totally unrelated when the VM's are running
> Linux but I wanted to check if things have recently changed without my
> knowledge.
>
> //adam
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
>
> --
>
> CONFIDENTIALITY NOTICE: This message is intended only for the use and
> review of the individual or entity to which it is addressed and may contain
> information that is privileged and confidential. If the reader of this
> message is not the intended recipient, or the employee or agent responsible
> for delivering the message solely to the intended recipient, you are hereby
> notified that any dissemination, distribution or copying of this
> communication is strictly prohibited. If you have received this
> communication in error, please notify sender immediately by telephone or
> return email. Thank you.
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] ElasticSearch on OpenStack

[Jeremy Stanley]

On 2016-09-02 12:36:27 + (+), Tim Bell wrote:
> Has anyone had experience running ElasticSearch on top of OpenStack VMs ?

The OpenStack community infrastructure includes a modest
ElasticSearch cluster indexing CI job results, behind the
http://logstash.openstack.org/ and
http://status.openstack.org/elastic-recheck/ services. We also use
the CirrusSearch extension for Mediawiki (which relies on a local
ElasticSearch instance) providing page searching for the
https://wiki.openstack.org/ service. All of these run on virtual
machine instances in Rackspace at the moment.

> Are there any tuning recommendations ?

Our use case isn't nearly as large as some, but you may be able to
find some ideas in our Puppet module for ES and the customization
class from which we instantiate it:

https://git.openstack.org/cgit/openstack-infra/puppet-elasticsearch/tree/

https://git.openstack.org/cgit/openstack-infra/system-config/tree/modules/openstack_project/manifests/elasticsearch_node.pp

-- 
Jeremy Stanley

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

Re: [Openstack-operators] Nova

[Mike Smith]

Hi Adam -

The OS of the guest is independent of the Openstack version.  Your choice of 
hypervisor (KVM, VMWare, HyperV, etc) would just need to support the OS version 
that you want to run on your guests.

Mike Smith
Lead Cloud Systems Architect
Overstock.com



On Sep 2, 2016, at 2:46 PM, Adam Lawson 
> wrote:


Hey everyone, do specific versions of OpenStack necessitate specific versions 
of guest os's? I.e. if I'm running a mitaka cloud platform, do the guest vm 
operating systems need to be a specific version of Linux? My understanding is 
the two are totally unrelated when the VM's are running Linux but I wanted to 
check if things have recently changed without my knowledge.

//adam

___
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

[Openstack-operators] Nova

[Adam Lawson]

Hey everyone, do specific versions of OpenStack necessitate specific
versions of guest os's? I.e. if I'm running a mitaka cloud platform, do the
guest vm operating systems need to be a specific version of Linux? My
understanding is the two are totally unrelated when the VM's are running
Linux but I wanted to check if things have recently changed without my
knowledge.

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

Re: [Openstack-operators] ElasticSearch on OpenStack

[David Medberry]

omitted on more line:

give java heap 30GB, and leave the rest of the memory to the OS filesystem
cache so that Lucene can make best use of it.

On Fri, Sep 2, 2016 at 2:15 PM, David Medberry 
wrote:

> From Nathan (on TWC Cloud team):
>
> Nathan: The page at https://www.elastic.co/guide/en/elasticsearch/guide/
> current/heap-sizing.html gives you good advice on a maximum size for the
> elasticsearch VM's memory.
>
> Nathan: suggest you pick a flavor with 64GB RAM or less, then base other
> sizing things off of that (i.e. choose a flavor with 64GB of RAM and as
> many CPUs as possible for that RAM allocation, then base disk size on
> testing of your use case)
>
> On Fri, Sep 2, 2016 at 6:46 AM, David Medberry 
> wrote:
>
>> Hey Tim,
>> We've just started this effort. I'll see if the guy running the service
>> can comment today.
>>
>> On Fri, Sep 2, 2016 at 6:36 AM, Tim Bell  wrote:
>>
>>>
>>>
>>> Has anyone had experience running ElasticSearch on top of OpenStack VMs ?
>>>
>>>
>>>
>>> Are there any tuning recommendations ?
>>>
>>>
>>>
>>> Thanks
>>>
>>> Tim
>>>
>>> ___
>>> 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] ElasticSearch on OpenStack

[David Medberry]

>From Nathan (on TWC Cloud team):

Nathan: The page at
https://www.elastic.co/guide/en/elasticsearch/guide/current/heap-sizing.html
gives you good advice on a maximum size for the elasticsearch VM's memory.

Nathan: suggest you pick a flavor with 64GB RAM or less, then base other
sizing things off of that (i.e. choose a flavor with 64GB of RAM and as
many CPUs as possible for that RAM allocation, then base disk size on
testing of your use case)

On Fri, Sep 2, 2016 at 6:46 AM, David Medberry 
wrote:

> Hey Tim,
> We've just started this effort. I'll see if the guy running the service
> can comment today.
>
> On Fri, Sep 2, 2016 at 6:36 AM, Tim Bell  wrote:
>
>>
>>
>> Has anyone had experience running ElasticSearch on top of OpenStack VMs ?
>>
>>
>>
>> Are there any tuning recommendations ?
>>
>>
>>
>> Thanks
>>
>> Tim
>>
>> ___
>> 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] Database cleanup scripts?

[Edmund Rhudy (BLOOMBERG/ 120 PARK)]

Great post, thanks. nova is my primary target for cleanup (to get rid of 
deleted instances and virtual interfaces), the other databases are mostly okay.

From: m...@mattfischer.com 
Subject: Re: [Openstack-operators] Database cleanup scripts?

Hi Ed,

Good to meet you in NYC last week. And fortunate timing for the question, I 
just published a summary of my experiences here: 
http://www.mattfischer.com/blog/?p=744

I know that the Nova DB cleanup stuff was broken in the past, and IIRC you are 
on Kilo, so it may not work for you until you get to Liberty or later. The 
Cinder DB cleanup is broken on Liberty and I think also Kilo, you will need 
Mitaka for that or you could roll your own. Our largest DBs were heat and nova 
so that was my focus. 


On Fri, Sep 2, 2016 at 8:14 AM, Edmund Rhudy (BLOOMBERG/ 120 PARK) 
 wrote:

Does anyone have any database cleanup scripts (especially for Nova/Cinder) that 
they are proud of and are willing to share? Googling around didn't turn up 
anything I felt was trustworthy; I found one in a GitHub Gist and stopped 
reading as soon as it disabled foreign key constraints.
___
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] libvirt: make snapshot use RBD snapshot/clone when available

[Matt Riedemann]

On 9/2/2016 10:11 AM, Saverio Proto wrote:

Hello,

this is merged upstream in Mitaka:

https://review.openstack.org/#/c/287954/

anyone already did a cherry pick in Liberty and is running this in production ?
I plan to test this soon. Any feedback is appreciated !

thank you

Saverio

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



The metacloud guys that proposed it had been running it for several 
releases in production before it landed in mitaka, so yes.


--

Thanks,

Matt Riedemann


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

Re: [Openstack-operators] Database cleanup scripts?

[Matt Riedemann]

On 9/2/2016 10:20 AM, Arne Wiebalck wrote:



On 02 Sep 2016, at 17:08, Matt Fischer > wrote:


On Fri, Sep 2, 2016 at 8:57 AM, Abel Lopez > wrote:

For cinder, since kilo, we've had 'cinder-manage db purge-deleted'


This is the issue we see with this tool in Liberty, I think this might
be fixed in M.

# cinder-manage db purge 365
 (some stuff works here)
...

2016-09-02 15:07:02.196 203924 ERROR cinder DBReferenceError:
(pymysql.err.IntegrityError) (1451, u'Cannot delete or update a parent
row: a foreign key constraint fails
(`cinder`.`volume_glance_metadata`, CONSTRAINT
`volume_glance_metadata_ibfk_2` FOREIGN KEY (`snapshot_id`) REFERENCES
`snapshots` (`id`))') [SQL: u'DELETE FROM snapshots WHERE
snapshots.deleted_at < %s'] [parameters: (datetime.datetime(2015, 9,
3, 15, 7, 2, 189701),)]



I think this is fixed here: https://review.openstack.org/#/c/338228/
(which comes with Newton only).

Cheers,
 Arne


--
Arne Wiebalck
CERN IT



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



If someone can backport that to stable/mitaka I'll +2 it. It's not a 
clean backport to mitaka.


There are also archive scripts in the osops repo here:

http://git.openstack.org/cgit/openstack/osops-tools-generic/tree/nova/openstack_db_archive.sh

I haven't used ^ personally, but I know it was written because the 
archive scripts in nova-manage were broken until a couple of releases 
back where we fixed the FKey issue.


We're still working on getting a purge instances nova-manage command in 
ocata (don't archive, straight up delete).


--

Thanks,

Matt Riedemann


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

Re: [Openstack-operators] Database cleanup scripts?

[Arne Wiebalck]

On 02 Sep 2016, at 17:08, Matt Fischer 
> wrote:


On Fri, Sep 2, 2016 at 8:57 AM, Abel Lopez 
> wrote:
For cinder, since kilo, we've had 'cinder-manage db purge-deleted'


This is the issue we see with this tool in Liberty, I think this might be fixed 
in M.

# cinder-manage db purge 365
 (some stuff works here)
...

2016-09-02 15:07:02.196 203924 ERROR cinder DBReferenceError: 
(pymysql.err.IntegrityError) (1451, u'Cannot delete or update a parent row: a 
foreign key constraint fails (`cinder`.`volume_glance_metadata`, CONSTRAINT 
`volume_glance_metadata_ibfk_2` FOREIGN KEY (`snapshot_id`) REFERENCES 
`snapshots` (`id`))') [SQL: u'DELETE FROM snapshots WHERE snapshots.deleted_at 
< %s'] [parameters: (datetime.datetime(2015, 9, 3, 15, 7, 2, 189701),)]


I think this is fixed here: https://review.openstack.org/#/c/338228/
(which comes with Newton only).

Cheers,
 Arne


--
Arne Wiebalck
CERN IT

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

[Openstack-operators] libvirt: make snapshot use RBD snapshot/clone when available

[Saverio Proto]

Hello,

this is merged upstream in Mitaka:

https://review.openstack.org/#/c/287954/

anyone already did a cherry pick in Liberty and is running this in production ?
I plan to test this soon. Any feedback is appreciated !

thank you

Saverio

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

[Openstack-operators] Database cleanup scripts?

[Edmund Rhudy (BLOOMBERG/ 120 PARK)]

Does anyone have any database cleanup scripts (especially for Nova/Cinder) that 
they are proud of and are willing to share? Googling around didn't turn up 
anything I felt was trustworthy; I found one in a GitHub Gist and stopped 
reading as soon as it disabled foreign key constraints.___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] ElasticSearch on OpenStack

[Van Leeuwen, Robert]

Hi,

I had some “interesting” issues in the past with sparse files on xfs with 
elasticsearch:
http://engineering.spilgames.com/hypervisor-kernel-panics-hit-2014-sl6-5/

If you pre-allocate your files you should be good.

Cheers,
Robert van Leeuwen

From: Tim Bell 
Date: Friday, September 2, 2016 at 2:36 PM
To: openstack-operators 
Subject: [Openstack-operators] ElasticSearch on OpenStack


Has anyone had experience running ElasticSearch on top of OpenStack VMs ?

Are there any tuning recommendations ?

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

Re: [Openstack-operators] ElasticSearch on OpenStack

[Matt Van Winkle]

We are running entire ELK clusters on our undercloud.  Let me see if I can 
point our resident metrics expert at this as well.

VW

Sent from my iPhone

On Sep 2, 2016, at 7:50 AM, David Medberry 
> wrote:

Hey Tim,
We've just started this effort. I'll see if the guy running the service can 
comment today.

On Fri, Sep 2, 2016 at 6:36 AM, Tim Bell 
> wrote:

Has anyone had experience running ElasticSearch on top of OpenStack VMs ?

Are there any tuning recommendations ?

Thanks
Tim

___
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
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Delete cinder service

[Arne Wiebalck]

On 02 Sep 2016, at 11:50, Nick Jones 
> wrote:

On 2 Sep 2016, at 9:28, William Josefsson wrote:

[..]

Is there any cleanup of volumes entries with deleted=1, or is it
normal these old entries lay around? thx will

There’s a timely blog post from Matt Fischer on exactly that subject:

http://www.mattfischer.com/blog/?p=744

His comment regarding the Cinder DB suggests that this process was broken in 
Liberty, however.  Would be good to have confirmation that it’s been rectified 
in Mitaka.

We actually did try it on Mitaka on a copy of our DB and ran into this one:
https://bugs.launchpad.net/cinder/+bug/1489523 (filed by Matt, btw :-)

We filed a patch, but this will only come with Newton from what I see.

Cheers,
 Arne

--
Arne Wiebalck
CERN IT

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

[Openstack-operators] ElasticSearch on OpenStack

[Tim Bell]

Has anyone had experience running ElasticSearch on top of OpenStack VMs ?

Are there any tuning recommendations ?

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

Re: [Openstack-operators] Delete cinder service

[Nick Jones]

On 2 Sep 2016, at 9:28, William Josefsson wrote:

[..]


Is there any cleanup of volumes entries with deleted=1, or is it
normal these old entries lay around? thx will


There’s a timely blog post from Matt Fischer on exactly that subject:

http://www.mattfischer.com/blog/?p=744

His comment regarding the Cinder DB suggests that this process was 
broken in Liberty, however.  Would be good to have confirmation that 
it’s been rectified in Mitaka.


--

-Nick

--
DataCentred Limited registered in England and Wales no. 05611763

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

Re: [Openstack-operators] [OpenStack-DefCore] [OSOps] Ansible work load test for interop patch set

[Matt Jarvis]

I was going to review this, but it got merged before I got to it. There's a
couple of fundamental issues with these scripts, the lack of error handling
being one, but more importantly using the existence of apt or yum to check
for OS version is not safe as either can exist on either platform. I'll put
in some changes if I get a chance.

On 31 August 2016 at 20:47, Kris G. Lindgren  wrote:

> I originally agreed with you, but then I thought about it more this way:
> It’s a tool to test to see if clouds are interop compatible (atleast that
> heat works the same on the two clouds).  While not technically a tool to
> manage openstack.  But still something that some Operators could want to
> know if they are looking at doing hybrid cloud.  Or they may want to ensure
> that two of their own private clouds are interop compatible.
>
>
>
> ___
>
> Kris Lindgren
>
> Senior Linux Systems Engineer
>
> GoDaddy
>
>
>
> *From: *Joseph Bajin 
> *Date: *Wednesday, August 31, 2016 at 1:39 PM
> *To: *"Yih Leong, Sun." 
> *Cc: *OpenStack Operators ,
> defcore-committee 
> *Subject: *Re: [Openstack-operators] [OpenStack-DefCore] [OSOps] Ansible
> work load test for interop patch set
>
>
>
> This looks like this was merged, but no one really answered my questions
> about an "InterOp Challenge" code base going into the Operators
> repository.
>
>
>
> --Joe
>
>
>
> On Wed, Aug 31, 2016 at 12:23 PM, Yih Leong, Sun. 
> wrote:
>
> Can someone from ospos please review the following patch?
>
> https://review.openstack.org/#/c/351799/
>
>
>
> The patchset was last updated Aug 11th.
>
> Thanks!
>
>
>
>
>
>
>
> On Tue, Aug 16, 2016 at 7:17 PM, Joseph Bajin 
> wrote:
>
> Sorry about that. I've been a little busy as of late, and was able to get
> around to taking a look.
>
>
>
> I have a question about these.   What exactly is the Interop Challenge?
> The OSOps repos are usually for code that can help Operators maintain and
> run their cloud.   These don't necessarily look like what we normally see
> submitted.
>
>
>
> Can you expand on what the InterOp Challenge is and if it is something
> that Operators would use?
>
>
>
> Thanks
>
>
>
> Joe
>
>
>
> On Tue, Aug 16, 2016 at 3:02 PM, Shamail  wrote:
>
>
>
> > On Aug 16, 2016, at 1:44 PM, Christopher Aedo  wrote:
> >
> > Tong Li, I think the best place to ask for a look would be the
> > Operators mailing list
> > (http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
> ).
> > I've cc'd that list here, though it looks like you've already got a +2
> > on it at least.
> +1
>
> I had contacted JJ earlier and he told me that the best person to contact
> would be Joseph Bajin (RaginBajin in IRC).  I've also added an OSOps tag to
> this message.
>
> >
> > -Christopher
> >
> >> On Tue, Aug 16, 2016 at 7:59 AM, Tong Li  wrote:
> >> The patch set has been submitted to github for awhile, can some one
> please
> >> review the patch set here?
> >>
> >> https://review.openstack.org/#/c/354194/
> >>
> >> Thanks very much!
> >>
> >> Tong Li
> >> IBM Open Technology
> >> Building 501/B205
> >> liton...@us.ibm.com
> >>
> >>
> >> ___
> >> Defcore-committee mailing list
> >> defcore-commit...@lists.openstack.org
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
> >
> > ___
> > Defcore-committee mailing list
> > defcore-commit...@lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
>
> ___
>
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
>
>
> ___
> Defcore-committee mailing list
> defcore-commit...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
>
>
>
>
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>

-- 
DataCentred Limited registered in England and Wales no. 05611763
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Delete cinder service

[Arne Wiebalck]

There is ‘cinder-manage db purge’ to delete entries which are marked as deleted.

I never tried it (and suggest to start with a copy of the db before touching 
the prod
ones). We usually do not purge databases unless we hit an issue.

Cheers,
 Arne


> On 02 Sep 2016, at 10:28, William Josefsson  
> wrote:
> 
> Thanks everyone for your replies! I did a safe select first to make
> sure there was only one match. than I updated deleted=1 for that
> service which seem to work. Now 'cinder service-list' shows the right
> output.
> 
> I notice in DB 'volumes', there are plenty of old volume entries, long
> ago deleted, and they have 'deleted=1'. The host value, is the old
> host name that no longer exist.
> 
> Is there any cleanup of volumes entries with deleted=1, or is it
> normal these old entries lay around? thx will
> 
> 
> 
> On Fri, Sep 2, 2016 at 1:24 AM, Kris G. Lindgren  
> wrote:
>> Just be careful with LIMIT x on your servers if you have replicated mysql 
>> databases.  At least under older versions of mysql this can lead to broken 
>> replication as the results of the query performed on the master and on the 
>> slave are not guaranteed to be the same.
>> 
>> https://dev.mysql.com/doc/refman/5.7/en/replication-features-limit.html
>> 
>> ___
>> Kris Lindgren
>> Senior Linux Systems Engineer
>> GoDaddy
>> 
>> On 9/1/16, 9:51 AM, "Nick Jones"  wrote:
>> 
>> 
>>On 1 Sep 2016, at 15:36, Jonathan D. Proulx wrote:
>> 
>>> On Thu, Sep 01, 2016 at 04:25:25PM +0300, Vladimir Prokofev wrote:
>>> :I've used direct database update to achive this in Mitaka:
>>> :use cinder;
>>> :update services set deleted = '1' where ;
>>> 
>>> 
>>> I belive the official way is:
>>> 
>>> cinder-manage service remove  
>>> 
>>> Which probably more or less does the same thing...
>> 
>>Yep.  Both options basically require direct interaction with the
>>database as opposed to via a Cinder API call, but at least with
>>cinder-manage the scope for making a mistake is far more limited than
>>missing some qualifying clause off an UPDATE statement (limit 1 is your
>>friend!) ;)
>> 
>>—
>> 
>>-Nick
>> 
>>--
>>DataCentred Limited registered in England and Wales no. 05611763
>> 
>>___
>>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
> 
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

--
Arne Wiebalck
CERN IT

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

Re: [Openstack-operators] Delete cinder service

[William Josefsson]

Thanks everyone for your replies! I did a safe select first to make
sure there was only one match. than I updated deleted=1 for that
service which seem to work. Now 'cinder service-list' shows the right
output.

I notice in DB 'volumes', there are plenty of old volume entries, long
ago deleted, and they have 'deleted=1'. The host value, is the old
host name that no longer exist.

Is there any cleanup of volumes entries with deleted=1, or is it
normal these old entries lay around? thx will



On Fri, Sep 2, 2016 at 1:24 AM, Kris G. Lindgren  wrote:
> Just be careful with LIMIT x on your servers if you have replicated mysql 
> databases.  At least under older versions of mysql this can lead to broken 
> replication as the results of the query performed on the master and on the 
> slave are not guaranteed to be the same.
>
> https://dev.mysql.com/doc/refman/5.7/en/replication-features-limit.html
>
> ___
> Kris Lindgren
> Senior Linux Systems Engineer
> GoDaddy
>
> On 9/1/16, 9:51 AM, "Nick Jones"  wrote:
>
>
> On 1 Sep 2016, at 15:36, Jonathan D. Proulx wrote:
>
> > On Thu, Sep 01, 2016 at 04:25:25PM +0300, Vladimir Prokofev wrote:
> > :I've used direct database update to achive this in Mitaka:
> > :use cinder;
> > :update services set deleted = '1' where ;
> >
> >
> > I belive the official way is:
> >
> > cinder-manage service remove  
> >
> > Which probably more or less does the same thing...
>
> Yep.  Both options basically require direct interaction with the
> database as opposed to via a Cinder API call, but at least with
> cinder-manage the scope for making a mistake is far more limited than
> missing some qualifying clause off an UPDATE statement (limit 1 is your
> friend!) ;)
>
> —
>
> -Nick
>
> --
> DataCentred Limited registered in England and Wales no. 05611763
>
> ___
> 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

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

Re: [Openstack-operators] Converged infrastructure

[Matt Jarvis]

Hi Mohammed

Could you give us an idea of what your node hardware looks like, and how
you split it up ? I'm doing some work on the economics of this, so I'd like
to understand the RAM and physical cores split.

On 1 September 2016 at 17:58, Mohammed Naser  wrote:

> I proposed a talk for the Summit which unfortunately did not make it.
>
> We overprovision compute nodes with memory enough for Ceph to run and
> we isolate an N number of cores dedicated for the OSD processes.  That
> way, there is no competition between VMs and OSDs.  We run all SSD and
> it has been quite successful for us.
>
> On Thu, Sep 1, 2016 at 12:37 AM, Blair Bethwaite
>  wrote:
> > Following on from Edmund's issues... People talking about doing this
> > typically seem to cite cgroups as the way to avoid CPU and memory
> > related contention - has anyone been successful in e.g. setting up
> > cgroups on a nova qemu+kvm hypervisor to limit how much of the machine
> > nova uses?
> >
> > On 1 September 2016 at 04:15, Edmund Rhudy (BLOOMBERG/ 120 PARK)
> >  wrote:
> >> We currently run converged at Bloomberg with Ceph (all SSD) and I
> strongly
> >> dislike it. OSDs and VMs battle for CPU time and memory, VMs steal
> memory
> >> that would go to the HV pagecache, and it puts a real dent in any plans
> to
> >> be able to deploy hypervisors (mostly) statelessly. Ceph on our largest
> >> compute cluster spews an endless litany of deep-scrub-related
> HEALTH_WARNs
> >> because of memory steal from the VMs depleting available pagecache
> memory.
> >> We're going to increase the OS memory reservation in nova.conf to try to
> >> alleviate some of the worst of the memory steal, but it's been one hack
> >> after another to keep it going. I hope to be able to re-architect our
> design
> >> at some point to de-converge Ceph from the compute nodes so that the two
> >> sides can evolve separately once more.
> >>
> >> From: matt.jar...@datacentred.co.uk
> >> Subject: Re:[Openstack-operators] Converged infrastructure
> >>
> >> Time once again to dredge this topic up and see what the wider operators
> >> community thinks this time :) There were a fair amount of summit
> submissions
> >> for Barcelona talking about converged and hyper-converged
> infrastructure, it
> >> seems to be the topic de jour from vendors at the minute despite feeling
> >> like we've been round this before with Nebula, Piston Cloud etc.
> >>
> >> Like a lot of others we run Ceph, and we absolutely don't converge our
> >> storage and compute nodes for a variety of performance and management
> >> related reasons. In our experience, the hardware and tuning
> characteristics
> >> of both types of nodes are pretty different, in any kind of recovery
> >> scenarios Ceph eats memory, and it feels like creating a SPOF.
> >>
> >> Having said that, with pure SSD clusters becoming more common, some of
> those
> >> issues may well be mitigated, so is anyone doing this in production now
> ? If
> >> so, what does your hardware platform look like, and are there issues
> with
> >> these kinds of architectures ?
> >>
> >> Matt
> >>
> >> DataCentred Limited registered in England and Wales no. 05611763
> >>
> >> ___
> >> 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
> >>
> >
> >
> >
> > --
> > Cheers,
> > ~Blairo
> >
> > ___
> > OpenStack-operators mailing list
> > OpenStack-operators@lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
>
> --
> 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
>

-- 
DataCentred Limited registered in England and Wales no. 05611763
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators